If you run the multi-region offline(manually) with devstack, it works according to the guide http://docs.openstack.org/developer/devstack/configuration.html#multi-region-setup. That's the script from line 551~567 https://review.openstack.org/#/c/412777/2/devstack-vm-gate.sh
Unfortunately there is no way to setup multi-region job in gate/check job until now, no script to enable this, that's why I submitted a patch to try to address the need. I saw your comments "Honestly I don't like how this adds yet another flag to check, and complicates d-g. The idea of roles was to start to *eliminate* all these flags flying around in DevStack and make it more readable. This goes in the other direction." 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 another node, only one role to support multi-region setup seems to be not possible. The flag "MULTI_REGION" is to make the subnode play with the role where no keystone will run. If we don't use the flag, or maybe use DEVSTACK_GATE_MULTI_REGION? This is the first patch in devstack-gate for me, any help or guide will be appreciated. Best Regards Chaoyi Huang (joehuang) ________________________________________ From: Sean M. Collins [[email protected]] Sent: 04 January 2017 0:58 To: OpenStack 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 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. We have some docs for running multiple regions - http://docs.openstack.org/developer/devstack/configuration.html#multi-region-setup I don't know how stale they are, but work was done. So, really I would like to see some work/research done into that configuration strategy before we start throwing things into devstack-gate My $0.02 -- Sean M. Collins __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
