Use this glossary to get definitions of OpenStack-related words and phrases.
To add to this glossary, fork the openstack/openstack-manuals
repository on
github.com and update the source files through the
OpenStack contribution process.
The swift context of an account, or a user account from an identity service such as Active Directory, /etc/passwd, OpenLDAP, keystone, and so on.
Checks for missing replicas, incorrect, and corrupted objects in a specified swift account by running queries against the back-end SQLite database.
An SQLite database that contains swift accounts and related metadata and is accessed by the accounts server. Alternately, the keystone back-end which contains accounts.
A swift worker that scans for and deletes account databases that are marked for deletion on an account server.
Lists containers in swift and stores container information in the account database.
Component of swift that provides account services such as list, create, modify, and audit. Do not confuse with keystone, OpenLDAP, or similar user account services.
Authentication and Identity Service by Microsoft, based on LDAP. Supported in OpenStack.
A group of fixed and/or floating IP addresses that are assigned to a nova project and can be used by or assigned to the VM instances in a project.
A subset of API calls that are accessible to authorized administrators and are generally not accessible to end users or the public internet, can exist as a separate service (keystone) or can be a subset of another API (nova).
Both a VM container format and a VM disk format. Supported by glance.
Both a VM container format and a VM disk format. Supported by glance.
Both a VM container format and a VM disk format. Supported by glance.
The most common web server software currently used on the Internet, known as HTTPd.
All OpenStack core projects are provided under the terms of the Apache License 2.0 license.
The daemon, worker, or service that a client communicates with to access an API. In OpenStack, API endpoints can provide services such as authentication, adding images, booting virtual machines, and attaching volumes.
A feature of nova and quantum that allows custom modules to extend the core APIs.
Alternative term for a quantum plug-in or quantum API extension.
Any node running a daemon or worker that provides an API endpoint.
In OpenStack, a the API version for a
project is part of the URL. For example,
example.com/nova/v1/foobar
.
A collection of specifications used to access a service, application, or program. Includes service calls, required parameters for each call, and the expected return values.
Used along with iptables, ebtables, and ip6tables in nova to provide firewall services.
A group of interrelated web development techniques used on the client-side to create asynchronous web applications. Used extensively in horizon.
Association of an interface ID to a logical port. Plugs an interface into a port.
A worker process that verifies the integrity of swift objects, containers, and accounts. Auditors is the collective term for the swift account auditor, container auditor, and object auditor.
Project name for the initial release of OpenStack.
The process that confirms that the user, process, or client is really who they say they are through private key, secret token, password, fingerprint, or similar method. Abbreviated as AuthN.
A string of text provided to the client after authentication. Must be provided by the user or process in subsequent requests to the API endpoint.
The act of verifying that a user, process, or client is authorized to perform an action, such as delete a swift object, list a swift container, start a nova VM, reset a password, and so on. Abbreviate as AuthZ.
A segregated area of a cloud deployment.
The storage method used by the keystone catalog service to store and retrieve information about API endpoints that are available to the client. Examples include a SQL database, LDAP database, or KVS back-end.
The persistent data store used that glance uses to retrieve and store VM images. Options include swift, local file system, S3, and HTTP.
A glance container format that indicates that no container exists for the VM image.
A grouped release of projects related to OpenStack that came out in February of 2011. It included Compute (nova) and Object Storage (swift) only.
A device that moves data in the form of blocks. These device nodes interface the devices, such as hard disks, CD-ROM drives, flash drives, and other addressable regions of memory.
A method of VM live migration used by KVM to evacuate instances from one host to another with very little downtime during a user-initiated switch-over. Does not require shared storage. Supported by nova.
A type of VM image that exists as a single, bootable file.
Contains configuration information for a swift ring, and is used to re-configure the ring or to recreate it from scratch after a serious failure.
An executable program that is used to keep a glance VM image cache at or below its configured maximum size.
An OpenStack grouped release of projects that came out in the spring of 2011. It included Compute (nova), Object Storage (swift), and the Image service (glance).
Defines resources for a cell, including CPU, storage, and networking. Can apply to the specific services within a cell or a whole cell.
A table within the nova back-end database that contains the current workload, amount of free RAM, number of VMs running on each host. Used to determine on which VM a host starts.
A notification driver that monitors VM instances and updates the capacity cache as needed.
Contains a list of available API endpoints to a user after they authenticate to keystone.
A keystone service that provides a list of available API endpoints to a user after they authenticate to keystone.
An incubated project that provides metering and billing facilities for OpenStack.
Provides logical partitioning of nova resources in a child and parent relationship. Requests are passed from parent cells to child cells if the parent cannot provide the requested resource.
A nova option that allows parent cells to pass resource requests to child cells if the parent cannot provide the requested resource.
The nova component that contains a list of the current capabilities of each host within the cell and routes requests as appropriate.
Massively scalable distributed storage system that consists of an object store, block store, and POSIX-compatible distributed file system. Compatible with OpenStack.
The POSIX-compliant file system provided by Ceph.
A simple certificate authority provided by nova for cloudpipe VPNs and VM image decryption.
A scheduling method used by nova that randomly chooses an available host from the pool.
A nova API parameter that allows you to download changes to the requested item since your last request, instead of downloading a new, fresh set of data and comparing it against the old data.
A configuration management tool that supports OpenStack.
If a requested resource such as CPU time, disk storage, or memory is not available in the parent cell, the request is forwarded to its associated child cells. If the child cell can fulfill the request, it does. Otherwise, it attempts to pass the request to any of its children.
The OpenStack Block Storage service that maintains the block devices that can be attached to virtual machine instances.
A person who plans, designs, and oversees the creation of clouds.
A node that runs network, volume, API, scheduler and image services. Each service may be broken out into separate nodes for scalability or availability.
A package commonly installed in VM images that performs initialization of an instance after boot using information that it retrieves from the metadata service such as the SSH public key and user data.
A service in nova used to create VPNs on a per-project basis.
A pre-made VM image that serves as a cloudpipe server. Essentially, OpenVPN running on Linux.
Lists allowed commands within the nova rootwrap facility.
A project that is not officially endorsed by the OpenStack Foundation. If the project is successful enough, it might be elevated to an incubated project and then to a core project, or it might be merged with the main code trunk.
The nova-api daemon that provides access to the nova services. Can also communicate with some outside APIs such as the Amazons EC2 API.
Alternative term for a nova API extension.
The nova component that chooses suitable hosts on which to start VM instances.
A node that runs the nova-compute daemon and the virtual machine instances.
Alternative term for the nova component that manages VMs.
A segmented large object within swift that is put back together again and then sent to the client.
The amount of time it takes for a new swift object to become accessible to all clients.
Contains the output from a Linux VM console in nova.
Used to organize and store objects within swift, similar to the concept as a Linux directory but cannot be nested. Alternative term for a glance container format.
Checks for missing replicas or incorrect objects in the specified swift containers through queries to the SQLite back-end database.
A SQLite database that contains swift containers and related metadata and is accessed by the container server
The “envelope” used by glance to store a VM image and its associated metadata, such as machine state, OS disk size, and so on.
Component of swift that manages containers.
The swift component that provides container services, such as create, delete, list, and so on.
Alternative term for a cloud controller node.
Depending on context, the core API is either the OpenStack API or the main API of a specific core project, such as nova, quantum, glance, and so on.
An official OpenStack project. Currently consists of Compute (nova), Object Storage (swift), Image Service (glance), Identity (keystone), Dashboard (horizon), Networking (quantum), and Volume (cinder).
Data that is only known to or accessible by a user that is used to verify the user is who they say they are and presented to the server during authentication. Examples include a password, secret key, digital certificate, fingerprint, and so on.
An open source community project by Dell that aims to provide all necessary services to quickly deploy clouds.
An element of the nova capacity cache that is calculated based on the number of build, snapshot, migrate, and resize operations currently in progress on a given host.
A user-created Python module that is loaded by horizon to change the look and feel of the dashboard.
The web-based management interface for OpenStack. An alternative name for horizon.
The component of swift that copies changes in the account, container, and object databases to other nodes.
The panel that is displayed when a user accesses the horizon dashboard.
New users are assigned to this keystone tenant if no tenant is specified when a user is created.
A keystone token that is not associated with a specific tenant and is exchanged for a scoped token.
An option within glance so that rather than immediately delete an image, it is deleted after a pre-defined number of seconds.
Setting for the nova RabbitMQ message delivery mode, can be set to either transient or persistent.
In the context of swift this refers to the underlying storage device.
Maps swift partitions to physical storage devices.
Used to distribute the partitions among swift devices. The distribution is usually proportional to the storage capacity of the device.
Community project that uses shell scripts to quickly deploy complete OpenStack development environments.
A grouped release of projects related to OpenStack that came out in the fall of 2011, the fourth release of OpenStack. It included Compute (nova 2011.3), Object Storage (swift 1.4.3), and the Image service (glance).
The underlying format that a disk image for a VM is stored as within the glance back-end store. For example, AMI, ISO, QCOW2, VMDK, and so on.
In swift, tools to test and ensure dispersion of objects and containers to ensure fault tolerance.
A web framework used extensively in horizon.
Daemon that provides DNS, DHCP, BOOTP, and TFTP services, used by the nova VLAN manager and FlatDHCP manager.
A record that specifies information about a particular domain and belongs to the domain.
A method to automatically configure networking for a host at boot time. Provided by both quantum and nova.
Used in nova along with arptables, iptables, and ip6tables to create firewalls and to ensure isolation of network communications.
The Amazon Elastic Compute Cloud, a public cloud run by Amazon that provides similar functionality to nova.
Used along with an EC2 secret key to access the nova EC2 API.
OpenStack supports accessing the Amazon EC2 API through nova.
A nova component that allows OpenStack to communicate with Amazon EC2
Used along with an EC2 access key when communicating with the nova EC2 API, is used to digitally sign each request.
The Amazon commercial block storage product, similar to cinder.
See API endpoint.
Alternative term for a keystone catalog.
A list of URL and port number endpoints that indicate where a service, such as object storage, compute, identity, and so on, can be accessed.
Any piece of hardware or software that wants to connect to the network services provided by quantum, the Network Connectivity service. An entity can make use of quantum by implementing a VIF.
A storage volume attached to a virtual machine instance that does not persist after the instance is terminated.
A grouped release of projects related to OpenStack that came out in April 2012, the fifth release of OpenStack. It included Compute (nova 2012.1), Object Storage (swift 1.4.8), Image (glance), Identity (keystone), and Dashboard (horizon).
An OpenStack-supported hypervisor, owned by VMware.
An OpenStack-supported hypervisor, owned by VMware.
MD5 hash of an object within swift, used to ensure data integrity.
A collection of command line tools for administering VMs, most are compatible with OpenStack.
The process of migrating one or all virtual machine (VM) instances from one host to another, compatible with both shared storage live migration and block migration.
Alternative term for a nova API extension or plug-in. In the context of keystone this is a call that is specific to the implementation, such as adding support for OpenID.
Additional requirements that a user can specify when requesting a new instance, examples include a minimum amount of network bandwidth or a GPU.
An easy method to create a local LDAP directory for testing keystone and nova. Requires Redis.
The nova scheduling method that attempts to fill a host with VMs rather than starting new VMs on a variety of hosts.
The step of the nova scheduling process where hosts that cannot run the VMs are eliminated and are not chosen.
Used to restrict communications between hosts and/or nodes, implemented in nova using iptables, arptables, ip6tables and etables.
An IP address that is associated with the same instance each time that instance boots, generally not accessible to end users or the public internet, used for management of the instance.
A nova networking manager that provides a single Layer 2 domain for all subnets in the OpenStack cloud. Provides a single DHCP server for each instance of nova-network to assign and manage IP addresses for all instances.
The nova component that gives IP addresses to authorized nodes and assumes DHCP, DNS, and routing configuration and services are provided by something else.
A nova networking method where the OS network configuration information is injected into the VM (VM) image before the instance starts.
A nova network configuration where all of the instances have IP addresses on the same subnet. Flat networks do not use VLANs.
Describes the parameters of the various virtual machine images that are available to users, includes parameters such as CPU, storage, and memory. Also known as instance type.
UUID for each nova or glance VM flavor or instance type.
An IP address that a nova project can associate with a VM so the instance has the same public IP address each time that it boots. You create a pool of floating IP addresses and assign them to instances as they are launched to maintain a consistent IP address for maintaining DNS assignment.
A grouped release of projects related to OpenStack that came out in the fall of 2012, the sixth release of OpenStack. It includes Compute (nova), Object Storage (swift), Identity (keystone), Networking (quantum), Image service (glance) and Volumes or Block Storage (cinder).
swift middleware that allows users to upload (post) an image through a form on a web page.
A core project that provides the OpenStack Image Service.
Processes client requests for VMs, updates glance metadata on the registry server, and communicates with the store adapter to upload VM images from the back-end store.
The keystone endpoint template that contains services available to all tenants.
An open-source, distributed, shared file system,
Project name for the seventh release of OpenStack.
An operating system instance running under the control of a hypervisor.
An object state in swift where a new replica of the object is automatically created due to a drive failure.
A type of reboot where a physical or virtual power button is pressed as opposed to a graceful, proper shutdown of the operating system.
An integrated project that aims to orchestrate multiple cloud applications for OpenStack.
The project that provides the OpenStack Dashboard.
A physical computer, also known as a node. Contrast with: instance.
A method to further subdivide availability zones into a collection of hosts.
One of the hypervisors supported by OpenStack, developed by Microsoft.
Software that arbitrates and controls VM access to the actual underlying hardware.
A collection of hypervisors grouped together through host aggregates.
Unique numeric ID associated with each user in keystone, conceptually similar to a Linux or LDAP UID.
Alternative term for the Identity Service API.
The source used by keystone to retrieve user information an OpenLDAP server for example.
Provides authentication services, also known as keystone.
The API used to access the OpenStack Identity Service provided through keystone.
A collection of files for a specific operating system (OS) that you use to create or rebuild a server. You can also create custom images, or snapshots, from servers that you have launched.
The glance API endpoint for management of VM images.
Used by glance to allow images on the local host to be used rather than re-downloading them from the image server each time one is requested.
Combination of URI and UUID used to access glance VM images through the image API.
A list of tenants that can access a given VM image within glance.
The keystone tenant who owns a glance virtual machine image.
A list of VM images that are available through glance.
Alternative name for the glance image API.
The current status of a VM image in glance, not to be confused with the status of a running instance.
The back-end store used by glance to store VM images, options include swift, local file system, S3, or HTTP.
The UUID used by glance to uniquely identify each VM image.
A community project may be elevated to this status and is then promoted to a core project.
The process of filtering incoming network traffic. Supported by nova.
The process of putting a file into a virtual machine image before the instance is started.
A running VM, or a VM in a known state such as suspended that can be used like a hardware server.
Unique ID that is specific to each running nova VM instance.
The current state of a nova VM image.
Alternative term for flavor.
Alternative term for a flavor ID.
Unique ID assigned to each nova VM instance.
Unique ID for a quantum VIF or vNIC in the form of a UUID.
Used along with arptables, ebtables, and iptables to create firewalls in nova.
Used along with arptables, ebtables, and ip6tables to create firewalls in nova.
One of the supported response formats for the OpenStack API.
Tool used for OpenStack development to run jobs automatically.
An OpenStack-supported hypervisor
The project that provides OpenStack Identity services.
A tool to automate system configuration and installation on Red Hat, Fedora, and CentOS based Linux distributions.
An object within swift that is larger than 5 GBs.
The collaboration site for OpenStack.
Term used for OSI network architecture for the data link layer.
Virtualization API library used by OpenStack to interact with many of its supported hypervisors, including KVM, QEMU and LXC.
Software used to allow multiple VMs to share a single physical NIC within nova.
Plugin that allows a Linux bridge to understand a quantum port, interface attachment, and other abstractions.
An OpenStack-supported hypervisor.
The ability within nova to move running virtual machine instances from one host to another with only a small service interruption during switch-over.
Alternative term for an admin API.
A network segment used for administration, not accessible to the public internet.
Used to track segments of a large object within swift.
A special swift object that contains the manifest for a large object.
The association between a glance VM image and a tenant, allows images to be shared with specified tenant(s).
Contains a list of tenants that can access a given VM image within glance.
The ability to start new VM instances based on the actual memory usage of a host, as opposed to basing the decision on the amount of RAM each running instance thinks it has available. Also known as RAM overcommit.
The software package used to provide AMQP messaging capabilities within nova, default is RabbitMQ.
The main virtual communication line used by all AMQP messages for inter-cloud communications within nova.
Passes requests from clients to the appropriate workers and returns the output to the client once the job is complete.
The process of moving a VM instance from one host to another.
Facility in nova that allows each virtual machine instance to have more than one VIF connected to it.
Unique ID assigned to each network segment within quantum.
The nova component that manages various network components, such as firewall rules, IP address allocation, and so on.
Any nova node that runs the network worker daemon.
Represents a virtual, isolated OSI layer 2 subnet in quantum.
Unique ID for a quantum network segment.
The nova-network worker daemon, provides services such as giving an IP address to a booting nova instance.
Alternative term for an ephemeral volume.
The OpenStack project that provides compute services.
Alternative term for the nova Compute API.
A nova component that manages IP address allocation, firewalls, and other network-related tasks.
A BLOB of data held by swift, can be in any format.
Alternative term for the swift object API.
Opens all objects for an object server and verifies the MD5 hash, size, and metadata for each object.
A configurable option within swift to automatically delete objects after a specified amount of time has passed or a certain date is reached.
Uniquely ID for a swift object.
Used by swift to determine the location of an object in the ring. Maps objects to partitions.
Component of swift that copies and object to remote partitions for fault tolerance.
Component of swift that is responsible for managing objects.
Alternative term for the swift object API.
Provides eventually consistent and redundant storage and retrieval of fixed digital content.
Allows a user to set a flag on a swift container so all objects within the container are versioned.
The person responsible for planning and maintaining an OpenStack installation.
If a requested resource, such as CPU time, disk storage, or memory, is not available in the parent cell, the request is forwarded to associated child cells.
A unit of storage within swift used to store objects, exists on top of devices, replicated for fault tolerance.
Contains the locations of all swift partitions within the ring.
Used by swift to determine which partition data should reside on.
A VM state where no changes occur (no changes in memory, network communications stop, etc), the VM is frozen but not shut down.
Disk volumes that persist beyond the lifetime of individual virtual machine instances. Contrast with: ephemeral storage
Software component providing the actual implementation for quantum APIs, or for Compute APIs, depending on the context.
Component of keystone that provides a rule management interface and a rule based authorization engine.
A virtual network port within quantum, VIFs / vNICs are connected to a port.
Unique ID for a quantum port.
A tool to automate system configuration and installation on Debian based Linux distributions.
A glance VM image that is only available to specified tenants.
A logical grouping of users within nova, used to define quotas and access to VM images.
User defined alpha-numeric string in nova, the name of a project.
Alternative term for a cloudpipe.
A node that provides the swift proxy service.
Users of swift interact with the service through the proxy server which in-turn looks up the location of the requested data within the ring and returns the results to the user.
An API endpoint used for both service to service communication and end user interactions.
A glance VM image that is available to all tenants.
An IP address that is accessible to end-users.
The Network Controller provides virtual networks to enable compute servers to interact with each other and with the public network. All machines must have a public and private network interface. The public network interface is controlled by the public_interface option.
A configuration management tool that supports OpenStack.
Programming language used extensively in OpenStack.
A core OpenStack project that provides a network connectivity abstraction layer to OpenStack Compute.
API used to access quantum, provides and extensible architecture to allow custom plugin creation.
Allows nova and quantum integration thus allowing quantum to perform network management for nova VMs.
Interface within quantum that allows organizations to create custom plugins for advanced features such as QoS, ACLs, or IDS.
If swift finds objects, containers, or accounts that are corrupt they are placed in this state, are not replicated, cannot be read by clients, and a correct copy is re-replicated.
One of the hypervisors supported by OpenStack, generally used for development purposes.
In nova, the ability to set resource limits on a per-project basis.
The nova setting that allows or disallows RAM overcommitment.
The ability to start new VM instances based on the actual memory usage of a host, as opposed to basing the decision on the amount of RAM each running instance thinks it has available. Also known as memory overcommit.
Configurable option within swift to limit database writes on a per-account and/or per-container basis.
The process of distributing swift partitions across all drives in the ring, used during initial ring creation and after ring reconfiguration.
A component of swift used to collect metrics.
A number within a database that is incremented each time a change is made. Used by swift when replicating.
A glance service that provides VM image metadata information to clients.
Provides data redundancy and fault tolerance by creating copies of swift objects, accounts, and containers so they are not lost when the underlying storage fails.
The number of replicas of the data in a swift ring.
The process of copying data to a separate physical device for fault tolerance and performance.
The swift back-end process that creates and manages object replicas.
Unique ID assigned to each request sent to nova.
An entity that maps swift data to partitions. A separate ring exists for each service, such as account, object, and container.
Builds and manages rings within swift, assigns partitions to devices, and pushes the configuration to other storage nodes.
Alpha-numeric ID assigned to each keystone role.
A feature of nova that allows the unprivileged “nova” user to run a specified list of commands as the Linux root user.
Modular system that allows the nova underlying message queue software to be changed. For example, from RabbitMQ to ZeroMQ or Qpid.
Object storage service by Amazon, similar in function to swift, can act as a back-end store for glance VM images.
A nova component that determines where VM instances should start. Uses modular design to support a variety of scheduler types.
A keystone API access token that is associated with a specific tenant.
String of text only known by the user, used along with an access key to make requests to the nova API.
A set of network traffic filtering rules that are applied to a nova instance.
A swift large object that has been broken up into pieces, the re-assembled object is called a concatenated object.
Alternative term for a VM image.
Unique ID assigned to each nova VM instance.
Alternative term for the keystone catalog.
Unique ID assigned to each service that is available in the keystone catalog.
A keystone feature that allows services such as nova to automatically register with the catalog.
Special keystone tenant that contains all services that are listed in the catalog.
An administrator defined token used by nova to communicate securely with keystone.
The method of storage used by horizon to track client sessions such as local memory, cookies, a database, or memcached.
A feature of the load balancing service. It attempts to force subsequent connections to a service to be redirected to the same node as long as it is online.
A horizon component that stores and tracks client session information. Implemented through the Django sessions framework.
Block storage that is simultaneously accessible by multiple clients. For example, NFS.
Runs automated tests against the core OpenStack API, written in Rails.
A point-in-time copy of an OpenStack storage volume or image. Use storage volume snapshots to back up volumes. Use image snapshots to back up data, or as “gold” images for additional servers.
The nova VM scheduling algorithm that attempts to start new VM on the host with the least amount of load.
An open source SQL toolkit for Python, used in OpenStack.
A lightweight SQL database, used as the default persistent storage method in many OpenStack services.
Community project that captures nova AMQP communications, useful for debugging.
Alternative term for a fixed IP address.
WSGI middleware component of swift that serves container data as a static web page.
The method that a service uses for persistent storage such as iSCSI, NFS, or local disk.
A swift node that provides container services, account services, and object services, controls the account databases, container databases, and object storage.
Component of XenAPI that provides a pluggable interface to support a wide variety of persistent storage back-ends.
A persistent storage method supported by XenAPI such as iSCSI or NFS.
Collective name for the swift object services, container services, and account services.
An OpenStack core project that provides object storage services.
Creates a full swift development environment within a single VM.
Collective term for components within swift that allows for additional functionality.
Acts as the gatekeeper to swift and is responsible for authenticating the user.
A node that runs swift account, container, and object services.
Point in time since the last container and accounts database sync among nodes within swift.
An authentication facility within swift that allows swift itself to perform authentication and authorization, frequently used in testing and development.
Automated software test suite designed to run against the trunk of the OpenStack core project.
A swift middleware component that allows a user to create URLs for temporary object access.
A group of users, used to isolate access to nova resources. An alternative term for a nova project.
A keystone API endpoint that is associated with one or more tenants.
Unique ID assigned to each tenant within keystone, the nova project IDs map to the keystone tenant IDs.
An alpha-numeric string of text used to access OpenStack APIs and resources.
Used to mark swift objects that have been deleted, ensures the object is not updated on another node after it has been deleted.
Unique ID assigned to each swift request, used for debugging and tracing.
Alternative term for a keystone default token.
Collective term for a group of swift components that process queued and failed updates for containers and objects.
In keystone each user is associated with one or more tenants, and in nova they can be associated with roles, projects, or both.
A blob of data that can be specified by the user when launching an instance. This data can be accessed by the instance through the metadata service or config drive. Commonly used for passing a shell script that is executed by the instance on boot.
Unique ID assigned to each quantum VIF.
Allows physical CPUs to be sub-divided and those divisions are then used by instances. Also known as virtual cores.
An operating system instance that runs on top of a hypervisor. Multiple VMs can run at the same time on the same physical host.
An L2 network segment within quantum.
An interface that is plugged into a port in a quantum network. Typically a virtual network interface belonging to a VM.
Attachment point where a virtual interface connects to a virtual network.
Provided by nova in the form of cloudpipes, specialized instances that are used to create VPNs on a per-project basis.
Alternative term for a VM or guest.
Software that runs on a host or node and provides the features and functions of a hardware based network switch.
Alternative term for a virtual network.
A nova networking manager that divides subnet and tenants into different VLANs allowing for Layer 2 segregation. Provides a DHCP server for each VLAN to assign IP addresses for instances.
The Network Controller provides virtual networks to enable compute servers to interact with each other and with the public network. All machines must have a public and private network interface. A VLAN network is a private network interface, which is controlled by the vlan_interface option with VLAN managers.
Alternative term for an image.
A nova component that provides users access to the consoles of their VM instances through VNC or VMRC.
Disk-based data storage generally represented as an iSCSI target with a file system that supports extended attributes, can be persistent or ephemeral. Commonly used as a synonym for block device.
An API on a separate endpoint for attaching, detaching, and creating block storage for compute VMs.
A nova component that oversees and coordinates storage volume actions.
Alternative term for a volume plugin.
Unique ID applied to each storage volume under the nova control.
A nova component that creates, attaches, and detaches persistent storage volumes.
A nova node that runs the cinder-volume daemon.
A plugin for the nova volume manager. Provides support for a new and specialized types of back-end storage.
Alternative term for the Block Storage API.
The nova component that interacts with back-end storage to manage the creation and deletion of volumes and the creation of compute volumes, provided by the nova-volume daemon.
Used by swift storage devices to determine which storage devices are suitable for the job. Devices are weighted by size.
The sum of each cost used when deciding where to start a new VM instance in nova.
A nova process that determines the suitability of the VM instances for a job for a particular host. For example, not enough RAM on the host, too many CPUs on the host, and so on.
A daemon that carries out tasks. For example, the nova-volume worker attaches storage to an VM instance. Workers listen to a queue and take action when new messages arrive.
Tool used in OpenStack development to ensure correctly ordered testing of changes in parallel.