Cloud Docs Home > F5 OpenStack LBaaSv2 Index

Attention

The F5 OpenStack Integrations documentation is moving to clouddocs.f5.com. Thank you for your patience during construction.

Glossary

active-active
Both BIG-IP devices in a pair are in an active state, processing traffic for different virtual servers or SNATs. If one device fails over, the remaining device processes traffic from the failed device in addition to its own traffic.
active-standby
active-standby pair
Only one of the two BIG-IP devices is in an active state – that is, processing traffic – at any given time. If the active device fails over, the second device enters active mode and processes traffic that was originally targeted for the primary device.
cluster
clustered
clustering
device cluster
device service cluster
device service clusters
DSC
Device Service Clustering provides synchronization and failover of BIG-IP configuration data among multiple BIG-IP devices on a network. You can configure a BIG-IP device on a network to synchronize some or all of its configuration data among several BIG-IP devices; fail over to one of many available devices; and/or mirror connections to a peer device to prevent interruption in service during failover.
device
BIG-IP hardware or virtual edition (VE).
device group
A device group is a component of a device service cluster. It consists of a collection of BIG-IP devices that trust each other and can synchronize, and sometimes fail over, their configuration data.
failover
fail over
fails over
Failover occurs when one device in an active-standby pair becomes unavailable; the secondary device processes traffic that was originally targeted for the primary device.
high availability
highly available
HA
The ability of a BIG-IP device to process network traffic successfully. An HA device is generally part of a device cluster.
mirror
mirroring
A BIG-IP system redundancy feature that ensures connection and persistence information is shared to another device in a device service cluster; mirroring helps prevent service interruptions if/when failover occurs.
multi-arm
multiple-arm
multi-arm mode
multiple-arm mode
Multi-arm mode is a network topology wherein servers/clients connect to the BIG-IP via different interfaces; two or more VLANs can be used to handle management and data traffic.
one-arm
one-arm mode
One-arm mode is a network topology wherein servers/clients connect to the BIG-IP via a single interface; a single VLAN handles all traffic.
overcloud
BIG-IP virtual edition (VE) deployed as an OpenStack instance.
pair
Two (2) BIG-IP devices configured to use the active-standby HA mode.
scalen
Two (2) or more BIG-IP devices configured as an active device cluster.
segmentation ID
segmentation id
VLAN tag
SSL offloading
SSL offloading relieves a Web server of the processing burden of encrypting and/or decrypting traffic sent via SSL, the security protocol that is implemented in every Web browser. For more information, see the F5 Glossary.
standalone
A single BIG-IP device; no HA.
undercloud
BIG-IP device (hardware or VE) deployed outside of OpenStack.
vcmp
Virtual Clustered Multiprocessing (vCMP) is a feature of the BIG-IP system that allows you to run multiple instances of the BIG-IP software on a single hardware platform.
vCMP guest
A vCMP guest is an instance of BIG-IP software created on the vCMP system for the purpose of provisioning one or more BIG-IP modules to process application traffic.
vCMP host
The vCMP host is the system-wide hypervisor that makes it possible for you to create and view BIG-IP instances, or vCMP ‘guests’.