ThirdPartySystems/Intel-PCI-CI-internal

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

(15Ê±04·Ö55Ãë) jyuso1: The main troubles PCI CI met:
(15Ê±05·Ö06Ãë) jyuso1: 1.Networking is not stable enough.Git operation fails some time.
(15Ê±05·Ö07Ãë) jyuso1: Our solution:Add HA pypi mirror,including local mirror and internal mirror to avoid networking down.
(15Ê±05·Ö07Ãë) jyuso1: Add main alert.If there is something wrong in network,we'll know is ASAP.
(15Ê±05·Ö33Ãë) jyuso1: 2.Tempest cases merge new content,test cases have to be update usually. Our solution:Don't use upstreaming Tempest directory,just maintain local Tempest code.
(15Ê±05·Ö43Ãë) jyuso1: 3.Software on CI server is not clean entirely and it may cause CI testing stuck,like mysql. Our solution:Add specified steps to clean these software.