devops overview

1
DevOps - Overview
2
Introduction

• DevOps is a term emerged from the combination of
  Development and Operations. The role of a DevOps
  engineer is to automate all the operational work
  in the way that a developer would do. The idea is
  to encourage frequent releases to increase
  quality and get early feedback.
• Hence, according to me, the main two objectives
  of DevOps are increasing the speed and quality
  the deliveries.

3
Characteristics of DevOps

• Ability to write code beyond simple scripts.
• Focus on stability and uptime.
• Extra focus on moving between states -
  
• In dev land, I have situations when the end
  result of a particular feature was analysed on
  its ow merit, without taking into consideration
  how a system can be moved from its desired future
  state. DevOps pays extra attention to this
  problematic area.

4
How DevOps works?

• DevOps integrating targets item conveyance,
  consistent testing, quality testing, feature
  advancement, and upkeep discharges so as to
  enhance dependability and security and give
  quicker improvement and arrangement cycles.

5
What are the DevOps tools?

• Nagios (and Icinga)
• Monit
• ELK Elasticsearch, Logstash, Kibana by means
  of Logz.io.
• io
• Jenkins
• Docker
• Ansible
• Collectl
• Git (GitHub)

6
Advantages

• There are several clear advantages to be had from
  DevOps. Collaboration can help alleviate
  deep-rooted problems such as the industry
  acceptance that projects will tend to run late,
  won't work properly or will cost more than
  anticipated. Prior to DevOps as a solution, this
  would mean that many projects would go back to
  square one. With DevOps, a solution is suggested
  early on which means those problems are handled
  and worked through, saving time and money.
• Also, if any issues arise, they can be dealt with
  by team members who can take ownership and solve
  the problem.

7
Why DevOps is so important?

• Shorter Advancement Cycles, Quicker Development
• Decreased Organization flaws, Rollbacks, and Time
  to Recuperate
• Enhanced Correspondence and Coordinated effort
• Expanded Efficiencies
• Decreased Expenses and IT Headcount

8
Disadvantages

• Once you're invested in the idea of DevOps
  there's a temptation to take it a step further
  and abandon the idea of specialists altogether
  and encourage your developers to develop skills
  in multitasking as QAs, system administrators and
  release managers etc.
• DevOps is also naturally suited to a development
  team that is already agile, i.e. fast iteration
  cycles, flexible scope model and dedicated long
  term resource allocation etc. If your team
  currently works in something such as a fixed
  scope model, then introducing DevOps will need
  wider business support to change the way the team
  works, otherwise it will feel like progress has
  slowed and functional targets are no longer being
  met.

9
DevOps Technical Challenges

• Environment provisioning
• Manual testing
• No DevOps center of excellence
• Test data
• Manual deployments
• Planning in a DevOps environment
• DevOps and suppliers
• DevOps and governance
• No integrated tools architecture
• Manual releases

10
Conclusion

• Very few companies reach the hyper-growth stage
  at which point this post is directly applicable.
  For many companies, a pure DevOps model built on
  modern cloud native primitives may be entirely
  sufficient given the number of engineers
  involved, the system reliability required, and
  the product iteration rate the business requires.

11
THANK YOU

• For More Information https//www.besanttechnologi
  es.com/