# The Equinix Metal cloud and Juju This document describes details specific to using your existing Equinix Metal cloud with Juju. > See more: [Equinix Metal](https://deploy.equinix.com/developers/docs/metal/) When using this 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](https://documentation.ubuntu.com/juju/2.9/reference/cloud.md#cloud-differences) As the differences related to (1) are already documented generically in the rest of the docs, here we record just those that follow from (2). ## Notes on `juju add-cloud` Type in Juju: `equinix` Name in Juju: `equinix` ## Notes on `juju add-credential` ### Authentication types #### `access-key` Attributes: - project-id: Packet project ID (required) - api-token: Packet API token (required) ## Supported constraints | [CONSTRAINT](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint) | | |---------------------------------------------------------------------------------------------------|-----| | conflicting: | | | supported? | | | - [allocate-public-ip](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-allocate-public-ip) | TBA | | - [arch](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-arch) | TBA | | - [container](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-container) | TBA | | - [cores](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-cores) | TBA | | - [cpu-power](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-cpu-power) | TBA | | - [image-id](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-image-id) | ✕ | | - [instance-role](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-instance-role) | TBA | | - [instance-type](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-instance-type) | TBA | | - [mem](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-mem) | TBA | | - [root-disk](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-root-disk) | TBA | | - [root-disk-source](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-root-disk-source) | ✕ | | - [spaces](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-spaces) | ✕ | | - [tags](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-tags) | TBA | | - [virt-type](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-virt-type) | TBA | | - [zones](https://documentation.ubuntu.com/juju/2.9/reference/constraint.md#constraint-zones) | | ## Supported placement directives | [PLACEMENT DIRECTIVE](https://documentation.ubuntu.com/juju/2.9/reference/placement-directive.md#placement-directive) | | |----------------------------------------------------------------------------------------------------|-----| | [](https://documentation.ubuntu.com/juju/2.9/reference/placement-directive.md#placement-directive-machine) | TBA | | [subnet=](https://documentation.ubuntu.com/juju/2.9/reference/placement-directive.md#placement-directive-subnet) | ✕ | | [system-id=](https://documentation.ubuntu.com/juju/2.9/reference/placement-directive.md#placement-directive-system-id) | ✕ | | [zone=](https://documentation.ubuntu.com/juju/2.9/reference/placement-directive.md#placement-directive-zone) | TBA | ## Other notes **Before deploying workloads to Equinix metal:**
Due to substrate limitations, the Equinix provider does not implement support for firewalls. As a result, workloads deployed to machines under the same project ID can reach each other even across Juju models. Deployed machines are always assigned both a public and a private IP address. This means that any deployed charms are implicitly exposed and proper access control mechanisms need to be implemented to prevent unauthorized access to the deployed workloads.