Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Intel NGFW CI"

Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Intel NGFW CI
 
{{ThirdPartySystemInfo|name=Intel NGFW CI
 
|account=intelotccloud
 
|account=intelotccloud
|contact=Jiang Yu <yux.y.jiang@intel.com>(jyuso), Zang Rui <rui.zang@intel.com>,Wang Yalei <yalei.wang@intel.com>,Wang Shane <shane.wang@intel.com>(shane-wang), <ngfw-ci@intel.com>
+
|contact=Jiang Yu <yux.y.jiang@intel.com>(jyuso), Zang Rui <rui.zang@intel.com>,Wang Yalei <yalei.wang@intel.com>,Wang Shane <shane.wang@intel.com>(shane-wang), <ngfw-ci@intel.com>,[https://etherpad.openstack.org/p/third-party-ci-status-tracking-intel-hardware What happens, click here.]
 
|intent=CI for INTEL next generation firewall (NGFW)
 
|intent=CI for INTEL next generation firewall (NGFW)
 
|structure=Jenkins, Gerrit Trigger, devstack, Tempest
 
|structure=Jenkins, Gerrit Trigger, devstack, Tempest

Revision as of 23:40, 2 January 2016

3rd party system: Intel NGFW CI
Gerrit Account: intelotccloud
Contact Information: Jiang Yu <yux.y.jiang@intel.com>(jyuso), Zang Rui <rui.zang@intel.com>,Wang Yalei <yalei.wang@intel.com>,Wang Shane <shane.wang@intel.com>(shane-wang), <ngfw-ci@intel.com>,What happens, click here.
Intent: CI for INTEL next generation firewall (NGFW)
Structure: Jenkins, Gerrit Trigger, devstack, Tempest
Method: Use Gerrit Trigger to trigger local jenkins project. Deploy NGFW firewall driver to test fwaas.
OpenStack Programs: Neutron
Current Status: offline, non-voting