[openstack-dev] [tripleo] TripleO CI+Tempest Squad Planning Summary: Sprint 17

[Matt Young]

>From the Halls of CI we greet thee!  HAIL!

# Overview

The CI and Tempest squads have recently completed the planning phase of
Sprint 17.  The Sprint runs from 26-July thru 15-Aug.  The sprint for both
squads is now in the initial design phase (first week) of the sprint.

The epic card and tasks for CI [1][2] and Tempest [3][4] squads are linked
below.

The Ruck and Rover for this sprint  are Gabriele Cerami (panda) and Rafael
Folco (rfolco).  Their notes and current status is tracked in the etherpad
for sprint 17 [5].

Please direct questions or queries to them regarding CI status or issues in
#tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick.

# CI Squad

* The main topic is focused on continuing the migration to zuul v3,
including migrating from legacy bash to ansible tasks/playbooks
* Between planned PTO and training, the team is running at reduced capacity
this sprint.

# Tempest Squad

* clearing out technical debt related to python-tempestconf and
refstack-client integration.
* developing materials for a presentation on implementing a tempest plugin.
* splitting out the validate-tempest role [6] to a discrete repository.
* Due to planned PTO the squad is quite resource constrained this sprint.

More detail on our team and process can be found in the spec [7]

Thanks,

Matt

[1] https://trello.com/c/JikmHXSS/881-sprint-17-goals
[2]
https://trello.com/b/U1ITy0cu/tripleo-and-rdo-ci?menu=filter=label:Sprint%2017%20CI

[3]
https://trello.com/c/yAnDETzJ/878-sprint-17-tempest-clear-technical-debts
[4]
https://trello.com/b/U1ITy0cu/tripleo-and-rdo-ci?menu=filter=label:Sprint%2017%20Tempest
[5] https://review.rdoproject.org/etherpad/p/ruckrover-sprint17
[6]
https://github.com/openstack/tripleo-quickstart-extras/tree/master/roles/validate-tempest
[7]
https://specs.openstack.org/openstack/tripleo-specs/specs/policy/ci-team-structure.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] TripleO Tempest squad status: Sprint 16

[Matt Young]

Greetings,

The TripleO Tempest squad has recently completed Sprint 16 (5-July -
25-July).

This sprint was focused on tasks related to python-tempestconf and
integration with the refstack client.  Some of this work will continue in
Sprint 17.

For a list of the completed and items for the sprint please refer to the
Epic card [1] and the task cards [2].

Thanks,

Matt

[1]
https://trello.com/c/1v1dYRnP/144-sprint-16-closing-python-tempestconf-items-out
[2]
https://trello.com/b/BjcIIp0f/tripleo-and-rdo-ci-archive?menu=filter=label:Sprint%2016%20Tempest
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] TripleO CI squad status: Sprint 16

[Matt Young]

Greetings,

The TripleO CI squad has recently completed Sprint 16 (5-July - 25-July).

The Sprint was focused on the migration to Zuul v3.  For a list of the
completed items for the sprint please refer to the Epic card [1] and the
task cards [2].

The Ruck & Rover roles this sprint were filled by Chandan Kumar and Sagi
Shnaidman.  Thanks to them for their efforts!

Detailed notes concerning bugs filed and issues worked on are available in
the etherpad [3]

Thanks,

Matt

[1] https://trello.com/c/vyWXcKOB/143-ci-squad-sprint-16-goals
[2]
https://trello.com/b/BjcIIp0f/tripleo-and-rdo-ci-archive?menu=filter=label:SPRINT%2016%20CI
[3] https://review.rdoproject.org/etherpad/p/ruckrover-sprint16
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] [tripleo-validations] using using top-level fact vars will deprecated in future Ansible versions

[Matt Young]

I've captured this as a point of discussion for the TripleO CI Team's
planning session(s).

Matt
On Tue, Jul 24, 2018 at 4:59 AM Bogdan Dobrelya  wrote:
>
> On 7/23/18 9:33 PM, Emilien Macchi wrote:
> > But it seems like, starting with Ansible 2.5 (what we already have in
> > Rocky and beyond), we should encourage the usage of ansible_facts
> > dictionary.
> > Example:
> > var=hostvars[inventory_hostname].ansible_facts.hostname
> > instead of:
> > var=ansible_hostname
>
> If that means rewriting all ansible_foo things around the globe, we'd
> have a huge scope for changes. Those are used literally everywhere. Here
> is only a search for tripleo-quickstart [0]
>
> [0]
> http://codesearch.openstack.org/?q=%5B%5C.%27%22%5Dansible_%5CS%2B%5B%5E%3A%5D=nope=roles=tripleo-quickstart
>
> --
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] Sprint 15 Planning Summary (CI, Tempest squads)

[Matt Young]

Greetings,

The TripleO CI & Tempest squads have begun work on Sprint 15.  Like
most of our sprints these are three weeks long and are planned on a
Thursday or Friday (depending on squad) and end with a retrospective
on Wednesdays.

Sprint 15 runs from 2018-06-14 to 2018-07-03

More information regarding our process is available in the
tripleo-specs repository [1]. Ongoing meeting notes and other detail
are always available in the Squad Etherpads [2,3].


# Ruck / Rover:
* weshay + quiquell
* https://review.rdoproject.org/etherpad/p/ruckrover-sprint15


# CI Squad

Epic: https://trello.com/c/bQuQ9aWF/802-sprint-15-ci-goals
Tasks: http://ow.ly/3kDB30kypjH

This sprint the CI squad is transitioning to a new topic!

We are spending the first of at least three sprints on the topic of
migrating tripleo CI to Zuul v3.  We’ve split the team into two “tiger
teams” [4] for the first portion of the sprint.  One is focused on
issues of networking and multinode support, the other looking at
generating job configuration parent jobs, from which other jobs will
derive.

This work will inform a number of activities in this sprint and
sprints to come.  This includes topics such as refactoring of TOCI
gate scripts (bash → ansible/python), full native ansible tooling, and
putting into place jobs to address python3, RHEL8 (future centos), RDO
on RHEL, and other topics enabled by support for an RH internal
deployment of Software Factory.

We will also be monitoring efforts by upstream openstack-infra to
transition jobs @ review.rdoproject.org to zuul v3, on standby to
assist as needed.


# Tempest Squad

Epic:  https://trello.com/c/6QKG0HkU/801-sprint-15-python-tempestconf
Tasks: http://ow.ly/XnB530kyppQ

The Tempest Squad this sprint is operating with UA (chandankumar) on
PTO for most of the sprint.  We are focused on 3 main topics:

* Closing out the remaining python-tempestconf refactor tasks for core
OpenStack services
* Create a presentation covering tempest plugin creation
* Targeted tasks addressing RefStack certification for rhos 11,12,13

For any questions please find us in #tripleo

Thanks,

Matt

[1] 
https://github.com/openstack/tripleo-specs/blob/master/specs/policy/ci-team-structure.rst
[2] https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
[3] https://etherpad.openstack.org/p/tripleo-tempest-squad-meeting
[4] https://en.wikipedia.org/wiki/Tiger_team

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] CI Team Sprint 13 Summary

[Matt Young]

Greetings,

The TripleO CI team has just completed Sprint 13 (5/3 - 05/23).  The
following is a summary of activities during our sprint.   Details on our
team structure can be found in the spec [1].


# Sprint 13 Epic (CI Squad): Upgrade Support and Refactoring

- Epic Card: https://trello.com/c/cuKevn28/728-sprint-13-upgrades-goals
- Tasks: http://ow.ly/L86Y30kg75L

This sprint was spent with the CI squad focused on Upgrades.

We wanted to be able to use existing/working/tested CI collateral (ansible
playbooks and roles) used in CI today.  Throughout many of these are
references to  “{{ release }}” (e.g. ‘queens’, ‘pike’).  In order to not
retrofit the bulk of these with “upgrade aware” conditionals and/or logic
we needed a tool/module that could generate the inputs for the ‘release’
variable (and other similar inputs).   This allows us to reuse our common
roles and playbooks by decoupling the specifics of {upgrades, updates, FFU}
* {pike, queens, rocky,…}.  We’ve created this tool, and also put into
place a linting and unit tests for it as well.  We also made a few of the
jobs that had been prototyped and created in previous sprints voting, then
used them to validate changes to said jobs to wire in the new workflow/tool.

We are optimistic that work done in sprint 13 will prove useful in future
sprints.  A table to describe some of the problem set and our thinking
around variables used in CI is at [2].  The tool and tests are at [3].


# Sprint 13 Epic (Tempest Squad):

- Epic Card:
https://trello.com/c/efqE5XMr/82-sprint-13-refactor-python-tempestconf
- Tasks: http://ow.ly/LH8Q30kgd1C

In Sprint 13 the tempest squad was focused on refactoring
python-tempestconf.  It is the primary tool used by tempest users to
generate tempest.conf automatically so that users can easily run tempest
tests. Currently in TripleO and Infrared CI, we pass numerous parameters
manually via CLI.  This is cumbersome and error prone.

The high level goals were to reduce the number of default CLI overrides
used today, and to prepare python-tempestconf enabling better integration
with refstack-client.  This entailed service discoverability work.  We
added support for keystone, glance, cinder, swift, and neutron.  Additional
service support is planned for future sprints.  We also improved existing
documentation for python-tempestconf.


# Ruck & Rover (Sprint 13)

Sagi Shnaidman (sshnaidm), Matt Young (myoung)
https://review.rdoproject.org/etherpad/p/ruckrover-sprint13

A few notable issues where substantial time was spent are below.  Note that
this is not an inclusive list:

- When centos 7.5 was released, this caused a number of issues that
impacted gates.  This included deltas between package versions in BM vs.
container images, changes to centos that caused failures when modifying
images (e.g. IPA) in gates, and the like.
- We experienced issues with our promoter server, and the tripleo-infra
tenant generally around DNS and networking throughput, which impactacted
ability to process promotions.
- RHOS-13 jobs were created, and will eventually be used to gate changes to
TQ/TQE.
- Numerous patches/fixes to RDO Phase 2 jobs and CI infra. We had
accumulated technical debt.  While we have additional work to do,
particularly around some of the BM configs, we made good progress in
bringing various jobs back online.  We are still working on this in sprint
14 and moving forward.

Thanks,

The Tripleo CI team

[1]
https://specs.openstack.org/openstack/tripleo-specs/specs/policy/ci-team-structure.html
[2] https://wiki.openstack.org/wiki/Tripleo-upgrades-fs-variables
[3]
https://github.com/openstack-infra/tripleo-ci/blob/master/scripts/emit_releases_file
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] tripleo upstream gate outtage, was: -> gate jobs impacted RAX yum mirror

[Matt Young]

Re: resolving network latency issue on the promotion server in
tripleo-infra tenant, that's great news!

Re: retrospective on this class of issue, I'll reach out directly early
this week to get something on the calendar for our two teams.  We clearly
need to brainstorm/hash out together how we can reduce the turbulence
moving forward.

In addition, as a result of working these issues over the past few days
we've identified a few pieces of low hanging (tooling) fruit that are ripe
for for improvements that will speed diagnosis / debug in the future.
We'll capture these as RFE's and get them into our backlog.

Matt

On Sun, May 13, 2018 at 10:25 AM, Wesley Hayutin 
wrote:

>
>
> On Sat, May 12, 2018 at 11:45 PM Emilien Macchi 
> wrote:
>
>> On Sat, May 12, 2018 at 9:10 AM, Wesley Hayutin 
>> wrote:
>>>
>>> 2. Shortly after #1 was resolved CentOS released 7.5 which comes
>>> directly into the upstream repos untested and ungated.  Additionally the
>>> associated qcow2 image and container-base images were not updated at the
>>> same time as the yum repos.  https://bugs.launchpad.net/tripleo/+bug/
>>> 1770355
>>>
>>
>> Why do we have this situation everytime the OS is upgraded to a major
>> version? Can't we test the image before actually using it? We could have
>> experimental jobs testing latest image and pin gate images to a specific
>> one?
>> Like we could configure infra to deploy centos 7.4 in our gate and 7.5 in
>> experimental, so we can take our time to fix eventual problems and make the
>> switch when we're ready, instead of dealing with fires (that usually come
>> all together).
>>
>> It would be great to make a retrospective on this thing between tripleo
>> ci & infra folks, and see how we can improve things.
>>
>
> I agree,
> We need to in coordination with the infra team be able to pin / lock
> content for production check and gate jobs while also have the ability to
> stage new content e.g. centos 7.5 with experimental or periodic jobs.
> In this particular case the ci team did check the tripleo deployment w/
> centos 7.5 updates, however we did not stage or test what impact the centos
> minor update would have on the upstream job workflow.
> The key issue is that the base centos image used upstream can not be
> pinned by the ci team, if say we could pin that image the ci team could pin
> the centos repos used in ci and run staging jobs on the latest centos
> content.
>
> I'm glad that you also see the need for some amount of coordination here,
> I've been in contact with a few folks to initiate the conversation.
>
> In an unrelated note, Sagi and I just fixed the network latency issue on
> our promotion server, it was related to DNS.  Automatic promotions should
> be back online.
> Thanks all.
>
>
>> --
>> Emilien Macchi
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] CI Squads’ Sprint 12 Summary: libvirt-reproducer, python-tempestconf

[Matt Young]

Greetings,

The TripleO squads for CI and Tempest have just completed Sprint 12.  The
following is a summary of activities during this sprint.   Details on our
team structure can be found in the spec [1].

---

# Sprint 12 Epic (CI): Libvirt Reproducer

* Epic Card: https://trello.com/c/JEGLSVh6/51-reproduce-ci-jobs-with-libvirt
* Tasks: http://ow.ly/O1vZ30jTSc3

"Allow developers to reproduce a multinode CI job on a bare metal host
using libvirt"
"Enable the same workflows used in upstream CI / reproducer using libvirt
instead of OVB as the provisioning mechanism"

The CI Squad prototyped, designed, and implemented new functionality for
our CI reproducer.   “Reproducers” are scripts generated by each CI job
that allow the job/test to be recreated.  These are useful to both CI team
members when investigating failures, as well as developers creating
failures with the intent to iteratively debug and/or fix issues.  Prior to
this sprint, the reproducer scripts supported reproduction of upstream CI
jobs using OVB, typically on RDO Cloud.  This sprint we extended this
capability to support reproduction of jobs in libvirt.

This work was done for a few reasons:

* (short term) enable the team to work on upgrades and other CI team tasks
more efficiently by mitigating recurring RDO Cloud infrastructure issues.
This was the primary motivator for doing this work at this time.
* (mid-longer term) enhance / enable iterative workflows such as THT
development, debugging deployment scenarios, etc.  Snapshots in particular
have proven quite useful.  As we look towards a future with a viable
single-node deployment capability, libvirt has clear benefits for common
developer scenarios.

It is expected that further iteration and refinement of this initial
implementation will be required before the tripleo-ci team is able to
support this broadly.  What we’ve done works as designed.  While we welcome
folks to explore, please note that we are not announcing a supported
libvirt reproducer meant for use outside the tripleo-ci team at this time.
We expect some degree of change, and have a number of RFE’s resulting from
our testing as well as documentation patches that we’re iterating on.

That said, we think it’s really cool, works well in its current form, and
are optimistic about its future.

## We did the following (CI):

* Add support to the reproducer script [2,3] generated by CI to enable
libvirt.
* Basic snapshot create/restore [4] capability.
* Tested Scenarios: featureset 3 (UC idem), 10 (multinode containers), 37
(min OC + minor update).  See sprint cards for details.
* 14-18 RFE’s identified as part of testing for future work
http://ow.ly/J2u830jTSLG

---

# Sprint 12 Epic (Tempest):

* Epic Card: https://trello.com/c/ifIYQsxs/75-sprint-12-undercloud-tempest
* Tasks: http://ow.ly/GGvc30jTSfV

“Run tempest on undercloud by using containerized and packaged tempest”
“Complete work items carried from sprint 11 or another side work going on.”

## We did the following (Tempest):

* Create tripleo-ci jobs that run containerized tempest on all stable
branches.
* Create documentation for configuring and running tempest using
containerized tempest on UC @tripleo.org, and blog posts. [5,6,7]
* Run certification tests via new Jenkins job using ansible role [8]
* Refactor validate-tempest CI role for UC and containers

---

# 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 12), Etherpad [9,10]:

* Quique Llorente(quiquell)
* Gabriele Cerami (panda)

A few notable issues where substantial time was spent were:

1767099 periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset030-master
vxlan tunnel fails randomly
1758899 reproducer-quickstart.sh building wrong gating package.
1767343 gate tripleo-ci-centos-7-containers-multinode fails to update
packages in cron container
1762351
periodic-tripleo-ci-centos-7-ovb-1ctlr_1comp-featureset002-queens-upload is
timeout Depends on https://bugzilla.redhat.com/show_bug.cgi?id=1565179
1766873 quickstart on ovb doesn't yield a deployment
1767049 Error during test discovery : 'must specify exactly one of host or
intercept' Depends on https://bugzilla.redhat.com/show_bug.cgi?id=1434385
1767076 Creating pingtest_sack fails: Failed to schedule instances:
NoValidHost_Remote: No valid host was found
1763634 devmode.sh --ovb fails to deploy overcloud
1765680 Incorrect branch used for not gated tripleo-upgrade repo

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

Thanks,

Matt


tq: https://github.com/openstack/tripleo-quickstart
tqe: 

[openstack-dev] [tripleo] CI & Tempest squad planning summary: Sprint 13

[Matt Young]

Greetings,

The TripleO CI & Tempest squads have begun work on Sprint 13.  Like most of
our sprints these are three weeks long and are planned on a Thursday or
Friday (depending on squad) and have a retrospective on Wednesday.  Sprint
13 runs from 2018-05-03 thru 2018-05-23.

More information regarding our process is available in the tripleo-specs
repository [1]. Ongoing meeting notes and other detail are always available
in the Squad Etherpads [2,3].

This sprint the CI squad is working on the Upgrades epic, and the Tempest
squad is refactoring python-tempestconf to in part enable the upstream
refstack group.


## Ruck / Rover:

* Matt Young (myoung) and Sagi Shnaidman (sshnaidm)
* https://review.rdoproject.org/etherpad/p/ruckrover-sprint13


## CI Squad

* Put in place voting update jobs (
https://review.openstack.org/#/q/topic:gate_update)
* Add additional check/gate jobs to gate changes made this sprint.
* Refine the design for how we model releases in CI, taking into account
feedback from a collaborative design session with the Upgrades team
(etherpad http://ow.ly/da5L30jSeo8).

Epic: https://trello.com/c/cuKevn28/728-sprint-13-upgrades-goals
Tasks: http://ow.ly/yeIf30jScyj


## Tempest Squad

* Refactor pythyon-tempestconf tempest config by dynamically discovering
resources

In Scope: Keystone, Nova, Glance, Neutron, Cinder, Swift.

The following are specifically NOT in scope for Sprint 13  They are
tentatively planned for future sprints: Heat, Ironic, ec2api, Zaquar,
Mistral, Manila, Octavia, Horizon, Ceilometer.

Epic:
https://trello.com/c/efqE5XMr/734-sprint-13-refactor-python-tempestconf
Tasks: http://ow.ly/YOXh30jScEw


For any questions please find us in #tripleo

Thanks,

Matt

[1]
https://github.com/openstack/tripleo-specs/blob/master/specs/policy/ci-team-structure.rst
[2] https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
[3] https://etherpad.openstack.org/p/tripleo-tempest-squad-meeting
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] CI Community Meeting tomorrow (2018-04-24)

[Matt Young]

Greetings,

Tomorrow the CI team will be hosting its weekly Community Meeting. We
welcome any/all to join.  The meeting is a place to discuss any concerns /
questions / issues from the community regarding CI.

It will (as usual) be held immediately following the general #tripleo
meeting on BlueJeans [2], typically ~14:30 UTC.  Please feel free to add
items to the agenda [2] or simply come and chat.

Thanks,

Matt

[1] https://bluejeans.com/7050859455

[2] https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] CI & Tempest squad planning summary: Sprint 12

[Matt Young]

Greetings,

The TripleO CI & Tempest squads have begun work on Sprint 12.  This is a 3
week sprint.

The Ruck & Rover for this sprint are quiquell and panda.

## CI Squad

Goals:

"As a developer, I want reproduce a multinode CI job on a bare metal host
using libvirt"
"Enable the same workflows used in upstream CI / reproducer using libvirt
instead of OVB"

Epic:  https://trello.com/c/JEGLSVh6/323-reproduce-ci-jobs-with-libvirt
Tasks: https://tinyurl.com/yd93nz8p

## Tempest Squad

Goals:

"Run tempest on undercloud by using containerized and packaged tempest as
well as against Heat, Mistral, Ironic, Tempest and python-tempestconf
upstream"
"Finish work items carried from sprint 11 or other side work going on."

Epic:  https://trello.com/c/ifIYQsxs/680-sprint-12-undercloud-tempest
Tasks: https://tinyurl.com/y8k6yvbm

For any questions please find us in #tripleo

Thanks,

Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Matt Young]

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=label:upgrades

[3] https://trello.com/b/BjcIIp0f/tripleo-and-rdo-ci-archive
[4] https://review.rdoproject.org/etherpad/p/ruckrover-sprint11
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

[Matt Young]

+1

On Thu, Dec 7, 2017 at 9:05 AM, Ronelle Landy  wrote:

> +1
>
> On Thu, Dec 7, 2017 at 8:47 AM, Brad P. Crochet  wrote:
>
>> +1
>>
>>
>> On Wed, Dec 6, 2017 at 10:46 AM Emilien Macchi 
>> wrote:
>>
>>> Team,
>>>
>>> Wes has been consistently and heavily involved in TripleO CI work.
>>> He has a very well understanding on how tripleo-quickstart and
>>> tripleo-quickstart-extras work, his number and quality of reviews are
>>> excellent so far. His experience with testing TripleO is more than
>>> valuable.
>>> Also, he's always here to help on TripleO CI issues or just
>>> improvements (he's the guy filling bugs on a Saturday evening).
>>> I think he would be a good addition to the TripleO CI core team
>>> (tripleo-ci, t-q and t-q-e repos for now).
>>> Anyway, thanks a lot Wes for your hard work on CI, I think it's time
>>> to move on and get you +2 ;-)
>>>
>>> As usual, it's open for voting, feel free to bring any feedback.
>>> Thanks everyone,
>>> --
>>> Emilien Macchi
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> --
>> Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
>> Principal Software Engineer
>> (c) 704.236.9385 <(704)%20236-9385>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] Proposing Ronelle Landy for Tripleo-Quickstart/Extras/CI core

[Matt Young]

+1


On Thu, Nov 30, 2017 at 10:34 AM, Dan Prince  wrote:

> +1
>
> On Wed, Nov 29, 2017 at 2:34 PM, John Trowbridge  wrote:
>
>> I would like to propose Ronelle be given +2 for the above repos. She has
>> been a solid contributor to tripleo-quickstart and extras almost since the
>> beginning. She has solid review numbers, but more importantly has always
>> done quality reviews. She also has been working in the very intense rover
>> role on the CI squad in the past CI sprint, and has done very well in that
>> role.
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Demystifying the kolla-kubernetes gate

[Matt Young]

Is there an invite for this?  I'm interested.

On Apr 19, 2017 1:20 PM, "Steven Dake (stdake)"  wrote:

Hey folks,



I am holding a workshop on how the kolla-kubernetes gate operates.  If you
are interested in this workshop, please sign up here:



http://doodle.com/poll/bee7umevf43nwi6y



Regards,

-steve



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev