Downloaded 176 times
Uploaded byMike McGarr
Infrastructure as Code (BBWorld/DevCon13)
This document discusses infrastructure as code and provides examples using tools like Chef, Vagrant, and Jenkins. It summarizes building a Jenkins server from source control using Chef recipes to install Java, add users, and install packages to set up the service. It emphasizes best practices like version control, testing, and treating infrastructure like code.
More Related Content
Similar to Infrastructure as Code (BBWorld/DevCon13)
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
Infrastructure as Code (BBWorld/DevCon13)
- 1. Infrastructure as Code Mike McGarr,Director of Learn DevOps Blackboard, Inc.
- 2. ABOUT ME Mike McGarr Directorof Learn DevOps Blackboard Inc. michael.mcgarr@blackboard.com I have been at Blackboard for 8 months. Software Engineer for 12+ years Founder of the DC Continuous Integration, Delivery and Deployment Meetup
- 3. LEARN DEVOPS TEAM Purpose:Provide development support to the rest of Learn‟s Product Development (PD) team. Includes: • Build/Release Engineering • Manage Enterprise Applications • Manage Data Center • Help desk for PD
- 4. ENTERPRISE APPLICATIONS Problems: • Manually managed •Little/No Version Control • No history/context
- 5. DATA CENTER Problems: • Fewknew how to run CM • Fewer knew how to fix CM tool • Lots of firefighting to resolve CM issues
- 6.
- 7. INFRASTRUCTURE AS CODE Automate thecreation and maintenance of servers (to the farthest extent possible) • Build from source control • Utilize open source tools • Ensure testability A practice popularized by the DevOps movement.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. VAGRANT $> vagrant boxadd $> vagrant init $> vagrant up $> vagrant ssh $> vagrant provision $> vagrant suspend $> vagrant destroy
- 20.
- 21.
- 22.
- 23. INSTALL JDK VIA CHEF 1.Include Java default recipe (recipe/default.rb) 2. Add cookbook dependency (metadata.rb) 3. Download Java cookbook 4. Run „vagrant provision‟
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34. VERSION CONTROL https://www.youtube.com/watch?v=ZDR433b0HJY $> gitinit $> git add . $> git commit –m “new commit” $> git remote add git:git@... $> git push origin master Chef/Puppet Server is not Version Control!!
- 35.
- 36. UNIT TESTING chefspec (ruby gem) https://github.com/acrmp/chefspec Testa cookbook fast and from anywhere spec/default_spec.rb
- 37. CONTINUOUS TESTING guard (ruby gem) https://github.com/guard/guard When alocal file changes, then run unit tests. Guardfile
- 38. INTEGRATION TESTING test kitchen (ruby gem) https://github.com/opscode/test-kitchen Runand test cookbook in Vagrant or LXC container. .kitchen.yml
- 39. STATIC ANALYSIS foodcritic (ruby gem) http://acrmp.github.io/foodcritic/ Styleguide and find defects in cookbook source code.
- 40. CONTINUOUS INTEGRATION Jenkins (Java app) When achange is checked in, then run tests and deploy to Chef Server.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46. LEARN TO PROGRAM Opsacting like developers… Learn the language! Learn the environment: • rvm • rbenv • gems • bundler
- 47. THANK YOU! Mike McGarr Directorof Learn DevOps Blackboard Inc. michael.mcgarr@blackboard.com @jmichaelmcgarr http://earlyandoften.wordpress.com
Editor's Notes
- #6 2000+ virtual machinesHundreds of learn instancesHundreds of test agentsIn-house CM tool
- #7 Constantly fighting firesResulted from high technical debtImpact to team:High WIPContext switchingLarge backlogImage: http://www.ctif.org/CTIF-Commission-Rescue-and-Fire
- #9 If your question is Puppet vs. Chef, the answer is yes.Advantages:Provide DSL (easier to read)Community for helpOpen source, corporate backingHandles errors, etc.
- #10 ConvergenceIdempotence
- #12 Manual changes lead to driftGoal: Avoid Configuration Drift
- #13 Fully capable of rebuilding a server from scratch at any timeEasier than troubleshooting unique issuesImage: http://coverlaydown.com/2013/02/the-phoenix-rises-on-coming-back-and-moving-forward/
- #14 The logical evolution of Phoenix Servers
- #15 DevOps is not about tools, it’s about culture.…however, tools can change behavior, …and behavior change leads to culture change.
- #21 Ruby Wrapper to VirtualBox (and others)Simplifies Local VM integrationUnderstands CM ToolsPlugin API
- #22 Chef client installed on machine<Vagrant boots machine, passes runlist to client>Describe Chef Server briefly
- #33 Discuss how some developer best practices can/should apply to ops.
- #34 Depict how changes are made:Change locally, in VagrantUnit test changes/regressionsRun Integration TestsCommit to Git (pre-commit hook to ensure incremented version)Jenkins runs testsIf successful, publish to Chef Server (staging environment)Staging environment updates (daemon or push)Manual testing…if all goodPromote change in Jenkins to production environmentServers update (daemon/push)
- #35 Communication mechanism
- #37 Requires:Updates to GemfileTo Run: bundle install && bundle exec rspec --color --format documentationUnit Tests: FIRSTFastIndependentRepeatableSelf-VerifyingTimely
- #39 Runs
- #43 Common gotcha…Removing a resource from
- #44 Script has explicit OS dependencies
- #45 Don’t forget to backup data prior to upgrade.