-DevOps Principles -DevOps Goals -Advantages and Disadvantages -DevOps and Agile -DevOps Tools -Why DevOps?

1. Under supervision of: Eng. Basma

2. o Eman Abdel-Gawad
o Eman Abdelmohsen
o Fatma Alzahraa Omar
o Gehad Elsayed
o Marwa Ahmed
Team
Members

3. Agenda
o Introduction
o DevOps Principles
o DevOps Goals
o Advantages and Disadvantages
o DevOps and Agile
o DevOps Tools
o Why DevOps?

4. Dilemma
o Modern Architectures are harder to manage
and scale using traditional processes.
o Cloud provides SERVICES but not PRODUCTS.

5. Solving
Dilemma in
Traditional
Way

6. Solving
Dilemma in
Traditional
Way

7. Solving
Dilemma in
Traditional
Way

8. Solving
Dilemma in
Traditional
Way

9. Solving
Dilemma in
Traditional
Way

10. Solving
Dilemma in
Traditional
Way

11. Solving
Dilemma in
Traditional
Way

12. Solving
Dilemma in
Traditional
Way

13. Solving
Dilemma in
Traditional
Way

14. Solving
Dilemma in
Traditional
Way

15. What is
DevOps?
o DevOps is a culture movement that
encourages great collaboration (teamwork)
to maintain building more quality software
more quickly with more reliability.

16. What is
DevOps
NOT?
o A role, person or organization
o Something only administrators do
o Something only developers do
o Tools

17. DevOps
Principles
o System thinking
o Amplify feedback loops
o Culture of continual experiment and learning

18. DevOps
Goals
o The goal of DevOps is very simple; it is to
make a company more money. list the
following reasons for adopting DevOps
practices:
- Increases net profit.
- Increases return on investment.
- Increases cash flow.

19. Advantage
of DevOps
o Removing barriers to getting useful
features.
o Removing the bottlenecks, conflicts, and
risk from the lifecycle between business
decision and customer outcome.
o The DevOps focus on fast deployment,
continual improvement, and automation
naturally forces collaboration with security
teams.
o Increased time efficiencies.

20. Advantage
of DevOps
o Ability to Identify, Respond and Improve
Business Needs.
o Movement Comes from Open Source.
o Covers the *entire* Application Life Cycle.
o Faster time to market.
o Putting control back into the hands of the
business.
o Smooth deployment for new features

21. Disadvantage
of DevOps
o Tools are brand new to the market or are
open-sourced.
o Relying on an external Infrastructure as a
Service (IaaS) or Platform as a Service
(PaaS) provider. This reliance reduces
control and visibility at the hardware and
network layers.
o Complicate the tracking of hardware
assets over time.

22. DevOps
and Agile
That's fundamentally not true as well.
DevOps is actually highly related to Agile
development processes. So, as we can see,
Agile introduced the concept that we need
to iterate in software development, that
we need to move through our cycles in an
iterative fashion, that we need to have
incremental changes and adapt and react
to change quickly and flexibly to make
o DevOps is Agile:

23. DevOps
and Agile
o DevOps is an Extension of Agile
Thinking?
the DevOps answer to that was to embed
operations into the development process.
Take experts from the operations teams and
put them into the product team. Make them
involved in every decision.
And when DevOps came on the scene, the
primary idea was remarkably similar, to
embrace constant delivery, to embrace
testing, to embrace operations.

24. o Operations
IT operations include system administrators,
database administrators, network engineers,
infrastructure architects, and support
personnel.
DevOps
and Agile

25. DevOps
and Agile

26. o Code [Version control]
o Build and deploy
o Test
o Monitor
Tool
Categories

27. Tools You
Must
Have in
Your
DevOps
Toolchain

28. Tools You
Must
Have in
Your
DevOps
Toolchain

29. Tools You
Must
Have in
Your
DevOps
Toolchain

30. Tools You
Must
Have in
Your
DevOps
Toolchain

31. Testing is a critical part of the handoff between
development and IT operations. Successful Agile
teams using DevOps practices fully integrate testing
into their software development lifecycle.
How
Testing
Fits into
the
DevOps
Toolchain

32. A test-driven development system creates confidence
that when all of the automated tests pass, the code is
good to go. Successful DevOps toolchains include a
fully automated test harness that can signal to both
development and IT operations teams when code
that’s in development and code on running systems is
passing (or failing) their tests.
How
Testing
Fits into
the
DevOps
Toolchain

33. o
o bring in talented testers.
o then deploy them wisely.
o Make sure they test API services for business logic
and processes to maximize the benefits of
automation.
Improve
testing
inside
your
Agile
environ
ment

34. Why
DevOps?
Customer
Requirements
Dev and
Testing Team
Operation

35. Development Operations
Change
»Developers introduce
changes
»They try to
implement every new
techniques introduced
»Change is the
enemy for
Operations
»Changes can lead
to instability
Why
DevOps?

36. »Difficult to integrate tools
»Less interest in learning each others
tools
»Different implementation of similar
tools
Why
DevOps?
Confusion

37. Development Operations
Sends out files
based on
requirements
Manually hacks the scripts
received and changes the
configuration files to reflect
changes in production which
could potentially lead to an issue.Why
DevOps?
During Deployment

38. Operations Development
Developer gave faulty
artifacts.
All the files are fine, the
error is because of some
other issue
Why
DevOps?
Loss Work

39. After deployment, QA
sees some anomalies
and raises defects
Developer realizes that
correct files was not
deployed
Operations Development
Why
DevOps?
After Deployment

40. Why
DevOps?
Benefits Of DevOps
o Continuous software delivery
More deploys means faster time-to-market
and continual improvement.
o More stable operating environments
You don’t have to choose stability versus new
features.
A single team is responsible for delivering new
features and stability.

41. Why
DevOps?
Benefits Of DevOps
o Less complex problems to fix
Because change sets are smaller.
o Faster resolution of problems
Because team members don’t need to wait
for a different team to troubleshoot and fix
the problem.

42. Thanks for Paying Attention