Cloud-Init & Constraint thoughts

[me@brandonholtsclaw.com]

On Wednesday, June 6, 2012 at 8:31 PM, Gustavo Niemeyer wrote:
> 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?
> 
Both were different angles at the same goal, to get at runtimes not installed on the default cloud images from the start instead of now using something like this in hooks/install:

#!/bin/bash
apt-get -yqq install ruby rubygems && ruby hooks/install.rb
exit 0 


same could be said for puppet manifests etc that already have support in cloud-init for, it would just be exposing that to the charm in juju way

 
> 
> gustavo @ http://niemeyer.net
> 
> 


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