Loading src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml +11 −18 Original line number Diff line number Diff line Loading @@ -290,7 +290,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. The following attribute names shall be supported by the VNFM in the attribute based filtering Loading @@ -306,7 +306,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the FmSubscription and in data types Loading Loading @@ -707,22 +707,15 @@ components: description: | 422 Unprocessable Content Shall be returned upon the following error: The content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the VNFM has tested the Notification endpoint as described in clause 7.4.6.3.2 and the test has failed. In this case, the "detail" attribute in the "ProblemDetails" structure shall convey more information about the error Shall be returned upon the following error: The content type of the message content is supportedand the message content of a request contains syntactically correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the VNFM has tested the Notification endpoint as described in clause 7.4.6.3.2 and the test has failed. In this case, the "detail" attribute in the "ProblemDetails" structure shall convey more information about the error. headers: Version: description: The used API version. Loading src/SOL003/VNFFaultManagement/definitions/SOL003VNFFaultManagement_def.yaml +1 −1 Original line number Diff line number Diff line Loading @@ -18,7 +18,7 @@ definitions: apply for the values of the attribute "faultDetails" related to changes in the state of virtualised resources: - One of the entries in the array shall provide information about the anticipated time of maintenance in the following format: "anticipatedTime=$time", wherein "$time" shall be formatted as a "DateTime", as specified in ETSI GS NFV-SOL 013 [8]. in ETSI GS NFV-SOL 013. - One of the entries in the array shall provide identification information about the affinity/anti-affinity group defined in the VNFD that is associated to the affected virtualised resource indicated by "rootCauseFaultyResource" in the following format: "affinityOrAntiAffinityGroupId=$group", wherein Loading src/SOL003/VNFIndicator/VNFIndicator.yaml +3 −3 Original line number Diff line number Diff line Loading @@ -296,7 +296,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfIndicator data type and in data types Loading @@ -310,7 +310,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfIndicator data type and in data types Loading @@ -324,7 +324,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfIndicatorSubscription data type and in Loading src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml +21 −21 Original line number Diff line number Diff line Loading @@ -1277,7 +1277,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfInstance and in data types referenced from it Loading @@ -1292,7 +1292,7 @@ components: in: query description: >- Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [8] for details. The VNFM shall support this parameter. of ETSI GS NFV-SOL 013 for details. The VNFM shall support this parameter. The following attributes shall be excluded from the VnfInstance structure in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided: Loading @@ -1309,7 +1309,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfLcmOpOcc and in data types Loading @@ -1324,7 +1324,7 @@ components: in: query description: >- Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [8] for details. The VNFM shall support clause 5.3 of ETSI GS NFV-SOL 013 for details. The VNFM shall support this parameter. The following attributes shall be excluded from the VnfLcmOpOcc structure in the response body if this parameter is provided, or none of the parameters Loading @@ -1345,7 +1345,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the LccnSubscription and in data types Loading @@ -1359,7 +1359,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfSnapshot and in data types Loading @@ -1374,7 +1374,7 @@ components: in: query description: >- Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [8] for details. The VNFM shall See clause 5.3 of ETSI GS NFV-SOL 013 for details. The VNFM shall support this parameter. The following attributes shall be excluded from the VnfSnapshot structure in the response body if this parameter is provided, or none of the Loading Loading @@ -1668,7 +1668,7 @@ components: content of a request contains syntactically correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the VNF package Loading Loading @@ -2140,7 +2140,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading Loading @@ -2263,7 +2263,7 @@ components: exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading Loading @@ -2385,7 +2385,7 @@ components: exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading Loading @@ -2583,7 +2583,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading Loading @@ -2706,7 +2706,7 @@ components: one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the Loading Loading @@ -3054,7 +3054,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task is not Loading Loading @@ -3165,7 +3165,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task is not Loading Loading @@ -3289,7 +3289,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the Loading Loading @@ -3402,7 +3402,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the Loading Loading @@ -3576,7 +3576,7 @@ components: Shall be returned upon the following error: The content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the presence of the response body. GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the VNFM has tested the Notification endpoint as described in clause 5.4.20.3.2 and the test has failed. In this case, the "detail" attribute in the "ProblemDetails" structure shall convey more Loading Loading @@ -3760,7 +3760,7 @@ components: SShall be returned upon the following error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the presence of the response body. GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist. Loading Loading @@ -3844,7 +3844,7 @@ components: correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the provided Loading Loading @@ -3923,7 +3923,7 @@ components: exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +3 −3 Original line number Diff line number Diff line Loading @@ -698,7 +698,7 @@ components: filter_vnf_packages: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013. The NFVO shall support receiving this parameter as part of the URI query string. The VNFM may supply this parameter. All attribute names that appear in the VnfPkgInfo and in data types referenced from it Loading @@ -713,7 +713,7 @@ components: in: query description: >- Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [8] for details. of ETSI GS NFV-SOL 013 for details. The NFVO shall support this parameter. The following attributes shall be excluded from the VnfPkgInfo structure in the response body if this parameter is provided, or none of the parameters "all_fields," "fields", Loading Loading @@ -813,7 +813,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The NFVO shall support receiving this parameter as part of the URI query string. The VNFM may supply this parameter. All attribute names that appear in the PkgmSubscription and in data types Loading Loading
src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml +11 −18 Original line number Diff line number Diff line Loading @@ -290,7 +290,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. The following attribute names shall be supported by the VNFM in the attribute based filtering Loading @@ -306,7 +306,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the FmSubscription and in data types Loading Loading @@ -707,22 +707,15 @@ components: description: | 422 Unprocessable Content Shall be returned upon the following error: The content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the VNFM has tested the Notification endpoint as described in clause 7.4.6.3.2 and the test has failed. In this case, the "detail" attribute in the "ProblemDetails" structure shall convey more information about the error Shall be returned upon the following error: The content type of the message content is supportedand the message content of a request contains syntactically correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the VNFM has tested the Notification endpoint as described in clause 7.4.6.3.2 and the test has failed. In this case, the "detail" attribute in the "ProblemDetails" structure shall convey more information about the error. headers: Version: description: The used API version. Loading
src/SOL003/VNFFaultManagement/definitions/SOL003VNFFaultManagement_def.yaml +1 −1 Original line number Diff line number Diff line Loading @@ -18,7 +18,7 @@ definitions: apply for the values of the attribute "faultDetails" related to changes in the state of virtualised resources: - One of the entries in the array shall provide information about the anticipated time of maintenance in the following format: "anticipatedTime=$time", wherein "$time" shall be formatted as a "DateTime", as specified in ETSI GS NFV-SOL 013 [8]. in ETSI GS NFV-SOL 013. - One of the entries in the array shall provide identification information about the affinity/anti-affinity group defined in the VNFD that is associated to the affected virtualised resource indicated by "rootCauseFaultyResource" in the following format: "affinityOrAntiAffinityGroupId=$group", wherein Loading
src/SOL003/VNFIndicator/VNFIndicator.yaml +3 −3 Original line number Diff line number Diff line Loading @@ -296,7 +296,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfIndicator data type and in data types Loading @@ -310,7 +310,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfIndicator data type and in data types Loading @@ -324,7 +324,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfIndicatorSubscription data type and in Loading
src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml +21 −21 Original line number Diff line number Diff line Loading @@ -1277,7 +1277,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfInstance and in data types referenced from it Loading @@ -1292,7 +1292,7 @@ components: in: query description: >- Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [8] for details. The VNFM shall support this parameter. of ETSI GS NFV-SOL 013 for details. The VNFM shall support this parameter. The following attributes shall be excluded from the VnfInstance structure in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided: Loading @@ -1309,7 +1309,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfLcmOpOcc and in data types Loading @@ -1324,7 +1324,7 @@ components: in: query description: >- Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [8] for details. The VNFM shall support clause 5.3 of ETSI GS NFV-SOL 013 for details. The VNFM shall support this parameter. The following attributes shall be excluded from the VnfLcmOpOcc structure in the response body if this parameter is provided, or none of the parameters Loading @@ -1345,7 +1345,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the LccnSubscription and in data types Loading @@ -1359,7 +1359,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The VNFM shall support receiving this parameter as part of the URI query string. The NFVO may supply this parameter. All attribute names that appear in the VnfSnapshot and in data types Loading @@ -1374,7 +1374,7 @@ components: in: query description: >- Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [8] for details. The VNFM shall See clause 5.3 of ETSI GS NFV-SOL 013 for details. The VNFM shall support this parameter. The following attributes shall be excluded from the VnfSnapshot structure in the response body if this parameter is provided, or none of the Loading Loading @@ -1668,7 +1668,7 @@ components: content of a request contains syntactically correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the VNF package Loading Loading @@ -2140,7 +2140,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading Loading @@ -2263,7 +2263,7 @@ components: exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading Loading @@ -2385,7 +2385,7 @@ components: exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading Loading @@ -2583,7 +2583,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading Loading @@ -2706,7 +2706,7 @@ components: one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the Loading Loading @@ -3054,7 +3054,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task is not Loading Loading @@ -3165,7 +3165,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task is not Loading Loading @@ -3289,7 +3289,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the Loading Loading @@ -3402,7 +3402,7 @@ components: target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], specified in clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the Loading Loading @@ -3576,7 +3576,7 @@ components: Shall be returned upon the following error: The content type of the message content is supported and the message content of a request contains syntactically correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the presence of the response body. GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the VNFM has tested the Notification endpoint as described in clause 5.4.20.3.2 and the test has failed. In this case, the "detail" attribute in the "ProblemDetails" structure shall convey more Loading Loading @@ -3760,7 +3760,7 @@ components: SShall be returned upon the following error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the presence of the response body. GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist. Loading Loading @@ -3844,7 +3844,7 @@ components: correct data but the data cannot be processed. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this resource, the response code 422 shall also be returned if the provided Loading Loading @@ -3923,7 +3923,7 @@ components: exists. The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [8], including rules for the GS NFV-SOL 013, including rules for the presence of the response body. Specifically in case of this task resource, the response code 404 shall also be returned if the task Loading
src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml +3 −3 Original line number Diff line number Diff line Loading @@ -698,7 +698,7 @@ components: filter_vnf_packages: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013. The NFVO shall support receiving this parameter as part of the URI query string. The VNFM may supply this parameter. All attribute names that appear in the VnfPkgInfo and in data types referenced from it Loading @@ -713,7 +713,7 @@ components: in: query description: >- Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [8] for details. of ETSI GS NFV-SOL 013 for details. The NFVO shall support this parameter. The following attributes shall be excluded from the VnfPkgInfo structure in the response body if this parameter is provided, or none of the parameters "all_fields," "fields", Loading Loading @@ -813,7 +813,7 @@ components: name: filter description: > Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [8]. GS NFV-SOL 013. The NFVO shall support receiving this parameter as part of the URI query string. The VNFM may supply this parameter. All attribute names that appear in the PkgmSubscription and in data types Loading
