I agree. I think the solution proposed earlier in this thread about making default to service catalog and optionally allow ops to choose 'the list of glance-apis to send data to', would make everyone's life easier.
On Mon, May 1, 2017 at 2:16 PM, Blair Bethwaite <blair.bethwa...@gmail.com> wrote: > On 28 April 2017 at 21:17, Sean Dague <s...@dague.net> wrote: > > On 04/28/2017 12:50 AM, Blair Bethwaite wrote: > >> We at Nectar are in the same boat as Mike. Our use-case is a little > >> bit more about geo-distributed operations though - our Cells are in > >> different States around the country, so the local glance-apis are > >> particularly important for caching popular images close to the > >> nova-computes. We consider these glance-apis as part of the underlying > >> cloud infra rather than user-facing, so I think we'd prefer not to see > >> them in the service-catalog returned to users either... is there going > >> to be a (standard) way to hide them? > > > > In a situation like this, where Cells are geographically bounded, is > > there also a Region for that Cell/Glance? > > Hi Sean. Nope, just the one global region and set of user-facing APIs. > Those other glance-apis are internal architectural details and should > be hidden from the public catalog so as not to confuse users and/or > over-expose information. > > Cheers, > > -- > Cheers, > ~Blairo > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
