Jump to: navigation, search

Meetings/Neutron-Upgrades-Subteam

< Meetings
Revision as of 17:46, 8 August 2016 by Dasm (talk | contribs) (Added Open Discussion topic.)

Meetings

Agenda

  • Announcements
  • Partial Multinode Grenade (assert:supports-rolling-upgrade)
  • Object implementation
  • Other patches on review
  • Open discussion

Open discussion

  • OVO Subteam Organization:
    • Discuss about certain format for Commit Message to avoid potential overlapping work, like: "Introduce OVO *item*; Refactor *item* DB Model, etc..."

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: