Summary

Oracle Cloud Infrastructure Compute offers significant price-performance and control improvements compared to on-premises data centers, while providing the elasticity and cost savings of the public cloud. Oracle has a longstanding reputation for providing technologies that empower enterprises to solve demanding business problems––and Oracle Cloud Infrastructure is the first cloud that’s purpose-built to enable enterprises to run business-critical production workloads.

Hakuna Cloud can automatize the provisioning and the disposal of Oracle Cloud Infrastructure Compute instances, using different configurable triggers. The OCI Compute instances are represented by instances in Hakuna Cloud.

Flavour: oracle-compute

Requirements

Hakuna supports the management of Standard shapes, both of Bare Metal instances and of VM instances.

Supported triggers

Trigger Supported Description
HTTP/HTTPS ModProxy Switch on the instance if an HTTP/S request is received
Metrics Switch off the instance if the CPU is low
Schedule Switch on or off the instance following a predefined schedule
SSH Enable SSH connection (eg: git)

Supported stop status

The instance is stopped by Hakuna, stopping the billing for that instance. The user can choose between a “soft” stop that gracefully shuts down the machine and a “normal” stop that simply turns off the instance. In both cases, the instance is not destroyed and any storage attached is not deleted.

Configuration

In order to be able to make API calls (i.e. starting and stopping the instances) on behalf of the customer, Hakuna needs the user to provide:

  • The zone where the Compute instances live;
  • The tenantID (OCID) of the tenancy;
  • The compartmentID (OCID) where the instances live;
  • The userID (OCID) of the user;
  • The RSA private key, along with its fingerprint, that is coupled with the public key provided to Oracle.

Steps to configure an Oracle provider

  • Execute hakuna create provider to create a new CloudProvider.
  • Select oracle-compute as the type, and pick a name to identify this provider in the future.
  • Insert the user OCID.
  • Insert the tenancy OCID.
  • Choose the zone.
  • Insert the path to the .pem RSA private key file.
  • Insert the fingerprint of the key.
  • The list of compartments managed by you will appear; choose one of them.