Jump to: navigation, search

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

m
 
(65 intermediate revisions by 10 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
 
−
** Ihar Hrachyshka: will be offline all the week
 
 
* Announcements
 
* Announcements
−
** upgrade tags added to governance repo: assert:supports-upgrade https://review.openstack.org/239771 assert:supports-rolling-upgrade: https://review.openstack.org/239778
+
** Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
−
* Organisational matters
+
* Linuxbridge multinode grenade job:
−
** Do we need a Launchpad tag?
+
** http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=8&fullscreen
−
* Partial Multinode Grenade
+
* Mixed server versions: https://governance.openstack.org/tc/reference/tags/assert_supports-zero-downtime-upgrade.html
−
** email thread: http://lists.openstack.org/pipermail/openstack-dev/2015-November/079344.html
+
** Implementation progress
−
** first experimental results: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080503.html
+
*** Online data migration framework: https://review.openstack.org/#/c/432494/
 +
*** /extensions/ exposure during upgrade: https://review.openstack.org/#/c/451993/
 +
** Gating
 
* Object implementation
 
* Object implementation
−
** Ihar talked to Armando on how we proceed with OVO adoption: no spec needed, RFE may not be needed; devref documenting conversion process is required; one or two objects to be chosen for Mitaka cycle
+
** LIKE support: https://review.openstack.org/#/c/419152/
−
** port (rossella) WIP patch https://review.openstack.org/#/c/253641/
+
** other patches: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db
−
** network (korzen)
+
* Other patches on review
−
* Patches on review
+
** https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron
−
** https://review.openstack.org/246242 adding assert:supports-upgrade tag to neutron (merged)
 
−
** https://review.openstack.org/245862 adding multinode grenade job to experimental (merged)
 
−
** https://review.openstack.org/241687 devref page on upgrades (merged)
 
−
** https://review.openstack.org/241154 devref update with the upgrade plan for RPC callbacks (ready to merge)
 
−
** https://review.openstack.org/248190 has_offline_migrations CLI for neutron-db-manage (WIP)
 
−
** https://review.openstack.org/#/c/253641/ port object (very WIP)
 
 
* Open discussion
 
* Open discussion
−
** [ihrachys] some attention in terms of data plane non-disruption on OVS agent restart (upgrade) is due for: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081264.html
+
 
 +
== Open discussion ==
 +
* <PUT YOUR TOPIC HERE>
 +
 
 +
== 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 ==
 
== Meeting commands ==
Line 47: Line 49:
 
Enhances the upgrade story for Neutron (all things upgrade: cold, rolling, alembic, grenade, ...).
 
Enhances the upgrade story for Neutron (all things upgrade: cold, rolling, alembic, grenade, ...).
  
−
= Bugs =
+
= Object adoption check list =
  
−
== Critical ==
+
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.
  
−
== High ==
+
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/

Latest revision as of 09:14, 29 June 2018

Meetings

Agenda

Open discussion

  • <PUT YOUR TOPIC HERE>

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
#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
#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:

Retrieved from "https://wiki.openstack.org/w/index.php?title=Meetings/Neutron-Upgrades-Subteam&oldid=162404"