You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Project Name:         ICE *(Incubation & Certification Environment)  

  • Proposed name for the project: ICE
  • Proposed name for the repository: ICE

Project description:

The project is to develop a certification program to provide assurance of VNF interoperability with ONAP. Obtaining a certifications shall be a self-service activity driven by the VNF Provider. Such a certification should be against a reference release of ONAP for use by the VNF provider & certification authority.

This project at ONAP WILL NOT operate as a Certification Authority.  This project WILL  create a process to identify and qualify Certification Authorities will be developed and maintained.  Self-Certification MAY be considered as a Certification authority option.  

 The project is intended to validate the following:

1)     VNF Guidelines/ Requirements compliance ( including e.g. security, resilience, upgradeability )

2)     VNF Operates with ONAP ( including e.g. VNF Instantiation, VNF Monitoring)

This project WILL propose how to deal with

(1) revisions to the certification testing regime and

(2) changes to the VNF and

(3) changes to the VNF metadata

This project will provide a process to evolve the certification criteria based on experience. At each release of ONAP, the scope of functionality tested and the test coverage for VNF certification may change. Lessons learned from operational experience may generate additional VNF requirements, or lead to improved test coverage etc.

The overall objective of the project is to build & foster an active community at ONAP contributing to all aspects of an ONAP VNF Certification program, and the key goals are:

1. Define and start to execute on a long-term strategy & goals to support and allow for a resource efficient model for  VNF validation across the combined ONAP  ecosystem.

2. Build & foster an active contributor community across the ONAP ecosystem to support a broad  alignment & definition  Around the ONAP VNF Requirements & Guidelines.

3. Introduce an efficient and seamless process to allow the community to contribute to all aspects  of the validation process and platform

And to:

1.  Define &   establish an overall governance model for the program to properly continuously define a scalable, and flexible model for certifying

2.  Define &   establish a resource-efficient model for VNF providers and other

parties to  acquire an ONAP Compatible  label.

3.  Define &   foster an active contributor community with at least 10 monthly active contributors from 4 different companies or organization

4.  Define a  roadmap for the expansion of the   program to include additional validation scope  and dependencies  to other projects inside  ONAP

The VNF Provider is expected to maintain its VNFs resulting in multiple versions including revisions dues to metadata changes. This Project SHALL provide guidance as to when recertification is recommended.  

This project will validate the VNF package integrity and provenance e.g. using signing & Attestation

This Project WILL validate VNF operation on some defined infrastructure (cloud) resources & environment. These tests can also include verification of the VNF compatibility with specific NVFI envs, e.g. public/private clouds and SP-specific NFVI deployments or standard reference NFVI platforms such as developed by OPNFV centered upon major commercial OpenStack distributions.

This Project WILL maintain the authoritative set of tests and test procedures for Certification of VNFs. This project SHALL develop the tests and test procedures traceable to the VNF Requirements

This Project SHALL report the test coverage of the VNF Certification program against the VNF Requirements and the ONAP. Each VNF requirement should be checked via a test to enable automation 'certification".



The Project SHALL report the results of the certification test suite on a given VNF to the person invoking the certification test.

The VNF Certification testing SHALL be as automated as possible. This Project SHALL develop that automation framework for certification testing.



Drivers:

  • De-risk deployments
  • separate Common industry certification from operator specific, or function specific   
  • Not providing certification of the functions a VNF is to provide
  • just get started

OpenStack?

Scope:

  • Describe the functionality to be provided by the project.  Please provide the full intended scope of the project; not just what is intended for the project's first release.
  • Specify any interface/API specification proposed,
  • Identity a list of features and functionality will be developed.
  • Identify what is in or out of scope. During the development phase, it helps reduce discussion.

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?
  • Please Include architecture diagram if possible
  • What other ONAP projects does this project depend on?
  •  Release 1 Definition
          
             
                
                   
            • Certified VNFs should vbe           able to be onboarded to inventory in A&AI, be available for           Servcie Design in SDC, report alarms through DCAE and be configurable           through ONAP.
              •     
               
            

(Certification scope may evolve by release)

  • VNF Requirements available (Assume delivered by VNF SDK Project)
  • VNF test cases available (scope of work
  •  
    •  
    • How does this align with external standards/specifications?

OPNFV also has some VNF Cetification activities.

  • APIs/Interfaces
  • Information/data models
  • Are there dependencies with other open source projects?
  • APIs/Interfaces
  • Integration Testing
  • etc.

Resources:

  • Primary Contact Person
  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)
          
             
                
                   
            • Steve Wright                AT&T
              •      
            • Parviz Yegani               Huawei
              •      
            • Eric Debeau                 Orange
              •      
            • Stephen Gooch           Wind River
              •      
            • Andrey Kojukhov .       amdocs

            • Oleg Kaplan                amdocs
              •      
            • Trevor Cooper             Intel
              •      
            • Amie Levy                   
              •      
            • Chengli Wang              China Mobile
              •      
            • Helen Chen                
              •      
            • Gary Wu                     
              •      
            • Zygmunt Lozinski         IBM
              •      
            • Erik Sundelof               AT&T
              •      
            • Don Levy                     AT&T
              •      
            • Amy Zwarico                AT&T
              •     
               
            

Other Information:

  • link to seed code (if applicable)
  • Vendor Neutral
  • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
  • Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name:
  • JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: 


  • No labels