The Oracle OCI cloud and Juju

List of supported clouds > Oracle OCI

This document describes details specific to using your existing Oracle OCI cloud with Juju.

See more: Oracle OCI

When using the Oracle OCI cloud with Juju, it is important to keep in mind that it is a (1) machine cloud and (2) not some other cloud.

See more: Cloud differences in Juju

As the differences related to (1) are already documented generically in our Tutorial, How-to guides, and Reference docs, here we record just those that follow from (2).

Juju points of variation Notes for the Oracle cloud
setup (chronological order):
CLOUD
supported versions:
requirements:
definition: Already known to Juju. Run juju clouds --all to confirm. (Pre-defined cloud name in Juju: oracle.)
CREDENTIAL
definition: auth-type: httpsig. You will have to provide your SSL private ke fingerprint, SSL private key, a cloud region, your SSL private key passphrase, and your user, tenancy, and compartment OCID.
> See more: Oracle OCI | Account and access concepts

If you want to use a YAML file:

credentials:
 oracle:
  <user-defined credential name>:
   auth-type: httpsig
   fingerprint: <SSL private key fingerprint>
   key: <SSL private key>
   region: <cloud region>
   pass-phrase: <SSL private key passphrase>
   tenancy: <tenancy OCID>
   user: <user OCID>
CONTROLLER
notes on bootstrap: You have to specify the compartment OCID via the cloud-specific compartment-id model configuration key (see below).
Example: juju bootstrap --config compartment-id=<compartment OCID> oracle oracle-controller
other (alphabetical order:)
CONFIGURATION (model)
cloud-specific: address-space (string)
The CIDR block to use when creating default subnets. The subnet must have at least a /16 size.

compartment-id (string)
The OCID of the compartment in which juju has access to create resources.
CONSTRAINT
conflicting: TBA
allocate-public-id
arch :white_check_mark:
Valid values: [amd64].
container :negative_squared_cross_mark:
cores :white_check_mark:
cpu-power :white_check_mark:
instance-role :negative_squared_cross_mark:
instance-type :white_check_mark:
mem :white_check_mark:
root-disk :white_check_mark:
root-disk-source :negative_squared_cross_mark:
spaces :negative_squared_cross_mark:
tags :negative_squared_cross_mark:
virt-type :negative_squared_cross_mark:
zones :white_check_mark:
PLACEMENT DIRECTIVE
<machine> TBA
subnet=... :negative_squared_cross_mark:
system-id=... :negative_squared_cross_mark:
zone=... TBA
RESOURCE (cloud)

Consistent naming, tagging, and the ability to add user-controlled tags to created instances.

 :negative_squared_cross_mark:

Last updated a month ago.

Help improve this document in the forum.