<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Glad to see this FFE. The Cisco Cloud Services team is very interested in the Reseller use case, and in a couple of possible extensions of the work. <a href="http://specs.openstack.org/openstack/keystone-specs/specs/kilo/reseller.html" class="">http://specs.openstack.org/openstack/keystone-specs/specs/kilo/reseller.html</a> covers the Keystone use cases, but there are several other developments required in other OpenStack projects to come up with a complete reseller “solution”. For my information, has anyone put together an overarching blueprint which captures the top level Reseller use cases and identifies all of the sub-projects and their dependencies? If so, wonderful. If not, we might try to work on this in the new Product Management WG.<div class=""><br class=""></div><div class="">I mentioned “extensions” to <a href="http://specs.openstack.org/openstack/keystone-specs/specs/kilo/reseller.html" class="">http://specs.openstack.org/openstack/keystone-specs/specs/kilo/reseller.html</a> . There are two that we’re thinking about:</div><div class="">- the multi-provider reseller: adding the user story where Martha buys OpenStack services from two or more </div><div class=""> providers and presents them to her customers through a single Horizon instance</div><div class="">- stacked reseller: Martha buys OpenStack services from a provider, Alex, and also from a reseller, Chris, who </div><div class=""> purchases OpenStack services from multiple providers </div><div class=""><br class=""></div><div class="">In each case, the unit of resale is a “virtual region”: a provider region subsetted using HMT/domains, with IdP supplied by the reseller, and constrained by resource consumption policies (e.g. Nova AZ “foo” is not available to customers of reseller “bar”).</div><div class=""><br class=""></div><div class="">I strongly doubt that any of this is particularly original, but I haven’t seen it written up anywhere.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">Geoff Arnold</div><div class="">Cisco Cloud Services</div><div class=""><a href="mailto:geoarnol@cisco.com" class="">geoarnol@cisco.com</a></div><div class=""><a href="mailto:geoff@geoffarnold.com" class="">geoff@geoffarnold.com</a></div><div class="">@geoffarnold</div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Mar 19, 2015, at 11:22 AM, Raildo Mascena <<a href="mailto:raildom@gmail.com" class="">raildom@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">In addition, <br class=""><br class="">In the last keystone meeting in March 17 in the <a href="http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2015-03-17.log" class="">IRC channel</a> we decided that Henry Nash (keystone core) will sponsor this feature as a FFE.<div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">Raildo</div></div><br class=""><div class="gmail_quote">On Tue, Mar 17, 2015 at 5:36 PM Raildo Mascena <<a href="mailto:raildom@gmail.com" class="">raildom@gmail.com</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hi Folks,<br class=""><br class="">We’ve discussed a lot in the last Summit about the Reseller use case. OpenStack needs to grow support for hierarchical ownership of objects.This enables the management of subsets of users and projects in a way that is much more comfortable for private clouds, besides giving to public cloud providers the option of reselling a piece of their cloud.<div class=""><br class="">More detailed information can be found in the spec for this change at: <a href="https://review.openstack.org/#/c/139824" target="_blank" class="">https://review.openstack.org/#/c/139824</a><br class=""><br class="">The current code change for this is split into 8 patches (to make it easier to review). We currently have 7 patches in code review and we are finishing the last one.<br class=""><br class="">Here is the workflow of our patches:<br class=""><br class="">1- Adding a field to enable the possibility to have a project with the domain "feature": <a href="https://review.openstack.org/#/c/157427/" target="_blank" class="">https://review.openstack.org/#/c/157427/</a><br class=""><br class="">2- Change some constraints and create some options to list projects (for is_domain flag, for parent_id):<br class=""><a href="https://review.openstack.org/#/c/159944/" target="_blank" class="">https://review.openstack.org/#/c/159944/</a><br class=""><a href="https://review.openstack.org/#/c/158398/" target="_blank" class="">https://review.openstack.org/#/c/158398/</a><br class=""><a href="https://review.openstack.org/#/c/161378/" target="_blank" class="">https://review.openstack.org/#/c/161378/</a><br class=""><a href="https://review.openstack.org/#/c/158372/" target="_blank" class="">https://review.openstack.org/#/c/158372/</a><br class=""><br class="">3- Reflect domain operations to project table, mapping domains to projects that have the is_domain attribute set to True. In addition, it changes the read operations to use only the project table. Then, we will drop the Domain Table.<br class=""><a href="https://review.openstack.org/#/c/143763/" target="_blank" class="">https://review.openstack.org/#/c/143763/</a><br class=""><a href="https://review.openstack.org/#/c/161854/" target="_blank" class="">https://review.openstack.org/#/c/161854/</a> (Only patch with work in progress)<br class=""><br class="">4- Finally, the inherited role will not be applied to a subdomain and its sub hierarchy. <a href="https://review.openstack.org/#/c/164180/" target="_blank" class="">https://review.openstack.org/#/c/164180/</a><br class=""><br class="">Since we have the implementation almost completed, waiting for code review, I am requesting an FFE to enable the implementation of this last patch and work to have this implementation merged in Kilo.</div></div><div dir="ltr" class=""><div class=""><br class=""><br class="">Raildo<br class=""></div></div></blockquote></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>