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 OCI cloud |
|---|---|
| setup (chronological order): | |
| CLOUD | |
| supported versions: | |
| requirements: | |
| definition: |  Juju automatically defines a cloud of this type. |
| - name: | oracle or user-defined |
| - type: | oci |
| - authentication types: | [httpsig] |
| - regions: | [TO BE ADDED] |
| - cloud-specific model configuration keys: | address-space (string) The CIDR block to use when creating default subnets. The subnet must have at least a /16 size. |
| CREDENTIAL | |
| definition: |  Starting with Juju 3.3.1, the region field is ignored. |
| 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:) | |
| CONSTRAINT | |
| conflicting: | TBA |
| supported? | |
- allocate-public-ip |
|
- arch |
 Valid values: [amd64, arm64]. |
- container |
 |
- cores |
|
- cpu-power |
|
- image-id |
|
- instance-role |
|
- instance-type |
|
- mem |
|
- root-disk |
|
- root-disk-source |
|
- spaces |
|
- tags |
|
- virt-type |
|
- zones |
|
| PLACEMENT DIRECTIVE | |
<machine> |
TBA |
subnet=... |
|
system-id=... |
|
zone=... |
TBA |
| MACHINE | |
| RESOURCE (cloud) Consistent naming, tagging, and the ability to add user-controlled tags to created instances. |
|