The DevOps Handbook
Part 4: The Second Way – The Technical Practices of Feedback 1. Introduction a. Goal – Implement fast feedback loops i. Enable working towards shared goals ii. See problems as they occur iii. Enable isn’t moving yet, just in case it decides to make a run for it…Tracking everything is key to moving fast, but the only way to do it is to make tracking anything easy…We enable engineers to track what they averages to reduce short-term fluctuations and highlight longer-term trends. iii. More exotic - Fast Fourier Transforms or Kolmogorov-Smirnov 4. Ch. 16 – Enable Feedback So Development and Operation0 码力 | 8 页 | 24.02 KB | 5 月前3The DevOps Handbook
Introduction a. Goal – Enable & 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 production v. Dev & Ops gain shared mastery of application & environment interactions 3. Ch. 10 Enable Fast and Reliable Automated Testing a. Undesired outcomes result from finding and fixes errors in a separate Developers working in small batches on trunk rather than long-lived feature branches f. BUILD A FAST AND RELIABLE AUTOMATED VALIDATION TEST SUITE i. Slow and periodic feedback kills – larger batch sizes0 码力 | 8 页 | 23.08 KB | 5 月前3The DevOps Handbook
context of global goals. ii. REDUCE BATCH SIZES1. Another key component to creating smooth and fast flow is performing work in small batch sizes. 2. Large batch sizes result in skyrocketing levels IT 1. Type 1 – System of Record – “Doing it right” 2. Type 2 – System of Engagement – “Doing it fast” ii. DevOps helps reject the bi-modal IT model and lets you do both c. START WITH THE MOST SYMPATHETIC0 码力 | 8 页 | 22.57 KB | 5 月前3The DevOps Handbook
API use e. DESIGN FOR OPERATIONS THROUGH CODIFIED NON-FUNCTIONAL REQUIREMENTS i. Designing for fast flow, deployability, and operations will derive NFRs. Codify these into the tests and pipeline f Automate as many security controls and tests as possible and incorporate into the pipeline iii. Enable fast feedback on potentially insecure changes g. ENSURE SECURITY OF THE APPLICATION i. Focus on the sad0 码力 | 9 页 | 25.13 KB | 5 月前3安全简介
Alignment Transparency House of Lean: "We need to figure out a way to deliver software so fast that our customers don't have time to change their minds" - Mary PoppendieckTeam -> Program -> Portfolio0 码力 | 2 页 | 304.16 KB | 5 月前3DoD CIO Enterprise DevSecOps Reference Design - Summary
lead-time: how long it takes for a new 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:0 码力 | 8 页 | 3.38 MB | 5 月前3A Seat at the Table: IT Leadership in the Age of Agility - Part 2
provisioned. The choice we have to make: Option 1: These techniques, if we use them correctly, enable a fast try-and-learn cycle in which developers can produce something, get feedback, and then adjust what0 码力 | 7 页 | 387.61 KB | 5 月前3A Seat at the Table - IT Leadership in the Age of Agility
actual success in accomplishing the business outcome for which it was intended. Fail often, fail fast—but fail well. Why in the Agile world do we talk about the need to fail and to fail often? This is0 码力 | 7 页 | 387.48 KB | 5 月前3k8s操作手册 2.3
inet 127.0.0.1/8 scope host lo 2: ens33:mtu 1500 qdisc pfifo_fast state UP #k8s服务器本身用于通信的网口 inet 10.99.1.61/24 brd 10.99.1.255 scope global 3: docker0: 0 码力 | 126 页 | 4.33 MB | 1 年前3
共 9 条
- 1