| management node |
In IBM Cloud Infrastructure Center, a management node is a Linux machine running a set of services that do management work. One and only one management node is required for one cloud. The relationship between management node and compute node is 1:n, which means one management node manages multiple compute nodes |
| compute node |
In IBM® Cloud Infrastructure Center, a compute node is a Linux® machine running a set of agents for hypervisor so that it can be managed by management node. Compute node has 1:1 relationship to hypervisors, for example, you need create one compute node for each z/VM® managed and through the compute node the z/VM is managed by management node to run workload (for example, schedule a virtual machine to run on the z/VM). |
| compute template |
Default configurations for virtual machines. For example, the cpu, memory, disk size, and others. Called flavors in OpenStack. |
| deploy templates |
Deploy templates allow authorized users to quickly, easily, and reliably deploy an image. A deploy template contains everything that you need to deploy an image, including the deploy target, the storage connectivity group to use, the compute template to use, the size of the virtual machine to create, and so on. After the deploy template has been created, it is simple to use the template to create one or more virtual machines. |
| host |
In IBM Cloud Infrastructure Center, a host is a hypervisor (for example, z/VM) that contains processors, memory, and I/O resources. |
| project |
Resources belong to a project. This allows for resources to be made accessible to a single user by giving that user their own project. Alternatively, multiple users can be given access to the same resource by giving each of those users a role on the project in question. Projects are sometimes referred to as tenants. |
| requests |
Requests are any actions that require administrator approval before they can complete. IBM Cloud Infrastructure Center sends an approval request when a user attempts an operation that an administrator has set up to require approvals. |
| self service portal |
This includes the ability to create and use deploy templates. Accessing the self service portal requires self_service or administrator authority. |
| self service user |
A user that has been granted self_service authority. Self service users can access the self service portal. |
| virtual server (VM) |
Also called virtual machine, it's collection of processor, memory, and I/O resources that are defined to run an operating system and its applications. Virtual machines are also called instances (in an OpenStack context). |
| z/VM |
z/VM is highly secure and scalable virtualization technology for cloud infrastructure and for running critical applications on IBM Z and LinuxONE servers. Directory Maintenance Facility for z/VM (DIRMAINT) provides efficient and secure interactive facilities for maintaining your z/VM system directory, Resource Access Control Facility (RACF®) manages system data security and integrity on z/VM systems. In this document DIRMAINT and RACF are used to represent the mandatory and optional configuration on z/VM and you might choose other third party tools to complete same tasks |
| KVM |
Red Hat Enterprise Linux (RHEL) Kernel-based Virtual Machine (KVM)provides the virtualization functionality, which enables a machine running RHEL to host multiple virtual machines (VMs), also referred to as guests. VMs use the host’s physical hardware and computing resources to run a separate, virtualized operating system (guest OS) as a user-space process on the host’s operating system. KVM will be used to represent Red Hat Enterprise Linux (RHEL) Kernel-based Virtual Machine (KVM) in the rest of the documentation |
| RHCOS |
Red Hat Enterprise Linux CoreOS (RHCOS) represents the next generation of single-purpose container operating system technology. RHCOS combines the quality standards of Red Hat Enterprise Linux (RHEL) with the automated, remote upgrade features from Container Linux. |
| local storage |
Storage gets allocated in support of a virtual machine and its lifecycle can't exceed the owning virtual machine's lifecycle. The disks disappear when the virtual machine that use the local storage is decommissioned. Usually it is the storage managed by the underlayer hypervisor of the compute node, for example the ECKD or FBA diskpool on z/VM hypervisor or the storage of the KVM hypervisor. root disk, ephemeral disk and swap disk can be allocated from local storage |
| persistent storage |
Persistent storage is about storage objects (for example, volume) that comes from storage provider. Access rights and bindings between virtual machines and persistent storage objects can be established and released dynamically. A volume can be attached to a virtual machine and will be available even after the virtual machine is decommissioned. |
| volume |
Storage objects that allocated from persistent storage, multiple volumes can be allocated and attached to virtual machine |
| boot from volume |
Boot a virtual machine from a volume as root disk. |
| root disk |
The disk that virtual machine boots from |
| swap disk |
The disk is used for memory swap when memory usage is high |
| data disk |
Different from root disk and swap disk, the other disks used by the virtual machine are called data disks in IBM Cloud Infrastructure Center |