From 19ebb22f0d8fe8fdbaa461a487bc92b8f562938b Mon Sep 17 00:00:00 2001 From: Giacomo Bernini Date: Thu, 17 Sep 2020 18:08:07 +0200 Subject: [PATCH] updates according to NFVSOL(20)000703r1_SOL012ed331 --- src/SOL012/PolicyManagement/PolicyManagement.yaml | 11 +++++++---- src/SOL012/components/SOL012_schemas.yaml | 7 +++++-- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/src/SOL012/PolicyManagement/PolicyManagement.yaml b/src/SOL012/PolicyManagement/PolicyManagement.yaml index b43a7ab..91a70a8 100644 --- a/src/SOL012/PolicyManagement/PolicyManagement.yaml +++ b/src/SOL012/PolicyManagement/PolicyManagement.yaml @@ -582,8 +582,12 @@ components: associations: description: > Initial value of the “associations” attribute in the “Policy” data structure which represents the policy. - How the PF determines the scope of applicability of the policy when this attribute - is absent is outside the scope of the present document. + Shall be absent when the association feature is not applicable for the PF. + The associations refer to identifiers of entities that the PF manages. E.g., if the PF is a VNFM, + the policy can associate to VNF instances; if the PF is NFVO, the policy can associate to an NS instances. + How the PF determines the scope of applicability of the policy when this attribute is absent is + outside the scope of the present document. + type: array items: $ref: "../components/SOL012_schemas.yaml#/components/schemas/Identifier" @@ -635,6 +639,7 @@ components: associations: description: > Identifiers of the entities that the PF manages and to which the policy associates to. + Shall be absent when the association feature is not applicable for the PF. The associations refer to identifiers of entities that the PF manages. E.g., if the PF is a VNFM, the policy can associate to VNF instances; if the PF is NFVO, the policy can associate to an NS instances. @@ -668,7 +673,6 @@ components: - id - designer - name - - policy - activationStatus - transferStatus - _links @@ -1091,7 +1095,6 @@ components: Shall be returned when the policy content has been transferred successfully. The response body shall be empty. - Editor's note: It is FFS whether an empty payload is allowed for 201 Created response headers: WWW-Authenticate: description: > diff --git a/src/SOL012/components/SOL012_schemas.yaml b/src/SOL012/components/SOL012_schemas.yaml index 7749c15..7b37493 100644 --- a/src/SOL012/components/SOL012_schemas.yaml +++ b/src/SOL012/components/SOL012_schemas.yaml @@ -320,6 +320,7 @@ components: data structure which represents the policy. The API producer shall ignore the identifiers that already exist in the "associations" attribute in the “Policy” data structure. + Shall be absent when the association feature is not applicable for the PF. type: array items: $ref: "../components/SOL012_schemas.yaml#/components/schemas/Identifier" @@ -328,13 +329,15 @@ components: Identifiers of entities to be removed from the “associations” attribute in the “Policy” data structure which represents the policy. The API producer shall ignore the identifiers that do not exist in the "associations" - attribute in the “Policy” data structure + attribute in the “Policy” data structure. + Shall be absent when the association feature is not applicable for the PF. type: array items: $ref: "../components/SOL012_schemas.yaml#/components/schemas/Identifier" removeAllAssociations: description: > - Shall be set to TRUE if the policy is no longer associated to any specific entities managed by the PF.ù + Shall be set to TRUE if the policy is no longer associated to any specific entities managed by the PF. + Shall be absent when the association feature is not applicable for the PF. If "removeAllAssociations" is set to TRUE, neither "addAssociations" nor “removeAssociations” attributes shall be present. Once all associations have been removed, how the PF determines the scope of applicability of -- GitLab