★设置源码文件字符编码 File → Se�ngs → Editor → File Encodeings → 右侧的“Global Encoding”设 置目标字符编码，默认UTF-8 ★pycharm安装模块 File → Se�ngs → Project: xxx →Python Interpreter → 右 侧 选 择 目 标 python解释器，再点击下面的+加号 ★第2章、Centos7源码安装python3 __name__ == "__main__": print(func_out()) 结果： Hello World ★第6章、python3内置函数 内置函数是指不用import导入任何模块就能直接使用的函数 ①算术相关 abs(x) #返回x的绝对值 min(x1,x2,x3) #返回最小值 hex(x) #将x转换成16进制数，带0x oct(x) #类的属性，一个字典，由类的数据属性组成 __doc__ #类的文档字符串 __name__ #类名 __module__ #类定义所在的模块 __bases__ #类的所有父类，一个元组 ⑥析构函数 __del__(self) #析构方法，在对象销毁时被调用 ⑦特殊属性 _protedA�r

set-�mezone Asia/Shanghai #设置时区 # systemctl restart chronyd # chronyc sources -v ⑦设置网络参数 #首先加载模块 # cat > /etc/modules-load.d/br_ne�ilter.conf <模块 # cat > /etc/modules-load.d/k8s-ipvs.conf <模块 ★最后重启操作系统 # reboot ★第1章、部署k8s版本<=1.23 k8s在1.23及之前版本默认是调用docker作为底层的容器运行时，从1.24版本开 始移除了

Effective practices 1. Blameless post-mortems 2. Controlled introduction of failures for practice c. SCHEDULE BLAMELESS POST-MORTEM MEETINGS AFTER ACCIDENTS OCCUR i. Blameless Post-Mortem – meeting to examine Model – where routine and systems govern everything; including strict compliance with budget and schedule 2. Experimental Model – every day every exercise and new piece of information is evaluated and large-scale fault injection across critical systems ii. Simulate and rehearse accidents for practice 1. Schedule the event 2. Give teams time to prepare, make changes, and establish procedures 3. Execute iii

and, if necessary, building slack into the plan to manage the potential impact of the risk on schedule.  Such an approach assumes that the risks are bounded and can be itemized, that we can know be Agile. Why do people feel like there is risk in an Agile approach? They are worried about the schedule for delivering what they think of as FOC. The perceived risk is that the project will be “finished” deliver each individual piece of functionality soon.  If it becomes truly necessary to hit a schedule milestone, then we can adjust our scope to be sure that we do so. The importance that we have

References [1] Speaker Slides and Videos: http://velocityconf.com/devops-web-performance-2015/public/schedule/proceedings [2] YouTube Playlist: https://www.youtube.com/playlist?list=PL055Epbe6d5Y86GSg3nhUH3o_v62FGpCI

Still not widely adopted  Advice  Do embark on a agile self-improvement effort.  Do mix in or schedule your recurring maintenance.  Do define a primary purpose and measure it.  Do process map. 

guys put in a change request, they have to wait a lifetime to get approvals, let alone get on the schedule. We have the business breathing down our neck to get crap done. We can’t wait for you to hem and

rooms ii. For deliberate change scheduling, gather representatives, not authorize changes, but to schedule and sequence. f. ENABLE PEER REVIEW OF CHANGES i. Require peer reviews, not external board approval

manufacturing plant. The result is long lead times and poor quality 3. Consider when we have an annual schedule for software releases, where an entire year’s worth of code that Development has worked on is

Warehouse program by Em Campbell-Pretty - $200M, All streams of work were significantly behind schedule. Surprising discovery: only 50% of the source code in Dev/Test environments matched Prod. They