preface part ⅰ. foundations 1. challenges and principles why infrastructure as code? what is infrastructure as code? goals of infrastructure as code challenges with dynamic infrastructure server sprawl configuration drift snowflake servers fragile infrastructure automation fear erosion principles of infrastructure as code systems can be easily reproduced systems are disable systems are consistent processes are repeatable design is always changing practices use definition files self-documented systems and processes version all the things continuously test systems and processes small changes rather than batches keep services available continuously antifragility: beyond "robust" the secret ingredient of antifragile it systems conclusion whats next? 2. dynamic infrastructure tforms what is a dynamic infrastructure tform? requirements for a dynamic infrastructure tform programmable on-demand self-service infrastructure resources provided by the tform pute resources storage resources work resources types of dynamic infrastructure tforms public iaas cloud munity iaas cloud private iaas cloud antipattern: hand-cranked cloud hybrid and mixed cloud options bare-metal clouds deci on a dynamic infrastructure tform public or private? cloud portability mechanical sympathy with the cloud and virtualization conclusion 3. infrastructure definition tools choosing tools for infrastructure as code requirement: scriptable interface requirement: unattended mode for mand-line tools requirement: support for unattended execution requirement: externalized configuration configuration definition files reusability with configuration definitions working with infrastructure definition tools provisioning infrastructure with procedural scripts defining infrastructure declaratively using infrastructure definition tools configuring servers …… part ⅱ.patterns part ⅲ.practices
以下为对购买帮助不大的评价