TechScrum DevOps 项目实训营

课程大纲

DevOps Fundamentals
Environment/Local Builds
Project Familiarization
• Download and install the required project dependencies.
• Understand the project's directory structure and primary functionalities.
• Review project documentation and comments.
Technical Stack & Environment
• Identify the tech stack: Typescript, Node.js, etc.
• Set up the development environment: Node.js, npm/yarn.
• Identify required environment variables and their purposes.
Local Execution
• Run the project's installation and start commands.
• Test the main functionalities of the project to ensure it operates correctly locally.
Cloud Infrastructure Setup
• Select the appropriate cloud platform based on project needs.
• Manually set up the necessary cloud services for frontend, such as storage and CDN services.
• Configure related networking and security settings.
DevOps Infrastructure as Code
Basic Frontend/Backend IaC Code
Frontend IaC
• Choose and familiarize with an IaC tool.
• Write simple IaC scripts for frontend deployment.
Backend Cloud Components
• Choose cloud servers or container services based on backend requirements.
• Manually deploy backend code, set up database connections, etc.
• Test backend functionalities and performance.
Backend IaC
• Use the chosen IaC tool to script backend deployment.
Frontend/Backend IaC Enhancement + Monitoring
IaC Enhancement for Frontend & Backend
• Optimize existing IaC scripts for frontend and backend.
• Add or modify resources based on project requirements.
Monitoring
• Select appropriate monitoring tools.
• Implement health checks for the frontend.
• Set up and configure cloud-based monitoring tools to monitor frontend CDN's performance and availability.
DevOps Monitoring and Logging
Cloud Account, GitHub Organization, Frontend/Backend Monitoring
Shared Resources
• Create a GitHub organization and invite team members.
• Choose a cloud platform and set up a shared account.
IaC & CI/CD for Frontend/Backend
• Deploy frontend and backend applications in the shared account.
• Optimize IaC scripts based on the characteristics of the shared account.
• Establish Continuous Integration/Continuous Deployment pipelines.
Extended Monitoring
• Expand monitoring capabilities for frontend and backend, including application performance and error rates.
• Set up alerts to ensure prompt issue responses.
Monitoring Tools IaC
Manual Setup of Monitoring Tools
• Choose monitoring tools like Prometheus, and Grafana based on project needs.
• Manually deploy these monitoring tools on the cloud platform.
IaC for ELK
• Familiarize with ELK's deployment and management.
• Use an IaC tool to script ELK deployment.
IaC for Monitoring
Infrastructure Enhancement
• Optimize networking, storage, and compute resources based on the expansion needs of the project.
IaC for Monitoring Tools
• Script the deployment of Prometheus, and Grafana using IaC.
• Automate the deployment of these tools on the cloud platform.
Integration & Pipeline Setup
• Ensure monitoring tools can correctly monitor frontend and backend applications.
• Configure integrations between monitoring tools and other services, such as alerts and log management(ELK/Opensearch).
DevOps Failover Strategies
Failover
Failover Strategies
• Learn and determine the appropriate failover strategies for the project.
• Configure and test auto-recovery functionalities.
• Optimize the application to handle various failure scenarios.
Challenge:
API Gateway + Lambda:
• Implement using Terraform, possibly in combination with SAM (Serverless Application Model).
• Prioritize using Lambdas written by developers.
• If the developer hasn't finished the Lambda function, the DevOps team can write a backup Lambda (for example, for handling tfstate files or frontend). This can be invoked using API Gateway, EventBridge, or S3.
EKS (Elastic Kubernetes Service) + AKS (Azure Kubernetes Service):
• Implement one of the platforms.
• Use Terraform to set up the cluster, worker nodes, and other foundational infrastructure.
• Deploy applications via a pipeline, with the pipeline located in the code repository.
Code Testing:
• Set up a SonarQube server and integrate it into the Jenkins pipeline. Email the test results to developers.
• Incorporate Snyk into the pipeline and email the test reports to developers.
• Scan once a week to compare code improvements.
• Implement unit tests for critical parts of the application and ensure they run as part of the CI/CD pipeline.
Load Testing:
• Use tools like JMeter or Locust to simulate heavy traffic to your infrastructure.
• Analyze the system's response and identify bottlenecks.
• Optimize the infrastructure based on the findings and retest.
Security:
• Integrate with some cloud platform security tools, like AWS securityhub….
• Integrate automated security scans in the CI/CD pipeline.
• Ensure all services are running with least privilege access.
Failover Trigger:
• Design mechanisms to detect system failures, such as health checks or monitoring alarms.
• Implement automated or semi-automated processes to redirect traffic to the failover infrastructure in case of system failure.
Vault:
• Set up a Vault server.
• Store credentials in Vault and modify or create new pipelines accordingly.
GitHub Actions/Bitbucket Pipelines:
• Re-implement Jenkins code pipelines using either GitHub Actions or Bitbucket Pipelines, depending on the type of the project's code repository.