1. Silliness
2. Unnecessary Capitalization
3. One picture of A Cat
How-to information will be relegated to linked github repositories to minimize the chances of demofail.
Attendees should expect to leave this talk being more comfortable allowing the Puppet Enterprise console to manage their infrastructure, and with some broad understanding of entirely code-based multi-repository methodologies incorporating PE.
linux sysadmin
puppet enterprise
systems thinking
transparency
austin puppet user group
govops
beard
beer
disclaimer: this is not a representation of my mental picture of management in general
Text
you do it to yourself, just you
you and no one else
but
vagrant oscar init
vagrant oscar init-vms -m master=puppetlabs/centos-6.5-64-nocm \
-a agent0=puppetlabs/centos-6.5-64-nocm \
-a agent1=puppetlabs/centos-7.0-64-nocm \
-a agent2=puppetlabs/ubuntu-14.04-64-nocm
vagrant up
note: this is the way to frustration
dropping opinion bombs
git clone https://github.com/moutons/howilearned-oscar.git
cd howilearned-oscar
bash getready
vagrant up master
vagrant up agent
vagrant ssh master
then, on the master
sudo su -
puppet module install zack/r10k
puppet apply /vagrant/git/howilearned-control/r10k_installation.pp
r10k deploy environment -pvvv
now you're ready to r10k like @glarizza told ya
As of PE 3.3.2
user:
admin@puppetlabs.com
pass:
puppetlabs
PE 3.7.0 changed to
user:
admin
pass:
puppetlabs
dem tabs tho
If Using PE 3.7.0 + remember to boost the master's memory in $(pwd)/config/roles.yaml)
wat
If Using PE 3.7.0 + remember to boost the master's memory in $(pwd)/config/roles.yaml)
wat
wat
If Using PE 3.7.0 + remember to boost the master's memory in $(pwd)/config/roles.yaml)
wat
wat