This is about supporting all the features of BDMv2.
This includes booting from a volume, in various ways, and
specifying a custom set of ephemeral disks. Note some drivers
only supports part of what the API allows.

Network Function Virtualization (NFV) is about virtualizing network node
functions into building blocks that may connect, or chain together to
create a particular service. It is common for this workloads needing
bare metal like performance, i.e. low latency and close to line speed
performance.

To reduce the size of the matrix, we organize the features into groups.
Each group maps to a set of user stories that can be validated by a set
of scenarios and tests. Typically, this means a set of tempest tests.

This list focuses on API concepts like attach and detach volumes, rather than
deployment specific concepts like attach an iSCSI volume to a KVM based VM.

The Feature Group Maturity rating is specific to the API concepts, rather than
specific to a particular deployment. That detail is covered in the deployment
rating for each feature group.

Note

Although having some similarities, this list is not directly related
to the DefCore effort.

Feature Group ratings:

Incomplete

Incomplete features are those that do not have enough functionality to
satisfy real world use cases.

Experimental

Experimental features should be used with extreme caution. They are likely
to have little or no upstream testing, and are therefore likely to
contain bugs.

Complete

For a feature to be considered complete, it must have:

complete API docs (concept and REST call definition)

complete Administrator docs

tempest tests that define if the feature works correctly

sufficient functionality and reliability to be useful in real world
scenarios

a reasonable expectation that the feature will be supported long-term

Complete and Required

There are various reasons why a complete feature may be required, but
generally it is when all drivers support that feature. New
drivers need to prove they support all required features before they are
allowed in upstream Nova.

Required features are those that any new technology must support before
being allowed into tree. The larger the list, the more features are
available on all Nova based clouds.

Deprecated

Deprecated features are those that are scheduled to be removed in a future
major release of Nova. If a feature is marked as complete, it should
never be deprecated.

If a feature is incomplete or experimental for several releases,
it runs the risk of being deprecated and later removed from the code base.