Hello,

After reviewing https://wiki.onap.org/display/DW/NetworkService, I still have 
many issues with network service IM model. The following are my comments:

Figure ONAP R2 (Simplification for implication)
[image2018-3-13_20-44-5.png]
[Thinh] Some of key network service class such as VlProfile, SAP 
(nsVirtualLink, VnfExtCp), Pnf descriptor, NsInstantiantionLevel, 
NsVirtualLinkConnectivity are missing in the above figure.


Example:
[https://wiki.onap.org/download/thumbnails/25436905/image2018-3-13_22-21-41.png?version=1&modificationDate=1521600187000&api=v2]
[Thinh] SAP and PNF are missing in the above figure.
Class:NSD


pnfdId

M

0..N

String

References the PNFD of a constituent PNF.

SDC

SDC/UUI/VFC

pnfdId

R3+

[Thinh] pnfdId should be part of R2

sapd

M

0..N

Sapd

Provides the descriptor of a service access point of the network service.

SDC

SDC/UUI/VFC

sapd

R3+


[Thinh] Sapd should be part of R2

lifeCycleManagementScript

M

0..N

LifeCycleManagementScript

Provides a life cycle management script written in a Domain Specific Language 
(DSL).

SDC

SDC/UUI/VFC

lifeCycleManagementScript

[Thinh] Should it be for further study (FFS) or what is blank means on the last 
column?


nsDf

M

1..N

NsDf

Identifies a DF within the scope of an NSD.

SDC

SDC/UUI/VFC

nsDf

R3+

[Thinh] R2 supports single network service deployment. NsDF includes many 
sub-class that is required for single deployment such as NsInstantiantionLevel, 
PnfProfile, VnfProfile,AffinityorAntiAffinityGroup, etc.  Thus, at least 
minimum, NsInstantiantionLevel should be supported in R2.

Class:NsVirtualLink

vitualLinkDescProvider

String

0..1

Defines the organization generating the VLD.

support:
Option

SDC

SDC/UUI/VFC

vitualLinkDescProvider

R3+

[Thinh] vitualLinkDescProvider should be part of R2

virtualLinkDf

VirtualLinkDf<https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version#DesignTimeModelCleanVersion-Class:VirtualLinkDescFlavour>

1..N


The VirtualLinkDf information element specifies properties for instantiating a 
VL according to a specific flavour.

support: MANDATORY

SDC

SDC/UUI/VFC

virtualLinkDf

R3+

[Thinh] virtualLinkDf should be part of R2

Class: ConnectivityType, Class: VirtualLinkDf, Class: QoS

[Thinh] Why Class: ConnectivityType, Class: VirtualLinkDf, and Class: QoS are 
listed on this wiki page where the table was marked as R3+ ? Also, these 
classes are incomplete.
Class:OpenstackNetwork

[Thinh] Class:OpenstackNetwork: What is the use case and purpose of having 
specific Class:OpenstackNetwork? This is implementation specific and tie up to 
specific target model.  There should a flexible model support different uses 
cases, such as two networks or multiple data center connectivities, see 
https://wiki.onap.org/display/DW/Network+Service+Virtual+Link

Regards,
Thinh

From: [email protected] 
[mailto:[email protected]] On Behalf Of denghui (L)
Sent: Tuesday, March 27, 2018 3:50 PM
To: [email protected]
Subject: [onap-discuss] [modeling] Last call for ONAP NS IM

Hello modelers,

According to last Sunday discussions, it seems that NS IM become more stable, 
here is one week call for ONAP NS IM.
https://wiki.onap.org/display/DW/NetworkService

After this call, this version will move into the clean version.

Thanks a lot

DENG Hui
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to