Overview

This approach describes how management services can be configured and controlled with a Puppet master server while leveraging JetPatch for actual tool deployment, eliminating the need for users to develop custom Puppet modules for tool agents.

Management Services Are Configured and Controlled with Puppet through JetPatch

In the first approach, management services are configured and controlled with the Puppet master server, as is normally the case. 

However, instead of forcing users to develop Puppet modules for tool agents and struggling with console server configuration, Puppet simply invokes JetPatch for actual tool deployment. 

The steps for deploying a new management service using Approach 1 are as follows:

1. The server node (with the Puppet agent pre-installed) requests a catalog from the Puppet master server.
2. Puppet delivers a catalog containing the JetPatch Puppet module and a set of JetPatch resources to the node – each resource designating a management service that JetPatch should deploy to the server, such as a backup tool.
3. Leveraging JetPatch's APIs, the JetPatch Puppet module accesses JetPatch and requests the deployment to the node.
4. JetPatch deploys the management agents to the node.
5. JetPatch automatically configures the tool's management console.

After the deployment process has been completed, JetPatch automatically ensures tool health, as well as consistent configuration and stability across its lifecycle. 

In this mode, deployment operations (pushing new tools, reconfiguring tools, and removing them) are managed through the Puppet console. 

Tool reporting, operational protocol enforcement, maintenance, and diagnostics are handled through the JetPatch console.