Difference between revisions of "Meetings/Neutron-Upgrades-Subteam"
< Meetings
(→Agenda) |
|||
| (23 intermediate revisions by 7 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: | + | * 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: | ||
| − | |||
* Announcements | * Announcements | ||
| − | ** | + | ** Rocky release schedule: https://releases.openstack.org/rocky/schedule.html |
| − | + | * Linuxbridge multinode grenade job: | |
| − | * | + | ** http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=8&fullscreen |
| − | ** | + | * Mixed server versions: https://governance.openstack.org/tc/reference/tags/assert_supports-zero-downtime-upgrade.html |
| − | * | + | ** Implementation progress |
| − | * | + | *** 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 | ||
| − | ** | + | ** LIKE support: https://review.openstack.org/#/c/419152/ |
| − | + | ** other patches: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db | |
| − | ** | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* Other patches on review | * Other patches on review | ||
| − | ** https://review.openstack.org/#/ | + | ** https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron |
| − | + | * Open discussion | |
| − | |||
| − | |||
| − | * | ||
| − | + | == Open discussion == | |
| − | * | + | * <PUT YOUR TOPIC HERE> |
== Backlog == | == Backlog == | ||
| Line 50: | 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; | ||
| + | * Introduce the custom SQL types in Neutron database schema | ||
== Meeting commands == | == Meeting commands == | ||
| Line 65: | 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, ...). | ||
| − | = | + | = 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/ | ||
Latest revision as of 09:14, 29 June 2018
Contents
Meetings
- Weekly on Mon at 1500 UTC
- IRC channel:
#openstack-meeting-alton freenode - Chair: Lujin Luo (lujinluo)
- Meetings, with their notes and logs, will be found under http://eavesdrop.openstack.org/meetings/neutron_upgrades
Agenda
- Announcements
- Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
- Linuxbridge multinode grenade job:
- Mixed server versions: https://governance.openstack.org/tc/reference/tags/assert_supports-zero-downtime-upgrade.html
- Implementation progress
- Online data migration framework: https://review.openstack.org/#/c/432494/
- /extensions/ exposure during upgrade: https://review.openstack.org/#/c/451993/
- Gating
- Implementation progress
- Object implementation
- Other patches on review
- Open discussion
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:
- 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/
