<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">From my previous 3K+ nodes 6+ regions OpenStack operations experience in Yandex, I found useless to have Cinder and Neutron services in cross-region manner.</div><div class=""><br class=""></div><div class="">BTW, nova-neutron cross-region interactions are still legitimate use case: you may utilize one neutron for many nova regions.</div><div class=""><br class=""><div class="">
<div class="">-- <br class="">With best regards,<br class="">Vladimir Eremin,<br class="">Fuel Deployment Engineer,<br class="">Mirantis, Inc.</div><br class=""><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Mar 4, 2016, at 7:43 AM, Dolph Mathews <<a href="mailto:dolph.mathews@gmail.com" class="">dolph.mathews@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Unless someone on the operations side wants to speak up and defend cross-region nova-cinder or nova-neutron interactions as being a legitimate use case, I'd be in favor of a single region identifier.<div class=""><br class=""></div><div class="">However, both of these configuration blocks should ultimately be used to configure keystoneauth, so I would be in favor of whatever solution simplifies configuration for keystoneauth.</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Mar 1, 2016 at 10:01 PM, Kai Qiang Wu <span dir="ltr" class=""><<a href="mailto:wkqwu@cn.ibm.com" target="_blank" class="">wkqwu@cn.ibm.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><p class="">Hi All,<br class=""><br class=""><br class="">Right now, we found that nova.conf have many places for region_name configuration. Check below:<br class=""><br class="">nova.conf<br class=""><br class="">*******<br class="">[cinder]<br class="">os_region_name = ***<br class=""><br class="">[neutron]<br class="">region_name= ***<br class=""><br class=""><br class=""><br class="">*******<br class=""><br class=""><br class="">From some mult-region environments observation, those two regions would always config same value. <br class=""><b class="">Question 1: Does nova support config different regions in nova.conf ? Like below</b><br class=""><br class="">[cinder]<br class=""><br class="">os_region_name = <font color="#0000FF" class="">RegionOne</font><br class=""><br class="">[neutron]<br class="">region_name=<font color="#0020C2" class=""> RegionTwo</font><br class=""><br class=""><br class="">From Keystone point, I suspect those regions can access from each other.<br class=""><br class=""><br class=""><b class="">Question 2: If all need to config with same value, why we not use single region_name in nova.conf ?</b> (instead of create many region_name in same file ) <br class=""><br class="">Is it just for code maintenance or else consideration ?<br class=""><br class=""><br class=""><br class="">Could nova and keystone community members help this question ? <br class=""><br class=""><br class="">Thanks<br class=""><br class=""><br class="">Best Wishes,<br class="">--------------------------------------------------------------------------------<br class="">Kai Qiang Wu (吴开强 Kennan）<br class="">IBM China System and Technology Lab, Beijing<br class=""><br class="">E-mail: <a href="mailto:wkqwu@cn.ibm.com" target="_blank" class="">wkqwu@cn.ibm.com</a><br class="">Tel: 86-10-82451647<br class="">Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br class=""> No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br class="">--------------------------------------------------------------------------------<br class="">Follow your heart. You are miracle! <br class="">
</p></div>
<br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>