NSP configuration file
nsp-config.yml file format
In order to deploy an NSP cluster, you must specify system parameters, installation options, and additional components in the following NSP configuration file on the NSP deployer host:
/opt/nsp/NSP-CN--DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml
The nsp-config.yml file has the following main sections:
-
platform—defines the following for the mandatory platform-baseServices installation option:
-
nsp—defines the NSP deployment; includes the following subsections:
A section begins with a header and section label, followed by descriptive text and one or more parameter lines. An example section layout is shown below.
################################################################
## platform - Platform specific configs ##
################################################################
platform:
## parameter_1 - This is the parameter 1 description.
## parameter_2 - This is the parameter 2 description.
## parameter_3 - This is the parameter 3 description.
# parameter_1=
# parameter_2=
parameter_3=true
To enable a parameter, delete the leading # symbol from the parameter line. In the example, only parameter_3 is enabled and configured.
Note: You must preserve the lead spacing of each line. Ensure that you delete only the # symbol, and no spaces, from a parameter line.
Note: In the event of a discrepancy between information in a configuration file and the NSP documentation, or if the documentation fails to adequately describe a specific configuration, the configuration file information is to be followed and considered correct. Also, the NSP Release Notice describes configuration updates and corrections that are not captured in the core documentation.
Enabling installation options
The installationOptions section lists all available installation options. You enable the deployment of an option by removing the leading # character from the name and id lines of the option.
Note: NSP Platform - Base Services, NSP Platform - Logging and Monitoring, and NSP Platform - Certificate Manager are mandatory and enabled by default.
In the example below, the following are enabled, and NSP Platform - Pluggable Network Adaptation is disabled:
installationOptions:
- name: "NSP Platform - Base Services"
id: platform-baseServices
- name: "NSP Platform - Certificate Manager"
id: platform-certificateManager
- name: "NSP Platform - Logging and Monitoring"
id: platform-loggingMonitoring
# - name: "NSP Platform - Pluggable Network Adaptation"
# id: platform-pluggableNetworkAdaptation
- name: "Network Infrastructure Management - Basic Management"
id: networkInfrastructureManagement-basicManagement
Configuring sizing for network automation
This section describes how to configure the following network automation functions:
The sizing for Workflows and Network Intents can be configured as typical or heavy.
-
Typical is the default size and applies to most deployments.
-
Heavy depends on deployment configuration and complexity.
The heavy setting applies only to medium, standard, and enhanced profiles. It is ignored for all other profiles.
Heavy may apply in deployments with high volumes of events, large services, customized configurations, or complex workflows.
If the sizing profiles do not apply to your deployment, contact Nokia technical support for assistance.
The modules section in nsp-config.yml lists the options for Workflows and Network Intents.
Note: In nsp-config.yml, Workflows settings are in the wfm subsection, and Network Intents settings are in the im subsection.
nsp:
modules:
wfm:
sizing:
type: typical
nsp:
modules:
im:
sizing:
type: typical