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 Intigua for actual tool deployment. The steps for deploying a new management service using Approach 1 are as follows:
- The server node (with the Puppet agent pre-installed) requests a catalog from the Puppet master server.
- Puppet delivers a catalog containing the Intigua Puppet module and a set of Intigua resources to the node – each resource designating a management service that Intigua should deploy to the server, such as a backup tool.
- Leveraging Intigua’s APIs, the Intigua Puppet module accesses Intigua and requests the deployment to the node.
- Intigua deploys the management agents to the node.
- Intigua automatically configures the tool’s management console.
After the deployment process has been completed, Intigua 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 Intigua console.