Jump to: navigation, search

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

Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Intel SRIOV CI Tap as a Service
 
{{ThirdPartySystemInfo|name=Intel SRIOV CI Tap as a Service
 
|account=mailto:intel-openstack-ci@intel.com@intel.com
 
|account=mailto:intel-openstack-ci@intel.com@intel.com
|contact= mailto:timothy.gresham@intel.com>, <mailto:matt.welch@intel.com
+
|contact= mailto:timothy.gresham@intel.com, mailto:matt.welch@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=Zuulv3, NodePool, Gerrit Trigger, devstack, Tempest
 
|structure=Zuulv3, NodePool, Gerrit Trigger, devstack, Tempest

Revision as of 22:28, 3 January 2020

3rd party system: Intel SRIOV CI Tap as a Service
Gerrit Account: mailto:intel-openstack-ci@intel.com@intel.com
Contact Information: mailto:timothy.gresham@intel.com, mailto:matt.welch@intel.com
Intent: Ensure Openstack will run properly on Intel hardware with SRIOV device(macvtap)
Structure: Zuulv3, NodePool, Gerrit Trigger, devstack, Tempest
Method: Use Gerrit Trigger to trigger ZuulV3,. Deploy OpenStack on Intel hardware and do some custom Tempest tests with parameters of booting VM with SR-IOV tap as a service feature.
OpenStack Programs: Neutron
Current Status: Online