| Div | ||
|---|---|---|
| ||
Admin Guide 1. Abiquo: Network |
| Div | ||
|---|---|---|
| ||
|
...
This section describes the VLAN Network configuration for the Abiquo Platform.
Virtual Networking Scenario
...
The Abiquo service network is a VLAN network that includes the following virtual network types:
Private networks within the virtual datacenter
External networks belonging to enterprises that allow access to networks outside the virtual datacenter
Unmanaged networks belonging to enterprises that are assigned IP addresses outside the Abiquo environment
Public networks using public IP addresses for
...
VMs
...
VMs on internal private networks can only communicate within the virtual datacenter.
...
To communicate outside it, use a virtual gateway
...
. VMs on public, external and unmanaged networks can communicate outside the virtual datacenter.
...
...
How Abiquo
...
manages the
...
service network
Abiquo
...
can manage the service network
...
with standard networking or software defined networking (SDN) integrations.
In standard networking, Abiquo manages virtual networks as separate VLANs. The Network Administrator configures VLANs in the top-of-rack switches.
...
When the Cloud Admin creates racks, they enter the VLAN range for private networks on the rack.
For each external, public, and unmanaged network, the Network Administrator should assign VLAN tags and the Cloud Admin should enter them into Abiquo.
...
With SDN integrations, the cloud admin should enter the provider ID of the public network.
...
How Abiquo assigns IP addresses to VMs
When a user deploys a VM, Abiquo generates a unique MAC address and binds it to an IP from the appropriate subnet and assigns it to the appropriate VLAN
...
.
Abiquo can use the following options to assign the network:
ISC DHCP servers:
Abiquo remotely manages ISC DHCP Servers, so the DHCP server will always lease the right IP to the MAC address on a VM.
The Network
...
Administrator configures the DHCP
...
relay
...
server so that it
...
listens to
...
VLANs and can be reached over a network from the
...
VMs (on the service network) so they can obtain the IP leases
...
Abiquo recommends the use of a DHCP relay server to provide VLAN support. See Configuring DHCP in the Administrator's Guide for information about how Abiquo uses DHCP
...
Configuring the Service Network in the Switches
...
SDN integrations:
Abiquo will create private networks and assign IP addresses using the DHCP server of the SDN system
Guest setup:
Abiquo can inject the network connection into a VM using cloud-init or hypervisor tools, which requires templates that support these methods.
Abiquo will use this option if the DHCP server is not found
...
Configure the service network in the switches
To configure the service network for standard networking, do these steps for the following hardware
...
.
Top-of-
...
rack switch
Configure all ports in trunk mode
Configure one port in access mode for each public VLAN ID for each hypervisor
In Abiquo, create a public VLAN with each public VLAN tag
For each external/unmanaged VLAN,
...
configure one port in access mode with the corresponding VLAN IDs for each hypervisor
In Abiquo,
...
create external/unmanaged VLANs
...
In Abiquo, edit each rack and exclude tags for external/public/unmanaged networks
...
from the VLAN ranges for private networks
Hypervisor
...
hosts
...
Connect every hypervisor in the rack
...
to an 802.1Q trunk port in the top-of-rack switch
...
All
...
VMs created in the hypervisors will have virtual NICs connected to virtual switches
...
Abiquo supports distributed virtual switches and standard virtual switches
With each network interface on the hypervisor that is
...
connected to a top-of-rack switch trunk port
...
, connect to a virtual switch
Abiquo will create the
...
VLANs/VNICs in the virtual switches.
DHCP
...
server
...
Connect the DHCP server
...
to an 802.1Q trunk port in the top-of-rack switch.
This is a requirement unless you are using SDN, guest setup, or only using unmanaged networks. See Configuring DHCP
...
To configure the DHCP Relay Server (or DHCP Server) that is providing VLAN support, for each VLAN
...
, supply one IP address on the service network but outside of the virtual datacenter range
...
- Private, public and external networks require DHCP configuration
Configuring Service Network VLAN Tags in Abiquo
After the Network Administrator has configured the physical networks as described above, configure the Service Network VLAN tags in Abiquo.
The following screenshots show the configuration of an example scenario in Abiquo.
This is an example to show the GUI functionality and this configuration is not supported by Abiquo.
In this example, only one network service type is used.
| Network | VLAN ID/tag |
|---|---|
| Public | 2 |
| External | 3 |
| Unmanaged | 4 |
| Reserved | 5 |
| Reserved | 6 |
| Private | 7 |
Create a public network in Abiquo using the first public IP range you have purchased for your datacenter and a configured VLAN tag (in our example tag 2).
After purchasing more public IPs for the datacenter, add a second public VLAN, also with the public VLAN tag (in our example, tag 2).
Create an external network with a configured VLAN tag (in our example, tag 3)
Create an unmanaged network with a configured VLAN tag (in our example, tag 4)
Create a rack with reserved VLAN tags. In our example, tags 2 to 6 are reserved for the public, external, unmanaged networks and future networks of these types.
When we deploy the first virtual machine, a private network is created with the first free VLAN tag (in this case, tag 7)
Multiple Virtual Switches per Hypervisor
Default Configuration of One Virtual Switch
The default Service Network configuration has one virtual switch or NIC per Host. All of the vNICs of virtual machines deployed on the hypervisor are attached to the same virtual switch or NIC. It was also connected to all the VLANs in the Infrastructure. The following diagram shows only one network service type (Service Network), which is the default configuration in Abiquo 2.4.
Multiple Switches Using Network Service Types
The new Network Service Type feature allows you to use multiple virtual switches or NICs in each hypervisor. The 'Network Service Type' is a 'tag' for identifying the networks your virtual switches or NICs will attach to. The infrastructure administrators tag each virtual switch or NIC to enable it and identify its network in Abiquo. Then administrators of public, external and unmanaged VLANs also tag each of these VLANs with a network service type. When users deploy virtual machines, Abiquo will attach their vNICs to the virtual switches or physical NICs with the tags matching their VLANs. The following diagram shows this approach.
Private Network IP Ranges
...
...
Default private network configuration
By default, each default private network will have its own VLAN but it will use the same IP address range, i. e. This means every customer tenant can create its their own network name (VLAN) with network address 192.168.0.0/24. This will create different VLANs but the same IP Network. Network administrators should be aware of this default configuration. For example:
Private network IP ranges
| Code Block |
|---|
Enterprise/Customer 1 -> VirtualDC 1
Network C1 -> 192.168.0.0/24, will be in VLAN5
Enterprise/Customer 2 -> VirtualDC 2
Network C2 -> 192.168.0.0/24, will be in VLAN8
|
Related topicsCloud Node