Page Comparison

...

...

...

...

...

...

...

When you create a network in private cloud

• If it is a private network, it is created in a virtual datacenter context
  Prior to Abiquo 3.2: IP and MAC addresses are generated for the network
  
  • If it is an IPv4 address
    
    • The gateway address is automatically created
    • The VLAN tag is not allocated until the first VM is deployed
      
      • It will be allocated from the rack's VLAN range that should be already configured in the switch or network management system
• If it is an external, public, or unmanaged network, it is created in a datacenter context
  
  • You enter a VLAN tag
    
    • This VLAN tag should be already configured in the switch or network management system
    • It should not be outside in the range of VLANs that the rack 's VLAN rangewill use for private networks
    • For external and public networks, the VLAN tag must be configured in DHCP
• From Abiquo 3.2: You can create an IP address or a network address range of addresses by entering the first address and the number of addresses to create
• The IPs in the network are added to the internal IP pool
  
  • For external or public network
    
    • IPs are marked as available/not available in the internal IP pool
  • For private network
    
    • All IPs are marked as available

...

• 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 or public 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 publicnot unmanaged)
• 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 when creating the network
  • 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.

Powering On a VM when using DCHP

When a VM is powered on

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

See Configuring DHCP and DHCP Troubleshooting

...

Abiquo automatically allocates private VLANs as part of the resource scheduling process. See VLAN Allocation

DHCP Options

Built-in DHCP Server

The Abiquo platform includes a built-in DHCP Server as part of the Remote Services. A DHCP Server should be used by only one datacenter. The built-in DHCP Server usually only serves leases to machines created in Abiquo, so it should not affect the rest of your infrastructure. However, as a security measure Abiquo recommends that you configure your firewall to filter the traffic from this server outside of the cloud environment, and vice versa.

DHCP Relay Server 

The use of a DHCP Relay Server is recommended and it is essential if more than 200 virtual machines will be deployed on Abiquo managed networks. If more than 1000 virtual machines will be deployed, a hierarchy of DHCP Relay Servers must be used. Abiquo provides a DHCP Relay Server configuration but the Network Administrator may replace this configuration with another solution that manages VLANs.