Book Image

DevOps Bootcamp

By : Mitesh Soni
Book Image

DevOps Bootcamp

By: Mitesh Soni

Overview of this book

DevOps Bootcamp delivers practical learning modules in manageable chunks. Each chunk is delivered in a day, and each day is a productive one. Each day builds your competency in DevOps. You will be able to take the task you learn every day and apply it to cultivate the DevOps culture. Each chapter presents core concepts and key takeaways about a topic in DevOps and provides a series of hands-on exercises. You will not only learn the importance of basic concepts or practices of DevOps but also how to use different tools to automate application lifecycle management. We will start off by building the foundation of the DevOps concepts. On day two, we will perform Continuous Integration using Jenkins and VSTS both by configuring Maven-based JEE Web Application?. We will also integrate Jenkins and Sonar qube for Static Code Analysis. Further, on day three, we will focus on Docker containers where we will install and configure Docker and also create a Tomcat Container to deploy our Java based web application. On day four, we will create and configure the environment for application deployment in AWS and Microsoft Azure Cloud for which we will use Infrastructure as a Service and Open Source Configuration Management tool Chef. For day five, our focus would be on Continuous Delivery. We will automate application deployment in Docker container using Jenkins Plugin, AWS EC2 using Script, AWS Elastic Beanstalk using Jenkins Plugin, Microsoft Azure VM using script, and Microsoft Azure App Services Using Jenkins. We will also configure Continuous Delivery using VSTS. We will then learn the concept of Automated Testing on day six using Apache JMeter and URL-based tests in VSTS. Further, on day seven, we will explore various ways to automate application lifecycle management using orchestration. We will see how Pipeline can be created in Jenkins and VSTS, so the moment Continuous? Integration is completed successfully, Continuous Delivery will start and application will be deployed. On the final day, our focus would be on Security access to Jenkins and Monitoring of CI resources, and cloud-based resources in AWS and Microsoft Azure Platform as a Service.

Related Content you might be interested in

Current Title:

Small book image
DevOps Bootcamp
Mitesh Soni
May, 2017 | 312 pages
Small book image
Chef Cookbook
Matthias Marschall
Feb, 2017 | 268 pages
Small book image
Practical AWS Networking
Mitesh Soni
Jan, 2018 | 258 pages
Small book image
Learning Azure Functions
Manisha Yadav | Mitesh Soni
Sep, 2017 | 240 pages
Table of Contents (9 chapters)
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
DevOps Concepts and Assessment Framework
DevOps Concepts and Assessment Framework
Need for DevOps
How can DevOps culture evolve?
Importance of PPT - people, process, and technology
Why DevOps is not all about tools
DevOps assessment questions
Summary
2
Continuous Integration
Continuous Integration
Installing Jenkins 2
Creating and configuring Maven-based JEE web applications
Integrating Jenkins and SonarQube
E-mail notifications in Jenkins
Continuous integration using Visual Studio Team Services
Summary
3
Containers
Containers
Overview of Docker containers
Understanding the difference between virtual machines and containers
Installing and configuring Docker
Creating a Tomcat container
Summary
4
Cloud Computing and Configuration Management
Cloud Computing and Configuration Management
An overview of the Chef configuration management tool
Installing and configuring a Chef workstation
Installing knife plugins for Amazon Web Services and Microsoft Azure
Summary
5
Continuous Delivery
Continuous Delivery
Continuous delivery in Docker container using Jenkins Plugin
Continuous Delivery in AWS EC2 and Microsoft Azure VM using Script
Continuous delivery in AWS Elastic Beanstalk using Jenkins Plugin
Continuous delivery in Microsoft Azure App Services Using FTP
Continuous delivery in Microsoft Azure App Services Using VSTS
Summary
6
Automated Testing (Functional and Load Testing)
Automated Testing (Functional and Load Testing)
Functional testing using Selenium
Load testing using a URL-based test and Apache JMeter for Microsoft Azure
Summary
7
Orchestration - End-to-End Automation
Orchestration - End-to-End Automation
End-to-end automation of application life cycle management using Jenkins
End-to-end automation using Jenkins, Chef, and AWS EC2
End-to-end automation using Jenkins and AWS Elastic Beanstalk
End-to end aautomation using Jenkins and Microsoft Azure app services
End-to-end automation orchestration of application life cycle management using VSTS
Summary
8
Security and Monitoring
Security and Monitoring
Security in Jenkins and VSTS
User management in Jenkins
Monitoring Jenkins and Microsoft Azure
Summary

Why DevOps is not all about tools

Yes, tools are nothing. They are not that important a factor in changing the culture of any organization. The reason is very simple. No matter what technology we use, we will perform continuous integration, cloud provisioning, configuration management, continuous delivery, continuous deployment, continuous monitoring, and so on.

Categorywise, different tool sets can be used, but all perform similar operations. It is just the way that tool performs a certain operation that differs, else the outcome is the same. The following are some of the tools based on the categories:

Category

Tools

Build automation

Nant, MSBuild, Maven, Ant and Gradle

Repository

Git and SVN

Static code analysis

Sonar and PMD

Continuous integration

Jenkins, Atlassian Bamboo, and VSTS

Configuration management

Chef, Puppet, Ansible, and Salt

Cloud platforms

AWS and Microsoft Azure

Cloud management tool

RightScale

Application deployment

Shell Scripts and Plugins

Functional testing

Selenium and Appium

Load testing

Apache Jmeter

Repositories

Artifactory, Nexus, and Fabric

Let's see how different tools can be useful in different stages for different operations. This may change based on the number of environments or the number of DevOps practices we follow in different organizations:

If we need to categorize tools based on different DevOps best practices, then we can categorize them based on open source and commercial categories. The following are just some examples:

Components

Open Source

IBM Urban Code

Electric-Cloud

Build tools

Ant or Maven
or MS Build

Ant or Maven or MS
Build

Ant or Maven or MS Build

Code repositories

Git or Subversion

Git or Atlassian Stash or Subversion or StarTeam

Git or Subversion or StarTeam

Code analysis tools

Sonar

Sonar

Sonar

Continuous integration

Jenkins

Jenkins or Atlassian Bamboo

Jenkins or ElectricAccelerator

Continuous delivery

Chef

Artifactory and IBM UrbanCode Deploy

ElectricFlow

In this book, we will try to focus on the open source category, as well as commercial tools. We will use Jenkins and Visual Studio Team Services for all the major automation and orchestration-related activities.

Previous Section
End of Section 5
Next Section