DevOps. Building a Continuous Delivery Pipeline

Transcription

1 DevOps Building a Continuous Delivery Pipeline

2 Who Am I Bobby Warner Founder &

3 What is the goal?

4 Infrastructure as Code Write code to describe our infrastructure Never manually execute a command on a Linux server Support multiple primary Linux distributions with different package managers Ubuntu uses apt, Centos uses yum

5 Continuous Integration Checking code into source control kicks off a build Builds automatically run tests Builds automatically publish results

6 Continuous Delivery Creates all infrastructure components required Picks up build artifacts from CI server and deploys to the infrastructure environment(s) Supports automatic releases or scheduled releases based on business needs

7 Continuous Delivery No longer SSH ing in to patch/configure servers Rather we release versions of our infrastructure Everything is stored in source-control

8 Process I thought DevOps was about getting Ops and Developers to work together? Yes, but this presentation is focused on tools

9 What are the tools?

10 Tools Git VirtualBox Vagrant Chef Jenkins

11 Git

12 Git Distributed version control that is now ubiquitous

13 Enterprise Git Atlassian Stash GitHub Enterprise

14 Git Flow

15 Git Demo Create a repo Commit a change Alias

16 VirtualBox & Vagrant

17 VirtualBox Do all your development in VMs Mirror your production environment Eliminate cross platform issues between developers

18 Vagrant Describe the type of machine and software that needs to be installed Store this file in source code control

19 Chef

20 What is Chef? Configuration management tool for your infrastructure Used to automate how you build, deploy, and manage your infrastructure Infrastructure becomes as versionable, testable, and repeatable as application code

21 Chef Testing Test Kitchen (test harness runner) ServerSpec (integration testing) ChefSpec (unit testing)

22 ServerSpec

23 What is AWS OpsWorks? AWS version of Chef Server Uses chef-client in local mode which launches a local in-memory Chef server called chef-zero

24 Chef Demo

25 Jenkins

26 What is Jenkins? Continuous integration server Create and monitor execution of repeatable jobs Used with many different languages and frameworks Excluding.NET, see Microsoft Team Foundation Server

27 Importance of Jenkins Future of Jenkins is a federated master model. No more single master enterprise installs of Jenkins. Jenkins is the orchestrator for your CI/CD pipelines, if it s down you won t be pushing any code

28 Jenkins Fail Don t create Jenkins jobs by hand though as there is no way to scale, audit, or track changes!

29 Jenkins Win Use Jenkins Job DSL plugin!

30 Jenkins Job DSL Plugin allows the definition of a job with Groovy code Offers a useful set of functions to configure common Jenkins items Jobs (i.e. Groovy code) can be stored in source code control

31 Jenkins Job DSL You can peer review job changes You can write tests for jobs You can make and extend classes of jobs

32 Jenkins Job DSL

33 Jenkins Chef DSL Example for getting started with the Jenkins Chef cookbook and the Jenkins Job DSL Automate Jenkins Infrastructure and Job management

34 Wrap Up

35 Call to Action Install Chef DK and create a Chef Cookbook! Setup Jenkins if you don t already use it! Configure one job with the DSL plugin!

36 Conclusion Thanks for attending this talk! I hope you found it useful to get an introduction to some of the tools for DevOps! Please get in touch if you are looking for DevOps consultants here in the Twin Cities! [email protected]