Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Div
classtocc

Table of Contents

...

  • The configuration may include a network interface in any of the Abiquo networks
    • From Abiquo 3.2: In VM configuration on the Network tab, the user can create a new IP address in a private network
    • The user can request an automatically generated IP address, to create a network interface
    • The user can select an existing IP address to create a network interface
    • For each network interface, Abiquo assigns a unique MAC address
      • For public networks, the MAC is generated when the NIC is purchased by the virtual datacenter
      • For external networks, the MAC is generated when the NIC is assigned to the virtual machine
      • For IPv6 networks, the MAC is used to generate the IP address
    • The MAC address is included in network configuration that is sent to the hypervisor

Deploying a VM

When the VM is deployed to a hypervisor

  • If the user did not create a NIC, then Abiquo configures one in the default network (if it is private, custom private, external or public)
  • The Abiquo Server sends the network configuration to the DHCP Server as a DHCP lease
    • The IP address is the one assigned when the VM was configured (by the user or Abiquo)
    • The MAC address was assigned by Abiquo when the VM was configured
    • The lease may include other information, e.g. one-time API key for Chef configuration
    • The IP addresses assigned by the DHCP server are static
  • If the VM is the first in the network
    • If it is a private network
      • Schedule resources and automatically select the VLAN tag (see below)
    • Else
      • Schedule resources using the VLAN tag reserved by the user at creation 
    • Create a new VLAN for this network
      • in ESX, create a port group for the VLAN
      • in KVM, create a virtual bridge for the VLAN
  • Otherwise, attach the NIC to an existing port group/virtual bridge, etc.

...

  1. It broadcasts a request for network configuration using DHCP
  2. The hypervisor passes the request over the service network
    • The service network is a trunk connection between hypervisors and DHCP for VLAN networks
    • If you are using a DHCP Relay Server
      • the relay forwards the request to the DHCP Server
    • Otherwise
      • the DHCP Server receives the request directly
  3. The DHCP Server sends a lease to the service network 
    • If you are using a DHCP Relay
      • the relay forwards the request to the VM
    • Otherwise
      • the VM receives the request directly over the service network
  4. The VM can now use its network configuration

...