Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0008218

SOL001 - TOSCA-based NFV descriptors spec

[NFV Specifications] Bug

public

21-11-2023 11:39

Reporter

Sujeet Banerjee

Assigned To

Priority

normal

Status

new

Resolution

open

Product Version

Target Version

Fixed in Version

Summary

0008218: [R4.3.1][R4.4.1] Clause 6.7.1.2 "Definition" of tosca.interfaces.nfv.Vnflcm does not define "Implementation"

Description

There are two conflicting clauses:

Clause 6.7.1.3: "Additional Requirements" which states:
---
"The 'implementation' and 'inputs' keynames specified in TOSCA-Simple-Profile-YAML-v1.3 [20] for an operation definition may be included for each operation listed in the Vnflcm interface definition."
---

BUT, the referred clause 6.7.1.2 "Definition", which provides the VnfLCM Interface definition, there is no attribute or property "implementation" defined. There is no TOSCA type defined for a bunch of keys with the VNF LCM Interface definition:
  "implementation": Type??
  "operations": Type??
  "notifications": Type??
  each operation: What is the base Type??

Additional Information

Further, it's not clear whether the key "implementation" is the parent of "inputs" or is a peer, as given in an example in clause 6.7.1.5 "Examples":

----
node_templates:
SunshineDB:
type: MyCompany.SunshineDB.1_0.1_0
..
interfaces:
  Vnflcm:
    operations:
      instantiate:
        implementation: instantiate-script
          inputs:
            script_input_1: value_1
            script_input_2: value_2
----

Issue History
Date Modified	Username	Field	Change
21-11-2023 11:39	Sujeet Banerjee	New Issue

Relationships

Notes
There are no notes attached to this issue.