Open Stack

On Thu, Feb 05, 2015 at 10:24:24AM -0600, Kurt Taylor wrote:
> On Thu, Feb 5, 2015 at 4:31 AM, Daniel P. Berrange <berrange at redhat.com>
> wrote:
> 
> > Hi Team Nova,
> >
> > This is a message to alert everyone to the fact that the old hypervisor
> > support matrix on the wiki[1], should really be considered obsolete.
> >
> > The canonical location for it going forward will be
> >
> >    http://docs.openstack.org/developer/nova/support-matrix.html
> >
> > That URL shows current GIT snapshot, releases will get their own URL
> > when the time comes.
> >
> > The source for this document is part of Nova GIT in the path
> >
> >    doc/source/support-matrix.ini
> >
> > The docs are auto-generated from that ini file using a sphinx extension
> >
> >    doc/ext/support_matrix.py
> >
> > The CSS styling is in
> >
> >    doc/source/_static/support-matrix.css
> >
> > Some things to note here
> >
> >  - The new doc was populated based on the contents of the old wiki page
> > from
> >    about two months ago, so if there have been additions to the wiki in
> > that
> >    time, they might not all have been captured - depends how good I was at
> >    figuring out changes.
> >
> >  - Improvements to the content and/or HTML styling should obviously be sent
> >    as patches to Nova GIT in the files mentioned above, via normal Gerrit
> >    review practice.
> >
> >  - Since it is in GIT, the support matrix is now able to record information
> >    per release branch of Nova. So users can be clear about what features
> >    their release of Nova supports, as opposed to playing guessing games.
> >
> >  - The in-tree document only covers features of the in-tree Nova drivers.
> >    As such it does not include information about Docker or PowerKVM or
> >    the (now deleted) BareMetal drivers. My currently suggestion is that
> >    people maintaining out of tree drivers, should reuse the sphinx
> > extension
> >    to format their own support matrix ini file in their local GIT repo.
> >
> 
> I think that maybe you have confused PowerKVM with PowerVM.  The PowerVM
> driver was removed, but PowerKVM support is in tree with libvirt.

Ok, so the wiki page was indeed referring to the libvirt impl. That wasn't
obvious since it didn't mention libvirt in the heading as all the other
libvirt columns did ! Sorry for not copying across your data then.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|