End user guide¶
The rest of this document should probably move to the admin guide.
Nova architecture: An overview of how all the parts in nova fit together.
Block Device Mapping: One of the more complicated parts to understand is the Block Device Mapping parameters used to connect specific block devices to computes. This deserves its own deep dive.
See the reference guide for details about more internal subsystems.
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.
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.
Once you are running nova, the following information is extremely useful.
Admin Guide: A collection of guides for administrating nova.
Quotas: Managing project quotas in nova.
Availablity Zones: Availability Zones are an end-user visible logical abstraction for partitioning a cloud without knowing the physical infrastructure. They can be used to partition a cloud on arbitrary factors, such as location (country, datacenter, rack), network layout and/or power source.
Scheduling: How the 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.