WIP: add NetworkManager TODO items

Signed-off-by: Tim Serong <[email protected]>

Author: tserong

docs/install/update-harvester-configuration.md

@@ -122,6 +122,21 @@ You can update the slave interfaces of Harvester's management bonding interface
 
 ### Runtime change
 
+:::info DOCS TODO
+
+Procedure is to add a new NM connection profile for the new interface, e.g.: `/etc/NetworkManager/system-connections`, with content:
+```
+[connection]
+id=bond-slave-eno50
+type=ethernet
+interface-name=eno50
+master=mgmt-bo
+slave-type=bond
+```
+...then `nmcli con reload` and probably `nmcli device reapply mgmt-bo`.
+
+:::
+
 1. Log in to a Harvester node and become root. See [how to log into a Harvester node](../troubleshooting/os.md#how-to-log-in-to-a-harvester-node) for more details.
 1. Identify the interface names with the following command:
 
@@ -151,6 +166,11 @@ You can update the slave interfaces of Harvester's management bonding interface
 
 ### Configuration persistence
 
+:::info DOCS TODO
+
+Files as in above TODO, and note `/oem/91_networkmanager.yaml` for pre v1.7.0 systems
+
+:::
 
 1. Backup the elemental cloud-init file `/oem/90_custom.yaml` as follows:
 

docs/logging/harvester-logging.md

@@ -47,6 +47,12 @@ In Harvester's practice, the `Logging`, `Audit` and `Event` shares one architect
 The Harvester logging infrastructure allows you to aggregate Harvester logs into an external service such as [Graylog](https://www.graylog.org), [Elasticsearch](https://www.elastic.co/elasticsearch/), [Splunk](https://www.splunk.com/), [Grafana Loki](https://grafana.com/oss/loki/) and others.
 
 ### Collected Logs
+:::info DOCS TODO
+
+Confirm this does NetworkManager logs and fix it if not.
+
+:::
+
 See below for a list logs that are collected:
  - Logs from all cluster `Pods`
  - Kernel logs from each `node`

docs/networking/clusternetwork.md

@@ -102,6 +102,15 @@ During installation of the first cluster node, you can configure the MTU value f
 
 ### Add Secondary VLAN Interfaces
 
+:::info DOCS TODO
+
+figure out how to do this. It probably means:
+- Add a new connection based on vlan-mgmt
+- Add the VLAN id to vlans in bridge-mgmt connection profile
+- Add the VLAN id to bridge-port in bond-mgmt connection profile
+
+:::
+
 Add the following commands to the `/oem/90_custom.yaml` file and reboot the node.
 
 - `/etc/wicked/scripts/setup_bond.sh` section
@@ -167,6 +176,12 @@ Exercise extreme caution when editing `/oem/90_custom.yaml`. Do not change other
 
 1. Change the MTU value in the `/oem/90_custom.yaml` file on each node.
 
+    :::info DOCS TODO
+
+    files are `/etc/NetworkManager/system-connections/{bond-mgmt,bridge-mgmt,vlan-mgmt}.nmconnection`, and you need to add the line `mtu=whatever` to the `[ethernet]` section if it's not already present (it won't be in the default case of 1500)
+
+    :::
+
     Locate the following paths, and then change the value in `MTU=1500`.
 
     - `path: /etc/sysconfig/network/ifcfg-mgmt-bo`

docs/upgrade/automatic.md

@@ -28,6 +28,16 @@ Harvester does not support downgrades. This restriction helps prevent unexpected
 
 :::
 
+:::info DOCS TODO
+
+Add information about NetworkManager migration when upgrading from v1.6.x to v1.7.0,
+notably that configuration will be generated based on `/oem/harvester.config` and will
+be saved in /oem/91_networkmanager.yaml. See https://github.com/harvester/harvester/pull/9039
+for more information.
+
+:::
+
+
 ## Upgrade paths
 
 The following table outlines the supported upgrade paths.