Hi Wenjing,

Quick question, can you clarify what the refstack trials are gating?

/ Chris

From: Wenjing Chu <[email protected]>
Date: Wednesday, 8 March 2017 at 20:47
To: Christopher Price <[email protected]>, Jose Angel Lausuch 
Sales <[email protected]>, "Gaoliang (kubi)" 
<[email protected]>, "[email protected]" 
<[email protected]>, Tomofumi Hayashi <[email protected]>, Ulrich 
Kleber <[email protected]>
Cc: Tianhongbo <[email protected]>, Dave Neary <[email protected]>, 
"SULLIVAN, BRYAN L" <[email protected]>, Leo Wang <[email protected]>, "Lijun 
(Matthew)" <[email protected]>, wangwulin <[email protected]>, 
TECH-DISCUSS OPNFV <[email protected]>
Subject: [dovetail] RE: Refstack progress and result database AND Dovetail 
weekly meeting agenda

Thanks for the update, Chris. Good to know they are making good progress.

Copy/move to tech discuss list.

The purpose of this email is to ask info ahead of time so our call can be more 
efficient. As you notice, time is running short and if all discussion is on the 
one hour call only per week, it can be hard to get on track. The refstack work 
is a gating item on many other tasks. Timely update would be very helpful for 
finalizing the dovetail plan – we set the goal to have the outline of the plan 
in place by March the 10th. We will likely be behind that but let’s try.

Can we also update on http/https resolution? Tomofumi, or someone in Functest 
please help? Thanks.

Let’s put these in the agenda for Friday:

-          Review of the Dovetail Danube plan outline   -----Wenjing  
https://wiki.opnfv.org/display/dovetail/Dovetail+Danube+Plan (Will be updated 
to before the call). We want to identify items we agreed and items still need 
more discussions so we narrow down on the remaining open issues.

-          Refstack integration in Functest, result DB, interface with Dovetail 
 -----Mathew/Linda/Jose

-          CI requirements for dovetail  --------  Uli

-          http and https issues     ---- Tomofumi/Functest

-          approaches to infra support for dovetail test reporting – Chris P

-          New meeting time for some people (as US moves to DST after this 
weekend)

Comments on the agenda?

Since the agenda of the last few weeks had been more than time allowed, no 
exception this week,  I encourage we all update, share and review info ahead of 
time and use the call time mainly to discuss issues and decisions etc. Thank 
you all!

Hongbo, I didn’t see the calendar invite of the meeting. I don’t know if it is 
just me or not, but can you double check and if it is missing, send out the 
meeting invite again? Thanks.

Regards,
Wenjing

From: Christopher Price [mailto:[email protected]]
Sent: Wednesday, March 08, 2017 10:26 AM
To: Wenjing Chu <[email protected]>; Jose Lausuch 
<[email protected]>; Gaoliang (kubi) <[email protected]>; 
[email protected]
Cc: Tianhongbo <[email protected]>; 'Dave Neary' 
<[email protected]>; SULLIVAN, BRYAN L <[email protected]>; Leo Wang 
<[email protected]>
Subject: Re: Refstack progress and result database

Hi Wenjing,

As we discussed last Friday, we intend to report back on the status of the 
refstack integration on the DoveTail call.

I suggest having a chat with Matthew 
[email protected]<mailto:[email protected]> and Linda 
[email protected]<mailto:[email protected]> if you would like to get 
iterative updates on the progress of this work as they are stepping up to help 
while Jose is on PTO.  They are making good progress.

We have a scheduled time on the test WG call to discuss approaches to infra 
support for dovetail test reporting planned for the 16th. We should discuss 
that as well on Friday.
Best to have those conversations on the community discussion forums rather than 
limited distribution lists.

/ Chris

From: Wenjing Chu <[email protected]<mailto:[email protected]>>
Date: Wednesday, 8 March 2017 at 19:10
To: Jose Angel Lausuch Sales 
<[email protected]<mailto:[email protected]>>, "Gaoliang 
(kubi)" <[email protected]<mailto:[email protected]>>, 
"[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Cc: Christopher Price 
<[email protected]<mailto:[email protected]>>, 
Tianhongbo <[email protected]<mailto:[email protected]>>, 
Dave Neary <[email protected]<mailto:[email protected]>>, "SULLIVAN, BRYAN L" 
<[email protected]<mailto:[email protected]>>, Leo Wang 
<[email protected]<mailto:[email protected]>>
Subject: RE: Refstack progress and result database

I got a PTO message from Jose. Let me add Morgan – Morgan, can you help out? 
Thanks.

Wenjing

From: Wenjing Chu
Sent: Wednesday, March 08, 2017 10:06 AM
To: 'Jose Lausuch' 
<[email protected]<mailto:[email protected]>>; Gaoliang (kubi) 
<[email protected]<mailto:[email protected]>>
Cc: 'Christopher Price' 
<[email protected]<mailto:[email protected]>>; 
Tianhongbo <[email protected]<mailto:[email protected]>>; 
'Dave Neary' <[email protected]<mailto:[email protected]>>; 'SULLIVAN, BRYAN L' 
<[email protected]<mailto:[email protected]>>; 'Leo Wang' 
<[email protected]<mailto:[email protected]>>
Subject: Refstack progress and result database

Hi Jose, and Kubi

I want to follow up on two major topics that we’ve been discussing: integrating 
Openstack refstack, and storing test result for the purpose of dovetail. I’m 
trying to get a high level consensus in order to get the outline of the 
dovetail plan in place.

Jose, can you give an update on the status of integrating Refstack in Functest? 
Below I assume that’s a given – but if not, we would have to adjust.

Let me assume Functest is successful in integrating Refstack client in Danube 
(I think the server may not be necessary), dovetail tool will adjust to make 
the following changes:

-          All refstack test cases can be replaced by a single citation of 
Refstack test suite version in compliance_set.json definition file.
Similarly, all test cases in refstack can be removed from the review discussion 
tasks in Jira, unclutter the jira boards.

As dovetail needs to support multiple upstreams, it will be sensible to keep 
the test results in MongoDB as opnfv test projects’ common db. One possible way 
is to take the refstack output and store it in Mongodb with opnfv formatting. 
Once in Mongodb, a common API server/UI can make the results available for 
multiple purposes including cvp.

Kubi, how does the above sound to Yardstick and other performance projects, for 
future?

Please everyone chime in if the above outline is aligned with your thinking so 
we can make progress in this Friday’s call.

Wenjing

_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to