A Seat at the Table – IT Leadership in the Age of Agility – Part 3 By Mark Schwartz “Courage, I say, is the value most needed by Agile IT leaders.” – Mark Schwartz Last Time in Part 2 Enterprise in no sense a “final” operating capability. Quality It is difficult for IT to gain a seat at the table when IT is always failing, but on the other hand, an IT leader who is reacting to statistical noise—failures and ties.The CIO’s Place at the Table IT leadership runs the business along with the others who run the business. The seat at the table is earned by being at the table. The role of senior IT leadership

A Seat at the Table – IT Leadership in the Age of Agility By Mark Schwartz “Mark Schwartz is a rare combination: a deep thinker who has also applied lean, Agile, and DevOps principles at the highest adapt, feedback-and-vision-oriented approach because of its complexity. A Nimble Approach to The Table Agile in One Paragraph: Agile thinking simply says that we should empower small teams to inspect adopting an intelligent attitude toward risk. Quality: It is difficult for IT to gain a seat at the table when IT is always failing, but on the other hand, an IT leader who is reacting to statistical noise—failures

A Seat at the Table – IT Leadership in the Age of Agility – Part 2 By Mark Schwartz “To the talented and hard-working government employees, so resilient in the face of impediments, criticism, and abuse sort of Star Chamber—a dimly lit group of serious, hooded faces (“decision makers”) seated around a table, passing judgment on each “formal proposal” presented to them. That last piece of Hunter and Westerman’s adopting an intelligent attitude toward risk. Quality: It is difficult for IT to gain a seat at the table when IT is always failing, but on the other hand, an IT leader who is reacting to statistical noise—failures

kubeadm init --kubernetes- version=v1.19.4 \ --apiserver-adver�se- address=10.99.1.51 \ # api server地址 --pod-network-cidr=10.244.0.0/16 \ # pod容器网段 --service-cidr=10.7.0.0/16 \ # service网段，即cluster kubeadm init --kubernetes- version=v1.28.2 \ --apiserver-adver�se- address=10.99.1.51 \ # api server地址 --pod-network-cidr=10.244.0.0/16 \ # pod容器网段 --service-cidr=10.7.0.0/16 \ # service网段，即cluster 高可用集群拓扑图： ★先配置HA高可用的反向代理 本例中vip为10.99.1.54（三台master ip为10.99.1.51~53）使用haproxy做反向代理 frontend k8s_api_tcp_6443 bind *:6443 mode tcp default_backend my_k8s_cluster_6443 backend my_k8s_cluster_6443

行sql语句 # 查询是否有名为'tb_test'的表 sqlite_cursor.execute( 'SELECT * FROM sqlite_master WHERE "type"="table" and "tbl_name"="tb_test";') result = sqlite_cursor.fetchall() # fetchall()从结果中获取 所有记录，返回一个list，元素为（即查询到的结果） print("tables: ", result) if len(result) == 0: # 若未查询到有此表，则创建此表 sqlite_cursor.execute("create table tb_test (id varchar(36) NOT NULL PRIMARY KEY,name varchar(128),age int)") try: sqlite_cursor.execute("insert tree_1_2 = tree_root.insert(tree_1, 2, "any", text="any") tree_2_0 = tree_root.insert(tree_2, 0, "api", text="api") tree_2_1 = tree_root.insert(tree_2, 1, "auth", text="auth") tree_2_2 = tree_root.insert(tree_2

create table tablexx (name VARCHAR(32), age INT, class INT); #创建名 为tablexx的表，3个字段 db_test=# \d tablexx; #查看表结构 Table "public ---------+-----+------- cof-lee | 28 | 1511 Tom | 23 | 1512 (2 rows) db_test=# drop table table_namexx; #删除数据表（谨慎操 作） ★说明： "public"."tablexx"中的public不是数 7753 kB db_test | 7901 kB # select pg_rela�on_size('table_name'); #查看表的大小，单位字节 # select pg_size_pre�y(pg_rela�on_size('table_name')); #以方便阅读的单位列 出表的大小 ★不建议使用带\反斜杠的内置命令，有些sql终端工具不支持发送带有\反斜杠

that could become an error and will likely trigger an alert 4. Error – error conditions such as API failures, internal issues 5. Fatal – forces a termination iv. Examples of potentially significant Use telemetry to measure outcomes iv. Etsy open-sourced their experimentation framework – Feature API e. INTEGRATE A/B TESTING INTO OUR FEATURE PLANNING i. Product owners should consider each feature

suite becomes the living documentation of the system specification and represent working examples of API use e. DESIGN FOR OPERATIONS THROUGH CODIFIED NON-FUNCTIONAL REQUIREMENTS i. Designing for fast changes through pair programming or code review 3. Instrument the repository to detect suspicious code (API calls from certain types of test code) 4. Ensure every CI process is in an isolated container 5

Coined by Martin Fowler in 2004 ii. Strangler Application 1. Put existing functionality behind an API 2. New functionality implemented in new services with new architecture 3. Make calls to old system

然后普通用户就可在自己的项目里配置“WebHook”功能了 Se�ngs→Webhooks→Add new webhook Webhook URL： h�p://10.99.1.241:32433/api/v2/job_templates/42/gitlab/ Webhook Key： vHRMIUlRQql9khxfr23sVlaeeMaLA7pZEmbKmmECeFL3bgF7kP Trigger可选择“Push