Jump to: navigation, search

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

m (Agenda)
(Agenda)
Line 16: Line 16:
 
** Sprint in Europe to speed up the adoption of OVO: March 14-16, Brno, Czech Republic, Red Hat office.
 
** 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
 
*** 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
 
*** 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)
Line 22: Line 23:
 
** LP bug: https://bugs.launchpad.net/neutron/+bug/1527675
 
** 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
 
** (rossella_s) allowed address pairs extension ported to OVO https://review.openstack.org/#/c/268274/  
 
** (rossella_s) allowed address pairs extension ported to OVO https://review.openstack.org/#/c/268274/  
 
** (rossella_s) WIP patch https://review.openstack.org/#/c/253641/ tests are passing, more extensions need to be ported, see backlog
 
** (rossella_s) WIP patch https://review.openstack.org/#/c/253641/ tests are passing, more extensions need to be ported, see backlog
Line 45: Line 47:
  
 
* Open discussion
 
* Open discussion
** how to move forward? Delay merges or create a branch for ovo work ?
 
  
 
== Backlog ==
 
== Backlog ==

Revision as of 14:56, 21 March 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;

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