- CLOUDSTACK-10024Getting issue details... STATUS
As a Cloud Owner
I want to migrate my existing guest networks to another physical network infrastructure
In order to make use of the extra features SDN provides.
Vmware
KVM
Isolated
VPC
Shared
Cloudstack supports multiple physical networks with guest traffic, but only when the guest traffic is given a tag. The network offering then also needs to specify the tag, so that the right physical network can be selected.
Cloudstack Core will be extended to support moving networks to another Physical Network, by adding API commands.
Migrating a network will keep the VM running on the same host, so there are no issues for multinic VM's, when you would migrate all networks one by one.
VR will be recreated. The new VR will get a new guest IP if it is no longer the gateway (target Network offering doesn’t specify VR as provider of source nat).
New VR will get the first free IP i.s.o. Gateway IP.
We will update the DB object with the details of the new implementation.
To be able to correctly cleanup the old implementation, we make a temporary copy of the network.
New API’s:
migrateNetwork
Parameter: networkId (UUID)
Parameter: networkOfferingId (UUID)
Parameter: resume (boolean)
migrateVpc
Parameter: vpcId (UUID)
Parameter: vpcOfferingId (UUID)
Parameter: tierNetworkOfferings[] (to defines the new network offering for each tier)
networkId
Parameter: resume (boolean)
The API implementation has to be as re-entrant as possible.
E.g. if 2 network objects are found in the db for the specified networkId (UUID), it will
By default indicate the error and fail
Unless “resume” is explicitly set to True, then try to resume as much as possible from the corrupt entry state.
Make a temporary copy of the network before migration to keep the implementation details(moving along VR and nics).
Implement 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
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.
Undeploy VR if needed
Shutdown network infrastructure on old physical network.
Delete original network
Make copy for original VPC.
Implement VPC on new Physical network using guest network guru,
Found by looking up the tag of the network offerings
Migrate Tiers
Make copy for original network (moving along VR and nics).
Implement 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 vpc on old physical network.
Delete original vpc
Provide Agent command to change the bridge of a nic in one call.
ReplugNicCommand
Allow both OVS and LinuxBridge on one host at the same time.
Currently only one VifProvider can be specified.
Given a VMware host setup, prepared for migration
And a physical network with VLAN encapsulation providing guest, management and storage networking
And a new physical network providing guest traffic tagged as “target”
And an isolated guest network in the VLAN physical network
And a network offering equivalent to the offering of the guest network tagged with “target”,
When I migrate the network using the target network offering
Then the network is configured on the new physical network
This can be refined to:
Note: US-1-3 and US-1-4 need persistent isolated network offering support with Nuage (upstream PR is available)
Given a VMware host setup
And a physical network with VLAN encapsulation providing guest, management and storage traffic
And a new physical network providing guest traffic tagged as “target”
And an isolated guest network in the VLAN physical network
And a network offering equivalent to the offering of the guest network tagged with “target”,
And 2 stopped vms in the guest network
When I migrate the network using the target network offering
Then the network is configured on the new physical network
And the VMs and their interfaces are configured on the new physical network
This can be refined to :
Given a VMware host setup
And a physical network with VLAN encapsulation providing guest, management and storage networking
And a new physical network with Guest Traffic tagged as “target”
And an isolated guest network in the VLAN physical network
And a network offering equivalent to the offering of the guest network with tag “target”
And 2 vms in the guest network
When I migrate the network using the target network offering
Then the network is configured on the new physical network
And the VMs and their interfaces are configured on the new physical network
And the VMs can reach each other
This can be refined to :