Use target VIF information on Migration
Today, instances are migrated to the target without any knowledge about the networking setup on the target host.
But having this kind of information would solve the following issues:
#1 Migration with Neutron macvtap agent migrates on invalid target in some special configuration
#2 Migration between hosts that run different l2 agents (e.g. source runs lb agent, target runs ovs-agent). This could be used as transition strategy for l2 agents. Today Live Migration succeeds, but instance does not have l2 connectivity to its networks anymore.
--> having the target-vif information, nova could modify the domain.xml accordingly and such a migration would succeed.
#3 This also solves problems where an instance was stuck in error state on the migration target, as port_binding had failed.
--> having this information nova could trigger a portbinding for the target host and see if that fails. If so, the migration could be aborted in pre_live_migration and the instance would still be Active.
All requires a new API extension on the Neutron side which is discussed here [1]
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Andreas Scheuring
- Direction:
- Needs approval
- Assignee:
- Andreas Scheuring
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
