NSP deployment environment

Containerization

A small-profile VM called an NSP deployer host holds and controls a Kubernetes container runtime environment. The NSP deployer host creates a Kubernetes cluster according to your NSP deployment specifications, and subsequently deploys the NSP software to the cluster.

The NSP container environment uses only the storage local to each NSP cluster member; no cluster-wide network storage is required. The NSP core service pods are deployed only to specific cluster members to ensure that each service has access to fixed portions of the local storage.

NSP deployment supports various forms and levels of system redundancy; see Chapter 8, System redundancy and fault tolerance, the NSP Planning Guide, and the NSP Installation and Upgrade Guide for information.

NSP cluster

The NSP software runs in pods on the NSP cluster nodes, which are also called the NSP cluster members. An NSP cluster may consist of one member, or three or more members that each host a portion of the installed NSP software. Each cluster member is a designated Kubernetes worker node on which NSP services run; at least one member is also a Kubernetes control node.

Deployment profiles

Based on the deployment scope and required level of fault tolerance, you specify one of the following NSP cluster deployment profiles, based on the response to your Nokia Platform Sizing Request:

• node-labels-basic-1node.yml—single-VM deployment

• node-labels-standard-3nodes.yml—standard deployment of three VMs

• node-labels-standard-4nodes.yml—standard deployment of four VMs

• node-labels-enhanced-6nodes.yml—enhanced deployment for HA

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.