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

Kubernetes、ServiceMesh、CI/CD 实践 杨文@JEX 2018.08.25 Service Mesh Meetup #3 深圳站关于我 • JEX 技术VP • 前小恩爱技术总监 • Gopher，开源爱好者 • Go 夜读发起人 • https://github.com/developer-learning/night-reading-go • https://github https://github.com/developer-learning/learning-kubernetes大纲 • 技术架构的演进 • 如何提升工程效率？DevOps • CI/CD 实战 • ServiceMesh • 踩过的一些坑 • Q&A技术架构的演进 • 单体架构 • 一个框架 • 一个数据库 • 分模块整合架构（前后端分析） • 不同的框架或业务模块 • 多种数据源 • 微服务架构 通知工作流程情况给开发/或者交付 QA 测试；如何提升工程效率？我是作者名称2017 年 DevOps 现 状调查报告DevOpsDevOps DevOps 不是一种新工具； DevOps 不是一种新团队； DevOps 不是一种新角色； DevOps 是一种文化：一切自动化，工具化，规范化；选择哪个 CI/CD 工具？Docker stats 查看 Docker 服务所占用的CPU和内存开销DroneDrone

important Conan features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 5 Devops guide 145 5.1 Using ConanCenter packages in production environments . . . . . . . . . . . . . . be more structured and thorough so that it can be used more easily for automation, especially in CI/CD systems. See also: • Commands reference 2.7 New deployers Conan 2 implements “deployers”, which installed in the system. You can do it with: $ git clone https://github.com/conan-io/conan conan_src $ cd conan_src $ git checkout develop2 # or to the specific tag you want to $ pip install -e . $ python

important Conan features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 5 Devops guide 145 5.1 Using ConanCenter packages in production environments . . . . . . . . . . . . . . be more structured and thorough so that it can be used more easily for automation, especially in CI/CD systems. See also: • Commands reference 2.7 New deployers Conan 2 implements “deployers”, which installed in the system. You can do it with: $ git clone https://github.com/conan-io/conan conan_src $ cd conan_src $ git checkout develop2 # or to the specific tag you want to $ pip install -e . $ python

important Conan features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 5 Devops guide 143 5.1 Using ConanCenter packages in production environments . . . . . . . . . . . . . . be more structured and thorough so that it can be used more easily for automation, especially in CI/CD systems. See also: • Commands reference 2.7 New deployers Conan 2 implements “deployers”, which installed in the system. You can do it with: $ git clone https://github.com/conan-io/conan conan_src $ cd conan_src $ git checkout develop2 # or to the specific tag you want to $ pip install -e . $ python

important Conan features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 5 Devops guide 143 5.1 Using ConanCenter packages in production environments . . . . . . . . . . . . . . be more structured and thorough so that it can be used more easily for automation, especially in CI/CD systems. See also: • Commands reference 2.7 New deployers Conan 2 implements “deployers”, which installed in the system. You can do it with: $ git clone https://github.com/conan-io/conan conan_src $ cd conan_src $ git checkout develop2 # or to the specific tag you want to $ pip install -e . $ python