FWaaS - clear migration between v1 and v2

Bug #1692133 reported by Kevin Benton
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
New
Undecided
Unassigned

Bug Description

This is to track the migration work between v1 and v2. Several concerns were brought up in the summit session about a hard forced switch: https://etherpad.openstack.org/p/neutron-boston-painpoints

So we need to either run v1 concurrently with v2, provide a migration, or just have a shim that translates v1 into v2 calls.

Tags: fwaas
tags: added: fwaas
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.