# git diff --cached #查看未提交的暂存 ★分支操作 分支（branch）的本质其实就是一个提交对象（commit），HEAD是一个指针， 它默认指向master分支，切换分支时就是让HEAD指向不同的分支。每次有新的 提交时，HEAD都会自动指向最新的提交。 首次创建分支前，得先进行一次提交，否则git无法创建分支（因为分支是基于 ★tag操作 tag是git版本库的一个标记命令，指向了某个commit的指针，tag命令主要用于 发布版本管理，当一个版本发布时，打上tag标签。 有了分支（branch）为什么还要引入tag这个概念呢？ 因为tag是相对于同一个分支而言的，同一分支不停地开发，有新增的文件，也 有修改旧的文件，每次提交（commit）后当前分支的HEAD指针会指向最新的提 交，那么如何管理旧的提交呢？可以对某个时间点的提交打个标记，方便后续 key 首先在linux服务器上生成用户的ssh密钥对文件 # ssh-keygen -t rsa -b 2048 -C "cof@cof-lee.com" -P "" -f cof-sshkey #直接生成key文件及公钥.pub文件，无需交互，-C指定密钥的描述信息，-P指定 加密密钥的密码，-f指定生成的文件名，生成的密钥文件： cof-sshkey为私钥， cof-sshkey

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 2.x版本 python3.0于2008-12-03发布 python各版本发布时间： 2024-03-08 ★第0章、linux执行python脚本的方式 python安装路径： 操 作 系 统 python 版本 安装路径 windows 2.7 C:\Python27 windows 3.10 C:\Users\ 用 户 名 \AppData\Local\Programs\Python\Python310 centos7 2.7.5 /usr/bin/python #这里可执行python代码，类似shell脚本 >>> print("hello") >>> exit() #退出交互模式 ②执行一次性代码 # python3 -c "要执行的代码，多个语句之间用;分号隔开" ③执行脚本 # vi test.py #内容如下3行 #!/usr/bin/env python3

racted/pem/tls-ca-bundle.pem ②安装k8s二进制组件 #使用aliyun的源（如果用的是RHEL8系列的系统，也是用的el7的仓库源，因为 k8s组件是用go语言写的，直接二进制文件就可用，不需要特殊的库依赖，于是 和系统弱相关，8或9系列的系统也直接可用这些rpm软件） # cat >> /etc/yum.repos.d/k8s-ali.repo <C /usr/bin/ # crictl -v #查看crictl版本 crictl version v1.28.0 # crictl images �gera-operator NAME READY STATUS RESTARTS AGE �gera-operator-59b69c49dc-t6crt 1/1 Running 1 (10m ago) 51m # kubectl get pods -n calico-system NAME

– 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 short lead times was small batch sizes of work b. Agile, Continuous Delivery, and the Three Ways 7 c. The First Way: The Principles of Flow 15 i. MAKE OUR WORK VISIBLE 1. A significant difference between the constraint usually follows this progression: a. Environment creation: b. Code deployment: c. Test setup and run: d. Overly tight architecture: iv. ELIMINATE HARDSHIPS AND WASTE IN THE VALUE

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 amplify signals to help avert the next catastrophe iii. Michael Roberto, Richard M.J. Bohmer, & Amy C. Edmondson (Harvard Business Review): organizations are typically structured as:1. Standardized Model organization is in direct proportion to the degree to which its policies are expressed as code.” c. CREATE A SINGLE, SHARED SOURCE CODE REPOSITORY FOR OUR ENTIRE ORGANIZATION i. Firm-wide shared source

automated environment build process iii. Environments will be stable, reliable, consistent, & secure c. CREATE OUR SINGLE REPOSITORY OF TRUTH FOR THE ENTIRE SYSTEM i. ALL parts (code & environments) of Delayed feedback fades the cause & effect link of the error; now requires firefighting and archaeology. c. Worst effect – lose the ability to learn from mistakes and diminish integrating that learning into development costs, 140% increase in programs under development, 78% reduction in cost per program c. SMALL BATCH DEVELOPMENT AND WHAT HAPPENS WHEN WE COMMIT CODE TO TRUNK INFREQUENTLY i. Branching Strategies

our monitoring systems need to be more available and scalable than the systems being monitored.” c. CREATE APPLICATION LOGGING TELEMETRY THAT HELPS PRODUCTION i. Dev & Ops create production telemetry metric, configure alerts when metric deviates significantly from mean 4. Repeat for weaker signals c. PROBLEMS THAT ARISE WHEN OUR TELEMETRY DATA HAS NON-GAUSSIAN DISTRIBUTION i. Many operational data new features development – feature is only “done” when it’s performing as expected in production c. HAVE DEVELOPERS FOLLOW WORK DOWNSTREAM i. Contextual Inquiry – product team watches customer use the

UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres grant all on database db_test to user1; #给user1授权，有操作 db_test库的所有权限 ★表操作 postgres=# \c db_test; #切换到目标数据库 db_test=# create table tablexx

accountability? You know the answer: Scrum. Let’s start a few thousand miles west of Washington, D.C., in the Washington state capital, Olympia. There, the past two administrations—first a Republican