从十到千，响应团队规模的敏捷与DevOps实践-冯斌

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

GitOps 2.0 THE FUTURE OF DEVOPS Table of Contents 1. The Pains of GitOps 1.0 1.1. GitOps tools 1.2. Splitting CI and CD 1.3. Promotion of releases between environments 1.4. Modeling multi-environment way you will have full traceability on each production change and can also easily answer critical DevOps metrics such as lead time (the time it takes from a commit to reach production). Observability environment) is often missing or considered secondary knowledge. Additionally, some of ​the classic DevOps metrics​ are very hard to monitor with current GitOps tools. Especially the lead time (the time

云原⽣ DevOps 平台 企业咨询 产业数字化 研发加速度 产品介绍 01 公司介绍 KodeRover 是国内云原⽣ DevOps 领域的领军企业，帮助企业提升产 研⼯程化⽔平，加速产业数字化进程，快速响应市场需求。核⼼团 队由国内外云计算、DevOps、⼯程运筹学领域专家组成，已连续完 成由盈动和经纬领投的天使轮/PreA 轮融资。公司旗舰产品云原⽣ DevOps 平台 Zadig Lead 肇兴 基本信息 “Zadig 毫⽆疑问是业界优秀的 CI/CD 产品，它也是真正理解微服务、重视微服务、 解决微服务痛点的产品。我们充分感受到 Zadig 的优秀设计思想是⾮常值得字节 DevOps 团队借鉴学习的。” Zadig 理念 & 应⽤ Zadig 具备丰富的开放能⼒ 可以集成⼀切 Zadig 产品特性 路特斯某运维团队，抛弃传统⼯具，⽤ Zadig 将研发重复性事务⾃动 到业务创新！ 字节跳动⻜书的若⼲团队⽤ Zadig 实现主⼲开发、持续验证，周部署 达 1200 次。完成⼤规模微服务的联调、集成测试，⾛上云原⽣ DevOps 交付之路！ Zadig 打通内部研发交付和外部客⼾交付，对内实现云原⽣ DevOps ⼯程化、基线 化。通过云原⽣技术和⼯程能⼒，建⽴企业多维度数字化能⼒，从业务、流程、质 量、成本管理，释放“数字⼯程师”⽣产⼒。 Zadig 研发数字化成功案例

Unsplash Cheng Wei Chen @ Cloud Edge Sumit 2020 From DevOps to GitOps with GitLab Cheng Wei Chen 陳 正瑋 DevOps Engineer @ 得寬科技
 《Effective DevOps 中⽂版》譯者、GitLab Hero http://chengweichen.com https://devopstw CI/CD Continuous Integration Continuous Delivery And Automation GitOps = IaC + MRs + CI/CD DevOps Photo by Fancycrave on Unsplash 範例分享 新 Issue Coding Commit CI/CD Pipeline 建立 Feature branch Code Review & Approve 4. Multi environment 5. CI/CD 6. Use Repository 7. Agile & Iteration DevOps 1. IaC 讓⼀切都成為 Code 2. Automation 盡可能⾃動化 如果不成，就紀錄它！ 3. Code Review & Approve 審查、複閱、檢查、稽核

your DevOps teams P.2 Git familiar with DevOps and GitOps For over a decade, software companies have been trying to move away from the waterfall approach to application development to the DevOps approach work together to handle everything themselves—from building and testing to deploying. The move to DevOps requires technical and cultural changes at an organizational level. A new set of tools that can Organizational leaders must also create a new culture that celebrates iterating and failing fast. Moving to DevOps is almost always worth the effort. It allows developers to roll out changes and updates very quickly