Jump to: navigation, search

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

(Agenda)
(Agenda)
Line 10: Line 10:
  
  
* Apologies for Absence
 
 
* Announcements
 
* Announcements
** catch-all bug for OVO work created: https://bugs.launchpad.net/neutron/+bug/1541928
 
* March code sprint
 
** Sprint in Europe to speed up the adoption of OVO: March 14-16, Brno, Czech Republic, Red Hat office.
 
*** etherpad with details: https://etherpad.openstack.org/p/code-sprint-neutron-objects-brno
 
*** report: http://lists.openstack.org/pipermail/openstack-dev/2016-March/089769.html
 
*** ML: http://lists.openstack.org/pipermail/openstack-dev/2016-January/085328.html
 
 
* 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
 
** first experimental results: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080503.html
 
** LP bug: https://bugs.launchpad.net/neutron/+bug/1527675
 
 
* Object implementation
 
* Object implementation
** '''All patches tracked under 'ovo' topic:''' https://review.openstack.org/#/q/topic:ovo
 
** Ongoing work:
 
*** (rossella_s) WIP Port patch https://review.openstack.org/#/c/253641/ tests are passing, more extensions need to be ported, see backlog
 
*** (korzen) WIP Network OVO: https://review.openstack.org/#/c/269658
 
*** (slunkad) WIP Port securitygroup extension https://review.openstack.org/#/c/275664/
 
*** (electrocucaracha) WIP Flavor OVO https://review.openstack.org/#/c/306685
 
*** (dguitarbite) port security
 
*** (ihrachysk) Usage of SubnetPool OVO https://review.openstack.org/#/c/300056/
 
** Done patches:
 
*** (korzen) WIP Subnet OVO: https://review.openstack.org/#/c/264273
 
*** (jlibosva) Add standard attributes to OVO objects https://review.openstack.org/#/c/292829/
 
*** (rossella_s) allowed address pairs extension ported to OVO https://review.openstack.org/#/c/268274/
 
*** (rossella_s) handle synthetic fields in a general way: https://review.openstack.org/#/c/283711/
 
*** (korzen) IPv6 mode field: https://review.openstack.org/273517
 
*** (korzen) support for composite primary keys: https://review.openstack.org/275790
 
*** (mhickey) Port Extra Dhcp Opt to OVO: https://review.openstack.org/#/c/273072/
 
*** (electrocucaracha) SubnetPool OVO: https://review.openstack.org/#/c/275789/
 
*** (hdaniel) rbac metaclass for objects: https://review.openstack.org/#/c/250081/
 
*** (saisriki) IP address Custom types in Sqlalchemy for Neutron DB https://review.openstack.org/#/c/277558/
 
*** (korzen) CIDR custom type in Sqlachemy: https://review.openstack.org/#/c/285349
 
*** (saisriki) MACAddress custom type in Sqlalchemy: https://review.openstack.org/#/c/286347
 
*** https://review.openstack.org/#/c/281850 Create a hook in base object to modify the fields before DB operations (korzen)
 
 
 
 
* Other patches on review
 
* Other patches on review
** https://review.openstack.org/#/c/270309/  Update Neutron with temporary registry pattern from VersionedObjectRegistry (mhickey, depends on new o.vo release)
 
** https://review.openstack.org/#/c/269056 Add Oslo Version serializer for RPC messages (korzen)
 
** rpc callbacks rolling upgrade Part 1: https://review.openstack.org/265347 (ajo)
 
** rpc callbacks rolling upgrade Part 2: https://review.openstack.org/268040 (ajo)
 
 
 
 
* Open discussion
 
* Open discussion
** Start working on using the Neutron objects in code base
 
  
 
== Backlog ==
 
== Backlog ==
* complete the sec group extensions object https://review.openstack.org/284738
 
* complete the port object https://review.openstack.org/253641
 
 
* think of validating migration rules with real resources (there should be an oslo.db fixture for that);
 
* 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;
 
* investigate the list of resources we migrate in grenade, maybe add more;

Revision as of 13:19, 20 June 2016

Meetings

Agenda

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

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: