e is only one role environment variable, then the primary node should
always set HOST_IP to $primary_node but not the default 127.0.0.1, because the
keystone will not work well in multi-region scenario if HOST_IP is 127.0.0.1.
Best Regards
Chaoyi Huang (joehuang)
_________________
joehuang wrote:
> In multi-region environment(for example, two regions RegionOne and
> RegionTwo), KeyStone will be shared in RegionOne and RegionTwo, so the
> primary node and subnode should use different role, one role to enable the
> keystone, while another role is to use the keystone in
penStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [infra][devstack-gate][all]support multi-region
gate environment
Jay Pipes wrote:
> I think it's a good idea to have multi-region testing in the gate, yes. How
> does the existing federated Keyston
] [infra][devstack-gate][all]support multi-region
gate environment
On 01/02/2017 09:06 PM, joehuang wrote:
> Hello,
>
> Currently only one region is supported in devstack-gate, there are lots
> of projects providing multi-region involved features, for example, heat
> multi-region, t
Jay Pipes wrote:
> I think it's a good idea to have multi-region testing in the gate, yes. How
> does the existing federated Keystone functionality get tested in the gate?
> Perhaps that might be an approach to copy? Just throwing out an idea here;
> I'm actually not familiar with this part of the
I don't like how it's adding more conditionals and complexity to an
already fairly complex shell script. I've commented as such on the
review.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage
On 01/02/2017 09:06 PM, joehuang wrote:
Hello,
Currently only one region is supported in devstack-gate, there are lots
of projects providing multi-region involved features, for example, heat
multi-region, tacker multi-vim, shadow multi-cloud, tricircle networking
across multi-region, kingbird
Hello,
Currently only one region is supported in devstack-gate, there are lots of
projects providing multi-region involved features, for example, heat
multi-region, tacker multi-vim, shadow multi-cloud, tricircle networking across
multi-region, kingbird resource sync and so on.
Thanks to the
