[KaiserPro]

Puppet's original design was that it was meant to be agent based on the things it was meant to configure. It was never very good at bringing up stuff before the agent could be connected.

The general flow was Imager->pre-configured puppet agent->connect to controller->apply changes to make it perform as x

originally it never really had the capacity to kick off the imaging/instantiation. THis meant that it scaled better (shared state is better handled than ansible)

However ansible shined because although it was a bastard to get running on more than a couple of hundred hosts in any speed, you could tell it to spin up 100x EC2(or equivalent) machines and then transform them into which every role that was needed. In puppet that was impossible to do in one go.

I assume thats changed, but I don't miss puppet.

[bigfatkitten]

It's not really that much of an embuggerance.

Kickstart or cloud-init to get the OS up and Puppet agent installed, then let Puppet do the rest.