<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Nov 16, 2014 at 5:31 AM, Irena Berezovsky <span dir="ltr"><<a href="mailto:irenab@mellanox.com" target="_blank">irenab@mellanox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Steve,<br>
Regarding SR-IOV testing, at Mellanox we have CI job running on bare metal node with Mellanox SR-IOV NIC. This job is reporting on neutron patches. Currently API tests are executed.<br>
The contact person for SRIOV CI job is listed at driverlog:<br>
<a href="https://github.com/stackforge/driverlog/blob/master/etc/default_data.json#L1439" target="_blank">https://github.com/stackforge/driverlog/blob/master/etc/default_data.json#L1439</a> </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
The following items are in progress:<br>
- SR-IOV functional testing<br></blockquote><div><br></div><div>Where do you envision these tests living?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Reporting CI job on nova patches<br></blockquote><div><br></div><div>Looking forward to it. I assume you will be working with the other people trying to set up assorted CI systems in this space.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Multi-node setup<br>
It worth to mention that we want to start the collaboration on SR-IOV testing effort as part of the pci pass-through subteam activity.<br>
Please join the weekly meeting if you want to collaborate or have some inputs: <a href="https://wiki.openstack.org/wiki/Meetings/Passthrough" target="_blank">https://wiki.openstack.org/wiki/Meetings/Passthrough</a><br>
<br>
BR,<br>
Irena<br>
<div class="HOEnZb"><div class="h5"><br>
-----Original Message-----<br>
From: Steve Gordon [mailto:<a href="mailto:sgordon@redhat.com">sgordon@redhat.com</a>]<br>
Sent: Wednesday, November 12, 2014 9:11 PM<br>
To: itai mendelsohn; Adrian Hoban; Russell Bryant; Ian Wells (iawells); Irena Berezovsky; <a href="mailto:baoli@cisco.com">baoli@cisco.com</a><br>
Cc: Nikola Đipanov; Russell Bryant; OpenStack Development Mailing List (not for usage questions)<br>
Subject: [Nova][Neutron][NFV][Third-party] CI for NUMA, SR-IOV, and other features that can't be tested on current infra.<br>
<br>
Hi all,<br>
<br>
We had some discussions last week - particularly in the Nova NFV design session [1] - on the subject of ensuring that telecommunications and NFV-related functionality has adequate continuous integration testing. In particular the focus here is on functionality that can't easily be tested on the public clouds that back the gate, including:<br>
<br>
- NUMA (vCPU pinning, vCPU layout, vRAM layout, huge pages, I/O device locality)<br>
- SR-IOV with Intel, Cisco, and Mellanox devices (possibly others)<br>
<br>
In each case we need to confirm where we are at, and the plan going forward, with regards to having:<br>
<br>
1) Hardware to run the CI on.<br>
2) Tests that actively exercise the functionality (if not already in existence).<br>
3) Point person for each setup to maintain it and report into the third-party meeting [2].<br>
4) Getting the jobs operational and reporting [3][4][5][6].<br>
<br>
In the Nova session we discussed a goal of having the hardware by K-1 (Dec 18) and having it reporting at least periodically by K-2 (Feb 5). I'm not sure if similar discussions occurred on the Neutron side of the design summit.<br>
<br>
SR-IOV<br>
======<br>
<br>
Adrian and Irena mentioned they were already in the process of getting up to speed with third party CI for their respective SR-IOV configurations. Robert are you attempting similar with regards to Cisco devices? What is the status of each of these efforts versus the four items I lifted above and what do you need assistance with?<br>
<br>
NUMA<br>
====<br>
<br>
We still need to identify some hardware to run third party CI for the NUMA-related work, and no doubt other things that will come up. It's expected that this will be an interim solution until OPNFV resources can be used (note cdub jokingly replied 1-2 years when asked for a "rough" estimate - I mention this because based on a later discussion some people took this as a serious estimate).<br>
<br>
Ian did you have any luck kicking this off? Russell and I are also endeavouring to see what we can do on our side w.r.t. this short term approach - in particular if you find hardware we still need to find an owner to actually setup and manage it as discussed.<br>
<br>
In theory to get started we need a physical multi-socket box and a virtual machine somewhere on the same network to handle job control etc. I believe the tests themselves can be run in VMs (just not those exposed by existing public clouds) assuming a recent Libvirt and an appropriately crafted Libvirt XML that ensures the VM gets a multi-socket topology etc. (we can assist with this).<br>
<br>
Thanks,<br>
<br>
Steve<br>
<br>
[1] <a href="https://etherpad.openstack.org/p/kilo-nova-nfv" target="_blank">https://etherpad.openstack.org/p/kilo-nova-nfv</a><br>
[2] <a href="https://wiki.openstack.org/wiki/Meetings/ThirdParty" target="_blank">https://wiki.openstack.org/wiki/Meetings/ThirdParty</a><br>
[3] <a href="http://ci.openstack.org/third_party.html" target="_blank">http://ci.openstack.org/third_party.html</a><br>
[4] <a href="http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/" target="_blank">http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/</a><br>
[5] <a href="http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/" target="_blank">http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/</a><br>
[6] <a href="http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/" target="_blank">http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/</a><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>
</div></div></blockquote></div><br></div></div>