Meetings/Neutron-Upgrades-Subteam

= Meetings =


 * Weekly on Mon at 1500 UTC
 * IRC channel:  on freenode
 * Chair: Ihar Hrachyshka (ihrachys)
 * Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/neutron_upgrades

= Agenda =


 * Announcements
 * Pike release schedule: https://releases.openstack.org/pike/schedule.html
 * Linuxbridge multinode grenade job:
 * http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=8&fullscreen
 * Mixed server versions: https://governance.openstack.org/tc/reference/tags/assert_supports-zero-downtime-upgrade.html
 * Implementation progress
 * Online data migration framework: https://review.openstack.org/#/c/432494/
 * /extensions/ exposure during upgrade: https://review.openstack.org/#/c/451993/
 * Gating
 * Object implementation
 * LIKE support: https://review.openstack.org/#/c/419152/
 * other patches: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db
 * Other patches on review
 * https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron
 * Open discussion

Open discussion

 * 

Backlog

 * 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


 * 1) startmeeting neutron_upgrades


 * 1) topic Announcements


 * 1) undo topic


 * 1) link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam


 * 1) action ihrachys will get something specific done this week


 * 1) endmeeting

= 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:
 * the object itself is introduced in the tree: https://review.openstack.org/#/c/275789/
 * the object is adopted in all database code that currently uses SQLAlchemy models directly: https://review.openstack.org/#/c/300056/
 * if the resource supports sorting/pagination on API level, corresponding API tests should be added BEFORE database code is switched to its object: https://review.openstack.org/#/c/306272/