Workflow for NSP system conversion to multi-interface
Description
The following workflow describes the sequence of high-level actions that are required to convert a single-interface NSP system to a system that uses multiple network interfaces.
An NSP system can use one network for all client, internal, and mediation communication, or the system can segregate different traffic types using separate networks and network interfaces.
See Multi-interface configuration for information about multi-interface support.
Stages
1 |
Back up the current NSP databases; perform “How do I back up the NSP cluster databases?” in the NSP System Administrator Guide. |
2 |
Back up any customized system files that you need to preserve, for example, TLS certificate files and any custom data files. |
3 |
Back up all files in the following directory to a secure location that is unaffected by the conversion activity: /opt/nsp/nsp-configurator/generated/ |
4 |
Perform To uninstall the NSP software from an NSP cluster. |
5 |
Perform To uninstall the NSP Kubernetes registry. |
6 |
Perform To provision the network bridge for NSP VMs on each physical host to reconfigure the network bridge for KVM access to the guest VMs. |
7 |
Install the NSP, as described in To install the NSP, with the exclusion of Step 27, which describes creating the NSP cluster VMs. You must specify the IP addresses of the required client, internal, and network interfaces during the installation. Note: Using the internal NSP network requires that you update the configuration of each other component to use the NSP internal address; the WS-NOC is an exception, and must use the NSP client interface address. |
8 |
Test the converted system to verify the system operation and data integrity, as required. |