-email@example.com Date: Thursday, October 10, 2013 10:17 PM To: OpenStack Development Mailing List firstname.lastname@example.org:email@example.com Subject: Re: [openstack-dev] [nova] Looking for clarification on the diagnostics API Looks like this has been brought
: [openstack-dev] [nova] Looking for clarification on the diagnostics API Yup, it seems to be hypervisor specific. I have added in the Vmware support following you correcting in the Vmware driver. Thanks Gary From: Matt Riedemann mrie...@us.ibm.com Reply-To: OpenStack Development Mailing List
@lists.openstack.org Subject: Re: [openstack-dev] [nova] Looking for clarification on the diagnostics API There is also a tempest patch now to ease some of the libvirt-specific keys checked in the new diagnostics tests there: https://review.openstack.org/#/c/51412/ To relay some of my concerns that I put
Tempest recently got some new tests for the nova diagnostics API  which failed when I was running against the powervm driver since it doesn't implement that API. I started looking at other drivers that did and found that libvirt, vmware and xenapi at least had code for the get_diagnostics
Looks like this has been brought up a couple of times: https://lists.launchpad.net/openstack/msg09138.html https://lists.launchpad.net/openstack/msg08555.html But they seem to kind of end up in the same place I already am - it seems to be an open-ended API that is hypervisor-specific.