devsnack/control-repo
1
0
Fork 0
Code Releases Activity
A control repository template
146 Commits 3 Branches 4 Tags 2.6 MiB
Ruby 41.1%
Puppet 28.6%
Shell 19.8%
Pascal 10%
PowerShell 0.5%
124b1a2727
Go to file
Nate McCurdy 124b1a2727 config_version: Show the compiling master's name 
Prior to this, the config_version script just showed the commit ID of
the version of code being compiled. This commit includes the compiling
Puppet master's hostname and environment name in the config_version.
This is very useful for debugging when a Puppet master is failing and
you have multiple masters behind a load balancer.

The output of config_version now looks like this:

pupmaster01-production-ac9785273a10
2017-07-05 17:09:51 -07:00
hieradata Remove max_requests_per_instance since hiera-eyaml is fixed 2016-08-04 15:51:07 -07:00
manifests Provide permalink for filebucket deprecation (#43) 2016-10-26 07:46:56 -07:00
scripts config_version: Show the compiling master's name 2017-07-05 17:09:51 -07:00
site Removed old role 2016-06-14 14:37:43 +10:00
.gitignore add .gitignore to ignore my example hiera file 2015-10-22 15:48:06 -07:00
environment.conf Put local site modules first in modulepath 2016-11-08 12:57:46 -05:00
LICENSE Initial commit 2015-08-11 10:07:49 -07:00
Puppetfile Reduce the scope of the control-repo to mostly an example 2016-03-29 15:53:10 -07:00
README.md Add GitHub instructions 2016-11-08 13:47:29 -05:00

README.md

Table of Contents

Created by gh-md-toc

Where Did All The Previous Code Go?

Initially, the control-repo project began as a 'starter' template for anyone who wanted to get started with r10k. As time passed, and Code Manager was integrated into Puppet Enterprise, the scope of this project grew to include opinionated Puppet profiles to set up many Puppet Enterprise components. As the code increased, so did the complexity of the control-repo project. To reduce that complexity, as well as continuing to meet the needs of individuals who would like a more minimal template, this repository was stripped of anything other than the bare minimum files necessary to get started with a functioning control-repo.

All of the code that was previously in this repository still exists in separate repositories under the Puppet Ramp Up Program namespace within Github and can be re-connected to an existing control-repo if that is required by adding the modules to the Puppetfile. Alternatively, if that previously opinionated control-repo is desired, it still exists on Github under the Puppet Ramp Up Program namespace. This control-repo project will remain a template for anyone who would like a minimal 'starter' template.

What You Get From This control-repo

This repository is a template control-repo that can be used with r10k or Puppet Enterprise Code Manager.

The major points are:

  • An environment.conf that correctly implements:
    • A site directory for roles, profiles, and any custom modules for your organization.
    • A config_version script.
  • Provided config_version scripts to output the commit of code that your agent just applied.
  • Basic example of roles/profiles code.
  • Example hieradata directory with pre-created common.yaml and nodes directory.
    • These match the default hierarchy that ships with PE.

Copy This Repo Into Your Own Git Server

GitLab

  1. Install GitLab.

  1. After GitLab is installed you may sign if with the root user and password 5iveL!fe.

  2. Make a user for yourself.

  3. 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 or laptop).

  1. Create a group called puppet (this is case sensitive).

  1. Add your user to the puppet group as well.

  2. Create a project called control-repo, and set the Namespace to be the puppet group.

  3. Clone this control repository to your laptop/workstation:

  • git clone <repository url>
  • cd control-repo
  1. Remove this repository as the origin remote:
  • git remote remove origin
  1. Add your internal repository as the origin remote:
  • git remote add origin <url of your gitlab repository>
  1. Push the production branch of the repository from your machine up to your git server
  • git push origin production

Stash

Coming soon!

GitHub

  1. Prepare your local git client to authenticate with GitHub.com or a local GitHub Enterprise instance.
  1. Create a repository called control-repo in your user account or organization. Ensure that "Initialize this repository with a README" is not selected.

  1. Make a note of your repository URL (HTTPS or SSH, depending on your security configuration).

  2. Clone this control repository to your laptop/workstation:

  • git clone <repository url>
  • cd control-repo
  1. Remove this repository as the origin remote:
  • git remote remove origin
  1. Add your internal repository as the origin remote:
  • git remote add origin <url of your github repository>
  1. Push the production branch of the repository from your machine up to your git server
  • git push origin production