provide easy v2 -> ml2 transition
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-midonet |
Fix Released
|
Critical
|
YAMAMOTO Takashi |
Bug Description
there should be an easy way to migrate from v2 to ml2.
eg. a script
incase we want to do something similar with what neutron did for
ovs/lb, [1]
at least we need to fill the following tables:
ml2_port_
ml2_port_bindings
ml2_distributed
from:
midonet_
portbindingports
and:
networksegments
from:
midonet_
probably it can be done in two steps.
1. make the monolithic plugin use ml2-compatible schema. i guess it can be done via usual contract migrations. probably we need to make it use OVO, or use ml2 code directly. otherwise ml2 schema changes will break our plugin.
2. have a script to do the rest of migration if any. i guess none.
random concerns:
- the relevant ml2 schema is not entirely stable. there're planned schema changes like distributed port binding stuff.
- ml2 doesn't use OVO yet.
- probably we need a way to control the order to execute migration scripts.
- how long should we allow users to switch?
Changed in networking-midonet: | |
importance: | Undecided → High |
description: | updated |
description: | updated |
description: | updated |
Changed in networking-midonet: | |
importance: | High → Critical |
Changed in networking-midonet: | |
assignee: | nobody → YAMAMOTO Takashi (yamamoto) |
milestone: | none → 5.0.0 |
status: | New → In Progress |
maybe we can do something similar with what neutron did for ovs/lb. /github. com/openstack/ neutron/ blob/11c0900dea 4d4e691c0c68cd7 b0c9cff656ce7a2 /neutron/ db/migration/ migrate_ to_ml2. py
https:/