Skip to content

Commit abc7e27

Browse files
joel-hamilljoel-hamill
committed
1.10 doc branch development
1 parent 14bfdb3 commit abc7e27

File tree

481 files changed

+32340
-10
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

481 files changed

+32340
-10
lines changed

‎1.10/administering-clusters/add-a-node.md

+75
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
post_title: Adding Agent Nodes
3+
nav_title: Adding Node
4+
menu_order: 800
5+
---
6+
7+
You can add agent nodes to an existing DC/OS cluster.
8+
9+
Agent nodes are designated as [public](/docs/1.10/overview/concepts/#public-agent-node) or [private](/docs/1.10/overview/concepts/#private) during installation. By default, they are designated as private during [GUI][1] or [CLI][2] installation.
10+
11+
### Prerequisites:
12+
13+
* DC/OS is installed using the [custom](/docs/1.10/installing/custom/) installation method.
14+
* The archived DC/OS installer file (`dcos-install.tar`) from your [installation](/docs/1.10/installing/custom/gui/#backup).
15+
* Available agent nodes that satisfy the [system requirements](/docs/1.10/installing/custom/system-requirements/).
16+
* The CLI JSON processor [jq](https://github.com/stedolan/jq/wiki/Installation).
17+
* SSH installed and configured. This is required for accessing nodes in the DC/OS cluster.
18+
19+
### Install DC/OS agent nodes
20+
Copy the archived DC/OS installer file (`dcos-install.tar`) to the agent node. This archive is created during the GUI or CLI [installation](/docs/1.10/installing/custom/gui/#backup) method.
21+
22+
1. Copy the files to your agent node. For example, you can use Secure Copy (scp) to copy `dcos-install.tar` to your home directory:
23+
24+
```bash
25+
scp ~/dcos-install.tar $username@$node-ip:~/dcos-install.tar
26+
```
27+
28+
2. SSH to the machine:
29+
30+
```bash
31+
ssh $USER@$AGENT
32+
```
33+
34+
1. Create a directory for the installer files:
35+
36+
```bash
37+
sudo mkdir -p /opt/dcos_install_tmp
38+
```
39+
40+
1. Unpackage the `dcos-install.tar` file:
41+
42+
```bash
43+
sudo tar xf dcos-install.tar -C /opt/dcos_install_tmp
44+
```
45+
46+
1. Run this command to install DC/OS on your agent nodes. You must designate your agent nodes as public or private.
47+
48+
Private agent nodes:
49+
50+
```bash
51+
sudo bash /opt/dcos_install_tmp/dcos_install.sh slave
52+
```
53+
54+
Public agent nodes:
55+
56+
```bash
57+
sudo bash /opt/dcos_install_tmp/dcos_install.sh slave_public
58+
```
59+
60+
**Tip:** You can verify the node type by running this command from the DC/OS CLI.
61+
62+
- Run this command to count the private agents.
63+
64+
```bash
65+
dcos node --json | jq --raw-output '.[] | select(.reserved_resources.slave_public == null) | .id' | wc -l
66+
```
67+
68+
- Run this command to count the public agents.
69+
70+
```bash
71+
dcos node --json | jq --raw-output '.[] | select(.reserved_resources.slave_public != null) | .id' | wc -l
72+
```
73+
74+
[1]: /docs/1.10/installing/custom/gui/
75+
[2]: /docs/1.10/installing/custom/cli/

‎1.10/administering-clusters/component-management.md

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
post_title: Component Management
3+
menu_order: 5.5
4+
---
5+
6+
The component management API controls installation and management of DC/OS component services. It is used by the DC/OS installer during install, upgrade, and uninstall. It is not designed for interaction by DC/OS users.
7+
8+
## Component Package Manager
9+
10+
The DC/OS Component Package Manager (Pkgpanda) implements the component management API and runs on all DC/OS nodes.
11+
12+
[Pkgpanda](https://github.com/dcos/dcos/tree/master/pkgpanda) consists of two parts: a package builder and a package manager.
13+
14+
- The **package builder** builds and bundles component packages from source code and pre-compiled artifacts as part of the DC/OS release building process.
15+
- The **package manager** is included as part of DC/OS an runs on each node, managing the installed and activated component packages on that node.
16+
17+
Component packages built by the package builder are distributed as part of the DC/OS installer for each release. The installer ships the component packages to each node and orchestrates the component management API to install them. The component packages contain one or more systemd service definitions, binaries, and configuration files.
18+
19+
20+
## Component health
21+
22+
Component health is monitored by the DC/OS Diagnostics (3DT) component. For more information about component monitoring, see [Monitoring](/docs/1.10/monitoring/).
23+
24+
25+
## Component logs
26+
27+
Component logs are sent to journald and exposed by the DC/OS Log component. For more infromation about component logs, see [Logging](/docs/1.10/monitoring/logging/).
28+
29+
30+
## Routes
31+
32+
The component management API is exposed through Admin Router and Admin Router Agent under the `/pkgpanda/` path on all nodes.
33+
34+
35+
## Resources
36+
37+
<div class="swagger-section">
38+
<div id="message-bar" class="swagger-ui-wrap message-success" data-sw-translate=""></div>
39+
<div id="swagger-ui-container" class="swagger-ui-wrap" data-api="/docs/1.10/api/pkgpanda.yaml">
40+
41+
<div class="info" id="api_info">
42+
<div class="info_title">Loading docs...</div>
43+
<div class="info_description markdown"></div>
44+
</div>

‎1.10/administering-clusters/convert-agent-type.md

+98
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
---
2+
post_title: Converting Agent Node Types
3+
nav_title: Convert Node Type
4+
menu_order: 700
5+
---
6+
7+
You can convert agent nodes to public or private for an existing DC/OS cluster.
8+
9+
Agent nodes are designated as [public](/docs/1.10/overview/concepts/#public-agent-node) or [private](/docs/1.10/overview/concepts/#private) during installation. By default, they are designated as private during [GUI][1] or [CLI][2] installation.
10+
11+
### Prerequisites:
12+
These steps must be performed on a machine that is configured as a DC/OS node. Any tasks that are running on the node will be terminated during this conversion process.
13+
14+
* DC/OS is installed using the [custom](/docs/1.10/installing/custom/) installation method and you have deployed at least one [master](/docs/1.10/overview/concepts/#master) and one [private](/docs/1.10/overview/concepts/#private) agent node.
15+
* The archived DC/OS installer file (`dcos-install.tar`) from your [installation](/docs/1.10/installing/custom/gui/#backup).
16+
* The CLI JSON processor [jq](https://github.com/stedolan/jq/wiki/Installation).
17+
* SSH installed and configured. This is required for accessing nodes in the DC/OS cluster.
18+
19+
### Determine the node type
20+
You can determine the node type by running this command from the DC/OS CLI.
21+
22+
- Run this command to determine how many private agents are there in the cluster. A result of `0` indicates that there are no private agents.
23+
24+
```bash
25+
dcos node --json | jq --raw-output '.[] | select(.reserved_resources.slave_public == null) | .id' | wc -l
26+
```
27+
28+
- Run this command to determine how many public agents are there in the cluster. A result of `0` indicates that there are no public agents.
29+
30+
```bash
31+
dcos node --json | jq --raw-output '.[] | select(.reserved_resources.slave_public != null) | .id' | wc -l
32+
```
33+
34+
### Uninstall the DC/OS private agent software
35+
36+
1. Uninstall DC/OS on the agent node.
37+
38+
```bash
39+
sudo -i /opt/mesosphere/bin/pkgpanda uninstall
40+
sudo systemctl stop dcos-mesos-slave
41+
sudo systemctl disable dcos-mesos-slave
42+
```
43+
44+
2. Remove the old directory structures on the agent node.
45+
46+
```bash
47+
sudo rm -rf /etc/mesosphere /opt/mesosphere /var/lib/mesos /var/lib/dcos
48+
```
49+
50+
3. Restart the machine.
51+
52+
```bash
53+
sudo reboot
54+
```
55+
56+
### Install DC/OS and convert agent node
57+
Copy the archived DC/OS installer file (`dcos-install.tar`) to the node that that is being converted. This archive is created during the GUI or CLI [installation](/docs/1.10/installing/custom/gui/#backup) method.
58+
59+
1. Copy the files to your agent node. For example, you can use Secure Copy (scp) to copy `dcos-install.tar` to your home directory:
60+
61+
```bash
62+
scp ~/dcos-install.tar $username@$node-ip:~/dcos-install.tar
63+
```
64+
65+
2. SSH to the machine:
66+
67+
```bash
68+
ssh $USER@$AGENT
69+
```
70+
71+
1. Create a directory for the installer files:
72+
73+
```bash
74+
sudo mkdir -p /opt/dcos_install_tmp
75+
```
76+
77+
1. Unpackage the `dcos-install.tar` file:
78+
79+
```bash
80+
sudo tar xf dcos-install.tar -C /opt/dcos_install_tmp
81+
```
82+
83+
1. Run this command to install DC/OS on your agent nodes. You must designate your agent nodes as public or private.
84+
85+
Private agent nodes:
86+
87+
```bash
88+
sudo bash /opt/dcos_install_tmp/dcos_install.sh slave
89+
```
90+
91+
Public agent nodes:
92+
93+
```bash
94+
sudo bash /opt/dcos_install_tmp/dcos_install.sh slave_public
95+
```
96+
97+
[1]: /docs/1.10/installing/custom/gui/
98+
[2]: /docs/1.10/installing/custom/cli/

0 commit comments

Comments
 (0)