Skip to end of metadata
Go to start of metadata

Meetings 

The compliance and verification committee meets on a regular basis.

Monday, 0600 Pacific Standard Time/ 1500 Central European Time / 2200 China Standard Time/1400 UTC with the following Zoom meeting information.

Join Zoom Meeting
https://zoom.us/j/693999620
 
One tap mobile
+16699006833,,693999620# US (San Jose)
+16465588656,,693999620# US (New York)
 
Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 558 8656 US (New York)
        855 880 1246 US Toll-free
        877 369 0926 US Toll-free
Meeting ID: 693 999 620

Find your local number: https://zoom.us/u/acP8o0LT6z 


There is a mailing list and calendar on groups.io.

Subscribe to the calendar here: https://lists.lfnetworking.org/g/compliance/ics/3684108/1233804156/feed.ics

Committee Charter:

  • The Compliance and Verification Committee (“C&V Committee”) is a members-driven committee within LF Networking that recommends policies and oversight for compliance and certification program to the Governing Board of LF Networking (“Governing Board”).
  • C&V Committee operates under the direction of the Governing Board and its recommendations are subject to approval by the Governing Board. The C&V Committee will meet by conference call, online conference or in face-to-face sessions.

  • Participation in the C&V Committee is open to members of LF Networking, and the target makeup of the C&V Committee is to include a balance of representatives with active testing

Committee Members:

NameCompany
Andrei KojukhovAmdocs
Atul PurohitVodafone
Beth CohenVerizon
Bryan SullivanAT&T
Bryan Whittleiconectiv
Davide CherubiniVodafone
Deng LingliChina Mobile
Frank BrocknersCisco
*Fu QiaoChina Mobile
*Ganesh Kadarkaraimuthu Verizon
Georg KunzEricsson
Glenn SeilerWind River
Juha OravainenNokia
Kanagaraj ManickamHuawei
Kareem ElhassanyEquinox International
Kodilinye Atuchukwu Vodafone
Larry LamersVMware
Lincoln Lavoie (Committee Chair)UNH-IOL Lincoln Lavoie
Mandeep Singh KalraAccenture
Mark ShostakAT&T
Morgan RichommeOrange
Mustafa ÖzdenNetsia
Patric LineVoerEir
Prayson PateADVA Optical Networking
*Rabi Abdel (Committee Vice-chair)Vodafone
Ramesh NagarajanAccenture
*Remi BarsOrange
Ryan HallahanAT&T
*Serena FengZTE
Shiby Parayiliconectiv
Susan Manginiiconectiv
*Steven WrightAT&T
*Tapio TallgrenNokia
Tim IrnichSUSE
Timo PeralaNokia
Trevor CooperIntel
Trevor LovettAT&T
*Victor GaoHuawei
Vincent DannoOrange
Vincent ScharfDeutsche Telekom
VM (Vicky) BrasseurJuniper
Xu DanHuawei
Yan GuanzhiHuawei
Yuan YueZTE
Fernando OliveiraVerizon

Each participating LFN member organization is entitled to one vote in the annual chair election.

The asterisk * indicates the voting member for organizations that have multiple members participating in the Committee

Governance

The Chair and Vice-Chair positions are appointment for a 1-year term each April.  Typical nomination period will be 2 weeks, followed by a 1 week voting period, similar to the typical project TSC processes.  

4 Comments

  1. Hi ,

    Sorry for some naive queries. 

    1. Is this verification program is for VNF level ( let say i on-boarded and deployed one VNF from vendor X and it will continue to run if in future i replace product with vendor Y ) ?  OR
    2. this verification program will support in components level ( let say i have a product ( specifically if ONAP) of different component VNFM, Orchastrator, etc and if i want to replace VNFM with another vendor products and it will continue running as a system etc ) OR
    3.  Something else to my understanding then please let me know.


    Would be helpful if you provide some more study materials. 

    Regards

    Abhay Narayan Katare


    1. Hello Abhay Narayan Katare

      For your first question, I think the answer is slightly more gray.  To "replace" a VNF between vendors, you would need to verify the functions provided by the VNF are "equal" in addition to ensuring the VNF runs on top of the infrastructure.  For example, if your VNF is providing an IP routing function, both VNFs need to provide the same IP routing capabilities to support the swap.  Because there are a huge (un-countable) number of possible functions provided by VNFs, the program is not able to solve that problem.  The program is focused on verification of the VNF running within the infrastructure, including MANO.  This is the next logical step, beyond the tests currently run by the VVP and VNFSDK projects cited by Victor.

      For the second part, Victor is correct, that would require testing of all the individual interfaces for each component.  The current NFVI program (https://nfvi-verified.lfnetworking.org/#/) does cover this topic to a degree, treating the NFVI as a "component" and testing it supports the set of capabilities, agreed by the OPNFV project for the specific test release.  The tests for the capabilities are pulled from a combination of the Functest and Tempest, Bottlenecks, and yardstick.  The tests are designed to run on both the vanilla open source installs, as well as commercial installs, which I think would give you part of what you are referring to, in terms of "swapping" or "comparing" one NFVI with another.

  2. Hi, Abhay Narayan Katare

    Please See my answer inline。
    Is this verification program is for VNF level ( let say i on-boarded and deployed one VNF from vendor X and it will continue to run if in future i replace product with vendor Y ) ? OR
    Victor: Yes, ONAP has two projects for VNF verification call VNFSDK(for tosca based VNF) and VVP (for Heat Based VNF). For the VNF Replacement, currently, in my opinion, the answer is No. we are try to define the common requirements for VNF LCM and Performance and Compliance Check. currently, the compliance test is available.
    this verification program will support in components level ( let say i have a product ( specifically if ONAP) of different component VNFM, Orchastrator, etc and if i want to replace VNFM with another vendor products and it will continue running as a system etc ) OR
    Victor: I think the answer is No. This is more like the API compliant between multiple components. Maybe you can have a quick look on ONAP VF-C projects which could talk with multiple VNFM via the driver.
    Something else to my understanding then please let me know.

    CVC Vision Reference: Meeting Minutes and Materials

    CVC MVP on ONAP EI Alto Release:VNF Validation Minimum Viable Product

    1. Hi Victor GaoLincoln Lavoie

      Thanks for your quick response.

      Let me again try to put my query as seems i could not clearly elaborate it.

      First Query:   Is this verification program will support in VNF level  ( let say i on-boarded and deployed one VNF from vendor X of ONAP (here i am not replacing VNF , i am just replacing Vendor of ONAP after it is on-boarded and deployed ) and in future due to cost or any other factor i want to replace this vendor with another Vendor of ONAP ( Let Say "Y" ).

      So, should this VP will support this feature of Vendor replacement.

      Second Query: 

      I am agree that in order to support interoparability in component level ( i.e. replacing particular component (SO, SDC, APC etc ) of ONAP from one vendor or even to integrate vendor specific support of VNFM in ONAP  etc) we have to first adopt standardization in interfaces ( SOL002, SOL003 etc Interfaces ) and even standardization in packaging of VNFs (SOL001, SOL004 etc support). 

      So this VP will also support this feature after adopting standardization.