Reviewed: https://review.openstack.org/620738 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d0ba488c1df86905082a13cc8598548244db0fd7 Submitter: Zuul Branch: master
commit d0ba488c1df86905082a13cc8598548244db0fd7 Author: Matt Riedemann <[email protected]> Date: Wed Nov 28 18:14:16 2018 -0500 Make [cinder]/catalog_info no longer require a service_name The service_name part of the cinder catalog_info option is not necessary to lookup the endpoint from the service catalog when we have the endpoint type (volumev3) and the interface (publicURL). This changes the option default to not include the service name and no longer makes a service name required. If one is provided, then it will be sent along to KSA/cinderclient, otherwise it is omitted. As this is a change in behavior of the config option, a release note is added. Change-Id: I89395fafffd60981fba17a7b09f7015e1f827b62 Closes-Bug: #1803627 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1803627 Title: Nova requires you to name your volumev3 service cinderv3 Status in OpenStack Compute (nova): Fix Released Bug description: Nova by default looks for the cinder endpoint by looking for a service type of volumev3 and that also has a name of "cinderv3" I think it should only be looking for an endpoint with a type of volumev3 The name attribute of an endpoint should be free to set by the operator. In our keystone we name this "Volume API V3" which is friendly as it also appears in horizon and using the CLI tools. (cinderv3 on the other hand is not so friendly) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1803627/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
