hashicorp / puppet-bootstrap Goto Github PK

A collection of single-file scripts to bootstrap your machines with Puppet.

License: Mozilla Public License 2.0

Shell 80.10% PowerShell 19.90%

puppet-bootstrap's Introduction

Puppet Bootstrap Scripts

This repository contains a multitude of single file scripts for setting up Puppet on a variety of machines.

Puppet is fantastic for managing infrastructure but there is a chicken/egg problem of getting Puppet initially installed on a machine so that Puppet can then take over for the remainder of system setup. This repository contains small scripts to bootstrap your system just enough so that Puppet can then take over.

Please contribute by forking and sending a pull request for your operating system.

The goal of this repository is to create a set of scripts that run on every version of every platform to set up Puppet.

Features of Each Script

Requires no parameters and runs without any human input, but can optionally take parameters to tune the packages the install and such. See each script for details on the parameters.
Uses only built-in software to install Puppet. These scripts have no external dependencies over the base install of their OS.
Installs Puppet agent and Facter.
Does not auto-start the Puppet agent service on the machine. Your bootstrap can choose to do this in addition to these scripts, if you'd like.

Using a Script

To use one of the scripts in this repository, you can either download the script directly from this repository as part of your machine setup process, or copy the contents of the script you need to your own location and use that. The latter is recommended since it then doesn't rely on GitHub uptime and is generally more secure.

If you do choose to download directly from this repository, make sure you link to a specific commit (and not master), so that the file contents don't change on you unexpectedly.

Contributing

Fork and pull request. Simple.

puppet-bootstrap's People

Contributors

Stargazers

Watchers

Forkers

mattr- jalogisch grossjo jcarley bionix glarizza oazmon gbitgit yoyossy rickychilcott laurentmoss boianmihailov anjshenoy pinterb gurteshwar ddrager opsgit mjroach rmsj mattiasgeniar davidgriffith kujilabs rodm miphip ibrimad grahamgilbert finn augustohp ktham petersellars kevinlowrie jeckhart michaelkrieg huit dillera mickengland blinkinglight biemond bitglue baijum ferventcoder ukabu lucciano wickedshimmy secoast00 cnsa rrudduck gavioto cloudvocacy zennro supasate bfeaver petems gtpuppet2014 jaredquinn abuxton aethylred zjfroot spacex genebean massiveclouds antonlindstrom marcusmyers adz msutter cstephs unicell joustava zouzias getvalkyrie hlangeveld jconover schrepfler zakdoek kian adambarthelson epitty1023 oxypwn osalkk randomnumber9 darkseed schkovich visualeyes burdara filirom1 kfowlks czhujer maelstrom168 ceh04 roister daosborne sebastian-kreis natemccurdy flavio-fernandes ludobonnet abulgatz lindsay-apitalent stagrlee miamioh biggiemac

puppet-bootstrap's Issues

Permission Error

I get this error when using this script

==> default: /tmp/vagrant-shell: line 1: /vagrant/puppet_bootstrap.sh: Permission denied
==> default: /tmp/vagrant-shell: line 3: puppet: command not found
==> default: /tmp/vagrant-shell: line 4: puppet: command not found
==> default: /tmp/vagrant-shell: line 5: puppet: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

my vagrantfile is as below

config.vm.provision :shell do |shell|
shell.inline = "/vagrant/puppet_bootstrap.sh;
mkdir -p /etc/puppet/modules;
puppet module install puppetlabs/git;
puppet module install puppetlabs/mysql;
puppet module install puppetlabs-tomcat;"
end

Add corresponding removal scripts

In some cases, such as Packer builds of Docker images, using Puppet for initial configuration is great. But since there's no intention of running Puppet after the initial build, its preferable to remove Puppet from the system. This is probably a simple one-liner for all the distros, but it'd be nice to have them all documented somewhere. For Debian/Ubuntu ones it'd probably just be:

apt-get purge -y --auto-remove puppet

Scripts should not blindly try to install puppet a second time over

It seems like the centos scripts are the only ones which try to verify if puppet is installed already, which would be true the second time puppet is ran, etc. All scripts should probably do that.

Licenses

Is it intended that these scripts remain the copyright property of the those who submitted them? If not, please can the contributors apply their appropriate licenses so that we know how we can use and/ or modify them.

what does this do

does this create infographics or is that puppet displaying what it does - very confused

Q: Why install RubyGems in addition to Puppet in ubuntu.sh?

Hi there,

Thanks for the great Puppet bootstrap scripts, they are very helpful indeed.

I was just looking through the one named ubuntu.sh and noticed the block at the bottom where you also install RubyGems. i.e.

# Install RubyGems for the provider
echo "Installing RubyGems..."
if [ $DISTRIB_CODENAME != "trusty" ]; then
  apt-get install -y rubygems >/dev/null
fi
gem install --no-ri --no-rdoc rubygems-update
update_rubygems >/dev/null

I am wondering why you do this? Not being that familiar with Puppet yet, I'm not really sure how RubyGems supports Puppet and why it is needed? I have looked around various docs but haven't yet found anything concrete.

Thanks for your time and thoughts.

Cheers,
Dan

Are these scripts current?

I noticed that the last update was over a year ago and the Ubuntu script mentions that it's compatible with Ubuntu 12.04!

Puppet 4 for CentOS

Hi,

I have added pull request #56 that updates CentOS scripts so that the latest Puppet 4 is installed from Puppet Collection 1 repository.

A few extra improvements:

Unified all CentOS scripts, they all now have a minor difference and should be compatible with their respective RHEL derivatives.
A better way to check if Puppet is installed. You can no longer rely on $PATH as puppet directory has changed in version and may not be available for root.
Added symlinks to puppet so that they are always in $PATH.

Using the current script you get the message:
"==> default: /tmp/vagrant-shell: 22: [: Illegal number:"
that is cause by this issue.

[0] https://wiki.debian.org/Shell
[1] https://packages.debian.org/dash
[2] https://github.com/hashicorp/puppet-bootstrap/blob/master/debian.sh#L22

CentOS: wget must be installed

The "wget" package must be installed before executing the following line

https://github.com/hashicorp/puppet-bootstrap/blob/master/centos_6_x.sh#L22

Similarly, for the other versions of CentOS.

wget not installed on all CentOS boxes

Suggest using curl in the scripts instead, eg.:

curl --silent --output "${repo_path}" "${REPO_URL}" 2>/dev/null