hieradata | ||
manifests | ||
scripts | ||
site | ||
environment.conf | ||
Puppetfile | ||
README.md |
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.
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 PE 2015.2
- Download the 2015.2 installer for your platform and copy it to your master
- Expand the tarball and
cd
into the directory - Run
puppet-enterprise-installer
to install
How to Copy This Repo Into Your Own Git Server
-
Make an user in your internal git server for yourself
-
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 )
-
Create a group or organization called "puppet"
-
Create a repository in your git server called control-repo
-
Upload this control repository to your control repository
- https://github.com/npwalker/control-repo
- git clone --mirror https://github.com/npwalker/control-repo.git
- cd control-repo
- git remote set-url --push
- 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
Update Your Install To Point To The Control Repository
https://docs.puppetlabs.com/pe/latest/r10k_config_console.html
Setting Up Your Git Management System
Setting Up Gitlab
- Install Gitlab on a server by specifying laying down the following trusted fact the soon-to-be Gitlab server and then install the PE agent.
---
extension_requests:
#pp_role
1.3.6.1.4.1.34380.1.1.13: 'gitlab'
-
After the install of the agent completes and an agent run completes Gitlab will be installed.
-
After Gitlab is installed you may sign if with the
root
user and password5iveL!fe
-
Create a group called
puppet
( this is case sensitive )
-
Create a user called
r10k_api_user
and add them to thepuppet
group -
Create a project called
control-repo
and set the Namespace to be thepuppet
group
- If you have direct internet access from your Gitlab server you can also use the "Import project from" option to import this repo
- If you do not have direct internet access then wait a little bit and we'll get to that later
- Logout of root and login as the
r10k_api_user
- Go to profile settings -> account ( https://<your_gitlab_server>/profile/account )
- Copy the api token
mv hieradata/nodes/example-puppet-master.yaml hieradata/nodes/<fqdn_of_your_puppet_master>.yaml
- Open
hieradata/nodes/<fqdn_of_your_puppet_master>.yaml
- edit
gms_api_token
to be your api token - edit
git_management_system
to be 'gitlab' - You should not need to edit the
gms_server_url
- edit
Setting up Github
Not yet completed.
Setting up Stash
Not yet completed.
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.
Run r10k
- Run
r10k deploy environment —verbose
and watch it install the modules from your Puppetfile