Jump to: navigation, search

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

Line 77: Line 77:
 
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/

Revision as of 11:01, 16 May 2016

Meetings

Agenda



  • Open discussion
    • Start working on using the Neutron objects in code base

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: