Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version | Location | Description | Submitted by | Date submitted |
|---|---|---|---|---|
| Printed | Page 20 First paragraph, "Infrastructure definition tools" |
"Used to manage the allocation and configuration [of] servers, [...]" |
m4z | Oct 06, 2021 |
| Printed | Page 51 Last paragraph above example 3-3 |
"appserver" should probably be "app" like in the CLI command and example 3-3. |
m4z | Oct 13, 2021 |
| Printed | Page 108 Figure 6-2 |
The figure shows two identical nginx webserver templates. Since the figure is about role-inheritance hierarchy (the "arrows"), this duplication makes no sense, it just adds redundancy. |
m4z | Oct 23, 2021 |
| Printed | Page 114 Section "Example of pulling to bootstrap" |
The code listing says "... template that implements push provisioning". Should be pull provisioning instead. |
Martin | Dec 27, 2020 |
| Printed | Page 128 Box "Example Naming Convention" |
The first two variables on line 2 contain extra backslashes behind the dollar signs. |
m4z | Oct 25, 2021 |
| Printed | Page 134 Last bullet point |
"Errors changes" should probably be "Errors in changes" or "Errors caused by changes" |
m4z | Oct 25, 2021 |
| Printed | Page 134 Paragraph below "Models for Server Change Management" |
"for making configuration changes servers" is probably missing an "on" before "servers" (or maybe it's supposed to be "server configuration changes"). |
m4z | Oct 25, 2021 |
| Printed | Page 135 Last paragraph before box |
"as with the Phoenix" is probably supposed to be a reference to the section "Pattern: Phoenix Servers" on p. 137. |
m4z | Oct 25, 2021 |
| Page 139 2nd section heading |
The heading of the 2nd section on page 139 is called "Practice: Apply Cron" but the content of this section has nothing to do with cron. It's more about using the same configuration tool across the servers lifecycle |
Ilja Bauer | Jul 24, 2016 | |
| Printed | Page 144 3rd heading |
In the 3rd heading "Confirmation Management Tooling" should be "Configuration Management Tooling" |
Ilja Bauer | Aug 08, 2016 |
| Printed | Page 144 Heading the middle of the page |
"Simplifying Confirmation Management" should be "… Configuration …". |
m4z | Oct 25, 2021 |
| Printed | Page 156 Both terraform command lines (lower half of the page) |
The section is about using the same definition file for multiple environments, yet both commands use different files via "-state". |
m4z | Oct 26, 2021 |
| Printed | Page 156 Both terraform command lines (re: my previous entry) |
Obviously I (did not read the warning box at the end of the page before posting and) do not understand how terraform finds the definition file. Maybe this could be clarified. |
m4z | Oct 26, 2021 |
| Printed | Page 228 "DevOops" Box, last paragraph |
The text reads "none of the servers were unable to resolve", which should probably be either s/unable/able/ or s/none/all/. |
m4z | Oct 06, 2021 |
| Mobi | Page 11905 text |
"templates an AWS, Aminator.4" should be "templates on AWS, Aminator.4" |
Anonymous | Oct 18, 2019 |