Main Menu

2. The first step in the DevOps methodology

https://www.udemy.com/course/devops-fundamentals-tools-technologies-and-infrastructure/learn/lecture/10554426#overview

What is DevOps?

• Is a software development methodology that stresses intercommunication between Software developers and other personnel, such as Testers, Designers, QA and Operations.
• The term was initially coined to describe the collaboration between Developers and Operations, so the two words were combined to create DevOps.
• DevOps is a direct descendant of the Agile software methodology
• First used in 2008
• Goal to leverage collaboration throughout development lifecycle.

What DevOps Does

• Blurs lines of responsibility
  • Developers write code
  • Operations sets up servers
  • Now these are shared
• Improved efficency
• How to measure still debated

How it started

• Evolution of software
  • Initially, Developers wrote programs to complete a task.  Operations procured the hardware to run these programs.
  • Now Software can emulate and virtualize
    • No need for Operations once the hypervisor is setup.
  • DevOps joins teams to analyze and review tasks that may require collaboration
    • Each team gets invested in different portions of other teams.
    • Teams take more ownership of the tasks they perform and understand how their roles impact other teams

3. Brief history of the traditional SDLC (Sofware Development Life Cycle)

https://www.udemy.com/course/devops-fundamentals-tools-technologies-and-infrastructure/learn/lecture/10554434#overview

• Simple programs ran on mainframes
• Programming languages developed, hardware prices dropped.
• Systems became more complex (Cloud hosted, load balancing)

Original Process

• Gather the requirements from Business Analyst (Blue prints)
• Developers work as a team to perform programming and testing tasks
  • Using whatever programming language is at their disposal.
• After designed, passed over to QA group to ensure stability and meets specifications
  • QA generally has little information about software development or hardware
  • Issues found (or imagined) are passed back to Devs to fix
  • Rinse and repeat until all issues resolved.
• Code is passed to Operation for installation
  • Operations provides the compute and network
  • This usually includes maintaining the OS/patching
  • Also little to no knowledge or care about software development

STOPPED TAKING NOTES HERE

4. Problems solved using DevOps

5. Rethinking the SDLC with DevOps

6. Factors driving DevOps acceptance

7. New challenges of the DevOps methodology