2013/08/22: PuppetConf Day 1

by Gene Kim on

#puppetconf

Up: Luke Kanies, Puppet Labs (@puppetmasterd):

  • ask your questions to him here: http://t.co/cm6QiEw5e8

  • @PuppetConf: .@puppetmasterd taking questions in his keynote, ask here: http://t.co/cm6QiEw5e8 #puppetconf #puppetize

  • @todd_heft: Feeling like Geppetto at

  • @cwebber: OH Shell Scripts and Bubble Gum

  • .@puppetmasterd: "We've made wifi here just good enough for email, & no more than that." (Truth. Wifi is pretty bad here. :)

  • @binford2k: Last year we had too many good talks and not enough time to see them all & this year we decided to make it dramatically worse!

  • @nerdguru: Puppet cloud partner NASCAR slide #PuppetConf http://t.co/EPlbpYik70

  • @nerdguru: Puppet cloud partner NASCAR slide #PuppetConf http://t.co/EPlbpYik70

  • @VMTrooper: @puppetmasterd sharing the *aaS companies leveraging #Puppet #PuppetConf #puppetize http://t.co/md25M114Aj

  • @gmacisme: "Most admins, there's a special kind of bridge you get to live under." @puppetmasterd

  • "Be more agile, help change the culture"

  • @Aethylred: RT @chorankates: 'The more backward compatible we are, the slower we are' @puppetmasterd #puppetconf #truth

Up: Gordon Rowell, Site Reliability Manager, Google: "Why Did We Think Large Scale Distributed Systems Would Be Easy"

  • Rowell: "At Google, we have rules that you never break"
  • Rowell: "the rules: make the service scale"
  • @ProfitBricksUSA: Gordon Rowell's keynote on complexity of large scale systems at #PuppetConf begins now http://t.co/3eHBWGA18b
  • Rowell: "understand all the layers of the system" (not just the app, look at the database, disks)
  • Rowell: "use every OS upgrade to clean up cruft" (very nice)

Up: Will Farrington, "Puppet At Github" (Yes!!)

  • .@wfarr: "puppet-lint enforces the puppet labs style guide"
  • @stack72: Listening to @wfarr talk about the use of puppet at @github is awesome. Sounds like an amazing place to work!
  • I'm loving watching @wfarr describing using git to commit puppet modules to build git. Not recursive, but still...
  • .@wfarr: "augeas is one of my favorite tools: we describe all our mysql configurations using it"
  • .@wfarr: "we're big fans of continuous integrations; we commit, jenkins runs, triggers git pull request"
  • .@wfarr: "we've invested lots into test parallelization; it remembers how long tests took before to help w/scheduling"
  • .@wfarr: "we branch deploy everything: Test, Stage, Prod? No, we have 181 environments. But only 5 are live/running"
  • .@wfarr: "We taught Hubot to automatically merge the master branch fore allowing any branch to deploy"
  • .@wfarr: "puppet roles: webkit dev, enterprise sales staff (?!?), core ruby dev, core git dev, frontend designer, .."
  • .@wfarr: "all puppet output goes to chat"
  • @stack72: I also love that @github have given 100% of employees full access to their puppet repo with 100% trust
  • .@wfarr: "upgrading to Puppet 3.x is urgent. it's being end of lifed nxt month; it's painful, been talking abt it for a year
  • .@wfarr: "
  • @stack72: Puppet is helping make everyone at @github more interested in the ops space. This is incredible
  • @stack72: Puppet is helping make everyone at @github more interested in the ops space. This is incredible
  • .@wfarr: "We still do lots of automation outside puppet; bash/ssh & for loops still so compelling; want mcollective in future
  • .@wfarr: "Musing: all software is terrible (anyone who's worked w/software long enuf knows this); exception? HAproxy" (haha)
  • .@wfarr: "'No software is better than no software' -- rthomayko; lesson: don't rely on complex software"
  • .@wfarr: "'the plumbing doesn't matter when all you care about is the porcelain; that's why ChatOps is so important to us"
  • See @wfarr's talk: http://speakerdeck.com/wfarr
  • .@wfarr: Q: "probs w/everyone having repo access?" A: "not in practice; everyone sees pull req, scrutinizes it before commit

Up: "Vagrant + Rouster At Salesforce . com", Connor Horan-Kates

  • Horan-Kates: "Initial team: 6 engrs: 3 system engrs, 2 QA and 1 dev; no ruby experience on either side: mostly perl/shell"
  • Horan-Kates: "Tools we used: rspec, rspec-puppet; why? we googled 'puppet test' & those came up" (haha)
  • Horan-Kates: (he's senior member of technical staff, Quality Engineer)
  • Horan-Kates: "Desires: move from perforce -> git; local git-commit hooks: puppet-lint, rspec, rspec-puppet (didn't ask dev)
  • Horan-Kates: "vagrantfile: 39 lines; called it 'piab': 'puppet in a box"
  • Horan-Kates: "Created vagrant base images for every server in salesforce.com; 39 lines of vagrant code vs. millions of $$
  • Horan-Kates: "Now we're using: jenkins, test-unit; Test::More; mock racadm; vagrant now 237 lines"
  • Horan-Kates: "We're working on rouster: porting salesforce::piab tests; I use it everyday, but it's long way from 1.0
  • Horan-Kates: "Moving from vagrant VMs to include physical hardware env to enable better validation
  • Horan-Kates: "Many devices (load balancers, storage) can't be emulated in vagrant"
  • Horan-Kates: "@jeffsussna: RT @RealGeneKim: Horan-Kates: "we googled 'puppet test' & those came up" #puppetconf << DevOps needs SEO too
  • @mitchellh: Hearing about how Vagrant is used across SalesForce. Had no idea they used it so heavily!
  • @davemangot: .@chorankates dropping into the ruby debugger during #rouster demo!
  • @mikemarod: Rouster looks awesome … Can actually verify that Puppet did what you wanted and not just that it ran successfully #PuppetConf
  • .@mikemarod: "Salesforce moving to all RHEL; using object model: no more shelling out;
  • Haha. I love acronyms: @chorankates alluding salesforce team calls salesforce,com "SFDC". Get it? @mreferre: By far and large the most intriguing presentation at #puppetconf by @botchagalupe
  • Haha. @chorankates: "Want to help? We want an awesome logo for Rouster!"
  • .@chorankates: "Vagrant has had 3 awesome logos; we've had none! But that will change!" (haha)

Up: Mitchell Hashimoto, "Multi-Provider Vagrant: AWS, VMware and more" (@mitchellh)

  • .@mitchellh:
  • @Aethylred: Vagrant installers are current, the gem is way behind!
  • @Aethylred: "I hear you like virtual box."
  • @Aethylred: Why other Vagrant providers? Virtual box is good at its job and it works but under load it just... disappoints you.
  • .@mitchellh: "Use case: vagrant can run puppet for CI"
  • @SoberBuildEng: "Honestly, VirtualBox is Bad" -@mitchellh (Keep telling people this & they never believe me until they do… and then OMG DO THEY)
  • .@mitchellh: "Vagrant Use case #2: develop locally, test remotely"
  • .@mitchellh: "Vagrant inside Vagrant: run vmware inside of LXC"
  • @stack72: Another good use of Vagrant is for acceptance tests #puppetconf http://t.co/77tstr2xBG //cc @mitchellh
  • .@mitchellh: "examples: old way: 8 vagrant boxes on each dev laptop; switched to 1 big vmware box, parceled out w/LXC to dev"
  • .@mitchellh: "Most amount I've ever done is installed vagrant inside of vagrant, 8 levels down. Then kernel panicked"
  • .@mitchellh: "vagrant box list now shows provider"
  • .@mitchellh: "@tonycollander: "Fun note, VMware can actually run inside VMware... So one day I run eight deep". Geeky and fun with @mitchellh :)
  • .@mitchellh: "Packer automaticlaly creates machine images for multiple providers, turning into docker-capable imgs
    • AWS, VMware, Digital Ocean
  • .@mitchellh: "Use case: prod and dev are different
  • .@mitchellh: "Use case: vagrant up takes too long; ie, vagrant destroy takes so long that you're not treating as disposble
  • .@mitchellh: "Lots of anti-image stigma: devops likes to villify images"
  • @Aethylred: The Vagrant file can include multi-provider configs allowing the handling of provider specific features yet maintain portability
  • .@mitchellh: "Why images villified by #devops? Gold images used to be the way; quarterly or worse; blessed by one person
  • .@mitchellh: "Modern config mgmt made it easy to build from scratch
  • .@mitchellh: "Machine images have tons of benefits: super fast infrastructure deploys; web svr: puppet 5m; images: 10 sec
  • .@mitchellh: "I have many sites where I store images and use them for a long time; used puppet only once to create imgs"
  • @Aethylred: RT @chadothompson: @mitchellh “Build your hipster kernel and put it on top of an LTS release”
  • @rclilly: RT @tonycollander: "Multi-Provider Vagrant: AWS, VMware and More". Best talk yet at #puppetconf w/ @mitchellh
  • @georgemcintosh: @mitchellh talk on Packer was cool. We have Veewee again, but without the suck
  • @chanezon: #PuppetConf @mitchellh talk on Vagrant & Packer was great. Just wish there were a --provider=[azure] option in addition to VMware & AWS:-)

Up: James Fryman, Github: "Building Data Driven Infrastructure"

  • @intjonathan: .@jfryman's follow-along link: http://t.co/8Kdo1yyfMM
  • Haha. @jfryman: "Let's face it. Wifi on planes really isn't Internet. It's something less" (As bad as conference wifi. :)
  • .@jfryman: "Business people think clouds are magic. But it's all run by us. We're the Meat Cloud"
  • .@jfryman: "I want to make all stuff that I do all day go away (automation) so I can be at home. #beerops
  • @xaeth: "We (the devs/ops people) are the Meat Cloud" @jfryman
  • @byron_miller: Mmm meat cloud and beer ops
  • @johnmorr: OH from @jfryman at #puppetconf: the "meat cloud," the people making the "cloud" work
  • Very funny. RT @johnmorr: @jfryman at #puppetconf: the "meat cloud" the people (dev and ops) who are making the "cloud" work
  • .@jfryman: "gpanel is our cmdb at github; oops. "cmdb" is sort of a dirty word." (haha. So not fair. :) #itil #devops
  • .@jfryman: "we use fog to provision all our environments, incl AWS; and gpanel"
  • .@jfryman: "puppet is the controller
  • .@jfryman: "
  • @Aethylred: Why isn't your system consuming its own metrics/monitoring data? It is machine readable after all?
  • .@jfryman: "Most tasks need to be automated; how much time did that add to my day? I love #chatops!"
  • .@jfryman: "All things must be deployable with a text file"
  • .@jfryman: " @Aethylred: Everything must be deployable from text files.
  • .@jfryman: "Big fail: When u over-copy/paste in puppet, creating config drift inside your config mgmt tool"
  • .@jfryman: "puppetdb is awesome; we created nagiosdb to auto-create thousands of small config files for nagios@frozenfoxx: "SQL Injection as a Service." #puppetconf omg, lolwut?!
  • .@jfryman: "Utopia, we have arrived!" Haha@wombleton: RT @Aethylred: What will we do when we automate our jobs? Something more interesting.
  • @mortsa: RT @puppetlabs: "If you can't #automate it, don't do it." - Gordon Rowell, Site Reliability @Google.

Misc

  • @Aethylred: Hmm having issues attaching new devices to the WiFi
  • Hahaha! RT @DevOpsDave: Hotel wifi at a tech conference saturates faster than strip joints during a Republican convention
  • @pdxmph: I am @nigelkersten, THE GREAT AND TERRIBLE! #PuppetConf http://t.co/XgOBSUcG7D
  • @ahpook: Awesome turnout for our #PuppetConf 5k! https://t.co/Dr82owBR3y http://t.co/0DJ7M4n9HW
  • @alexanderfortin: Watching #puppetconf streaming keynote with work buddies http://t.co/nphF3De2cE
  • @madgreek65: Packed house @ #puppetconf #devops http://t.co/1oNF4K8BmE
  • @DevOpsDave: First sad face I've seen at #puppetconf #conferencefail http://t.co/w1fdrLYAJD
  • @a_perilli: Our research showed that Puppet adoption propagates within orgs from bottom up. Exactly like VMware spread in its early days. #PuppetConf
  • Some might have advised that drinking 5 espressos this morning was unwise. Maybe they're right... Hands are shaking...
  • Everyone say 'hi' to @patrickdebois, the grandfather of DevOps! :)

  • Watch #puppetconf streaming link here: http://t.co/nphF3De2cE

  • @bakaster: Best advice I've heard this year. "Break things... In a controlled environment"

  • Agreed! RT @stack72: Listening to @wfarr talk abt use of puppet at @github is awesome. Sounds like an amazing place to work!
    RT @stack72: Puppet is helping make everyone at @github more interested in the ops space. This is incredible

  • @Aethylred: APIs That have 'create' for first instance and 'modify' for subsequent changes break idempotency

  • @walidshaari: RT @robynbergeron: .@addvin "our own IT dep't uses Puppet - a big part of how we manage our infrastructure at Red Har"

  • @walidshaari: RT @robynbergeron: .@addvin "our own IT dep't uses Puppet - a big part of how we manage our infrastructure at Red Har"

  • @_kmwhite: RT @jbronn: So, Cisco uses Puppet, Salt, and Fabric to deploy #heterops

  • Hahaha RT @jeffsussna: RT @RealGeneKim: Horan-Kates: "we googled 'puppet test' & those came up" #puppetconf << DevOps needs SEO too

  • @RealGeneKim: I've posted my notes from #PuppetConf Day 1' posted at http://t.co/h92o0maH5O

  • Love it. RT @davemangot: .@chorankates dropping into the ruby debugger during #rouster demo!

  • @moritacocoa: RT @a_perilli: Google finally got to the bottom line #PuppetConf: "If you can't automate, don't do it":
    http://t.co/SaVUlLBbmO
    http://t.…

  • RT @mreferre: By far and large the most intriguing presentation at #puppetconf by @botchagalupe

  • RT @tonycollander: "Fun note, VMware can actually run inside VMware... One day I run eight deep". Geeky & fun w/@mitchellh :)

  • RT @intjonathan: .@jfryman's follow-along link: http://t.co/8Kdo1yyfMM

  • @sjoeboo: once again, @grim_radical 's #puppetconf talk is my highlight of the day.

  • RT @xaeth: "We (the devs/ops people) are the Meat Cloud" @jfryman
    Very funny. RT @johnmorr: @jfryman at #puppetconf: the "meat cloud" the people (dev and ops) who are making the "cloud" work
    RT @Aethylred: Everything must be deployable from text files.
    Haha. Holy cow. RT @frozenfoxx: "SQL Injection as a Service." #puppetconf omg, lolwut?!
    RT @wombleton: RT @Aethylred: What will we do when we automate our jobs? Something more interesting.