Open Stack

Hmm, that particular tempest run might have had admin credentials in the config (that particular result is from earlier this summer).  I was planning to do a new run this week or next anyway to take care of a couple of extraneous failures for tests that just became required in 2016.08, so I’ll double check then.

At Your Service,

Mark T. Voelker
OpenStack Architect



> On Sep 7, 2016, at 3:12 PM, Catherine Cuong Diep <cdiep at us.ibm.com> wrote:
> 
> Hi Mark,
> 
> The RefStack result [1] in this result set shows 1187 pass tests. Just want to confirm whether this RefStack test result was run with admin credential. Thanks for sharing the data!
> 
> [1] https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d
> 
> Catherine Diep
> ----- Forwarded by Catherine Cuong Diep/San Jose/IBM on 09/07/2016 12:02 PM -----
> 
> From:  Mark Voelker <mvoelker at vmware.com>
> To:  "defcore-committee at lists.openstack.org" <defcore-committee at lists.openstack.org>
> Date:  09/07/2016 11:32 AM
> Subject:  [OpenStack-DefCore] [interop-challenge] VIO 2.5 Test Result Report
> 
> 
> 
> 
> 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
> 
> [attachment "vio_2.5_results.txt" deleted by Catherine Cuong Diep/San Jose/IBM] [attachment "ATT00001.txt" deleted by Catherine Cuong Diep/San Jose/IBM] _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee