The DevOps Handbook
discovery: only 50% of the source code in Dev/Test environments matched Prod. They fixed forward, but changes not put back into version control. Focused on version control and automated environment creation environments (Prod, pre-prod(s), dev, & new) iv. Immutable Infrastructure 1. Once created no changes are allowed 2. Changes must be put into version control and then new infrastructure is created 3. To prevent that learning into future work d. Google Web Server (GWS) team was struggling with changes – Hard line: no changes would be accepted into GWS without accompanying automated tests. Spread Testing Grouplet0 码力 | 8 页 | 23.08 KB | 5 月前3The DevOps Handbook
and rehearse accidents for practice 1. Schedule the event 2. Give teams time to prepare, make changes, and establish procedures 3. Execute iii. Expose latent defects in the systems and create progressively as possible and incorporate into the 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 private changes l. CREATE SECURITY TELEMETRY IN OUR ENVIRONMENT i. Create environment telemetry 1. OS changes in production, build infrastructure, etc. 2. Security group changes 3. Changes to configurations0 码力 | 9 页 | 25.13 KB | 5 月前3The DevOps Handbook
track what they need to track, at the drop of a hat, without requiring time-sucking configuration changes or complicated processes.” iv. 2015 State of DevOps Report – high performers had MTTR 168x faster ization decisions 2. System and data access 3. System and application changes, especially privileged changes 4. Data changes (CRUD) 5. Invalid input, possible malicious injections or threats 6. Resources or Ops to create telemetry for functions built ii. Generate graphs with overlays of production changes iii. Tools – StatsD, JMX, codahale, New Relic, Prometheus, etc. f. CREATE SELF-SERVICE ACCESS TO0 码力 | 8 页 | 24.02 KB | 5 月前3A Seat at the Table: IT Leadership in the Age of Agility - Part 2
in any direction you choose. That is its latent value; the inverse of the cost of implementing changes in the future. What does such an EA, brimming with latent value, look like? It has little technical It is loosely coupled—pieces of it can be easily exchanged for newer pieces without requiring changes to the whole ball of EA. It has a robust, automated regression test suite, so that new development with continuous user feedback and then continuing to adapt the system over time as the business changes versus buying an undefined stream of future services from a vendor who doesn’t know your business0 码力 | 7 页 | 387.61 KB | 5 月前3git 操作手册
#提交当前工作目录的所有文件到暂存区(add为暂存操 作),命令最后有一个点. # git status #再次查看状态 On branch master No commits yet Changes to be commi�ed: (use "git rm --cached..." to unstage) new file: main.py 头像,点击左上角的三道杠 点击“Admin” 或者浏览器直接输入: h�ps://x.x.x.x/admin 取消勾选“Sign-up enabled”,然后点击下面的“Save changes”之后可关闭“用户申 请创建账号”的功能 ★禁用gravatar头像 gitlab默认使用gravatar头像功能,会访问www.gravatar.com网站,内网环境下导 致gitlab页面加载缓慢,可禁用此功能 或者浏览器直接输入: h�ps://x.x.x.x/admin Se�ngs→General→Account and limit 取消勾选“Gravatar enabled”然后点击下面的“Save changes”即可 ★创建普通用户账号 关闭“New naviga�on” 关闭后,左上角出现三道杠,右上角出现用户头像,点击左上角的三道杠 点击“Admin” 创建一个名为cof的用户账号,邮箱为cof@cof-lee 0 码力 | 35 页 | 1.69 MB | 1 年前3The Phoenix Project
the system to increase resilience. Four Types of Work 1. Business projects 2. IT projects 3. Changes 4. Unplanned work “What can displace planned work? Unplanned work. That’s why Erik called it the place to decide whether a change is a good idea, the role of change control board is to ensure changes have been properly coordinated with and agreed to by proper stakeholders. Attributions [1] Amazon0 码力 | 3 页 | 154.45 KB | 5 月前3A Seat at the Table - IT Leadership in the Age of Agility
organizational mindset is critical to any successful technology transformation but requires substantial changes in behavior at every level, and Mark’s thorough analysis will prove invaluable to leaders who must vision for what IT leadership must become. Uncertainty and Risk: Third, underlying all of these changes – all of the problems with plan-drive approaches, all of the advantages of Agile approaches – is0 码力 | 4 页 | 379.23 KB | 5 月前3The DevOps Handbook
waiting for responses 3. Instead a. Use peer reviews of our proposed changes to gain whatever assurance is needed that our changes will operate as designed. b. automate as much of the quality checking0 码力 | 8 页 | 22.57 KB | 5 月前3A Seat at the Table - IT Leadership in the Age of Agility
of today’s emerging workforce. These characteristics of today’s emerging workforce reinforce the changes I have been describing, making them almost inevitable. Respect for skill: Your new IT workforce development will help test. Software engineers will oversee their code in production and help make changes to the infrastructure if necessary to improve performance. Fairness and social responsibility:0 码力 | 7 页 | 387.48 KB | 5 月前3Government Excerpt
agencies. They actually have something tangible.” “Shippable product,” in their case, means actionable changes to policy. It doesn’t have to be a thing; it just has to be something, anything, that creates value0 码力 | 3 页 | 414.99 KB | 5 月前3
共 11 条
- 1
- 2