And 3rd party labs. :)

On Fri, Aug 11, 2017 at 11:14 AM, SULLIVAN, BRYAN L (BRYAN L) <
[email protected]> wrote:

> And before I forget, we should also allow end-users to participate in the
> beta program of course!
>
> Thanks,
> Bryan Sullivan | AT&T
>
> -----Original Message-----
> From: SULLIVAN, BRYAN L (BRYAN L)
> Sent: Friday, August 11, 2017 8:04 AM
> To: 'Lincoln Lavoie' <[email protected]>; Christopher Price <
> [email protected]>
> Cc: [email protected]
> Subject: RE: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
> Wenjing is going to add a page where we can document the plans and results
> for the beta program. Here’s what I suggested:
> • We freeze the CVP suite and Dovetail tools prior to start of the beta
> • We offer all OPNFV vendor members who produce commercial platforms that
> are applicable the chance to run the tests against their product and
> produce results provided back to OPNFV (in the form that CVP result
> reviewers will be expected to assess)
> • We get C&C to provide a team of result reviewers for the beta
> • On the wiki we build a table of those vendors who plan to do this, the
> results of the tests as assessed by the team, and any feedback of the
> vendor (sub-pages as needed depending upon the amount of feedback)
> • We do not release until both Dovetail and C&C are satisfied with the
> beta results, e.g. for scope (# of vendors participating) and results
> (reliability of the test suite/tools, and rate of compliance success)
>
> Thanks,
> Bryan Sullivan | AT&T
>
> From: [email protected] [mailto:
> [email protected]] On Behalf Of Lincoln Lavoie
> Sent: Friday, August 11, 2017 7:40 AM
> To: Christopher Price <[email protected]>
> Cc: [email protected]
> Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
> Hi Chris,
>
> We talked about this at the very end of the call, and I think it's in
> alignment.  I think we just need to write down the "rules" for the beta
> trial period, and get people signed up to participate in that process.  In
> other groups, I've seen the "cookie" to get that is the beta users would be
> the first users listed as "certified" and the organization would provide
> some press / media coverage to promote that accomplishment.
>
> Cheers,
> Lincoln
>
> On Fri, Aug 11, 2017 at 10:29 AM, Christopher Price <mailto:
> [email protected]> wrote:
> Sounds like a good approach Lincoln.  It would be nice to see how
> something like that fits into our current activities.  Sorry I couldn’t be
> on the call to discuss it today, finding myself a little over scheduled at
> the moment.
>
> / Chris
>
> From: Lincoln Lavoie <mailto:[email protected]>
> Date: Friday, 11 August 2017 at 16:01
> To: Christopher Price <mailto:[email protected]>
> Cc: Tianhongbo <mailto:[email protected]>, TECH-DISCUSS OPNFV
> <mailto:[email protected]>
>
> Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
> Hi Chris,
>
> What I've seen other programs do for trials/launch is the following:
>
> 1. Freeze the development of new work
> 2. A group of companies or users would volunteer to be beta trial testers,
> submitting feedback / bugs
> 3. Only bug fixes from those beta "customers" are reviewed and accepted.
> 4. We need to decide the beta outcome requirements (i.e. all customers are
> passing, all tests run, etc).
> 5. Once that outcome mark is hit, that version would be considered the
> version submitted for approval.
>
> Cheers,
> Lincoln
>
> On Fri, Aug 11, 2017 at 5:12 AM, Christopher Price <mailto:
> [email protected]> wrote:
> Hi Hongbo,
>
> Thanks, I’ve seen the information on the wiki.
> I guess the questions I have relates more to:  Once we have the tool in a
> ready state, do we have a plan to validate it against volunteer commercial
> systems prior to having the TSC vote and making it generally available?  I
> didn’t see that information on the wiki page, maybe I missed it?
>
> / Chris
>
> From: Tianhongbo <mailto:[email protected]>
> Date: Friday, 11 August 2017 at 11:05
> To: Christopher Price <mailto:[email protected]>,
> TECH-DISCUSS OPNFV <mailto:[email protected]>
> Subject: RE: [dovetail] weekly call agenda 8/11
>
> Hi Chris:
>
> Here is the page for recoding the history of this. We can discuss further.
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.
> opnfv.org_display_dovetail_Running-2Bhistory-2Bfor-2Bthe-
> 2Bdovetail-2Btool&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=G6rTJNQcAfoxUGn85uFP2BFvW7yxOA
> -a5DF7tkl_Ex0&e=
>
> Best regards
>
> hongbo
>
> From: mailto:[email protected] [mailto:mailto:
> [email protected]] On Behalf Of Christopher Price
> Sent: 2017年8月11日 16:55
> To: mailto:[email protected]
> Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
> Hi Guys,
>
> Do we have a time-plan for the remaining work?
>
> I see we still have a lot of documentation work to do and the test cases
> are in flux, but we have other things to do as well.
> -          Do we intend to test/validate the documentation in any way with
> community scenario’s prior to merging it?
> o   Do we have people, resources and time-plans for that?
> -          Will we arrange to test the toolchain against volunteer
> commercial systems in labs prior to making it available for use?
> o   Same as above; people, resources, time-plans?
>
> I can also see the links are all pointing to “https://urldefense.
> proofpoint.com/v2/url?u=http-3A__artifact.opnfv.org&d=DwMFaQ&c=LFYZ-o9_
> HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZ
> GNIrk-cgy0&m=-dwHgwLsTeowK_964D_XAiwPPle4hOsXb81wp9M4rjI&s=e7ZROw0-
> kxiIjS8MtKdwFFlxA5xafeOdsZav-vc1Y-M&e=” which is not I assume where we
> intend to publish the documentation.
>
> Would be good to see how these items line up during the status review and
> remaining milestones discussion.
>
> / Chris
>
>
> From: <mailto:[email protected]> on behalf of
> Trevor Cooper <mailto:[email protected]>
> Date: Friday, 11 August 2017 at 09:29
> To: TECH-DISCUSS OPNFV <mailto:[email protected]>
> Subject: Re: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
> Thanks Wenjing. I have updated the docs tracking page, lets review this
> for accuracy and highlight where reviews are most needed
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.
> opnfv.org_display_dovetail_Dovetail-2BDocumentation-
> 2Bfor-2BReview&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=JPekEWguFQcj5ODZXN8oLakGGyByaP
> eOTiFppGE9Qgk&e= …
>
> /Trevor
>
>
> From: mailto:[email protected] [mailto:
> [email protected]] On Behalf Of Wenjing Chu
> Sent: Thursday, August 10, 2017 9:14 AM
> To: TECH-DISCUSS OPNFV <mailto:[email protected]>
> Subject: [opnfv-tech-discuss] [dovetail] weekly call agenda 8/11
>
> Hi Dovetailers,
>
> Proposed agenda for this week’s call on Friday:
>
> 1)  Current tool+test status: (10 min)
> a.  dovetail version 0.5
> b.  Testing pod resources
> 2)  Docs, including the test case requirement patch
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.
> opnfv.org_gerrit_-23_c_38763_1&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=2NYKkUNqHPKHfV4MwIjUnaYv9dgPAC
> rYjlrVARxFQUk&e=  -(10 min)
> 3)  Overall status review and plan for the remaining milestones.  (40 min)
> As the project is getting into shape, it’s good time for us to map out the
> remaining milestones and time table.
>
> As always, let us know if you have comments/suggestions.
>
> Regards
> Wenjing
>
>
> _______________________________________________
> opnfv-tech-discuss mailing list
> mailto:[email protected]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss&d=DwMFaQ&c=LFYZ-o9_
> HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZ
> GNIrk-cgy0&m=-dwHgwLsTeowK_964D_XAiwPPle4hOsXb81wp9M4rjI&s=
> Q2O5g8DtTKrWPUGx46w8DGFYnxbnWEm-m65QnyzXP5A&e=
>
>
>
>
> --
> ************************************************************
> *******************
> Lincoln Lavoie
> Senior Engineer, Broadband Technologies
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.
> iol.unh.edu&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=DFcWgTiaqy-BbQG2CnUEUO3kQk4M-d84V7g_
> WFxlmSs&e=
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.
> iol.unh.edu&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=DFcWgTiaqy-BbQG2CnUEUO3kQk4M-d84V7g_
> WFxlmSs&e=
> 21 Madbury Rd., Ste. 100, Durham, NH 03824
> Mobile: +1-603-674-2755
> mailto:[email protected]
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.
> facebook.com_UNHIOL&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=anwCKhV9xHURaHZIqDlmiZYCyBmCcj
> r3GNj2jdtC0Ew&e=  https://urldefense.proofpoint.com/v2/
> url?u=https-3A__twitter.com_-23-21_UNH-5FIOL&d=DwMFaQ&c=
> LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZ
> GNIrk-cgy0&m=-dwHgwLsTeowK_964D_XAiwPPle4hOsXb81wp9M4rjI&
> s=hGTnv3CIcPM6bGa_99v7XugJnm00yqB1wnOX6lt8_1s&e=  https://urldefense.
> proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_
> unh-2Dinteroperability-2Dlab&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=NEDDaBldX3wu7_
> Ein2N2MiMOmrfGSFqzk9v6mTp5dkc&e=
>
> Ars sine scientia nihil est! -- Art without science is nothing.
> Scientia sine ars est vacua! -- Science without art is empty.
> ************************************************************
> *******************
>
>
>
>
> --
> ************************************************************
> *******************
> Lincoln Lavoie
> Senior Engineer, Broadband Technologies
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.
> iol.unh.edu&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=DFcWgTiaqy-BbQG2CnUEUO3kQk4M-d84V7g_
> WFxlmSs&e=
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.
> iol.unh.edu&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=DFcWgTiaqy-BbQG2CnUEUO3kQk4M-d84V7g_
> WFxlmSs&e=
> 21 Madbury Rd., Ste. 100, Durham, NH 03824
> Mobile: +1-603-674-2755
> mailto:[email protected]
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.
> facebook.com_UNHIOL-23&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=u27ZbL_jpb3jWEmCV40C6c1mTIhWkB-
> BHVTXwYOKMlY&e=  https://urldefense.proofpoint.com/v2/
> url?u=https-3A__twitter.com_-23-21_UNH-5FIOL&d=DwMFaQ&c=
> LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZ
> GNIrk-cgy0&m=-dwHgwLsTeowK_964D_XAiwPPle4hOsXb81wp9M4rjI&
> s=hGTnv3CIcPM6bGa_99v7XugJnm00yqB1wnOX6lt8_1s&e=  https://urldefense.
> proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_
> unh-2Dinteroperability-2Dlab&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-
> JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=-dwHgwLsTeowK_
> 964D_XAiwPPle4hOsXb81wp9M4rjI&s=NEDDaBldX3wu7_
> Ein2N2MiMOmrfGSFqzk9v6mTp5dkc&e=
>
> Ars sine scientia nihil est! -- Art without science is nothing.
> Scientia sine ars est vacua! -- Science without art is empty.
> ************************************************************
> *******************
>



-- 
*******************************************************************************
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies

<https://www.iol.unh.edu>
www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
[email protected]
<http://www.facebook.com/UNHIOL#>   <https://twitter.com/#!/UNH_IOL>
<http://www.linkedin.com/company/unh-interoperability-lab>

Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.
*******************************************************************************
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to