Overview

This article describes the automation scripts included in the JetPatch Puppet integration. 

The scripts cover two areas: client-side functionality tests using the agent's CLI and custom modules, and back-end functionality tests triggered from the master server using Puppet manifests and MCollective.

Agent's Client Functionality Test Scripts

The following scripts test agent operations initiated from the client side using CLI commands and Puppet custom modules:

• Execute several workflows using the agent's CLI commands and a Puppet custom module
• Install/uninstall package via manifest on target node
• Run script (search) via manifest on target node
• Check the agent's logs to ensure the successful execution of operations in previous steps

Agent's Back-End Functionality Test Scripts

The following scripts test agent operations triggered from the back-end master server using Puppet manifests and MCollective:

Puppet Manifest

• Trigger Agent's functionality from the back-end server using Puppet manifest
• Install package via manifest from master server on target node
• Uninstall the package from the endpoint via the back-end server using the Puppet manifest

MCollective

• Trigger Agent's functionality using Puppet MCollective
• Install the package via mcollective from the master server on the target node
• Get the status of a package via mcollective from the master server on the target node
• Purge a package via mcollective from the master server on the target node
• Search for info on the node from the backend server
• Get the status of a service on the target node from the master server via mcollective
• Stop/start the service on the target node from the master server via mcollective
• Disable vAgent on the target node from the master server
• Re-enable vAgent on the target node from the master server

Validation

• Check Agent logs to ensure the successful execution of operations in the previous steps