Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

i've realized a vMaaS with 3 vnodes where i deployed juju-gui (node1) and openstack in the other 2 nodes (node2,node3). These last ones at moment are in ready status on vMaaS. Then i've added other vnodes to vMaaS to deploy Cassandra and hadoop, i've already added a new maas environment on environments.yaml called it maassvr02. But every time i try to bootstrap the new one, juju makes the boot of node3 and not the new vnodes. my question is:

which is the right way to realize multiple juju environment like that? thanks a lot.

the solution is to run the following commands:

$: juju sync-tools -e maassvr02
$: juju bootstrap -e maassvr02 --to node4.maas --debug

then i've added also the node5.maas

share|improve this question
Can you post your environments.yaml (obscure the secrets) and share the command you're running to bootstrap? – Adam Collard Jul 20 '14 at 21:26
the configuration file is that: and the commands used to bootstrap the new environment are these – Riccardo Magrini Jul 21 '14 at 7:24
Thanks, those both seem reasonable (note the -e is unnecessary if you've "juju switch"ed). You say that you've installed openstack on nodes 2 and 3, but they are in Ready state? That is inconsistent, if you have services deployed they should be Started, not Ready. Did you use Juju to deploy to nodes 2 and 3? – Adam Collard Jul 21 '14 at 8:35
hi, i deployed Openstack via juju on nodes 2-3 when their status was in allocated, at the end of the procedure i tested Openstack dashboard and then decided to stop the nodes in ready status via MaaS to create another juju environment with new vnodes. – Riccardo Magrini Jul 21 '14 at 8:53
Stopping a node is essentially powering it off. It should only be done when you no longer need the data or services on that machine. It sounds like MAAS and Juju are behaving as designed – Adam Collard Jul 21 '14 at 8:54
up vote 4 down vote accepted

OP posted:

I've resolved that in this way: after to add the new environment i run these commands:

juju sync-tools -e maassvr02
juju bootstrap -e maassvr02 --to node4.maas --debug 
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.