Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Intel-IPMI-CI"

m
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Intel IPMI CI
 
{{ThirdPartySystemInfo|name=Intel IPMI CI
 
|account=intelotccloud
 
|account=intelotccloud
|contact=  <timothy.gresham@intel.com>, <openstack-nfv-ci@intel.com>, <yih.leong.sun@intel.com>,[ Experimental https://etherpad.openstack.org/p/third-party-ci-status-tracking-intel-hardware  CI Status.]
+
|contact=  <timothy.gresham@intel.com>, <openstack-nfv-ci@intel.com>, [ Experimental https://etherpad.openstack.org/p/third-party-ci-status-tracking-intel-hardware  CI Status.]
 
|intent=Ensure Openstack Ceilometer run properly on Intel hardware with IPMI device
 
|intent=Ensure Openstack Ceilometer run properly on Intel hardware with IPMI device
 
|structure=Jenkins, Gerrit Trigger, devstack, Tempest
 
|structure=Jenkins, Gerrit Trigger, devstack, Tempest

Revision as of 18:10, 30 October 2018

3rd party system: Intel IPMI CI
Gerrit Account: intelotccloud
Contact Information: <timothy.gresham@intel.com>, <openstack-nfv-ci@intel.com>, [ Experimental https://etherpad.openstack.org/p/third-party-ci-status-tracking-intel-hardware CI Status.]
Intent: Ensure Openstack Ceilometer run properly on Intel hardware with IPMI device
Structure: Jenkins, Gerrit Trigger, devstack, Tempest
Method: Use Gerrit Trigger to trigger local jenkins project. Deploy OpenStack on Intel hardware and do custom Tempest tests with booting VM with IPMI feature.
OpenStack Programs: Ceilometer
Current Status: testing, non-voting