Jump to: navigation, search

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

Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Intel PCI CI
 
{{ThirdPartySystemInfo|name=Intel PCI CI
 
|account=intelotccloud
 
|account=intelotccloud
|contact=Jiang Yu <yux.y.jiang@intel.com>(jyuso), Wang Shane <shane.wang@intel.com>(shane-wang), <pci-ci@intel.com>
+
|contact=Jiang Yu <yux.y.jiang@intel.com>(jyuso), Wang Shane <shane.wang@intel.com>(shane-wang), <pci-ci@intel.com>,[https://etherpad.openstack.org/p/third-party-ci-status-tracking-intel-hardware What happens, click here.]
 
|intent=Ensure Openstack will run properly on Intel hardware with PCI device
 
|intent=Ensure Openstack will run properly on Intel hardware with PCI device
 
|structure=Jenkins, Gerrit Trigger, devstack, Tempest
 
|structure=Jenkins, Gerrit Trigger, devstack, Tempest

Revision as of 21:48, 10 December 2015

3rd party system: Intel PCI CI
Gerrit Account: intelotccloud
Contact Information: Jiang Yu <yux.y.jiang@intel.com>(jyuso), Wang Shane <shane.wang@intel.com>(shane-wang), <pci-ci@intel.com>,What happens, click here.
Intent: Ensure Openstack will run properly on Intel hardware with PCI device
Structure: Jenkins, Gerrit Trigger, devstack, Tempest
Method: Use Gerrit Trigger to trigger local jenkins project. Deploy OpenStack on Intel hardware and do some custom Tempest tests with parameters of booting VM with PCI feature.
OpenStack Programs: Nova
Current Status: testing, non-voting