sustain fast flow of work by implementing continuous delivery i. Create the foundation of our deployment pipeline ii. Enabling fast & reliable automated testing iii. Enabling & practicing continuous Integrating objectives of QA & Operations to improve outcomes 2. Ch. 9 – Create the Foundations of Our Deployment Pipeline a. Enterprise Data Warehouse program by Em Campbell-Pretty - $200M, All streams of work INCLUDE RUNNNING IN PRODUCTION-LIKE ENVIRONMENTS i. In general, the longer the interval between deployment, the worse the outcome ii. Ensure Dev & QA routinely integrate with prod-like environments at

--iface-regex=10.99.1.* 匹配要通信的ip网段（为node结点的通 信ip网段，即pod容器流量使用此ip网络对应的网口进行vxlan封装） #最后重新部署flannel的deployment文件 # kubectl apply -f kube-flannel.yml #可见flannel的pod启动了（名称为kube-flannel-xxxx） # ip -d link resource # kubectl create -f custom-resources.yaml #如果需要更改镜像，只能部署 后，只能更改相应的daemonset及deployment #查看calico节点状态，状态全部为Running则为启动成功 # kubectl get pods -n �gera-operator NAME limits.memory: 4Gi #内存资源限制的总量限额 count/deployments.apps: "2" #可以创建的deployment总数 count/deployments.extensions: "2" persistentvolumeclaims: "2" #可以创建的pvc总数

standards for libraries, infrastructure, and environments 2. Deployment tools 3. Testing standards and tools, including security 4. Deployment pipeline tools 5. Monitoring and analysis tools 6. Tutorials Integrate security with our deployment pipeline iv. Integrate security with our telemetry for better detection and recovery v. Protect our deployment pipeline vi. Integrate our deployment activities with our that are pre- approved and appropriately configured and secured. f. INTEGRATE SECURITY INTO OUR DEPLOYMENT PIPELINE i. Hardening the application after development completes is not acceptable. Left issues

VALUE OF DEVOPS i. Code and change deployments (thirty times more frequent) ii. Code and change deployment lead time (two hundred times faster) iii. Production deployments (sixty times higher change success where an entire year’s worth of code that Development has worked on is released to production deployment. Like in manufacturing, this large batch release creates sudden, high levels of WIP and massive progress from deployment lead times measured in months or quarters to lead times measured in minutes, the constraint usually follows this progression: a. Environment creation: b. Code deployment: c. Test

TELEMETRY GAPS i. Expand metrics from business, application, infrastructure, client software, and deployment pipeline levels 1. With every production incident identify missing telemetry that could help TELEMETRY TO MAKE DEPLOYMENTS SAFER i. Actively monitor production telemetry whenever anyone performs deployment; focus on the metrics associated with the feature. ii. If negative results, ideally feature toggle Traditional change controls 1. Lead to long lead times and diminish effectiveness of feedback from the deployment process 2. Increase friction by adding more steps/approvals which tends to increase batch size

requirement to be delivered and deployed. Deployment speed: how fast a new version of the application can be deployed into the production environment. Deployment frequency: how often a new release can be actions.  Automate as much of the development and deployment activities as possible.  Adopt common tools from planning and requirements through deployment and operations.  Leverage agile software principles

Control our destiny  Started to engineer solutions for issues related to product configuration and deployment  Built a strong relationship with development (built empathy)  Development began to see operational innovation and optimization.  Environment homogenization and assimilation – no snowflakes  Deployment methodologies, automation, monitoring, and management tested continuously. Steve Barr steve.barr@csgi Scrum, Craig Larman  Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, Jez Humble and David Farley  The Phoenix Project: A Novel About IT, DevOps, and

automated pipelines that help the developer move frictionlessly and quickly from requirements to deployment.  The developer uses a powerful integrated development environment (IDE) that centralizes the is tested automatically through scripted tests.  It is deployed automatically with automated deployment tools onto infrastructure that can be automatically provisioned. The choice we have to make:

system calls Continuous Delivery in Financial Training by David Genn (IG) @david_genn  Separate deployment from release  Automate everything  Trust your tests  Conversations are way better than project

adequate for the feature to be deployed.  It is easy enough to say that the feature is ready for deployment when it passes all of its tests. But is quality a simple yes-or-no attribute? If it passes its