Y'all-

        TL;DR: Does glance ever really need/use multiple endpoint URLs?

        I'm working on bp use-service-catalog-for-endpoints[1], which intends
to deprecate disparate conf options in various groups, and centralize
acquisition of service endpoint URLs.  The idea is to introduce
nova.utils.get_service_url(group) -- note singular 'url'.

        One affected conf option is [glance]api_servers[2], which currently
accepts a *list* of endpoint URLs.  The new API will only ever return *one*.

        Thus, as planned, this blueprint will have the side effect of
deprecating support for multiple glance endpoint URLs in Pike, and
removing said support in Queens.

        Some have asserted that there should only ever be one endpoint URL for
a given service_type/interface combo[3].  I'm fine with that - it
simplifies things quite a bit for the bp impl - but wanted to make sure
there were no loudly-dissenting opinions before we get too far down this
path.

[1]
https://blueprints.launchpad.net/nova/+spec/use-service-catalog-for-endpoints
[2]
https://github.com/openstack/nova/blob/7e7bdb198ed6412273e22dea72e37a6371fce8bd/nova/conf/glance.py#L27-L37
[3]
http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2017-04-27.log.html#t2017-04-27T20:38:29

Thanks,
Eric Fried (efried)
.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to