Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 29 Next »

Project Name:

  • Proposed      name for the project: VNF Requirements
  • Proposed      name for the repository: vnfrqts

Project description:

  • Create and maintain VNF Requirements targeted to ONAP user audiences and the tasks they perform. For example:
    • a  VNF Provider (developer) using VNF Requirements in designing, testing, and certifying a VNF for use on ONAP
    • a Service Provider using VNF Requirements as prototype text for RFPs to acquire VNFs to run in an ONAP context
  • This project will build an ecosystem for ONAP compatible VNFs by publishing guidelines and requirements:
    • For  VNF vendors across the VNF lifecycle
      • For the VNF Packages at acquisition time
      • For the VNF validation and testing tools at onboarding time 
      • For the VNF functionality common to all VNFs at Service Design time
      • For the VNF functionality common to all VNFs during Service Operation.
      • Including VNF functionality considering vendor VNF CI/CD tool chains
      • Including VNF functionality considering in service ONAP and network cloud CI/CD tool chains
      • Including requirements and processes considering VNF validation and testing tools and processes
    • For service providers to use as prototype text  for RFPs  such that
      • the  guidelines and requirement are individually numbered for tracking purposes e.g.   
        • to assess the degree of compliance by a VNF
        • to assess the degree of compliance in VNF onboarding testing & validation programs
  • This project will develop the VNF test cases and procedures  for use in the VNF validation program

 

Scope:

  • This project will deliver a unified set of VNF Guidelines and Requirements.
    • The VNF Guidelines and Requirements must be  versioned to enable evolution based on operational experience
    • The VNF Guidelines and Requirements will support the ONAP Architecture Principles.
  • Identify a list of features and functionality will be developed.
    • The VNF Guidelines and Requirements will support the Release 1 Use Cases.
      • Use cases focused on VNF Requirements may be developed in this project, and they will need to be aligned with the ETE Platform use cases.  
    • It will be incorporating and integrating the source material on VNF Guidelines and Requirements from OPEN-O and ECOMP in Release 1 
    • VNF Guidelines and Requirements  are to be refined beyond prototype text  (e.g. through EPIC statements, use cases)  to deliver test cases and test procedures for us in VNF onboarding & validation. VNF Requirement level use cases to be aligned with ETE platform use cases
  • Identify what is in or out of scope. During the development phase, it helps reduce discussion.
    • VNF Guidelines may be forward looking, or include best practices in VNF design and VNF lifecycle processes.
    • VNF Requirements from ONAP APIs should be linked to the ONAP Release
    • VNF  Requirements may include: 
      • expected  operational characteristics ( e.g. security, resilience, upgradeability) 
      • conditional  requirements (e.g. When configured for deployment on High Availability Network Cloud Infrastructure, the VNF Shall …)

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?
        •   
      • SDN-C          (for API requirements on VNFs)  
      • APPC            (for VNF configuration  requirements) 
      • VF-C             (for  VNF life cycle managment and configuration)
      • Service Design & Creation               (for VNF onboarding)  
      • DCAE            (for VNF reporting requirements)
      • Authentication and authorization Framework (for VNF Security Requirements)
      • Modeling        (for Tosca Data Modeling for VNF)
    • What   other projects depend on this project? 
      • VNF SDK   
        • VNF  tooling should support the development and packaging of VNFs that are  conformant to the VNF Requirements  
      • VNF Validation program (ICE)   
        • VNF  Validation  should be traceable  against the VNF Requirements   
      • Documentation   
        • References   to deliverables produced by this project may be included in various ONAP release documents maintained through the  documentation project
      • Reference  VNFs (now Integration  Project)
        • Reference  VNFs should be VNF Requirement compliant. The Integration Project  maintaining those Reference VNFS would be dependent on the VNF Requirements for validating compliance.
  • How does this align with external standards/specifications?
    • External       specifications of APIs/Interfaces or Information/data models to be       referenced where applicable
  • Are there dependencies with other open source projects?
    • OPEN-O (Mercury release)
    • OpenECOMP
    • OpenStack  (Network Cloud Infrastructure Requirements)


Resources:


  • Project      Roles (include RACI chart, if applicable)



Other Information:

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

Key Project Facts

Project Name:

  • JIRA      project name: VNF Requirements
  • JIRA      project prefix: vnfrqts

Repo name:                      

  • vnfrqts/guidelines
  • vnfrqts/requirements
  • vnfrqts/epics
  • vnfrqts/usecases
  • vnfrqts/testcases



Lifecycle State:                 TSC approval June 9th, 2017.
Primary Contact:              Steven Wright (AT&T) sw3588@att.com
Project Lead:                     Steven Wright (AT&T) sw3588@att.com 

(confirmed by email June 21st, 2017)


mailing list tag                  [vnfrqts]             
Committers:                     

Steven Wright (AT&T) sw3588@att.com (AT&T)

Wenyao Guan guanwenyao@chinamobile.com (China Mobile)

Yuanxing   Feng feng.yuanxing@zte.com.cn (ZTE)

*Link to TSC approval: 

Link to approval of additional submitters: 

  • No labels