01 - Introduction of Devops

-
Traditional Development Models: Waterfall
  1. Requirement Gathering -> Business
  2. System Design
  3. System Implementation
  4. System Testing -> QA / Testing team
  5. System Deployment
  6. System Maintenance

DevOps is short for Development Operations
  • It focuses on collaboration between developers and other parties involved in building, deploying, operating, and maintaining software systems
  • It is about defining a flow from development through full-scale operation of a system
  • It is about Systems Thinking with feedback to earlier stages of a DevOps workflow
  • The emphasis is on automating processes required to release and change the software
  • With a view to rapid, frequent, and reliable releases

Agile
  • Agile Software Development is an umbrella term for a set of methods and on the values and principles expressed in the Agile Manifesto
  • Solutions evolve through collaboration between self-organizing, teams utilizing the appropriate practices for their context
                Product Backlog -> Sprint Planning -> Spring Backlog ===> Scrum Team ===> Sprint Review --> Increment
                                                                                                              (Scrum Master)

Agile & DevOps
  • Some of the principles of Agile manifesto that lead to a DevOps environment
  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter time scale
  • Business people and developers must work together daily throughout the project
  • DevOps not only talks about the collaboration between Development and Operations but improved collaboration between all teams including business
  • DevOps also promotes using a lot of automation to complete the many tasks and steps that go into making a deliverable potentially shippable increment
  • Using tools to replace the non-human steps like build creation, environment setup, trigger test cases, automated deployments multiple times in a day
What DevOps is Not 
  • A title
  • A separate team
  • A tool
  • Only Culture
  • Only automation
  • Anarchy
  • A one size fits all strategy
Evolution of IT
Development Process        ===> Waterfall              --> Agile                --> DevOps
Application Architecture      ===> Monolithic           --> N-Tire               --> Microservices
Deployment & Packaging   ===> Physical Servers --> Virtual Servers --> Containers
Application Infrasturcture    ===> DataCenre           --> Hosted             --> Cloud

DevOps Goals
  • Smaller, more frequent release
  • Reduced effort and risks
  • Reduced cost of product iterations and delays
  • A culture of communication and collaboration
  • Consistency and speed through automation
Characteristics DevOps
  • Continuous Itegration (Jenkins ) -> Push code -> complied -> Testing
  • Monitoring Tools (Nagios )
  • Being Proactive
  • Working Together
  • Automated Testing
  • Cross Training

DevOps Values
Automation -> Lean -> Measurement -> Sharing -> Culture

DevOps Stakeholders
Architects, Business representatives, Customers, Product Manager, Project Manager, Quality - QA, QC , Suppliers


DevOps Workflow  ( DevOps + Continuous Delivery Cycle )
  • Business Need / Use Cases
    • Product Owner
  • Software development Team
    • IDE = Integrated Deployment Environment
      • eclipse, Visual Studio
  • Software Check-in
    • git (VC = Version Control ) or ( SCM Source = Code Management)
  • Automated Software Build
    • Compiled Code ( CI / CD )
      • Jenkins
      • Bamboo
      • Maven
  • Automated Test Scripts
    • QA / Testing Team
      • Visual Studio
      • Jenkins
  • Automated Deployment
    • Dev -> QA -> Staging -> Product
      • Ansible
      • CHEF
      • Puppet labs
  • Monitoring / Operations
    • System Centre
    • Nagios


Comments

Post a Comment

Popular posts from this blog

05 - Docker - Containers

-
Image
 Docker - Containers - Container is operating system-level virtualization  ( Linux Kernal ) Allow for multiple isolated user-space instances called containers They share a single kernel Can be added or removed any times - Containers consist of a self-contained Linux file system Can be from any Linux distribution which is compatible with the host kernel Usually contain a single application such as a server - Operating  Is often used in Cloud Computing Docker Architecture Docker is available in two editions: Community Edition (CE) - open-source Enterprise Edition (EE) Docker uses a client-server architecture Client REST API  (   the primary user interface which communicates ) Over HTTP Over local Unix Socket Docker CLI docker build docker pull docker run Servers (Docker_Host) Is the Docker daemon Responsible for building, running, and distributing containers Docker daemon Container Images Registry (docker.io , DockerHub) Responsible for the storage, management, and delivery of Docker im
Read more

08 - PUPPET - Configuration Management

-
Image
 PUPPET - Configuration Management A Configuration Management Tool A framework for Systems Automation A Declarative Domain Specific Language (DSL) An Open Source software is written in Ruby Works on Linux, Unix (Solaris, AIX, *BSD), macOS, Windows |Supported Platforms) Developed by Puppet Labs Puppet Agent Required SSL certificate Default fatches after 60 minutes noop - dry run Puppet Open Source or Enterprise Puppet Langauge Declarative - Domain Specific Langauge (DSL) define STATES (No procedures) Puppet code is written in manifest ( .pp extension ) In the code, we declare resources that affect elements of the system (files, packages, services ... ) Resources are grouped into classes Classes and configuration files are organized in modules Puppet Resource Abstraction Layers Puppet Catalog Certificate Management Server Resources Facter Puppet Manifest Puppet Resources Resource Types Reference Puppet Nodes Roles Define Policy Puppet Virtual Resources Puppet Lab   Pu
Read more

06 - Docker Swarm - Container Orchestration

-
Image
 Docker Swarm - Container Orchestration Create Cluster Build & Deployment automated Rolling Deployment Update Version Docker Swarm is clustering for Docker It turns several Docker hosts into a single virtual Docker host The Swarm is controlled by Swarm Manager Each Docker code communicates with the manager It can be installed manually or by using Docker Machine Scheduler Service Discover Consul -> provide DNS Zookeeper - configuration management tools Cheat Sheet => https://lzone.de/cheat-sheet/Docker%20Swarm LAB mkdir DockerSwarm cd DockerSwarm mkdir manager vm1 vm2  *** Manager Node **** cd manager vagrant ssh sudo su - hostnamectrl set-hostname managernode.unix.in bash vi /etc/hosts 192.168.33.14 managernode.unix.in 192.168.33.15 workernode1.unix.in 192.168.33.16 workernode1.unix.in ## Install Docker C curl -fsSL get.docker.com | sh ## Add user Vagrant in Docker group sudo usermod -aG docker vagrant id vagrant ## Start Docker Service
Read more