<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 2:32 PM, Nels Nelson <span dir="ltr"><<a href="mailto:nels.nelson@rackspace.com" target="_blank">nels.nelson@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Greetings list,-<br>
<br>
Over the next few weeks I will be working on developing additional Tempest<br>
gating unit and functional tests for the libvirt-lxc compute driver.<br></blockquote><div><br></div><div>Tempest is driver agnostic, just like the nova APIs strive to be. As a consumer of nova I shouldn't need to know what driver is being used.</div>
<div>So there should not be any libvirt-lxc only tests in Tempest.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
I am trying to figure out exactly what is required in order to accomplish<br>
the goal of ensuring the continued inclusion (without deprecation) of the<br>
libvirt-lxc compute driver in OpenStack. My understanding is that this<br>
requires the upgrading of the support status in the Hypervisor Support<br>
Matrix document by developing the necessary Tempest tests. To that end, I<br>
am trying to determine what tests are necessary as precisely as possible.<br>
<br>
I have some questions:<br>
<br>
* Who maintains the Hypervisor Support Matrix document?<br>
<br>
<a href="https://wiki.openstack.org/wiki/HypervisorSupportMatrix" target="_blank">https://wiki.openstack.org/wiki/HypervisorSupportMatrix</a><br>
<br>
* Who is in charge of the governance over the Support Status process? Is<br>
there single person in charge of evaluating every driver?<br></blockquote><div><br></div><div><br></div><div>The nova team is responsible for this, with the PTL as the lead of that team.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
* Regarding that process, how is the information in the Hypervisor<br>
Support Matrix substantiated? Is there further documentation in the wiki<br>
for this? Is an evaluation task simply performed on the functionality for<br>
the given driver, and the results logged in the HSM? Is this an automated<br>
process? Who is responsible for that evaluation?<br></blockquote><div><br></div><div>I am actually not sure about this one, but I don't believe it is automated though.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
* How many of the boxes in the HSM must be checked positively, in<br>
order to move the driver into a higher supported group? (From group C to<br>
B, and from B to A.)<br>
<br>
* Or, must they simply all be marked with a check or minus,<br>
substantiated by a particular gating test which passes based on the<br>
expected support?<br>
<br>
* In other words, is it sufficient to provide enough automated testing<br>
to simply be able to indicate supported/not supported on the support<br>
matrix chart? Else, is writing supporting documentation of an evaluation<br>
of the hypervisor sufficient to substantiate those marks in the support<br>
matrix?<br>
<br>
* Do "unit tests that gate commits" specifically refer to tests<br>
written to verify the functionality described by the annotation in the<br>
support matrix? Or are the annotations substantiated by "functional<br>
testing that gate commits"?<br></blockquote><div><br></div><div>In order to get a driver out of group C and into group B, a third party testing system should run tempest on all nova patches. Similar to what we have for Xen (<a href="https://review.openstack.org/#/q/reviewer:openstack%2540citrix.com+status:open,n,z">https://review.openstack.org/#/q/reviewer:openstack%2540citrix.com+status:open,n,z</a>).</div>
<div><br></div><div>To move from Group B to group A, the driver must have first party testing that we gate on (we cannot land any patches that fail for that driver).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Thank you for your time and attention.<br>
<br>
Best regards,<br>
-Nels Nelson<br>
Software Developer<br>
Rackspace Hosting<br>
<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
</blockquote></div><br></div></div>