04/26/2013 ChefConf Day 2

by Gene Kim on

#chefconf

PS: My talk here at #chefconf on "Why Everyone Needs DevOps Now & DevOps Patterns" will be today at 1:45pm. See you there!

Up: Adam Jacob, Chief Community Officer, Opscode

  • .@adamhjk: "Opscode is 5 yrs old"
  • .@adamhjk: "We care about DevOps and continuous delivery; we care about how quickly we can deliver to customers"
  • .@adamhjk: "Why do people like GE who build planes and trains care about DevOps? Why?" /cc @bmc_devops
  • .@adamhjk: "
  • @jdeamattson: #ChefConf @adamhjk Everyone he talks to, every role, all they care about: 1. DevOps and 2. Continuous Delivery! Why?
  • .@adamhjk: "Globalization: integrtn in commodity, capital/labor markets: took 40 yrs for container ships to mv 70% of seatrade
  • .@adamhjk: "It took only 22 yrs for Internet access to reach 78% of North America; 75% of Thxgvg purchases were online
  • .@adamhjk: "
  • @chipadeedoodah: #ChefConf @adamhjk “If you wanna see people fight like they fight about devops, ask economists to define globalization.”
  • .@adamhjk: "When I wrecked my car, entire car insurance process was done online; never talked to a real person. It was awesome
  • .@adamhjk: "For my entire professional career, I've never cashed a paycheck; all direct deposit
  • .@adamhjk: "Let's talk about bananas in Uganda: studied perishable crops & cell phones: cell phone use from 46% to 70%, 2003-05
  • .@adamhjk: "Who showed up? Traders, who knew prices of bananas, transacting w/farmers, who want to sell them; Uber for bananas?
  • @jdeamattson: #ChefConf @adamhjk Software is the interface for consumption. This is what driving both fo these trends...
  • @jdeamattson: #ChefConf @adamhjk Now it the opportunity to use cell phones to create UberNana! Everyone's Private Banana Trader...
  • .@adamhjk: "Every technology that previously impacted only internal business functions now directly supports customer interactions
  • .@adamhjk: "DevOps is being driven by inexorable, global, macroeconomic forces" and h/t to @patrickdebois (+100)
  • @chipadeedoodah: #ChefConf @adamhjk: “Devops isn’t about us deciding to be better at what we do. It’s about external forces pushing us to what we MUST do.”
  • @gmiranda23: @adamhjk "The global economy will never go through ITIL" lulz
  • .@adamhjk: "Sam Walton, Wal-Mart: 'The goal as company is to have customer svc that is not just the best, but legendary"
  • .@adamhjk: "Jeff Bezos, Amazon: 'in physical world, poor cst svc causes person tells 6 friends; online, they tell 6000 friends
  • .@adamhjk: "#devops & continuous delivery enable us to build the best customer experience"
  • .@adamhjk: "1) Winners have strong cultures of personal empowerment & accountable; Google, Facebook: 'we're all responsible'"
  • .@adamhjk: "If you have strong reliance on decision making, you don't have property #1; if you have architect who doesn't code, you don't have it
  • .@adamhjk: "2) Winners treat failure as a learning opportunity, not as dangerous thing to be avoided
  • .@adamhjk: "3) Winners hv Service Oriented Arch; easy to partition along failure domains, scale, segregate work for dev
  • .@adamhjk: "Phil Dibowitz, Facebook: 'The #1 thing we can't do is get in people's way"
  • .@adamhjk: "4) Winners are addicted to data on internal perf & cust perception; don't waste time arguing
  • @DataCenterTT: RT @TomWalatTT: #IT surfaces from the back room to take the helm http://t.co/cOmxgKhx3x @PariseauTT #ChefConf #Chef #Puppet
  • @zanshin: Don't confuse existing structures for hard business requirements.
  • (Anyone notice something really strange with the @adamhjk's org chart? It doesn't match actual flow of work...)
  • @julian_dunn: If failure is something to be learned from and not feared, we need to make the failure blast radius smaller, IMO. #Chefconf
  • .@adamhjk: "They found a corner of the business, practiced continuous delivery, & went wider & wider, changing the biz"
  • .@adamhjk: "Use tooling to institutionalize culture; your current tools probably reflect culture & world economy 20 yrs ago
  • .@adamhjk: "Every failure lacked one or more of the previous
  • @geekubed: RT @julian_dunn: If failure is something to be learned from and not feared, we need to make the failure blast radius smaller, IMO. #Chefconf
  • .@adamhjk: "Tools do matter, maybe as much as culture; use git, even though it's hard;
  • @chrisfarnham: Tooling is culture institutionalized. Think about the behavior you want to engender and build tools that enable it. Culture>tools
  • @mattscoble: "Tooling is culture institutionalized."
  • .@adamhjk: "If you can't close your eyes and see the business changed
  • @russellcardullo: #chefconf @adamhjk "Your choice of scm affects available workflows". Having used clearcase and sourcesafe in the past couldn't agree more.
  • .@adamhjk: "If biz response is 'I don't want chg, I'm ok w/drifting slowly to fail', then pushing chg may jeopardize career
  • .@adamhjk: "If your biz doesn't get it, just quit; everyone in this room is hiring, and they get it." (Interesting)
  • .@adamhjk: "You are the only people on the planet who can transform your business; there are no reserve troops"
  • .@adamhjk: "Your business leaders don't know the details"
  • .@adamhjk: "Your knowledge is the critical knowledge"
  • @chipadeedoodah: #ChefConf @adamhjk: “If you build a Continuous Delivery Ferrari and (the business) is only ready for a Yugo, you’re going to crash & burn.”
  • @jdeamattson: #ChefConf @adamhjk We are the people creating world our children and children's children will live in; take this responsibility seriously
  • @craig_tracey: @adamhjk "If your CEO doesnt understand and you dont want to convince him, fuckin quit, because everyone in this room is hiring"
  • @mary_grace: there is no "secret science." if you want to transform your business... do it! and if you're not allowed to, quit.@adamhjk #ChefConf
  • @rberger: @adamhjk Keynote was AWESOME. Nailed big themes tying together DevOps, Continuous Delivery and Global Transformation #Chefconf
  • @julian_dunn: RT @gmiranda23: @adamhjk "The global economy will never go through ITIL" lulz

Jason Stowe, Cycle Computing

  • .@jasonastowe: "I'm here to recruit you. Not for a job. I'm here to recruit you for a cause"
  • .@jasonastowe: "[in prior yrs in high performance computing], researcher had to wait for computing" (showing pile of svrs for 26K core cluster)
  • .@jasonastowe: "had to wait for servers, find space for them, finding cooling, configure it
  • .@jasonastowe: "Innovation bottleneck: researchers/scientists hv to size questions to infrastructure you have"
  • .@jasonastowe: "mainframs, vax, pc, beowolf clusters, centralized cloud"
  • .@jasonastowe: "experiment/test and analyze phase takes most time; like compile/link for dev"
  • .@jasonastowe: "Cycle time between experiments in large-scale HPC jobs often take nearly a year
  • @chipadeedoodah: RT @jdeamattson: #ChefConf @jasonastowe HPC clusters are too small, except when they were too large and you were paying for resources didn't need.
  • Wow. @jasonastowe: "Last yr, we built 50K-core cloud we built for 3 hours; 12 yrs of computing for $14K. Today, only $2500
  • .@jasonastowe: "This yr, we built 10.6K-instance cluster in 2 hrs for cancer target; ran on 1 chef 11 svr
  • .@jasonastowe: "My cause: not about optimizing process: it's about doing things we've never been able to do before
  • .@jasonastowe: "We can do 1) better science (not restricted to last yrs hardware), 2) faster science (do jobs fast)
  • .@jasonastowe: "Lack of access to compute lengthens clinical trials, prevents pharmaceuticals from getting to market
  • .@jasonastowe: "@ablythe: "Monte Carlo wait time is to scientists what the compiler wait time is to the software engineer." @jasonastowe
  • .@jasonastowe: "Big 10 Pharma: built 10,6K cluster in 2 hrs, ran 40 yrs of science in 11h for $4k (old way: $44MM proj)
  • .@jasonastowe showing what a 10K node cluster looks like: "everyone will get Retina displays from now on"
    https://pbs.twimg.com/media/BIywOhoCAAMzEtF.jpg
  • .@jasonastowe: "30K core run; 10 yrs of compute in 8 hrs for $10k; found 3 compounds now in web lab testing"
  • .@jasonastowe: "Lessons: 1) capacity is not an issue; 2) hw = sw; 3) testing is important; we do lots of small runs before large runs
  • .@jasonastowe: "Spent over $1mm on test runs
  • .@jasonastowe: "Servers are not houseplants that you name & nurture; they're wheat (you seed, grow, reap, burn)"
  • .@jasonastowe: "Use case: Gene Expression analysis req N^2 comparison within 78 TB stem cell RNA samples;
  • .@jasonastowe: "That was a 1MM compute hour job; 115 yrs of computnig in 1 week: $20K; 8-10K core cluster
  • .@jasonastowe: "If you started this job in 1880 on first computer, it would have finished in 2012, when Gangnam Style came out"
  • @BATidwell: "At what scale do you need to use Chef?" "Yes." #ChefConf #dontloveyourserver
  • @jtimberman: $ knife node list | wc -l 10599

Jason Stowe talking at #chefconf about one of Cycle Computing’s clusters
* .@jasonastowe: "When you contribute to chef, you're helping accelerate science"
* @julian_dunn: "knife node list | wc -l" --> 10599 @jasonastowe. Awesome. #ChefConf
* @geekubed: Ditto! ‏Amazing. RT @tamayoduck
Thanks @jasonstowe for bringing science to #ChefConf... Really compelling use cases for compute automation

Up: How A Mouse Became a Chef - Disney Chris Putonen, Brian Scott, Steven Wagner

  • @stormtrooperguy: No pics or video at the Disney keynote. Hmmmmm
  • @mary_grace: RT @nathenharvey: Picture of a picture #chefconf. http://t.co/i7OAuTlIjy
  • @andrewsmhay: I fear that an army of Twitterers live-tweeting the Disney talk is more dangerous than a few pics #ChefConf
  • Putonen: Excited to hear about their talk about continuous delivery pipeline.
  • Putonen: "Legacy IT ops is painful; lots of tedious manual steps, lots of shell scripts to deployment, outages, etc.
  • Putonen: "QA signs off on deployment, we deploy, and everything blows up. We're no different."
  • Putonen: "We not only have silos, we have silos within silos; (e.g., ESPN vs Disney corporate vs. everyone else)
  • Putonen: "Devs went Agile, resulting in IT Ops like deer in highlight; they not only went Agile, they went rogue (AWS!)
  • Putonen: "We were a BladeLogic shop; how do we xform org;
  • @julian_dunn: "... rogue developers swiping their corporate credit cards at Amazon" - Chris Putonen from @Disney, #ChefConf
  • Putonen: "we wanted open source,
  • Putonen: "start up small/simple ala Eric Ries; my 1st instinct was large waterfall project, which was doomed to fail
  • Putonen: "Instead, start very small, pivot, using continuous delivery techniques: build/measure/learn
  • @jonathan_thorpe: Chef was a DevOps catalyst at Disney. #chefconf #devops
  • Putonen: "We picked sr systems engineer SWAT team: I needed ppl & I wanted them to take kool-aid back to their teams
  • @wolf31o2: Undertaking small changes leads to mediocrity
  • Putonen: "Lots of training: Orlando, Bristol, LA from Opscode; why? not enough chef rockstars; every deserves right to learn cool stuff
  • @julian_dunn: Putonen of @Disney says the big monolithic project plan to implement #Opschef doesn't work. #ChefConf
  • Putonen: "Road shows and demos: Disney Corp, Parks and Resorts, ESPN; held Hack Days to help create templates
  • Putonen: "Oh, no. Futurama was canceled again this week." (Oh, no!)
  • Putonen: "Evangelize, communicate, have fun"
  • Putonen: "Lessons learned: 1) don't be afraid of ruby if u're a sysadmin"
  • Putonen: "Lessons learned: 2) we're all becoming Devs" (profound) "we have git repos for cookbooks"
  • Putonen: "Lessons learned: 3) change takes time; longer than we thought it would take, but it's ok" (200 ops/dev using chef)
  • Putonen: "We now have hundreds of product app cookbooks; 4000 chef nodes; automated cookbook testing framework
  • Putonen: "OS patching, change control, monitoring, F5"
  • Putonen: "why do I need chef for LAMP when I have perl? How much time do u spend in chg control, in F5 changing things; instant convert
  • Putonen: "...and now we need chef licenses for another 1000 nodes as we roll out to more data center.."
  • @jassinpain: RT @jtimberman: “Just enough ruby for Chef” http://t.co/iRjbNvfgh7 #ChefConf
  • Putonen: now showing first continuous integration for OS patching
  • @rberger: @DisneyChefQs Keynote is a great story of DevOps adoption and they're going to show code, YAY! Culture & Tools #Chefconf

  • Haha. Wagner: "describing Mavel XP: 'no more grabbing tarball, putting it into perforce, scp into yadda yadda'" (crowd laughs)

  • Wagner: "Dev: 'yea totally, we devs don't want that either!'

  • Wagner: "How do we get dev to stop checking stuff into his local Peforce repo? We're using artifactory

  • Wagner: "For orchestration, we're using #rundeck; we love it" /cc @damonedwards

  • Golly. Wagner's slides and builds are so pretty... Envious...

  • @chipadeedoodah: #ChefConf Disney talk reinforcing my opinion that artifact repo is an essential piece of CD pipeline. Wishing for better options than Maven.

  • @rberger: @DisneyChefQs Keynote continued awesomeness. Showing how they got started with Chef for deploying Marvel XP Game service! #ChefConf

  • Wagner: "Here's how we built continuous integration for chef.." (this is awesome)

  • Wagner: "Source control: apps, containers, infrastructure: switched to github enteprise; used LDAP for logins

  • Wagner: "Stood up artifact repository: artifactory in beginning, but switched to nexus; used for all envs for build/deploy

  • Wagner: "Rundeck: delegates & schedules: deployments, maintenance, forensics; originally just a replacement for cron

  • Wagner: "config mgmt: deploys and audits; source of truth, cross platform

  • @newgoliath: #chefconf "gotta respect that archive repo"

  • Wagner: "ingredients: src ctrl, continuous integ, artifact repo, orechestration, config mgmt

  • Scott: "Sites using chef: disney.com; go.com; spoonful.com (drupal 30MM view/mo), disneycareers.com; Disney Infinity (game)

  • Scott: "Change ctrl: all change orders and chg req goes into service desk; plugin automatically creates chg order"

  • Scott: "Network Location plugin find out where this node lives"

  • Scott: "MOTD handler; @julian_dunn: . @Disney also wrote a network location plugin for Ohai to store DC location, VLAN, VLAN name as auto attribs #ChefConf

  • @ericreeves: knife-servicedesk? Automated change orders? HOLY SHIT. MY BRAIN JUST IMPLODED WITH AWESOME.

  • @julian_dunn: . @Disney also wrote a custom LWRP to interact with F5s #ChefConf

  • @juliandunn: Disney also has a nexusfile resource LWRP (similar to @RiotGames' nexus cookbook LWRPs) #ChefConf

  • @julian_dunn: Many good ideas and utilities from Disney, but sad that they can't contrib back to the community. #ChefConf

  • @miah_: RT @ohlol: WE DONT ALLOW COMPILERS BUT LOL RUBY INTERPRETER

  • @VigilantGuy: What I learned from #chefconf Tweets: b the Automator not the Automated

  • @glennodonnell: “@RealGeneKim: Putonen: we're all becoming Devs ... we have git repos for cookbooks" #chefconf Profound indeed! Infra is code, so it's true!

On testing...

  • Wagner: "on testing: cookbook updates led to failures; (e.g.,make chg, all QA clusters fail); showed need for testing/CI
  • Wagner: "We built remy to built test every platoform, env, data center, app"
  • Wagner: "We used jenkins to drive chef testing/CI; plugins: github pull req, groovyaxis, multijob, warnings
  • Wagner: "sanity checks;
  • @gondoi: Emerging theme for #ChefConf this year: testing cookbooks. Lots of options.
  • @SidChoudhury: #chefconf is full of culinary goodness - cookbook, recipe, knife, foodcritic, test kitchen, berkshelf, spiceweasel, yardchef ... hungry!
  • @bryanwb: neat to know that disney uses chef-workflow written by @deliciousgravy
  • @julian_dunn: They plan to refactor to use chef-workflow - interesting. https://t.co/FTk3bkf6Ul #ChefConf
  • @julian_dunn: "The great thing about Remy as an automated testing service is that the acronym is RATS" #ChefConf
  • @rberger: @DisneyChefQs Name for their Elastic Scaling framework: Elastic Girl! & Cookbook Test Framework Remy #Chefconf
  • @jonathan_thorpe: RT @jdeamattson: #ChefConf Don't roll your own Testing Framework; contribute to Test Kitchen which is pue unadulterated awesomeness...
  • @t3kb0t: Epic talks from @thephild, @resetexistence and @jasonastowe at #chefconf. These guys are changing the game.

Up: Level Up the Change in Your Enterprise - Nordstrom Robert Cummings (@opsrob)

  • .@opsrob: "Does big, established status quo always win? No! Here's how to win"
  • .@opsrob: "Book 'The Other Side Of Innovation'; status quo is a performance engine, optimized for repeatable, predictable
  • .@opsrob: "Ex: You're Ford Motors: 1965 Mustang: a success, so you won't make drastic changes; Until 1970s gas crisis: Mustang II
  • .@opsrob: "Oh, that Mustang II. That's one ugly car" (haha)
  • .@opsrob: "Without that performance engine, your company wouldn't be around to fund your project: reliable, repeatable, messy
  • .@opsrob: "@fak3r: #chefconf Did Mustang make a fastback in 1965? Always thought it was later, not the first year... too picky?
  • @geekubed: RT @jdeamattson: #ChefConf It is difficult for an Org to prepare for punctuated equilibrium in future, and deliver repeatable and predictable performance.
  • @geekubed: RT @jdeamattson: #ChefConf It is difficult for an Org to prepare for punctuated equilibrium in future, and deliver repeatable and predictable performance.
  • .@opsrob: "Strategy: build small dedicated team outside of perf engine: take small piece of work, be accountable for success
  • .@opsrob: "Staff it with top talent, allow them to break the rules; they have no safety net of being inside perf engine
  • (Holy cow. I am loving @opsrob talk. I need to read the book "Other Side Of Innovation")
  • .@opsrob: "talking about #phoenixproject and the Brent Effect. Wow, that's cool."
    https://pbs.twimg.com/media/BIzHfTTCEAEadQ4.jpg
  • .@opsrob: "Learning from #phoenixproject: performance engineers & bureaucracies are very resilient, can work w/o Brent
  • @jdeamattson: #ChefConf Org is performance engine; don't want to disrupt. To enable change, create dedicated team outside of performance engine.
  • @jdeamattson: #ChefConf The Brent Effect from The Phoenix Project. Hat-tip to @RealGeneKim
  • .@opsrob: "Don't be afraid to take Brent out of the performance engine; it's scary, but they'll survive w/o him"
  • @michaelpgoetz: "The Brent Affect" <-- I mention this almost daily.. We should all be Brent... #ChefConf
  • @michaelpgoetz: "The Brent Affect" <-- I mention this almost daily.. We should all be Brent... #ChefConf
  • @mike_chavez: Had a great chat with the awesome Mr. @RealGeneKim.
  • @geekubed: Agree, fun. MT ‏@RealGeneKim @opsrob: "talking abt #phoenixproject & Brent Effect. Wow, that's cool." #chefconf http://t.co/ECVP3C1uB3
  • .@opsrob: "Project works. Now what? 1) back into Performance Engine; 2) Rotate others into dedicated team for next big chg"
  • .@opsrob: "3) Or grow the dedicated team, shrink the Performance Engine (for big transformational projects)
  • .@opsrob: "@julian_dunn: . @OpsRob is talking about being transparent up-front about what you want to accomplish, in order to get buy-in. +1. #ChefConf
  • @hippiehacker: "I invite people to be where I am, without forcing them to leave where they are." Powerful words from @metaxis #ChefConf
  • .@opsrob: "Our dedicated team: 1) get chef running, 2) define workflows, 3) put into perf engine
  • .@opsrob: "1st attempt: tackled one file that is hand-edited; even that didn't work, b/c it was so customized; demoralizing!"
  • .@opsrob: "2nd attempt: automated build of one server w/horrible history. now can build w/1 person"
  • .@opsrob: "tackle something just hard enough to show progress"
  • .@opsrob: "didn't embed person back into perf engine, so it wasn't adopted as thoroughly as should have been
  • .@opsrob: "3rd attempt: get Windows admins to build cookbooks, and put them back into perf engine, subsuming old process
  • .@opsrob: "4th project: create continuous delivery pipeline in 6 weeks; did weekly demos; locked team members in room
  • .@opsrob: "6 weekly demos are brutal. Don't do them on Fridays; don't do it w/3 wk daughter" (oh my)
  • .@opsrob: "Embrace your organization; Introduce something awesome; Share how you're doing it" (Nice!)
  • had ppl email SVP asking 'how can we help"
  • @julian_dunn: Advice from @OpsRob : don't start enterprise transformation projects when you have a newborn daughter. :-) #ChefConf
  • @dougireton: @opsrob is rocking his #chefconf keynote on Leveling Up Your Change

  • My updated notes of ChefConf Day 2 posted at http://scribes.tweetscriber.com/realgenekim/127

Who Says Elephants Can't Cook? How IBM and Opscode are changing the role of code in defining next generation infrastructures Mohammed Abdula, Mitch Hill

Gene Kim

  • @wolf31o2: RT @OpsRob: Definitely catch @realgenekim #chefconf presentation on replay, DevOps Patterns Distilled, it is awesome. Show it to your boss.
  • @andrewsmhay: I’ll be signing @RealGeneKim’s book for anyone that wants me to :P #ChefConf
  • @elbrum: RT @RealGeneKim: Putonen: "Lessons learned: 2) we're all becoming Devs" (profound) "we have git repos for cookbooks"
  • @jdeamattson: #ChefConf @RealGeneKim Imagine the impact of eliminating IT Failure on the future of the planet: $2.6 trillion for other stuff.
  • @OpsRob: Definitely catch @realgenekim #chefconf presentation on replay, DevOps Patterns Distilled, it is awesome. Show it to your boss.
  • @discoposse: RT @RealGeneKim: .@adamhjk: "You are the only people on the planet who can transform your business; there are no reserve troops"
  • @jdeamattson: #ChefConf @RealGeneKim Cost of IT @kevinkarwaski: @jhulten are there any digital Kanban boards you recommend? Would love to see your lightning talk as a full session next year!
  • Failure, Worldwide, Annually: $2.6 Trillion per year.
  • @jdeamattson: #ChefConf @RealGeneKim Allocate 20% of cycles to technical debt reduction.
  • @jdeamattson: #ChefConf @RealGeneKim Skill Mastery: better to practice 15 minutes a day vs. 3 hours once a week.
  • @jonathan_thorpe: The Third Way: Culture of Continual Experimentation and Learning - Erik in The Phoenix Project @RealGeneKim
  • @trobrock: RT @B1ackavar: "At the end of each sprint, we must have shippable code - and the environment it runs in" - @RealGeneKim
  • @dcnem: Show me your code has "Production Hygiene" before you can hand it to ops. Google policy. @realgenekim #ChefConf
  • @jdeamattson: #ChefConf @RealGeneKim "We found that when we woke up developers at 2 AM, defects got fixed faster than ever." Patrick Lightbody
  • @SometimesAlex: “We found that when we woke up developers at 2am, defects got fixed faster than ever.” #ChefConf
  • @wolf31o2: RT @jdeamattson: #ChefConf @RealGeneKim What is your lead time: from commit to running in production?
  • @dcnem: The First Way: Optimize for the next downstream step. @realgenekim #ChefConf
  • @jonathan_thorpe: At the end of a sprint have code deployed to a production like environment - agile sprint deliverable defined by @RealGeneKim
  • @B1ackavar: "At the end of each sprint, we must have shippable code - and the environment it runs in" - @RealGeneKim
  • @djbphaedrus: RT @andrewsmhay: “Every company is an IT company” - @RealGeneKim #ChefConf
  • @dcnem: Code committed but not running in production is inventory/WIP @realgenekim #ChefConf
  • @jdeamattson: #ChefConf @RealGeneKim To be clear about it, something big is happening. We are in a time of change.
  • @jdeamattson: #ChefConf @RealGeneKim What is your lead time: from commit to running in production?
  • @jdeamattson: #ChefConf @RealGeneKim How much of that is run time vs. queue time?
  • @dcnem: @realgenekim Decouple Deployment risk from Release risk. #ChefConf
  • @B1ackavar: Amazon - average of 1 deploy every 11.6 seconds. - @RealGeneKim
  • @jdeamattson: #ChefConf @RealGeneKim Just learned to not conflate 'deployments' with 'releases'; the two are different.
  • @zanshin: OH: Nobody wants to do fewer deploys.
  • @wolf31o2: RT @andrewsmhay: I wonder how @RealGeneKim’s going to live tweet his talk? :P #ChefConf
  • @jonathan_thorpe: Infosec people are the Star Trek red shirt guys @RealGeneKim
  • @jdeamattson: #ChefConf @RealGeneKim Spock is the developer; Scotty is Ops; and InfoSec, they are the guy in the Red Shirt :-)
  • @stormtrooperguy: No one invites Scotty to the meetings until the warp drives are already down. #ChefConf
  • @gargarxp: RT @SoberBuildEng: "Show me a developer not causing an outage, I'll show you a developer on vacation." -@RealGeneKim

Others

  • @tomduffield: "Every environment is production for someone" - Dan Nemec
  • @jchackert: RT @SoberBuildEng: "Dev is Production for everyone except people buying stuff." - @sascha_d
  • @rfutrick: RT @mipsytipsy: Slides for my mongodb #chefconf talk: https://t.co/bZV3Lxzgxk
  • @michaelpgoetz: RT @fnichol: This is so damn true /c @sascha_d #ChefConf http://t.co/BmNlgJhZyB
  • @tomduffield: RT @michaelpgoetz: "Vagrant gives you no excuse for not testing your recipes" #ChefConf @sascha_d
  • @ShipShowPodcast: RT @fnichol: Watching @sascha_d talking like a pro #ChefConf http://t.co/XsW0OVk0xb
  • @jonathan_thorpe: "Tools support the process that support the culture" - Aaron Suggs #chefconf #devops
  • @jdeamattson: RT @SoberBuildEng: "The ability to learn from another's mistakes is a sign of operational maturity." -@sascha_d
  • @devoptimist: "dev is production for the developers" @sascha_d Truth

Misc

  • @jamesdotcuff: "Utility HPC: Right Systems, Right Scale, Right Science!" @jasonastowe of @cyclecomputing up in 1hr! http://t.co/zyiwsNYtyC
  • @jbbrown: Good Luck today @OpsRob - Glad you're speaking at
  • +1! RT @jbbrown: Good Luck today @OpsRob - Glad you're speaking at
  • RT @jdeamattson: @adamhjk Everyone he talks to, every role, all they care about: 1. DevOps & 2. Continuous Delivery! Why?
  • RT @chipadeedoodah: @adamhjk “If you wanna see people fight like they fight about devops, ask economists to define globalization.”
  • RT @russellcardullo: "Your choice of scm affects available workflows". Having used clearcase & sourcesafe in past couldn't agree more.
  • RT @chipadeedoodah: @adamhjk: “If u build cont deliv Ferrari & (the business) is only ready for Yugo, u'r going to crash & burn.”
  • RT @ablythe: "Monte Carlo wait time is to scientists what the compiler wait time is to the software engineer." @jasonastowe
  • "Devs going rogue!" RT @julian_dunn: "rogue developers swiping their corp credit cards for AWS" Putonen from @Disney, #ChefConf
  • RT @julian_dunn: Putonen of @Disney says the big monolithic project plan to implement #Opschef doesn't work. #ChefConf
  • RT @jassinpain: RT @jtimberman: “Just enough ruby for Chef” http://t.co/iRjbNvfgh7 #ChefConf
  • RT @rberger: continued awesomeness. Showing how they got started with Chef for deploying Marvel XP Game service! #ChefConf

jjj
* @gmiranda23: RT @opscode: Deep dive into our work w/ our friends @IBM and @joyent from @theregister: http://t.co/ttZ7LYTRPu #ChefConf
jjj
RT @juliandunn: They wrote a network location plugin for Ohai to store DC location, VLAN, VLAN name as auto attribs #ChefConf
+1 RT @t3kb0t: Epic talks from @thephild, @resetexistence and @jasonastowe at #chefconf. These guys are changing the game.
@stormtrooperguy: IT core conflict: faster response while providing stable and predictable results. #ChefConf #paraphrased
@adamhjk: RT @kevsmith: Arista opening libraries, providers, resources, and cookbooks to let Chef manage their devices. Nice!
My favorite is http://leankit.com: free version avail! RT @kevinkarwaski: @jhulten are there any digital Kanban boards you like?
RT @tomduffield: "Every environment is production for someone" - Dan Nemec
RT @jchackert: RT @SoberBuildEng: "Dev is Production for everyone except people buying stuff." - @sascha
d
RT @tomduffield: RT @michaelpgoetz: "Vagrant gives you no excuse for not testing your recipes" #ChefConf @saschad
@jonathan
thorpe: "Over 10000 deploys and only 11% were to production" Aaron Suggs
RT @jonathanthorpe: "Over 10000 deploys and only 11% were to production" Aaron Suggs
Love it!!! RT @devoptimist: "dev is production for the developers" @sascha
d Truth