DevOps Design and Automation For Developers- 5 days

-
DevOps Design and Automation For Developers-  5 days

Pre-Requisites:
Knowledge of Software engineering and Hands-on on Linux
(It Is mandatory to accomplish the training prerequisite conditions before nominating for the session)

Course Content:
Module 1      DevOps Fundamentals
      Introduction to DevOps
      DevOps Process
      DevOps Team
      Architecture application for DevOps
      DevOps Technology Reference Architecture
     
Module 2      Source Code Repository in GIT
      GIT Fundamentals
      GIT Banching and Merging
      Lab: Woking With GIT
      Lab: GIT Branching and Merging
      Lab: Code Commit Private GITHub
     
Module 3      Continuous Integration and Deployment
      Continuous Integration Fundamentals
      Continuous Delivery Fundamentals
      CI/CD with Jenkins
      Lab: Install and Configure Jenkins
      Lab: Create a Simple pipeline in Jenkins
      Lab: Introduction to Groovy Scripts for Pipelines
      Lab: Crete a Maven Pipeline Build with Cobertura and Junit Test cases
                        
Module 4      Automate Cloud IaaS for DevOps
      Cloud Overview
                                           Lab: Create a Autoscaling Applications in AWS
Module 5      Docker Containers
      Docker Fundamentals
      Lab: Working with Docker
      Build and Ship Docker Images
      Lab: Build and Ship Images
      Docker Container as a Service
      Lab: Build a Kubernetes Cluster in AWS
      Create a Micro service Application
      Lab: Build and RUN a three tier application in cloud
      Lab: Run a Micro serviced docker application using Jenkins                       
Module 6      Automation using Ansible
      Ansible Fundamentals
      Ansible Modules
      Lab: Managing Application config in Ansible
      Lab: Creating and Running Docker using Ansible
      Lab: Build and Run Docker in Jenkins                        
Module 7      Design and automate DevOps End to End
               Move the Code and Development to DevOps Model
               Move Agile in Infrastructure and Development
               Create a DevOps Environment in Cloud
               Use Containers for Application building process
               Put Code and Containers in GIT
               Automate Infrastructure Creation and Scaling in Cloud
               Automate Configuration using Ansible
               Repeat the Process in Different environments
               Create a DevOps Process for you Organization
               Lab: Create a Pipeline for your application
               DIY: Create a Complete stack Pipleine

Comments

Post a Comment

Popular posts from this blog

Cloud Computing in simple

-
Cloud Computing =   Infrastructure as a Service (IaaS) + Platform as a Service (PaaS) + Software as a Service (SaaS) Cloud computing, also known as Cloud Technology, Cloud Applications or Cloud-based services. Cloud Computing is the practice of using a network of remote servers hosted on the internet to store, manage and process data, rather than a local server or a personal computer. Examples of cloud-based services include customer self-scheduling, data storage, online payment, and accounting software Different Type of Clouds Infrastructure as a Service (IaaS)  – Allows users with the services like Virtual servers, Virtual storage, Physical Database, Virtual Network, Physical Network. E.g. Google Storage ,  IBM Cloud Computing ,  Nimbus Platform as a Service (PaaS)  – Provides computational resources via a platform upon which applications and services can be developed and hosted. E.g. Databases, Data Stores,  Force.com ,  Google App Engine ,  Windows Azure  (Platform). Soft
Read more

How to Write an Effective Design Document

-
Image
How to Write an Effective Design Document Why write a design document? A design document is a way for you to communicate to others what your design decisions are and why your decisions are good decisions. Don’t worry if your design is not UML compliant and don’t worry if you didn’t use a special modeling tool to create it. The biggest factor that determines if your design document is good is whether or not it clearly explains your intentions. This presents a problem, however. In order to convey design decisions, you have to consider the audience that you are writing for. A peer developer will understand why a well-crafted class abstraction is a good design, however your manager will probably not. Because your peer developers and your manager have different concepts of what makes a design good, there is a need for two design documents; one for peer developers and one for managers. Each document serves a different and equally valuable purpose as you begin your project development. I
Read more

Bookmark

-
Good Blog about Architecture & design Patterns:   http://martinfowler.com/bliki/ http://www.sharepoint-videos.com/ http://go.cloudshare.com/Linkedin_ProPlus_SharePoint.html A Technical Q/A site: http://www.bookmarkresource.com http://blog.krisvandermast.­ com/ASPNET20PageLifeCycle.aspx http://blogs.vertigosoftware.­ com/shannonf/archive/2005/08/­ 07/1355.aspx http://john-sheehan.com/blog/­ net-cheat-sheets/ http://www.eggheadcafe.com/­ articles/20051227.asp http://duartes.org/gustavo/­ articles/Asp.net-Runtime-­ Cheat-Sheet-HttpRequest-­ HttpRuntime.aspx http://www.addedbytes.com/­ cheat-sheets/javascript-cheat- ­sheet/ http://www.antsmagazine.com/­ 2009/04/100-useful-cheat-­ sheets-for-web-designers-­ developers/ Nice link abt .Net 3.5: http://www.simple-talk.com/ dotnet/.net-framework/.net-3. 5-language-enhancements/ nice articles about JQuery. http://encosia.com/2008/05/29/ using-jquery-to-directly-call- aspnet-ajax-page-methods/ http://encosia.co
Read more