Glossary of Terms
Node
Physical Bare-metal Server
Compute Node
Server which runs the hypervisor the customer instance lives on
Infrastructure Node
Command and Control (control plane) of the Cloud, these servers are what run the cloud and carry network traffic between instances.
Storage Node
Bare-metal server where customer instance data is stored. High capacity servers with a large number of SSDs, Storage nodes are grouped into storage clusters. SSDs are managed by an OSD.
Bare-metal server
A physical server that is used by one customer. Each server offered for rental is a distinct physical piece of hardware that is a functional server on its own. They are not virtual servers running under a hypervisor in multiple pieces of shared hardware. Future cloud services will allow customers to book bare-metal servers via the OpenStack Ironic service.
Storage Cluster
A group of Storage Servers which is Highly Available and Redundant providing storage services to a Cloud Region.
Instance
Virtual Machine running on a Compute Node. Instances have many sizes. Instances are billed by the hour.
CPU
Physical Processor in a Compute node, can be made by Intel or AMD, OneQode uses both. OneQode uses CPUs which balance the highest possible Core count whilst still not performing below 3.7 Gigahertz (3.7Ghz).
Core
A physical core on the CPU of the Compute node.
Thread
Virtual Components of a CPU Core. CPUs allow 2 threads per core. Threads are reserved for customers as a vCPU.
vCPU
Threads assigned to a customer Instance
Node Memory
RAM installed in a physical node
Instance Memory
RAM assigned to a customer Instance
Hypervisor
Software that runs on the compute node and runs/controls the customer virtual machines
OSD Node
A storage node without the control plane, contributing only disk space to a Storage Cluster.
Control Plane
A collection of highly available services responsible for provisioning, controlling and monitoring its assigned workload - ie storage, infrastructure
Cloud Region
A top level geographic area - ie a city
Availability Zone (AZ)
Collections of aggregate groups in a failure zone
Failure Zone
A Sub-Zone of a Cloud region, allows OneQode to offer Highly Available and Redundant services within a cloud region.
Aggregate Group
Groupings of compute, disk images and networking resources
Kubernetes
Software that allows customers to programmatically allocate and use OneQode Cloud resources, originally developed by google to manage in house resources.
Keystone
OpenStack’s single source of authentication and access control for end users. This service is critical to cloud operations.
Loadbalancer
Public facing web server responsible for forwarding HTTP/API requests to the cloud and balancing the requests between servers and keeping track of failed servers to no longer forward requests
Instance Storage/Volumes
Instance data that is contained inside a file on the Storage Cluster.
Images
Official Images
Images provided upstream by the official maintainers of the operating system (supported)
Community Images
Images provided by a third party community member, provided for convenience to customers but unsupported
Customer Images
Variants of official or community images maintained by the customer with their own customisations
API
An interface for customers to interact with the OneQode cloud via programmable software such as Kubernetes.
OneQode Cloud
A private (soon to be public) cloud service operated by OneQode which allows customers to access high performance, on demand compute resources to run applications on.
OpenStack
An open source cloud framework that forms the core of the software that runs the OneQode Cloud.
Tenant Network
A private virtual network within OneQode cloud that customers can use for internal communications between instances.
Cloud Router
A virtual router that customers can use to allow instances on a Tenant Network to access the internet via NAT.
Public Network
The Public Networks assign Internet Routable IP addresses to Customer Instances making them reachable on the internet.
NAT
Network Address translation. Allows multiple servers to operate behind a single Public Internet Routable IP.
Floating IP
instances are expected to be ephemeral, if keeping the address consistent is required by the client, we offer floating ips they can retain and assign to the instance of their choice