systemctl start chronyd # cat > /etc/chrony.conf <file /var/lib/chrony/dri� makestep 1.0 3 rtcsync keyfile /etc/chrony.keys leapsectz right/UTC logdir /var/log/chrony cgroupdriver=systemd" ] } # mkdir -p /etc/systemd/system/docker.service.d # docker info ★docker会修改防火墙规则，导致pod网络不通 # vi /usr/lib/systemd/system/docker.service #在[Service]下的ExecStart=/usr/bin/dockerd 置文件并编辑 # vi /etc/kubeadm-init.yaml apiVersion: kubeadm.k8s.io/v1beta2 bootstrapTokens: - groups: - system:bootstrappers:kubeadm:default-node-token token: abcdef.0123456789abcdef �l: 24h0m0s usages:

查找替换 ★设置字体颜色 File → Se�ngs → Editor → Color Scheme → Language Defaults → 选中目 标Scheme ★设置背景颜色 File→Se�ngs→Editor→Color Scheme→Console Colors→Scheme → 选 择 合适的主题 ★显示空白字符 File → Se�ngs → Editor General → Appearance → 选 中 Show whitespaces ★不进行拼写检查 File → Se�ngs → Editor → Inspec�ons → Proofreading → Type 取消勾选 ★设置项目的python解释器 File → Se�ngs → Project: xxx →Python Interpreter → 右 侧 选 择 目 次数多了（按2次shi� 键），结果就弹出全局搜索框，不太友好，可以关闭此功能 File → Se�ngs → Advanced Se�ngs → 右 侧 的 User Interface ， 勾 选 Disable double modifier key shortcuts ★设置每行最大长度 File → Se�ngs → Editor → Code Style → 右侧的 General下的

★系统设置 系统设置信息保存在/etc/gitconfig文件里 # git config --system user.name cof # git config --system user.email cof@cof-lee.com # git config --system --list #查看系统设置 # git "git rm --cached <file>..." to unstage) new file: main.py #暂存区有了一个新的文件：main.py # git commit -m "msgxxx" #将暂存区提交到仓库区（commit为提交操作），- m后指定本次提交的说明信息 1 file changed, 1 inser�on(+)

mv /var/lib/pgsql/13/* /data_pg/ #将原数据目录下所有内容移动到新 数据目录下 # vi /usr/lib/systemd/system/postgresql-13.service #pg-13版本，修改systemd服 务文件，指定数据目录 #修改这行：Environment=PGDATA=/var/lib/pgsql/13/data/ # mv /var/lib/pgsql/* /data_pg/ #将原数据目录下所有内容移动到新数 据目录下 # vi /usr/lib/systemd/system/postgresql.service #pg-10版本，修改systemd服务 文件，指定数据目录 #修改这行：Environment=PGDATA=/var/lib/pgsql/data/ --reload pg_hba.conf 配 置 保 存 在 postgres 库 下 面 的 名 为 pg_catalg 的 schema 下 的 pg_hba_file_rules表里： INSERT INTO "pg_hba_file_rules" ("line_number", "type", "database", "user_name", "address", "netmask", "auth_method"

redis-server 0.0.0.0:6379 # kill -9 14989 #先结束刚刚运行的进程 # cat > /etc/systemd/system/redis.service < info # Server redis_version:6.2.13 ...... executable:/usr/local/bin/redis-server config_file:/root/redis-6.2.13/redis.conf ...... 10.99.1.51:6379> shutdown #停止服务运行，谨慎操作

and last, that the business should be thought of as a community, or perhaps as a Complex Adaptive System, which needs to be led and managed through an inspect-and- adapt, feedback-and-vision-oriented approach dysfunctional transformation cycle. It lies, I believe, in our distinction between the development of a system and its operation and maintenance.  Dividing our IT spending into development and maintenance buckets way to incrementally modernize a legacy system as defined by Martin Fowler.  Instead of building an entirely new system, we take a small piece of the legacy system and rebuild it in a way that lets it

consistent, & secure c. CREATE OUR SINGLE REPOSITORY OF TRUTH FOR THE ENTIRE SYSTEM i. ALL parts (code & environments) of the system are shared in a version control repository ii. Version control is for When a change causes the build or automated tests to fail: 1. No new work is allowed to enter the system until the problem is fixed. 2. Bring in whatever help is needed to resolve the problem iii. Prioritize tests of the integrated system as a whole 3. Work towards single-piece flow iii. Trunk & state of Deployment Pipeline represents & communicates the current state of the system iv. Modified Definition

Accidents are due to the inevitable design problems in complex systems that we build; they are system problems – not individual problems iii. Effective practices 1. Blameless post-mortems 2. Controlled “could have” a. These are counterfactual statements b. Frames the problem as the system as imagined rather than the system that actually exists 4. Focus on – “Why did it make sense to me when I took that and behavior of libraries and components ii. Test suite becomes the living documentation of the system specification and represent working examples of API use e. DESIGN FOR OPERATIONS THROUGH CODIFIED

Logging Levels 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 GTP 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 friction by adding more steps/approvals which tends to increase batch size ii. Toyota Production System – “people closest to a problem typically know the most about it.” iii. 2014 State of DevOps Report

organization iii. ENABLING ORGANIZATIONAL LEARNING AND A SAFETY CULTURE 1. When we work within a complex system, by definition it is impossible for us to perfectly predict all the outcomes for any action we processes, often to help individual departments maintain their “turf.” Failure is processed through a system of judgment, resulting in either punishment or justice and mercy. c. Generative organizations OF RECORD AND SYSTEMS OF ENGAGEMENT i. Gartner Bi-modal IT 1. Type 1 – System of Record – “Doing it right” 2. Type 2 – System of Engagement – “Doing it fast” ii. DevOps helps reject the bi-modal IT