（python3无long长整型） True=1, False=0 string 有序strx='xxxx' stry="xxx" 不区别单引号与双引号， 单个字符也是string list 有序 列表，数组 tuple 有序 元组 set 无序 不重复（自动删除重复项） 集合 py3新 增 dic�onary 无序 字典 数 组 ， 其 元 素 值 可 变 ， 其 元 素 类 型 为 int （0~255） py3新增 不可变类型： Number String Tuple bytes 可变类型： List Dic�onary Set bytearray set 集合是由若干个元素组成的，基本功能是 进行成员关系测试 和 删 除重复元素 set可以进行数学上的集合运算（差集，并集，交集等） listxx) 将字符串str型list转为int型list strlist = ["23","15","6","44"] #元素类型为str strnn = list(map(int, strlist)) #map()将strlist的元素 都转为int型，map()返回的是map类型，需要再使用 list()转为list型 tuple(map(int

OUR CENTRALIZED TELEMETRY INFRASTRUCTURE i. Remove the silos of information – Developers don’t just log what’s interesting to development. Operations don’t just monitor what’s up or down. ii. Modern Monitoring ON UNDESIRED OUTCOMES i. An approach 1. Analyze most severe incident in recent past. 2. Create list of telemetry that could have enabled earlier detection and diagnosis as well as confirmation 3. effective monitoring in place, reliable deployments, and architecturally suitable to fast, frequent change b. Identifies any regulatory or contractual compliance objectives2. Ops engineers consult with teams

git config --global h�p.sslVerify false #不验证ssl证书 # git config --global --list #查看全局设置 ★本地设置 针 对 单 一 项 目 的 设 置 ， 使 用 --local 参 数 ， 本 地 设 置 信 #设置邮箱 # git config --local h�p.sslVerify false #不验证ssl证书 # git config --local --list #查看本地设置 ★系统设置 系统设置信息保存在/etc/gitconfig文件里 # git config --system config --system user.email cof@cof-lee.com # git config --system --list #查看系统设置 # git config --list #查看所有设置（全局+本地+系统） # git config user

/var/lib/chrony/dri� makestep 1.0 3 rtcsync keyfile /etc/chrony.keys leapsectz right/UTC logdir /var/log/chrony EOF # �medatectl set-�mezone Asia/Shanghai #设置时区 # systemctl restart chronyd # family="ipv4" source address="10.244.0.0/16" accept' # firewall-cmd --run�me-to-permanent # firewall-cmd --list-all ★如果有硬件交换机做ACL或基于云的安全组做访问控制，则可关闭服务器上的 防火墙软件 ⑨加载ipvs模块 # cat > /etc/modules-load.d/k8s-ipvs ③k8s集群初始化 # kubeadm version #先查看k8s版本 # GitVersion:"v1.19.4" # kubeadm config images list #查看k8s其他组件的docker镜像名，默认用 k8s.gcr.io/的镜像源地址 k8s.gcr.io/kube-apiserver:v1.19.4 k8s.gcr.io/kub

Creating performance testing environments can easily be more complex than the application itself iv. Log performance results and evaluate compared to previous results l. INTEGRATE NON-FUNCTIONAL REQUIREMENTS OUR ANDON CORD WHEN THE DEPLOYMENT PIPELINE BREAKS i. Keep the build in a green state ii. When a change causes the build or automated tests to fail: 1. No new work is allowed to enter the system until deployment 3. Peer reviews iv. 2013 State of DevOps Report – no statistically significant difference in change success rates between organizations where Development deployed code and those where Operations deployed

GitHub Pull Requests by Ralph Bodenner (New Relic) https://bit.ly/pull-request-your-culture  How you change your process matters  Terms: culture, metaprocess, process, entropy  Actively discourage email: com/devops-web-performance-2015/public/schedule/proceedings [2] YouTube Playlist: https://www.youtube.com/playlist?list=PL055Epbe6d5Y86GSg3nhUH3o_v62FGpCI

total of nine hours time the seven steps…” Change Control  “We need to tighten up our change controls… what’s preventing us from getting there?”  “That change management tool is impossible to use. There’s boxes for ‘applications affected’ don’t even have what I need. It’s why I’ve stopped even putting in change requests.”  “I have to manually type in hundreds of server names in one of the text boxes. Most to fit in a sixty-four-character text box? What idiot built that form?”  “When my guys put in a change request, they have to wait a lifetime to get approvals, let alone get on the schedule. We have the

kick start testing efforts – Part 6: The Technical Practices of Integrating Information Security, Change Management, and Compliance 1. Introduction a. Goal to simultaneously achieve Information Security and recovery v. Protect our deployment pipeline vi. Integrate our deployment activities with our change approval process vii. Reduce reliance on separation of duties 2. Ch. 22 – Information Security Protecting the Deployment Pipeline a. INTEGRATE SECURITY AND COMPLIANCE INTO CHANGE APPROVAL PROCESSES i. Effective change management recognized different risks associated with different types of changes

should make a plan and then stick to it is a terrible idea in an environment of uncertainty and change. It has dominated the IT world because it appears to offer predictability, control, and efficiency hollow and missing needed capabilities.  We want a smooth ball of EA, an EA shaped to facilitate change and reuse, something you can easily roll in any direction you choose. That is its latent value; it based on user feedback is often lower than that of buying a finished product that is hard to change.  The advantages of the agility that can be gained through a flexible, changeable, custom system

DEVOPS i. Code and change deployments (thirty times more frequent) ii. Code and change deployment lead time (two hundred times faster) iii. Production deployments (sixty times higher change success rate) in poor flow and poor quality outcomes. This validates our common experience that the larger the change going into production, the more difficult the production errors are to diagnose and fix, and the Critical Mass & Silent Majority 3. Identify the Holdouts ii. Ron van Kemenade, CIO of ING, “Leading change requires courage, especially in corporate envrionments where people are scared and fight you. But