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

Added docs around bootstrapping a Nomad cluster #1361

Merged
merged 3 commits into from
Jun 28, 2016
Merged

Conversation

diptanu
Copy link
Contributor

@diptanu diptanu commented Jun 27, 2016

This is the first cut of the documentation for bootstrapping a Nomad cluster. Need to add more links, this is for the team to comment on the structure of the docs.

@@ -0,0 +1,132 @@
---
layout: "docs"
page_title: "Creating a cluster"
Copy link
Contributor

Choose a reason for hiding this comment

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

Creating a Nomad Cluster

@diptanu diptanu merged commit 5e406f3 into master Jun 28, 2016
@diptanu diptanu deleted the cluster-docs branch June 28, 2016 18:00
register the server and the client agents with Consul and try to auto-discover
the servers if it can talk to a local Consul agent on the same server.

Please refer to the (documentation)[/jobspec/servicediscovery.html] for the
Copy link
Contributor

Choose a reason for hiding this comment

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

This is the wrong link. It should be /docs/agent/config.html.md#consul_options

connected users can target the Nomad Servers in various regions from any other
region while submitting a job or querying any Nomad API.

Fedarating multiple Nomad clusters is as simple as joining a server to any other
Copy link
Contributor

Choose a reason for hiding this comment

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

Federating multiple Nomad clusters is as simple as going servers. From a server in one region simply issue a join command to the remote region as follows:

@github-actions
Copy link

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 Apr 22, 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.

3 participants