Jump to: navigation, search

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

(Backlog)
 
(39 intermediate revisions by 9 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
* Organisational matters
+
** Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
** Sprint in Europe to speed up the adoption of OVO?
+
* Linuxbridge multinode grenade job:
* Partial Multinode Grenade (assert:supports-rolling-upgrade)
+
** http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=8&fullscreen
** email thread: http://lists.openstack.org/pipermail/openstack-dev/2015-November/079344.html
+
* Mixed server versions: https://governance.openstack.org/tc/reference/tags/assert_supports-zero-downtime-upgrade.html
** first experimental results: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080503.html
+
** Implementation progress
** LP bug: https://bugs.launchpad.net/neutron/+bug/1527675
+
*** 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
** (rossella_s) allowed address pairs extension ported to OVO https://review.openstack.org/#/c/268274/
+
** LIKE support: https://review.openstack.org/#/c/419152/
** (rossella_s) WIP patch https://review.openstack.org/#/c/253641/ tests are passing, more extensions need to be ported, see backlog
+
** other patches: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db
** (korzen) WIP Subnet OVO: https://review.openstack.org/#/c/264273
+
* Other patches on review
** (korzen) WIP Network OVO: https://review.openstack.org/#/c/269658
+
** https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron
**(mhickey) Port Extra Dhcp Opt to OVO: https://review.openstack.org/#/c/273072/
 
** (dguitarbite) Port Security
 
** (rossella_s) handle synthetic fields in a general way
 
** (saisriki) take care of special DB fields like IPNetworkField the way Nova does, that is defining them like it's done in nova/db/sqlalchemy/types
 
* Patches on review
 
** https://review.openstack.org/241154 devref update with the upgrade plan for RPC callbacks (merged). Need to ask @ajo if there is code to review.
 
** https://review.openstack.org/#/c/253641/ port object (rossella, very WIP)
 
** 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/#/c/268274/ allowed address pais extension (rossella_s)
 
** https://review.openstack.org/#/c/268273/ Handle OVO that don't have ID as primary key (rossella_s)
 
** https://review.openstack.org/#/c/269056 Add Oslo Version serializer for RPC messages (korzen)
 
** https://review.openstack.org/#/c/273517 OVO common enum classes for IP version and IPv6 modes (korzen)
 
** https://review.openstack.org/#/c/273072/ Port Extra Dhcp Opt to OVO (mhickey)
 
 
* Open discussion
 
* Open discussion
** create an RFE bug for OVO work?
+
 
** data disruption issues with features that integrate with ovs agent on agent restart: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081264.html
+
== Open discussion ==
 +
* <PUT YOUR TOPIC HERE>
  
 
== Backlog ==
 
== Backlog ==
Line 44: Line 33:
 
* investigate the list of resources we migrate in grenade, maybe add more;
 
* 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;
 
* job that runs expand from master, then leave the cloud on N-1 release and run tempest;
* (korzen) SubnetPool OVO can be taken out of Subnet OVO patch - https://review.openstack.org/#/c/264273/10/neutron/objects/subnet.py
+
* Introduce the custom SQL types in Neutron database schema
* (korzen) Add support for multiple primary key support in base OVO
 
* for the port object we still need the following extensions: security groups. An example of porting an extension https://review.openstack.org/#/c/268274/
 
* create an hook to modify the object field before writing in the DB (see https://review.openstack.org/#/c/264273 )
 
  
 
== Meeting commands ==
 
== Meeting commands ==
Line 63: 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: