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

Compare with Current View Page History

« Previous Version 18 Next »

The VNF Requirements Project maintains repos for  the source documentation of various deliverable:


RepoPublished forDescriptionEPIC supportedDeliverable document Title(s) 
/guidelinesExternal audienceThis includes objectives and motivations for the VNF Requirements work as well as  aspirational, forward looking, narrative text for use in prototype RFP text.VNFRQTS-6
  •  ONAP VNF Guidelines
/requirementsExternal AudienceThis is narrative text for use in prototype RFP text. VNFRQTS-6
  •  ONAP VNF Requirements
/epicsInternal AudienceFormalized requirements descriptions e.g. "As a ROLE I need SOMETHING so that SOME PURPOSE IS REALIZED"see Project Charter
/usecasesInternal audienceThis is a template structure providing a context for specific requirements. This illustrates behavior, sequences of operation, variants, error conditions, etc. There may be multiple use cases associated with a single requirement. Documents VNF specific use cases in support of ONAP E2E use cases.see Project Charter
  • Mapping VNF use cases and with E2E Release A use cases
/testcasesInternal AudienceThis expands the use case template structure to supply the additional fields necessary to describe a test scenario. There may be multiple test case descriptions associated with a single use caseVNFRQTS-8
  • ONAP VNF Requirements Test Descriptions 


VNF Guidelines Document Outline - Wenyao Guan

  1. Purpose
  2. Scope
  3. Introduction 
    1. Motivation
    2. Audience
    3. Program and Document structure
  4. VNF Context
    1. Business Process Impacts
    2. VNF View of ONAP integration
    3. Evolving towards VNFs
  5. VNF Characteristics
    1. VNF Development
    2. ONAP Ready
    3. Virtualization Environment Ready
  6. Summary
  7. Appendix
    1. Glossary
    2. References
    3. Comparison between VNF Guidelines and ETSI GS NFV-SWAxxx

VNF Requirements Document Outline - Herb Patten

  1. Purpose
  2. Scope
  3. Introduction
    1. Overview of the document, use of the requirements for
  4. VNF Development Requirements
    1. VNF Design
    2. VNF Resiliency
    3. VNF Security
    4. VNF Modularity
    5. Devops
  5. VNF Modeling Requirements
    1. TOSCA YAML
    2. HEAT
  6. Infrastructure Requirements
    1. OpenStack
    2. Azure
  7. ONAP Management Requirements
    1. Service Design
    2. VNF On-boarding and package management
    3. Configuration Management
    4. Monitoring & Management
  8. Appendix
    1. Data Record Formats

Seed Document mapping for VNF Requirements

Seed Document

Section

ONAP Document

Section

VNF Cloud Readiness Requirements for ONAP

Title, Document Revision History, Table of Contents, Definitions, 1. Introduction

N/A

N/A

VNF Cloud Readiness Requirements for ONAP

2. VNF Design

VNF Requirements

4.a VNF Design

VNF Cloud Readiness Requirements for ONAP

3. Resiliency

VNF Requirements

4.b VNF Resiliency

VNF Cloud Readiness Requirements for ONAP

4. Security

VNF Requirements

4.c VNF Security

VNF Cloud Readiness Requirements for ONAP

5. DevOps

VNF Requirements

4.e Devops

VNF Management Requirements for ONAP

Title, Document Revision History, Table of Contents, 1. Introduction

N/A

N/A

VNF Management Requirements for ONAP

2. Design Definition

VNF Requirements

7.b VNF On-boarding and package management

VNF Management Requirements for ONAP

3. Configuration Management

VNF Requirements

7.c Configuration Management

VNF Management Requirements for ONAP

4. Monitoring & Management

VNF Requirements

7.d Monitoring & Management

VNF Management Requirements for ONAP

Appendix A - Chef JSON Key Description

VNF Requirements

8.a Data Records

VNF Management Requirements for ONAP

Appendix B - Ansible JSON Key Value Description

VNF Requirements

8.a Data Records

VNF Management Requirements for ONAP

Appendix C - VNF License Information Guidelines

VNF Requirements

8.a Data Records

VNF Management Requirements for ONAP

Appendix D – Ansible Server Specification

VNF Requirements

8.a Data Records

VNF Heat Template Requirements for ONAP

Title, Document Revision History, Table of Contents, Definitions,   Introduction sections 1, 1.1, 1.2, 1.3, Appendix A Glossary, Last page –   creative common license

N/A

N/A

VNF Heat Template Requirements for ONAP

1.4 VNF Modularity

6. Design Pattern: VNF Modularity

7. Scaling Considerations

VNF Requirements

4.d VNF Modularity

VNF Heat Template Requirements for ONAP

2. General Guidelines

3. Networking

4. Parameter Naming Convention

5. Heat Template Constructs

VNF Requirements

5.b Heat


VNF Management Requirements for Open-O1. IntroductionVNF RequirementsN/A
VNF Management Requirements for Open-O2.1 VNF Develop StepsVNF Guidelines5.a VNF Development
VNF Management Requirements for Open-O2.2 VNF Rest APIVNF Requirements7.c Configuration Management
VNF Management Requirements for Open-O3.1 VNFM Driver Develop StepsVNF Guidelines5.a VNF Development
VNF Management Requirements for Open-O3.2 Create SVNFM Adaptor MircoserviceVNF Guidelines5.a VNF Development
 VNF TOSCA Template Requirements 1 Introduction VNF Requirements 5.a TOSCA YAML
  VNF TOSCA Template Requirements 4 NFV TOSCA Template  VNF Requirements  5.a TOSCA YAML


Seed Document mapping for VNF Guidelines

Seed Document

Section

ONAP Document

Section

VNF Guidelines for Network Cloud and OpenECOMP

Title, Document Revision History, Table of Contents

N/A

N/A

VNF Guidelines for Network Cloud and OpenECOMP

2. 1 Motivation

VNF Guidelines

3.a Motivation

VNF Guidelines for Network Cloud and OpenECOMP

2.2 Audience

VNF Guidelines

3.b Audience

VNF Guidelines for Network Cloud and OpenECOMP

2.3 Program and Document structure

VNF Guidelines

3.c Program and Document structure






3 VNF Context

VNF Guidelines

4 VNF Context


3.1 Business Process Impacts

VNF Guidelines

4.1 Business Process Impacts


3.2 VNF View of ONAP integration

VNF Guidelines

4.b VNF View of ONAP integration


3.3 Evolving towards VNFs

VNF Guidelines

4.c Evolving towards VNFs



VNF Guidelines




VNF Guidelines




VNF Guidelines




VNF Guidelines




VNF Guidelines



EPIC statement structure for requirements

For each requirement adopt a standardized numbering scheme, and format

Reqt #Requirement text
xxxAs a ROLE I need SOMETHING so that SOME PURPOSE IS REALIZED


Use Case Template

For each use case adopt a standardized format

  1. Title
  2. Requirement #
  3. summary
  4. Actors (VNF, Operator, ONAP Platform etc.)
  5. Preconditions
  6. Operational sequence ( e.g. Message Sequence chart + text explanations) 
  7. Post conditions

Test Case Description Template

  1. Title
  2. Requirement #
  3. Use Case #
  4. summary
  5. ONAP Actors (VNF, Operator, ONAP Platform components etc.)
  6. Preconditions ( ONAP, VNF states, test equipment/ data patterns, measurements) 
  7. Operational sequence ( e.g. Message Sequence chart + text explanations) 
  8. Post conditions (any post processing of the measurements, any cleanup of the ONAP configuration, reset of the test equipment etc.)
  9. Test Result decision ( measurement  decision criteria )
  • No labels