<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Yes. 100% upstream.<div class=""><br class=""></div><div class="">And although I’ve referred to it as “reseller” (following the previous Keystone BP), it’s a much more generic pattern. Long term, I think it turns into something like a supply chain framework for services.</div><div class=""><br class=""></div><div class="">Geoff</div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Apr 28, 2015, at 3:51 AM, Tim Bell <<a href="mailto:Tim.Bell@cern.ch" class="">Tim.Bell@cern.ch</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" class="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)" class="">
<style class=""><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->

<div lang="EN-GB" link="blue" vlink="purple" class="">
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class="">Geoff,<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class=""> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class="">Would the generic parts of your “reseller” solution by contributed to the upstream projects (e.g. glance, horizon, ceilometer) ? It
 would be good to get the core components understanding hierarchical multitenancy for all the use cases.<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class=""> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class="">The nova quota work is being submitted upstream for Liberty by Sajeesh (<a href="https://blueprints.launchpad.net/nova/+spec/nested-quota-driver-api" class="">https://blueprints.launchpad.net/nova/+spec/nested-quota-driver-api</a>)<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class=""> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class="">The cinder quota proposal is also underway (<a href="https://blueprints.launchpad.net/cinder/+spec/cinder-nested-quota-driver" class="">https://blueprints.launchpad.net/cinder/+spec/cinder-nested-quota-driver</a>)<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class=""> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class="">Tim<o:p class=""></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US" class=""> </span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt" class="">
<div class="">
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm" class=""><p class="MsoNormal"><b class=""><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif" class="">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif" class=""> Geoff Arnold [<a href="mailto:geoff@geoffarnold.com" class="">mailto:geoff@geoffarnold.com</a>]
<br class="">
<b class="">Sent:</b> 28 April 2015 08:11<br class="">
<b class="">To:</b> OpenStack Development Mailing List (not for usage questions)<br class="">
<b class="">Subject:</b> Re: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy and Glance?<o:p class=""></o:p></span></p>
</div>
</div><p class="MsoNormal"><o:p class=""> </o:p></p>
<div class=""><p class="MsoNormal">Use cases:<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><a href="https://wiki.openstack.org/wiki/HierarchicalMultitenancy" class="">https://wiki.openstack.org/wiki/HierarchicalMultitenancy</a><o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><p class="MsoNormal">Blueprints:<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal">(Kilo):<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><a href="https://blueprints.launchpad.net/keystone/+spec/hierarchical-multitenancy" class="">https://blueprints.launchpad.net/keystone/+spec/hierarchical-multitenancy</a><o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><a href="https://blueprints.launchpad.net/keystone/+spec/reseller" class="">https://blueprints.launchpad.net/keystone/+spec/reseller</a><o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal">(Liberty):<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><a href="https://blueprints.launchpad.net/nova/+spec/multiple-level-user-quota-management" class="">https://blueprints.launchpad.net/nova/+spec/multiple-level-user-quota-management</a><o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><a href="https://blueprints.launchpad.net/nova/+spec/nested-quota-driver-api" class="">https://blueprints.launchpad.net/nova/+spec/nested-quota-driver-api</a><o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal">(Pending):<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><a href="https://blueprints.launchpad.net/horizon/+spec/hierarchical-projects" class="">https://blueprints.launchpad.net/horizon/+spec/hierarchical-projects</a><o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><a href="https://blueprints.launchpad.net/horizon/+spec/inherited-roles" class="">https://blueprints.launchpad.net/horizon/+spec/inherited-roles</a><o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><p class="MsoNormal">As for adoption, it’s hard to say. The HMT work in Keystone was a necessary starting point, but in order to create a complete solution we really need the corresponding changes in Nova (quotas), Glance (resource visibility), Horizon (UI
 scoping), and probably Ceilometer (aggregated queries). We (Cisco) are planning to kick off a Stackforge project to knit all of these things together into a complete “reseller” federation system. I’m assuming that there will be other system-level compositions
 of the various pieces.<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class=""><p class="MsoNormal">Geoff<o:p class=""></o:p></p>
</div>
<div class=""><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class="">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" class="">
<div class=""><p class="MsoNormal">On Apr 27, 2015, at 9:48 PM, Tripp, Travis S <<a href="mailto:travis.tripp@hp.com" class="">travis.tripp@hp.com</a>> wrote:<o:p class=""></o:p></p>
</div><p class="MsoNormal"><o:p class=""> </o:p></p>
<div class=""><p class="MsoNormal">Geoff,<br class="">
<br class="">
Getting a spec on HMT would be helpful, as Nikhil mentioned.<br class="">
<br class="">
As a general question, what it the current adoption of domains / vs<br class="">
hierarchical projects? Is there a wiki or something that highlights what<br class="">
the desired path forward is with regard to domains?<br class="">
<br class="">
Thanks,<br class="">
Travis<br class="">
<br class="">
On 4/27/15, 7:16 PM, "Geoff Arnold" <<a href="mailto:geoff@geoffarnold.com" class="">geoff@geoffarnold.com</a>> wrote:<br class="">
<br class="">
<br class="">
<o:p class=""></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" class=""><p class="MsoNormal">Good points. Iıll add some details. Iım sure the Reseller guys will have<br class="">
some comments.<br class="">
<br class="">
Geoff<br class="">
<br class="">
<br class="">
<o:p class=""></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" class=""><p class="MsoNormal">On Apr 27, 2015, at 3:32 PM, Nikhil Komawar<br class="">
<<a href="mailto:nikhil.komawar@RACKSPACE.COM" class="">nikhil.komawar@RACKSPACE.COM</a>> wrote:<br class="">
<br class="">
Thanks Geoff. Added some notes and questions.<br class="">
<br class="">
-Nikhil<br class="">
<br class="">
________________________________________<br class="">
From: Geoff Arnold <<a href="mailto:geoff@geoffarnold.com" class="">geoff@geoffarnold.com</a>><br class="">
Sent: Monday, April 27, 2015 5:50 PM<br class="">
To: OpenStack Development Mailing List (not for usage questions)<br class="">
Subject: [openstack-dev] [Keystone][Glance] Hierarchical multitenancy<br class="">
and       Glance?<br class="">
<br class="">
In preparation for Vancouver, Iıve been looking for blueprints and<br class="">
design summit discussions involving the application of the Keystone<br class="">
hierarchical multitenancy work to other OpenStack projects. One obvious<br class="">
candidate is Glance, where, for example, we might want domain-local<br class="">
resource visibility as a default. Despite my searches, I wasnıt able to<br class="">
find anything. Did I miss something obvious?<br class="">
<br class="">
Iıve added a paragraph to<br class="">
<a href="https://etherpad.openstack.org/p/liberty-glance-summit-topics" class="">https://etherpad.openstack.org/p/liberty-glance-summit-topics</a> to make<br class="">
sure it doesnıt get overlooked.<br class="">
<br class="">
Cheers,<br class="">
<br class="">
Geoff<br class="">
<br class="">
_________________________________________________________________________<br class="">
_<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <br class="">
<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
<br class="">
_________________________________________________________________________<br class="">
_<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <br class="">
<a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p class=""></o:p></p>
</blockquote><p class="MsoNormal"><br class="">
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p class=""></o:p></p>
</blockquote><p class="MsoNormal"><br class="">
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p class=""></o:p></p>
</div>
</blockquote>
</div><p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
</div>
</div>

__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></div></body></html>