Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/VMware CI"

 
(14 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{ThirdPartySystemInfo|name=VMWARE CI
+
{{ThirdPartySystemInfo|name=VMware NSX CI
 
|account=9008
 
|account=9008
|contact=Salvatore Orlando (irc: salv-orlando, email: sorlando at nicira dot com), Ryan Hsu (irc: rhsu, email: rhsu at vmware dot com)
+
|contact=Kobi Samoray (ksamoray dot vmware dot com), Hui Jiang (jhui dot vmware dot com)
|intent= Validate Neutron changes with NSX plugin backend, Validate Nova changes with vCenter driver
+
|intent= Validate Neutron changes with NSX plugin backend, Validate Nova changes with vCenter driver, Validate Cinder changes with vCenter VMDK driver
 
|structure=customized version of devstack-gate, devstack, tempest
 
|structure=customized version of devstack-gate, devstack, tempest
 
|method=Each test run uses a fresh devstack + VMware NSX + vCenter infrastructure. Infrastructure setup is performed with an ad hoc script and internal deployment tools. Neutron: smokeserial job, full job (non voting), largeops job. Nova: smokeserial job
 
|method=Each test run uses a fresh devstack + VMware NSX + vCenter infrastructure. Infrastructure setup is performed with an ad hoc script and internal deployment tools. Neutron: smokeserial job, full job (non voting), largeops job. Nova: smokeserial job
|programs=Neutron, Nova, stackforge/vmware-nsx (which is obviously not a program_
+
|programs=Neutron, Nova, stackforge/vmware-nsx (which is obviously not a program)
|status=voting. In the last few days we have done some work to restore the VMware NSX CI, which was disabled due to the advanced services spin-off.
+
|status=voting<br>
The CI has been disabled for about 3 weeks. Our team worked hard to bring back the NSX plugin to a fully functional state; nevertheless, we are still noticing some intermittent failures which cause NSX CI jobs to fail. Our team will keep working in the next days on ensuring these remaining issues are root caused and fixed.}}
+
On 2014-01-09 there has been a regression in the NSX plugin which now always fails tempest.test.scenario.test_network_basic_ops when the route is put administratively down.
 +
The issue will be fixed soon. In the meanwhile the CI is keeping voting to try and avoid introduction of further regressions. Please ignore VMware NSX CI failures in TestNetworkBasicOps<br>
 +
 
 +
To run the job on a patch, leave a comment with "vmware-recheck-patch".
 +
 
 +
Please see [https://wiki.openstack.org/wiki/NovaVMware/Minesweeper/Status here] for current status and a history of service disruptions.}}

Latest revision as of 14:22, 2 December 2020

3rd party system: VMware NSX CI
Gerrit Account: 9008
Contact Information: Kobi Samoray (ksamoray dot vmware dot com), Hui Jiang (jhui dot vmware dot com)
Intent: Validate Neutron changes with NSX plugin backend, Validate Nova changes with vCenter driver, Validate Cinder changes with vCenter VMDK driver
Structure: customized version of devstack-gate, devstack, tempest
Method: Each test run uses a fresh devstack + VMware NSX + vCenter infrastructure. Infrastructure setup is performed with an ad hoc script and internal deployment tools. Neutron: smokeserial job, full job (non voting), largeops job. Nova: smokeserial job
OpenStack Programs: Neutron, Nova, stackforge/vmware-nsx (which is obviously not a program)
Current Status: voting

On 2014-01-09 there has been a regression in the NSX plugin which now always fails tempest.test.scenario.test_network_basic_ops when the route is put administratively down. The issue will be fixed soon. In the meanwhile the CI is keeping voting to try and avoid introduction of further regressions. Please ignore VMware NSX CI failures in TestNetworkBasicOps

To run the job on a patch, leave a comment with "vmware-recheck-patch".

Please see here for current status and a history of service disruptions.