barr@csgi.com @srbarr1 Overall Quality improvements, “it” goes in better, and with less issues.  Maintenance window changed from once a week to everyday  Expanded Sphere of Influence  Machine Imaging DEG and 3rd Party Application Installations  Route Adds – requires heightened security access  Database Data Script Execution  Load Balancer Node Disablement  OS and Security Patching  Requesting 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.  Do focus on Quality first

distinction between the development of a system and its operation and maintenance.  Dividing our IT spending into development and maintenance buckets leads to some ineffective ways of making decisions. A nod

our metrics 1. All production deployments should be visible on graphs 2. Similarly useful are maintenance, backups, and other activities. 3. Ch. 15 – Analyze Telemetry to Better Anticipate Problems and A/B testing helps reduce zero or negative value add features to the baseline that also increase maintenance costs and identify opportunity costs. d. INTEGRATE A/B TESTING INTO OUR RELEASE i. A/B testing

Procrastination and Self-Control – Why We Can’t Make Ourselves Do What We Want to Do  Example: Vehicle Maintenance, E-mail  Experiment: Class paper deadlines  Observations: o “We found that the students in

buying a vendor’s product, where the investment is one large lump sum—and a commitment to future maintenance payments. Then, of course, there is the risk of the vendor going out of business or discontinuing

delivered as a single “product” at the end of a project, a “product” that then only required a bit of maintenance now and then, the economics of IT delivery often favored buying a product off the shelf. But when

pg_catalg 的 schema 下 的 pg_hba_file_rules表里： INSERT INTO "pg_hba_file_rules" ("line_number", "type", "database", "user_name", "address", "netmask", "auth_method", "options", "error") VALUES (94, 'host', '{all}' #创建一个名为cof的 用户，并设置密码 postgres=# grant all on database db_test to cof; #给cof授权，有操作db_test 库的所有权限 postgres=# postgres=# revoke all on database db_test from cof; #撤销用户权限 postgres=# #提示符#前的postgres表示当前数据库名 postgres=# select datname from pg_database; #列出所有数据库（标准的sql 语句） datname ----------- postgres template1 template0 db_test postgres=#

③创建Secret secret资源是区分命名空间的 ★命令行方式创建secret 创建账号密码验证secret # kubectl create secret generic database-auth --from-literal=username=root --from- literal=password=passwd123 创建存储于某文件的认证secret # kubectl kubernetes.io/tls 2 7s database-auth Opaque 2 10m myssh-key-secret Opaque 2 3m43s # kubectl get secret database-auth -oyaml #secret的文本信息均以base64编码 "2023-12-05T21:19:48Z" name: database-auth namespace: default resourceVersion: "1167" uid: 38790a7e-30ee-4b75-8132-18bca66ca512 type: Opaque ★基于清单文件创建secret # cat > database-auth2.yaml <

0 码力 | 126 页 | 4.33 MB | 1 年前

3

environment, test, c. Swing traffic to new environment, Rollback by swinging traffic back 2. Database changes a. Create two DB – put one in read only mode, backup & restore to new environment, swing