Well, I have to start somewhere. I'll just start poking around to see what I find, and follow my nose.
- Google for "Fedora infrastructure puppet." Where are notes for how to check out puppet?
http://infrastructure.fedoraproject.org/infra/docs/puppet.txtThese notes have an older flavor than my course. Ben Ford says that puppet is now moving to the git/svn model of "command subcommand flags," and that what was once "puppetca" is now "puppet cert". The notes look like they use the older syntax.
- How do I get to the machine for checking out the puppet git repo?
$ ssh lockbox01.phx2.fedoraproject.org- What's the command to check it out?
$ git clone /git/puppetInstructions say only check it out on lockbox01. I suspect this means just use it there, since anywhere else wouldn't make sense. Exploring the repo locally is easier, so I check it out on my own machine like this:
$ git clone lockbox01.phx2.fedoraproject.org:/git/puppet- The top-level "main" -- the place Puppet looks first -- is manifests/site.pp. This installation just has site.pp import other files in the directory. What manifests are imported that aren't in the repo?
private/*.ppThere is no private directory, but this suggests that a typical practice might be to put your own private puppet manifests into a local directory by this name, for experimentation.
2 things:
ReplyDeletea) We do want you to just use the repo on lockbox01... we haven't made the repo public, so we prefer not to copy it to lots of remote machines. No great biggie tho.
b) The private repo is a seperate git repo thats only accessable to a small group of people. This repo/tree has all our passwords in it... it's merged into the main checkout for puppet so it can fill in passwords, but day to day folks can't see them in the git repo.