of work were significantly behind schedule. Surprising discovery: only 50% of the source code in Dev/Test environments matched Prod. They fixed forward, but changes not put back into version control automated environment creation – time reduced from 8 weeks to 1 day b. ENABLE ON-DEMAND CREATION OF DEV, TEST, AND PRODUCTION ENVRIONMENTS i. Major contributing cause of issues stems from releases representing they get sick, you shoot them.” iii. Ensure consistency across all environments (Prod, pre-prod(s), dev, & new) iv. Immutable Infrastructure 1. Once created no changes are allowed 2. Changes must be

/boot/cmdline.txt #如果有这个文件就编辑此文件 # 在 原 有 的 console=�yAMA0,115200 console=�y1 root=/dev/mmcblk0p3 roo�stype=ext4 elevator=deadline rootwait 这行后面添加 cgroup_enable=memory cgroup_memory=1 default via 10.99.1.1 dev ens33 proto sta�c metric 100 #k8s服务器底层默认路由 10.99.1.0/24 dev ens33 proto kernel scope link src 10.99.1.61 metric 100 10.244.0.0/24 via 10.244.0.0 dev flannel.1 onlink 244.1.0 dev flannel.1 onlink #去往10.244.1/24的pod网段下一跳指向flannel.1 10.244.2.0/24 via 10.244.2.0 dev flannel.1 onlink #去往10.244.2/24的pod网段下一跳指向flannel.1 10.244.3.0/24 dev cni0

than the systems being monitored.” c. CREATE APPLICATION LOGGING TELEMETRY THAT HELPS PRODUCTION i. Dev & Ops create production telemetry as part of their daily workii. If it was important enough for an CREATION OF PRODUCTION METRICS AS PART OF DAILY WORK i. Create infrastructure to make it easy for Dev or Ops to create telemetry for functions built ii. Generate graphs with overlays of production changes ideally feature toggle off and fix-forward or use other Blue- Green, Canary release patterns b. DEV SHARES PAGER ROTATION DUTIES WITH OPS i. Complex systems will inevitably have unexpected problems

Automation: g. Myth—DevOps is Only for Open Source Software: 2. Foreword xix 3. Imagine a World Where Dev and Ops Become DevOps: a. THE CORE, CHRONIC CONFLICT i. Among them are the two following goals, which daily Work of Development a. CREATE SHARED SERVICES TO INCREASE DEVELOPER PRODUCTIVITY i. Enable Dev teams to spend more time building functionality, as opposed to created infrastructure ii. Automation LIAISON TO EACH SERVICE TEAM i. Reduces costs compared to embedded operations d. INTEGRATE OPS INTO DEV RITUALS i. Help better understand development culture. ii. Radiate operational concerns into the

support Putting Performance Best Practices Together to Create the Perfect SPA by Chris Love (Love2Dev) @ChrisLove http://www.slideshare.net/docluv/putting-performance-best-practices-together-for-a-spa

organizational software engineering culture and practice that aims at unifying software development (Dev), security (Sec) and operations (Ops). The main characteristic of DevSecOps is to automate, monitor

RITUALS TO PAY DOWN TECHNICAL DEBT i. Regularly schedule day- or week- long improvement blitzes with Dev & Ops teams. Focus on problems they care about. NO FEATURE WORK ii. Goal is focused improvement on

financial incentives to supportyou. Text “1” to @obvious if you like the first option, or “2” to @/dev/null if you prefer the second. Governance and Oversight Governance has traditionally been viewed

are managed by 'conda init' !! __conda_setup="$('/root/anaconda3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)" if [ $? -eq 0 ]; then eval "$__conda_setup" else if [ -f "/root/anaconda3/etc/profile