Home > Workload Solutions > Container Platforms > Red Hat OpenShift Container Platform > Archive > Design Guide—Red Hat OpenShift Container Platform 4.2 > Terminology
The following table provides definitions for some of the terms that are used in this design guide:
Table 1. Terminology
Term |
Explanation |
Container Storage Interface (CSI) |
A standard communications protocol for connecting container orchestration platforms such as Kubernetes to a storage plug-in. |
DevOps |
Engineering practices that combine software development and deployment, ensuring continuous delivery of quality software applications following a shortest-path delivery cycle. |
High availability (HA) |
An approach to system design that aims to ensure operational continuity, performance, and uptime in information systems. |
HA network |
Multiple network paths that provide redundant switches and NICs so that a cluster can continue to operate if a switch or NIC fails. |
Persistent Volume (PV) |
Storage that is provisioned by an administrator so that it can be used within the container infrastructure. A PV is assigned a StorageClass, which is a cluster storage resource against which PVC requests can be issued. |
Perisistent Volume Claim (PVC) |
A pointer to a persistent volume on the physical storage. When a container makes a PVC request, OpenShift allocates a physical disk and binds it to the PVC. After the container image is destroyed, the volume that is bound to the PVC is released, but the persistent storage policy for the volume determines when the volume is deleted. |
Virtual Link Trunking (VLT) |
A networking feature that allows switches to be aggregated so that they can be treated as a single unit. Provision of multiple NIC connections from each server across at least two aggregated switches provides resilience against component failure. |