Step 1 — Run the Collector Installer
On the designated on-premises manager node, run:
chmod +x installer.minerva.collector.<BUILD>
./installer.minerva.collector.<BUILD>
Installer Prompts
Collector Bootstrap Bundle File Path
Collector bootstrap bundle file path
The path of the collector bootstrap bundle generated after the Platform Stack installation. This bundle provides the Collector Stack with the information it needs to reach the Platform Stack (for example, the Platform Stack IP address) and includes sensitive credentials.
Warning: The Collector Bootstrap Bundle includes sensitive credentials and certificates. Please ensure it is transmitted using a secure method in compliance with your organization's information security policies.
Host time, DNS, logrotate, docker subnet
Same as described in Step 1 of the cloud-side installation.
Platform Stack FQDN
Enter Platform Stack IP address or FQDN:
The publicly reachable FQDN or IP address of the cloud platform manager node. This is the address the on-premises services use to reach the Platform Stack. Example: minerva.nvidia.example.com
Tenant name (optional)
Enter a tenant name. Hit Enter for default:
Using tenants provides a mechanism for isolating metrics within a single Platform Stack. Leave blank to use the default tenant.
Outbound proxy
Enter outbound HTTP or HTTPS proxy URL if any. Hit Enter if none:
The proxy is used by on-premises services to reach the internet. TCP connectivity between platform and collector on ports 14317, 443, and 24317 remains mandatory.
Step 2 — Configure deploy-cfg.yml
The installer creates and configures deploy-cfg.yml. Only merge approved local overrides (e.g. changing the proxy)
Do not edit deploy-cfg-default.yml — it is overwritten on every upgrade.
Step 3 — Bring Up the Stacks
From ~/minerva/ on the on-premises manager:
./svm stack-up all
Next: Initial Configurations
Last updated: