44Cluster management
55==================
66
7- A NethServer 8 cluster _ is composed of one **leader ** node and multiple
8- **worker ** nodes.
9-
10- .. _cluster : https://en.wikipedia.org/wiki/Computer_cluster
7+ A NethServer 8 cluster [#clu ]_ is composed of one **leader ** node and
8+ multiple **worker ** nodes.
119
1210All nodes are managed through the Web user interface, which operates on
1311the leader node.
@@ -27,8 +25,62 @@ by the VPN network size. However, it is advisable to add nodes gradually
2725to avoid degrading the leader's performance due to increasing workload.
2826
2927
28+ .. _node-views :
29+
30+ Node overview and details
31+ =========================
32+
33+ The ``Nodes `` page displays an overview of the configured cluster nodes.
34+ Each card shows basic node attributes, the node alert counter, and node
35+ actions, which are explained in detail in the following sections.
36+
37+ - Cluster nodes are uniquely identified by an increasing number. They are
38+ named ``Node 1 ``, ``Node 2 `` and so on. Use the ``Edit label `` action
39+ from the three-dots menu to assign a custom name to the node. Note that
40+ this label is only for UI visualization; see :ref: `set-fqdn ` to change
41+ the host name.
42+
43+ - ``FQDN `` is the fully qualified host name (including the DNS domain
44+ suffix) assigned to the node's operating system. It must meet the node
45+ :ref: `DNS requirements <dns-reqs >`.
46+
47+ - ``IP address `` is the main system address. It is the source address of
48+ the default IP route, selected among the available system IP addresses.
49+ To change basic network configuration refer to
50+ :ref: `os-network-section `.
51+
52+ - ``Applications `` is the number of applications installed on the node. It
53+ is a link to the :ref: `Applications page <applications-section >`,
54+ already filtered for the selected node.
55+
56+ If there is an ongoing NethServer 7 migration procedure, a special node
57+ representing the NethServer 7 system is shown. All actions related to this
58+ node must be executed from the NethServer 7 migration tool available on
59+ that system. During migration, some cluster and application actions are
60+ inhibited. Refer to :ref: `migration-section ` for more information.
61+
62+ The :guilabel: `See details ` button opens a detailed view of the selected
63+ node.
64+
65+ - ``Applications `` and ``Network interfaces `` link to pages that provide
66+ further details about the applications running on the node and the full
67+ list of IP addresses.
68+
69+ - ``VPN `` shows a summary of the node’s internal WireGuard network
70+ parameters. The ``Endpoint `` value is important in case of :ref: `new
71+ leader promotion <node-promotion-section>`. To change the WireGuard
72+ listening port number, refer to :ref: `vpn-custom-section `.
73+
74+ - The ``Alerts `` panel lists active node alerts, collected every minute.
75+ See how to configure email notifications in :ref: `alerts-section `.
76+
77+ - The following sections summarize CPU, load, memory, and disk usage.
78+ Metrics are collected every minute, and averages are calculated over a
79+ two-minute interval. For a detailed view of collected system metrics,
80+ refer to :ref: `grafana_access-section `.
81+
3082Add a node
31- ==========
83+ ----------
3284
3385You can add (join) a worker node to an existing cluster.
3486The process consists of the following steps:
@@ -57,7 +109,7 @@ clicking the join button.
57109When the node registration is complete, you can return to the leader user interface and install applications running on the new worker node.
58110
59111Remove a node
60- =============
112+ -------------
61113
62114Worker nodes can be removed from the cluster. Before removing a given
63115worker node, ensure no account provider replica is running on it. In the
@@ -87,7 +139,7 @@ off the node to finalize the node removal.
87139.. _set-fqdn :
88140
89141Change FQDN
90- ===========
142+ -----------
91143
92144A node's FQDN is typically set during the post-installation steps. If it
93145becomes necessary to change the FQDN later, follow these steps:
@@ -109,7 +161,7 @@ DNS as outlined in :ref:`dns-reqs`.
109161.. _node-promotion-section :
110162
111163Promote a node to leader
112- ========================
164+ ------------------------
113165
114166Adding and removing nodes may necessitate changing the cluster **leader
115167node **.
@@ -141,7 +193,7 @@ node promotion.
141193
142194
143195Reachable leader node
144- ---------------------
196+ ^^^^^^^^^^^^^^^^^^^^^
145197
146198If the current leader node is functioning properly, follow these steps:
147199
@@ -161,7 +213,7 @@ promote the node` button becomes active, allowing you to complete the
161213node promotion.
162214
163215Unreachable leader node
164- -----------------------
216+ ^^^^^^^^^^^^^^^^^^^^^^^
165217
166218If the current leader node is not reachable, run a command on any other
167219worker node. Be prepared for this situation by enabling SSH, console, or
@@ -229,15 +281,22 @@ Available for both Android and iOS:
229281Reset the cluster administrator password
230282----------------------------------------
231283
232- If you are locked out of the web user interface and you can still access a
233- system command-line shell as ``root `` (e.g. by the system recovery console
234- or SSH), run the following command to disable 2FA and reset the password:
284+ If you are locked out of the web user interface but can still access a
285+ system command-line shell as ``root `` (e.g. through the system recovery
286+ console or SSH), run the following command **on the leader node ** to
287+ disable 2FA and reset the password:
235288
236289::
237290
238291 api-cli run alter-user --data '{"user":"admin","set":{"password":"Nethesis,1234","2fa":false}}'
239292
240- Replace the ``admin `` and ``Nethesis,1234 `` default credentials as needed.
293+ Replace the ``admin `` username and ``Nethesis,1234 `` password with the
294+ desired credentials.
295+
296+ .. note ::
297+
298+ The above command fails with ``AuthenticationError `` if executed on a
299+ **worker node **. Run it only on the leader node.
241300
242301
243302.. _audit-trail-section :
@@ -259,3 +318,7 @@ Audit trail events can be filtered by user, date, action type, and custom text m
259318 Audit trail information is stored in the leader node disk. In case of
260319 :ref: `new leader promotion <node-promotion-section >` the audit trail
261320 information in the old leader is no longer accessible.
321+
322+ .. rubric :: Footnotes
323+
324+ .. [#clu ] https://en.wikipedia.org/wiki/Computer_cluster
0 commit comments