When writing a Puppet manifest you can use the “content” reserved word. You then have quotes around the actual text content of this file right in the manifest itself. This works for a file that you want to create on a Puppet Agent server as long as the content is roughly one line of text. But for a binary file, this will not work (as it cannot appear in the manifest). The “source” reserved word allows you to point to a specific file on the Puppet Master server.
Deploying Puppet Master and Puppet Agents for the first time can involve a significant amount of troubleshooting. In this post, I want to review six miscellaneous points that may arise. These are somewhat random, but they can serve in the rudimentary stages of quickly getting a proof of concept established.
1. With a default configuration, Puppet Master on Linux will run manifests with only one name in only one location: /etc/puppet/manifests/site.pp
Many DevOps engineers do use manifests with different names.
While as of right now, there is not a great way to install Ansible on Windows servers (because you have to install cygwin). Ansible running on Linux can readily configure Windows servers and push files down to them. There are some things to look out for when setting this up. It is not overly documented on Ansible’s website. Some documentation (on various websites) tells DevOps engineers (or the professional using Ansible) to use a windows.yml file in a group_vars directory.
Are are asking yourself “why am I being prompted for a password when my SSH keys were set up correctly?” When the contents of the .pub file (the public key) are placed into the authorized_keys file (in the /home/jdoe/.ssh/ folder of a client machine), the user should be able to SSH over to the server with no password — unless the SSH key was generated with a passphrase. Assuming the SSH key was generated with an ssh-keygen command and no corresponding passphrase was entered at the time of creation,