ONAP R4 Modeling High Level Requirements

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	Owner
Resource and Service	TOSCA 1.2	ONAP onboarding data model (TOSCA) and internal data model should be based on OASIS TOSCA 1.2 core syntax and normative types	SDC, SO, VFC	??	??
Resource	ETSI NFV SOL001 v2.5.1	VNFD	SDC, VFC	CCVPN	Former user (Deleted)			Former user (Deleted)
Resource	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 (Ericsson) Michela Bevilacqua			Michela Bevilacqua
Resource	ETSI NFV IFA011 v2.5.1	Update the VNFD IM to align with IFA011 v2.5.1	SDC, VFC		Former user (Deleted)	N/A related to DM SOL001 progress		Former user (Deleted)
Resource	PNFD	Create onboarding PNFD IM	SDC, SO, VFC		Former user (Deleted) Benjamin Cheung	N/A		Former user (Deleted)
Resource	VNFD	New requirement for the VNFD	SDC, VFC	VoLTE	guochuyi	N/A impact R4 DM?		guochuyi
Service	ETSI NFV SOL001 v2.5.1	NSD	SDC, SO, VFC	CCVPN	Thinh Nguyenphu (Unlicensed)			Thinh Nguyenphu (Unlicensed)
Service		Nested Service	SDC, SO, VFC	CCVPN	guochuyi Kevin Scaggs	TBA	High	guochuyi

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	Owner
Service	Internal Service IM	To document the internal Service IM as implemented by SDC and SO to support the usecase	N/A	CCVPN	guochuyi Kevin Scaggs	N/A	High	guochuyi
Service	Onboarding NS IM	To document the onboarding NS IM as supported by the usecase	N/A	CCVPN	guochuyi Former user (Deleted)	N/A	HighHigh	Former user (Deleted)
Resource	allotted resource	To document the allotted resource IM as implemented by SDC	N/A		Kevin Scaggs	N/A		Kevin Scaggs
Resource

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

3) Lower Priority:

Modeling Domain	Modeling Requirement	Modeling Requirement Description	Impacted Projects	Modeling Spec Commitment	Code Commitment	Owner
Service
Service
Common	Policy	create policy IM, reflect current policy project implementation	Policy	Kevin Scaggs	N/A	Kevin Scaggs
Common	VES	create VES IM	DCAE	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

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 (Unlicensed) 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) Former user (Deleted) victor 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 (Unlicensed) 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.

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