The NSP platform is composed of virtual components in a containerized environment:

• NSP deployer host: a small-profile VM which deploys the container runtime environment for the NSP cluster

  The NSP deployer host creates a Kubernetes cluster according to your NSP deployment specifications, and subsequently deploys the NSP software to the cluster.

• NSP cluster: one or more VMs which together host the NSP software and functions

  An NSP cluster may consist of one member, or three or more members that each host a portion of the installed NSP software.

  • NSP cluster member: a Kubernetes worker node VM in an NSP cluster. An NSP cluster member is also called a cluster node, depending on the context.

  • NSP cluster host: a specific NSP cluster member from which NSP deployment operations in the cluster are performed. Typically, node 1 of a cluster is chosen as the NSP cluster host and becomes a Kubernetes control node.

  • Pods: Kubernetes pods devoted to distinct NSP services are distributed among VMs in the cluster.

    The NSP software runs in pods on the NSP cluster nodes.

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

For information about NSP deployment and working with NSP deployers, see “NSP deployment terms and concepts” and “NSP deployment basics” in the NSP Installation and Upgrade Guide.

For information about how to manage NSP clusters and pods, see “NSP cluster administration” in the NSP System Administrator Guide.