Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: multiregion deployment feature #8185

Merged
merged 5 commits into from
Jun 18, 2020
Merged

docs: multiregion deployment feature #8185

merged 5 commits into from
Jun 18, 2020

Conversation

tgross
Copy link
Member

@tgross tgross commented Jun 17, 2020

To go with #8184

@tgross tgross marked this pull request as ready for review June 17, 2020 15:55
@angrycub
Copy link
Contributor

saw an &emdash; leaking out to the output. Not sure how to fix yet or would have made a suggestion. Just wanted to let you know I was looking.

@tgross
Copy link
Member Author

tgross commented Jun 17, 2020

Fixed the emdash in 89eca7f

@tgross
Copy link
Member Author

tgross commented Jun 17, 2020

@yishan-lin @changli0617 it'd probably be worth getting some of your input here with respect to the nomenclature gap between "Multi-Cluster Deployment" and "multiregion deployment" as it's been crafted in the implementation. The operator-facing concept in Nomad is the region (see also region and the Multi-Region Federation Guide), which is why we used the configuration value multiregion.

It's probably fine that we have the "marketing name" in the enterprise section of the docs here so long as it points to the operator-facing name, but I wanted to bring it to your attention.

Copy link
Member

@schmichael schmichael left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! re Multi-cluster vs Multiregion:

We'll have to live with some ambiguity unfortunately, but I think it's for good reason:

  1. "Multi-cluster" will be used in marketing material where the audience may not be familiar with Nomad's notion of "regions"
  2. "Multiregion" will be used in reference material as it uses Nomad-specific terminology

Since Nomad "clusters" and "regions" are synonymous, hopefully using both terms isn't too jarring. If so we may make changes to marketing material over time, but the technical implementation (and therefore reference docs too) would continue to use the Nomad-specific terminology.

website/pages/docs/enterprise/index.mdx Outdated Show resolved Hide resolved
@tgross tgross merged commit 6fd4f3e into master Jun 18, 2020
@tgross tgross deleted the multiregion_docs branch June 18, 2020 12:41
@github-actions
Copy link

github-actions bot commented Jan 3, 2023

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants