c10348aeb4
Add a copy of Nova's support matrix document within the docs for nova-powervm. Within each section a powervm option has been added, denoting whether or not each feature is currently supported. This includes the base support matrix files as well as the library and conf changes required to build it in the nova-powervm docs build. Change-Id: I46511c61ce35164ec89098c6d876edb26ca8d261
42 lines
1.8 KiB
ReStructuredText
42 lines
1.8 KiB
ReStructuredText
|
|
Feature Support Matrix
|
|
======================
|
|
|
|
.. warning::
|
|
Please note, while this document is still being maintained, this is slowly
|
|
being updated to re-group and classify features
|
|
|
|
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.
|
|
|
|
.. support_matrix:: support-matrix.ini
|