Jump to: navigation, search

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

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

Revision as of 20:22, 17 October 2018

3rd party system: Intel SRIOV CI
Gerrit Account: intelotccloud
Contact Information: <timothy.gresham@intel.com>, <openstack-nfv-ci@intel.com>
Intent: Ensure Openstack will run properly on Intel hardware with SRIOV device(macvtap)
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 SR-IOV feature.
OpenStack Programs: Neutron
Current Status: offline, non-voting