[openstack-dev] [tripleo] CI / Tempest Sprint 11 Summary

Matt Young myoung at redhat.com
Fri Apr 13 22:24:00 UTC 2018


Greetings,

The TripleO squads for CI and Tempest have just completed Sprint 11.  The
following is a summary of activities during this sprint.  The newly formed
Tempest Squad has completed its first sprint.  Details on the team
structure can be found in the spec [1].

Sprint 11 Epic (CI Squad): Upgrades
Epic Card: https://trello.com/c/8pbRwBps/549-upstream-upgrade-ci

This is the second sprint that the team focused on CI for upgrades.  We
expect additional sprints will be needed focused on upgrades, and have a
number of backlog tasks remaining as well [2]

We did the following:
* Prune and remove old / irrelevant jobs from CI
* Assess the current state of existing jobs to determine status and issues.
* Ensure the reproducer script enabling the correct branches of
tripleo-upgrade
* Implement “Keystone Only” CI job.  This is a minimal deployment with the
smallest set of services (keystone + deps) in play.
   * tripleo-ci-centos-7-scenario000-multinode-oooq-container-updates
* Consolidate  docker namespaces between docker.io, rdoproject.org


Sprint 11 Epic (Tempest Squad): Containerize Tempest
Epic Card: https://trello.com/c/066JFJjf/537-epic-containerize-tempest


As noted above, this is the first sprint for the newly formed Tempest
Squad.  The work was a combination of the sprint epic and team members’
pre-existing work that is nearing completion.

We did the following:
* Fix tempest plugins upgrade issue (RHOS 10>11>12>13)
* Switch to stestr to run tempest beginning with queens
* Move neutron CLI calls to openstack CLI
* Containerize tempest on featureset027 (UC idempotency)

We made progress on the following, but work remains and continues in Sprint
12
* Refactor validate-tempest CI role for UC and containers (reviews in
flight)
* Updates to ansible-role-openstack-certification playbook & CI jobs that
use it.
* Upstream documentation covering above work

Note:
We have added a new trello board [2] to archive completed sprint cards.
Previously we were archiving (trello operation) the cards, making it
difficult to analyze/search the past.

Ruck and Rover

Each sprint two of the team members assume the roles of Ruck and Rover
(each for half of the sprint).
* Ruck is responsible to monitoring the CI, checking for failures, opening
bugs, participate on meetings, and this is your focal point to any CI
issues.
* Rover is responsible to work on these bugs, fix problems and the rest of
the team are focused on the sprint. For more information about our
structure, check [1]

Ruck & Rover (Sprint 11), Etherpad [4]:
* Arx Cruz (arxcruz)
* Rafael Folco (rfolco)

Two issues in particular where substantial time was spent were:

http://bugs.launchpad.net/bugs/1757556 (SSH timeouts)
https://bugs.launchpad.net/tripleo/+bug/1760189 (AMQP issues)

The full list of bugs open or worked on were:

https://bugs.launchpad.net/tripleo/+bug/1763009
https://bugs.launchpad.net/tripleo/+bug/1762419
https://bugs.launchpad.net/tripleo/+bug/1762351
https://bugs.launchpad.net/tripleo/+bug/1761171
https://bugs.launchpad.net/tripleo/+bug/1760189
https://bugs.launchpad.net/bugs/1757556
https://bugs.launchpad.net/tripleo/+bug/1759868
https://bugs.launchpad.net/tripleo/+bug/1759876
https://bugs.launchpad.net/tripleo/+bug/1759583
https://bugs.launchpad.net/tripleo/+bug/1758143
https://bugs.launchpad.net/tripleo/+bug/1757134
https://bugs.launchpad.net/tripleo/+bug/1755485
https://bugs.launchpad.net/tripleo/+bug/1758932
https://bugs.launchpad.net/tripleo/+bug/1751180

If you have any questions and/or suggestions, please contact us in #tripleo

Thanks,

Matt

[1]
https://specs.openstack.org/openstack/tripleo-specs/specs/policy/ci-team-structure.html
[2]
https://trello.com/b/U1ITy0cu/tripleo-and-rdo-ci?menu=filter&filter=label:upgrades

[3] https://trello.com/b/BjcIIp0f/tripleo-and-rdo-ci-archive
[4] https://review.rdoproject.org/etherpad/p/ruckrover-sprint11
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180413/4234c952/attachment.html>


More information about the OpenStack-dev mailing list