<div dir="ltr">+1</div><div class="gmail_extra"><br clear="all"><div><div><br></div>-Dolph</div>
<br><br><div class="gmail_quote">On Fri, Jan 18, 2013 at 10:14 AM, George Reese <span dir="ltr"><<a href="mailto:george.reese@imaginary.com" target="_blank">george.reese@imaginary.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">+1<div><div><div class="h5"><br><div><div>On Jan 18, 2013, at 10:10 AM, Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>> wrote:</div><br><blockquote type="cite">
A couple folks have recently brought up why there isn't any ability in<br>Nova to list the availability zones and show the AZ and region for an<br>instance.<br><br>Phil Day shared the related blueprint [1] which led me to investigate<br>
one of the patches proposed for the blueprint for listing availability<br>zones:<br><br><a href="https://review.openstack.org/#/c/19824/" target="_blank">https://review.openstack.org/#/c/19824/</a><br><br>I'd like to bring up a point that I think is important to address before<br>
such a patch is accepted.<br><br>Why is the listing of availability zones or regions an operation in Nova<br>at all? This information more naturally belongs in Keystone.<br><br>Many installations of Nova (including ours) do not use one giant Nova<br>
database that stores data for instances in multiple availability zones.<br>To scale more effectively, we have a single Nova database for one<br>availability zone in a region.<br><br>On the other hand, we have a singular Keystone database cluster that<br>
stores catalog information for more than one availability zone and more<br>than one region. We do this to enable a unified authentication model<br>across regions and AZs.<br><br>IMHO, it makes more sense to put operations for listing AZs and regions<br>
into Keystone since:<br><br>a) Keystone already has natural interfaces for returning service<br>catalogs. Listing availability zones (and further, regions) is a natural<br>extension of the service catalog.<br><br>b) Availability zones and regions apply to more than just Nova. At a<br>
minimum, volumes in Cinder are assigned in an availability zone.<br>Keystone advertises more endpoints than just Nova, so again it seems<br>more natural to have Keystone advertise the availability zones and<br>regions a tenant has access to.<br>
<br>Thoughts?<br>-jay<br><br>[1] <a href="https://blueprints.launchpad.net/nova/+spec/show-availability-zone" target="_blank">https://blueprints.launchpad.net/nova/+spec/show-availability-zone</a><br><br>_______________________________________________<br>
OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div><div>
<span style="border-spacing:0px;text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<span style="border-spacing:0px;text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<div>--</div><div>George Reese (<a href="mailto:george.reese@imaginary.com" target="_blank">george.reese@imaginary.com</a>)<br>t: @GeorgeReese m: <a href="tel:%2B1%28207%29956-0217" value="+12079560217" target="_blank">+1(207)956-0217</a> Skype: nspollution<br>
<br></div><div><br></div></div></span><br></div></span><br><br>
</div>
<br></div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>