...
In the OCI portal, you can deploy VMs with smaller disk sizes. If you onboard these VMs and undeploy them, then when you try to redeploy the VM in Abiquo, if you do not resize the disk, OCI will respond with a disk size validation error.
Azure ARM OCI feature | Support | Comments |
|---|
Configure and remove VMs | 
| When you create a VM, you’ll select the hardware profile.
Abiquo supports OCI Flex shapes, which are dyamic hardware profiles
 The minimum sizes of boot volumes to deploy in OCI using Abiquo are: 50 GB for Linux 250 GB for Windows
See https://docs.oracle.com/en-us/iaas/Content/Block/Concepts/bootvolumes.htm#Custom |
Onboard templates |
| To retrieve a private template to onboard it, enter the Image ID in the search dialog. The platform does not display private templates in the search results for performance reasons. The platform automatically onboards templates of deployed VMs
|
Reconfigure VMs |
| To change the IPs and disks of a deployed VM, the VM must be running (powered on). This is because OCI supports only hot-reconfigure for IPs and disks |
Power on VM |
|
|
Power off VM |
|
|
Reset VM |
|
|
Pause and resume VM |
|
|
Storage |
| Abiquo volumes are generally Block volumes in OCI. Users can onboard and create volumes, and attach them to VMs The supported controllers are paravirtualized and SCSI. See https://docs.oracle.com/en-us/iaas/Content/Block/Concepts/overview.htm#attachtype An OCI Boot volume in position 0 of the boot sequence is an Abiquo hard disk. If you undeploy the VM, OCI will delete the boot volume An OCI Boot volume in another position in the disk sequence is an Abiquo volume
The minimum sizes of boot volumes to deploy in OCI using Abiquo are 50 GB for Linux and 250 GB for Windows After users detach volumes from VMs or delete VMs, the synchronization process will make the volumes available in the public cloud region Users can move volumes between virtual datacenters and release them to the region OCI does not support premium storage for some hardware profiles. The platform does not enable you to configure VMs with premium storage Abiquo imports shared volumes that are attached to a VM. You cannot create shared volumes in Abiquo For each VM using the volume, Abiquo reports a new volume You can import shared volumes attached to a VM only You cannot reconfigure or delete shared volumes because you cannot detach them from the VMs You can resize shared volumes
|
Take a VM snapshot |
| The VM must be powered off. You can create an instance template of the boot disk only.
See Create instances to save Save VM disks to templatescreate an instance template |
Remote access |
| Requires user SSH key and first a private IP in a public subnet and secondly, a public IP, and a firewall with port 22 open For Oracle Linux and CentOS images, the default username is opc. For Ubuntu images, the default username is ubuntu. For Windows, the default username is opc and the platform will display the initial password for first login
|
Create and delete networks |
| Each Abiquo VDC will map to an OCI Virtual Cloud Network An Abiquo private network will map to a subnet in the VDC network
When you create a VDC, the OCI VCN has a default security list and then Abiquo blocks all incoming traffic VMs To be able to deploy your VM, the first IP address must always be a private IP address, in a private network or a public subnet. To be able to connect to your VM, the first IP address must be a private IP in a public subnet and the second IP address must be a public IP.
|
Create and delete VPNs | - |
|
Create and delete VDCs |
| OCI VDCs require resource groups, which are OCI Compartments Abiquo VDCs will not be locked to a single resource group but it may be more difficult to display resources in other resource groups Each Abiquo VDC will map to an OCI Virtual Cloud Network (VCN)
|
Create and manage firewall policies |
| |
Use Chef | - |
|
Use Chef attributes | - |
|
VM bootstrap scripts |
| On Linux and Windows using cloud-init and cloudbase-init. The Windows templates provided by Oracle Cloud Infrastructure include cloudbase-init. |
VM variables |
| On Linux and Windows as instance metadata. |
Load balancing |
| See OCI load balancers table and Abiquo and Oracle Cloud Infrastructure load balancers |
Import and synchronize VMs |
| To onboard VMs, the enterprise must have credentials registered. If you onboard a VM with a boot volume that is smaller than the minimum size (50 GB for Linux, 250 GB for Windows), and you then undeploy and redeploy it, OCI may respond with validation error for disk size. |
VM monitoring and metrics |
| |
Dashboard billing widgets |
| The Home view dashboard view can display public cloud billing information, including the latest bills and estimated bill. For the default tab display, see Hybrid and Home view, and for configuration instructions see Obtain OCI credentials |
High availability |
| Requires the privileges to Manage availability sets and Assign availability set to VM Abiquo availability sets represent OCI Availability domains To use high availability, attach VMs to Regional subnets that are not specific to a single Availability domain
|
Resource groups |
| Resource groups represent Compartments in OCI.
Requires the privilege to Manage resource groups, also Delete resource groups When you synchronize (or onboard) a virtual datacenter (an OCI Virtual Cloud Network), Abiquo only onboards the resource groups of the VDC and the resources in the VDC When you synchronize a virtual resource (firewall, load balancer, availability set, and so on), Abiquo will onboard its resource group (if it wasn't already in Abiquo) When Abiquo periodically onboards and synchronizes volumes (OCI disks), then Abiquo will onboard the resource groups of the volumes. This may mean that some volumes and their resource groups may be automatically onboarded before the user onboards their resources in the platform
|
Tags |
| Abiquo multicloud tags are OCI Freeform tags and you can apply these tags to the following entities in the provider: virtual datacenters, VMs, firewalls, and load balancers. |
...