Versions Compared

Version Old Version 9 New Version 10
Changes made by

Sandeep Shah

Erik Sundelof

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Project Name:          ICE *(Incubation & Certification Environment) ONAP ICE  

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

Project description:

The project is to develop a certification validation 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 any other validation authority.

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

The overall objective of the proposal is to build & foster an active community at ONAP contributing to all aspects of an ONAP VNF Validation 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.

It will be important as part of these deliverables to define ways for 3rd parties to carry out the validation to allow for an efficient and broad adaption. The developed processes and tools will be available for any use within the scope of the Apache 2.0 license and all changes to them must be contributed back the ONAP community.

Exploring possible expansions to the validation scope is an essential part of this project and especially looking to define specific steps to do so. Some immediate candidates would be to validate the integration with DCAE and/or A&AI as well introducing validation of TOSCA templates. This work by its very nature will need to be closely linked to the work with the ONAP VNF Requirements and Guidelines.

Key related projects and components are the Open-O VNF SDK and the ONAP SDC component who both will play important roles into defining the long-term direction for the program. 


The project is intended to validate the following:

...

  • 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:

...

The scope for this project is to establish an ONAP VNF Validation Program by the end of 2017 allowing anyone to obtain an ONAP Compatible label for their VNFs. The key deliverables currently identified for this project to be completed by the end of 2017 are:

  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

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

...

Resources:

  • Primary Contact Person: Erik Sundelof es4410@att.com
  • Names, gerrit IDs, and company affiliations of the committers
    • Erik Sundelof, AT&T
    • Steven Wright, AT&T
    • Sandeep Shah, Tech Mahindra
    • Wenyao Guan, China Mobile
  • 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                Huawei
    •      
  • Gary Wu                     Huawei
    •      
  • Zygmunt Lozinski         IBM
    •      
  • Erik Sundelof               AT&T
    •      
  • Don Levy                     AT&T
    •      Amy Zwarico               
    • 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, Huawei
    • Gary Wu, Huawei
    • Zygmunt Lozinski, IBM
    • Don Levy, AT&T
    • Amy Zwarico, AT&T
    • Maopeng Zhang
    •         ZTE
  • Wenyao Guan              China Mobile
  • Sandeep Shah           Tech Mahindra
    •          
    • , ZTE
  • Project Roles (include RACI chart, if applicable)

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)

...