Puppet 4 needs a lot of new directories in order to even attempt to run. It would be nice if puppet had a way to create the directory structure that it needs in order to run.
For now I'm trying to ignore the seemingly non-existent upgrade path from puppet 3 to puppet 4 that doesn't involve firing up a new puppet 4 server to run alongside the puppet 3 server.
On Friday, April 17, 2015 at 3:04:51 PM UTC-7, Tim Skirvin wrote:Ken Bowley <kbo...@gmail.com> writes:
> We've been using Puppet since the 0.24 days, and it's always been fairly
> simple to add in a new system.
> Do a base install (Linux or Mac OS X)
> Install Ruby if Linux
> gem install puppet
> run puppet
> sign the cert on the puppetmaster
> let puppet take care of everything else.
[...]
> This workflow no longer works with Puppet 4.
I haven't investigated any of this yet; what doesn't work?
- Tim Skirvin (tski...@fnal.gov)
--
HPC Systems Administrator / Developer http://www.linkedin.com/in/tskirvin
Fermilab - USCMS-T1 Collaboration Experiment Computing Facilities
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/bd5ade5e-169f-4d30-be91-b3fc6152bff9%40googlegroups.com.