Difference between revisions of "ThirdPartySystems/Intel-PCI-CI-internal"
(→Over View) |
(→Issue) |
||
| Line 20: | Line 20: | ||
=== Issue === | === Issue === | ||
| − | + | In Intel CI environment, we need a proxy to pull git repository, pip package and apt package. Also we will push the CI test log to an AWS log server.<br/> | |
| − | + | Any problem during the pull or push process, Our CI will report failure to the gerrit. | |
| − | + | ||
| − | + | We have do some improvement to our CI. | |
| − | + | ||
| − | + | But still some problems need to fix. | |
Revision as of 07:45, 9 November 2015
Intel PCI CI
Intel PCI CI is used to ensure Openstack will 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.
Over View
picture: see this link https://wiki.openstack.org/w/images/0/0d/F2Xi3Ucq.1447053596.png
And this is the CI work flow:
1.Jenkins server Listens a patchset action from gerrit server.
2.Begin to clean local server.Including execute unstack.sh, execute clean.sh, delete related logs, kill all openstack daemons,delete devstack directory.
3.After Clean step is over,do git pull in all directories in /opt/stack/ ,make sure the source code is the latest version.
4.Apply patch to Nova source code.Use command: git fetch xxxx && git checkout xxxx
5.Modify devstack/lib/nova,insert PCI parameters.
6.Generate local.conf file.
7.Running devstack installation.
8.After devstack is done,run PCI Tempest test cases.
9.Report results back to gerrit server.
Issue
In Intel CI environment, we need a proxy to pull git repository, pip package and apt package. Also we will push the CI test log to an AWS log server.
Any problem during the pull or push process, Our CI will report failure to the gerrit.
We have do some improvement to our CI.
But still some problems need to fix.
