Triton deployment planning
Modified: 13 Dec 2022 21:28 UTC
This section explains the additional, non-network related, information required for the installation of Triton; these values will be used during the installation process.
General environment questions
| Value | Description | Example |
|---|---|---|
| Company Name | The name of the company or division; this is used for identification purposes only. | MNX Solutions |
| Datacenter Region | The region or metro area this data center is located in; this is used to group multiple data centers within a region. This value needs to be in lowercase. All datacenters within a region should have low latency to each other. | us-central |
| Datacenter Name | The name of this data center; commonly is a derivative of the region, but doesn't need to be. This value needs to be in lowercase. | us-central-1, us-chi-1 |
| Datacenter City, State | The location of this data center; this is used for identification purposes only. | San Franscisco, CA |
| Root Password | The password used by the root account for the head node and compute nodes. This as long and complex as reasonably possible. Use of a random password generator is highly recommended. | DyLFoxpZAAh4InGhS8Dwum6z |
| Admin Password | The password used by the admin account in the Triton installation. This as long and complex as reasonably possible. Use of a random password generator is highly recommended. | 2cKswlyTrxcmkpdoUctA61Lo |
| Administrator Email | Address associated with the admin account. This should be an address where operators receive messages. | ops@example.com |
| Email from Address | The return email address used for alerts. Typically, an address where support staff receive messages. | support@example.com |
| Enable Telemetry | Enables Triton to periodically provide information back to Triton developers to assist with version management and vulnerability announcements. Customers with support contracts are required to enable this feature. | Y |
Environment notes
- The site operator will need to have physical access to the data center, or access to "remote hands", as there are certain tasks that require physical access to the hardware during the initial setup.
- Triton has several options to install the head node: USB drive, ISO, or iPXE. If installing via USB, during installation you can choose to boot from the zpool or the USB. Using USB boot, requires the USB for any subsequent reboots as well as for system management tasks that require updates to the key, such as addition of new platform images. For this reason, an internal USB slot is recommended for this purpose. If you initially choose USB booting, you can switch to booting from the zpool using the
piadmcommand. Using zpool boot, the installation media may be removed after install. If installing via ISO or iPXE, the system will be automatically configured to boot from the zpool. - Although Triton compute nodes can use onboard PXE to boot, it is highly recommended that USB keys be used in compute nodes in order to use the Triton modified iPXE software. These drives should be inserted into an internal USB port and should remain in the servers at all time. Compute nodes can also be converted to loading iPXE from the zpool post-setup using the
piadmcommand, but having a bootable USB provides a fallback mechanism in case of emergencies. - The site operator should coordinate with the networking team in order to make any network changes required; any pre-authorization for potential changes should be acquired if possible. A successful deployment of Triton is highly dependent on a properly configured network in infrastructure.
