Dear TSC, I would like to propose the formation of a VNF validation subcommittee to develop and maintain a process to allow any VNF provider with a path to obtain an ONAP compatible label allowing for efficient & streamlined validations for both VNF and service providers. This has been a result of discussions with the community to clarify the work around the current project VVP. That project will remain but will focus solely on developing and maintaining any tools needed to support such validation activities which does not fall under the purview of other projects and/or components of ONAP.
Do note that there is an ongoing discussion around the relation with other LF projects and the potential of an LF wide validation/compliance program. Until that discussion is settled, it is however recommended to form this subcommittee. Please see the details below (which are also available at https://wiki.onap.org/pages/viewpage.action?pageId=25428888) Erik * TSC subcommittee name: VNF Validation Subcommittee (VVC) * TSC subcommittee purpose: The VNF validation subcommittee is responsible for developing and maintaining a process to allow any VNF provider with a path to obtain an ONAP compatible label allowing for efficient & streamlined validations for both VNF and service providers. The three key goals are: - Define and execute on a strategy to support and allow for resource-efficient VNF validations from both the VNF and service providers perspective - Define and implement the working model & framework for 3rd parties to be certified to validate VNFs and assign them with an ONAP compatible label - Identify and select the first set of 3rd parties to carry out, track and report successful VNF validations The VNF validation subcommittee will not make decisions around the implementation of various toolsets for validation but rather define. The VNF validation subcommittee is advisory by nature, and not authoritative. It may provide advice to projects and to the TSC, such as by providing a forum to help define alignment around the necessary feature sets or processes enhancement to facilitate the validation process and/or requirements. The VNF validation subcommittee operates on a rough consensus basis. If the subcommittee is unable to reach consensus on what advice to offer, the subcommittee will refer the matter to the TSC or inform the project that advice cannot be rendered. * TSC subcommittee expected deliverables: The VNF validation subcommittee will develop and maintain a defined, documented process for any VNF provider to obtain an ONAP compatible label. * TSC subcommittee starting participants: The VNF validation subcommittee is open to all interested participants, and meetings are open.
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
