consistent, & secure c. CREATE OUR SINGLE REPOSITORY OF TRUTH FOR THE ENTIRE SYSTEM i. ALL parts (code & environments) of the system are shared in a version control repository ii. Version control is for Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014 State of DevOps eliminates “worked on my machine” 3. Package the application to enable repeatable installation and configuration into an environment 4. Environments can be more production-like in a consistent and repeatable

Accidents are due to the inevitable design problems in complex systems that we build; they are system problems – not individual problems iii. Effective practices 1. Blameless post-mortems 2. Controlled “could have” a. These are counterfactual statements b. Frames the problem as the system as imagined rather than the system that actually exists 4. Focus on – “Why did it make sense to me when I took that source code repository is powerful way to share local discoveries to the entire organization 1. Configuration standards for libraries, infrastructure, and environments 2. Deployment tools 3. Testing standards

engineers to track what they need to track, at the drop of a hat, without requiring time-sucking configuration changes or complicated processes.” iv. 2015 State of DevOps Report – high performers had MTTR Logging Levels 1. Debug – anything that happens in the program 2. Info – user driven actions or system specific 3. Warn – conditions that could become an error and will likely trigger an alert 4. Error GTP Security & Risk Management group) 1. Authentication/authorization decisions 2. System and data access 3. System and application changes, especially privileged changes 4. Data changes (CRUD) 5. Invalid

possible. Control our destiny  Started to engineer solutions for issues related to product configuration and deployment  Built a strong relationship with development (built empathy)  Development

and last, that the business should be thought of as a community, or perhaps as a Complex Adaptive System, which needs to be led and managed through an inspect-and- adapt, feedback-and-vision-oriented approach dysfunctional transformation cycle. It lies, I believe, in our distinction between the development of a system and its operation and maintenance.  Dividing our IT spending into development and maintenance buckets way to incrementally modernize a legacy system as defined by Martin Fowler.  Instead of building an entirely new system, we take a small piece of the legacy system and rebuild it in a way that lets it

cgroupdriver=systemd" ] } # mkdir -p /etc/systemd/system/docker.service.d # docker info ★docker会修改防火墙规则，导致pod网络不通 # vi /usr/lib/systemd/system/docker.service #在[Service]下的ExecStart=/usr/bin/dockerd 置文件并编辑 # vi /etc/kubeadm-init.yaml apiVersion: kubeadm.k8s.io/v1beta2 bootstrapTokens: - groups: - system:bootstrappers:kubeadm:default-node-token token: abcdef.0123456789abcdef �l: 24h0m0s usages: 置文件并编辑 # vi /etc/kubeadm-init.yaml apiVersion: kubeadm.k8s.io/v1beta3 bootstrapTokens: - groups: - system:bootstrappers:kubeadm:default-node-token token: abcdef.0123456789abcdef �l: 24h0m0s usages:

organization iii. ENABLING ORGANIZATIONAL LEARNING AND A SAFETY CULTURE 1. When we work within a complex system, by definition it is impossible for us to perfectly predict all the outcomes for any action we processes, often to help individual departments maintain their “turf.” Failure is processed through a system of judgment, resulting in either punishment or justice and mercy. c. Generative organizations OF RECORD AND SYSTEMS OF ENGAGEMENT i. Gartner Bi-modal 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

Unlimited. Key Concepts The Three Ways [2] The First Way emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department. The outcomes of putting degradation, always seeking to increase flow, and always seeking to achieve profound understanding of the system (as per Deming). The Second Way is about creating the right to left feedback loops. The goal of daily work, creating rituals that reward the team for taking risks, and introducing faults into the system to increase resilience. Four Types of Work 1. Business projects 2. IT projects 3. Changes 4

systems that preserve many of the advantages of buying off the shelf.  The risk of developing a system incrementally and altering it based on user feedback is often lower than that of buying a finished change.  The advantages of the agility that can be gained through a flexible, changeable, custom system —a smooth rather than a lumpy EA, as we put it in the last chapter—are becoming morecompelling, and assembling best-practice frameworks with continuous user feedback and then continuing to adapt the system over time as the business changes versus buying an undefined stream of future services from a vendor

“finished” late.  This, as we know, is based on the outdated idea that we define the scope of the system ahead of time and keep working until we deliver it. That is precisely what we do not do in an Agile consequences. In the plan-driven model, quality was easier to understand.  We specified what the system should do, and then measured quality as adherence to that specification.  The opposite of a defect say that we are deciding between two different open source products for building a piece of the system and do not know enough of their impacts to make the choice. In the old-school way of making the