luxolus/open-nomad
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity

final deps update, fix some anchor link aliases

Browse source
This commit is contained in:
Jeff Escalante 2020-05-14 14:09:12 -04:00
parent cd81911e17
commit e9076f6fcd
3 changed files with 165 additions and 1784 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1939
website/package-lock.json generated
View file

File diff suppressed because it is too large Load diff

2
website/package.json
View file

@ -4,7 +4,7 @@
"version": "0.0.1",
"author": "HashiCorp",
"dependencies": {
"@hashicorp/nextjs-scripts": "^7.0.0",
"@hashicorp/nextjs-scripts": "^7.1.2",
"@hashicorp/react-alert-banner": "^3.1.0",
"@hashicorp/react-button": "^2.2.0",
"@hashicorp/react-call-to-action": "^0.2.0",

8
website/pages/docs/install/production/reference-architecture.mdx
View file

@ -38,7 +38,7 @@ The design shared in this document is the recommended architecture for productio
Nomad to Consul connectivity is over HTTP and should be secured with TLS as well as a Consul token to provide encryption of all traffic. This is done using Nomad's [Automatic Clustering with Consul](https://learn.hashicorp.com/nomad/operating-nomad/clustering).
### <a name="one-region"></a>Deployment Topology within a Single Region
### Deployment Topology within a Single Region ((#one-region))
A single Nomad cluster is recommended for applications deployed in the same region.
@ -50,7 +50,7 @@ The time taken by a new server to join an existing large cluster may increase as
![Reference diagram](/img/nomad_reference_diagram.png)
### <a name="multi-region"></a>Deployment Topology across Multiple Regions
### Deployment Topology across Multiple Regions ((#multi-region))
By deploying Nomad server clusters in multiple regions, the user is able to interact with the Nomad servers by targeting any region from any Nomad server even if that server resides in a separate region. However, most data is not replicated between regions as they are fully independent clusters. The exceptions are [ACL tokens and policies][acl], as well as [Sentinel policies in Nomad Enterprise][sentinel], which _are_ replicated between regions.
@ -58,7 +58,7 @@ Nomad server clusters in different datacenters can be federated using WAN links.
Additional documentation is available to learn more about [Nomad server federation](https://learn.hashicorp.com/nomad/operating-nomad/federation).
## <a name="net"></a>Network Connectivity Details
## Network Connectivity Details ((#net))
![Nomad network diagram](/img/nomad_network_arch.png)
@ -68,7 +68,7 @@ Nomad client clusters require the ability to receive traffic as noted above in t
Additional documentation is available to learn more about [Nomad networking](/docs/install/production/requirements#network-topology).
## <a name="system-reqs"></a>Deployment System Requirements
## Deployment System Requirements ((#system-reqs))
Nomad server agents are responsible for maintaining the cluster state, responding to RPC queries (read operations), and for processing all write operations. Given that Nomad server agents do most of the heavy lifting, server sizing is critical for the overall performance efficiency and health of the Nomad cluster.