Re: [openstack-dev] [nova] Hypervisor support matrix now in GIT
On Thu, Feb 5, 2015 at 10:46 AM, Daniel P. Berrange berra...@redhat.com wrote: 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 berra...@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 No problem at all, here's the patch to add it: https://review.openstack.org/#/c/153342/ Kurt Taylor (krtaylor) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Hypervisor support matrix now in GIT
On 2/5/2015 4:49 AM, Daniel P. Berrange wrote: On Thu, Feb 05, 2015 at 11:40:46AM +0100, Andreas Jaeger wrote: On 02/05/2015 11:31 AM, Daniel P. Berrange wrote: 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 [...] In that case, I suggest to remove it's contents and just leave a pointer to the new location, See my point about it being the only place with info about the out of tree Docker PowerKVM drivers. I want to give them time to setup a support matrix in their own GIT repo before removing the only source of info about them. I will be updating the wiki page to warn people about the new location though. Regards, Daniel There might be some confusion on PowerKVM here, the pKVM support is in tree in the libvirt driver, that's what the PowerKVM third party CI is running against. The new as of last week PowerVM driver in stackforge [1] (and older PowerVC driver in stackforge [2]) are different and shouldn't be in the hypervisor support matrix wiki or the in-tree hypervisor support table. I can't wait for the day when there will be one power driver to rule them all and Frodo will have to destroy it in Mount Doom to avoid confusion. The only thing I'd say about the pKVM support in the in-tree matrix is what it's distro support is, i.e. if I have latest Fedora ppc64 will nova libvirt/qemu work with it? How about Ubuntu? [1] http://git.openstack.org/cgit/stackforge/nova-powervm/ [2] http://git.openstack.org/cgit/stackforge/powervc-driver/ -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Hypervisor support matrix now in GIT
On Thu, Feb 5, 2015 at 4:31 AM, Daniel P. Berrange berra...@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. I've not deleted the wiki page, since in the short term it is the only place with info about Docker/PowerKVM. - When submitting a new virt driver for merge in Nova, you should add it to the docs/source/support-matrix.ini file. This clearly shows reviewers what feature set your initial code submission supports For example, the Parallels team who have been adding Parallels support to Libvirt for Kilo should submit a patch to update this matrix prior to Kilo release. Likewise people working on making libvirt KVM run on Arm and PPC should update the matrix, since it only records x86 support status for Libvirt currently. I will push a patch to update the matrix shortly. - When adding support for new APIs to existing drivers, rememeber to update the docs/source/support-matrix.ini file to list the new capability for the driver you changed. - If adding new public API features, consider whether to add a new feature line item to the docs/source/support-matrix.ini if it is likely users need to know about support status across drivers. - Against each line item feature, there is note about whether the feature is considered mandatory to support in all drivers. The current support matrix only lists 2 features as mandatory - start and stop of instances. Everything else was left as optional on the basis that at least one existing in-tree driver doesn't support the feature. It is very important to note that this is a *tentative* list. The decision about mandatory vs optional features is subject to change as it has *not* undergone detailed critique by Nova core team at this time. IOW, we might make more features mandatory to support in the future. TBD. - There is clear scope for making the existing feature list more fine grained. For example there are many different ways to configure block storage for guests and only a few of them are captured in the current support matrix. Likewise for networking, and many other aspects of guest configuration. Sean has added the support matrix as a discussion item for today's Nova meeting, to evaluate what if any changes we need to make to it in the near term to better capture the current thoughts of Nova team about support status. https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting So either send questions in this thread or join the IRC meeting Regards, Daniel [1] https://wiki.openstack.org/wiki/HypervisorSupportMatrix -- |: 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 :| __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:
Re: [openstack-dev] [nova] Hypervisor support matrix now in GIT
On Thu, Feb 5, 2015 at 10:22 AM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: On 2/5/2015 4:49 AM, Daniel P. Berrange wrote: On Thu, Feb 05, 2015 at 11:40:46AM +0100, Andreas Jaeger wrote: On 02/05/2015 11:31 AM, Daniel P. Berrange wrote: 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 [...] In that case, I suggest to remove it's contents and just leave a pointer to the new location, See my point about it being the only place with info about the out of tree Docker PowerKVM drivers. I want to give them time to setup a support matrix in their own GIT repo before removing the only source of info about them. I will be updating the wiki page to warn people about the new location though. Regards, Daniel There might be some confusion on PowerKVM here, the pKVM support is in tree in the libvirt driver, that's what the PowerKVM third party CI is running against. The new as of last week PowerVM driver in stackforge [1] (and older PowerVC driver in stackforge [2]) are different and shouldn't be in the hypervisor support matrix wiki or the in-tree hypervisor support table. I can't wait for the day when there will be one power driver to rule them all and Frodo will have to destroy it in Mount Doom to avoid confusion. The only thing I'd say about the pKVM support in the in-tree matrix is what it's distro support is, i.e. if I have latest Fedora ppc64 will nova libvirt/qemu work with it? How about Ubuntu? [1] http://git.openstack.org/cgit/stackforge/nova-powervm/ [2] http://git.openstack.org/cgit/stackforge/powervc-driver/ -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Thanks Matt, I'll include that in the patch. Kurt Taylor (krtaylor) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Hypervisor support matrix now in GIT
On Thu, Feb 05, 2015 at 10:22:08AM -0600, Matt Riedemann wrote: On 2/5/2015 4:49 AM, Daniel P. Berrange wrote: On Thu, Feb 05, 2015 at 11:40:46AM +0100, Andreas Jaeger wrote: On 02/05/2015 11:31 AM, Daniel P. Berrange wrote: 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 [...] In that case, I suggest to remove it's contents and just leave a pointer to the new location, See my point about it being the only place with info about the out of tree Docker PowerKVM drivers. I want to give them time to setup a support matrix in their own GIT repo before removing the only source of info about them. I will be updating the wiki page to warn people about the new location though. Regards, Daniel There might be some confusion on PowerKVM here, the pKVM support is in tree in the libvirt driver, that's what the PowerKVM third party CI is running against. The new as of last week PowerVM driver in stackforge [1] (and older PowerVC driver in stackforge [2]) are different and shouldn't be in the hypervisor support matrix wiki or the in-tree hypervisor support table. Ok, so in this page https://wiki.openstack.org/wiki/HypervisorSupportMatrix#Features The 'PowerKVM' column doesn't mention libvirt and it links to this page www.ibm.com/systems/power/software/linux/powerlinux/powerkvm So I assumed that was referring to one of the stackforge drivers, and that info on power-kvm-with-libvirt was simply missing entirely from the wiki page. So we'd need someone to update the new in-tree docs with power-kvm-on-libvirt information from scratch. If anyone still cares about the non-libvirt Power drivers they can maintain a support matrix in stackforge for that. The only thing I'd say about the pKVM support in the in-tree matrix is what it's distro support is, i.e. if I have latest Fedora ppc64 will nova libvirt/qemu work with it? How about Ubuntu? The approach we've been trying to take with libvirt recently is that each new platform we support (whether a new architecture, or new libvirt hypervisor) would explicitly declare the minimum required libvirt version for that platform. eg the Parallels driver added MIN_LIBVIRT_PARALLELS_VERSION = (1, 2, 12) And in init_host() if (CONF.libvirt.virt_type == 'parallels' and not self._host.has_min_version(MIN_LIBVIRT_PARALLELS_VERSION)): Given that Power support in libvirt requires some minimum version, we'll need to add a MIN_LIBVIRT_POWER_KVM_VERSION and check for that. These min version numbers aren't something I've attempted to capture in the context of the feature matrix. 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 :| __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Hypervisor support matrix now in GIT
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 berra...@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 :| __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Hypervisor support matrix now in GIT
On 02/05/2015 11:31 AM, Daniel P. Berrange wrote:
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
[...]
In that case, I suggest to remove it's contents and just leave a pointer
to the new location,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton, HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] Hypervisor support matrix now in GIT
On Thu, Feb 05, 2015 at 11:40:46AM +0100, Andreas Jaeger wrote: On 02/05/2015 11:31 AM, Daniel P. Berrange wrote: 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 [...] In that case, I suggest to remove it's contents and just leave a pointer to the new location, See my point about it being the only place with info about the out of tree Docker PowerKVM drivers. I want to give them time to setup a support matrix in their own GIT repo before removing the only source of info about them. I will be updating the wiki page to warn people about the new location though. 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 :| __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
