Juju already has knowledge of the Joyent cloud, so unlike previous versions there is no need to provide a specific configuration for it, it 'just works'. Joyent will appear in the list of known clouds when you issue the command:
And you can see more specific information (e.g. the supported regions) by running:
juju show-cloud joyent
If at any point you believe Juju's information is out of date (e.g. Joyent just announced support for a new region), you can update Juju's public cloud data by running:
The Credentials page offers a full treatment of credential management.
In order to authenticate itself to the Joyent cloud, Juju will need the following information:
- sdc-user - obtained from the Joyent Dashboard
- sdc-key-id - The fingerprint of an SSH key uploaded to Joyent (obtained from the Joyent Dashboard)
- private-key-path - full local path to the actual private key (e.g. '/home/ubuntu/.ssh/id_rsa'). See note below.
The first two values are easily obtained from the 'Account' section via the Joyent Dashboard
Note: The private key is currently uploaded to the cloud in order to remotely sign requests to the Joyent API. It is highly recommended that the private key used in this way should not be a common SSH key you use for other purposes, but a specific one used for the Joyent cloud.
With the above information, you can now run the command:
juju add-credential joyent
...and supply relevant answers to the questions. Note that the path to the SSH key must be the full system path, not using any bash shortcuts such as '~'.
Note: During initial setup if you are having issues deploying charms contact Joyent support at https://help.joyent.com/home to verify your account is capable of provisioning virtual machines.
You are now ready to create a Juju controller for cloud 'joyent':
juju bootstrap joyent joyent-controller
Above, the name given to the new controller is 'joyent-controller'. Joyent will provision an instance to run the controller on.
For a detailed explanation and examples of the
bootstrap command see the
Creating a controller page.
A controller is created with two models - the 'controller' model, which should be reserved for Juju's internal operations, and a model named 'default', which can be used for deploying user workloads.
See these pages for ideas on what to do next: