Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1692133
Title:
FWaaS - clear migration between v1 and v2
Status in neutron:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1692133/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
