On Tue, Nov 13, 2012 at 05:05:42PM -0800, Garrett Holmstrom wrote:
What about a service that runs before cloud-init itself, scans the user-data for needed plugins, and then yum-installs them if they're missing?
That isn't going to work for every case, but it sounds like a great "90%" starting point. Maybe a little script could read user-data, and if it contains cloud-config data, the script reads that and takes action on the bits that it has to.
What do you folks think? Anyone itching to give it a try?
I can take a stab at it. Any suggestions for how we should split up the cloud-init package?