Create a Tower template for adding/updating the CheckMK agent

[acozine]

User story

As an engineer, I want CheckMK to stay up-to-date with any changes (new services installed, replacement VMs, etc.).

Acceptance criteria

• I can run the utils/checkmk_agent.yml playbook from a template in Tower and install the CheckMK agent on a single VM with --limit <vmname>
• I can run the utils/checkmk_agent.yml playbook from a template in Tower, update all the monitored services on existing VMs, and ensure that the CheckMK agent is installed on all VMs in an environment with --limit <envname>

Concrete example

If I run the Tower template with --limit sandbox-xk2843.princeton.edu

Implementation notes, if any

• create the template
• install the checkmk.general collection on an EE (either update an existing EE or build a new, special-purpose one)
• add a documentation line to the playbook noting that to run it locally, you need to install the checkmk.general collection
• test the template on a new VM to confirm that the playbook installs the agent
• test the template on a replacement VM to confirm that the playbook updates data collection
• test the template on a VM with recent changes to confirm that the playbook updates monitored services