Compute resources in Abiquo Datacenters are represented as machines on racks.
In Abiquo, a rack is a logical entity used for grouping machines. Groups of machines may be useful in:
Abiquo racks can be configured to mirror physical racks, i.e. a group of machines connected to the same top-of-rack switch. The Administrator's Guide describes the Configuring the Service Network for Cloud Tenant Networks.
The PHYSICAL SERVERS list is on the left-hand side of the datacenter pane.
The buttons above the PHYSICAL SERVERS list are used to manage racks and machines.
Create a rack or add a machine. If there are no racks in your datacenter, click the add button to Create a Rack. If a standard rack is selected, click the add button to Create a Physical Machine on the selected rack.
Delete a rack or remove a machine.
Edit the selected rack or machine.
When creating or editing a physical machine, the Check button refreshes the resources used on the selected machine and synchronizes the virtual infrastructure (for virtual machines in the UNKNOWN state)
Complete the following fields to create a standard rack.
Complete the following Network Parameters.
To add a machine, first select a rack, then click the add button.
If there are no racks in your datacenter, the add button will open a popup to create racks. Abiquo uses the Discovery Manager remote service to automatically discover machines and retrieve their details.
If you already selected a rack, select "Physical machine" in the drop-down menu.
Enter the Hypervisor type then enter the connection details for the hypervisor:
Using the connection details, the Discovery Manager will try to connect with the hypervisor running on the machine.
Abiquo will automatically complete the default hypervisor user, password and port set in Configuration View (see Create new infrastructure defaults).
Then Abiquo will open:
To add an Oracle VM master hypervisor, select the hypervisor type from the pulldown list.
Enter the Oracle VM connection data. If you do not enter the optional Manager Port, Abiquo will use the default port described in Ports and Communications
The Multiple hypervisor selection popup will open with a list of the hypervisors managed by the master hypervisor.
By default, the Import existing virtual machines checkbox is ticked.
Select the hypervisors you wish to add.
You will need to complete the process to Create a machine for each of these hypervisors. Click Edit beside a hypervisor to open the main Create physical machine popup for that hypervisor. After you complete the details in this popup, the Incomplete warning will be removed from beside the physical machine.
Mark the checkbox beside your hypervisors to add them to Abiquo.
Click Accept to complete the process.
After Abiquo has automatically discovered the physical machine, complete the information on the tabs of the Create physical machine popup.
This table describes each field in the form:
The name of the machine (usually set to its hostname).
The rack where the machine will be added.
An optional description of the machine.
The number of CPUs are retrieved from the machine and cannot be changed.
The RAM is retrieved from the machine and cannot be changed
The type of virtualization technology you selected in the previous hypervisor selection dialog
The IP address of the machine in the management network
The user for the hypervisor connection (for XenServer, Hyper-V and ESXi). For Hyper-V only the down-level logon name (domain\user) format is supported
The password (for XenServer, Hyper-V and ESXi)
|Port||Port (ESXi) or AIM port for the connection (KVM). If not provided, Abiquo will use the default port in the Ports and Communications table|
The state of the machine, see #Physical Machine States. Click 'Check' to update the state
|Import existing virtual machines||Tick this checkbox to import virtual machines already running on the hypervisor host|
Network interface is required
To save the physical machine, you must select at least one network interface.
On the Network Interfaces tab, you can tag the virtual switches or physical NICs to use for virtual machine network connections. The network service type is a tag that enables and identifies a network in Abiquo. After you tag the network interfaces, you can tag external, unmanaged and public VLANs to use these interfaces.
Before you can assign a network service type Manage Network Service types, create it on the Datacenter's Networks tab. See Manage Network Service Types.
Select a service type from the the drop-down list to assign it to the network interface. The default Network Service Type is called Service Network.
Abiquo may list ALL the NICs and virtual switches on the machine, including those that are not suitable for use with virtual machine networks Abiquo. Usually the default network interface for use with virtual machine networks will be as follows.
|vSwitch0 connected to VMNICx|
|Hyper-V||As named during installation||SERVICE_NETWORK|
Abiquo recommends that you check the network interfaces with your Network Administrator.
New network interfaces will be detected when:
You cannot change the network service type assigned to an interface if there are virtual machines deployed with virtual NICs using addresses in the network. To change a network service type, first remove it from the existing interface by setting this to "Not assigned". Then assign the network service type to a different interface.
To disable the NIC so that it cannot be used in Abiquo, select "Not assigned".
On standard racks Abiquo uses IPMI in the high availability (HA) process to shut down a machine that is not responding. Click IPMI tab to edit the IPMI parameters. On managed racks, Abiquo HA uses the API of the managed rack to control the machine.
For further information about Abiquo high availability, see Configuring High Availability of Virtual Machines in the Administrator's Guide.
Datastore is required
To save the physical machine, you must enable at least one datastore. Do not enable the NFS repository (usually /opt/vm_repository)
In Abiquo, datastores include the disks used by the hypervisors to store information related to the virtual machines and the NFS repositories. When you create a machine, you will see a list of all the datastores (and potential datastores) that are installed on that machine. For some hypervisors this list includes the NFS repository (usually /opt/vm_repository), which should not be used as a hypervisor datastore. New datastores will be detected when a machine check is performed.
To edit datastore details, select the datastore and click the Configuration button. To enable a datastore, select the datastore and mark the Enabled checkbox. The Abiquo datastore allocation process will deploy a VM on the enabled datastore with the most available space.
If you require more disk capacity on a hypervisor, you can add a new datastore. First, configure the disk on the machine and in the hypervisor, then edit the physical machine in Abiquo. On the General Information tab, click "Check" to check the state of the machine. Go to the Datastores tab and you should see the new datastore, then click Enabled. The datastore allocation process will deploy VMs to the datastore with the most available space.
Wherever possible, the datastores list does not include the NFS repository because it is an internal datastore that is used to share images between the NFS server and the hypervisor. If the NFS Repository is visible in the datastores list, you should not enable it as a hypervisor datastore because deployment over a network to the same NFS shared directory from which the virtual image templates are being copied will severely degrade performance.
If you wish to retrieve and import VMs that are already running on your physical machine, you must enable all the hypervisor datastores that contain these VMs. Abiquo does not retrieve persistent VMs because their system disks are located on external volumes.
Abiquo runs a periodic infrastructure check process to update infrastructure values in the Abiquo database, including the real disk space available on a datastore. However, at deployment time, Abiquo only checks the database values. The datastore allocation process will deploy using the hypervisor datastore with the most available space.
Abiquo High Availability of Virtual Machines requires all the hypervisor hosts involved to share the same datastore, which must be enabled for deployment of virtual machines. This will allow Abiquo to restart machines in other hypervisors from the shared datastore. High availability does not copy virtual machine system disks. Thus, if none of the other high availability hypervisors can see the datastore used by a hypervisor, the virtual machines using this datastore will not be restarted. Therefore, you should enable only shared datastores (and disable other datastores) on high availability hosts and ensure that the shared datastore is available to all other high availability hosts in the same group.
This functionality was deprecated in version 3.0. Please use the Abiquo API to create multiple machines.
The Physical Servers list is on the left side of the datacenter pane. The machines are organized by racks.
Enter text in the search box at the top of the physical servers list to filter racks and only display the racks with names containing this text. To reset the filter and display all racks, clear the text and press enter.
The following table describes the possible states of physical machines.
|Gray||STOPPED||The machine is stopped; it does not respond to ping|
|Orange||PROVISIONED||The machine exists, but there is no connection to the hypervisor|
|Yellow||NOT MANAGED||The machine and hypervisor exist, but are not properly configured|
|Green||MANAGED||The machine and hypervisor are ready to deploy virtual machines|
The machine and hypervisor are ready but the machine has been disabled by the cloud administrator to prevent users from working with their virtual machines.
|Gray||UNLICENSED||There are not enough licenses for the cores in this virtual machine|
|Gray||HA IN PROGRESS||The machine and hypervisor are being used by the high availability process|
|Gray||DISABLED FOR HA||The machine and hypervisor have been disabled by high availability after restarting of virtual machines on another hypervisor|
|Pink||HALTED FOR SAVE||The machine, which belongs to a UCS rack, has been powered down by Abiquo. Therefore the machine is ready for power on under certain circumstances|
You can view the virtual machines created on each machine. The virtual machines can be viewed as a list.
A summary of the properties of a machine appears below the virtual machines pane when the user selects a virtual machine. This summary contains the information on the selected object. The virtual machine control panel contains the controls listed in the table in the Control Machines section.
To edit a rack, select it in the rack list and press the edit button at the top of the physical servers list.
You can change the same rack values that you entered to #Create Racks
You cannot modify the network parameters of a rack to exclude a VLAN ID from the range or as a specific exclusion if there are any virtual machines deployed in a network using that VLAN tag ID
A summary of the properties of a machine appears below the virtual machines pane when the user selects a physical machine. The tabs are:
The general tab provides information about CPU, RAM, Hard disk, IP address, Hypervisor type and Port for the hypervisor connection.
The network interfaces tab displays a list of interfaces and the service type tags that are assigned to them. Service type tags are also assigned to VLANs.
Contains the description of the physial machine entered by the user.
The used resources (CPU, RAM, Hard Disk) in the physical infrastructure are updated:
The resources used can be viewed on the State tab of the Machine details pane.
Manually refreshing allocated resources
Edit the physical machine and click the Check button to refresh the state and resources of the selected machine.
The following buttons enable the user to control physical machines.
|Send email to owners|
|Retrieve or import virtual machines|
|Capture retrieved virtual machine|
|Delete retrieved virtual machines that were not imported|
The provisioning process selects a machine for deploying a virtual machine, according to the Virtual Machine Allocation. You can disable a machine in order to avoid deploying virtual machines on it. To do this, click the disable button:
When the machine is disabled, the disable button will change to an enable button. To re-enable the machine, click the enable button.
After a machine has been disabled by HA, the status indicator will be gray. The system administrator should restart the machine and check the hypervisor before re-enabling the machine.
Attention: Restarting an ESX or ESXi host disabled by HA
Before manually enabling an ESXi host in Abiquo:
A machine disabled by HA will have the state HA DISABLED in the Abiquo GUI. Manually enable the machine in Abiquo by clicking the enable button on the right-hand side of the screen.
Machines can be reserved for a specific enterprise and the enterprise's deployments can also be restricted to these reserved machines. This is done in Users View by selecting the editing the Enterprise and selecting the Reservations tab.
Click the email iconto send email notifications about a machine or its virtual machines. Notifications can be sent to either the owner of the machine (the user who created it) or to the administrator or enterprise manager.
The managers of an enterprise are all the users of that enterprise with the "Define Enterprise Manager" privilege. All users who have virtual machines deployed on that machine will receive email notifications about a machine.
For event notification from Abiquo, the system administrator should use the Abiquo Events Notifier.
To delete a rack, first check there are no virtual machines deployed on its machines. You cannot delete a rack with virtual machines deployed on its machines.
Select the rack in the rack list and press the Delete Button in the top right corner of the PHYSICAL SERVERS list. The rack will be deleted.