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 State of DevOps ability to learn from mistakes and diminish integrating 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 eliminates “worked on my machine” 3. Package the application to enable repeatable installation and configuration into an environment 4. Environments can be more production-like in a consistent and repeatable

technology under the sun  Solaris, Windows, Linux  Apache, IIS, TCServer, etc.  Oracle, DB2, SQL Server  How we got better  We read and we studied.  Created a self-improvement project  2 week iterations possible. Control our destiny  Started to engineer solutions for issues related to product configuration and deployment  Built a strong relationship with development (built empathy)  Development

source code repository is powerful way to share local discoveries to the entire organization 1. Configuration standards for libraries, infrastructure, and environments 2. Deployment tools 3. Testing standards infrastructure, etc. 2. Security group changes 3. Changes to configurations 4. XSS, SQLi attempts 5. Server errorsii. Consider blocking and storing source of events when attacks are detected to facilitate

including software and security engineers, data specialists, testers, quality assurance, and configuration managers. Ideally these participants are co-located in the same physical space. While Agile some established periods where the operational community cannot integrate new releases. 9.5 Configuration Management (CM) The many smaller developments and flexible requirements process that characterize additional CM methods for Agile include:  Assign the daily management of configuration items to the Agile team, while a Configuration Manager focuses on program/enterprise-level activities such as creating

engineers to 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

”  “I have to manually type in hundreds of server names in one of the text boxes. Most of the time, there’s not enough room in the field! A hundred server names are supposed to fit in a sixty-four-character