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

OpenShift Container Platform 4.13 CI/CD 包含有关 OpenShift Container Platform 构建、管道和 GitOps 的信息 Last Updated: 2024-02-17 OpenShift Container Platform 4.13 CI/CD 包含有关 OpenShift Container Platform 构建、管道和 other trademarks are the property of their respective owners. 摘要 摘要 OpenShift Container Platform 的 CI/CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 目 目录 录 第 第 1 章 章 OPENSHIFT CONTAINER PLATFORM CI/CD 概述 概述 1.1. OPENSHIFT 构建 1.2. OPENSHIFT PIPELINES 1.3. OPENSHIFT GITOPS 1.4. JENKINS 第 第 2 章 章 构

Kubernetes Native DevOps Practice — 王磊磊 @TenxCloud Agenda • Our DevOps Expectations • Kubernetes Capabilities/Advantages to Build DevOps Solution • Architecture and Features • CRD and operator design availability • Extensibility / Integration • CI/CD examples • Future plan Our DevOps Expectations • Build a platform and easy to integrate with other DevOps/third-party tools • Easy to be customized Capabilities/Advantages to Build DevOps Solution Pod Job CronJob • k8s itself is NOT a PaaS or DevOps platform，but … • k8s resources that can be used to build DevOps solution Volumes ConfigMap Secret

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 from features and not Git hashes 3.3. The new Codefresh GitOps dashboard 3.4. Argo CD Integration 3.5. CI/CD pipelines with Codefresh 3.6. Getting started with GitOps 2.0 Introduction points of GitOps: 1. GitOps covers only a subset of the software lifecycle 2. Splitting CI and CD with GitOps is not straightforward 3. GitOps doesn’t address promotion of releases between environments

Python与Devops Law 目录 CONTENTS Devops技术栈 Devops构建示例 Python工具二次开发 Devops DevOps 是一个完整的面向IT运维的工作流，以 IT 自动化以及持续集成（CI）、持续部署（CD）为 基础，来优化程式开发、测试、系统运维等所有 环节 构建Devops之前面临的问题 Devops 过程包含，代码构建打包、测试、部署、发布、监控、回滚等等一个 过程包含，代码构建打包、测试、部署、发布、监控、回滚等等一个 项目的闭环、快速构建以上过程。 构建Devops常用软件技术栈 •代码管理（SCM）：GitHub、GitLab、SubVersion •构建工具：Ant、maven •自动部署：ansible、saltstack、puppet •持续集成（CI）：Jenkins •配置管理：Ansible、Chef、Puppet、SaltStack •容器：Docker、kvm sul •脚本语言：python、ruby、shell •日志管理：ELK、Logentries •系统监控：zabbix、prometheus 前东家关于Devops的一些实践 Devops传统方式下构建示例 Devops发布流程需要考虑几个问题 1、发布什么应用，发布到哪里（CMDB） 2、发布人员是否有权限（RBAC） 3、发布过程是否有认证，授权发布（流程审计） 4、发

HorizonCD 云音乐在GitOps CD领域的最佳实践 朱旭 网易云音乐 云原生开发工程师 目 录 背景 01 Horizon模板体系 02 GitOps最佳实践 03 Horizon产品介绍 04 Horizon落地 05 背景 第一部分 背景 云主机时代的痛点 2020年，云音乐开始容器化转型 效率 低下 计算 焦虑 运维 繁琐 成本 高昂 背景 业界优秀产品 站在巨人的肩膀上，打造符合公司中长期发展的 DevOps CD 产品 - Horizon Helm Chart的理念 如何屏蔽 k8s 复杂性？ 屏蔽大部分细节，将少量配置开放给 使用者 集中了应用依赖的各种 资源 helm chart不足： • 面向开发者，对普通用户不友好 Horizon模板体系 第二部分 ├── Chart.yaml ├── README metadata: name: demo spec: replicas: 3 ... GitOps in Horizon Horizon作为面向用户的统一界面，用户不感知 gitlab 和 argo CD GitOps in Horizon 应用生命周期->代码库的生命周期 GitOps in Horizon GitOps in Horizon Horizon产品介绍 第四部分 Horizon介绍