Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Fujitsu iRMC CI"

Line 8: Line 8:
 
|programs=Ironic
 
|programs=Ironic
 
|status=testing in ci-sandbox}}
 
|status=testing in ci-sandbox}}
'''Recheck trigger:''' "rerun Fujitsu iRMC CI"<br />
+
'''Recheck trigger:''' "Fujitsu iRMC CI-recheck" and "recheck"<br />
  
 
'''Maintenance plan:''' "6/20 00:00 - xx:xx(UTC)"<br />
 
'''Maintenance plan:''' "6/20 00:00 - xx:xx(UTC)"<br />

Revision as of 20:30, 13 July 2016

3rd party system: Fujitsu iRMC Driver
Gerrit Account: Fujitsu_iRMC_CI
Contact Information: fj-lsoft-irmcci@dl.jp.fujitsu.com
maintainer(s) in the above Mail-list: Isao, Watanabe; Naohiro, Tamura.
Intent: Ensure that OpenStack will run properly with Fujitsu iRMC Driver
Structure: Nodepool, Zuul, Jenkins, fully upstream components with local configuration, Tempest, Devstack
Method: Using Zuul to connect to Gerrit
OpenStack Programs: Ironic
Current Status: testing in ci-sandbox


Recheck trigger: "Fujitsu iRMC CI-recheck" and "recheck"

Maintenance plan: "6/20 00:00 - xx:xx(UTC)"
Sorry for inconvenience.

Other Fujitsu CI systems:

  • Fujitsu ETERNUS CI

https://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_ETERNUS_CI

  • Fujitsu C-Fabric CI

https://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_C-Fabric_CI

  • Fujitsu ISM CI

https://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_ISM_CI