Hi Marco, There's a docs branch up for review here:
https://code.launchpad.net/~axwalk/juju-core/manual-provisioning-docs/+merge/188501 (It needs a couple of tweaks, e.g. admin-secret can be removed from the config example.) Quick start is something like this: - $ juju init - Modify ~/.juju/environments.yaml, setting the bootstrap-host in the null environment. - $ juju bootstrap - $ juju add-machine ssh:<host> - $ juju deploy ... # units will be placed on manually provisioned machines Note that you can't currently destroy-environment. The best you can do is remove all the units, services, and machines other than the bootstrap node. Then, ssh to the bootstrap node, manually stop the juju upstart services and remove their /etc/init config files. There's a TODO for this. Cheers, Andrew On Sat, Oct 5, 2013 at 7:00 PM, Marco Ceppi <ma...@ondina.co> wrote: > On Sat, Oct 5, 2013 at 1:48 AM, Curtis Hovey-Canonical < > cur...@canonical.com> wrote: > >> >> * the “null” provider is now available, for creating environments with >> existing machines. >> > > This is awesome news! Is there any preliminary documentation about it's > configuration? > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
