python3学习手册 简介： Python官网： h�ps://www.python.org Python由Guido van Rossum于1989年底发明，于1991年发行第一版， Python源代码遵循GPL协议 Python是一种解释型、面向对象、动态数据类型、可交互的语言 python2.0于2000-10-16发布，于2020年1月1日停止更新2.x版本， Python-2.7成为最后一个py ①进入交互模式 # python3 #输入python3 回车 >>> #这里可执行python代码，类似shell脚本 >>> print("hello") >>> exit() #退出交互模式 ②执行一次性代码 # python3 -c "要执行的代码，多个语句之间用;分号隔开" #内容如下3行 #!/usr/bin/env python3 # coding=u�-8 print("hello world") # chmod +x test.py #添加可执行权限 # python3脚本文件开头位置要指定以下2行（使用的python解释器及本 源码文件编码） #!/usr/bin/env python3 # coding=u�-8

k8s操作手册 前言： 1.蓝色字体表示命令行命令，正式执行时不要复制前面的#号，#号只是提示应 该使用root权限操作 2.绿色字体表示注释，有时注释太多就不用绿色表示了 3.注意：本文档的所有操作请先在测环境进行实践，请不要直接在真实的服务 器中操作！ 版权声明： 本文档以开源的形式发布，所有条款如下： （1）无担保：作者不保证文档内容的准确无误，亦不承担由于使用此文档所导致的任何后果 里。如： 主机名 ip地址 k8s-master1.cof-lee.com 10.99.1.51 k8s-master2.cof-lee.com 10.99.1.52 k8s-master3.cof-lee.com 10.99.1.53 k8s-node01.cof-lee.com 10.99.1.61 k8s-node02.cof-lee.com 10.99.1.62 规划Pod网络： com k8s-master1 10.99.1.52 k8s-master2.cof-lee.com k8s-master2 10.99.1.53 k8s-master3.cof-lee.com k8s-master3 10.99.1.61 k8s-node01.cof-lee.com k8s-node01 10.99.1.62 k8s-node02.cof-lee.com k8s-node02

git操作手册 前言： 1.蓝色字体表示命令行命令，正式执行时不要复制前面的#号，#号只是提示应 该使用root权限操作 2.绿色字体表示注释，有时注释太多就不用绿色表示了 3.注意：本文档的所有操作请先在测环境进行实践，请不要直接在真实的服务 器中操作！ 版权声明： 本文档以开源的形式发布，所有条款如下： 1. 无担保：作者不保证文档内容的准确无误，亦不承担由于使用此文档所导致的任何后果 #查看所有设置（全局+本地+系统） # git config user.name #查看用户名 ★以上3个范围的设置优先级： 本地设置 > 全局设置 > 系统设置 ★push.default配置项 # git config --local push.default simple (HEAD -> master) msgxxx # git log 文件名 #查看目标文件的提交记录 # git log -p -3 #查看最近3次提交记录 # git reflog #查看git操作记录 # git reset HEAD^

LEARNING CULTURE i. Unjust responses to incidents 1. Impede safety 2. Promote fear over mindfulness 3. Create bureaucracy rather than carefulness 4. Cultivate secrecy, evasion, and self-protection ii improve safety by allowing them to give detailed accounts of their contributions to the failures 3. Enable and encourage people who do make mistakes to be the experts who educate the rest of the organization involved in decisions that may have contributed to the problem 2. People who identified the problem 3. People who responded to the problem 4. People who diagnosed the problem 5. People who were affected

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 into version control 1. Application code & dependencies 2. Environment scripts & creation tools 3. DB scripts and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation changes are allowed 2. Changes must be put into version control and then new infrastructure is created 3. To prevent variance: a. Disable remote logins to productions b. Routinely kill and replace production

1. Debug – anything that happens in the program 2. Info – user driven actions or system specific 3. Warn – conditions that could become an error and will likely trigger an alert 4. Error – error conditions Security & Risk Management group) 1. Authentication/authorization decisions 2. System and data access 3. System and application changes, especially privileged changes 4. Data changes (CRUD) 5. Invalid input organizational goals 2. Business metrics typically represent part of the customer acquisition funnel 3. Goal – Actionable metrics that inform changes. If not actionable, likely a vanity metric. 4. Reinforces

“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 that cascade through the entire 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 center positioned after the bottleneck, it remains starved, waiting for work to clear the bottleneck. 3. In typical DevOps transformations, as we progress from deployment lead times measured in months or

preening How does it work? 1. Choose a task you’d like to get done 2. Set the Pomodoro for 25 minutes 3. Work on the task until the Pomodoro rings 4. When the Pomodoro rings, put a checkmark on a paper accomplish a specific task 2. Learn to protect your Pomodoro from the internal and external interruption 3. Make accurate estimations of how many Pomodoros you need for a certain activity 4. Set a timetable seasonWhy does this work? (Theory) Flow: The Psychology of Optimal Experience by Mihaly Csikszentmihalyi [3] From Amazon.com Psychologist Mihaly Csikszentmihalyi's famous investigations of "optimal experience"

postgresql操作手册 前言： 1.蓝色字体表示命令行命令，正式执行时不要复制前面的#号，#号只是提示应 该使用root权限操作 2.绿色字体表示注释，有时注释太多就不用绿色表示了 3.注意：本文档的所有操作请先在测试机里进行实践，请不要直接在真实的服 务器中操作！ 版权声明： 本文档以开源的形式发布，所有条款如下： （1）无担保：作者不保证文档内容的准确无误，亦不承担由于使用此文档所导致的任何后果 Environment=PGDATA=/data_pg/data/ # systemctl daemon-reload # systemctl restart postgresql ★第3章、设置监听ip及端口号 pg默认监听127.0.0.1的ip及5432/tcp端口 ★PG-13版本 # vi /var/lib/pgsql/13/data/postgresql.conf db_namexx; #删除数据库，谨慎操作 创建用户并授权： postgres=# create user user1 with password 'passwdxxyy3'; #创建一个名为user1 的用户，并设置密码 postgres=# grant all on database db_test to user1; #给user1授权，有操作

edule/proceedings [2] YouTube Playlist: https://www.youtube.com/playlist?list=PL055Epbe6d5Y86GSg3nhUH3o_v62FGpCI