devsnack/control-repo
1
0
Fork 0
Code Releases Activity
A control repository template
129 Commits 3 Branches 4 Tags 2.6 MiB
Ruby 41.1%
Puppet 28.6%
Shell 19.8%
Pascal 10%
PowerShell 0.5%
2c98a9264c
Go to file
Nick Walker 2c98a9264c Reduce the scope of the control-repo to mostly an example 
Prior to this commit, the control-repo was an example of the
structure of a control repo but it also included puppet code to
help setup code manager and instructions to get that all setup
in a very specific way.

This was great for users that wanted to follow those instructions
exactly but wasn't great for people just looking for an example to
start from.

After this commit, the control-repo will be just an example once
again and a new repo somehwere else will pop up to provide the
explicit instructions on how to use the example with code manager.

There are links added to puppetlabs/control-repo to a new repo
that will have a version of the code that once lived in
puppetlabs/control-repo
2016-03-29 15:53:10 -07:00
hieradata Reduce the scope of the control-repo to mostly an example 2016-03-29 15:53:10 -07:00
manifests Reduce the scope of the control-repo to mostly an example 2016-03-29 15:53:10 -07:00
scripts Update config_version to read r10k_deploy.json file 2015-12-18 09:24:27 -08:00
site Reduce the scope of the control-repo to mostly an example 2016-03-29 15:53:10 -07:00
.gitignore add .gitignore to ignore my example hiera file 2015-10-22 15:48:06 -07:00
environment.conf remove environment_timeout =0 from environment.conf 2015-10-28 11:36:44 -07: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 Reduce the scope of the control-repo to mostly an example 2016-03-29 15:53:10 -07: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 setup many Puppet Enterprise components. As the code increased, so did the complexity of the control-repo project. To reduce that complexity, as well as continue 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 Labs RampUp Program namespace within Github and can easily be re-connected to an existing control-repo if that is required (simply add the modules to the Puppetfile). Alternatively, if that previously-opinoinated control-repo is desired, it still exists on Github under the Puppet Labs RampUp 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 exists as 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 / 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

Coming soon!