Open Stack

Hi,

Referring to bug https://bugs.launchpad.net/nova/+bug/1087735, I'd like to get some thoughts on how the current implementation can be improved
for filtering endpoints by region.

For example, during Cinder volume attachment as described in the bug, if we specify 'attr' and 'filter_value' correctly for a specific region,
(Eg: attr='region', filter_value='RegionTwo') in the call to service_catalog.url_for()  , cinder correctly parses this value and returns a matching endpoint for this region.
https://github.com/openstack/nova/blob/master/nova/volume/cinder.py#L63

However, it is unclear how these parameters should be passed from nova volume API.
As a possible solution, should the context object also contain a "region_name" parameter added to it, and then extract this parameter into the cinderclient?
Does it make sense to add another flag/configuration parameter to nova.conf for accepting region?
How can we ensure that a region name is consistently utilized and validated across APIs as well as python clients?


Best Regards,
Rohit Karajgi | Lead Engineer | NTT Data Global Technology Services Private Ltd | w. +91.20.6604.1500 x 378 |  m. +91 992.242.9639 | rohit.karajgi at nttdata.com<mailto:rohit.karajgi at nttdata.com>


______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data.  If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121211/2c944b00/attachment.html>