Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/ProphetStor CI"

 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=ProphetStor CI
 
{{ThirdPartySystemInfo|name=ProphetStor CI
|account=prophetstor-ci
+
|account=prophetstor.ci
 
|contact=Rick Chen(rick on IRC) / Email rick.chen@prophetstor.com
 
|contact=Rick Chen(rick on IRC) / Email rick.chen@prophetstor.com
 
|intent=Test cinder changes with tempest using the ProphetStor volume driver plugin
 
|intent=Test cinder changes with tempest using the ProphetStor volume driver plugin
Line 6: Line 6:
 
|method=Each test run uses a fresh VM. devstack and OpenFlow controller run on a single node. 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. devstack and OpenFlow controller run on a single node. After tempest tests are completed, logs are copied to the log server and the used VM is destroyed.
 
|programs=Cinder
 
|programs=Cinder
|status=production, testing}}
+
|status=enabled }}
 +
'''Recheck trigger:''' "run ProphetStor CI"

Latest revision as of 02:59, 26 July 2016

3rd party system: ProphetStor CI
Gerrit Account: prophetstor.ci
Contact Information: Rick Chen(rick on IRC) / Email rick.chen@prophetstor.com
Intent: Test cinder changes with tempest using the ProphetStor volume driver plugin
Structure: zuul, tempest, devstack, customized version of devstack-gate
Method: Each test run uses a fresh VM. devstack and OpenFlow controller run on a single node. After tempest tests are completed, logs are copied to the log server and the used VM is destroyed.
OpenStack Programs: Cinder
Current Status: enabled


Recheck trigger: "run ProphetStor CI"