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

Compare with Current View Page History

« Previous Version 18 Next »

Based on timeplan of modeling subcommittee, high level requirements need to be finished by M0/M1, 

There are 4 categories of high level requirement,

  • 1) Will be implemented and included in the release 4
  • 2) Documentation after implemented, or implemented but not in the release
  • 3) Lower Priority
  • 4) Experimental

The first category is that those requirement will be implemented and commited by the impacted projects in this release

the second category will document the current implementation in those projects.

Other two categories like lower priority and experimental will not be included in the release 3, the contributor will work with best effort to influence future release.

Owners of each requirement needs to coordinate the modeling spec commitment and code commitment with PTLs of impacted project.


1) Will be implemented and included in the release 4


Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

Mapping to M1 requirementOwner
Resource and Service DMTOSCA 1.2ONAP onboarding data model (TOSCA) and internal data model should be based on OASIS TOSCA 1.2 core syntax and normative typesSDC, SO, VFC
??



Resource DM

ETSI NFV SOL001 v2.5.1

VNFD - the ONAP internal data model should be able to reflect ETSI SOL001 VNFDs provided for onboarding

SDC, VFC

CCVPN

 user-7acab




 user-7acab

Resource DM

ETSI NFV
SOL001
v2.5.1

PNFD - the ONAP internal data model (AID)should be able to reflect ETSI SOL001 PNFDs provided for onboarding.

(committed goal)

''''''''''''''''

Could an Onboarded PNFD also be internally mapped to the second ONAP internal model (nfv tosca types) ?

Could two internal descriptors coexist in the same internal SDC package  ?

(stretch goal)


SDC


Ericsson

Fei Zhang

Michela Bevilacqua


Ericsson.

Part of 5G UC Onboarding UC in Dublin.

SDC-1976



Michela Bevilacqua

Resource IMETSI NFV IFA011 v2.5.1Update the VNFD IM to align with IFA011 v2.5.1SDC, VFC

Jessie S Jewitt

N/A

related to DM SOL001 progress



Jessie S Jewitt

Resource IMPNFDCreate onboarding PNFD IMSDC, SO, VFC

Jessie S Jewitt

Benjamin Cheung

N/A

Jessie S Jewitt

Resource IMVNFD

New requirement for the VNFD

Chuyi Guo Xu Yang - can you please elaborate?

SDC, VFCVoLTE

Chuyi Guo

N/A

impact R4 DM?



Chuyi Guo

Service DMETSI NFV SOL001 v2.5.1

 NSD - the ONAP internal data model should be able to reflect ETSI SOL001 NSD provided for onboarding

SDC, SO, VFC

CCVPN

Thinh Nguyenphu




Thinh Nguyenphu

Service IMETSI NFV IFA014 v2.5.1Nested Service SDC, SO, VFC CCVPN 

Chuyi Guo
Kevin Scaggs  

 TBA High  Chuyi Guo


2) Documentation after implemented, or implemented but not in the release

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

Mapping to M1 requirement Owner

 Service

 


Internal Service IM


To document the internal Service IM as implemented by SDC and SO to support the usecase


N/A


CCVPN


Chuyi Guo
Kevin Scaggs


N/A


High



Chuyi Guo

 Onboarding NS IM

To document the onboarding NS IM as supported by the usecase


N/A


CCVPN


Chuyi Guo
user-7acab


N/A


HighHigh



user-7acab
Resource allotted resource

To document the allotted resource IM as implemented by SDC

N/A


Kevin Scaggs

N/A 

Kevin Scaggs 

 






 


 












Below tables are not downgrade, but casablanca won't make it

3) Lower Priority:

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

 Owner

Service



 







  






Common

 

Policy

create policy IM, reflect current policy project implementation

Policy


Kevin Scaggs

N/A


Kevin Scaggs

VEScreate VES IMDCAE


Kevin Scaggs

N/A


Kevin Scaggs

Infrastructure


















4) Experimental:

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

 Owner

Common

License

create license IM


Kevin Scaggs



Kevin Scaggs

Root

create super classes for current models

SDC, AAI

Kevin Scaggs

Chesla Wechsler



Kevin Scaggs



Per discussion in Paris, requirements can be based on:

  • Release / project specific needs
  • Recognized 'future' needs
  •  Documenting existing models

Some concepts may be complex enough, if we wait for the release / project requirement, we will be too late to properly develop the concept.


the committee agreed

1) Thinh Nguyenphu will lead 1st task force working on #1,#2 recommendations:

Recommend#1: member companies prepare and submit these additional extension to ETSI NFV IFA and SOL WG toward v2.6.1 or later. (agreed) Recommend#2: ONAP adopts SOL001 Type extension method, per clause 5.6 (agreed)

2) user-7acab Weitao Gao will lead 2nd task  working on $4 recommendation:

Recommend #4: SDC supports SOL001 v2.5.1 type definitions (VNFD, PNFD, NSD) (agreed)

3) Thinh Nguyenphu will report NSD comparision with service csar in 2 weeks, 

All 3 work will be reported to Anatoly weekly DM conference call, Anatoly will ask final approval from Modeling subcommittee 


Following are a few development areas to consider. 

  1. Resource
    1. PNF
    2. Allotted (Contribution Posted)
    3. Network Function (perhaps related to rooting descriptors and instances below)
    4. Network Slicing
    5. Pnf
  2. Service
    1. Network Service 
    2. Service Instance (Runtime)
    3. CFS reconcile (BBS Use Case)
  3. Infrastructure
    1. Multi-VIM/Clouid
    2. Cloud Region
  4. Common
    1. VES (Some Material Posted)
    2. License 
    3. Rooting Descriptors and Instances
    4. Policy
  5. Other
    1. Onboarding and Runtime Model Classes 
    2. Scaling
    3. Configuration
    4. Further HPA Modeling
  • No labels