NSP deployment terms and concepts

Introduction

The NSP deployment and administration guides use specific terms to describe some basic elements of an NSP system. The following topics define commonly used terms used in the NSP system documentation that may be unfamiliar to the reader.

Note: Although the usage of each term is typically as described, a specific context may include a variant of the term.

Station

A station is a physical processing entity that has one native OS instance, or hosts OS instances in multiple VMs. The term station is typically used only for low-level configuration operations to distinguish the VM from the entity on which the VM is deployed.

The term “host station” is sometimes used to clearly indicate the physical station that hosts a specific function.

NSP deployer host

The NSP deployer host is a VM from which you deploy the container environment for an NSP cluster.

NSP cluster

An NSP cluster is a group of one or more VMs in a Kubernetes container environment that host NSP software and functions. An NSP system deployment includes at least one NSP cluster.

NSP cluster member

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

NSP cluster host

The NSP cluster host is 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.

Independent and shared-mode deployments

A shared-mode deployment is an NSP deployment in which the WS-NOC or NFM-P components share a central set of NSP platform resources in the NSP cluster, instead of using the nspOS embedded in the NFM component. If you add an independently deployed system to an NSP deployment, the independent system stops using the embedded local nspOS, and instead uses the shared nspOS hosted by the NSP.

The following graphic depicts the two types of deployments currently supported: