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 resource sync and so on.
Thanks to the patch "Introduce roles into the feature matrix", it's
possible to assign the sub-node in devstack-gate with a new role
"subnode_multi_region", so that all services will start and share same
keystone in the primary node, this is the typical devstack multi-region
mode. One environment variable MULTI_REGION is introduced to enable the
sub-node running as the second region(currently the first step is to
setup two-node two-region environment).
One patch was prepared to enhance
devstack-gate: https://review.openstack.org/#/c/412777/
And Tricircle will begin to try the multi-region gate/check
job: https://review.openstack.org/#/c/414909/
The devstack plugin of Tricircle is also enhanced to support
multi-region job: https://review.openstack.org/#/c/414860/
How do you think about this idea? It's basic requirement to have
multi-region gate/check job for Tricricle, hope this could be on board
before Ocata release. once Tricircle can be tested through such a
multi-region job, other projects can also benefit from the same
infrastructure.
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 gate at all.
Best,
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev