| Cloud Admin | Enterprise Admin | User |
|---|---|---|
 |
 |
|
Each Physical Machine belongs to a Rack, and Rack holds multiple Physical Machines. Before adding Physical Machines to the Infrastructure, a Rack has to be created. The available actions to manage Racks and Physical Machines are:
|
|
|
Creating Racks
To create a new Rack, the following form must be filled:
|
|
|
Creating Physical Machines
To create a new Physical Machine, the following form must be filled:
The following table describes each field in the form :
| Field | Description | ||
|---|---|---|---|
| Name | The name of the physical machine (Usually set to its hostname). | ||
| Rack | The Rack where the Physical Machine will be added. | ||
| Description | An optional description of the Physical Machine. | ||
| CPU /RAM / Hard Disk | The Resources allocated in the Cloud. This information will be used in the provisioning process. Abiquo stores the real resource allocation of the Physical Machine and the allocated resources in the cloud. At the beginning, real resources = allocated resources. | ||
| IP | The address of the Physical machine in the Management network. | ||
| IP Service | The address of the Physical machine in the Service network. | ||
| Virtual Switch | (In Community Edition this is a free text field) The virtual switch in the hypervisor connected to the service network. This networking resource will be used to provide virtual machine inter-Virtual machine connectivity and public connectivity, using the IEEE 802.1Q.
|
||
| Hypervisor Type | The type of virtualization technology. | ||
| User-Password/Port | Depending on the Hypervisor Type selected, the connection configuration will be the tuple user-password (for XenServer, HyperV and ESXi) or the AIM port to connect (KVM and XEN). | ||
| State |
|
||
| Datastores | Datastores screen has a section in this document that explain how to works with them. Basically, since 1.6.5 abiquo allows to manage multiple datastores for each PhysicalMachine and it's integrated in a vCenter environment |
Autodiscovering Physical machines
 | Enterprise Edition Functionality This feature is available in Abiquo Enterprise Edition |
Enterprise Edition uses the Discovery Manager remote service to autodiscover Physical machines and their information. When creating a Physical machine, you have two options: the 'Basic' way and the 'Advanced' one.
Basic Physical Machine discovering
In the drop down menu 
of the Infrastructure Screen
select the 'Physical Machine' option and the following popup appears if the Basic button is pressed. The only required field is the IP address of the physical machine to add:
Once the IP address has been entered, the Discovery manager will look for all information about which Hypervisor is running in the remote physical machine. The client has a configuration file with the default user and password to use to log in into the remote hypervisor. If the default user and password matches with the actual physical machine, the Discovery Manager will show the form described in the previous section, filled with the discovered values.
If the default user and password don't match with the remote Hypervisor credentials, you will see a screen like the advanced screen.
The third option is that any Hypervisor is responding to the call. In this case, the form is shown filled with blanks.
Advanced Physical Machine discovering.
If you press the 'Advanced' button, you will see the advanced way to retrieve the Physical Machine information. You use this option when you know all connection data of the remote hypervisor.
Depending on the Hypervisor you choose, the next step will be fill the user and password (XenServer, HyperV and ESXi) or fill the port field in the same screen (Xen and KVM).
If the Hypervisor doesn't respond, you also will have the option to see the empty Physical Machine screen to fill yourself the Physical Machine definition.
Create multiples physical machines.
| New feature This feature is available since 1.6.5 release. |
With this feature, you will be able to register into the Abiquo platform multiple existing physical machines which IPs are into a defined range. The Discovery Manager will check into each IP if the physical machine has the requirements stablished in the 'Muliple Physical Machines' screen. The main difference with the previous section (add single Physical Machine) is that you'll never see the confirmation screen with the physical machine parameters.
In the drop down menu of the Infrastructure Screen
select the 'Multiple Physical Machines' option and you will see the following screen:
|
|
|
Datastores management
| New feature This feature is available since 1.6.5 release. |
Now it's possible to show all the datastores that are installed in Host. The scheduler will deploy the VM in both datatastores if they are enabled.
Note that nfsrepository, that it's used internally to share the images between NFS server and Host, are not shown in the list of datastores. This behivour appears in order to avoid posible bad use of this datastore.
| Field | Description |
|---|---|
| Name |
Datastore Name |
| UUID | The unique value identifier |
| Directory | Exported by datastore |
| Size | Max Size in the datastore |
| Used | Used size in the datastore |
| Enabled | If datastore can be used for scheduler or not to deploy abiquo VM |
Disabling a Physical Machine
| Enterprise Edition Functionality This feature is available in Abiquo Enterprise Edition |
The provisioning process always find the better Physical Machine to deploy a Virtual Machine, accorting to the Best Fit Resource Scheduler. System Administrators can disable a Physical Machine in order to avoid deploying Virtual Machines on it. This can be done by clicking the disable button:
Physical and Virtual Machine details
A resume of the properties of the machine appears when the user selects a virtual machine or a physical machine. It contains the information on the selected object and the System Administrator can edit its properties.
Each time an user deploys or undeploys a Virtual Appliance, the used resources (CPU, RAM, Hard Disk) in the physical infrastructure are updated. This resource allocation values, can be viewed in the State tab of the Physical Machine details.
 | Manually refreshing allocated resources In some situations, the allocated resources information may be out of date. To manually refresh it, the  button can be clicked to refresh the state of the selected Physical Machine. |
Virtual Machine overview
It is possible to show the virtual machines created in different physical machines (or grouped by rack). The virtual machines can be viewed as a list of names or icons with each entry representing a virtual machine object.
In each virtual machine object the following actions can be done:
- Power On/Power Off the virtual machine.
- Pause the virtual machine.
- Restart the virtual machine.
- Access the virtual machine server via VDRP/VNC (if supported by the Hypervisor).
Retrieve existing Virtual Machines from Physical Machine
| Enterprise Edition Functionality This feature is available in Abiquo Enterprise Edition |
At Physical Machine level, user can get all the information of the virtual machines that are running in the hypervisor and that are not yet managed by the Abiquo Platform.
This is done by clicking the retrieve button 
of the details of a Physical Machine. All found Virtual Machines will appear in the Virtual Machine list with the following icon: 
Sending e-mail notifications
| Enterprise Edition Functionality This feature is available in Abiquo Enterprise Edition |
This functionality allows to send e-mail notifications related to a Physical or Virtual Machine either to the owner of the machine (the user who creates it) or to the Enterprise administrator.
When an e-mail notification realted to a Physical Machine is sent, all users that have Virtual Machines deployed in that Physical machine will recieve the notification.
