Jump to: navigation, search

Difference between revisions of "Meetings/Neutron-Upgrades-Subteam"

(16 intermediate revisions by 6 users not shown)
Line 4: Line 4:
* Weekly on Mon at 1500 UTC
* Weekly on Mon at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> on [https://freenode.net/ freenode]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> on [https://freenode.net/ freenode]
* Chair: Ihar Hrachyshka (ihrachys)
* Chair: Lujin Luo (lujinluo)
* Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/neutron_upgrades
* Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/neutron_upgrades
Line 10: Line 10:
* Apologies for Absence
* Announcements
* Announcements
** catch-all bug for OVO work created: https://bugs.launchpad.net/neutron/+bug/1541928
** Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
* March code sprint
* Linuxbridge multinode grenade job:
** Sprint in Europe to speed up the adoption of OVO: March 14-16, Brno, Czech Republic, Red Hat office.
** http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=8&fullscreen
*** etherpad with details: https://etherpad.openstack.org/p/code-sprint-neutron-objects-brno
* Mixed server versions: https://governance.openstack.org/tc/reference/tags/assert_supports-zero-downtime-upgrade.html
*** report: http://lists.openstack.org/pipermail/openstack-dev/2016-March/089769.html
** Implementation progress
*** ML: http://lists.openstack.org/pipermail/openstack-dev/2016-January/085328.html
*** Online data migration framework: https://review.openstack.org/#/c/432494/
* Partial Multinode Grenade (assert:supports-rolling-upgrade)
*** /extensions/ exposure during upgrade: https://review.openstack.org/#/c/451993/
** email thread: http://lists.openstack.org/pipermail/openstack-dev/2015-November/079344.html
** Gating
** first experimental results: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080503.html
** LP bug: https://bugs.launchpad.net/neutron/+bug/1527675
* Object implementation
* Object implementation
** '''All patches tracked under 'ovo' topic:''' https://review.openstack.org/#/q/topic:ovo
** LIKE support: https://review.openstack.org/#/c/419152/
** Ongoing work:
** other patches: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db
*** (rossella_s) allowed address pairs extension ported to OVO https://review.openstack.org/#/c/268274/
*** (rossella_s) WIP Port patch https://review.openstack.org/#/c/253641/ tests are passing, more extensions need to be ported, see backlog
*** (korzen) WIP Subnet OVO: https://review.openstack.org/#/c/264273
*** (korzen) WIP Network OVO: https://review.openstack.org/#/c/269658
*** (slunkad) WIP Port securitygroup extension https://review.openstack.org/#/c/275664/
*** (electrocucaracha) WIP Flavor OVO https://review.openstack.org/#/c/306685
*** (jlibosva) Add standard attributes to OVO objects https://review.openstack.org/#/c/292829/
*** (dguitarbite) port security
*** (ihrachysk) Usage of SubnetPool OVO https://review.openstack.org/#/c/300056/
** Done patches:
*** (rossella_s) handle synthetic fields in a general way: https://review.openstack.org/#/c/283711/
*** (korzen) IPv6 mode field: https://review.openstack.org/273517
*** (korzen) support for composite primary keys: https://review.openstack.org/275790
*** (mhickey) Port Extra Dhcp Opt to OVO: https://review.openstack.org/#/c/273072/
*** (electrocucaracha) SubnetPool OVO: https://review.openstack.org/#/c/275789/
*** (hdaniel) rbac metaclass for objects: https://review.openstack.org/#/c/250081/
*** (saisriki) IP address Custom types in Sqlalchemy for Neutron DB https://review.openstack.org/#/c/277558/
*** (korzen) CIDR custom type in Sqlachemy: https://review.openstack.org/#/c/285349
*** (saisriki) MACAddress custom type in Sqlalchemy: https://review.openstack.org/#/c/286347
*** https://review.openstack.org/#/c/281850 Create a hook in base object to modify the fields before DB operations (korzen)
* Other patches on review
* Other patches on review
** https://review.openstack.org/#/c/270309/  Update Neutron with temporary registry pattern from VersionedObjectRegistry (mhickey, depends on new o.vo release)
** https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron
** https://review.openstack.org/#/c/269056 Add Oslo Version serializer for RPC messages (korzen)
* Open discussion
** rpc callbacks rolling upgrade Part 1: https://review.openstack.org/265347 (ajo)
** rpc callbacks rolling upgrade Part 2: https://review.openstack.org/268040 (ajo)
== Open discussion ==
* Open discussion
** Start working on using the Neutron objects in code base
== Backlog ==
== Backlog ==

Latest revision as of 09:14, 29 June 2018



Open discussion



  • think of validating migration rules with real resources (there should be an oslo.db fixture for that);
  • investigate the list of resources we migrate in grenade, maybe add more;
  • job that runs expand from master, then leave the cloud on N-1 release and run tempest;
  • Introduce the custom SQL types in Neutron database schema

Meeting commands

/join #openstack-meeting-alt
#startmeeting neutron_upgrades
#topic Announcements
#undo topic
#link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam
#action ihrachys will get something specific done this week

Sub-team Charter

Enhances the upgrade story for Neutron (all things upgrade: cold, rolling, alembic, grenade, ...).

Object adoption check list

At the moment, the main focus of the team is on adoption of oslo.versionedobjects library for all database interactions. This is to open the door for alembic-less data migrations in next cycles.

To adopt the library for a resource, the following should be made: