gz模块安装包一样打包我们的源代码并执行setup.py去安装我们 的代码模块，可以使用distu�ls模块里的setup函数去打包 例如，我们写的代码有cof.py及lee.py两个模块，main.py只是用于测试 的主函数 现在需要把cof.py及lee.py打包成一个安装包 在我们的源程序目录下再创建一个setup.py文件，内容如下： from distutils.core import setup setup(name='cof' ython去执行此setup.py， 命令如下： >C:\Users\cof\AppData\Local\Programs\Python\Python310\python.exe setup.py sdist 这样就成了，在源程序目录下生成一个名为dist的子目录，里面有生成 的安装包 将安装包复制到其他需要使用这些程序模块的地方，再解压此安装 包， 执行里面的setup.py文件进行安装，命令如下： python3 setup.py install #将模块文件安装到本python3环 境的site-packages里 打包模块包： 现在需要把源程序目录下的cofpkg模块包打包成一个安装包 在我们的源程序目录下再创建一个setup.py文件，内容如下： from setuptools import setup setup(name='cofpkg'

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 STREAM 1 vs BROWNFIELD SERVICES i. DevOps is not just for Greenfield ii. Important Predictor – Is the application architected (or could be re- architected) for testability and deployability? iii. Successful Brownfield mainframe and supporting applications a. They 2X release frequency b. Resulted in increased application reliability c. Reduced deployment lead time from 2 weeks to <1 day 2. Etsy a. “Barely survived

yum install postgresql-server -y # EL8安装光盘AppSteam里自带有10.x 版本的软件包 # postgresql-setup --initdb --unit postgresql # systemctl enable postgresql # systemctl start postgresql 如果想安装其他版本，可到官网查询安装方法 module disable postgresql -qy # yum install postgresql13-server -y # /usr/pgsql-13/bin/postgresql-13-setup initdb # systemctl enable postgresql-13 # systemctl start postgresql-13 ★第2章、设置数据存储路径 PostgreSQL

若不能，则需要提前下载所需镜像到所有节点/或者指定使用内部镜像仓库 # kubectl apply --server-side -f ./setup/ #初始化设置， k8s v1.22版本开 始支持此命令 # kubectl create -f ./setup/ #初始化设置，适用于k8s所有版本，与 上面二选一 # kubectl

Major contributing cause of issues stems from releases representing the first time we see how an application behaves in a production-like environment ii. Don’t just document the environment specifications the value stream iii. Everything, everything, everything is checked 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, procedures, etc. 7. Application configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014

and are subsequently transmitted to receiving equipment for monitoring 1. Create telemetry in application & environments (to include production, pre-production, and CD pipeline) iii. Ian Malpass, Etsy what’s up or down. ii. Modern Monitoring architecture 1. Data Collection at business logic, application, & environments layer a. Events, logs, & metrics b. Common service to centralize, rotate, and 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 as part of their

providing application/infrastructure stacks that are pre- approved and appropriately configured and secured. f. INTEGRATE SECURITY INTO OUR DEPLOYMENT PIPELINE i. Hardening the application after development pipeline iii. Enable fast feedback on potentially insecure changes g. ENSURE SECURITY OF THE APPLICATION i. Focus on the sad paths or bad paths to effectively address QA, Infosec and related concerns

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

new requirement to be delivered and deployed. Deployment speed: how fast a new version of the application can be deployed into the production environment. Deployment frequency: how often a new release

as we try to become Agile. This frame of reference includes the notions of project, systems, application, investment, architecture, skill set, and accountability. We have, to be honest, made a jumble