Jump to: navigation, search

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

Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Intel IPMI CI
 
{{ThirdPartySystemInfo|name=Intel IPMI CI
 
|account=intelotccloud
 
|account=intelotccloud
|contact= Yongli He<yongli.he@intel.com>(heyongli), <pci-ci@intel.com>,[ Experimental https://etherpad.openstack.org/p/third-party-ci-status-tracking-intel-hardware  CI Status.]
+
|contact= Leijie Yun<leijiex.yun@intel.com>(leijie),Yongli He<yongli.he@intel.com>(heyongli), <pci-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 06:26, 10 November 2016

3rd party system: Intel IPMI CI
Gerrit Account: intelotccloud
Contact Information: Leijie Yun<leijiex.yun@intel.com>(leijie),Yongli He<yongli.he@intel.com>(heyongli), <pci-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