<div dir="ltr">Manila uses "project_id"s in URLs as Cinder does. So, the same amount of work for each of projects is required.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 4, 2015 at 3:29 AM, Jim Rollenhagen <span dir="ltr"><<a href="mailto:jim@jimrollenhagen.com" target="_blank">jim@jimrollenhagen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
> On Dec 3, 2015, at 12:06, Sean Dague <<a href="mailto:sean@dague.net">sean@dague.net</a>> wrote:<br>
><br>
> For folks that don't know, we've got an effort under way to look at some<br>
> of what's happened with the service catalogue, how it's organically grown,<br>
> and do some pruning and tuning to make sure it's going to support what<br>
> we want to do with OpenStack for the next 5 years (wiki page to dive<br>
> deeper here - <a href="https://wiki.openstack.org/wiki/ServiceCatalogTNG" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/ServiceCatalogTNG</a>).<br>
><br>
> One of the items which came up is removing project_id from API urls.<br>
> Today there is a very odd linkage between keystone service catalog<br>
> entries and project_ids. For instance in Nova every single project has a<br>
> different API endpoint.<br>
><br>
> <a href="https://nova.api.server/v2.1/$project_id" rel="noreferrer" target="_blank">https://nova.api.server/v2.1/$project_id</a><br>
><br>
> That has implications for caching, and exposing this anonymously, and<br>
> having to carry around the whole service catalog in your oslo.context<br>
> (which means putting it over the RPC bus a lot).<br>
><br>
> For Nova, this was almost entirely ignored. It turned out to be a pretty<br>
> simple functional change to have a set of routes which don't need them -<br>
> <a href="https://review.openstack.org/#/c/233076/6" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/233076/6</a> (it's more involved to have<br>
> comprehensive testing, but we'll ignore that for now).<br>
><br>
> Projects that spawned from Nova: Cinder, Glance, Ironic, Manila, Magnum,<br>
> I'm hoping this is just as much of a surface integration that optionally<br>
> dropping it shouldn't be a big deal. However, for any projects that have<br>
> it, if folks could speak up, that would be great. It would also be good<br>
> to know which projects are up for making this kind of change this cycle,<br>
> as certain future work is inhibited until we get this in. We'll be<br>
> landing this in Nova this cycle.<br>
><br>
> Swift is a different story, the project_id is a core concept in the<br>
> resources. That's fine, but when we expose a new resource for the<br>
> service catalog tng, we won't be doing the magic substitution on the<br>
> server side. New clients, consuming the new interface, will need to<br>
> construct the urls themselves.<br>
><br>
> So, for Cinder, Glance, Ironic, Manila, Magnum (and others I might have<br>
> missed) where are you standing on this one? And are there volunteers in<br>
> those projects to help move this forward?<br>
<br>
</div></div>Ironic today has no concept of tenant/project/etc so should be nothing to do here. :)<br>
<span class="HOEnZb"><font color="#888888"><br>
// jim<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> -Sean<br>
><br>
> --<br>
> Sean Dague<br>
> <a href="http://dague.net" rel="noreferrer" target="_blank">http://dague.net</a><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Kind Regards<br>Valeriy Ponomaryov<br><a href="http://www.mirantis.com" target="_blank">www.mirantis.com</a><br><a href="mailto:vponomaryov@mirantis.com" target="_blank">vponomaryov@mirantis.com</a><br></div></div>
</div>