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 ]
IDProjectCategoryView StatusDate SubmittedLast Update
00081683GPP SA5 Bug Tracking[NFV Specifications] Clarificationpublic15-09-2022 08:0415-12-2022 09:18
ReporterSujeet Banerjee 
Assigned Tobhyrraju 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusresolvedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0008168: "VnfIndicator" being defined in both "VNFD" and "VnfDf" information Elements; Ambiguity over referencing
DescriptionWhat is the behavior of MANO, when the same VnfIndicator information is present in both VnfDf and Vnfd Information Elements?
- Are the consumers, subscribing to the Indicator Notification, supposed to get double notifications?
- Or, is one of the VnfIndicator definitions going to have an "Overriding Effect"; say, VnfDf.vnfIndicator supersedes Vnfd.vnfIndicator (or vice-versa)?
TagsNo tags attached.
TS/TR Rapporteur
Source (company - Author)
TS number
TS version
Clause Reference(s)
Attached Files

- Relationships

-  Notes
(0016408)
Bruno Chatras (reporter)
20-09-2022 15:12

My assumption is that Vnfd.vnfIndicator contains a list of VNF indicators applicable to any DF (*) while VnfDf.vnfIndicator contains a list of VNF indicators that are specific to a DF.
(*) Perhaps this should be stated explicitly in Table 7.1.2.2-1.
(0016409)
Sujeet Banerjee (reporter)
21-09-2022 09:09

Still unanswered -
1. "what if both Vnfd and DF define with the same indicatorId and/or indicator_name?", Will one override the other?
2. What will be the response returned by the VNFM for GET '/indicators/{vnfInstanceId}/{indicatorId}'
3. Will the subscriber get multiple notifications for the same type of change?
(0016410)
Bruno Chatras (reporter)
21-09-2022 09:17

1. This does not make sense and should be forbiden. An indicator is either globally applicable all DFs or specific to a DF. Indicator names shall be unique within the scope of the VNFD.
2. I assume you mean "returned by the VNF", right? The VNF will return the information associated to the IndicatorId.
3. No
(0016411)
Sujeet Banerjee (reporter)
22-09-2022 06:26

Ok, got it.

However, under what circumstances would a VNF-vendor need to define an indicator specific to a DF, given the same could be done through VNF-specific indicator anyways? IFA007 and IFA008 do not distinguish whether a vnfIndicator is specific to a DF or a VNF (afterall, the subscription request filter takes an indicator-Id). Am I missing any usecase?
(0016412)
Bruno Chatras (reporter)
23-09-2022 10:44

Let's take as an example a VNF that has 3 VNFCs (A,B and C) and 2 DFs.
- DF1 (Basic functionality): with VNFC A & B
- DF2 (Extended Functionality): with VNFC A,B & C
VNF indicators sent by VNFC A & B are applicable to all DFs while VNF indicators sent from VNFC C are specific to DF-2.
(0016413)
bhyrraju (reporter)
26-10-2022 11:49

Checked tables Table 7.1.2.2-1 (VNFD). As Bruno indicated, the vnfIndicator in the table is applicable at VNFD level (default for any Deployment flavours).
The description says "Declares the VNF indicators that are supported by this VNF".

If there are specific requirements for a Deployment Flavour, they are represented in "deploymentFlavour" attribute (Content VnfDf) in the VNFD (Table 7.1.2.2-1).
In this case, a new set of vnfIndicators can be defined specific to that deployment flavour. Refer to Table 7.1.8.2.2-1, these are the indicators specific to the deployment flavour.
The description in this table says "Declares the VNF indicators that are supported by this VNF (specific to this DF)".

- Issue History
Date Modified Username Field Change
15-12-2022 09:18 Sujeet Banerjee New Issue
15-12-2022 09:18 Sujeet Banerjee Issue generated from: 0008121


MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker