<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 5, 2015 at 4:31 AM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Team Nova,<br>
<br>
This is a message to alert everyone to the fact that the old hypervisor<br>
support matrix on the wiki[1], should really be considered obsolete.<br>
<br>
The canonical location for it going forward will be<br>
<br>
<a href="http://docs.openstack.org/developer/nova/support-matrix.html" target="_blank">http://docs.openstack.org/developer/nova/support-matrix.html</a><br>
<br>
That URL shows current GIT snapshot, releases will get their own URL<br>
when the time comes.<br>
<br>
The source for this document is part of Nova GIT in the path<br>
<br>
doc/source/support-matrix.ini<br>
<br>
The docs are auto-generated from that ini file using a sphinx extension<br>
<br>
doc/ext/support_matrix.py<br>
<br>
The CSS styling is in<br>
<br>
doc/source/_static/support-matrix.css<br>
<br>
Some things to note here<br>
<br>
- The new doc was populated based on the contents of the old wiki page from<br>
about two months ago, so if there have been additions to the wiki in that<br>
time, they might not all have been captured - depends how good I was at<br>
figuring out changes.<br>
<br>
- Improvements to the content and/or HTML styling should obviously be sent<br>
as patches to Nova GIT in the files mentioned above, via normal Gerrit<br>
review practice.<br>
<br>
- Since it is in GIT, the support matrix is now able to record information<br>
per release branch of Nova. So users can be clear about what features<br>
their release of Nova supports, as opposed to playing guessing games.<br>
<br>
- The in-tree document only covers features of the in-tree Nova drivers.<br>
As such it does not include information about Docker or PowerKVM or<br>
the (now deleted) BareMetal drivers. My currently suggestion is that<br>
people maintaining out of tree drivers, should reuse the sphinx extension<br>
to format their own support matrix ini file in their local GIT repo.<br></blockquote><div><br></div><div>I think that maybe you have confused PowerKVM with PowerVM. The PowerVM driver was removed, but PowerKVM support is in tree with libvirt.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I've not deleted the wiki page, since in the short term it is the<br>
only place with info about Docker/PowerKVM.<br>
<br>
- When submitting a new virt driver for merge in Nova, you should add<br>
it to the docs/source/support-matrix.ini file. This clearly shows<br>
reviewers what feature set your initial code submission supports<br>
<br>
For example, the Parallels team who have been adding Parallels support<br>
to Libvirt for Kilo should submit a patch to update this matrix prior<br>
to Kilo release.<br>
<br>
Likewise people working on making libvirt KVM run on Arm and PPC<br>
should update the matrix, since it only records x86 support status<br>
for Libvirt currently.<br></blockquote><div><br></div><div>I will push a patch to update the matrix shortly.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- When adding support for new APIs to existing drivers, rememeber to<br>
update the docs/source/support-matrix.ini file to list the new<br>
capability for the driver you changed.<br>
<br>
- If adding new public API features, consider whether to add a new<br>
feature line item to the docs/source/support-matrix.ini if it is<br>
likely users need to know about support status across drivers.<br>
<br>
- Against each line item feature, there is note about whether the<br>
feature is considered mandatory to support in all drivers. The<br>
current support matrix only lists 2 features as mandatory - start<br>
and stop of instances. Everything else was left as optional on the<br>
basis that at least one existing in-tree driver doesn't support<br>
the feature.<br>
<br>
It is very important to note that this is a *tentative* list. The<br>
decision about mandatory vs optional features is subject to change<br>
as it has *not* undergone detailed critique by Nova core team at<br>
this time. IOW, we might make more features mandatory to support<br>
in the future. TBD.<br>
<br>
- There is clear scope for making the existing feature list more<br>
fine grained. For example there are many different ways to configure<br>
block storage for guests and only a few of them are captured in the<br>
current support matrix. Likewise for networking, and many other<br>
aspects of guest configuration.<br>
<br>
<br>
Sean has added the support matrix as a discussion item for today's<br>
Nova meeting, to evaluate what if any changes we need to make to it<br>
in the near term to better capture the current thoughts of Nova team<br>
about support status.<br>
<br>
<a href="https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting" target="_blank">https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting</a><br>
<br>
So either send questions in this thread or join the IRC meeting<br>
<br>
Regards,<br>
Daniel<br>
<br>
[1] <a href="https://wiki.openstack.org/wiki/HypervisorSupportMatrix" target="_blank">https://wiki.openstack.org/wiki/HypervisorSupportMatrix</a><br>
<span class="HOEnZb"><font color="#888888">--<br>
|: <a href="http://berrange.com" target="_blank">http://berrange.com</a> -o- <a href="http://www.flickr.com/photos/dberrange/" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
|: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o- <a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> :|<br>
|: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o- <a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
|: <a href="http://entangle-photo.org" target="_blank">http://entangle-photo.org</a> -o- <a href="http://live.gnome.org/gtk-vnc" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>