Conclusion DevOps


by DevOpsSchool.com

Rajesh Kumar

(Senior DevOps Manager & Principal Architect)


Rajesh Kumar — an award-winning academician and consultant trainer, with 15+ years’ experience in diverse skill management, who has more than a decade of experience in training large and diverse groups across multiple industry sectors.

Usually we don’t have


  • Centralized Source Management Tools
  • Centralized Build Server for all the Products
  • Common Build Script across the organization
  • Configuration Management Tools such puppet or salt
  • Standard Release and Deployment Process
  • Automated Testing Just after build
  • Code Review Setup
  • Static Code Analysis
  • Test Coverage
  • Centralized Dashboard for all CI/CD reporting and Notification
  • SCM Infrastructure Monitoring Setup

Goals


  • Faster Development Process across the Solutions
  • Reduces Costs and Burdon on People and Process
  • Reduces Engineers options making SCM support easier
  • Enforces Uniform Corporate Process
  • Standard Version control and Builds
  • Fast, Reliable, and ready to QA/Deploy Build operation
  • Streamline Release and Deployment Process
  • Simplified Branching, Tagging, and Directory organization
  • Strong Tools integration between CM, Build, QA and Deployment, Feedback, etc

What We want…


  • Continuous Integration is for immediate feedback
  • Automated Testing based on Continuous Integration
  • Continuous Delivery based on Automated Testing
  • Automated Test Deployments
  • Useful Feedback on time
  • Measurement!!! & Monitoring!!!
  • Unify the software delivery process across the product line SDLC

-Reduce duplication of effort

-Improve consistency

-Embrace change

-Remove known sources of error

DevOps is a Philosophy


  • Agile & Lean applied to the whole software delivery chain, not just developers

  • Driven by efficiency and consistencies

- Building applications

- Building Environments

- Configuring Applications and environments

- Optimizing software Delivery to End to End

DevOps is…


  • no definition
  • It certainly isn't a person
  • No strict rules
  • No strict tools
  • It's not even new
  • If you aren't doing it already ...
  • ... you are doing it wrong

Benefits


Business Benefits


  • Developer productivity
  • Smoother workflow within organization
  • Supports many Development Models
  • Open source, Profitability and Growth
  • SCM team is focusing on developing CM technology and framework instead of support.

Non-Functional Benefits


  • Security
  • Backups
  • High Availability
  • Upgradability
  • Faster Development
  • Monitoring and Notification
  • Scale

Vision and Directions of DevOps


  • Must have
    • Centralized build server across products
    • Standard approach for validating builds through automated testing
    • Centralized static code analysis setup for all products
    • Significant automated test coverage across products
    • - Nice to have (Standardization)

    • Centralized common source management tools such as Git
    • Common build script across the organization
    • Standard release and deployment process across products
    • Centralized monitoring setup for CM infrastructure, builds and notifications
    • Centralized server to manage, upgrades and Install SCM, builds and QA machines

DevOps / CI / CD


What is Continuous Integration (CI)?


Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.


- Martin Fowler

What is Continuous Delivery (CD)?


Continuous Delivery is the continual delivery of code to an environment once the developer feels the code is ready to ship. The idea is to deliver code to a user base - QA (UAT or Staging) or customers (Production environment), for continual review and inspection.

What is Continuous Delivery (CD)?


Continuous Delivery is the continual delivery of code to an environment once the developer feels the code is ready to ship. The idea is to deliver code to a user base - QA (UAT or Staging) or customers (Production environment), for continual review and inspection.

Benefits from CI / CD?


    • Fast, reliable, and ready to QA/Deploy/Build operation
    • Seamless integration between CM, build, QA, deployment, security, and continuous feedback.
    • Reduces risks and defects and Improves the quality of the deliverables
    • Improves development team agility and velocity
    • Make Every build is for potential release
    • Eliminate manual bottlenecks and automate whatever possible
    • Have automated tests you can trust and Enforces best practices
    • Avoid wait time, handoff conflicts and human errors
    • Know results earlier! Fix bugs faster! More stable builds!
    • Supports transition to Cloud based deployment

Why Feedback?


  • Monitoring is for Feedback of

Code Quality poor | average | good | best

- Builds pass | fail

- Test Quality

- System Availability

- Performance of Tools and Products

- SCM Infrastructure Availability

- It save time of.

  • Developer
  • Engineer
  • Manager
  • Director
  • CEO

Continuous Delivery Workflow


Delivery Vs Deployment


Challenges for Large Organization


Community


https://www.devopsschool.com/community/

Solution


DevOps

DevOpsSchool Community Networks


These platforms provide you the opportunity to connect with peers and industry DevOps leaders, where you can share, discuss or get information on latest topics or happenings in DevOps culture and grow your DevOps professionals network.

DevOps
Build & Release
DevOps
Build & Release
DevOpsSchool
DevOps Group
BestDevOps.com
      

Any Questions?


Thank You!


DevOpsSchool — Lets Learn, Share & Practice DevOps

www.devopsschool.com

Connect with us on
contact@devopsschool.com | +91 700 483 5930