changed 6 years ago  
Linked with GitHub

Shanghai 2019 PTG notes

Below is the list of sessions attended and summary and action items.

Next steps for policy in OpenStack

Etherpad: https://etherpad.openstack.org/p/PVG-keystone-forum-policy

Keystone has introduced three roles(Admin, member and reader) to handle policies.
Nova team has already started working on that.
Tempest patches are already up for testing policies changes.
The upstream QA team is going to work on patrole tempest plugin to test there also.
It is going to be a big change in all openstack services.
If an openstack services has already completed policy in code changes, Then they can go ahead and make changes in api.
A pop up team is formed in order to work with various openstack team. Notes are on etherpad.

Action Items:

  • How we can leverage these policies changes in TripleO side so that we donot break backward compatibilty. May be a
    config change somewhere will help it? Proposing a Blueprint might help to discuss the scope?
  • Enabling patrole tempest plugin in Tripleo CI to test.

Swift Operator Feedback

Etherpad: https://etherpad.openstack.org/p/PVG-swift-ops-feedback

Since swift codebase ported to Python3 very late due to lots of cpython bugs.
Operators are moving to Python3 swift by Dec, 2019.

Food for thought:

  • Having a upgrade job from RHEL-7.x running queens to RHEL-8.x running train with python2.7 swift and other services on Python3
    and then upgrade to python3 swift might help to find out py2 and py3 related upgrade issues.

Ceph Rook workshop

Attended this workshop, it was good.
Github Repo: https://github.com/packet-labs/Rook-on-Bare-Metal-Workshop

OpenStack QA PTG

Etherpad:

Upcoming work:

  • Migrate all projects from .testr.conf to .stestr.conf
  • Improving RBAC testing including keystone system scope changes in Patrole
  • Drop Python2.7 support from QA
  • Introduce new glance tempest tests
  • Adoption of whitebox tempest plugin
  • Improving tempest cleanup
  • Restarting Bug traige and reviews
  • Scenario manager stable interface

Action Items from TripleO/Tempest side:

  • Needs help on getting feedback on tempest reviews add it to QA office hour etherpad: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
  • Need to focus some time on traiging and fixing upstream bugs as a part of sprint work
  • Tripleo CI will be not getting affected as Master and train will be running on CentOS 8 by Feb 2020
  • Introduce patrole testing plugin in TripleO CI
  • Enabling IPv6 tempest tests coverage in TripleO CI
  • Enabling whitebox tempest plugin in TripleO CI
  • Remove tripleo common tempest plugin as it is already deprecated.
  • Take a look at component CI skip list implemented in upstream

OpenInfra PTG

Etherpad:

Interesting Discussions:

  • Podman as replacement for docker?
  • Running nodepool-builder with ansible and/or docker
    • may be using buildah manifest with disk image builder for making dib usage easier
  • Making zuul-jobs roles platform agnostics
    • follow the os_tempest model for the same
  • Zuul Jobs and Ansible roles to deal with rpm packaging
  • logreduce integration
  • Discussions around testing config changes via keeping something between config and untrusted repo

Action Items:

  • Moving mock, rpm related roles to zuul-jobs from https://pagure.io/zuul-distro-jobs
    • if things work well, then Zuul upstream docs will introduce a section to highlight third party zuul jobs roles
  • Add a post playbook to test logreduce in upstream jobs as a POC
  • Make changes in RDO gerrit config in order to not run trigger zuul jobs again if there is an update in commit message
  • work with infra team to deploy codimd (open source version of hackmd)

Tripleo CI and OpenStack-ansible

Etherpad: https://etherpad.openstack.org/p/tripleo-ptg-ussuri

Discussions and Action Items

  • Improving octavia testing in TripleO CI
    • Add support for octavia tempest plugin in os_tempest
    • Add third party check jobs for octavia upstream repo with octavia tempest tests
  • Collect-logs integration in openstack-ansible project

Zuul Distro Jobs

I have an interesting discussion with migi during the PTG on how we can work towards consolidating the work around testing openstack packages in the CI jobs.
In TripleO CI, we have built-test-packages[https://opendev.org/openstack/tripleo-quickstart-extras/src/branch/master/roles/build-test-packages] role to built
rpm for each of the OpenStack projects by parsing commit message as well as including depends-on projects.
In Downstream, we have patch-component [https://github.com/rhos-infra/patch-components] ansible role which builds the rpm from downstream patches and inject it
into the infrared Jobs.
One of the thing we found use of zuul-distro-jobs (https://pagure.io/zuul-distro-jobs/blob/master/f/roles) and tripleo CI is also evaluating this role and reuse
in CI for packaging and testing rpm in CI.

Action Items:

  • Document how downstream and upstream patches or gerrit review/depends-on rpm got build in CI
    • find the common ground and work towards reusing on role to solve all the packaging related tasks using zuul-distro-jobs.

Sharing tempest skip list for each release

In os_tempest side, we follow a schema to maintain the skip list [https://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/defaults/main.yml#L103] and in TripleO CI, we have skip list for each release [https://opendev.org/openstack/tripleo-quickstart-extras/src/branch/master/roles/validate-tempest/vars] and these skip lists are periodically updated based on the result of fs021 job where skip list is used as a whitelist.

Discussion

  • Might be we can share the same skip list for upstream and downstream for each osp release so that we have clear idea what is broken or not supported.
    • It depends on os_tempest adoption in infrared jobs.
Select a repo