On 03/03/2016 11:43 PM, Dolph Mathews wrote:
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.
MOC use case I think depends on this. I'll see
Hi,
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.
BTW, nova-neutron cross-region interactions are still legitimate use case:
you may utilize one neutron for many nova regions.
Hi,
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.
BTW, nova-neutron cross-region interactions are still legitimate use case: you
may utilize one neutron for many nova regions.
--
t;OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 04/03/2016 12:46 pm
Subject: Re: [openstack-dev] [keystone][nova] Many same "region_name"
configuration really meaingful for Multi-reg
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.
However, both of these configuration blocks should ultimately be used to
configure keystoneauth,
Hi All,
Right now, we found that nova.conf have many places for region_name
configuration. Check below:
nova.conf
***
[cinder]
os_region_name = ***
[neutron]
region_name= ***
***
From some mult-region environments observation, those two regions would
always config same value.
