Hi Cedric, Specifically with the Cloud Native OVP, the committee is working to help gather and aling requirements both inside the CNTT group, but also other "external" groups, such as ONAP or CNCF. This is absolutely necessary if the telecom industry is going to have an aligned set of requirements for vendor CNF products or infrastructure that seek to make claims about their offerings. Beyond the cloud native aspects, the larger OVP scope is not only about the testing requirements, made through reference to the CNTT specifications or project implementations, but also handles the creation and maintenance of the badge program governance. Since there is a desire (from what I've heard) of a well understand badging of products, that can been easily consumed by operators and their business teams (i.e. those responsible for documenting a request for proposals), the badge programs work to bridge the gaps between the detailed specification and test output (that could be 100's to 1000's of test cases).
In how OVP pertains to MELD, the output of MELD (i.e. the new potato) would continue to be one component of input into those badge spaces, alongside ONAP, CNCF, and potential other communities in the future. Hopefully this helps add some clarity to roles, beyond just documenting test cases within RC-1 or RC-2. Cheers, Lincoln On Mon, Sep 21, 2020 at 4:18 PM <cedric.olliv...@orange.com> wrote: > Jim, > > > > Yes O in OVP is deprecated and falsy for a while (see Compliance and > Verification Committee – LFN Committee). Nothing related to Meld. > > Sorry, I still don’t understand “OVP engagement plan” out of the rename > already on the agenda. > > > > BYW I would consider that any CNTT RC2 super-set (Cloud Native OVP?) is by > definition out of CNTT. > > Of course any additional test cases in RC2 would be welcome! > > > > Cédric > > > > *De :* Jim Baker [mailto:jba...@linuxfoundation.org] > *Envoyé :* lundi 21 septembre 2020 17:48 > *À :* OLLIVIER Cédric TGI/OLN <cedric.olliv...@orange.com> > *Cc :* cntt-tech-steer...@lists.opnfv.org; Lincoln Lavoie < > lylav...@iol.unh.edu>; Kozlowski, Walter < > walter.kozlow...@team.telstra.com>; Georg Kunz <georg.k...@est.tech>; > ulrich.kle...@huawei.com; Ranganath, Sunku <sunku.rangan...@intel.com>; > zhu...@chinatelecom.cn; hu....@zte.com.cn; wang.chang...@zte.com.cn; > fuq...@chinamobile.com; trevor.coo...@intel.com; ild...@openstack.org; > Monkman, Bob <bob.monk...@intel.com>; STEINBRUECK, SCOTT A <ss7...@att.com>; > Tom van Pelt <tp...@gsma.com>; Soininen, Jonne (Nokia - FI/Espoo) < > jonne.soini...@nokia.com>; DIEGO William TGI/OLN <william.di...@orange.com>; > nch...@mirantis.com; beth.co...@verizon.com; Brandon Wick < > bw...@linuxfoundation.org>; Heather Kirksey <hkirk...@linuxfoundation.org>; > Abdel, Rabi <rabab...@amazon.com>; cntt-...@lists.opnfv.org; > opnfv-tech-discuss@lists.opnfv.org > *Objet :* Re: [cntt-tech-steering] Meld Kick off meeting minutes > > > > Cedric, > > OVP engagement is really focused on ensuring the OVP program stays aligned > with the changes in the combined project. The name itself (OVP = OPNFV > verification program) will need to change as the OPNFV name becomes > deprecated. The name itself is incorrect today as it is ONAP that provides > the VNF/CNF onboarding testing... > > > > Cloud Native OVP is looking at a super-set of tests beyond what CNTT RC2 > may define. > > FYI, > > Jim > > > > On Mon, Sep 21, 2020 at 2:40 AM <cedric.olliv...@orange.com> wrote: > > Hi, > > > > In “Task Force Scope Statements”, I franky don’t understand “OVP > engagement plan”. > > CNTT RC1 and RC2 describe and select all mandatory test cases from OPNFV > and even define the way to export the test results (99,999% of the overall > work). > > In that case, OVP is reduced to a reviewer committee checking the test > results produced by CNTT cookbooks for LFN badges. > > Furthermore OVP is LFN committee and it’s out of OPNFV/CNTT Merger. > > Or is it about the next code contributions of OVP actors to the OPNFV test > frameworks? > > > > Again, I would encourage us not to use “Debt” everywhere. > > In OpenSource, such word would have asked for hundreds or thousands of > commits in the related project (OPNFV or CNTT). > > > > Cédric > > > > *De :* cntt-tech-steer...@lists.opnfv.org [mailto: > cntt-tech-steer...@lists.opnfv.org] *De la part de* STEELE, SCOT > *Envoyé :* vendredi 18 septembre 2020 18:23 > *À :* Lincoln Lavoie <lylav...@iol.unh.edu>; Kozlowski, Walter < > walter.kozlow...@team.telstra.com>; Georg Kunz <georg.k...@est.tech>; > ulrich.kle...@huawei.com; Ranganath, Sunku <sunku.rangan...@intel.com>; > zhu...@chinatelecom.cn; hu....@zte.com.cn; wang.chang...@zte.com.cn; > fuq...@chinamobile.com; trevor.coo...@intel.com; ild...@openstack.org; > Monkman, Bob <bob.monk...@intel.com>; STEINBRUECK, SCOTT A <ss7...@att.com>; > Tom van Pelt <tp...@gsma.com>; Soininen, Jonne (Nokia - FI/Espoo) < > jonne.soini...@nokia.com>; DIEGO William TGI/OLN <william.di...@orange.com>; > nch...@mirantis.com; beth.co...@verizon.com; Brandon Wick < > bw...@linuxfoundation.org>; Jim Baker <jba...@linuxfoundation.org>; > Heather Kirksey <hkirk...@linuxfoundation.org>; Abdel, Rabi < > rabab...@amazon.com> > *Cc :* 'cntt-...@lists.opnfv.org' <cntt-...@lists.opnfv.org>; > opnfv-tech-discuss@lists.opnfv.org; cntt-tech-steer...@lists.opnfv.org > *Objet :* [cntt-tech-steering] Meld Kick off meeting minutes > > > > Please review the notes from today’s Kick off meeting > > > > https://wiki.lfnetworking.org/x/JA5oAg > > > > Additionally we are looking for some more volunteers for the > Organization/Governance Task force. Please consider helping with this > initiative. > > > > > > Scot Steele, MS Organization Development > > Principal System Engineer– Org Development > > Network Cloud > > Office 707 461 8279 > > Mobile 678 654 5994 > > > > > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete > this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > > Thank you. > > > > > -- > > Jim Baker > > Linux Foundation Networking - Technical Program Manager > > mobile: +1 970 227 6007 > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > -- *Lincoln Lavoie* Senior Engineer, Broadband Technologies 21 Madbury Rd., Ste. 100, Durham, NH 03824 lylav...@iol.unh.edu https://www.iol.unh.edu +1-603-674-2755 (m) <https://www.iol.unh.edu>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#24412): https://lists.opnfv.org/g/opnfv-tech-discuss/message/24412 Mute This Topic: https://lists.opnfv.org/mt/76986513/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
