DevOps combines software development and IT operations to shorten the development lifecycle while allowing for frequent, close-aligned releases with business objectives. It uses toolchains across coding, building, testing, packaging, releasing, configuring, and monitoring. Key principles include incorporating business needs, decomposing user stories methodically, and using clouds to improve computing. DevOps emerged from agile methodology and blends development and operations roles. Career paths can begin as system administrators who gain programming skills or developers who learn operations processes.

1. About DevOps in simple steps
Few words about hiring of DevOps by Ihor Odynets
Grid Dynamics ● Intro
● Description
● Principles
● History
● Dev
● Ops
● Tools
● Clouds
● Culture
● Trends
● Specifics
● Career path
● Key words
● Resources
● QA

2. Intro
Long-long time ago...
In far-far galaxy…
System administrators and IT specialist was in same position.
Operations in IT was in base level and development was easy - going. But...

3. Description
DevOps is a set of software development
practices that combines software
development (Dev) and information
technology operations (Ops) to shorten
the systems development life cycle while
delivering features, fixes, and updates
frequently in close alignment with
business objectives.
__________________________________________
TECHNICALLY MOSES WAS THE FIRST PERSON
WITH A TABLET DOWNLOADING DATA FROM
THE CLOUD.
But remember - DevOps it’s not only about clouds

4. As DevOps is intended to be a cross-functional mode
of working, those that practice the methodology use
different sets of tools—referred to as toolchains—
rather than a single one.These toolchains are
expected to fit into one or more of the following
categories, reflective of key aspects of the
development and delivery process:[
1. Coding – code development and review, source
code management tools, code merging
2. Building – continuous integration tools, build status
3. Testing – continuous testing tools that provide
feedback on business risks
4. Packaging – artifact repository, application pre-
deployment staging
5. Releasing – change management, release
approvals, release automation
6. Configuring – infrastructure configuration and
management, infrastructure as code tools
7. Monitoring – applications performance monitoring,
end-user experience
General overview

5. Principles vol.1

6. Principles vol. 2
DevOps - child of Agile
Agile view of principles in DevOps based on
“Just in time” solution - continuous processes.
Agile ideal system for R&D departments -
always in process.
Changes of requirements, tools or ideas take
new architecture of processes and solutions.
All process on the way but big chance of geps
and problems (risks).
Day after day this systems works better and like
next stage - stream of life (LIoT) - ( Life in
internet of things).

7. Principles vol. 3
1. Business drivers
have needs;
2. Methodology
helpful for
decomposition
of user stories;
3. DevOps collect all
parts of
solutions;
4. Clouds improve
computing and
performing;

8. History
Turing First site Social side of DevOps
Fortran Ben Trainor (Google) New way (and clouds)
ARPANET 1967-69? Flickr IoT and AI

10. Toolchain
Tools for
DevOps -
different parts
of toolchain
Different
solutions -
different ways

11. Tools vol.1 Dev- and -Ops

12. Tools vol.2
Docker is a tool
designed to make it
easier to create, deploy,
and run applications by
using containers.
Containers allow a
developer to package up
an application with all of
the parts it needs, such
as libraries and other
dependencies, and ship it
all out as one package.
Any Application
Any Infrastructure
Any Operating System
Any Orchestrator

13. Tools vol.3 mr. Jenkins

14. Clouds

15. Clouds vol.2 (Private clouds and VPC)
Private cloud refers to a model of cloud
computing where IT services are
provisioned over private IT infrastructure
for the dedicated use of a single
organization. A private cloud is usually
managed via internal resources. The
terms private cloud and virtual private
cloud (VPC) are often used
interchangeably.
This clouds can be in AWS or Google
or different clouds. Or not.

16. Culture

17. Trends

18. Career path (DevOps vs System administrators).
Most DevOps engineers start like
system administrators who have
learned programming tools, or
developers who have figured out
the intricacies of the operations
processes. It is desirable to have a
basic technical education, to
understand the issues related to
system administration and
automation of various tasks.
https://gridu.litmos.com/home/LearningPath/35005?r=Fals
e&ts=636903236083361835
Devops' job is to collaborate on a
high-level and ensure synergy in
each section of the company. A
sysadmin guy is more focused
on configuring, keeping up and
maintaining servers and
computer systems. ... Devops
guys can do everything a
sysadmin does, but a sysadmin
cannot do everything a devops
guy does
But remember: DevOps - not system admin!

19. Key words
Clouds
AWS, Amazon, GCP,
GoogleCloud, ORACLE,
IBMCloud, Azure,
“Microsoft Clouds”,
Sharepoint, SaaS,
PaaS, IaaS,
Deployment, Private
cloud, Community cloud,
Public cloud, Hybrid
cloud, VPC.
CICD
First line:
AnthillPro, Bamboo, Buildbot,
CruiseControl, GoCD (Go
continuous delivery), Hudson,
TeamCity, Travis CI, Visual
Studio Team Services,
FlexDeploy (Flexagon).
Bach, Python, Groovy
Second line:
CFEngine, Distelli, LCFG,
Otter, Version control, trunk,
staging, DO-178C, MPW,
CMake, OpenMake Software,
Premake
Config tools
Ansible, CFEngine,
ChefINFRA(Chef),,
Puppet, Saltstack,
Docker, PowerShell
DSC.
UNIX-systems and
networks
Linux, Ubuntu, Debian,
Centos, Redhat, Alpine

20. Q&A