OpenStack Compute (nova)

What is nova?

Nova is the OpenStack project that provides a way to provision compute instances (aka virtual servers). Nova supports creating virtual machines, baremetal servers (through the use of ironic), and has limited support for system containers. Nova runs as a set of daemons on top of existing Linux servers to provide that service.

It requires the following additional OpenStack services for basic function:

  • Keystone: This provides identity and authentication for all OpenStack services.
  • Glance: This provides the compute image repository. All compute instances launch from glance images.
  • Neutron: This is responsible for provisioning the virtual or physical networks that compute instances connect to on boot.

It can also integrate with other services to include: persistent block storage, encrypted disks, and baremetal compute instances.

For End Users

As an end user of nova, you'll use nova to create and manage servers with either tools or the API directly.

Tools for using Nova

  • Horizon: The official web ui for the OpenStack Project.
  • OpenStack Client: The official CLI for OpenStack Projects. You should use this as your CLI for most things, it includes not just nova commands but also commands for most of the projects in OpenStack.
  • Nova Client: For some very advanced features (or administrative commands) of nova you may need to use nova client. It is still supported, but the openstack cli is recommended.

Writing to the API

All end user (and some administrative) features of nova are exposed via a REST API, which can be used to build more complicated logic or automation with nova. This can be consumed directly, or via various SDKs. The following resources will help you get started with consuming the API directly.

  • Compute API Guide:: The concept guide for the API. This helps lay out the concepts behind the API to make consuming the API reference easier.
  • Compute API Reference: The complete reference for the API, including all methods and request / response parameters and their meaning.
  • API Microversion History: The compute API evolves over time through Microversions. This provides the history of all those changes. Consider it a "what's new" in the compute API.
  • Block Device Mapping: One of the trickier parts to understand is the Block Device Mapping parameters used to connect specific block devices to computes. This deserves its own deep dive.
  • Configuration drive: Provide information to the guest instance when it is created.

For Operators

Architecture Overview

Installation

The detailed install guide for nova. A functioning nova will also require having installed keystone, glance, and neutron. Please ensure that you follow their install guides first.

Deployment Considerations

There is information you might want to consider before doing your deployment, especially if it is going to be a larger deployment. For smaller deployments the defaults from the install guide will be sufficient.

  • Compute Driver Features Supported: While the majority of nova deployments use libvirt/kvm, you can use nova with other compute drivers. Nova attempts to provide a unified feature set across these, however, not all features are implemented on all backends, and not all features are equally well tested.
    • Feature Support by Use Case: A view of what features each driver supports based on what's important to some large use cases (General Purpose Cloud, NFV Cloud, HPC Cloud).
    • Feature Support full list: A detailed dive through features in each compute driver backend.
  • Cells v2 Planning: For large deployments, Cells v2 allows sharding of your compute environment. Upfront planning is key to a successful Cells v2 layout.
  • Placement service: Overview of the placement service, including how it fits in with the rest of nova.
  • Running nova-api on wsgi: Considerations for using a real WSGI container instead of the baked-in eventlet web server.

Maintenance

Once you are running nova, the following information is extremely useful.

  • Admin Guide: A collection of guides for administrating nova.

    Warning

    This guide was imported during the Pike cycle and is a bit out of date. It will be updated during Queens to be more accurate.

  • Upgrades: How nova is designed to be upgraded for minimal service impact, and the order you should do them in.

  • Quotas: Managing project quotas in nova.

  • Aggregates: Aggregates are a useful way of grouping hosts together for scheduling purposes.

  • Filter Scheduler: How the filter scheduler is configured, and how that will impact where compute instances land in your environment. If you are seeing unexpected distribution of compute instances in your hosts, you'll want to dive into this configuration.

  • Exposing custom metadata to compute instances: How and when you might want to extend the basic metadata exposed to compute instances (either via metadata server or config drive) for your specific purposes.

Reference Material

  • Nova CLI Command References: the complete command reference for all the daemons and admin tools that come with nova.
  • Configuration:
    • Configuration Guide: detailed configuration guides for various parts of you Nova system. Helpful reference for setting up specific hypervisor backends.
    • Config Reference: a complete reference of all configuration options available in the nova.conf file.
    • Sample Config File: a sample config file with inline documentation.
  • Policy: nova, like most OpenStack projects, uses a policy language to restrict permissions on REST API actions.

For Contributors

If you are new to Nova, this should help you start to understand what Nova actually does, and why.

There are also a number of technical references on both current and future looking parts of our architecture. These are collected below.

Indices and tables