Jump to: navigation, search

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

(Agenda)
Line 34: Line 34:
 
** (rossella_s) handle synthetic fields in a general way
 
** (rossella_s) handle synthetic fields in a general way
 
** (dguitarbite) port security
 
** (dguitarbite) port security
** (saisriki) take care of special DB fields like IPNetworkField the way Nova does, that is defining them like it's done in nova/db/sqlalchemy/types
+
** (saisriki) WIP for Custom types in Sqlalchemy for Neutron DB https://review.openstack.org/#/c/277558/
 
* 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/270309/  Update Neutron with temporary registry pattern from VersionedObjectRegistry (mhickey, depends on new o.vo release)

Revision as of 22:48, 8 February 2016

Meetings

Agenda

  • 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;
  • create an hook to modify the object field before writing in the DB (see https://review.openstack.org/#/c/264273 )

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