Note that neither the controller node nor the compute nodes routes traffic through the provider network, only nested VMs do.Īccording to OpenStack’s installation guide, each node is configured with a static IP address on the management network. Nested VMs bridge onto the latter NIC to gain link-layer connectivity to the provider network. One is connected to the management network while the other to the provider network. To provide internet access to the nested VMs, we need additionally a provider network. The management network provides internet access to the controller and compute nodes. The controller and compute nodes communicates through the management network, through which the controller node sends the VM image to a chosen compute node and configures several running parameters. Since my controller and compute node are all Hyper-V VMs, the VMs running inside the compute node are thus nested VMs. The minimum setup of OpenStack cluster is comprised of one controller node and one or more compute nodes. The creation and deletion of VMs are achieved by interacting with the controller node. OpenStack is a platform that allows one to spawn VMs inside a set of compute nodes. I am recently working on deploying OpenStack in a virtualized environment hosted by Hyper-V. TL DR: Enable MAC address spoofing in Hyper-V manager network adapter settings if nested VMs are bridged onto that NIC.
0 Comments
Leave a Reply. |