Infrastructure As Code: Managing Servers in the Cloud (英語) ペーパーバック – 2016/6/27
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
Virtualization, cloud, containers, server automation, and software-defined networking are meant to simplify IT operations. But many organizations adopting these technologies have found that it only leads to a faster-growing sprawl of unmanageable systems. This is where infrastructure as code can help. With this practical guide, author Kief Morris of ThoughtWorks shows you how to effectively use principles, practices, and patterns pioneered through the DevOps movement to manage cloud age infrastructure.
Ideal for system administrators, infrastructure engineers, team leads, and architects, this book demonstrates various tools, techniques, and patterns you can use to implement infrastructure as code. In three parts, you'll learn about the platforms and tooling involved in creating and configuring infrastructure elements, patterns for using these tools, and practices for making infrastructure as code work in your environment.
- Examine the pitfalls that organizations fall into when adopting the new generation of infrastructure technologies
- Understand the capabilities and service models of dynamic infrastructure platforms
- Learn about tools that provide, provision, and configure core infrastructure resources
- Explore services and tools for managing a dynamic infrastructure
- Learn specific patterns and practices for provisioning servers, building server templates, and updating running servers
Kief Morris has been designing, building, and running automated IT server infrastructure for nearly twenty years, having started out with shell scripts and Perl, moving on to CFengine, Puppet, Chef, and Ansible among other technologies as they've emerged. He is the head of ThoughtWorks' European practice for Continuous Delivery and DevOps, helping clients find more effective ways of building and managing infrastructure operations.
The middle portions of the book look at design patterns related to the cloud. Often "anti-patterns" are explored as well to show what not to do. Templating servers and configuration management is detailed.
Part III of the book was basically a summary of DevOps. I found the information to be too general here, and sometimes not that relevant to Infrastructure. To give an example, the author discusses Code Reviews where he says: "All too often, code reviewing becomes a wasteful activity that doesn't lead to improvements actually being made to code. Pair programming is more rigorous, with input from two people leading to better design and improvements made in real time."
The author often states opinions like this, but does not back them up by anything but his opinion. There was no evidence provided to show that code reviews are wasteful, while pair programming boosts productivity. Maybe this has been the case for the author, but I would have liked to seen more evidence for a lot of his claims. A lot of the asides in the book were taken from the author's personal experiences and used to prove something.
I found the stronger parts of the book where the author shows configurations and details. Parts in which the author relied on personal experiences and generalizations were not as good. Overall though, this was an informative book that is helping define the new rules for cloud based architectures.
- 洋書 > Computers & Technology > Hardware > Parallel Processing Computers
- 洋書 > Computers & Technology > Microsoft > Home Computing & How-to > Windows OS
- 洋書 > Computers & Technology > Networking > Network Administration
- 洋書 > Computers & Technology > Operating Systems > Linux > Networking & System Administration