(orOr: migrate networks to new physical network)
Jira | ||||||
---|---|---|---|---|---|---|
|
...
During migration of a network the UUID of objects are swapped so that external system (like NuageVsp) will perceive the migration as a delete of the network on the old physical network followed by a reimplement on the new physical network. Because of this, orchestration systems can still use the same UUID's as before (the resulted objects in CloudStack will have the same UUID's except for the VR.).
Make a temporary copy of the network before migration to keep the implementation details (moving along VR and nics).
Implement original network on new Physical network using guest network guru, found by looking up the tag of the offering
Implement services (Dhcp, static nat, source nat, …)
Deploy VR if needed
Migrate vnics to new physical network (move them back from the copy to the original network that is upgraded now)
Prepare Nic on Guru (add vport, vm interface, vm)
Prepare Nic on Element (apply acl rules, …)
Send ReplugNicCommand to host
Remove nic on native element and guru
Shutdown network services on old physical network (for this the copy object is used)
Undeploy VR if needed
Shutdown network infrastructure on old physical network
Delete original network
During migration of a network the UUID of objects are swapped so that external system (like NuageVsp) will perceive the migration as a delete of the network on the old physical network followed by a reimplement on the new physical network. Because of this, orchestration systems can still use the same UUID's as before (the resulted objects in CloudStack will have the same UUID's except for the VR.).
Make copy of original VPC Implement and implement VPC on new Physical network using guest network guru, found by looking up the tag of the network offerings
Migrate Tiers to newly created VPC in the new Physical Network (same pattern as migrate network happens for every tier.)
Make copy of original network (moving along VR and nics)
Implement Re-implement original network on new Physical network using guest network guru
Implement services (Dhcp, static nat, source nat, …)
Deploy VR if needed
Migrate vnics to new physical network
Prepare Nic on Guru (add vport, vm interface, vm)
Prepare Nic on Element (apply acl rules, …)
Send ReplugNicCommand to host
Release nic on native element and guru
Shutdown network services on old physical network
Undeploy VR if needed
Shutdown network infrastructure on old physical network
Delete original network
Shutdown (original) vpc on in old physical network
Delete original vpc
...
The resume logic follows below table :
resume parameter value \ Network migration "state" | Good | Bad (but error resolved) |
False (default) | Success | Fail (again) |
True | Success | >> Success << |
Based on the resume parameter and the related field in the networks table, we “force” migration of a network even if the network offering of the network is already the same as the current network offering. In that case, we will use the network that is stored in the related field (DB table) as the already generated copy. Otherwise we follow the normal migration procedure.
...