github.com/anth0d/nomad@v0.0.0-20221214183521-ae3a0a2cad06/website/content/docs/enterprise/index.mdx (about)

     1  ---
     2  layout: docs
     3  page_title: Nomad Enterprise
     4  description: >-
     5    Nomad Enterprise adds operations, collaboration, and governance capabilities
     6    to Nomad.
     7  
     8    Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
     9  ---
    10  
    11  # Nomad Enterprise
    12  
    13  Nomad Enterprise adds collaboration, operational, and governance capabilities
    14  to Nomad. Nomad Enterprise is available as a base Platform package with an
    15  optional Governance & Policy add-on module.
    16  
    17  Please navigate the sub-sections for more information about each package and
    18  its features in detail.
    19  
    20  ~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
    21  source version of Nomad. Servers running the open source version of Nomad will
    22  panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
    23  for more details.
    24  
    25  ## Nomad Enterprise Platform
    26  
    27  Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
    28  enhances performance and availability through Advanced Autopilot features such
    29  as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
    30  
    31  ### Automated Upgrades
    32  
    33  Automated Upgrades allows operators to deploy a complete cluster of new
    34  servers and then simply wait for the upgrade to complete. As the new servers
    35  join the cluster, server logic checks the version of each Nomad server
    36  node. If the version is higher than the version on the current set of voters,
    37  it will avoid promoting the new servers to voters until the number of new
    38  servers matches the number of existing servers at the previous version. Once
    39  the numbers match, Nomad will begin to promote new servers and demote old
    40  ones.
    41  
    42  See the [Autopilot - Upgrade
    43  Migrations](https://learn.hashicorp.com/tutorials/nomad/autopilot#upgrade-migrations)
    44  documentation for a thorough overview.
    45  
    46  ### Automated Backups
    47  
    48  Automated Backups allows operators to run the snapshot agent as a long-running
    49  daemon process or in a one-shot mode from a batch job. The agent takes
    50  snapshots of the state of the Nomad servers and saves them locally, or pushes
    51  them to an optional remote storage service, such as Amazon S3.
    52  
    53  This capability provides an enterprise solution for backup and restoring the
    54  state of Nomad servers within an environment in an automated manner. These
    55  snapshots are atomic and point-in-time.
    56  
    57  See the [Operator Snapshot agent](/docs/commands/operator/snapshot/agent)
    58  documentation for a thorough overview.
    59  
    60  ### Enhanced Read Scalability
    61  
    62  This feature enables an operator to introduce non-voting server nodes to a
    63  Nomad cluster. Non-voting servers will receive the replication stream but will
    64  not take part in quorum (required by the leader before log entries can be
    65  committed). Adding explicit non-voters will scale reads and scheduling without
    66  impacting write latency.
    67  
    68  See the [Autopilot - Read
    69  Scalability](https://learn.hashicorp.com/tutorials/nomad/autopilot#server-read-and-scheduling-scaling)
    70  documentation for a thorough overview.
    71  
    72  ### Redundancy Zones
    73  
    74  Redundancy Zones enables an operator to deploy a non-voting server as a hot
    75  standby server on a per availability zone basis. For example, in an
    76  environment with three availability zones an operator can run one voter and
    77  one non-voter in each availability zone, for a total of six servers. If an
    78  availability zone is completely lost, only one voter will be lost, so the
    79  cluster remains available. If a voter is lost in an availability zone, Nomad
    80  will promote the non-voter to a voter automatically, putting the hot standby
    81  server into service quickly.
    82  
    83  See the [Autopilot - Redundancy
    84  Zones](https://learn.hashicorp.com/tutorials/nomad/autopilot#redundancy-zones)
    85  documentation for a thorough overview.
    86  
    87  ### Multiple Vault Namespaces
    88  
    89  Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
    90  to support multiple Vault Namespaces for topology simplicity and fleet
    91  consolidation when running Nomad and Vault together. Nomad will automatically
    92  retrieve a Vault token based on a job's defined Vault Namespace and make it
    93  available for the specified Nomad task at hand.
    94  
    95  See the [Vault Integration documentation](/docs/integrations/vault-integration#enterprise-configuration) for more information.
    96  
    97  ## Governance & Policy
    98  
    99  Governance & Policy features are part of an add-on module that enables an
   100  organization to securely operate Nomad at scale across multiple teams through
   101  features such as Audit Logging, Resource Quotas, and Sentinel Policies.
   102  
   103  ### Audit Logging
   104  
   105  Secure clusters with enhanced risk management and operational traceability to
   106  fulfill compliance requirements. This Enterprise feature provides
   107  administrators with a complete set of records for all user-issued actions in
   108  Nomad.
   109  
   110  With Audit Logging, enterprises can now proactively identify access anomalies,
   111  ensure enforcement of their security policies, and diagnose cluster behavior
   112  by viewing preceding user operations. Designed as an HTTP API based audit
   113  logging system, each audit event is captured with relevant request and
   114  response information in a JSON format that is easily digestible and familiar
   115  to operators.
   116  
   117  See the [Audit Logging Documentation](/docs/configuration/audit) for a
   118  thorough overview.
   119  
   120  ### Resource Quotas
   121  
   122  Resource Quotas enable an operator to limit resource consumption across teams
   123  or projects to reduce waste and align budgets. In Nomad Enterprise, operators
   124  can define quota specifications and apply them to namespaces. When a quota is
   125  attached to a namespace, the jobs within the namespace may not consume more
   126  resources than the quota specification allows.
   127  
   128  This allows operators to partition a shared cluster and ensure that no single
   129  actor can consume the whole resources of the cluster.
   130  
   131  See the [Resource Quotas
   132  Guide](https://learn.hashicorp.com/tutorials/nomad/quotas) for a thorough
   133  overview.
   134  
   135  ### Sentinel Policies
   136  
   137  In Nomad Enterprise, operators can create Sentinel policies for fine-grained
   138  policy enforcement. Sentinel policies build on top of the ACL system and allow
   139  operators to define policies such as disallowing jobs to be submitted to
   140  production on Fridays or only allowing users to run jobs that use
   141  pre-authorized Docker images. Sentinel policies are defined as code, giving
   142  operators considerable flexibility to meet compliance requirements.
   143  
   144  See the [Sentinel Policies
   145  Guide](https://learn.hashicorp.com/tutorials/nomad/sentinel) for a thorough
   146  overview.
   147  
   148  ## Multi-Cluster & Efficiency
   149  
   150  Multi-Cluster & Efficiency features are part of an add-on module that enables
   151  an organization to operate Nomad at scale across multiple clusters through
   152  features such as Multiregion Deployments.
   153  
   154  ### Multiregion Deployments
   155  
   156  [Multiregion Deployments] enable an operator to deploy a single job to multiple
   157  federated regions. This includes the ability to control the order of rollouts
   158  and how each region will behave in the event of a deployment failure.
   159  
   160  ### Dynamic Application Sizing
   161  
   162  Dynamic Application Sizing enables organizations to optimize the resource
   163  consumption of applications using sizing recommendations from Nomad. This
   164  feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
   165  routine of manually setting resource requirements. DAS comprises support for
   166  vertical [scaling policies], a new API and UI for reviewing recommended job
   167  changes, and a collection of Nomad Autoscaler plugins informed by best-practice
   168  statistical measures.
   169  
   170  ## Try Nomad Enterprise
   171  
   172  Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
   173  request a trial of Nomad Enterprise.
   174  
   175  [multiregion deployments]: /docs/job-specification/multiregion
   176  [autoscaling capabilities]: /tools/autoscaling
   177  [scaling policies]: /tools/autoscaling/policy
   178  [gh-9958]: https://github.com/hashicorp/nomad/issues/9958