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 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 Production System – “people closest to a problem typically know the most about it.” iii. 2014 State of DevOps Report – high performing organizations relied more on peer review and less on external approval

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

点分配一个24位的子 网， # cat /run/flannel/subnet.env #查看当前结点注册的pod子网信息 ⑦部署calico网络插件（与flannel二选一） 官 方 指 导 ： h�ps://docs.�gera.io/calico/latest/ge�ng- started/kubernetes/quickstart # 53:6443 check weight 1 inter 2000 rise 2 fall 2 #如果vip设备就在这3台master结点上，则Haproxy监听的端口不能为6443，否则 与后端api监听的端口冲突了，可改为其他端口号 #本例使用单独的一台服务器来配置vip及反向代理，vip使用keepalived软件来生 成，配置省略。 ★先安装master1 ★使用命令行方式初始化集群 cof- lee.com:5443/k8s" \ #指定镜像源为集群可访问的源地址 --control-plane- endpoint=10.99.1.54:6443 \ #指定控制面板vip与端口号 --ignore-preflight-errors=Swap \ #忽略swap未关闭而导致的检查错误 --upload-certs #将控制平面证书上传到kubeadm-certs Secret；并在后续添加节点时自动分发证

( 1+2j ) （python3无long长整型） True=1, False=0 string 有序strx='xxxx' stry="xxx" 不区别单引号与双引号， 单个字符也是string list 有序 列表，数组 tuple 有序 元组 set 无序 不重复（自动删除重复项） 集合 py3新 判断a和b是否引用自同一个对象，是则返回 True is not # a is b 同 id(a) == id(b) # id(x)用于获取对象x的内存地址 ⑥位运算符 & 与运算 ^ 异或 | 或 << 左位移 ~ 取反 >> 右位移 ★运算符优先级： 指数** > 位运算 > 乘除 > 加减 三维类推： matrix = [[[0 for _ in range(3)] for _ in range(4)] for _ in range(2)] print(matrix) #查看数组行数与列数 arr = [[1, 2, 3], [4, 5, 6], [7, 8, 9], [10, 11, 12]] print(len(arr)) # 行数 print(len(arr[0]))