Jon Forrest
2014-Mar-12 22:49 UTC
[Puppet Users] Problems in Ch. 8 and 9 of Pro Puppet 2nd Edition
Here are the issues I found in Chapters 8 and 9. Jon Forrest M = mistake U = unclear T = typo E = text change C = comment (T) Pg. 191 "like librarian puppet" -> "like librarian-puppet" (T) Pg. 191 "rspec-puppet, rspec-system and integrating" -> "rspec-puppet, rspec-system, and integrating" (U) Pg. 194 "mysql::db provider" What's a "provider"? (T) Pg. 196 "The puppet-module tool" -> "The Puppet Module tool" (This is how you've referred to it up to now.) (T) Pg. 197 "in your version control" -> "in your version control system" (U) Pg. 197 "you will need to remove the contents" Do you mean to remove the contents of /etc/puppet/modules from the file system or from the version control system, or both? (E) Pg. 197 "You can specify the version" -> "You can specify the version you want to install" (E) Pg. 198 "to version control" -> "to your version control system" (C) Pg. 198 You haven't mentioned Puppetfile.lock before. You should say something about it if it's so critical that it needs to be kept in a version control system. (T) Pg. 199 "First up is puppet lint" -> "First up is puppet-lint" (E) Pg. 202 "want a fixtures file" -> "want a .fixtures.yml file" (T) Pg. 202 "we have modified fixtures.yml" -> "we have modified .fixtures.yml" (E) Pg. 203 "specify osfamily as one of the OS families" -> "assign osfamily the name of one of the OS families" (E) Pg. 203 "it will throw an error" -> "spec will throw an error" (Is the name of this tool "spec" or "rspec"?) (T) Pg. 208 "creating the rspec system directory layout" -> "Creating the rspec-system directory layout" (T) Pg. 210 "and then CD to the Vagrant folder" -> " "and then cd to the Vagrant folder" (T) Pg. 210 "Accessing rspec system Vagrant machines" -> "Accessing rspec-system Vagrant machines" (E) Pg. 217 "sent to the master server" -> "sent to the Puppet master" (E) Pg. 217 "success or failure of those resources" -> "success or failure of those changes" (E) Pg. 221 "Specifying this tag will make the report return all error messages" -> "Specifying this tag will make Puppet send all error messages" (E) Pg. 221 "We can install RRDTools via package" -> "We can install the RRDTools package" (E) Pg. 221 "Red Hat, CentOS, and Mandriva versions" -> "Red Hat, CentOS, and Mandriva" (E) Pg. 222 "Both gems should work to produce" -> "Both gems should produce" (E) Pg. 222 "in the form of an HTTP Post" -> "via an HTTP Post" (E) Pg. 222 "on the master" -> "on the Puppet master" (E) Pg. 222 "supports the importation of" "supports importing" (U) Pg. 223 "Instead, the report processors are stored in the lib/puppet/reports directory. For example, on an Ubuntu Puppet master we'd add our custom report processor to the /usr/lib/ruby/vendor_ruby/puppet/reports" directory" The second location mentioned, /usr/lib/ruby/vendor_ruby/puppet/reports, is not in lib/puppet/reports, as the first sentence says it should be. (E) Pg. 223 "You could also parse particular" -> "You could also filter particular" (E) Pg. 223 "We also wrote our summary report out to a directory named after the Puppet agent host located under the reports directory" -> "We also wrote our summary report out to a directory, located under the reports directory, named after the Puppet agent host" (T) Pg. 225 "reporting data from thecode" -> "reporting data from the code" -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAF0Z9iqHSxSY35unOZtC-aW3hS4shw6ak9z%2Bnz0RNzV2tvXVOQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.