Jump to: navigation, search

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

Line 12: Line 12:
 
* Apologies for Absence
 
* Apologies for Absence
 
* Announcements
 
* Announcements
** upgrade tags added to governance repo: assert:supports-upgrade https://review.openstack.org/239771 assert:supports-rolling-upgrade: https://review.openstack.org/239778
 
 
* Organisational matters
 
* Organisational matters
** Do we need a Launchpad tag?
 
 
* Partial Multinode Grenade (assert:supports-rolling-upgrade)
 
* Partial Multinode Grenade (assert:supports-rolling-upgrade)
 
** email thread: http://lists.openstack.org/pipermail/openstack-dev/2015-November/079344.html
 
** email thread: http://lists.openstack.org/pipermail/openstack-dev/2015-November/079344.html
 
** first experimental results: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080503.html
 
** first experimental results: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080503.html
** how do we collect new results?
+
** LP bug: https://bugs.launchpad.net/neutron/+bug/1527675
 
* Object implementation
 
* Object implementation
** Ihar talked to Armando on how we proceed with OVO adoption: no spec needed, RFE may not be needed; devref documenting conversion process is required; one or two objects to be chosen for Mitaka cycle
 
 
** port (rossella) WIP patch https://review.openstack.org/#/c/253641/
 
** port (rossella) WIP patch https://review.openstack.org/#/c/253641/
** network (korzen)
+
** network (korzen): too complex subtree to unravel; we need the tree documented to move the ball
** we will need to add a hasher validator for object registry to make sure we don't introduce unintended changes that affect objects (ihrachys)
 
 
* Patches on review
 
* 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/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/248190 has_offline_migrations CLI for neutron-db-manage (WIP)
+
** https://review.openstack.org/248190 has_offline_migrations CLI for neutron-db-manage (mhickey, WIP)
** https://review.openstack.org/#/c/253641/ port object (very WIP)
+
** https://review.openstack.org/#/c/253641/ port object (rossella, very WIP)
 +
** https://review.openstack.org/258026 versioned objects hasher test (mhickey)
 
* Open discussion
 
* Open discussion
** [ihrachys] some attention in terms of data plane non-disruption on OVS agent restart (upgrade) is due for: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081264.html
+
** data disruption issues with features that integrate with ovs agent on agent restart: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081264.html
 +
 
 +
== 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;
  
 
== Meeting commands ==
 
== Meeting commands ==

Revision as of 10:43, 21 December 2015

Meetings

Agenda

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;

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, ...).

Bugs

Critical

High