Hi Lincoln, My point about OVP is neither its name or its business. I was simply asking for some clarity about “OVP engagement plan” in MELD topics.
Agree, CNTT RC1 and RC2 document and select test cases implemented/integrated/maintained by OPNFV. Merging CNTT and OPNFV doesn’t change the model where a third-party, OVP or something else, can review the CNTT RC test results and can deliver a CNTT badge if it’s successful. What’s new due to the merge CNTT/OPNFV which asks for a specific topic: “OVP engagement plan” in MELD? Will OVP members bring developers for new test cases in OPNFV? Cédric De : Lincoln Lavoie [mailto:[email protected]] Envoyé : lundi 21 septembre 2020 22:32 À : OLLIVIER Cédric TGI/OLN <[email protected]> Cc : Jim Baker <[email protected]>; [email protected]; Kozlowski, Walter <[email protected]>; Georg Kunz <[email protected]>; [email protected]; Ranganath, Sunku <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Monkman, Bob <[email protected]>; STEINBRUECK, SCOTT A <[email protected]>; Tom van Pelt <[email protected]>; Soininen, Jonne (Nokia - FI/Espoo) <[email protected]>; DIEGO William TGI/OLN <[email protected]>; [email protected]; [email protected]; Brandon Wick <[email protected]>; Heather Kirksey <[email protected]>; Abdel, Rabi <[email protected]>; [email protected]; [email protected] Objet : Re: [cntt-tech-steering] Meld Kick off meeting minutes 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 <[email protected]<mailto:[email protected]>> 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:[email protected]<mailto:[email protected]>] Envoyé : lundi 21 septembre 2020 17:48 À : OLLIVIER Cédric TGI/OLN <[email protected]<mailto:[email protected]>> Cc : [email protected]<mailto:[email protected]>; Lincoln Lavoie <[email protected]<mailto:[email protected]>>; Kozlowski, Walter <[email protected]<mailto:[email protected]>>; Georg Kunz <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; Ranganath, Sunku <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Monkman, Bob <[email protected]<mailto:[email protected]>>; STEINBRUECK, SCOTT A <[email protected]<mailto:[email protected]>>; Tom van Pelt <[email protected]<mailto:[email protected]>>; Soininen, Jonne (Nokia - FI/Espoo) <[email protected]<mailto:[email protected]>>; DIEGO William TGI/OLN <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Brandon Wick <[email protected]<mailto:[email protected]>>; Heather Kirksey <[email protected]<mailto:[email protected]>>; Abdel, Rabi <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 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 <[email protected]<mailto:[email protected]>> 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 : [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] De la part de STEELE, SCOT Envoyé : vendredi 18 septembre 2020 18:23 À : Lincoln Lavoie <[email protected]<mailto:[email protected]>>; Kozlowski, Walter <[email protected]<mailto:[email protected]>>; Georg Kunz <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; Ranganath, Sunku <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Monkman, Bob <[email protected]<mailto:[email protected]>>; STEINBRUECK, SCOTT A <[email protected]<mailto:[email protected]>>; Tom van Pelt <[email protected]<mailto:[email protected]>>; Soininen, Jonne (Nokia - FI/Espoo) <[email protected]<mailto:[email protected]>>; DIEGO William TGI/OLN <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Brandon Wick <[email protected]<mailto:[email protected]>>; Jim Baker <[email protected]<mailto:[email protected]>>; Heather Kirksey <[email protected]<mailto:[email protected]>>; Abdel, Rabi <[email protected]<mailto:[email protected]>> Cc : '[email protected]<mailto:[email protected]>' <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> https://www.iol.unh.edu +1-603-674-2755 (m) [https://docs.google.com/uc?export=download&id=1j_iI6anwrnbQWNpTyuvukMLSNJJ8_8QU&revid=0B_0ujwABDnFZTmJiR3EzK0d1VjFKTjQvMENBWVM0QnA4ajhjPQ]<https://www.iol.unh.edu> _________________________________________________________________________________________________________________________ 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.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#24413): https://lists.opnfv.org/g/opnfv-tech-discuss/message/24413 Mute This Topic: https://lists.opnfv.org/mt/76986513/21656 Group Owner: [email protected] Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
