Versions Compared

Old Version 4

changes.mady.by.user Steven Wright

Saved on

compared with

New Version Current

changes.mady.by.user Marge Hillis

Saved on

Key

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

...

  • 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 …)

...

    • What other ONAP projects does this project depend on?
    • 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  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)

...

  • Primary      Contact Person                Steven Wright (AT&T) sw3588@att.com
  • Names,      gerrit IDs, and company affiliations of the committers
  • Names      and affiliations of any other contributors
    • Ryan Hallahan    Hallahan          rh173x@att.com                                            (AT&T)
    • Scott Blandford         cb1694@att.com                                           (AT&T)Herb Patten       hp1256@att.com
    •             Fari Behi                   fb2634@att.com                             (AT&T)
    • Fari Behi               fb2634@att.com              (AT&T)
    • Alan Weinstock aw2574@att.com             (AT&T)

...


  • Project      Roles (include RACI chart, if applicable)

 Image Added



Other Information:

...

Project Name:

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

Repo name:                      

...

      ( all under https://gerrit.onap.org)                

  • vnfrqts/guidelines
  • org.onap.vnfrqts/requirementsorg.onap.
  • vnfrqts/epics
  • org.onap.vnfrqts/usecasesorg.onap.
  • vnfrqts/testcases

...

 



Lifecycle State:                 incubationTSC 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)

Andrei Kojukhov andreik@amdocs.com (Amdocs)

*Link to TSC approval: 

Link to approval of additional submitters: