On 04/06/2011 09:36 AM, Mark Foster wrote: > On 03/31/2011 05:05 PM, Mathias Gug wrote: > >> Could you clarify what behavior are you referring to? The fact that >> puppet doesn't start after the package is installed? >> > Bingo! > It requires manual intervention (editing the /etc/default/puppet file). > The irony is that it could be fixed via puppet if it puppet was actually > running. >
We ended up using a --exec from vmbuilder to change the option to YES in /etc/default/puppet. Also turned on auto signing of keys on the puppet master. Fire up a new VM and puppet kicks off to complete configuration. So the use case exists for autostart of the puppet agent, auto provisioning of newly created VM's, potential for elastic cloud expansion. Sorry for the old thread reply. - cameron -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
