Difference between revisions of "Meetings/Neutron-Upgrades-Subteam"
< Meetings
(→Open discussion) |
|||
Line 20: | Line 20: | ||
== Open discussion == | == Open discussion == | ||
+ | * memory consumption concerns around OVO | ||
== Backlog == | == Backlog == |
Revision as of 15:02, 6 February 2017
Contents
Meetings
- Weekly on Mon at 1500 UTC
- IRC channel:
#openstack-meeting-alt
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
- Partial Multinode Grenade (assert:supports-rolling-upgrade)
- Object implementation
- Other patches on review
- Open discussion
Open discussion
- memory consumption concerns around OVO
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:
- 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/