Driver for networking-sfc has been added to Tricircle, need to
add networking-sfc to PROJECTS variable to allow DevStack to
clone networking-sfc so Tricircle's dsvm test can proceed.
Change-Id: I7c18aee7074b83ff3ab5aaf3509647893e395ec7
Convert some more job templates to use local_conf.
This handles files [s-z]* and converts all templates where a conversion
was directly possible.
Change-Id: Idf3143ea38709d69e8de01667bc129fe9cacdbca
The multi-region job for Tricircle needs to update some
environment variables which will be used in the devstack based
test environment setup, it's impossible to set these variables
in pre_test_hook.sh without sourcing it, which leads to the job
failure. gate_hook is a better hook point to do this, many other
projects like Octvia, Magnum etc already used this hook point to
configure environment variables. It's better to use gate_hook
but not pre_test_hook in Tricircle multiregion job
Change-Id: I6763d7141895dfc3e94baed92b2c052a698049d1
Signed-off-by: joehuang <joehuang@huawei.com>
Tricircle is to provide networking automation across Neutron in
multi-region OpenStack deployments. Currently the function test
job in Tricircle can only work in single region, and most of
the multi-region test cases are not able to be executed.
It's time to add one non-voting multi-region gate/check test
job in Tricircle. The multi-region devstack-gate environment
will be configured in the pre_test_hook.sh in
another patch to Tricircle project
(https://review.openstack.org/#/c/438382/)
The Tricircle devstack plugin has already been updated to
support such a multi-region job.
Change-Id: Ie7c7a1475c104c78453e785f8729bc1025f530fc
Signed-off-by: joehuang <joehuang@huawei.com>
We have now some rather long job-template names, shorten them with
replacing job-suffix with suffix.
Before this change we had 1500 usages of job-suffix and 700 of just
suffix. This change therefore unifies to one setting.
Note that this does not change any job names at all, they are unchanged,
it changes and shortens only the names of job-templates.
Change-Id: I514df039a848d9f6619bca3adc05dfb84a761fc9
Tricircle was accepted as one of OpenStack big-tent projects:
https://review.openstack.org/#/c/338796/.
Add jobs for function test on ubuntu-xenial(non-voting), and
documentation publish to docs.openstack.org. Function test on
ubuntu-xenial job is non-voting job at first.
Change-Id: I10edb1a2d2a3d3d7f143f82076a673de8bc685d0
Signed-off-by: joehuang <joehuang@huawei.com>
The Tricircle provides an OpenStack API gateway and networking automation
to allow multiple OpenStack instances, spanning in one site or multiple
sites or in hybrid cloud, to be managed as a single OpenStack cloud.
As the OpenStack API gateway, the Tricircle should be able to accept
OpenStack API and forward it to regarding bottom OpenStack.
The Tricircle will be installed together with Nova/Cinder/Neutron in
the DevStack, and reuse the tempest use cases to test the Tricircle and
bottom OpenStack which are managed by the Tricircle.
This patch is to add the functional test job in the project-config.
The hook scripts which will be used in the functional test job are
merged in the patch: https://review.openstack.org/#/c/329300/
Change-Id: Ic485432739f9e61242623c0f7b457a80023fe627
Signed-off-by: Chaoyi Huang <joehuang@huawei.com>