This contains tips for deploying the Foglight® Agent Manager to a large number of UNIX® or Windows® hosts in your environment. It also discusses some of the deployment options you might want to consider.
Deploying the Foglight Agent Manager is a multi-step process that includes selecting and deploying an Agent Manager cartridge, downloading the Agent Manager installer, and installing the Agent Manager. The steps in this process are described in Installing external Agent Managers .
The instructions in this include references to the Agent Manager silent installer parameters.
These parameters are used with the --silent command option when you run the Agent Manager installer non-interactively—for example, to install the Agent Manager from the command-line onto remote machines, as described in the examples in this.
SeeUsing the Agent Manager silent installer for more information about these parameters.
If you are planning to deploy the Agent Manager to multiple UNIX® hosts, you can simplify the process by creating a deployment script that downloads installers, installs, and starts the Agent Manager on these hosts.
This example is based on using the Wget network utility to download Management Server installers, providing a specific set of configuration options with the Agent Manager silent installer command, and using passwords to log in to remote hosts over SSH.
However, you could instead create a script that works with any file-retrieval tool that downloads content using HTTP, such as cURL or a Perl script that uses the LWP::Simple interface.
Additionally, if you require non-default silent installer parameters, such as those used to connect to the Management Server through a proxy, you could edit the parameters used when invoking the Agent Manager silent installer to suit your environment. See Using Agent Manager silent installer Parameters for more information.
The end of the example, Part 5: Run the script , describes using one type of login method (passwords) for connecting to remote machines using SSH. However, if you have private keys configured in your environment, you might encounter different scenarios when establishing an SSH connection, which are described in Part 5: Run the script .
|
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center