[RFE] Implement migration from iptables-based security groups to ovsfw
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
When switching an ovs-agent from iptables to ovsfw, new instances will be created using the ovsfw, but old instances will stick with iptables. In fact, there isn't a way to migrate an instance from iptables to ovsfw, and one should be provided.
Considerations:
a. It isn't enough to just remove the qvo/qvb/qbr interfaces and then attach the tap device directly to the integration bridge - we should also change the domain xml of the instance itself, so that when migrating an instance from one compute node to the other, nova won't depend on non-existent devices. Should this be done in Nova or in Neutron? Should Nova be notified?
b. On Neutron side, we should also change the Port table to indicate a change. This might require a new RPC call from the agent side.
| tags: | added: ovs-fw rfe |
| summary: |
- Implement migration from iptables-based security groups to ovsfw + [RFE] Implement migration from iptables-based security groups to ovsfw |
| Changed in neutron: | |
| assignee: | nobody → John Schwarz (jschwarz) |
| status: | New → In Progress |
| Changed in neutron: | |
| assignee: | John Schwarz (jschwarz) → nobody |
| Changed in neutron: | |
| status: | In Progress → Incomplete |
| importance: | Undecided → Wishlist |
| Kevin Benton (kevinbenton) wrote auto-abandon-script | #1 |
| Changed in neutron: | |
| status: | Incomplete → New |
| tags: | added: timeout-abandon |
| OpenStack Infra (hudson-openstack) wrote Change abandoned on neutron (master) | #2 |
| Armando Migliaccio (armando-migliaccio) wrote | #3 |
| Changed in neutron: | |
| status: | New → Incomplete |
| status: | Incomplete → Triaged |
| Kevin Benton (kevinbenton) wrote | #4 |
| tags: |
added: rfe-postponed removed: rfe timeout-abandon |
| Kevin Benton (kevinbenton) wrote | #5 |
This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.