The aim of this section is to list and describe, from a functional perspective, the different components that it will appear in the documentation
The Apps library is the centralized virtual machine template library. Users can create virtual machines from the templates available in the Apps Library. The Apps library is also called the Appliance library or Application library.
The platform's default template format for each hypervisor. See Template Compatibility Table#Hypervisor Compatibility Table
|Captured virtual machine||A virtual machine that was created in a hypervisor outside of Abiquo and retrieved by Abiquo, then captured. Abiquo can manage captured virtual machines in the same way as virtual machines created in Abiquo. See Import and Capture Virtual Machines.|
Datacenters and providers that offer pay-as-you-go, scalable, and flexible virtual infrastructure (compute, network and storage) as a service to final users
A group of physical machines on the same LAN (Local Area Network). These machines are usually located in the same place, and share a network and resources (e.g. electrical power)
|Datacenter networks||Networks that are created at datacenter level: external, public and unmanaged networks.|
|Default network||Network that can be set for an enterprise (external, private) or virtual datacenter (public, external, private). If the user does not create a network configuration, the platform will create one using the default network.|
|Deploy||The process of allocating, provisioning and powering on a virtual machine. Also called launching a VM.|
An enterprise is a cloud tenant. So an enterprise could be a third-party company, development group, company department, and so on. All the users in an enterprise can access the same virtual infrastructure. Each enterprise has its own partition in the Apps library.
The maximum amount of resources that are available to an enterprise or virtual datacenter, for example, RAM, CPU, hard disk.
A virtualization platform enabling the creation of different virtual machines on the same physical machine.
|Instance||See Virtual Machine Instance|
|Managed networks||Virtual machine networks that receive their IP addresses from Abiquo, including: private, external and public networks.|
|Onboard||The platform can synchronize public cloud regions to onboard VMs and other resources that were created outside of Abiquo in public cloud providers|
Persistent Virtual Machine Template
To create a persisent virtual machine template, the platform copies the system disk of a virtual machine template to a volume of external storage, so that system disk data persists after the Virtual Machine is undeployed
A physical machine, cloud node, or host has a hypervisor running on it in order to provide a virtualization infrastructure
|Reconfigure||To change the virtual machine configuration after deployment. If your virtual machine does not support hot reconfigure, you must power it first in order to reconfigure it. Elements that can be changed during a reconfigure include: network interfaces and volumes.|
|Scope||An access list of enterprises and/or datacenters|
When the user reaches the soft limit for a resource, the system alerts the user that they are near the absolute limit of a resource, called the hard limit.
|Synchronized||When virtual machines are synchronized, the virtual machine states are the same in Abiquo and in the hypervisor or public cloud region.|
A public or private repository of virtual machine templates. Descriptions and virtual machine disk files are served by HTTP.
|Tenant||In Abiquo, cloud tenants are known as enterprises.|
|Undeploy||The process of destroying the virtual machine in the hypervisor and releasing resources on the platform.|
|Unavailable VM template||An unavailable VM template in private cloud is a template with no disk file. In public cloud it is a template that is in the Abiquo Apps library cache but not available in the cloud provider. Users cannot deploy this template. Administrators can replace the disk file to make the template available again or when the template is no longer in use, they can delete it from the Apps library.|
Users of the platform are grouped into tenants, which may be organizations, departments, and so on. Each user has a role with a group of privileges to allow the user to work with platform features.
|VApp Spec||A VApp spec is a configuration blueprint saved from a virtual appliance. Users can easily create a new virtual appliance from a VApp spec. A VApp spec is an abbreviation for "virtual appliance specification".|
A virtual appliance (VApp) is a group of virtual machines running in a virtual datacenter. The virtual appliance can contain a related set of virtual machines that are used to provide a service, for example, a web stack. At the virtual appliance level, you can deploy these virtual machines together, view their performance statistics, create anti-affinity layers for VM high availability, and so on.
A partitioned area of the cloud with a set of virtual resources that belongs to one tenant and may be controlled by the tenant administrator (limit resources, create volumes, obtain public IP addresses, etc). The virtual resources are available to administrators and users on a self-service basis. The virtual appliances in a virtual datacenter all use the same type of virtualization technology (hypervisor, public cloud provider). These virtual appliances are all in the same public cloud region or physical datacenter and rack. See Manage Virtual Datacenters
|Virtual Datacenter Networks||Networks created at virtual datacenter level: private networks that are isolated within the virtual datacenter.|
A guest or virtual machine is an instance of a virtual image with network and storage configurations. On a hypervisor it can be understood as a virtual operating system instance. One physical machine with a hypervisor installed can host various virtual machines.
Virtual Machine Instance
To create a virtual machine instance, the platform copies selected virtual machine disks and saves them as a new template in the Apps library.
Virtual Machine Template
A virtual machine template contains the disk files that the platform will use to create a virtual machine and the definition of the virtual machine. In public cloud, the platform only stores the virtual machine definition and it uses the disk files in the provider.