Introduction to dev ops

DevOps
Software Development (Dev)
& IT Operations (Ops)
DevOps course by Abdul Rahim

What is DevOps?
DevOps is a culture which promotes collaboration between
Development and Operations Team to deploy code to production
faster in an automated & repeatable way. The word 'DevOps' is a
combination of two words 'development' and 'operations.'

– A set of practices intended to reduce the time between
committing a change to a system and the change being placed into
normal production, while ensuring high quality.
– DevOps can be defined as an alignment of development and IT
operations with better communication and collaboration.
– DevOps is the practice of operations and development engineers
participating together in the entire service lifecycle, from design
through the development process to production support.
DevOps Definition

History of DevOps
The concept of DevOps emerged out of a discussion
between Andrew Clay and Patrick Debois in 2008. They
were concerned about the drawbacks of Agile and wanted
to come up with something better. The idea slowly began
to spread and after the DevOpsDays event held in Belgium
in 2009, it became quite a buzzword.

DevOps Main Objectives
– Speed
– Rapid Delivery
– Reliability
– Scale
– Improved Collaboration
– Security

Software Development Life
Cycle (SDLC)
SDLC is a process followed for a software project, within a
software organization. It consists of a detailed plan
describing how to develop, maintain, replace and alter or
enhance specific software. The life cycle defines a
methodology for improving the quality of software and the
overall development process.

Waterfall Model
Requirement
Design
Implementation
Testing
Deployment
Maintenance

Agile Methodology

DevOps Best Practices
The following are DevOps best practices:
– Continuous Development
– Continuous Integration
– Continuous Delivery/Continuous Deployment
– Microservices
– Infrastructure as Code
– Monitoring and Logging
– Communication and Collaboration

Continuous Development
– The first phase of the DevOps lifecycle is where the planning and
software coding takes place. The planning involves understanding
the vision of the project and envisioning a software based on
those perceptions.
– The code can be written in any language on an integrated
development environment (IDE), but it is maintained by using
Version Control tools. Maintaining the code is referred to as Source
Code Management (SCM).

Continuous Development
IDE
Eclipse
NetBeans
MS Visual Studio
IntelliJ IDEA
Xcode IDE
Android Studio
Building
Ant
Maven
Gradle
SCM
GitHub
SVN
GitLab
Mercurial

Continuous Integration
– This stage is the heart of the entire DevOps life cycle.
– Continuous integration is a software development practice where
developers regularly merge their code changes into a central
repository, after which automated builds and tests are run. The
key goals of continuous integration are to find and address bugs
quicker, improve software quality, and reduce the time it takes to
validate and release new software updates.
– Jenkins is a very popular tool used in this phase.

Continuous Integration
CI Tools
TeamCity
Jenkins
Travis CI
CircleCI
Bamboo
GitLab CI

Continuous
Delivery/Deployment
Continuous delivery/deployment is a software development practice
where code changes are automatically built, tested, and prepared for
a release to production. It expands upon continuous integration by
deploying all code changes to a testing environment and/or a
production environment after the build stage. When continuous
delivery is implemented properly, developers will always have a
deployment-ready build artifact that has passed through a
standardized test process.

Continuous
Delivery/Deployment
CI Tools
Puppet
Chef
Ansible
SaltStack

Continuous
Delivery/Deployment

Microservices
– Microservices - also known as the microservice architecture - is an architectural
style that structures an application as a collection of services that are
– Highly maintainable and testable
– Loosely coupled
– Independently deployable
– Organized around business capabilities
– Owned by a small team
– The microservice architecture enables the rapid, frequent and reliable delivery
of large, complex applications. It also enables an organization to evolve its
technology stack.

Microservices

Microservices
PROS
– Freedom to use technology
– Responsible of single business capability
– Separate Ownership & Tracking
– Frequent Software Releases
– Parallel releases & feature requests
– No Single Point of Failure
– Each service scaled independently
– No Delay for Developers
– Can be reused
CONS
– Complex architecture
– Single functionality becomes
distributed so latency
– Difficult to trace a call and which
Microservice is taking time
– A good amount of integration/e2e
tests are required
– Data division for Microservices
– Difficult to maintain transaction safety

Microservices
– 500+ Microservices

Infrastructure as Code
– Infrastructure as code is a practice in which infrastructure is
provisioned and managed using code.
– Infrastructure and servers can quickly be deployed using
standardized patterns, updated with the latest patches and
versions, or duplicated in repeatable ways.
– Deploy everything in an automated way or through scripts
– Main purpose is to have state & deployment manifests in any
central place

Infrastructure as Code
Tools
Terraform
Chef
Ansible
SaltStack
GitOps

Monitoring and Logging
– This is a very crucial stage of the DevOps life cycle where you continuously
monitor the performance of your application.
– Continuous monitoring helps in sustaining the availability of services in the
application.
– It also determines the threats and root causes of recurring system errors.
– Security issues get resolved and problems are automatically detected and fixed.
– Compared to the software development teams, the IT operations teams are
more involved in this phase. Their role is pivotal in supervising user activity,
checking the system for unusual behavior, and tracing the presence of bugs.

Monitoring and Logging
Tools
Sensu
Splunk
Nagios
NewRelic
ELK Stack

Communication and
Collaboration
– The most important part of DevOps
– DevOps was introduced due to conflicts between Developers & Operations team
blaming each other
– Physically bringing together the workflows and responsibilities of development and
operations.
– Maintain visibility across organizations for various events such as deployments,
bugs, server downtimes, etc.
– Give continuous feedback to respective stakeholder
– If feature is correct and deployed, take feedback from consumer
– If issue in code, give feedback to developer
– If issue in infrastructure, communicate to teams as soon as possible

Containers and Virtual
Development
– Package Software into Standardized Units for Development, Shipment and
Deployment
– Containers are a solution to the problem of how to get software to run reliably
when moved from one computing environment to another. This could be from a
developer's laptop to a test environment, from a staging environment into
production, and perhaps from a physical machine in a data center to a virtual
machine in a private or public cloud.
– Instead of virtualizing the hardware stack as with the virtual machines
approach, containers virtualize at the operating system level, with multiple
containers running atop the OS kernel directly.

Development
Containers
Docker
Vagrant
Virtual
Vmware
HyperV
Oracle VirtualBox

Development

Cluster Management
(Scalability)
– Clearly, containers are an exciting new advancement in creating
and delivering applications.
– However, controlling a vast deployment of containers presents
some complications.
– Containers must be matched with resources. Failures have to be
resolved quickly.
– These challenges have led to a concurrent demand for cluster
management and orchestration tools.

Cluster Management
(Scalability)
– Cluster management can vary from low-involvement activities
such as sending work to a cluster to high-involvement work such
as load-balancing and availability.

Cluster Management
(Scalability)
Tools
Docker Swarm
Google Kubernetes
Apache Mesos
Fleet – Core OS

Introduction to dev ops

More Related Content

What's hot

Similar to Introduction to dev ops

Recently uploaded

Introduction to dev ops