website: update docs for command renames

This commit is contained in:
Ryan Uber
2015-09-22 11:08:36 -07:00
parent 120974820f
commit e028331065
3 changed files with 23 additions and 23 deletions

View File

@@ -1,14 +1,14 @@
---
layout: "docs"
page_title: "Commands: agent-force-leave"
sidebar_current: "docs-commands-agent-force-leave"
page_title: "Commands: server-force-leave"
sidebar_current: "docs-commands-server-force-leave"
description: >
Force a node into the "left" state.
Force a server into the "left" state.
---
# Command: agent-force-leave
# Command: server-force-leave
The `agent-force-leave` command forces a server to enter the "left" state.
The `server-force-leave` command forces a server to enter the "left" state.
This can be used to eject server nodes which have failed and will not rejoin
the cluster. Note that if the server is actually still alive, it will
eventually rejoin the cluster again.
@@ -16,7 +16,7 @@ eventually rejoin the cluster again.
## Usage
```
nomad agent-force-leave [options] <node>
nomad server-force-leave [options] <node>
```
This command expects only one argument - the node which should be forced
@@ -28,8 +28,8 @@ to enter the "left" state.
## Examples
Force-leave the node "node1":
Force-leave the server "node1":
```
$ nomad agent-force-leave node1
$ nomad server-force-leave node1
```

View File

@@ -1,14 +1,14 @@
---
layout: "docs"
page_title: "Commands: agent-join"
sidebar_current: "docs-commands-agent-join"
page_title: "Commands: server-join"
sidebar_current: "docs-commands-server-join"
description: >
Joins the local server to one or more Nomad servers.
---
# Command: agent-join
# Command: server-join
The `agent-join` command joins the local server to one or more Nomad servers.
The `server-join` command joins the local server to one or more Nomad servers.
Joining is only required for server nodes, and only needs to succeed against
one or more of the provided addresses. Once joined, the gossip layer will
handle discovery of the other server nodes in the cluster.
@@ -16,7 +16,7 @@ handle discovery of the other server nodes in the cluster.
## Usage
```
nomad agent-join [options] <addr> [<addr>...]
nomad server-join [options] <addr> [<addr>...]
```
One or more server addresses are required. If multiple server addresses are
@@ -33,6 +33,6 @@ be 1.
Join the local server to a remote server:
```
$ nomad agent-join 10.0.0.8:4648
Joined 1 nodes successfully
$ nomad server-join 10.0.0.8:4648
Joined 1 servers successfully
```

View File

@@ -1,21 +1,21 @@
---
layout: "docs"
page_title: "Commands: agent-members"
sidebar_current: "docs-commands-agent-members"
page_title: "Commands: server-members"
sidebar_current: "docs-commands-server-members"
description: >
Display a list of the known cluster members and their status.
Display a list of the known server members and their status.
---
# Command: agent-members
# Command: server-members
The `agent-members` command displays a list of the known servers in the cluster
The `server-members` command displays a list of the known servers in the cluster
and their current status. Member information is provided by the gossip protocol,
which is only run on server nodes.
## Usage
```
nomad agent-members [options]
nomad server-members [options]
```
## General Options
@@ -33,7 +33,7 @@ nomad agent-members [options]
Default view:
```
$ nomad agent-members
$ nomad server-members
Name Addr Port Status Proto Build DC Region
node1.global 10.0.0.8 4648 alive 2 0.1.0dev dc1 global
node2.global 10.0.0.9 4648 alive 2 0.1.0dev dc1 global
@@ -42,7 +42,7 @@ node2.global 10.0.0.9 4648 alive 2 0.1.0dev dc1 global
Detailed view:
```
$ nomad agent-members -detailed
$ nomad server-members -detailed
Name Addr Port Tags
node1 10.0.0.8 4648 bootstrap=1,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
node2 10.0.0.9 4648 bootstrap=0,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1