<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Hi,</div><div>At the moment the administrator is able to retrieve diagnostics for a running VM. Currently the implementation is very loosely defined, that is, each driver returns whatever they have to return. This is problematic in a number of respects:</div><ol><li>The tempest tests were written specifically for one driver and break with all other drivers (the test was removed to prevent this bug <span class="str">1240043</span>)</li><li>An admin is unable to write tools that may work with a hybrid cloud</li><li>Adding support for get_diagnostics for drivers that do not support is painful</li></ol><div>I'd like to propose the following for the V3 API (we will not touch V2 in case operators have applications that are written against this this may be the case for libvirt or xen. The VMware API support was added in I1):</div><ol><li>We formalize the data that is returned by the API [1]</li><li>We enable the driver to add extra information that will assist the administrators in troubleshooting problems for VM's</li></ol><div>I have proposed a BP for this - <a href="https://blueprints.launchpad.net/nova/+spec/diagnostics-namespace">https://blueprints.launchpad.net/nova/+spec/diagnostics-namespace</a> (I'd like to change the name to v3-api-diagnostics which is more apt)</div><div><br></div><div>And as Nelson Mandel would have said: It always seems impossible until it's done.</div><div><br></div><div>Moving forwards we decide to provide administrator the option of using the for V2 (it may be very helpful with debugging issues). But that is another discussion.</div><div><br></div><div>Thanks</div><div>Gary</div><div><br></div><div>[1] https://etherpad.openstack.org/p/vm-diagnostics</div></body></html>