Cloud-Init & Constraint thoughts

[me@brandonholtsclaw.com]

Thinking over a few issues when charming I was thinking since we have both constraints now and cloud-init is a hard dependency how about the ability to pass in 2 different items from the charm that will become user-data either directly or abstracted by juju 

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.

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 

Thoughts ?

-- 
Brandon Holtsclaw
http://www.brandonholtsclaw.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20120606/27e53492/attachment.html>