juju/control should be aware of subordinates

juju/providers/common/tests/data/cloud_init_distro

 #cloud-config
 apt-update: true
 apt-upgrade: true
 machine-data: {juju-provider-type: dummy, juju-zookeeper-hosts: 'cotswold:2181,longleat:2181',
   machine-id: passport}
 output: {all: '| tee -a /var/log/cloud-init-output.log'}
-packages: [bzr, byobu, tmux, python-setuptools, python-twisted, python-txaws, python-zookeeper, juju]
-runcmd: [sudo mkdir -p /var/lib/juju, sudo mkdir -p
-    /var/log/juju, 'cat >> /etc/init/juju-machine-agent.conf <<EOF
+packages: [bzr, byobu, tmux, python-setuptools, python-twisted, python-txaws, python-zookeeper,
+  juju]
+runcmd: [sudo mkdir -p /var/lib/juju, sudo mkdir -p /var/log/juju, 'cat >> /etc/init/juju-machine-agent.conf
+    <<EOF
 
     description "Juju machine agent"
 
     author "Juju Team <juju@lists.ubuntu.com>"
 
 
     start on runlevel [2345]
 
     stop on runlevel [!2345]
 
     respawn
 
 
     env JUJU_MACHINE_ID="passport"
 
     env JUJU_ZOOKEEPER="cotswold:2181,longleat:2181"
 
 
     exec python -m juju.agents.machine --nodaemon --logfile /var/log/juju/machine-agent.log
     --session-file /var/run/juju/machine-agent.zksession >> /tmp/juju-machine-agent.output
     2>&1
 
     EOF
 
     ', /sbin/start juju-machine-agent]
 ssh_authorized_keys: [chubb]