Prerequisites and personnel
This page summarizes the deployment prerequisites and teams needed to implement the Nomad Enterprise Installation Guide.
Supported platforms and versions
As of HVD Document Version 1.0, the Installation Guide supports deploying Nomad Enterprise on the following compute platforms:
- Bare-metal or VM-based servers in a private datacenter
- AWS on EC2 instances
This guide applies to Nomad Enterprise versions nomad_1.9.3+ent and later, and can be downloaded from HashiCorp Releases(opens in new tab) or the HashiCorp Developer page(opens in new tab).
While Nomad Enterprise is officially supported for a number of different operating systems and processor architectures, this guide primarily uses linux/amd64 within its examples, unless otherwise specified.
Required teams
Most tasks within this guide will be owned by a single team, who is responsible for deploying shared infrastructure services. This is sometimes referred to as a platform team. However, a successful deployment of Nomad Enterprise requires collaboration across various functions within the organization. The platform team may interface with various other teams, such as networking, information security, or identity teams, to perform tasks such as allocating IP space, managing certificates, defining identity roles and permissions, or overseeing DNS hosted zones and records. In cases where the infrastructure resides on a public cloud, these functions might converge under a unified cloud team.
The primary platform team should thoroughly review the Installation Guide in order to identify any teams they may be dependent on or may require approval from for the tasks required as part of the deployment. The platform team should appoint a project lead to oversee the deployment process and ensure effective communication with dependent teams and functions.