The following table describes the NSP deployment types available in the nsp-config.yml file. See your NSP Platform Sizing Response for information about the correct deployment type for your requirements. See “NSP cluster requirements” in the NSP Planning Guide for platform requirements.

NSP provides redundancy options through disaster recovery (DR) and high availability (HA). All deployments have the option of DR, where NSP is deployed in identical redundant clusters in geographically separate data centers. See Chapter 8, System redundancy and fault tolerance for more details about redundancy.

Deployment type	Description	Redundancy options
Customer-lab	Lab deployment	Option for DR
Small	Production deployment for small enterprise networks, single node cluster
Medium	Production deployment for medium sized networks
Basic	Production deployment with a single node cluster
Standard	Production deployment
Enhanced	Production deployment always deployed in multi-node cluster for HA	HA and option for DR Enhanced is the only deployment type that includes HA.
Special deployments	Deployments that only include the NRC-P Simulation tool or Centralized License Manager are standalone only	None

Node labels file

Based on your deployment type and redundancy requirements, the response to your Nokia Platform Sizing Request will specify a node labels file for your needs. The node labels file name is entered during the installation of the NSP; see the NSP Installation and Upgrade Guide.

The node labels file determines which Kubernetes pods run on which NSP cluster nodes.

As required to accommodate system or network growth, you can later add instances of functions such as MDM to an NSP cluster that has sufficient resources. See the NSP Installation and Upgrade Guide for information.