Nick Walker 9b50d5e31e Update the README, add an all_in_one_pe role

Updating README for instructions on how to use the control-repo
by putting it in your own git server and then using the r10k
answers during installation of PE.

Removing the manifest for configuring r10k using zack/r10k.

Added a role that can be used to bootstrap an all-in-one PE
installation.

2015-08-13 14:10:29 -07:00

2.5 KiB

Raw Blame History

Before Starting:

This control repo and the steps below are intended to be used during a new installation of PE.

If you intend to use it on an existing installation of PE then you'll have to figure out some of the steps on your own and be warned that if you've already written or downloaded modules when you start using r10k it will remove all of the existing modules and replace them with what you define in your Puppetfile. Please copy or move your existing modules to another directory to ensure you do not lose any work you've already started.

How to Copy This Repo Into Your Own Git Server

Make an user in your internal git server
Make an ssh key to link with your user. You’ll want to do this on the machine you intend to edit code from ( most likely not your puppet master but your local workstation / laptop )

https://help.github.com/articles/generating-ssh-keys/

Create a repository in your git server called control-repo
Setup your control repository by copying this one

Remove the .git directory from the cloned repo.

cd control-repo
rm -rf .git

git init
Find the url to your internal repo this is usually on the front page of the repo

Add the repo as a remote
git remote add origin git@gitlab-server:root/control-repo.git

Push the repository from your machine up to your git server

git push origin production

Lay Down a Trusted Fact Before Installing PE

This control repository is setup to manage certain portions of your PE installation for you if you lay down a trusted fact called pp_role before installing. In order to immeadiately gain from these benefits you will need to lay down a file that looks exactly like the below in /etc/puppetlabs/puppet/csr_attributes.yaml

---
extension_requests:
  #pp_role
  1.3.6.1.4.1.34380.1.1.13: 'all_in_one_pe'

Install a New PE 2015.2+ Instance or Update an Existing PE Instance To Use the Control Repository

Install PE Specifying Answers To Point To Your Control Repository

https://docs.puppetlabs.com/pe/latest/r10k_config_answers.html

#TODO Flush out generating an answer file and then appending these answers onto the end of it.

Update Existing PE 2015.2+ Install To Point To The Control Repository

https://docs.puppetlabs.com/pe/latest/r10k_config_console.html

Run r10k

Run r10k deploy environment —verbose and watch it install the modules from your Puppetfile

2.5 KiB Raw Blame History Unescape Escape