Jump to: navigation, search

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

m
 
(25 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Intel PCI CI
 
{{ThirdPartySystemInfo|name=Intel PCI CI
|account=Intel PCI CI
+
|account=intelotccloud
|contact=contact info for people taking responsibility for this system
+
|contact= timothy.gresham@intel.com, pci-ci@intel.com,[https://etherpad.openstack.org/p/third-party-ci-status-tracking-intel-hardware  CI Status.]
|intent=of this system, why do you have it
+
|intent=Ensure Openstack will run properly on Intel hardware with PCI device([https://github.com/intel-hw-ci/Intel-Openstack-Hardware-CI/tree/master/pci_testcases pci_testcases])
|structure=of this system, what tools are you using
+
|structure=Jenkins, Gerrit Trigger, devstack, Tempest
|method=what you are actually doing
+
|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.
|programs=touched by this system
+
|programs=Nova
|status=of this system, in production, testing, non-voting, voting, disabled}}
+
|status=testing, non-voting}}

Latest revision as of 17:22, 24 April 2019

3rd party system: Intel PCI CI
Gerrit Account: intelotccloud
Contact Information: timothy.gresham@intel.com, pci-ci@intel.com,CI Status.
Intent: Ensure Openstack will run properly on Intel hardware with PCI device(pci_testcases)
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