Oracle Cloud features table

Configure and remove VMs

An Abiquo VM is an Orchestration with one Instance and one persistent bootable volume.

• The platform identifies the VM by the Orchestration name, which is the platform's UUID. The user cannot edit the Orchestration Name.

• The platform assigns the VM Label (also called the Friendly name) to the Instance Name. The VM Label cannot contain parenthesis "()".

Reconfigure VMs

Power off/power on VMs

In Oracle Cloud, the power off will destroy the instance but in the platform it will not. However, it is possible that during a power off, the IPs that were attached to the VM could be taken by another VM, so Abiquo checks this before powering on again

Reset VM

-

Pause and resume VM

-

Take a VM snapshot

-

Remote access

Using the SSH key registered in your user account before deploying the VM. For LInux VMs, the default user is "opc". For Windows VMs, edit the template in the platform and enter Administrator as the user name and also enter a password. Use a public IP address and firewall policies to give access to an SSH port in Linux and RDP port in Windows.

Create and delete networks

You cannot use the same name for more than one network in a region, including private networks in different virtual datacenters (because Oracle Cloud does not support a native virtual datacenter entity). To create more than one virtual datacenter, specify a custom private network for all VDCs after the first one.

The compatible Oracle networks are:

• Private networks: IP networks

• Public IP: IP reservation, which is associated with a private IP.

These are the networks that the platform will create and onboard

Create and delete VDCs

 Oracle cloud does not support native VDCs, see Create and delete networks

Create and manage firewall policies

You can create firewall policies with security group rules

Use Chef

-

Use Chef attributes

-

VM bootstrap scripts

-

 The initial version does not support Cloud-init

VM variables

-

Load balancing

-

Import and synchronize

• To onboard VMs, each orchestration must have one instance and one persistent bootable volume

• To onboard Firewall rules, each ACL entry is a firewall rule and it must have one protocol/source/target only or the platform will synchronize the policy only with the UNREADABLE prefix on its name, meaning that you cannot modify or view the rules, and you can only do two actions: apply them to VMs or delete them from the platform

• To onboard Firewalls that are assigned to VM NICs, Abiquo synchronizes all the ACLs and attaches them to the VM

• To onboard Public IPs, they must not be reserved in a shared network, which is incompatible with Abiquo

VM monitoring and metrics

-

Import VM template
from private cloud datacenter

-

Dashboard billing widgets

-