Cloud-Init & Constraint thoughts

[Gustavo Niemeyer]

Hi Brandon,

> 1) a package list constraint or metadata that would be installed on all
> nodes that had that constraint , e.g. ruby1.9 or php-cli , these could be
> added very easily to the array that is passed in now for installing juju and
> bzr etc during cloud init. so they could be used as the runtime for
> hook/install and such.

That would remove the important property of charms of being
self-contained. In other words, one shouldn't have to prepare the
environment in manual ways to enable the charm to work.

> 2) the same type of thing only just a base64 encoded #user-script to be
> executed by cloud-init in its normal fashion provided by the charm as a hook
> of say hooks/init

Not sure I understand. Why not just using hooks/{install,start} to do
the task itself?


gustavo @ http://niemeyer.net