Manual provisioning - feedback wanted
andrew.wilkins at canonical.com
Mon Sep 9 01:47:34 UTC 2013
As was noted in the 1.13.3 release notes thread, we did not announce one
the major features that made it into the release (manual provisioning).
This was intentional as we have not written any documentation yet. On the
other hand, it would be good to get some feedback so that we can make
changes if necessary, or feed into the documentation.
So, below is a bit of a run-down. If you're interested in this feature, try
it out and let us know if you or have any issues or any thoughts for
As of 1.13.3 you can now do this:
juju add-machine ssh:[user@]host
and a series of commands will be carried out on that host, via SSH, to
provision the machine into the current juju environment. This will enable
you to compose a juju environment out of your existing systems.
Here's a few things to bear in mind:
- Currently you do need to have an existing, bootstrapped environment.
Work on improving this situation is underway
- The machine you're provisioning must be able to route to machine 0 (for
the state/API), and storage (to get tools, etc.)
- There is no change in supported operating systems; the machine being
provisioned must be running Ubuntu 12.04+
- Multiple invocations of ssh will be made, and sudo is used on the remote
host to install the machine agent. To reduce noisy prompts, you should use
public key authentication. To completely eliminate prompting, you'll also
need to enable passwordless sudo on the target host.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju