The DevOps Handbook – Parts 5 & 6 – Part 5: The Third Way – The Technical Practices of Continual Learning and Experimentation; 1. Introduction a. Goal – practices to enable learning as quickly, frequently improvement blitz – dedicated and concentrated period of time to address a given issue b. Target DevOps Dojo and 30-Day Challenge – teams work with dedicated Dojo coaches and engineers, execute 2-day from other organizations & teams iv. Participate in peer reviews e. SHARE YOUR EXPERIENCES FROM DEVOPS CONFERENCES i. Cost is always a consideration. BUT, encourage attendance at conferences, give talks

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 monitoring 1. Create telemetry in application & environments (to include production, pre-production, and CD pipeline) iii. Ian Malpass, Etsy – “If Engineering at Etsy has a religion, it’s the Church of Graphs without requiring time-sucking configuration changes or complicated processes.” iv. 2015 State of DevOps Report – high performers had MTTR 168x faster than low performers b. CREATE OUR CENTRALIZED TELEMETRY

The DevOps Handbook – Part 3 The First Way – The Technical Practices of Flow 1. Introduction a. Goal – Enable & sustain fast flow of work by implementing continuous delivery i. Create the foundation configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014 State of DevOps Report – use of version control by Ops was the highest predictor of both IT performance & organizational created from trunk using a one-click process, and validated with automated tests.” v. 2015 State of DevOps Report – trunk-based development predicts higher throughput and better stability, and even higher

DevOps A Horse’s Perspective Just a horse, not a unicorn, 1000 deploys per/second not feasible.  History – How I Got Here?  Contentious relationship existed between development and operations.  Community of Practice, etc.  Test Driven Infrastructure  Blue – green deployments  Combining DevOps Scrum – planning, standups, boards, and backlogs  Making work visible (it’s still hidden)  Poor and Deployment Automation, Jez Humble and David Farley  The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win, Gene Kim, Kevin Behr, and George Spafford.  The Lean Primer, Craig

The DevOps Handbook – Part 1 & 2 1. Preface xi a. Myth—DevOps is Only for Startups: b. Myth—DevOps Replaces Agile c. Myth—DevOps is incompatible with ITIL d. Myth—DevOps is Incompatible with Information Security and Compliance: e. Myth—DevOps Means Eliminating IT Operations, or “NoOps” f. Myth—DevOps is Just “Infrastructure as Code” or Automation: g. Myth—DevOps is Only for Open Source Software: 2. Foreword xix 3. Imagine a World Where Dev and Ops Become DevOps: a. THE CORE, CHRONIC CONFLICT i. Among them are the two following goals, which must be pursued simultaneously: 1. Respond to the

com/Phoenix-Project-DevOps-Helping-Business/dp/0988262509/[2] The Three Ways: The Principles Underpinning DevOps, Gene Kim, http://itrevolution.com/the-three-ways- principles-underpinning-devops/

Schwartz “Mark Schwartz is a rare combination: a deep thinker who has also applied lean, Agile, and DevOps principles at the highest level, leading an extraordinary Agile transformation in the US Federal Mark’s thorough analysis will prove invaluable to leaders who must execute it.” – Jez Humble, CTO, DevOps Research & Assessment, LLC A Few Themes Getting in Our Own Way: First, that we have locked ourselves to speed up its inspecting and adapting process to maximize its impact. Continuous Delivery and DevOps place the entire value stream in the hands of that small team so that it can optimize the whole

Whom did I meet?Attributions and References [1] Speaker Slides and Videos: http://velocityconf.com/devops-web-performance-2015/public/schedule/proceedings [2] YouTube Playlist: https://www.youtube.com/playlist

#查看全局设置 ★本地设置 针 对 单 一 项 目 的 设 置 ， 使 用 --local 参 数 ， 本 地 设 置 信 息 保 存 在 项 目 目 录/.git/config文件里 # cd 项目目录 # git init #初始化仓库，将在当前路径下生成.git子目录，子目录里有 此git仓库的相关信息 # git config --local 0以前的默认配置项是matching） matching 推送本地和远程都存在的同名分支 ★仓库操作 # mkdir ~/testgit #创建项目目录 # cd ~/testgit # git init #初始化仓库，将在当前路径下生成.git子目录，子目录里 有此git仓库的相关信息，初始化后要设置当前工作的用户名等相关信息，否则 h�ps://gitlab.cof-lee.com/cof/pro-1.git #克隆远程仓库到本地，默认 克隆的是远程的默认分支，本例中远程仓库默认分支为main（克隆后会自动在 当前目录下生成项目目录） # cd pro-1/ #进入克隆后的项目目录 # git remote -v #直接克隆的话，默认将远程仓库映射到本地，别

本小节讲解k8s v1.24及之后版本的安装；首先按照第0章的步骤完成准备工作。 ①安装并配置containerd ★安装containerd.io软件 可以使用阿里的源或docker官方的软件源 # cd /etc/yum.repos.d/ # wget h�ps://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo #aliyun的源 ： h�ps://docs.�gera.io/calico/latest/ge�ng- started/kubernetes/quickstart # mkdir ~/calico # cd ~/calico # wget h�ps://raw.githubusercontent.com/projectcalico/calico/v3.26.1/manifests/�gera- default-token-bk95n Events: #以下是某容器默认挂载的一个存储卷，里面一般有3个文件 ①创建用户账号 # cd /etc/kubernetes/pki # openssl genrsa -out kube-user01.key 2048 #创建用户的私钥 # openssl req -new