Cloudstack Isolation Network VM creation and VM communication

The following is the creation of an isolated guest network (not a network in VPC) in Cloudstack's advance Zone, and a VLAN id:305,vm template for Ubuntu 10.04,

Flow chart

The following figure is the main process for organizing the creation of VMS and VM communications.

See the flow chart, it should be generally clear what is going on, say some of their own summary, not necessarily correct, if you feel that there is disagreement, you can discuss

Problems and conclusions encountered in the verification process

1, because of each isolated guest network, there is a separate vrouter virtual machine to provide gateway services, different VLANs, can have the same subnet.

2. When a VM is created using the Quarantined guest network, a vrouter virtual machine is created for the network, and a VLAN interface is worn on the host where the Vrouter resides and the host where the new VM resides, as shown in the following illustration: (The system assigns VLAN id:305 to the network, and the isolation network is 192.1 68.1.1/24)

2.1 When you create a virtual machine in an isolated network, you first create the corresponding Vrouter VM for that network, and the Vrouter virtual machine corresponds to the following network card information:

[[Nic:public-10.41.2.233-vlan://untagged], [nic:guest-192.168.1.1-vlan://305], [Nic:control-169.254.3.76-null]]

2.2 Configure the MAC address and IP of the VM that will be created to the Vrouter virtual machine

Execute function:

Com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.execute (Dhcpentrycommand)

Execute the script dhcp_entry.sh, the final execution of the script is Vrouter virtual machine:/root/edithosts.sh (the script is mainly configured DHCP, this article does not explain)

2.3 Create VM, at this time carry the network card information: [nic:guest-192.168.1.113-vlan://305], but the IP is used, the virtual machine IP from the vrouter virtual machine get (according to the new VM MAC address get)