juju system ssh keys - revisiting

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

...
> This hints to me that Juju run is improperly design. We already 
> have a way to inform all machines that we have work for them to
> do. Which *doesn't* require us to ssh into them (the hook
> triggers).
> 
> Just create a "run" hook that fires a custom script when there is 
> data to be run. Why would be SSH into those machines directly?
> 
> 
>> I believe the rationale was so that juju-run can target machines 
>> as well as units. To target a machine without any units deployed 
>> would mean hooks are out of the question.
> 

Then just run a hook context runner in the Machine agent. Still *much*
better than actually needing to SSH into every machine and violating
the model of every-other-way we run stuff on machines in the environment.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKv7T0ACgkQJdeBCYSNAAPsLwCfVDV/adPkzKk8RfIhEJgCZEEl
gU4An3TxGlipHH2FhDFlH8YSlfPtdOrN
=EDgS
-----END PGP SIGNATURE-----