Hi, Great to hear. One thing that is important to address is the different plugins. I guess that this may complicate things a little. I think that the addition of Melange may also extend the scope. As of yet I am not familiar with this. Thanks Gary
On 05/24/2012 09:59 AM, Hua BJ Zhang wrote: > > Hi all, > > I want to start a blueprint to implement the "System/Integration > testing" listed in http://wiki.openstack.org/QuantumStarterBugs. this > blueprint said " > We need system/integration testing that exercises much more > functionality than the basic excercise.sh script. We'd also like to > explore integration with Tempest and working with the openstack CI > team to make sure that both unit tests and system/integration testing > is a gate to Quantum commits in Folsom. (interested parties: debo, > davelaps) " > > So my idea is to make a initial commit into tempest project first, > after I have finished it, I will continue to consider adding more > quantum system test cases into tempest. this initial commit will > include following 3 aspects: > 1) only add 3 basic system test cases ( create tenants, create vms, > create networks ) into tempest just by referring > $devstack/exercises/quantum.sh > 2) finish the common service module code for quantum in > $tempest/tempest/services/quantum/json > 3) update $devstack/tools/devstack's build_bm_mulit.sh script to > leverage the openstack jenkin's infrastructure to set up quantum > testing env. > > from the doc ( http://ci.openstack.org/), we can learnthe openstack CI > testing process, my understand is: > Jenkins and Gerrit has been integrated by a blueprint project ( > gate-tempest-devstack-vm, > https://jenkins.openstack.org/view/Tempest/job/gate-tempest-devstack-vm/configure), > so following CI process ( openstack-ci ) will start when we commit the > code to Gerrit for reviewing. > 1, use orachestra & cobbler to install operation system for bare-metal > machines, and also use LVM/kexec to accelerate the rebooting time. > 2, then use puppet (openstack-ci-puppet) to install and configure > other dependent software. > 3, use $devstack/tools/devstack's build_bm_mulit.sh script to install > openstack on CI testing cluster. ( can refer > http://ci.openstack.org/jenkins.html#run-test-suite ) > 4, finally run tempest testing suite. > so I think in order to let CI can run quantum tempest testing, I also > need to update $devstack/tools/devstack's build_bm_mulit.sh script to > build an openstack with quantum install on several bare metal machines. > > can someone double check my understanding how it works above and > provide any additional input ? in addition, If it is ok, should I add > one new blueprint or just do it under blueprint > https://blueprints.launchpad.net/quantum/+spec/quantum-system-test ? > looking forward to your reply, many thanks. > > > > Best Regards. > > Zhang Hua(张华) > ---------------------------------------------------- > IBM China System and Technology Lab(CSTL), Beijing > E-Mail: zhhu...@cn.ibm.com > Tel: 86-10-82452020 > Address: Building 28(Ring Building), ZhongGuanCun Software Park, > No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193 >
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp