Hi Tong et al, Attached are results for VIO 2.5. Note that Tong and I discussed the issues that we found on IRC and he has a patch up here that could use your reviews to make the workload code more portable: https://review.openstack.org/#/c/366784 I’ve documented the problems in these results anyway since I think it’ll be useful learning coming out of the challenge. To summarize: if you are concerned about workload portability, best practice for your workload code should be to either parameterize names for things like NICs and block devices or ideally to discover them. FWIW, both of these issues are quite trivial to work around in the workloads we’re testing with. At Your Service, Mark T. Voelker -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: vio_2.5_results.txt URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20160907/3fd05148/attachment.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20160907/3fd05148/attachment-0001.txt>