Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Nexenta CI"

(Updating Info for build and including Manila)
m (Updated structure, contacts email addresses)
 
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Nexenta CI
 
{{ThirdPartySystemInfo|name=Nexenta CI
 
|account=nexentaci
 
|account=nexentaci
|contact=alexey.khodos@nexenta.com, ilya@nexenta.com, alex.deiter@gmail.com
+
|contact=akhodos@tintri.com, alex.deiter@gmail.com
 
|intent=Third party CI for NexentaStor  
 
|intent=Third party CI for NexentaStor  
|structure=uses sos-ci, ansible and a mix of VMware VMs and bare-metal
+
|structure=Uses 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
 
|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, Manila
 
|programs=Cinder, Manila
 
|status=reporting to gerrit}}
 
|status=reporting to gerrit}}
 
'''Recheck trigger:''' "run-nexentaci"
 
'''Recheck trigger:''' "run-nexentaci"

Latest revision as of 19:58, 28 November 2022

3rd party system: Nexenta CI
Gerrit Account: nexentaci
Contact Information: akhodos@tintri.com, alex.deiter@gmail.com
Intent: Third party CI for NexentaStor
Structure: Uses 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"