[openstack-dev] [networking-sfc] PTG notes

Cathy Zhang Cathy.H.Zhang at huawei.com
Tue Feb 28 19:21:39 UTC 2017

Hi Bernard,

Thanks for the notes! I just talked with Louis. We will pull the stable branch for networking-sfc today. 
I hope after the branch is pulled, everyone can help doing more testing on the stable branch to make it more stable:-)


-----Original Message-----
From: Bernard Cafarelli [mailto:bcafarel at redhat.com] 
Sent: Tuesday, February 28, 2017 7:04 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [networking-sfc] PTG notes


I will miss the next two IRC meetings, so here is a quick summary email of PTG topics of interest for networking-sfc in the Pike cycle.

* Release, stable branching, stadium requirements For Ocata, neutron-lib patches are waiting for our stable branch creation (should be OK today?). The release itself is not as urgent, so we can still run some tests after merging the last open feature [0], and before tagging the release For Pike, stadium projects will synchronize releases with neutron [1] Except from more generic requirements, no new specific requirements to expect in this cycle

* Tempest tests
Two interesting items here:
 * Split tempest plugin repositories [2]: if agreed we will move the tempest plugin in a separate branchless repository (and proper configuration depending on features)
 * Refactor of tempest scenario base classes [3]: we will probably have to keep our copy of manager.py, and update to new API when it is ready

* Python 3.5 support
This is a project-wide goal for Pike, we have python3 unit tests already, but we should add a tempest/python3 check, and make it work (without forgetting the currently buggy multinode check)

* neutron-lib hacking checks
These are additional PEP8 checks we should enable as a neutron-lib consumer project. Some changes are underway [4], but we should enable these in networking-sfc

* API updates
Changes need to be advertised via a new extension (SFC graphs current review)

* Push notifications
This is in progress for Neutron [5], but can be nice for stadium projects too

* Common classifier
This probably deserves its separate topic, but we had an interesting session (possible consumers: networking-bpvpn, networking-sfc, FWaaS, QoS, Tap-as-a-Service, …) [6]

The completed neutron etherpad is at [7], with Kevin's nice summary at [8] I leave it to other PTG attendees to correct/extend this list!

[0] https://review.openstack.org/#/c/420339/
[1] https://review.openstack.org/#/c/437699/
[2] https://etherpad.openstack.org/p/qa-ptg-pike-tempest-plugins
[3] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112938.html
[4] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112988.html
[5] https://blueprints.launchpad.net/neutron/+spec/push-notifications
[6] https://review.openstack.org/#/c/333993/
[7] https://etherpad.openstack.org/p/neutron-ptg-pike-final
[8] http://lists.openstack.org/pipermail/openstack-dev/2017-February/113032.html

Bernard Cafarelli

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list