Javascript on your browser is not enabled.

Post-Conference Workshop - #ATAGTR2017

Mukta Aphale Valerian D’Souza
Steering Committee Member, Agile Testing Alliance

Title: Certified Professional DevOps Foundation

Date 18th to 20th March 2017

Time 9:30 am to 5:30 PM

Venue O Hotel Pune

Workshop Mentor – Valerian D’Souza

What is CP-DOF course?
CP-DOF stands for “Certified Professional – DevOps Foundation” certification prepared and honored by “Agile Testing Alliance”. The course is applicable for all roles and knowledge, experience & certification is consciously designed all the roles in DevOps.

How is it useful?
Leading organizations have adopted the DevOps approach to deliver in-time software. DevOps has quickly become the most hyped, overused and ambiguous term in IT. It is being used to reference everything from job titles (DevOps is not a job title!) to technology practices, but the truth is that DevOps is more of a culture than anything else. It is about transformation, about building quality in, improving productivity and about automation in Dev, Testing and Operations.

CP-DOF is a one of its kind initiative to marry 2 distinct worlds of Agile and Operations together. Learn DevOps fundamentals along with Continuous Integration and Continuous Delivery and deep dive into DevOps concepts and mind-set.

CP-DOF is the first step in DevOps roadmap. Certified CP-DOF professionals are eligible for next level of certification called CP-DOF Advanced.

Day-1
  1. DevOps Fundamentals
  2. Agile and DevOps Concepts
  3. DevOps history, Why, When and How? 2009-2017
  4. DevOps Various Propounded Principles
  5. DevOps Life Cycle
  6. DevOps Jargon
  7. Salaries and Career Growth
  8. Software Configuration Management (SCM)
  9. Configure Manage everything
  10. Artefact-ing
  11. Application Life-Cycle Management (ALM)
  12. Repository Management (GIT)(Artifatory)
  13. Continuous Integration/Delivery (CI)(Jenkins)
  14. Best Practices Version Management and Control
  15. Automated Build
  16. Code Coverage (SonarQube)
  17. CI at every Check-in. (Continuous Testing)
  18. CI Servers
  19. Continuous Release / Deployment (CD)(Jenkins)(Ansible)
  20. Anytime Deployable software building culture
  21. Automated Deployment using QA checks in-built
  22. Every Change/Check-in leads to feedback
  23. Mines survival concept (Canary Release)
  24. Gradual and stealth releases (Dark Launches)
  25. Monkey Disruptions (Simian Monkeys - Conformity, Janitor, Chaos)
Day-2
  1. Continuous Monitoring
  2. Monitoring the DevOps performance metrics & success factors
  3. Automation - almost everything
  4. Infrastructure Management
  5. Binary Artifacting
  6. Infrastructure built by code
  7. Single point access to Logs
  8. Shared Monitoring systems
  9. Run-time Server Configuration Management to avoid Drift
  10. Immutable Infrastructure (Infrastructure as a non-changing image)
  11. Containerization (Docker)
  12. Service Discovery Protocols
  13. Virtualization to create Golden Images
  14. Infrastructure as Code
  15. Tools - Jekins, Git, Chef, Puppet, Docker, Artifactory, SonarQube, Maven, JBoss.
  16. DevOps Anti-patterns
  17. Manually Deploying Software
  18. Manual Configurations of Production Environment
  19. Ice cream cone
Day-3
  1. DevOps Culture
  2. Different people will do different things to solve problems
  3. Everybody should understand what others in the same team are doing
  4. We grow systems and knowledge
  5. Trust
  6. Experimentation & improvement
  7. Safe to fail environment
  8. How well do we cultivate knowledge?
  9. Reward those who help others learn
  10. You just can’t hire in cultural change
  11. Useful DevOps Tools Groups by category
  12. Databases
  13. Operations App Stack
  14. Operating Systems
  15. Cloud Containers
  16. Continuous Integration
  17. Configuration Management
  18. Scripting
  19. Top Skills in Demand in DevOps environment
  20. Case Study
  21. Create and use Docker VM effortlessly
  22. Managing and versioning of code
  23. Build Process
  24. Integrate Jenkins and Github with commit as trigger
  25. Continuous Testing
  26. Continuous Deployment
  27. Running the pipeline