ThirdPartySystems/Intel-PCI-CI-internal - Revision history

Shaohef at 02:34, 16 November 2015

2015-11-16T02:34:18Z

2015-11-13T17:14:27Z

2015-11-10T01:08:59Z

‎Our plan

2015-11-10T01:02:57Z

‎Intel PCI CI

2015-11-10T00:38:41Z

‎Issue

2015-11-09T12:07:24Z

‎Our plan

2015-11-09T08:46:40Z

‎Overview

2015-11-09T08:38:10Z

‎Overview

2015-11-09T08:30:50Z

‎Issue

2015-11-09T08:25:42Z

‎Overview

← Older revision		Revision as of 02:34, 16 November 2015
Line 1:		Line 1:
		+	https://etherpad.openstack.org/p/third-party-ci-status-tracking-intel-hardware
	== Intel PCI CI==		== Intel PCI CI==
	Intel PCI CI is used to ensure OpenStack to run properly on Intel hardware with PCI device.		Intel PCI CI is used to ensure OpenStack to run properly on Intel hardware with PCI device.

@@ Line 34: / Line 34: @@
 [[File:Intel-CI-improvement1.png]]
-* Zabbix monitor/alarm: this will be triggered automatically to notice operation.
+* Zabbix monitor/alarm: this will be triggered automatically to notice operation[ongoing].
-* Proxy HA: currently we have 3 proxy server, and they can back up each other.
+* Proxy HA: currently we have 3 proxy server, and they can back up each other[automation switching scripts available].
-* Local PIP mirror and PIP repository HA (done): all test machine has their own local pip mirror, this will reduce testing time.
+* Local PIP mirror and PIP repository mirror server form a active active HA mode(done): all test machine has their own local pip mirror, this will reduce testing time.
 * Mail alert  (done): any network issue will be sent out to operations. We have work shift between US and China.

@@ Line 34: / Line 34: @@
 [[File:Intel-CI-improvement1.png]]
-* Zabbix monitor/alarm
+* Zabbix monitor/alarm: this will be triggered automatically to notice operation.
-* Proxy HA
+* Proxy HA: currently we have 3 proxy server, and they can back up each other.
-* Local PIP mirror and PIP repository HA (done)
+* Local PIP mirror and PIP repository HA (done): all test machine has their own local pip mirror, this will reduce testing time.
-* Mail alert  (done)
+* Mail alert  (done): any network issue will be sent out to operations. We have work shift between US and China.

@@ Line 1: / Line 1: @@
 == Intel PCI CI==
-Intel PCI CI is used to ensure Openstack will run properly on Intel hardware with PCI device.
+Intel PCI CI is used to ensure OpenStack to run properly on Intel hardware with PCI device.
-It 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.
+It leverages 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.

@@ Line 25: / Line 25: @@
 But still some problems need to fix. <br/>
-* especially it will failed when pull git repository.
+* especially it will failed when pull git repository.(pull git repository every test, incremental pull)
 * some times the proxy will disconnect.
 * the network speed is very slow

@@ Line 32: / Line 32: @@
 === Our plan ===
-[[File:Intel-CI-improvement.png]]
+[[File:Intel-CI-improvement1.png]]
 * Zabbix monitor/alarm

@@ Line 9: / Line 9: @@
 And this is the CI working flow: <br/>
 Structure: Jenkins, Gerrit Trigger, devstack, Tempest(not upstream version).<br/>
-# Jenkins master server Listens a patchset action from gerrit server. <br/>
+# Jenkins master server Listens a patchset action from gerrit server,assign task to a testing server. <br/>
 # Begin to clean local server.Including execute unstack.sh, execute clean.sh, delete related logs, kill all openstack daemons，remove mysql packages,delete devstack directory.<br/>
 # After Clean step is over,do git pull in all directories in /opt/stack/ ,make sure the source code is the latest version.<br/>

@@ Line 7: / Line 7: @@
 === Overview ===
 [[file:F2Xi3Ucq.1447053596.png]]
-# And this is the CI working flow: <br/>
+And this is the CI working flow: <br/>
-# Structure: Jenkins, Gerrit Trigger, devstack, Tempest(not upstream version).<br/>
+Structure: Jenkins, Gerrit Trigger, devstack, Tempest(not upstream version).<br/>
 # Jenkins master server Listens a patchset action from gerrit server. <br/>
 # Begin to clean local server.Including execute unstack.sh, execute clean.sh, delete related logs, kill all openstack daemons,delete devstack directory.<br/>
@@ Line 18: / Line 18: @@
 # After devstack is done,run PCI Tempest test cases.<br/>
 # Report results back to gerrit server.<br/>
 === Issue ===