master
stable/ussuri
stable/train
stable/rocky
stable/stein
experiment
queens-eol
pike-eol
ussuri-em
ocata-eol
train-em
stein-em
8.0.0
8.0.0.0rc1
rocky-em
queens-em
7.0.0
7.0.0.0rc1
pike-em
ocata-em
6.0.0
5.1.0
5.0.0
4.3.0
4.2.0
4.1.0
fortest-eol
newton-eol
icehouse-eol
4.0.0
3.4.0
mitaka-eol
3.3.0
3.2.0
3.1.0
3.0.0
2.1.0
2.0.2
2.0.1
v2.0.1
v2.0.0
stateful
poc-kilo
poc
v1.2.1
v1.2
v1.1
${ noResults }
4 Commits (bfe02339b34cfe83a4efcad436edadfe71656d55)
| Author | SHA1 | Message | Date |
|---|---|---|---|
zhiyuan_cai
|
bfe02339b3 |
Fix DevStack script error
1. What is the problem When running DevStack script of the Tricircle, during the setup of Nova_apigw, script tries to add some configuration options to the Neutron configuration file. However this file doesn't exist at that time, thus script fails. 2. What is the solution to the problem Stop modifying the Neutron configuration file during the setup of Nova_apigw. Instead, we modify that file during the setup of Neutron server. 3. What the features need to be implemented to the Tricircle to realize the solution No new features. Some lines of scripts are removed. Change-Id: I94ada1e5a49f14942fa4c00690cffe2a87428e75 |
7 years ago |
|
Chaoyi Huang
|
9cf49bbf65 |
Add tempest test cases which are needed for integration test in Tricircle
1.What is the purpose of this patch set? The Tricircle project doesn't provide integration test yet. As the OpenStack API gateway, the Tricircle should pass the test for all OpenStack tempest test cases. When a feature parity is implemented in the Tricircle, proper test cases should be selected and executed in the Jenkins integration job. To simplify the test cases selection, all tempest test cases of Nova/Cinder/Neutron/Scenario are listed in the files of this patch, and give example in tempest_volume.sh on how to run selected test cases. The hook scripts for the Jenkins job has been provided in: https://review.openstack.org/#/c/329300/ This patch is to update the hook scripts. 2. What is the benefit of this patch set for the Tricircle project? Reuse OpenStack Nova/Cinder/Neutron tempest test cases, and provide integration gate test for new patches. 3.What is the platform you tested it out? After the Jenkins job patch is merged, the test will be executed in the OpenStack CI pipeline, and as one of the gate test for a new patch. CI pipeline will be triggered by gerrit review process, and the test will be executed in the devstack VM(booted by CI pipeline). http://docs.openstack.org/infra/system-config/jenkins.html And the Jenkin job patch is being review in OpenStack infra project-config: https://review.openstack.org/#/c/329740/ Change-Id: Ic5ec358889265e1d54071cd0d20e2aaa081736d1 Signed-off-by: Chaoyi Huang <joehuang@huawei.com> |
7 years ago |
|
Chaoyi Huang
|
da6c08f93e |
Add hook scripts for the Jenkins job for Tricircle tempest
1.What is the purpose of this patch set? The Tricircle project doesn't provide integration test yet. To achieve integration test, the Tricircle needs to provide hook scripts for the Jenkins job to execute the test. The Tricircle integration test Jenkins job will be configured in https://github.com/openstack-infra/project-config/tree/master/jenkins/jobs A Jenkins job patch will be submited to project-config once this patch is merged. Without the hook scripts provided in this patch, the Jenkins job configured in project-config is not able to be executed successfully. After the autotimc Jenkins job is established, all new patches sumitted to the Tricircle should pass the integration test, i.e. the test is also the gate test for a new patch. For example, for cinder volume type patch, currently no integration test is provided, we don't know the patch work or not. As new features added to the Tricircle, integration test cases from the Tempest for OpenStack Nova/Cinder/Neutron could be added to the post_test_hook.sh, to test the features added to the Tricircle is correct or not. 2.What is the benefit of this patch set for the Tricircle project? Reuse OpenStack Nova/Cinder/Neutron tempest test cases, and provide integration gate test for new patches. 3.What is the platform you tested it out? After the Jenkins job patch is merged, the test will be executed in the OpenStack CI pipeline, and as one of the gate test for a new patch. CI pipeline will be triggered by gerrit review process, and the test will be executed in the devstack VM(booted by CI pipeline). http://docs.openstack.org/infra/system-config/jenkins.html Change-Id: I5333681fdcaefb01498d9d8c6751d5d174bf57c2 Signed-off-by: Chaoyi Huang <joehuang@huawei.com> |
7 years ago |
|
Chaoyi Huang
|
c8f3a65549 |
Add the Tricircle tempest plugin with a sample test case
1.What is the purpose of this patch set? The Tricircle project doesn't provide integration test yet. To achieve integration test, the Tricircle needs to provide Tempest plugin, so that the integration test job could be configured in CI pipeline. Tempest is a set of integration tests to be run against a live OpenStack cluster: http://docs.openstack.org/developer/tempest/overview.html Tempest has an external test plugin interface which enables project to integrate an external test suite as part of a tempest run. http://docs.openstack.org/developer/tempest/plugin.html This patch set is to create the Tricircle tempest plugin with a sample test case. And main purpose of the patch set is to make tempest enable to discover the Tricircle tempest plugin and its test case. 2.What is the benefit of this patch set for the Tricircle project? Make the Tricircle tempest plugin being able to be discovered by Tempest, and support later integration test job. 3.What is the platform you tested it out? It will work on all linux distribution including python venv, docker container are available. The procedure to make discovering processes are as follows: Install the Tricircle after the patch merged (the Tricircle tempest plugin and the sample tempest test case will be installed together for they are in the same repository): 1. git clone https://github.com/openstack/tricircle.git 2. sudo pip install -e tricircle/ Install the Tempest in another folder in order to avoid the python import error: 1. git clone https://github.com/openstack/tempest.git 2. sudo pip install -e tempest/ Then run testr in tempest folder to see if the test case of the Tricircle has been discovered: 1. cd tempest/ 2. testr list-tests | grep Tricircle The Tricircle devstack plugin is also updated with the Tricircle package installation in order to simplify the tempest discovering processes. Change-Id: I977c23f5e55e3ee062190fa9d5e6472e5d5acb33 Signed-off-by: Chaoyi Huang <joehuang@huawei.com> |
7 years ago |