Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/NEC V Cinder CI"

(Created page with "{{ThirdPartySystemInfo|name=NEC V Cinder CI |account=nec-v-cinder-ci |contact=Naoki Saito(n-saito on IRC) / Email nec-v-cinder-ci@istorage.jp.nec.com |intent=Test cinder chan...")
 
 
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=NEC V Cinder CI
 
{{ThirdPartySystemInfo|name=NEC V Cinder CI
|account=nec-v-cinder-ci  
+
|account=nec--v-cinder-ci  
 
|contact=Naoki Saito(n-saito on IRC) / Email nec-v-cinder-ci@istorage.jp.nec.com
 
|contact=Naoki Saito(n-saito on IRC) / Email nec-v-cinder-ci@istorage.jp.nec.com
 
|intent=Test cinder changes with tempest using the NEC Storage V series
 
|intent=Test cinder changes with tempest using the NEC Storage V series

Latest revision as of 09:49, 8 February 2024

3rd party system: NEC V Cinder CI
Gerrit Account: nec--v-cinder-ci
Contact Information: Naoki Saito(n-saito on IRC) / Email nec-v-cinder-ci@istorage.jp.nec.com
Intent: Test cinder changes with tempest using the NEC Storage V series
Structure: tempest, devstack and NEC Storage V100 (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