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

0008175

3GPP SA5 Bug Tracking

[NFV Specifications] Feature Gap

public

16-09-2022 08:38

15-12-2022 09:18

Reporter

Sujeet Banerjee

Assigned To

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0008175: [V4.3.1] [Claim 6.8.13.2] Property 'mcio_constraint_params' in Vdu.OsContainerDeployableUnit is irrelevant and CONFLICTING

Description

The valid values for 'mcio_constraint_params' as given below are irrlevant:

- affinity_nfvi_pop
- affinity_zone
- affinity_zone_group
- affinity_nfvi_node
- affinity_cis_node
- anti_affinity_nfvi_pop
- anti_affinity_zone
- anti_affinity_zone_group
- anti_affinity_nfvi_node
- anti_affinity_cis_node
- local_affinity_nfvi_pop
- local_affinity_zone
- local_affinity_zoneGroup
- local_affinity_nfvi_node
- local_affinity_cis_node
- local_anti_affinity_nfvi_pop
- local_anti_affinity_zone
- local_anti_affinity_zone_group
- local_anti_affinity_nfvi_node
- local_anti_affinity_cis_node

That is because, the placement constraints can be specified CORRECTLY using the policies: "AffinityRule" / "AntiaffinityRule" (Clause 6.10.10)

The property 'mcio_constraint_params' may be CONFLICTING because, it does not specify, say in case of affinity GROUPS (e.g. affinity_cis_node), how more than one SETs of VDUs can be placed into more than one groupings.

Additional Information

These allowed values of 'mcio_constraint_params' are irrelevant as well:
- node_additional_capability_ssd
- node_additional_capability_dpdk
- node_additional_capability_sriov
- node_additional_capability_gpu
- node_additional_capability_fpga
- node_additional_capability_cpu_pin
- node_capability_logical_numa
- node_pool

That's because, these are NOT contraints. They are indeed requirements for additional capabilities, and can be specified using other properties of Vdu.OsContainerDeployableUnit, eg. "requested_additional_capabilities" and/or "logical_node" (clause 6.8.13.2)

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: 0008133

Relationships

Notes
There are no notes attached to this issue.