Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/NEC Cinder CI"

 
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=NEC Cinder CI
 
{{ThirdPartySystemInfo|name=NEC Cinder CI
 
|account=nec-cinder-ci  
 
|account=nec-cinder-ci  
|contact=Shingo Takeda (stakeda on IRC) / Email nec-cinder-ci@istorage.jp.nec.com
+
|contact=Naoki Saito(n-saito on IRC) / Email nec-cinder-ci@istorage.jp.nec.com
 
|intent=Test cinder changes with tempest using the NEC Storage M series
 
|intent=Test cinder changes with tempest using the NEC Storage M series
|structure=zuul, jenkins, tempest, devstack and NEC Storage M110 (FC/iSCSI combo)
+
|structure=tempest, devstack and NEC Storage M110 (FC/iSCSI combo)
 
|method=Each test run uses a fresh VM. The VM accesses an FC HBA via PCIe passthrough. After tempest tests are completed, logs are copied to the log server and the used VM is destroyed.
 
|method=Each test run uses a fresh VM. The VM accesses an FC HBA via PCIe passthrough. After tempest tests are completed, logs are copied to the log server and the used VM is destroyed.
 
|programs=Cinder
 
|programs=Cinder
 
|status=enabled, non-voting}}
 
|status=enabled, non-voting}}

Latest revision as of 00:03, 5 February 2020

3rd party system: NEC Cinder CI
Gerrit Account: nec-cinder-ci
Contact Information: Naoki Saito(n-saito on IRC) / Email nec-cinder-ci@istorage.jp.nec.com
Intent: Test cinder changes with tempest using the NEC Storage M series
Structure: tempest, devstack and NEC Storage M110 (FC/iSCSI combo)
Method: Each test run uses a fresh VM. The VM accesses an FC HBA via PCIe passthrough. After tempest tests are completed, logs are copied to the log server and the used VM is destroyed.
OpenStack Programs: Cinder
Current Status: enabled, non-voting