Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Nexenta CI"

(Updating Info for build and including Manila)
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Nexenta CI
 
{{ThirdPartySystemInfo|name=Nexenta CI
 
|account=nexentaci
 
|account=nexentaci
|contact=mikhail.khodos@nexenta.com, ilya@nexenta.com, nexentaedge@gmail.com
+
|contact=alexey.khodos@nexenta.com, ilya@nexenta.com, alex.deiter@gmail.com
 
|intent=Third party CI for NexentaStor  
 
|intent=Third party CI for NexentaStor  
|structure=uses sos-ci, (ansible) and my own OpenStack Private Cloud
+
|structure=uses sos-ci, ansible and a mix of VMware VMs and bare-metal
|method=Monitor gerrit stream, deploy instance, fire up devstack with current cinder patch, run dsvm-full using NexentaStor as backend device for Cinder
+
|method=Monitor gerrit stream, deploy instance, fire up devstack with current cinder or manila patch, run dsvm-full using NexentaStor as backend device for Cinder/Manila
|programs=Cinder
+
|programs=Cinder, Manila
 
|status=reporting to gerrit}}
 
|status=reporting to gerrit}}
'''Recheck trigger:''' "recheck-nexenta"
+
'''Recheck trigger:''' "run-nexentaci"

Revision as of 13:21, 13 June 2019

3rd party system: Nexenta CI
Gerrit Account: nexentaci
Contact Information: alexey.khodos@nexenta.com, ilya@nexenta.com, alex.deiter@gmail.com
Intent: Third party CI for NexentaStor
Structure: uses sos-ci, ansible and a mix of VMware VMs and bare-metal
Method: Monitor gerrit stream, deploy instance, fire up devstack with current cinder or manila patch, run dsvm-full using NexentaStor as backend device for Cinder/Manila
OpenStack Programs: Cinder, Manila
Current Status: reporting to gerrit


Recheck trigger: "run-nexentaci"