openstack/nova
Code Issues Proposed changes
cf4b2e79f4
nova/doc/source/support-matrix.rst
John Garbutt b583604f05 Add argument to support-matrix sphinx extension 
Make it easier to add additional support-matrix entries by making the
filename of the ini file a required argument of the directive.

As a side effect, its clearer in the rst file where the data is stored.

Change-Id: I05bd30b64152368b53c030a32754d0ed4a35bf88
2016-01-06 11:32:30 +00:00

1.9 KiB
Raw Blame History

Feature Support Matrix

Warning

Please note, while this document is still being maintained, this is slowly being updated to re-group and classify features using the definitions described in here: feature_classification

When considering which capabilities should be marked as mandatory the following general guiding principles were applied

  • Inclusivity - people have shown ability to make effective use of a wide range of virtualization technologies with broadly varying featuresets. Aiming to keep the requirements as inclusive as possible, avoids second-guessing what a user may wish to use the cloud compute service for.
  • Bootstrapping - a practical use case test is to consider that starting point for the compute deploy is an empty data center with new machines and network connectivity. The look at what are the minimum features required of a compute service, in order to get user instances running and processing work over the network.
  • Competition - an early leader in the cloud compute service space was Amazon EC2. A sanity check for whether a feature should be mandatory is to consider whether it was available in the first public release of EC2. This had quite a narrow featureset, but none the less found very high usage in many use cases. So it serves to illustrate that many features need not be considered mandatory in order to get useful work done.
  • Reality - there are many virt drivers currently shipped with Nova, each with their own supported feature set. Any feature which is missing in at least one virt driver that is already in-tree, must by inference be considered optional until all in-tree drivers support it. This does not rule out the possibility of a currently optional feature becoming mandatory at a later date, based on other principles above.