ChatGPT, 
Claude, 
Gemini, 
Grok — all four for Bluehost Private Cloud Glossary and Container Terms
This glossary explains the technical terms you will see across the Bluehost Private Cloud articles, in plain language. It covers Oracle Cloud Infrastructure (OCI), the platform Private Cloud is built on, plus VMware and container terms that are useful if you are comparing private cloud options or migrating from another platform.
Note: Including a term here does not mean every OCI or container service is part of every Private Cloud environment. Your Bluehost solutions engineer confirms what is included in your environment during scoping.
Private cloud fundamentals
Core terms used throughout the Bluehost Private Cloud articles.
| Term | What it means |
|---|---|
| Bare metal | A physical server used directly, without a hypervisor dividing it into virtual machines. |
| Cluster | A group of connected servers (nodes) that work together as one environment. In Bluehost Private Cloud, your cluster is made up of multiple nodes dedicated to your business. |
| Egress | Data leaving your environment, such as traffic sent from your servers to visitors or other systems on the internet. |
| Hypervisor | Software that runs on a physical server and divides it into multiple isolated virtual machines. |
| Ingress | Data coming into your environment, such as requests from visitors to your website or app. |
| Managed service | Hosting where the provider operates the infrastructure for you. Bluehost Private Cloud is fully managed by Bluehost by default. |
| Multi-node | An environment that runs on more than one server, so a single server failure does not have to take your workloads offline. |
| Multi-tenant | Infrastructure shared by more than one customer, such as shared hosting or a standard VPS host. |
| Node | A single server, physical or virtual, that is part of a cluster. |
| Noisy neighbor | When another customer on shared hardware uses so many resources that your performance suffers. Single-tenant infrastructure removes this risk. |
| Private cloud | Cloud infrastructure is dedicated to one organization rather than shared with other customers. |
| Resource overcommitment | Assigning more virtual resources (such as vCPUs or memory) to VMs than the physical hardware has on the assumption that not all will be used at once. |
| Single-tenant | Infrastructure reserved for one customer only. No other customer shares your hardware. |
| Tenancy | How infrastructure is divided between customers. In OCI, “tenancy” also means your organization’s top-level account. |
| vCPU | A virtual CPU assigned to a virtual machine. One vCPU usually maps one thread on a physical processor core. |
| Virtual machine (VM) | A software-based computer that runs its own operating system and applications on a shared or dedicated physical server. |
| Workload | Any application, website, database, or process running in your environment. |
Oracle Cloud Infrastructure (OCI) terms
Bluehost Private Cloud is built on OCI. These are the OCI terms you are most likely to see.
| Term | What it means |
|---|---|
| Availability domain (AD) | One or more isolated data centers within an OCI region. Some regions have several availability domains; many have one. |
| Block volume | Network-attached storage that works like a hard drive for an OCI instance. Used for operating systems, applications, and databases. |
| Boot volume | The block volume that holds an instances operating system. |
| Bucket | A container for files (called objects) in OCI Object Storage. |
| Compartment | A logical folder in OCI used to organize resources and control who can access them. |
| Custom image | A saved copy of an instances operating system and configuration that can be used to create new instances. OCI can import images in common formats, including VMDK and QCOW2. |
| Dynamic Routing Gateway (DRG) | An OCI virtual router that connects your virtual cloud network to other networks, such as an office network or another cloud. |
| FastConnect | A private, dedicated network connection between your own network and OCI that does not travel over the public internet. |
| Fault domain | A group of hardware within an availability domain. Spreading nodes across fault domains protects workloads from a single hardware failure. Each availability domain has three. |
| Flexible shape | An OCI compute shape that lets you choose the exact number of OCPUs and amount of memory for a instance. |
| Instance | An OCI compute server, either a virtual machine or a bare metal server. |
| Internet gateway | The OCI component that allows resources in a public subnet to communicate with the internet. |
| Live migration | Moving a running virtual machine to a different physical host without shutting it down, often during hardware maintenance. |
| Load balancer | A service that spreads incoming traffic across multiple nodes, so no single node is overloaded. |
| NAT gateway | The OCI component that lets resources in a private subnet reach the internet for things like updates, without being reachable from the internet. |
| Network security group (NSG) | A set of firewall rules applied to specific resources, such as a group of instances. |
| Object Storage | OCI storage for files such as media, backups, and logs, accessed over the network rather than attached like a disk. |
| OCID | Oracle Cloud Identifier. A unique ID assigned to every resource in OCI. |
| OCPU | Oracle CPU. A unit of compute equal to one physical processor core. On most x86 shapes, one OCPU equals two vCPUs. |
| Region | A geographic area containing one or more OCI data centers. |
| Security list | A set of firewall rules applied to every resource in a subnet. |
| Service gateway | An OCI component that lets your private network reach OCI services, such as Object Storage, without going over the internet. |
| Shape | A predefined template that sets an OCI instance’s CPU, memory, and network capacity. |
| Site-to-Site VPN | An encrypted connection over the internet between your network and your OCI environment. |
| Subnet | A smaller section of a virtual cloud network. Subnets can be public (reachable from the internet) or private. |
| Vault | OCI’s service for managing encryption keys and secrets such as passwords and certificates. |
| Virtual cloud network (VCN) | A private network in OCI that you control, like a traditional data center network. |
VMware terms
Common terms from VMware-based private clouds, useful if you are comparing options or migrating.
| Term | What it means |
|---|---|
| Datastore | A storage location in VMware where VM files are kept, built on local disks, a storage array, or vSAN. |
| Distributed Resource Scheduler (DRS) | A VMware feature that automatically balances VMs across hosts in a cluster based on resource use. |
| ESXi | VMware’s hypervisor. It is installed directly on a physical server and runs VMs. |
| Fault Tolerance (FT) | A VMware feature that runs a live copy of a VM on a second host, so it can take over instantly if the first host fails. |
| NSX | VMware’s software-defined networking and security platform, used to create virtual networks and firewall rules. |
| OVF / OVA | Standard file formats for packaging and moving virtual machines. An OVA is a single-file version of an OVF package. |
| Port group | A VMware network setting that defines how VMs connect to a virtual switch, often mapped to a VLAN. |
| Resource pool | A way to divide a VMware cluster’s CPU and memory into shares for different teams or workloads. |
| Snapshot | A point-in-time record of a VM’s state. Snapshots are useful before changes but are not a replacement for backups. |
| Template | A master copy of a VM used to create new, identically configured VMs. |
| vCenter Server | VMware’s central management tool for controlling multiple ESXi hosts and their VMs. |
| VMDK | Virtual Machine Disk. The file format VMware uses for a VM’s virtual hard drive. |
| vMotion | A VMware feature that moves a running VM from one host to another with no downtime. |
| VMware Tools | Software installed inside a VMware VM to improve performance and allow management from vCenter. |
| vSAN | VMware’s software-defined storage that pools the local disks of cluster hosts into shared storage. |
| vSphere | The name for VMware’s core virtualization platform, made up mainly of ESXi and vCenter Server. |
| vSphere HA | A VMware feature that automatically restarts VMs on another host if their host fails. |
| vSwitch | A virtual network switch in VMware that connects VMs to each other and to physical networks. |
Container terms
Containers are a lighter-weight way to package and run applications. These terms come up when running modern apps, microservices, and AI workloads.
| Term | What it means |
|---|---|
| Container | A lightweight, portable package that holds an application and everything it needs to run. Containers share the host’s operating system kernel, so they start faster and use fewer resources than VMs. |
| Container image | A read-only template used to create a container. It includes the application code, libraries, and settings. |
| Container registry | A storage location for container images, such as OCI Container Registry. |
| Container runtime | The software that runs containers on a server, such as a container. |
| Deployment | A Kubernetes setting that describes how many copies of an application should run and how to update them. |
| Docker | A widely used toolset for building and running containers. |
| Helm | A package manager for Kubernetes that installs and updates applications using reusable templates called charts. |
| Kubernetes | Open-source software that automatically deploys, scales, and manages containers across a cluster of servers. |
| Microservices | An application design where an app is split into small, independent services that each run in their own container. |
| Namespace | A way to divide a Kubernetes cluster into separate areas for different teams, apps, or environments. |
| OKE | Oracle Container Engine for Kubernetes. OCI’s managed Kubernetes service. |
| Orchestration | Automatically manage many containers, including starting, stopping, scaling, and recovering them. |
| Pod | The smallest unit in Kubernetes. A pod holds one or more containers that share network and storage. |
| Worker node | A server in a Kubernetes cluster that runs your application pods. |
Availability and recovery terms
Terms that describe how your environment stays online and recovers from problems.
| Term | What it means |
|---|---|
| Backup retention | How long backup copies are kept before they are deleted. |
| Disaster recovery (DR) | The plan and process for restoring service after a major failure. |
| Failover | Automatically switching to a healthy node or system when one fails. |
| Health check | A regular test that confirms that a node is responding. Load balancers use health checks to stop sending traffic to a failing node. |
| High availability (HA) | An infrastructure design that keeps workloads running when a component fails |
| Planned maintenance | Scheduled work on infrastructure, announced in advance. |
| RPO (Recovery Point Objective) | The maximum amount of data measured in time could be lost in failure. An RPO of one hour means you could lose up to one hour of data. |
| RTO (Recovery Time Objective) | The maximum time it should take to restore service after a failure. |
| SLA (Service-Level Agreement) | A formal commitment for service performance, such as uptime. |
| Uptime | The percentage of time a service is available and working. |
Security terms
Terms that describe how your environment and data are protected.
| Term | What it means |
|---|---|
| Audit log | A record of who did what and when in your environment. |
| DDoS attack | Distributed denial of service. An attempt to overwhelm a service with traffic, so it stops working. |
| Encryption at rest | Protecting data while it is stored, so it cannot be read without the right key. |
| Encryption in transit | Protecting data while it moves between systems, such as with TLS |
| Identity and access management (IAM) | The system that controls who can access which resources and what they can do. |
| Least privilege | Giving each person or system only the access it needs, and no more. |
| Network segmentation | Dividing a network into separate zones so a problem in one area cannot easily spread. |
| SSL/TLS certificate | A digital certificate that enables encrypted HTTPS connections to your website or app. |
| Web Application Firewall (WAF) | A filter that blocks common web attacks before they reach your application. |
| Zero trust | A security approach where no user or system is trusted by default, and every access request is verified. |
VMware to OCI equivalents
If you are coming from VMware, this table shows the closest OCI equivalent for common components. They are similar in purpose but do not always work the same way. For a full comparison,
| VMware | Closest OCI equivalent |
|---|---|
| ESXi host | Compute instance or bare metal server |
| vCenter Server | OCI Console and APIs (operated by Bluehost) |
| vSphere cluster | Multiple instances spread across fault domains |
| vMotion | Live migration |
| vSphere HA | Multi-node design with fault domains and load balancing |
| Datastore / vSAN | Block volumes |
| VMDK | Boot volume or block volume (VMDK files can be imported as custom images) |
| Template / OVA | Custom image |
| Snapshot | Volume backup |
| NSX segment / port group | VCN subnet |
| NSX distributed firewall | Network security groups and security lists |
| Resource pool | Compartments and flexible shapes |
| VMware Kubernetes offering | OKE (Oracle Container Engine for Kubernetes) |
Did you find this article helpful?