Cloud Computing - Unit 07

DevOps Practices

- Continuous Integration - Continuous Delivery - Microservices - Infrastructure as Code - Monitoring and Logging - Communications and Collaboration

DevOps Benefits

- Speed - Rapid Delivery - Reliability - Scale - Improved Collaboration - Security

Rolling Deployments - Advantages

Allows the application to remain available during the deployment, and issues can be detected and addressed as the rollout progresses.

Basic CI/CD Pipeline - 3. Test

Automated tests (unit tests, integration tests, etc.) are run against the build to detect any defects or errors.

Popular Continuous Deployment Strategies

Below are key CD strategies used in DevOps practices: ➢ Rolling Deployments ➢ Canary Deployments ➢ Blue/Green Deployments

Continuous Deployment Strategies

Continuous Deployment (CD) strategies define how software changes are moved from code to various environments and, ultimately, to production. These strategies aim to optimize the deployment process for reliability, speed, and safety.

DevOps Model and Team Structure - Cross-functional Teams

Engineers in a DevOps environment are versatile, working across various aspects of the application lifecycle and developing broad skills beyond their traditional roles.

DevOps Benefits - Reliability

Ensure the quality of application updates and infrastructure changes so you can reliably deliver more rapidly while maintaining a positive experience for end users. Use continuous integration and delivery to test that each change is functional and safe.

DevOps Model and Team Structure - Breaking Down Silos

In DevOps, development and operations teams are not separated; instead, they work closely together or may even merge into a single team. This enhances collaboration across the application lifecycle (i.e., development, testing, and deployment to operations).

Rolling Deployments - Description

In rolling deployments, the new application version is gradually deployed across all servers or regions, replacing the older version. This is done in phases, usually server by server or cluster by cluster, until the new version is fully deployed.

DevOps Benefits - Improved Collaboration

Objective: Build more effective teams under a DevOps cultural model, emphasizing ownership and accountability. Developers and operations teams collaborate closely, share many responsibilities, and combine their workflows.

DevOps Benefits - Rapid Delivery

Objective: Increase the frequency and pace of releases so you can innovate and improve your product faster. The quicker you release new features and fix bugs, the faster you can respond to your customers' needs and build a competitive advantage.

DevOps Benefits - Speed

Objective: Move at high velocity so you can innovate faster for customers, adapt better to changing markets, and become more efficient at driving business results.

DevOps Benefits - Security

Objective: Move quickly while retaining control and preserving compliance. You can adopt a DevOps model without sacrificing security by using automated compliance policies, fine-grained controls, and configuration management techniques.

DevOps Benefits - Scale

Objective: Operate and manage your infrastructure and development processes at scale. Automation and consistency help you manage complex or changing systems efficiently with reduced risk.

Basic CI/CD Pipeline - 5. Monitor and Feedback

Post-deployment, the application is monitored for issues. Feedback is collected and used to initiate subsequent cycles of development, testing, and deployment.

Blue/Green Deployments - Description

This strategy involves two identical environments: one Blue (active production environment) and one Green (idle or staging environment). When a new version of the software is ready for release, it's deployed to the Green environment. After testing and verification, traffic is switched from the Blue to the Green environment, making the Green environment the new production.

Basic CI/CD Pipeline - 4. Deploy

Upon successful testing, the CD process automatically deploys the build to a staging or production environment.

CI/CD Overview

[CI] Build ➔ [CI] Test ➔ [CI]Merge ➔ ➔ [CD][Continuous Delivery] Automatically Release to Repository ➔ [CD][Continuous Deployment] Automatically Deploy to Production

Continuous delivery/deployment (CD)

is a 2 part process that refers to the integration, testing, and delivery of code changes.

Continuous integration (CI)

refers to the practice of automatically and frequently integrating code changes into a shared source code repository

DevOps Model and Team Structure

• Breaking Down Silos • Cross-functional Teams

CI/CD

➔ CI/CD is an essential practice in DevOps that streamlines the application development lifecycle by automating: ➢ Integration Process ➢ Deployment Process. ➔ CI/CD enables developers to merge code changes more frequently and reliably into a central repository, followed by automatic builds and tests.

Basic CI/CD Pipeline

➔ Code ➔ Build ➔ Test ➔ Deploy ➔ Monitor and Feedback

Continuous delivery vs deployment

➢ Continuous delivery stops short of automatic production deployment. ➢ Continuous deployment automatically releases updates into the production environment.

DevOps Practices - Continuous Delivery

➢ Definition: Automatic build, test, and preparation of code changes for production release. ➢ Benefits: Ensures deployment-ready builds that have passed standardized tests, enabling faster feature release and bug fixes.

DevOps Practices - Microservices

➢ Definition: Designing applications as a collection of small, independently deployable services. ➢ Benefits: Allows for diverse programming frameworks/languages, facilitates independent deployment, and centers around business capabilities for better scalability and resilience.

DevOps Practices - Continuous Integration

➢ Definition: Developers frequently merge code changes into a central repository, where automated builds and tests are run. ➢ Benefits: Quickly find and address bugs, improve software quality, and speed up software release.

DevOps Practices - Communication and Collaboration

➢ Definition: Enhancing interaction and shared responsibilities between development, operations, and other organizational teams. ➢ Benefits: Streamlines workflows, aligns goals, and accelerates project completion by fostering an environment of shared knowledge and cooperation.

DevOps Practices - Infrastructure as Code

➢ Definition: Managing and provisioning infrastructure through code instead of manual processes. ➢ Benefits: Increases efficiency in deployment, updates, and duplication of infrastructure with reduced risk and enhanced repeatability.

DevOps Practices - Monitoring and Logging

➢ Definition: Tracking application and infrastructure performance to understand the impact on end-user experience. ➢ Benefits: Helps in proactive problem-solving and understanding the root causes of issues by analyzing data and logs.

Canary Deployments - Description

A canary release involves rolling out the new version to a small subset of users or servers before making it available to everybody. This approach helps in identifying any issues with the new version under real usage conditions without affecting all users.

DevOps

DevOps combines cultural philosophies, practices, and tools that increase an organization's ability to deliver applications and services at high velocity, evolving and improving products faster than organizations using traditional software development and infrastructure management processes.

Basic CI/CD Pipeline - 1. Code

Developers commit changes to the version control system, triggering the CI/CD process.

Blue/Green Deployments - Advantages

Minimizes downtime and allows for easy rollback, as the Blue environment remains unchanged until the switch.

Canary Deployments - Advantages

Reduces the risk of introducing a new version, as it allows monitoring the impact on a smaller scale before a wider rollout.

Basic CI/CD Pipeline - 2. Build

The CI tool automatically compiles the code into a runnable build, ensuring the application can be executed.