List of supported clouds > Manual
This document describes details specific to using the Manual (manual) cloud with Juju.
The Manual (manual) cloud is a cloud you create with Juju from existing machines.
The purpose of the Manual cloud is to cater to the situation where you have machines (of any nature) at your disposal and you want to create a backing cloud out of them.
If this collection of machines is composed solely of bare metal you might opt for a MAAS cloud. However, recall that such machines would also require IPMI hardware and a MAAS infrastructure. In contrast, the Manual cloud can make use of a collection of disparate hardware as well as of machines of varying natures (bare metal or virtual), all without any extra overhead/infrastructure.
When using the Manual 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 Manual cloud |
|---|---|
| setup (chronological order): | |
| CLOUD | |
| supported versions: | N/A |
| requirements: | - At least two pre-existing machines (one for the controller and one where charms will be deployed). - The machines must be running on Ubuntu. - The machines must be accessible over SSH from the terminal you’re running the Juju client from using public key authentication (in whichever way you want to make that possible using generic Linux mechanisms). ( - The machines must be able to |
| definition: | You will need to supply a name you wish to call your cloud and the ssh connection string for the controller, the username@, or the . |
| - name: | user-defined |
| - type: | manual |
| - authentication types: | No preset auth-types. Just make sure you can SSH into the controller machine. |
| - regions: | [TO BE ADDED] |
| - cloud-specific model configuration keys: | N/A |
| CREDENTIAL | |
| definition: | Credentials should already have been set up via SSH. Nothing to do! |
| CONTROLLER | |
| notes on bootstrap: | The machine that will be allocated to run the controller on is the one specified during the add-cloud step. If you encounter an error of the form “initializing ubuntu user: subprocess encountered error code 255 (ubuntu@{IP}: Permission denied (publickey).)”: |
| other (alphabetical order:) | |
| CONSTRAINT | |
| conflicting: | |
| supported? | |
- allocate-public-ip |
 |
- arch |
 Valid values: For controller: [host arch]. For other machines: arch from machine hardware. |
- 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 | With any other cloud, the Juju client can trigger the creation of a backing machine (e.g. a cloud instance) as they become necessary. In addition, the client can also cause charmed operators to be deployed automatically onto those newly-created machines. However, with a Manual cloud the machines must pre-exist and they must also be specifically targeted during charmed operator deployment. (Note: A MAAS cloud must also have pre-existing backing machines. However, Juju, by default, can deploy charmed operators onto those machines, or add a machine to its pool of managed machines, without any extra effort.) Machines must be added manually, unless they are LXD. Example: Further notes: |
| RESOURCE (cloud) Consistent naming, tagging, and the ability to add user-controlled tags to created instances. |
N/A |
Contributors: @swalladge , @whershberger, @hmlanigan
for not supported for example?