diff options
Diffstat (limited to 'aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml')
-rw-r--r-- | aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml | 26365 |
1 files changed, 23425 insertions, 2940 deletions
diff --git a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml index b5d83e21..aaa008d4 100644 --- a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml +++ b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml @@ -1,28 +1,9 @@ -# -# ============LICENSE_START======================================================= -# org.onap.aai -# ================================================================================ -# Copyright © 2017 AT&T Intellectual Property. All rights reserved. -# ================================================================================ -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. -# ============LICENSE_END========================================================= -# -# ECOMP is a trademark and service mark of AT&T Intellectual Property. -# - swagger: "2.0" info: description: | + + [Differences versus the previous schema version](apidocs/aai_swagger_v10.diff) + Copyright © 2017 AT&T Intellectual Property. All rights reserved. Licensed under the Creative Commons License, Attribution 4.0 Intl. (the "License"); you may not use this documentation except in compliance with the License. @@ -71,19 +52,22 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: target-pe in: path description: The Target provider edge router required: true type: string + example: __TARGET-PE__ - name: availability-zone-name in: path description: Name of the availability zone required: true type: string + example: __AVAILABILITY-ZONE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json) required: true schema: $ref: "#/definitions/relationship" @@ -108,16 +92,19 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: target-pe in: path description: The Target provider edge router required: true type: string + example: __TARGET-PE__ - name: availability-zone-name in: path description: Name of the availability zone required: true type: string + example: __AVAILABILITY-ZONE-NAME__ /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}: get: tags: @@ -132,7 +119,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/ctag-pool" + $ref: "#/getDefinitions/ctag-pool" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -141,16 +128,19 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: target-pe in: path description: The Target provider edge router required: true type: string + example: __TARGET-PE__ - name: availability-zone-name in: path description: Name of the availability zone required: true type: string + example: __AVAILABILITY-ZONE-NAME__ - name: data-center-code in: query description: Data center code which can be an alternate way to identify a complex @@ -170,7 +160,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing ctag-pool - description: create or update an existing ctag-pool + description: | + Create or update an existing ctag-pool. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool consumes: - application/json @@ -187,22 +180,76 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: target-pe in: path description: The Target provider edge router required: true type: string + example: __TARGET-PE__ - name: availability-zone-name in: path description: Name of the availability zone required: true type: string + example: __AVAILABILITY-ZONE-NAME__ - name: body in: body - description: ctag-pool object that needs to be created or updated + description: ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json) required: true schema: $ref: "#/definitions/ctag-pool" + patch: + tags: + - CloudInfrastructure + summary: update an existing ctag-pool + description: | + Update an existing ctag-pool + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: physical-location-id + in: path + description: Unique identifier for physical location, e.g., CLLI + required: true + type: string + example: __PHYSICAL-LOCATION-ID__ + - name: target-pe + in: path + description: The Target provider edge router + required: true + type: string + example: __TARGET-PE__ + - name: availability-zone-name + in: path + description: Name of the availability zone + required: true + type: string + example: __AVAILABILITY-ZONE-NAME__ + - name: body + in: body + description: ctag-pool object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/ctag-pool" delete: tags: - CloudInfrastructure @@ -224,16 +271,19 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: target-pe in: path description: The Target provider edge router required: true type: string + example: __TARGET-PE__ - name: availability-zone-name in: path description: Name of the availability zone required: true type: string + example: __AVAILABILITY-ZONE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -253,7 +303,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/ctag-pools" + $ref: "#/getDefinitions/ctag-pools" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -262,6 +312,7 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: data-center-code in: query description: Data center code which can be an alternate way to identify a complex @@ -298,9 +349,10 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplex.json) required: true schema: $ref: "#/definitions/relationship" @@ -325,6 +377,7 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ /cloud-infrastructure/complexes/complex/{physical-location-id}: get: tags: @@ -339,7 +392,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/complex" + $ref: "#/getDefinitions/complex" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -348,6 +401,7 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: data-center-code in: query description: Data center code which can be an alternate way to identify a complex @@ -367,7 +421,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing complex - description: create or update an existing complex + description: | + Create or update an existing complex. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureComplexesComplex consumes: - application/json @@ -384,12 +441,52 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: body in: body - description: complex object that needs to be created or updated + description: complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplex.json) required: true schema: $ref: "#/definitions/complex" + patch: + tags: + - CloudInfrastructure + summary: update an existing complex + description: | + Update an existing complex + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureComplexesComplex + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: physical-location-id + in: path + description: Unique identifier for physical location, e.g., CLLI + required: true + type: string + example: __PHYSICAL-LOCATION-ID__ + - name: body + in: body + description: complex object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/complex" delete: tags: - CloudInfrastructure @@ -411,6 +508,7 @@ paths: description: Unique identifier for physical location, e.g., CLLI required: true type: string + example: __PHYSICAL-LOCATION-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -430,7 +528,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/complexes" + $ref: "#/getDefinitions/complexes" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}/relationship-list/relationship: @@ -454,19 +552,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: volume-group-id in: path description: Unique ID of volume-group. required: true type: string + example: __VOLUME-GROUP-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json) required: true schema: $ref: "#/definitions/relationship" @@ -491,16 +592,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: volume-group-id in: path description: Unique ID of volume-group. required: true type: string + example: __VOLUME-GROUP-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}: get: tags: @@ -515,7 +619,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/volume-group" + $ref: "#/getDefinitions/volume-group" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -524,16 +628,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: volume-group-id in: path description: Unique ID of volume-group. required: true type: string + example: __VOLUME-GROUP-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -563,7 +670,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing volume-group - description: create or update an existing volume-group + description: | + Create or update an existing volume-group. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup consumes: - application/json @@ -580,22 +690,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: volume-group-id in: path description: Unique ID of volume-group. required: true type: string + example: __VOLUME-GROUP-ID__ - name: body in: body - description: volume-group object that needs to be created or updated + description: volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json) required: true schema: $ref: "#/definitions/volume-group" + patch: + tags: + - CloudInfrastructure + summary: update an existing volume-group + description: | + Update an existing volume-group + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: volume-group-id + in: path + description: Unique ID of volume-group. + required: true + type: string + example: __VOLUME-GROUP-ID__ + - name: body + in: body + description: volume-group object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/volume-group" delete: tags: - CloudInfrastructure @@ -617,16 +781,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: volume-group-id in: path description: Unique ID of volume-group. required: true type: string + example: __VOLUME-GROUP-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -646,7 +813,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/volume-groups" + $ref: "#/getDefinitions/volume-groups" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -655,11 +822,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -691,29 +860,34 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: volume-id in: path description: Unique ID of block storage volume relative to the vserver. required: true type: string + example: __VOLUME-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json) required: true schema: $ref: "#/definitions/relationship" @@ -738,26 +912,31 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: volume-id in: path description: Unique ID of block storage volume relative to the vserver. required: true type: string + example: __VOLUME-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}: get: tags: @@ -772,7 +951,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/volume" + $ref: "#/getDefinitions/volume" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -781,26 +960,31 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: volume-id in: path description: Unique ID of block storage volume relative to the vserver. required: true type: string + example: __VOLUME-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -843,7 +1027,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing volume - description: create or update an existing volume + description: | + Create or update an existing volume. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume consumes: - application/json @@ -860,32 +1047,100 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: volume-id in: path description: Unique ID of block storage volume relative to the vserver. required: true type: string + example: __VOLUME-ID__ - name: body in: body - description: volume object that needs to be created or updated + description: volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json) required: true schema: $ref: "#/definitions/volume" + patch: + tags: + - CloudInfrastructure + summary: update an existing volume + description: | + Update an existing volume + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: volume-id + in: path + description: Unique ID of block storage volume relative to the vserver. + required: true + type: string + example: __VOLUME-ID__ + - name: body + in: body + description: volume object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/volume" delete: tags: - CloudInfrastructure @@ -907,26 +1162,31 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: volume-id in: path description: Unique ID of block storage volume relative to the vserver. required: true type: string + example: __VOLUME-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -946,7 +1206,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/volumes" + $ref: "#/getDefinitions/volumes" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -955,21 +1215,25 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -1029,24 +1293,28 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json) required: true schema: $ref: "#/definitions/relationship" @@ -1071,21 +1339,25 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -1107,34 +1379,40 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -1159,31 +1437,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -1205,39 +1489,46 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -1262,36 +1553,43 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -1306,7 +1604,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -1315,36 +1613,43 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -1429,7 +1734,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -1446,42 +1754,124 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - CloudInfrastructure @@ -1503,36 +1893,43 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -1559,39 +1956,46 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -1616,36 +2020,43 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -1660,7 +2071,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -1669,36 +2080,43 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -1783,7 +2201,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -1800,42 +2221,124 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - CloudInfrastructure @@ -1857,36 +2360,43 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -1906,7 +2416,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -1915,31 +2425,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -2008,7 +2524,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -2025,37 +2544,112 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - CloudInfrastructure + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - CloudInfrastructure @@ -2077,31 +2671,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -2121,7 +2721,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -2130,26 +2730,31 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -2224,34 +2829,40 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -2276,31 +2887,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -2315,7 +2932,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -2324,31 +2941,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -2426,7 +3049,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -2443,37 +3069,112 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - CloudInfrastructure + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - CloudInfrastructure @@ -2495,31 +3196,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -2539,7 +3246,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -2548,26 +3255,31 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -2642,29 +3354,34 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -2689,26 +3406,31 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -2730,34 +3452,40 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -2782,31 +3510,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -2821,7 +3555,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -2830,31 +3564,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -2928,7 +3668,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -2945,37 +3688,112 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - CloudInfrastructure @@ -2997,31 +3815,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -3048,34 +3872,40 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -3100,31 +3930,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -3139,7 +3975,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -3148,31 +3984,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -3246,7 +4088,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -3263,37 +4108,112 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - CloudInfrastructure @@ -3315,31 +4235,37 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -3359,7 +4285,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -3368,26 +4294,31 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -3445,7 +4376,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface consumes: - application/json @@ -3462,32 +4396,100 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - CloudInfrastructure + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - CloudInfrastructure @@ -3509,26 +4511,31 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -3548,7 +4555,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -3557,21 +4564,25 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -3624,7 +4635,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vserver" + $ref: "#/getDefinitions/vserver" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -3633,21 +4644,25 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -3690,7 +4705,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing vserver - description: create or update an existing vserver + description: | + Create or update an existing vserver. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver consumes: - application/json @@ -3707,27 +4725,88 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: body in: body - description: vserver object that needs to be created or updated + description: vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json) required: true schema: $ref: "#/definitions/vserver" + patch: + tags: + - CloudInfrastructure + summary: update an existing vserver + description: | + Update an existing vserver + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: vserver-id + in: path + description: Unique identifier for this vserver relative to its tenant + required: true + type: string + example: __VSERVER-ID__ + - name: body + in: body + description: vserver object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vserver" delete: tags: - CloudInfrastructure @@ -3749,21 +4828,25 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: vserver-id in: path description: Unique identifier for this vserver relative to its tenant required: true type: string + example: __VSERVER-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -3783,7 +4866,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vservers" + $ref: "#/getDefinitions/vservers" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -3792,16 +4875,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -3838,19 +4924,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json) required: true schema: $ref: "#/definitions/relationship" @@ -3875,16 +4964,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}: get: tags: @@ -3899,7 +4991,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/tenant" + $ref: "#/getDefinitions/tenant" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -3908,16 +5000,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -3937,7 +5032,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing tenant - description: create or update an existing tenant + description: | + Create or update an existing tenant. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant consumes: - application/json @@ -3954,22 +5052,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: body in: body - description: tenant object that needs to be created or updated + description: tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json) required: true schema: $ref: "#/definitions/tenant" + patch: + tags: + - CloudInfrastructure + summary: update an existing tenant + description: | + Update an existing tenant + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: tenant-id + in: path + description: Unique id relative to the cloud-region. + required: true + type: string + example: __TENANT-ID__ + - name: body + in: body + description: tenant object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/tenant" delete: tags: - CloudInfrastructure @@ -3991,16 +5143,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: tenant-id in: path description: Unique id relative to the cloud-region. required: true type: string + example: __TENANT-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -4020,7 +5175,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/tenants" + $ref: "#/getDefinitions/tenants" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4029,11 +5184,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -4065,19 +5222,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: flavor-id in: path description: Flavor id, expected to be unique across cloud-region. required: true type: string + example: __FLAVOR-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json) required: true schema: $ref: "#/definitions/relationship" @@ -4102,16 +5262,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: flavor-id in: path description: Flavor id, expected to be unique across cloud-region. required: true type: string + example: __FLAVOR-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}: get: tags: @@ -4126,7 +5289,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/flavor" + $ref: "#/getDefinitions/flavor" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4135,16 +5298,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: flavor-id in: path description: Flavor id, expected to be unique across cloud-region. required: true type: string + example: __FLAVOR-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -4164,7 +5330,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing flavor - description: create or update an existing flavor + description: | + Create or update an existing flavor. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor consumes: - application/json @@ -4181,22 +5350,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: flavor-id in: path description: Flavor id, expected to be unique across cloud-region. required: true type: string + example: __FLAVOR-ID__ - name: body in: body - description: flavor object that needs to be created or updated + description: flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json) required: true schema: $ref: "#/definitions/flavor" + patch: + tags: + - CloudInfrastructure + summary: update an existing flavor + description: | + Update an existing flavor + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: flavor-id + in: path + description: Flavor id, expected to be unique across cloud-region. + required: true + type: string + example: __FLAVOR-ID__ + - name: body + in: body + description: flavor object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/flavor" delete: tags: - CloudInfrastructure @@ -4218,16 +5441,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: flavor-id in: path description: Flavor id, expected to be unique across cloud-region. required: true type: string + example: __FLAVOR-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -4247,7 +5473,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/flavors" + $ref: "#/getDefinitions/flavors" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4256,11 +5482,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -4292,19 +5520,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: group-id in: path description: Group id, expected to be unique across cloud-region. required: true type: string + example: __GROUP-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json) required: true schema: $ref: "#/definitions/relationship" @@ -4329,16 +5560,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: group-id in: path description: Group id, expected to be unique across cloud-region. required: true type: string + example: __GROUP-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}: get: tags: @@ -4353,7 +5587,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/group-assignment" + $ref: "#/getDefinitions/group-assignment" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4362,16 +5596,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: group-id in: path description: Group id, expected to be unique across cloud-region. required: true type: string + example: __GROUP-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -4396,7 +5633,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing group-assignment - description: create or update an existing group-assignment + description: | + Create or update an existing group-assignment. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment consumes: - application/json @@ -4413,22 +5653,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: group-id in: path description: Group id, expected to be unique across cloud-region. required: true type: string + example: __GROUP-ID__ - name: body in: body - description: group-assignment object that needs to be created or updated + description: group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json) required: true schema: $ref: "#/definitions/group-assignment" + patch: + tags: + - CloudInfrastructure + summary: update an existing group-assignment + description: | + Update an existing group-assignment + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: group-id + in: path + description: Group id, expected to be unique across cloud-region. + required: true + type: string + example: __GROUP-ID__ + - name: body + in: body + description: group-assignment object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/group-assignment" delete: tags: - CloudInfrastructure @@ -4450,16 +5744,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: group-id in: path description: Group id, expected to be unique across cloud-region. required: true type: string + example: __GROUP-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -4479,7 +5776,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/group-assignments" + $ref: "#/getDefinitions/group-assignments" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4488,11 +5785,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -4524,19 +5823,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: snapshot-id in: path description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. required: true type: string + example: __SNAPSHOT-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json) required: true schema: $ref: "#/definitions/relationship" @@ -4561,16 +5863,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: snapshot-id in: path description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. required: true type: string + example: __SNAPSHOT-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}: get: tags: @@ -4585,7 +5890,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/snapshot" + $ref: "#/getDefinitions/snapshot" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4594,16 +5899,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: snapshot-id in: path description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. required: true type: string + example: __SNAPSHOT-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -4643,7 +5951,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing snapshot - description: create or update an existing snapshot + description: | + Create or update an existing snapshot. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot consumes: - application/json @@ -4660,22 +5971,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: snapshot-id in: path description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. required: true type: string + example: __SNAPSHOT-ID__ - name: body in: body - description: snapshot object that needs to be created or updated + description: snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json) required: true schema: $ref: "#/definitions/snapshot" + patch: + tags: + - CloudInfrastructure + summary: update an existing snapshot + description: | + Update an existing snapshot + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: snapshot-id + in: path + description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. + required: true + type: string + example: __SNAPSHOT-ID__ + - name: body + in: body + description: snapshot object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/snapshot" delete: tags: - CloudInfrastructure @@ -4697,16 +6062,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: snapshot-id in: path description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. required: true type: string + example: __SNAPSHOT-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -4726,7 +6094,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/snapshots" + $ref: "#/getDefinitions/snapshots" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4735,11 +6103,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -4771,19 +6141,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json) required: true schema: $ref: "#/definitions/relationship" @@ -4808,16 +6181,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}: get: tags: @@ -4832,7 +6208,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/metadatum" + $ref: "#/getDefinitions/metadatum" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4841,20 +6217,24 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -4889,7 +6269,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing metadatum - description: create or update an existing metadatum + description: | + Create or update an existing metadatum. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum consumes: - application/json @@ -4906,26 +6289,86 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: body in: body - description: metadatum object that needs to be created or updated + description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json) required: true schema: $ref: "#/definitions/metadatum" + patch: + tags: + - CloudInfrastructure + summary: update an existing metadatum + description: | + Update an existing metadatum + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: image-id + in: path + description: Image id, expected to be unique across cloud region + required: true + type: string + example: __IMAGE-ID__ + - name: metaname + in: path + required: true + type: string + example: __METANAME__ + - name: body + in: body + description: metadatum object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/metadatum" delete: tags: - CloudInfrastructure @@ -4947,20 +6390,24 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: resource-version in: query description: resource-version for concurrency @@ -4980,7 +6427,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/metadata" + $ref: "#/getDefinitions/metadata" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -4989,16 +6436,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5043,7 +6493,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/image" + $ref: "#/getDefinitions/image" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5052,16 +6502,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5096,7 +6549,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing image - description: create or update an existing image + description: | + Create or update an existing image. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage consumes: - application/json @@ -5113,22 +6569,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ - name: body in: body - description: image object that needs to be created or updated + description: image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json) required: true schema: $ref: "#/definitions/image" + patch: + tags: + - CloudInfrastructure + summary: update an existing image + description: | + Update an existing image + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: image-id + in: path + description: Image id, expected to be unique across cloud region + required: true + type: string + example: __IMAGE-ID__ + - name: body + in: body + description: image object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/image" delete: tags: - CloudInfrastructure @@ -5150,16 +6660,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: image-id in: path description: Image id, expected to be unique across cloud region required: true type: string + example: __IMAGE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -5179,7 +6692,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/images" + $ref: "#/getDefinitions/images" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5188,11 +6701,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5224,19 +6739,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: switch-name in: path description: DVS switch name required: true type: string + example: __SWITCH-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json) required: true schema: $ref: "#/definitions/relationship" @@ -5261,16 +6779,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: switch-name in: path description: DVS switch name required: true type: string + example: __SWITCH-NAME__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}: get: tags: @@ -5285,7 +6806,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/dvs-switch" + $ref: "#/getDefinitions/dvs-switch" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5294,16 +6815,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: switch-name in: path description: DVS switch name required: true type: string + example: __SWITCH-NAME__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5323,7 +6847,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing dvs-switch - description: create or update an existing dvs-switch + description: | + Create or update an existing dvs-switch. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch consumes: - application/json @@ -5340,22 +6867,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: switch-name in: path description: DVS switch name required: true type: string + example: __SWITCH-NAME__ - name: body in: body - description: dvs-switch object that needs to be created or updated + description: dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json) required: true schema: $ref: "#/definitions/dvs-switch" + patch: + tags: + - CloudInfrastructure + summary: update an existing dvs-switch + description: | + Update an existing dvs-switch + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: switch-name + in: path + description: DVS switch name + required: true + type: string + example: __SWITCH-NAME__ + - name: body + in: body + description: dvs-switch object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/dvs-switch" delete: tags: - CloudInfrastructure @@ -5377,16 +6958,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: switch-name in: path description: DVS switch name required: true type: string + example: __SWITCH-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -5406,7 +6990,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/dvs-switches" + $ref: "#/getDefinitions/dvs-switches" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5415,11 +6999,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5451,19 +7037,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: network-uuid in: path description: UUID of the network. Unique across a cloud-region required: true type: string + example: __NETWORK-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json) required: true schema: $ref: "#/definitions/relationship" @@ -5488,16 +7077,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: network-uuid in: path description: UUID of the network. Unique across a cloud-region required: true type: string + example: __NETWORK-UUID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}: get: tags: @@ -5512,7 +7104,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/oam-network" + $ref: "#/getDefinitions/oam-network" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5521,16 +7113,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: network-uuid in: path description: UUID of the network. Unique across a cloud-region required: true type: string + example: __NETWORK-UUID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5556,7 +7151,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing oam-network - description: create or update an existing oam-network + description: | + Create or update an existing oam-network. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork consumes: - application/json @@ -5573,22 +7171,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: network-uuid in: path description: UUID of the network. Unique across a cloud-region required: true type: string + example: __NETWORK-UUID__ - name: body in: body - description: oam-network object that needs to be created or updated + description: oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json) required: true schema: $ref: "#/definitions/oam-network" + patch: + tags: + - CloudInfrastructure + summary: update an existing oam-network + description: | + Update an existing oam-network + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: network-uuid + in: path + description: UUID of the network. Unique across a cloud-region + required: true + type: string + example: __NETWORK-UUID__ + - name: body + in: body + description: oam-network object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/oam-network" delete: tags: - CloudInfrastructure @@ -5610,16 +7262,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: network-uuid in: path description: UUID of the network. Unique across a cloud-region required: true type: string + example: __NETWORK-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -5639,7 +7294,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/oam-networks" + $ref: "#/getDefinitions/oam-networks" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5648,11 +7303,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5684,19 +7341,22 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: availability-zone-name in: path description: Name of the availability zone. Unique across a cloud region required: true type: string + example: __AVAILABILITY-ZONE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json) required: true schema: $ref: "#/definitions/relationship" @@ -5721,16 +7381,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: availability-zone-name in: path description: Name of the availability zone. Unique across a cloud region required: true type: string + example: __AVAILABILITY-ZONE-NAME__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}: get: tags: @@ -5745,7 +7408,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/availability-zone" + $ref: "#/getDefinitions/availability-zone" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5754,16 +7417,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: availability-zone-name in: path description: Name of the availability zone. Unique across a cloud region required: true type: string + example: __AVAILABILITY-ZONE-NAME__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5778,7 +7444,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing availability-zone - description: create or update an existing availability-zone + description: | + Create or update an existing availability-zone. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone consumes: - application/json @@ -5795,22 +7464,76 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: availability-zone-name in: path description: Name of the availability zone. Unique across a cloud region required: true type: string + example: __AVAILABILITY-ZONE-NAME__ - name: body in: body - description: availability-zone object that needs to be created or updated + description: availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json) required: true schema: $ref: "#/definitions/availability-zone" + patch: + tags: + - CloudInfrastructure + summary: update an existing availability-zone + description: | + Update an existing availability-zone + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: availability-zone-name + in: path + description: Name of the availability zone. Unique across a cloud region + required: true + type: string + example: __AVAILABILITY-ZONE-NAME__ + - name: body + in: body + description: availability-zone object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/availability-zone" delete: tags: - CloudInfrastructure @@ -5832,16 +7555,19 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: availability-zone-name in: path description: Name of the availability zone. Unique across a cloud region required: true type: string + example: __AVAILABILITY-ZONE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -5861,7 +7587,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/availability-zones" + $ref: "#/getDefinitions/availability-zones" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5870,11 +7596,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5906,14 +7634,16 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegion.json) required: true schema: $ref: "#/definitions/relationship" @@ -5938,11 +7668,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}: get: tags: @@ -5957,7 +7689,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/cloud-region" + $ref: "#/getDefinitions/cloud-region" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -5966,11 +7698,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: cloud-type in: query description: Type of the cloud (e.g., openstack) @@ -5985,7 +7719,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing cloud-region - description: create or update an existing cloud-region + description: | + Create or update an existing cloud-region. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegion consumes: - application/json @@ -6002,17 +7739,64 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: body in: body - description: cloud-region object that needs to be created or updated + description: cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegion.json) required: true schema: $ref: "#/definitions/cloud-region" + patch: + tags: + - CloudInfrastructure + summary: update an existing cloud-region + description: | + Update an existing cloud-region + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureCloudRegionsCloudRegion + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: cloud-owner + in: path + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + required: true + type: string + example: __CLOUD-OWNER__ + - name: cloud-region-id + in: path + description: Identifier used by the vendor for the region. Second part of composite key + required: true + type: string + example: __CLOUD-REGION-ID__ + - name: body + in: body + description: cloud-region object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/cloud-region" delete: tags: - CloudInfrastructure @@ -6034,11 +7818,13 @@ paths: description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname required: true type: string + example: __CLOUD-OWNER__ - name: cloud-region-id in: path description: Identifier used by the vendor for the region. Second part of composite key required: true type: string + example: __CLOUD-REGION-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -6058,7 +7844,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/cloud-regions" + $ref: "#/getDefinitions/cloud-regions" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}/relationship-list/relationship: @@ -6082,9 +7868,10 @@ paths: description: Unique name of network profile. required: true type: string + example: __NM-PROFILE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureNetworkProfilesNetworkProfile.json) required: true schema: $ref: "#/definitions/relationship" @@ -6109,6 +7896,7 @@ paths: description: Unique name of network profile. required: true type: string + example: __NM-PROFILE-NAME__ /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}: get: tags: @@ -6123,7 +7911,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/network-profile" + $ref: "#/getDefinitions/network-profile" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -6132,11 +7920,15 @@ paths: description: Unique name of network profile. required: true type: string + example: __NM-PROFILE-NAME__ put: tags: - CloudInfrastructure summary: create or update an existing network-profile - description: create or update an existing network-profile + description: | + Create or update an existing network-profile. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureNetworkProfilesNetworkProfile consumes: - application/json @@ -6153,12 +7945,52 @@ paths: description: Unique name of network profile. required: true type: string + example: __NM-PROFILE-NAME__ - name: body in: body - description: network-profile object that needs to be created or updated + description: network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureNetworkProfilesNetworkProfile.json) required: true schema: $ref: "#/definitions/network-profile" + patch: + tags: + - CloudInfrastructure + summary: update an existing network-profile + description: | + Update an existing network-profile + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureNetworkProfilesNetworkProfile + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: nm-profile-name + in: path + description: Unique name of network profile. + required: true + type: string + example: __NM-PROFILE-NAME__ + - name: body + in: body + description: network-profile object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/network-profile" delete: tags: - CloudInfrastructure @@ -6180,6 +8012,7 @@ paths: description: Unique name of network profile. required: true type: string + example: __NM-PROFILE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -6199,7 +8032,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/network-profiles" + $ref: "#/getDefinitions/network-profiles" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship: @@ -6223,9 +8056,10 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserver.json) required: true schema: $ref: "#/definitions/relationship" @@ -6250,6 +8084,7 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship: put: tags: @@ -6271,14 +8106,16 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -6303,11 +8140,13 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -6329,24 +8168,28 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -6371,21 +8214,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -6407,29 +8254,34 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -6454,26 +8306,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -6488,7 +8345,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -6497,26 +8354,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -6587,7 +8449,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -6604,32 +8469,100 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - CloudInfrastructure @@ -6651,26 +8584,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -6697,29 +8635,34 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -6744,26 +8687,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -6778,7 +8726,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -6787,26 +8735,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -6877,7 +8830,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -6894,32 +8850,100 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - CloudInfrastructure @@ -6941,26 +8965,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -6980,7 +9009,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -6989,21 +9018,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -7058,7 +9091,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -7075,27 +9111,88 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - CloudInfrastructure + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - CloudInfrastructure @@ -7117,21 +9214,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -7151,7 +9252,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -7160,16 +9261,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -7230,24 +9334,28 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -7272,21 +9380,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -7301,7 +9413,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -7310,21 +9422,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -7388,7 +9504,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -7405,27 +9524,88 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - CloudInfrastructure + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - CloudInfrastructure @@ -7447,21 +9627,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -7481,7 +9665,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -7490,16 +9674,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -7560,19 +9747,22 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -7597,16 +9787,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -7628,24 +9821,28 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -7670,21 +9867,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -7699,7 +9900,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -7708,21 +9909,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -7782,7 +9987,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -7799,27 +10007,88 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - CloudInfrastructure @@ -7841,21 +10110,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -7882,24 +10155,28 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -7924,21 +10201,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -7953,7 +10234,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -7962,21 +10243,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -8036,7 +10321,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -8053,27 +10341,88 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - CloudInfrastructure @@ -8095,21 +10444,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -8129,7 +10482,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -8138,16 +10491,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -8191,7 +10547,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface consumes: - application/json @@ -8208,22 +10567,76 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - CloudInfrastructure + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - CloudInfrastructure @@ -8245,16 +10658,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -8274,7 +10690,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -8283,11 +10699,13 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -8326,7 +10744,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/p-interface" + $ref: "#/getDefinitions/p-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -8335,11 +10753,13 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -8368,7 +10788,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing p-interface - description: create or update an existing p-interface + description: | + Create or update an existing p-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterface consumes: - application/json @@ -8385,17 +10808,64 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: p-interface object that needs to be created or updated + description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterface.json) required: true schema: $ref: "#/definitions/p-interface" + patch: + tags: + - CloudInfrastructure + summary: update an existing p-interface + description: | + Update an existing p-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: p-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/p-interface" delete: tags: - CloudInfrastructure @@ -8417,11 +10887,13 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -8441,7 +10913,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/p-interfaces" + $ref: "#/getDefinitions/p-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -8450,6 +10922,7 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -8490,14 +10963,16 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -8522,11 +10997,13 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -8548,24 +11025,28 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -8590,21 +11071,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -8626,29 +11111,34 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -8673,26 +11163,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -8707,7 +11202,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -8716,26 +11211,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -8811,7 +11311,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -8828,32 +11331,100 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - CloudInfrastructure @@ -8875,26 +11446,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -8921,29 +11497,34 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -8968,26 +11549,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -9002,7 +11588,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -9011,26 +11597,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -9106,7 +11697,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -9123,32 +11717,100 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - CloudInfrastructure @@ -9170,26 +11832,31 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -9209,7 +11876,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -9218,21 +11885,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -9292,7 +11963,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -9309,27 +11983,88 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - CloudInfrastructure + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - CloudInfrastructure @@ -9351,21 +12086,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -9385,7 +12124,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -9394,16 +12133,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -9469,24 +12211,28 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -9511,21 +12257,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -9540,7 +12290,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -9549,21 +12299,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -9632,7 +12386,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -9649,27 +12406,88 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - CloudInfrastructure + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - CloudInfrastructure @@ -9691,21 +12509,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -9725,7 +12547,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -9734,16 +12556,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -9809,19 +12634,22 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -9846,16 +12674,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -9877,24 +12708,28 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -9919,21 +12754,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -9948,7 +12787,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -9957,21 +12796,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -10036,7 +12879,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -10053,27 +12899,88 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - CloudInfrastructure @@ -10095,21 +13002,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -10136,24 +13047,28 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -10178,21 +13093,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -10207,7 +13126,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -10216,21 +13135,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -10295,7 +13218,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -10312,27 +13238,88 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - CloudInfrastructure + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - CloudInfrastructure @@ -10354,21 +13341,25 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -10388,7 +13379,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -10397,16 +13388,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -10455,7 +13449,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface consumes: - application/json @@ -10472,22 +13469,76 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - CloudInfrastructure + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - CloudInfrastructure @@ -10509,16 +13560,19 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -10538,7 +13592,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -10547,11 +13601,13 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -10595,7 +13651,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-interface" + $ref: "#/getDefinitions/lag-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -10604,11 +13660,13 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -10642,7 +13700,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing lag-interface - description: create or update an existing lag-interface + description: | + Create or update an existing lag-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface consumes: - application/json @@ -10659,17 +13720,64 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: lag-interface object that needs to be created or updated + description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json) required: true schema: $ref: "#/definitions/lag-interface" + patch: + tags: + - CloudInfrastructure + summary: update an existing lag-interface + description: | + Update an existing lag-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: lag-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/lag-interface" delete: tags: - CloudInfrastructure @@ -10691,11 +13799,13 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -10715,7 +13825,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-interfaces" + $ref: "#/getDefinitions/lag-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -10724,6 +13834,7 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -10757,7 +13868,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/pserver" + $ref: "#/getDefinitions/pserver" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -10766,6 +13877,7 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -10789,7 +13901,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing pserver - description: create or update an existing pserver + description: | + Create or update an existing pserver. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructurePserversPserver consumes: - application/json @@ -10806,12 +13921,52 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: body in: body - description: pserver object that needs to be created or updated + description: pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserver.json) required: true schema: $ref: "#/definitions/pserver" + patch: + tags: + - CloudInfrastructure + summary: update an existing pserver + description: | + Update an existing pserver + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructurePserversPserver + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: hostname + in: path + description: Value from executing hostname on the compute node. + required: true + type: string + example: __HOSTNAME__ + - name: body + in: body + description: pserver object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/pserver" delete: tags: - CloudInfrastructure @@ -10833,6 +13988,7 @@ paths: description: Value from executing hostname on the compute node. required: true type: string + example: __HOSTNAME__ - name: resource-version in: query description: resource-version for concurrency @@ -10852,7 +14008,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/pservers" + $ref: "#/getDefinitions/pservers" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship: @@ -10876,9 +14032,10 @@ paths: description: Unique ID of the vdc required: true type: string + example: __VDC-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json) required: true schema: $ref: "#/definitions/relationship" @@ -10903,6 +14060,7 @@ paths: description: Unique ID of the vdc required: true type: string + example: __VDC-ID__ /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}: get: tags: @@ -10917,7 +14075,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/virtual-data-center" + $ref: "#/getDefinitions/virtual-data-center" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -10926,6 +14084,7 @@ paths: description: Unique ID of the vdc required: true type: string + example: __VDC-ID__ - name: vdc-name in: query description: Name of the virtual data center @@ -10935,7 +14094,10 @@ paths: tags: - CloudInfrastructure summary: create or update an existing virtual-data-center - description: create or update an existing virtual-data-center + description: | + Create or update an existing virtual-data-center. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter consumes: - application/json @@ -10952,12 +14114,52 @@ paths: description: Unique ID of the vdc required: true type: string + example: __VDC-ID__ - name: body in: body - description: virtual-data-center object that needs to be created or updated + description: virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json) required: true schema: $ref: "#/definitions/virtual-data-center" + patch: + tags: + - CloudInfrastructure + summary: update an existing virtual-data-center + description: | + Update an existing virtual-data-center + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vdc-id + in: path + description: Unique ID of the vdc + required: true + type: string + example: __VDC-ID__ + - name: body + in: body + description: virtual-data-center object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/virtual-data-center" delete: tags: - CloudInfrastructure @@ -10979,6 +14181,7 @@ paths: description: Unique ID of the vdc required: true type: string + example: __VDC-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -10998,7 +14201,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/virtual-data-centers" + $ref: "#/getDefinitions/virtual-data-centers" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /business/connectors/connector/{resource-instance-id}/relationship-list/relationship: @@ -11022,9 +14225,10 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnector.json) required: true schema: $ref: "#/definitions/relationship" @@ -11049,6 +14253,7 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}: get: tags: @@ -11063,7 +14268,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/metadatum" + $ref: "#/getDefinitions/metadatum" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -11072,10 +14277,12 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: model-invariant-id in: query description: the ASDC model id for this resource or service model. @@ -11100,7 +14307,10 @@ paths: tags: - Business summary: create or update an existing metadatum - description: create or update an existing metadatum + description: | + Create or update an existing metadatum. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateBusinessConnectorsConnectorMetadataMetadatum consumes: - application/json @@ -11117,16 +14327,62 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: body in: body - description: metadatum object that needs to be created or updated + description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnectorMetadataMetadatum.json) required: true schema: $ref: "#/definitions/metadatum" + patch: + tags: + - Business + summary: update an existing metadatum + description: | + Update an existing metadatum + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateBusinessConnectorsConnectorMetadataMetadatum + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: resource-instance-id + in: path + description: Unique id of resource instance. + required: true + type: string + example: __RESOURCE-INSTANCE-ID__ + - name: metaname + in: path + required: true + type: string + example: __METANAME__ + - name: body + in: body + description: metadatum object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/metadatum" delete: tags: - Business @@ -11148,10 +14404,12 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: resource-version in: query description: resource-version for concurrency @@ -11171,7 +14429,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/metadata" + $ref: "#/getDefinitions/metadata" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -11180,6 +14438,7 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ - name: model-invariant-id in: query description: the ASDC model id for this resource or service model. @@ -11214,7 +14473,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/connector" + $ref: "#/getDefinitions/connector" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -11223,6 +14482,7 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ - name: model-invariant-id in: query description: the ASDC model id for this resource or service model. @@ -11247,7 +14507,10 @@ paths: tags: - Business summary: create or update an existing connector - description: create or update an existing connector + description: | + Create or update an existing connector. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateBusinessConnectorsConnector consumes: - application/json @@ -11264,12 +14527,52 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ - name: body in: body - description: connector object that needs to be created or updated + description: connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnector.json) required: true schema: $ref: "#/definitions/connector" + patch: + tags: + - Business + summary: update an existing connector + description: | + Update an existing connector + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateBusinessConnectorsConnector + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: resource-instance-id + in: path + description: Unique id of resource instance. + required: true + type: string + example: __RESOURCE-INSTANCE-ID__ + - name: body + in: body + description: connector object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/connector" delete: tags: - Business @@ -11291,6 +14594,7 @@ paths: description: Unique id of resource instance. required: true type: string + example: __RESOURCE-INSTANCE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -11310,7 +14614,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/connectors" + $ref: "#/getDefinitions/connectors" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/relationship-list/relationship: @@ -11334,19 +14638,22 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json) required: true schema: $ref: "#/definitions/relationship" @@ -11371,16 +14678,19 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}: get: tags: @@ -11395,7 +14705,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/metadatum" + $ref: "#/getDefinitions/metadatum" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -11404,20 +14714,24 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -11467,7 +14781,10 @@ paths: tags: - Business summary: create or update an existing metadatum - description: create or update an existing metadatum + description: | + Create or update an existing metadatum. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum consumes: - application/json @@ -11484,26 +14801,86 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: body in: body - description: metadatum object that needs to be created or updated + description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json) required: true schema: $ref: "#/definitions/metadatum" + patch: + tags: + - Business + summary: update an existing metadatum + description: | + Update an existing metadatum + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: global-customer-id + in: path + description: Global customer id used across ECOMP to uniquely identify customer. + required: true + type: string + example: __GLOBAL-CUSTOMER-ID__ + - name: service-type + in: path + description: Value defined by orchestration to identify this service across ECOMP. + required: true + type: string + example: __SERVICE-TYPE__ + - name: service-instance-id + in: path + description: Uniquely identifies this instance of a service + required: true + type: string + example: __SERVICE-INSTANCE-ID__ + - name: metaname + in: path + required: true + type: string + example: __METANAME__ + - name: body + in: body + description: metadatum object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/metadatum" delete: tags: - Business @@ -11525,20 +14902,24 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: resource-version in: query description: resource-version for concurrency @@ -11558,7 +14939,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/metadata" + $ref: "#/getDefinitions/metadata" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -11567,16 +14948,19 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -11643,29 +15027,34 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json) required: true schema: $ref: "#/definitions/relationship" @@ -11690,26 +15079,31 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}: get: tags: @@ -11724,7 +15118,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/tunnel-xconnect" + $ref: "#/getDefinitions/tunnel-xconnect" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -11733,26 +15127,31 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -11822,7 +15221,10 @@ paths: tags: - Business summary: create or update an existing tunnel-xconnect - description: create or update an existing tunnel-xconnect + description: | + Create or update an existing tunnel-xconnect. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect consumes: - application/json @@ -11839,32 +15241,100 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: body in: body - description: tunnel-xconnect object that needs to be created or updated + description: tunnel-xconnect object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json) required: true schema: $ref: "#/definitions/tunnel-xconnect" + patch: + tags: + - Business + summary: update an existing tunnel-xconnect + description: | + Update an existing tunnel-xconnect + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: global-customer-id + in: path + description: Global customer id used across ECOMP to uniquely identify customer. + required: true + type: string + example: __GLOBAL-CUSTOMER-ID__ + - name: service-type + in: path + description: Value defined by orchestration to identify this service across ECOMP. + required: true + type: string + example: __SERVICE-TYPE__ + - name: service-instance-id + in: path + description: Uniquely identifies this instance of a service + required: true + type: string + example: __SERVICE-INSTANCE-ID__ + - name: id + in: path + description: Allotted Resource id UUID assigned to this instance. + required: true + type: string + example: __ID__ + - name: id + in: path + description: Allotted Resource id UUID assigned to this instance. + required: true + type: string + example: __ID__ + - name: body + in: body + description: tunnel-xconnect object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/tunnel-xconnect" delete: tags: - Business @@ -11886,26 +15356,31 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: resource-version in: query description: resource-version for concurrency @@ -11925,7 +15400,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/tunnel-xconnects" + $ref: "#/getDefinitions/tunnel-xconnects" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -11934,21 +15409,25 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -12035,24 +15514,28 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json) required: true schema: $ref: "#/definitions/relationship" @@ -12077,21 +15560,25 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}: get: tags: @@ -12106,7 +15593,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/allotted-resource" + $ref: "#/getDefinitions/allotted-resource" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -12115,21 +15602,25 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -12199,7 +15690,10 @@ paths: tags: - Business summary: create or update an existing allotted-resource - description: create or update an existing allotted-resource + description: | + Create or update an existing allotted-resource. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource consumes: - application/json @@ -12216,27 +15710,88 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: body in: body - description: allotted-resource object that needs to be created or updated + description: allotted-resource object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json) required: true schema: $ref: "#/definitions/allotted-resource" + patch: + tags: + - Business + summary: update an existing allotted-resource + description: | + Update an existing allotted-resource + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: global-customer-id + in: path + description: Global customer id used across ECOMP to uniquely identify customer. + required: true + type: string + example: __GLOBAL-CUSTOMER-ID__ + - name: service-type + in: path + description: Value defined by orchestration to identify this service across ECOMP. + required: true + type: string + example: __SERVICE-TYPE__ + - name: service-instance-id + in: path + description: Uniquely identifies this instance of a service + required: true + type: string + example: __SERVICE-INSTANCE-ID__ + - name: id + in: path + description: Allotted Resource id UUID assigned to this instance. + required: true + type: string + example: __ID__ + - name: body + in: body + description: allotted-resource object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/allotted-resource" delete: tags: - Business @@ -12258,21 +15813,25 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: id in: path description: Allotted Resource id UUID assigned to this instance. required: true type: string + example: __ID__ - name: resource-version in: query description: resource-version for concurrency @@ -12292,7 +15851,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/allotted-resources" + $ref: "#/getDefinitions/allotted-resources" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -12301,16 +15860,19 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -12370,7 +15932,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/service-instance" + $ref: "#/getDefinitions/service-instance" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -12379,16 +15941,19 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -12438,7 +16003,10 @@ paths: tags: - Business summary: create or update an existing service-instance - description: create or update an existing service-instance + description: | + Create or update an existing service-instance. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance consumes: - application/json @@ -12455,22 +16023,76 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: body in: body - description: service-instance object that needs to be created or updated + description: service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json) required: true schema: $ref: "#/definitions/service-instance" + patch: + tags: + - Business + summary: update an existing service-instance + description: | + Update an existing service-instance + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: global-customer-id + in: path + description: Global customer id used across ECOMP to uniquely identify customer. + required: true + type: string + example: __GLOBAL-CUSTOMER-ID__ + - name: service-type + in: path + description: Value defined by orchestration to identify this service across ECOMP. + required: true + type: string + example: __SERVICE-TYPE__ + - name: service-instance-id + in: path + description: Uniquely identifies this instance of a service + required: true + type: string + example: __SERVICE-INSTANCE-ID__ + - name: body + in: body + description: service-instance object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/service-instance" delete: tags: - Business @@ -12492,16 +16114,19 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: service-instance-id in: path description: Uniquely identifies this instance of a service required: true type: string + example: __SERVICE-INSTANCE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -12521,7 +16146,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/service-instances" + $ref: "#/getDefinitions/service-instances" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -12530,11 +16155,13 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -12566,14 +16193,16 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json) required: true schema: $ref: "#/definitions/relationship" @@ -12598,11 +16227,13 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}: get: tags: @@ -12617,7 +16248,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/service-subscription" + $ref: "#/getDefinitions/service-subscription" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -12626,11 +16257,13 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -12645,7 +16278,10 @@ paths: tags: - Business summary: create or update an existing service-subscription - description: create or update an existing service-subscription + description: | + Create or update an existing service-subscription. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription consumes: - application/json @@ -12662,17 +16298,64 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: body in: body - description: service-subscription object that needs to be created or updated + description: service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json) required: true schema: $ref: "#/definitions/service-subscription" + patch: + tags: + - Business + summary: update an existing service-subscription + description: | + Update an existing service-subscription + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: global-customer-id + in: path + description: Global customer id used across ECOMP to uniquely identify customer. + required: true + type: string + example: __GLOBAL-CUSTOMER-ID__ + - name: service-type + in: path + description: Value defined by orchestration to identify this service across ECOMP. + required: true + type: string + example: __SERVICE-TYPE__ + - name: body + in: body + description: service-subscription object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/service-subscription" delete: tags: - Business @@ -12694,11 +16377,13 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: service-type in: path description: Value defined by orchestration to identify this service across ECOMP. required: true type: string + example: __SERVICE-TYPE__ - name: resource-version in: query description: resource-version for concurrency @@ -12718,7 +16403,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/service-subscriptions" + $ref: "#/getDefinitions/service-subscriptions" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -12727,6 +16412,7 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -12758,9 +16444,10 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomer.json) required: true schema: $ref: "#/definitions/relationship" @@ -12785,6 +16472,7 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ /business/customers/customer/{global-customer-id}: get: tags: @@ -12799,7 +16487,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/customer" + $ref: "#/getDefinitions/customer" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -12808,6 +16496,7 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: subscriber-name in: query description: Subscriber name, an alternate way to retrieve a customer. @@ -12822,7 +16511,10 @@ paths: tags: - Business summary: create or update an existing customer - description: create or update an existing customer + description: | + Create or update an existing customer. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateBusinessCustomersCustomer consumes: - application/json @@ -12839,12 +16531,52 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: body in: body - description: customer object that needs to be created or updated + description: customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomer.json) required: true schema: $ref: "#/definitions/customer" + patch: + tags: + - Business + summary: update an existing customer + description: | + Update an existing customer + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateBusinessCustomersCustomer + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: global-customer-id + in: path + description: Global customer id used across ECOMP to uniquely identify customer. + required: true + type: string + example: __GLOBAL-CUSTOMER-ID__ + - name: body + in: body + description: customer object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/customer" delete: tags: - Business @@ -12866,6 +16598,7 @@ paths: description: Global customer id used across ECOMP to uniquely identify customer. required: true type: string + example: __GLOBAL-CUSTOMER-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -12885,7 +16618,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/customers" + $ref: "#/getDefinitions/customers" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}/relationship-list/relationship: @@ -12909,9 +16642,10 @@ paths: description: Unique ID of this asset required: true type: string + example: __VNF-IMAGE-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationVnfImagesVnfImage.json) required: true schema: $ref: "#/definitions/relationship" @@ -12936,6 +16670,7 @@ paths: description: Unique ID of this asset required: true type: string + example: __VNF-IMAGE-UUID__ /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}: get: tags: @@ -12950,7 +16685,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vnf-image" + $ref: "#/getDefinitions/vnf-image" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -12959,6 +16694,7 @@ paths: description: Unique ID of this asset required: true type: string + example: __VNF-IMAGE-UUID__ - name: application in: query description: The application that the image instantiates. @@ -12978,7 +16714,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing vnf-image - description: create or update an existing vnf-image + description: | + Create or update an existing vnf-image. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationVnfImagesVnfImage consumes: - application/json @@ -12995,12 +16734,52 @@ paths: description: Unique ID of this asset required: true type: string + example: __VNF-IMAGE-UUID__ - name: body in: body - description: vnf-image object that needs to be created or updated + description: vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationVnfImagesVnfImage.json) required: true schema: $ref: "#/definitions/vnf-image" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing vnf-image + description: | + Update an existing vnf-image + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationVnfImagesVnfImage + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-image-uuid + in: path + description: Unique ID of this asset + required: true + type: string + example: __VNF-IMAGE-UUID__ + - name: body + in: body + description: vnf-image object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vnf-image" delete: tags: - ServiceDesignAndCreation @@ -13022,6 +16801,7 @@ paths: description: Unique ID of this asset required: true type: string + example: __VNF-IMAGE-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -13041,7 +16821,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vnf-images" + $ref: "#/getDefinitions/vnf-images" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /service-design-and-creation/services/service/{service-id}/relationship-list/relationship: @@ -13065,9 +16845,10 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServicesService.json) required: true schema: $ref: "#/definitions/relationship" @@ -13092,6 +16873,7 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-ID__ /service-design-and-creation/services/service/{service-id}: get: tags: @@ -13106,7 +16888,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/service" + $ref: "#/getDefinitions/service" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -13115,6 +16897,7 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-ID__ - name: service-description in: query description: Description of the service @@ -13124,7 +16907,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing service - description: create or update an existing service + description: | + Create or update an existing service. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationServicesService consumes: - application/json @@ -13141,12 +16927,52 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-ID__ - name: body in: body - description: service object that needs to be created or updated + description: service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServicesService.json) required: true schema: $ref: "#/definitions/service" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing service + description: | + Update an existing service + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationServicesService + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: service-id + in: path + description: This gets defined by others to provide a unique ID for the service, we accept what is sent. + required: true + type: string + example: __SERVICE-ID__ + - name: body + in: body + description: service object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/service" delete: tags: - ServiceDesignAndCreation @@ -13168,6 +16994,7 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -13187,7 +17014,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/services" + $ref: "#/getDefinitions/services" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}/relationship-list/relationship: @@ -13211,14 +17038,16 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-TYPE__ - name: vnf-type in: path description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. required: true type: string + example: __VNF-TYPE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json) required: true schema: $ref: "#/definitions/relationship" @@ -13243,11 +17072,13 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-TYPE__ - name: vnf-type in: path description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. required: true type: string + example: __VNF-TYPE__ /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}: get: tags: @@ -13262,7 +17093,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/service-capability" + $ref: "#/getDefinitions/service-capability" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -13271,16 +17102,21 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-TYPE__ - name: vnf-type in: path description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. required: true type: string + example: __VNF-TYPE__ put: tags: - ServiceDesignAndCreation summary: create or update an existing service-capability - description: create or update an existing service-capability + description: | + Create or update an existing service-capability. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability consumes: - application/json @@ -13297,17 +17133,64 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-TYPE__ - name: vnf-type in: path description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. required: true type: string + example: __VNF-TYPE__ - name: body in: body - description: service-capability object that needs to be created or updated + description: service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json) required: true schema: $ref: "#/definitions/service-capability" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing service-capability + description: | + Update an existing service-capability + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: service-type + in: path + description: This gets defined by others to provide a unique ID for the service, we accept what is sent. + required: true + type: string + example: __SERVICE-TYPE__ + - name: vnf-type + in: path + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + required: true + type: string + example: __VNF-TYPE__ + - name: body + in: body + description: service-capability object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/service-capability" delete: tags: - ServiceDesignAndCreation @@ -13329,11 +17212,13 @@ paths: description: This gets defined by others to provide a unique ID for the service, we accept what is sent. required: true type: string + example: __SERVICE-TYPE__ - name: vnf-type in: path description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. required: true type: string + example: __VNF-TYPE__ - name: resource-version in: query description: resource-version for concurrency @@ -13353,7 +17238,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/service-capabilities" + $ref: "#/getDefinitions/service-capabilities" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}/relationship-list/relationship: @@ -13377,30 +17262,36 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: element-choice-set-uuid in: path required: true type: string + example: __ELEMENT-CHOICE-SET-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json) required: true schema: $ref: "#/definitions/relationship" @@ -13425,27 +17316,33 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: element-choice-set-uuid in: path required: true type: string + example: __ELEMENT-CHOICE-SET-UUID__ /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}: get: tags: @@ -13460,7 +17357,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/element-choice-set" + $ref: "#/getDefinitions/element-choice-set" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -13469,27 +17366,33 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: element-choice-set-uuid in: path required: true type: string + example: __ELEMENT-CHOICE-SET-UUID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -13509,7 +17412,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing element-choice-set - description: create or update an existing element-choice-set + description: | + Create or update an existing element-choice-set. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet consumes: - application/json @@ -13526,33 +17432,104 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: element-choice-set-uuid in: path required: true type: string + example: __ELEMENT-CHOICE-SET-UUID__ - name: body in: body - description: element-choice-set object that needs to be created or updated + description: element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json) required: true schema: $ref: "#/definitions/element-choice-set" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing element-choice-set + description: | + Update an existing element-choice-set + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: model-invariant-id + in: path + description: Unique identifier corresponding to the main definition of a model in ASDC + required: true + type: string + example: __MODEL-INVARIANT-ID__ + - name: model-version-id + in: path + description: Unique identifier corresponding to one version of a model in ASDC + required: true + type: string + example: __MODEL-VERSION-ID__ + - name: model-element-uuid + in: path + required: true + type: string + example: __MODEL-ELEMENT-UUID__ + - name: model-constraint-uuid + in: path + required: true + type: string + example: __MODEL-CONSTRAINT-UUID__ + - name: constrained-element-set-uuid + in: path + required: true + type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ + - name: element-choice-set-uuid + in: path + required: true + type: string + example: __ELEMENT-CHOICE-SET-UUID__ + - name: body + in: body + description: element-choice-set object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/element-choice-set" delete: tags: - ServiceDesignAndCreation @@ -13574,27 +17551,33 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: element-choice-set-uuid in: path required: true type: string + example: __ELEMENT-CHOICE-SET-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -13614,7 +17597,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/element-choice-sets" + $ref: "#/getDefinitions/element-choice-sets" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -13623,23 +17606,28 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -13676,26 +17664,31 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json) required: true schema: $ref: "#/definitions/relationship" @@ -13720,23 +17713,28 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}: get: tags: @@ -13751,7 +17749,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/constrained-element-set" + $ref: "#/getDefinitions/constrained-element-set" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -13760,23 +17758,28 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -13796,7 +17799,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing constrained-element-set - description: create or update an existing constrained-element-set + description: | + Create or update an existing constrained-element-set. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet consumes: - application/json @@ -13813,29 +17819,94 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: body in: body - description: constrained-element-set object that needs to be created or updated + description: constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json) required: true schema: $ref: "#/definitions/constrained-element-set" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing constrained-element-set + description: | + Update an existing constrained-element-set + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: model-invariant-id + in: path + description: Unique identifier corresponding to the main definition of a model in ASDC + required: true + type: string + example: __MODEL-INVARIANT-ID__ + - name: model-version-id + in: path + description: Unique identifier corresponding to one version of a model in ASDC + required: true + type: string + example: __MODEL-VERSION-ID__ + - name: model-element-uuid + in: path + required: true + type: string + example: __MODEL-ELEMENT-UUID__ + - name: model-constraint-uuid + in: path + required: true + type: string + example: __MODEL-CONSTRAINT-UUID__ + - name: constrained-element-set-uuid + in: path + required: true + type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ + - name: body + in: body + description: constrained-element-set object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/constrained-element-set" delete: tags: - ServiceDesignAndCreation @@ -13857,23 +17928,28 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: constrained-element-set-uuid in: path required: true type: string + example: __CONSTRAINED-ELEMENT-SET-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -13893,7 +17969,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/constrained-element-sets" + $ref: "#/getDefinitions/constrained-element-sets" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -13902,19 +17978,23 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -13944,7 +18024,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/model-constraint" + $ref: "#/getDefinitions/model-constraint" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -13953,19 +18033,23 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -13985,7 +18069,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing model-constraint - description: create or update an existing model-constraint + description: | + Create or update an existing model-constraint. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint consumes: - application/json @@ -14002,25 +18089,84 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: body in: body - description: model-constraint object that needs to be created or updated + description: model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint.json) required: true schema: $ref: "#/definitions/model-constraint" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing model-constraint + description: | + Update an existing model-constraint + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: model-invariant-id + in: path + description: Unique identifier corresponding to the main definition of a model in ASDC + required: true + type: string + example: __MODEL-INVARIANT-ID__ + - name: model-version-id + in: path + description: Unique identifier corresponding to one version of a model in ASDC + required: true + type: string + example: __MODEL-VERSION-ID__ + - name: model-element-uuid + in: path + required: true + type: string + example: __MODEL-ELEMENT-UUID__ + - name: model-constraint-uuid + in: path + required: true + type: string + example: __MODEL-CONSTRAINT-UUID__ + - name: body + in: body + description: model-constraint object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/model-constraint" delete: tags: - ServiceDesignAndCreation @@ -14042,19 +18188,23 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-constraint-uuid in: path required: true type: string + example: __MODEL-CONSTRAINT-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -14074,7 +18224,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/model-constraints" + $ref: "#/getDefinitions/model-constraints" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14083,15 +18233,18 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -14128,18 +18281,21 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json) required: true schema: $ref: "#/definitions/relationship" @@ -14164,15 +18320,18 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}: get: tags: @@ -14187,7 +18346,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/model-element" + $ref: "#/getDefinitions/model-element" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14196,15 +18355,18 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -14224,7 +18386,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing model-element - description: create or update an existing model-element + description: | + Create or update an existing model-element. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement consumes: - application/json @@ -14241,21 +18406,74 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: body in: body - description: model-element object that needs to be created or updated + description: model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json) required: true schema: $ref: "#/definitions/model-element" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing model-element + description: | + Update an existing model-element + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: model-invariant-id + in: path + description: Unique identifier corresponding to the main definition of a model in ASDC + required: true + type: string + example: __MODEL-INVARIANT-ID__ + - name: model-version-id + in: path + description: Unique identifier corresponding to one version of a model in ASDC + required: true + type: string + example: __MODEL-VERSION-ID__ + - name: model-element-uuid + in: path + required: true + type: string + example: __MODEL-ELEMENT-UUID__ + - name: body + in: body + description: model-element object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/model-element" delete: tags: - ServiceDesignAndCreation @@ -14277,15 +18495,18 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-element-uuid in: path required: true type: string + example: __MODEL-ELEMENT-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -14305,7 +18526,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/model-elements" + $ref: "#/getDefinitions/model-elements" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14314,11 +18535,13 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -14348,7 +18571,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/metadatum" + $ref: "#/getDefinitions/metadatum" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14357,15 +18580,18 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -14385,7 +18611,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing metadatum - description: create or update an existing metadatum + description: | + Create or update an existing metadatum. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum consumes: - application/json @@ -14402,21 +18631,74 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: body in: body - description: metadatum object that needs to be created or updated + description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum.json) required: true schema: $ref: "#/definitions/metadatum" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing metadatum + description: | + Update an existing metadatum + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: model-invariant-id + in: path + description: Unique identifier corresponding to the main definition of a model in ASDC + required: true + type: string + example: __MODEL-INVARIANT-ID__ + - name: model-version-id + in: path + description: Unique identifier corresponding to one version of a model in ASDC + required: true + type: string + example: __MODEL-VERSION-ID__ + - name: metaname + in: path + required: true + type: string + example: __METANAME__ + - name: body + in: body + description: metadatum object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/metadatum" delete: tags: - ServiceDesignAndCreation @@ -14438,15 +18720,18 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: metaname in: path required: true type: string + example: __METANAME__ - name: resource-version in: query description: resource-version for concurrency @@ -14466,7 +18751,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/metadata" + $ref: "#/getDefinitions/metadata" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14475,11 +18760,13 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -14516,14 +18803,16 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVer.json) required: true schema: $ref: "#/definitions/relationship" @@ -14548,11 +18837,13 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}: get: tags: @@ -14567,7 +18858,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/model-ver" + $ref: "#/getDefinitions/model-ver" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14576,11 +18867,13 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -14600,7 +18893,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing model-ver - description: create or update an existing model-ver + description: | + Create or update an existing model-ver. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVer consumes: - application/json @@ -14617,17 +18913,64 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: body in: body - description: model-ver object that needs to be created or updated + description: model-ver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVer.json) required: true schema: $ref: "#/definitions/model-ver" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing model-ver + description: | + Update an existing model-ver + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVer + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: model-invariant-id + in: path + description: Unique identifier corresponding to the main definition of a model in ASDC + required: true + type: string + example: __MODEL-INVARIANT-ID__ + - name: model-version-id + in: path + description: Unique identifier corresponding to one version of a model in ASDC + required: true + type: string + example: __MODEL-VERSION-ID__ + - name: body + in: body + description: model-ver object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/model-ver" delete: tags: - ServiceDesignAndCreation @@ -14649,11 +18992,13 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-version-id in: path description: Unique identifier corresponding to one version of a model in ASDC required: true type: string + example: __MODEL-VERSION-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -14673,7 +19018,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/model-vers" + $ref: "#/getDefinitions/model-vers" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14682,6 +19027,7 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -14708,9 +19054,10 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModel.json) required: true schema: $ref: "#/definitions/relationship" @@ -14735,6 +19082,7 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ /service-design-and-creation/models/model/{model-invariant-id}: get: tags: @@ -14749,7 +19097,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/model" + $ref: "#/getDefinitions/model" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14758,6 +19106,7 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: model-type in: query description: Type of the model, e.g., service, resource, widget, etc. @@ -14767,7 +19116,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing model - description: create or update an existing model + description: | + Create or update an existing model. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationModelsModel consumes: - application/json @@ -14784,12 +19136,52 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: body in: body - description: model object that needs to be created or updated + description: model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModel.json) required: true schema: $ref: "#/definitions/model" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing model + description: | + Update an existing model + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationModelsModel + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: model-invariant-id + in: path + description: Unique identifier corresponding to the main definition of a model in ASDC + required: true + type: string + example: __MODEL-INVARIANT-ID__ + - name: body + in: body + description: model object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/model" delete: tags: - ServiceDesignAndCreation @@ -14811,6 +19203,7 @@ paths: description: Unique identifier corresponding to the main definition of a model in ASDC required: true type: string + example: __MODEL-INVARIANT-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -14830,7 +19223,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/models" + $ref: "#/getDefinitions/models" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}/relationship-list/relationship: @@ -14853,17 +19246,20 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: related-lookup-uuid in: path required: true type: string + example: __RELATED-LOOKUP-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json) required: true schema: $ref: "#/definitions/relationship" @@ -14887,14 +19283,17 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: related-lookup-uuid in: path required: true type: string + example: __RELATED-LOOKUP-UUID__ /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}: get: tags: @@ -14909,7 +19308,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/related-lookup" + $ref: "#/getDefinitions/related-lookup" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -14917,14 +19316,17 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: related-lookup-uuid in: path required: true type: string + example: __RELATED-LOOKUP-UUID__ - name: named-query-name in: query required: false @@ -14933,7 +19335,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing related-lookup - description: create or update an existing related-lookup + description: | + Create or update an existing related-lookup. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup consumes: - application/json @@ -14949,20 +19354,71 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: related-lookup-uuid in: path required: true type: string + example: __RELATED-LOOKUP-UUID__ - name: body in: body - description: related-lookup object that needs to be created or updated + description: related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json) required: true schema: $ref: "#/definitions/related-lookup" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing related-lookup + description: | + Update an existing related-lookup + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: named-query-uuid + in: path + required: true + type: string + example: __NAMED-QUERY-UUID__ + - name: named-query-element-uuid + in: path + required: true + type: string + example: __NAMED-QUERY-ELEMENT-UUID__ + - name: related-lookup-uuid + in: path + required: true + type: string + example: __RELATED-LOOKUP-UUID__ + - name: body + in: body + description: related-lookup object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/related-lookup" delete: tags: - ServiceDesignAndCreation @@ -14983,14 +19439,17 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: related-lookup-uuid in: path required: true type: string + example: __RELATED-LOOKUP-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -15010,7 +19469,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/related-lookups" + $ref: "#/getDefinitions/related-lookups" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15018,10 +19477,12 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: named-query-name in: query required: false @@ -15040,7 +19501,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/property-constraint" + $ref: "#/getDefinitions/property-constraint" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15048,14 +19509,17 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: property-constraint-uuid in: path required: true type: string + example: __PROPERTY-CONSTRAINT-UUID__ - name: named-query-name in: query required: false @@ -15064,7 +19528,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing property-constraint - description: create or update an existing property-constraint + description: | + Create or update an existing property-constraint. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint consumes: - application/json @@ -15080,20 +19547,71 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: property-constraint-uuid in: path required: true type: string + example: __PROPERTY-CONSTRAINT-UUID__ - name: body in: body - description: property-constraint object that needs to be created or updated + description: property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json) required: true schema: $ref: "#/definitions/property-constraint" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing property-constraint + description: | + Update an existing property-constraint + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: named-query-uuid + in: path + required: true + type: string + example: __NAMED-QUERY-UUID__ + - name: named-query-element-uuid + in: path + required: true + type: string + example: __NAMED-QUERY-ELEMENT-UUID__ + - name: property-constraint-uuid + in: path + required: true + type: string + example: __PROPERTY-CONSTRAINT-UUID__ + - name: body + in: body + description: property-constraint object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/property-constraint" delete: tags: - ServiceDesignAndCreation @@ -15114,14 +19632,17 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: property-constraint-uuid in: path required: true type: string + example: __PROPERTY-CONSTRAINT-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -15141,7 +19662,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/property-constraints" + $ref: "#/getDefinitions/property-constraints" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15149,10 +19670,12 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: named-query-name in: query required: false @@ -15177,13 +19700,15 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json) required: true schema: $ref: "#/definitions/relationship" @@ -15207,10 +19732,12 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}: get: tags: @@ -15225,7 +19752,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/named-query-element" + $ref: "#/getDefinitions/named-query-element" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15233,10 +19760,12 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: named-query-name in: query required: false @@ -15245,7 +19774,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing named-query-element - description: create or update an existing named-query-element + description: | + Create or update an existing named-query-element. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement consumes: - application/json @@ -15261,16 +19793,61 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: body in: body - description: named-query-element object that needs to be created or updated + description: named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json) required: true schema: $ref: "#/definitions/named-query-element" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing named-query-element + description: | + Update an existing named-query-element + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: named-query-uuid + in: path + required: true + type: string + example: __NAMED-QUERY-UUID__ + - name: named-query-element-uuid + in: path + required: true + type: string + example: __NAMED-QUERY-ELEMENT-UUID__ + - name: body + in: body + description: named-query-element object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/named-query-element" delete: tags: - ServiceDesignAndCreation @@ -15291,10 +19868,12 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-element-uuid in: path required: true type: string + example: __NAMED-QUERY-ELEMENT-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -15314,7 +19893,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/named-query-elements" + $ref: "#/getDefinitions/named-query-elements" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15322,6 +19901,7 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-name in: query required: false @@ -15346,9 +19926,10 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQuery.json) required: true schema: $ref: "#/definitions/relationship" @@ -15372,6 +19953,7 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ /service-design-and-creation/named-queries/named-query/{named-query-uuid}: get: tags: @@ -15386,7 +19968,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/named-query" + $ref: "#/getDefinitions/named-query" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15394,6 +19976,7 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: named-query-name in: query required: false @@ -15402,7 +19985,10 @@ paths: tags: - ServiceDesignAndCreation summary: create or update an existing named-query - description: create or update an existing named-query + description: | + Create or update an existing named-query. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQuery consumes: - application/json @@ -15418,12 +20004,51 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: body in: body - description: named-query object that needs to be created or updated + description: named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQuery.json) required: true schema: $ref: "#/definitions/named-query" + patch: + tags: + - ServiceDesignAndCreation + summary: update an existing named-query + description: | + Update an existing named-query + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQuery + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: named-query-uuid + in: path + required: true + type: string + example: __NAMED-QUERY-UUID__ + - name: body + in: body + description: named-query object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/named-query" delete: tags: - ServiceDesignAndCreation @@ -15444,6 +20069,7 @@ paths: in: path required: true type: string + example: __NAMED-QUERY-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -15463,7 +20089,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/named-queries" + $ref: "#/getDefinitions/named-queries" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/logical-links/logical-link/{link-name}/relationship-list/relationship: @@ -15487,9 +20113,10 @@ paths: description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ required: true type: string + example: __LINK-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLogicalLinksLogicalLink.json) required: true schema: $ref: "#/definitions/relationship" @@ -15514,6 +20141,7 @@ paths: description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ required: true type: string + example: __LINK-NAME__ /network/logical-links/logical-link/{link-name}: get: tags: @@ -15528,7 +20156,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/logical-link" + $ref: "#/getDefinitions/logical-link" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15537,6 +20165,7 @@ paths: description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ required: true type: string + example: __LINK-NAME__ - name: model-invariant-id in: query description: the ASDC model id for this resource or service model. @@ -15581,7 +20210,10 @@ paths: tags: - Network summary: create or update an existing logical-link - description: create or update an existing logical-link + description: | + Create or update an existing logical-link. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkLogicalLinksLogicalLink consumes: - application/json @@ -15598,12 +20230,52 @@ paths: description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ required: true type: string + example: __LINK-NAME__ - name: body in: body - description: logical-link object that needs to be created or updated + description: logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLogicalLinksLogicalLink.json) required: true schema: $ref: "#/definitions/logical-link" + patch: + tags: + - Network + summary: update an existing logical-link + description: | + Update an existing logical-link + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkLogicalLinksLogicalLink + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: link-name + in: path + description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ + required: true + type: string + example: __LINK-NAME__ + - name: body + in: body + description: logical-link object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/logical-link" delete: tags: - Network @@ -15625,6 +20297,7 @@ paths: description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ required: true type: string + example: __LINK-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -15644,7 +20317,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/logical-links" + $ref: "#/getDefinitions/logical-links" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}/relationship-list/relationship: @@ -15668,24 +20341,28 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ - name: cos in: path description: unique identifier of probe required: true type: string + example: __COS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json) required: true schema: $ref: "#/definitions/relationship" @@ -15710,21 +20387,25 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ - name: cos in: path description: unique identifier of probe required: true type: string + example: __COS__ /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}: get: tags: @@ -15739,7 +20420,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/class-of-service" + $ref: "#/getDefinitions/class-of-service" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15748,26 +20429,33 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ - name: cos in: path description: unique identifier of probe required: true type: string + example: __COS__ put: tags: - Network summary: create or update an existing class-of-service - description: create or update an existing class-of-service + description: | + Create or update an existing class-of-service. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService consumes: - application/json @@ -15784,27 +20472,88 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ - name: cos in: path description: unique identifier of probe required: true type: string + example: __COS__ - name: body in: body - description: class-of-service object that needs to be created or updated + description: class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json) required: true schema: $ref: "#/definitions/class-of-service" + patch: + tags: + - Network + summary: update an existing class-of-service + description: | + Update an existing class-of-service + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: site-pair-set-id + in: path + description: Unique id of site pair set. + required: true + type: string + example: __SITE-PAIR-SET-ID__ + - name: routing-instance-id + in: path + description: Unique id of routing instance + required: true + type: string + example: __ROUTING-INSTANCE-ID__ + - name: site-pair-id + in: path + description: unique identifier of probe + required: true + type: string + example: __SITE-PAIR-ID__ + - name: cos + in: path + description: unique identifier of probe + required: true + type: string + example: __COS__ + - name: body + in: body + description: class-of-service object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/class-of-service" delete: tags: - Network @@ -15826,21 +20575,25 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ - name: cos in: path description: unique identifier of probe required: true type: string + example: __COS__ - name: resource-version in: query description: resource-version for concurrency @@ -15860,7 +20613,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/classes-of-service" + $ref: "#/getDefinitions/classes-of-service" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15869,16 +20622,19 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/relationship-list/relationship: put: tags: @@ -15900,19 +20656,22 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json) required: true schema: $ref: "#/definitions/relationship" @@ -15937,16 +20696,19 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}: get: tags: @@ -15961,7 +20723,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/site-pair" + $ref: "#/getDefinitions/site-pair" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -15970,21 +20732,27 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ put: tags: - Network summary: create or update an existing site-pair - description: create or update an existing site-pair + description: | + Create or update an existing site-pair. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair consumes: - application/json @@ -16001,22 +20769,76 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ - name: body in: body - description: site-pair object that needs to be created or updated + description: site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json) required: true schema: $ref: "#/definitions/site-pair" + patch: + tags: + - Network + summary: update an existing site-pair + description: | + Update an existing site-pair + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: site-pair-set-id + in: path + description: Unique id of site pair set. + required: true + type: string + example: __SITE-PAIR-SET-ID__ + - name: routing-instance-id + in: path + description: Unique id of routing instance + required: true + type: string + example: __ROUTING-INSTANCE-ID__ + - name: site-pair-id + in: path + description: unique identifier of probe + required: true + type: string + example: __SITE-PAIR-ID__ + - name: body + in: body + description: site-pair object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/site-pair" delete: tags: - Network @@ -16038,16 +20860,19 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: site-pair-id in: path description: unique identifier of probe required: true type: string + example: __SITE-PAIR-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -16067,7 +20892,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/site-pairs" + $ref: "#/getDefinitions/site-pairs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -16076,11 +20901,13 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/relationship-list/relationship: put: tags: @@ -16102,14 +20929,16 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json) required: true schema: $ref: "#/definitions/relationship" @@ -16134,11 +20963,13 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}: get: tags: @@ -16153,7 +20984,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/routing-instance" + $ref: "#/getDefinitions/routing-instance" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -16162,16 +20993,21 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ put: tags: - Network summary: create or update an existing routing-instance - description: create or update an existing routing-instance + description: | + Create or update an existing routing-instance. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance consumes: - application/json @@ -16188,17 +21024,64 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: body in: body - description: routing-instance object that needs to be created or updated + description: routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json) required: true schema: $ref: "#/definitions/routing-instance" + patch: + tags: + - Network + summary: update an existing routing-instance + description: | + Update an existing routing-instance + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: site-pair-set-id + in: path + description: Unique id of site pair set. + required: true + type: string + example: __SITE-PAIR-SET-ID__ + - name: routing-instance-id + in: path + description: Unique id of routing instance + required: true + type: string + example: __ROUTING-INSTANCE-ID__ + - name: body + in: body + description: routing-instance object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/routing-instance" delete: tags: - Network @@ -16220,11 +21103,13 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: routing-instance-id in: path description: Unique id of routing instance required: true type: string + example: __ROUTING-INSTANCE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -16244,7 +21129,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/routing-instances" + $ref: "#/getDefinitions/routing-instances" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -16253,6 +21138,7 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ /network/site-pair-sets/site-pair-set/{site-pair-set-id}/relationship-list/relationship: put: tags: @@ -16274,9 +21160,10 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSet.json) required: true schema: $ref: "#/definitions/relationship" @@ -16301,6 +21188,7 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ /network/site-pair-sets/site-pair-set/{site-pair-set-id}: get: tags: @@ -16315,7 +21203,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/site-pair-set" + $ref: "#/getDefinitions/site-pair-set" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -16324,11 +21212,15 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ put: tags: - Network summary: create or update an existing site-pair-set - description: create or update an existing site-pair-set + description: | + Create or update an existing site-pair-set. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkSitePairSetsSitePairSet consumes: - application/json @@ -16345,12 +21237,52 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: body in: body - description: site-pair-set object that needs to be created or updated + description: site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSet.json) required: true schema: $ref: "#/definitions/site-pair-set" + patch: + tags: + - Network + summary: update an existing site-pair-set + description: | + Update an existing site-pair-set + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkSitePairSetsSitePairSet + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: site-pair-set-id + in: path + description: Unique id of site pair set. + required: true + type: string + example: __SITE-PAIR-SET-ID__ + - name: body + in: body + description: site-pair-set object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/site-pair-set" delete: tags: - Network @@ -16372,6 +21304,7 @@ paths: description: Unique id of site pair set. required: true type: string + example: __SITE-PAIR-SET-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -16391,7 +21324,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/site-pair-sets" + $ref: "#/getDefinitions/site-pair-sets" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}/relationship-list/relationship: @@ -16415,19 +21348,22 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: global-route-target in: path description: Number used to identify an RT, globally unique in the network required: true type: string + example: __GLOBAL-ROUTE-TARGET__ - name: route-target-role in: path description: Role assigned to this route target required: true type: string + example: __ROUTE-TARGET-ROLE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json) required: true schema: $ref: "#/definitions/relationship" @@ -16452,16 +21388,19 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: global-route-target in: path description: Number used to identify an RT, globally unique in the network required: true type: string + example: __GLOBAL-ROUTE-TARGET__ - name: route-target-role in: path description: Role assigned to this route target required: true type: string + example: __ROUTE-TARGET-ROLE__ /network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}: get: tags: @@ -16476,7 +21415,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/route-target" + $ref: "#/getDefinitions/route-target" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -16485,16 +21424,19 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: global-route-target in: path description: Number used to identify an RT, globally unique in the network required: true type: string + example: __GLOBAL-ROUTE-TARGET__ - name: route-target-role in: path description: Role assigned to this route target required: true type: string + example: __ROUTE-TARGET-ROLE__ - name: vpn-name in: query description: VPN Name @@ -16509,7 +21451,10 @@ paths: tags: - Network summary: create or update an existing route-target - description: create or update an existing route-target + description: | + Create or update an existing route-target. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVpnBindingsVpnBindingRouteTargetsRouteTarget consumes: - application/json @@ -16526,22 +21471,76 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: global-route-target in: path description: Number used to identify an RT, globally unique in the network required: true type: string + example: __GLOBAL-ROUTE-TARGET__ - name: route-target-role in: path description: Role assigned to this route target required: true type: string + example: __ROUTE-TARGET-ROLE__ - name: body in: body - description: route-target object that needs to be created or updated + description: route-target object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json) required: true schema: $ref: "#/definitions/route-target" + patch: + tags: + - Network + summary: update an existing route-target + description: | + Update an existing route-target + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVpnBindingsVpnBindingRouteTargetsRouteTarget + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vpn-id + in: path + description: VPN ID, globally unique within A&AI + required: true + type: string + example: __VPN-ID__ + - name: global-route-target + in: path + description: Number used to identify an RT, globally unique in the network + required: true + type: string + example: __GLOBAL-ROUTE-TARGET__ + - name: route-target-role + in: path + description: Role assigned to this route target + required: true + type: string + example: __ROUTE-TARGET-ROLE__ + - name: body + in: body + description: route-target object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/route-target" delete: tags: - Network @@ -16563,16 +21562,19 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: global-route-target in: path description: Number used to identify an RT, globally unique in the network required: true type: string + example: __GLOBAL-ROUTE-TARGET__ - name: route-target-role in: path description: Role assigned to this route target required: true type: string + example: __ROUTE-TARGET-ROLE__ - name: resource-version in: query description: resource-version for concurrency @@ -16592,7 +21594,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/route-targets" + $ref: "#/getDefinitions/route-targets" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -16601,6 +21603,7 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: vpn-name in: query description: VPN Name @@ -16632,9 +21635,10 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBinding.json) required: true schema: $ref: "#/definitions/relationship" @@ -16659,6 +21663,7 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ /network/vpn-bindings/vpn-binding/{vpn-id}: get: tags: @@ -16673,7 +21678,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vpn-binding" + $ref: "#/getDefinitions/vpn-binding" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -16682,6 +21687,7 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: vpn-name in: query description: VPN Name @@ -16696,7 +21702,10 @@ paths: tags: - Network summary: create or update an existing vpn-binding - description: create or update an existing vpn-binding + description: | + Create or update an existing vpn-binding. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVpnBindingsVpnBinding consumes: - application/json @@ -16713,12 +21722,52 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: body in: body - description: vpn-binding object that needs to be created or updated + description: vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBinding.json) required: true schema: $ref: "#/definitions/vpn-binding" + patch: + tags: + - Network + summary: update an existing vpn-binding + description: | + Update an existing vpn-binding + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVpnBindingsVpnBinding + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vpn-id + in: path + description: VPN ID, globally unique within A&AI + required: true + type: string + example: __VPN-ID__ + - name: body + in: body + description: vpn-binding object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vpn-binding" delete: tags: - Network @@ -16740,6 +21789,7 @@ paths: description: VPN ID, globally unique within A&AI required: true type: string + example: __VPN-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -16759,7 +21809,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vpn-bindings" + $ref: "#/getDefinitions/vpn-bindings" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/vpls-pes/vpls-pe/{equipment-name}/relationship-list/relationship: @@ -16782,9 +21832,10 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPe.json) required: true schema: $ref: "#/definitions/relationship" @@ -16808,6 +21859,7 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship: put: tags: @@ -16828,14 +21880,16 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -16859,11 +21913,13 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -16884,24 +21940,28 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -16925,21 +21985,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -16960,29 +22024,34 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -17006,26 +22075,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -17040,7 +22114,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -17048,26 +22122,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -17124,7 +22203,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -17140,32 +22222,99 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -17186,26 +22335,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -17231,29 +22385,34 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -17277,26 +22436,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -17311,7 +22475,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -17319,26 +22483,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -17395,7 +22564,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -17411,32 +22583,99 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -17457,26 +22696,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -17496,7 +22740,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -17504,21 +22748,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -17559,7 +22807,10 @@ paths: tags: - Network summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -17575,27 +22826,87 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - Network + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - Network @@ -17616,21 +22927,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -17650,7 +22965,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -17658,16 +22973,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -17713,24 +23031,28 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -17754,21 +23076,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -17783,7 +23109,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -17791,21 +23117,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -17855,7 +23185,10 @@ paths: tags: - Network summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -17871,27 +23204,87 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - Network + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - Network @@ -17912,21 +23305,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -17946,7 +23343,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -17954,16 +23351,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -18009,19 +23409,22 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -18045,16 +23448,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -18075,24 +23481,28 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -18116,21 +23526,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -18145,7 +23559,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -18153,21 +23567,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -18213,7 +23631,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -18229,27 +23650,87 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -18270,21 +23751,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -18310,24 +23795,28 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -18351,21 +23840,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -18380,7 +23873,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -18388,21 +23881,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -18448,7 +23945,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -18464,27 +23964,87 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -18505,21 +24065,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -18539,7 +24103,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -18547,16 +24111,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -18586,7 +24153,10 @@ paths: tags: - Network summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface consumes: - application/json @@ -18602,22 +24172,75 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - Network + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - Network @@ -18638,16 +24261,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -18667,7 +24293,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -18675,11 +24301,13 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -18704,7 +24332,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/p-interface" + $ref: "#/getDefinitions/p-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -18712,11 +24340,13 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -18731,7 +24361,10 @@ paths: tags: - Network summary: create or update an existing p-interface - description: create or update an existing p-interface + description: | + Create or update an existing p-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterface consumes: - application/json @@ -18747,17 +24380,63 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: p-interface object that needs to be created or updated + description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterface.json) required: true schema: $ref: "#/definitions/p-interface" + patch: + tags: + - Network + summary: update an existing p-interface + description: | + Update an existing p-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: p-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/p-interface" delete: tags: - Network @@ -18778,11 +24457,13 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -18802,7 +24483,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/p-interfaces" + $ref: "#/getDefinitions/p-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -18810,6 +24491,7 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -18835,14 +24517,16 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -18866,11 +24550,13 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -18891,24 +24577,28 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -18932,21 +24622,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -18967,29 +24661,34 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -19013,26 +24712,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -19047,7 +24751,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -19055,26 +24759,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -19136,7 +24845,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -19152,32 +24864,99 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -19198,26 +24977,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -19243,29 +25027,34 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -19289,26 +25078,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -19323,7 +25117,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -19331,26 +25125,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -19412,7 +25211,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -19428,32 +25230,99 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -19474,26 +25343,31 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -19513,7 +25387,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -19521,21 +25395,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -19581,7 +25459,10 @@ paths: tags: - Network summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -19597,27 +25478,87 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - Network + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - Network @@ -19638,21 +25579,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -19672,7 +25617,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -19680,16 +25625,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -19740,24 +25688,28 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -19781,21 +25733,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -19810,7 +25766,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -19818,21 +25774,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -19887,7 +25847,10 @@ paths: tags: - Network summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -19903,27 +25866,87 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - Network + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - Network @@ -19944,21 +25967,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -19978,7 +26005,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -19986,16 +26013,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -20046,19 +26076,22 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -20082,16 +26115,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -20112,24 +26148,28 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -20153,21 +26193,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -20182,7 +26226,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -20190,21 +26234,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -20255,7 +26303,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -20271,27 +26322,87 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -20312,21 +26423,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -20352,24 +26467,28 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -20393,21 +26512,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -20422,7 +26545,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -20430,21 +26553,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -20495,7 +26622,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -20511,27 +26641,87 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -20552,21 +26742,25 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -20586,7 +26780,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -20594,16 +26788,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -20638,7 +26835,10 @@ paths: tags: - Network summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface consumes: - application/json @@ -20654,22 +26854,75 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - Network + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - Network @@ -20690,16 +26943,19 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -20719,7 +26975,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -20727,11 +26983,13 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -20761,7 +27019,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-interface" + $ref: "#/getDefinitions/lag-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -20769,11 +27027,13 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -20793,7 +27053,10 @@ paths: tags: - Network summary: create or update an existing lag-interface - description: create or update an existing lag-interface + description: | + Create or update an existing lag-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterface consumes: - application/json @@ -20809,17 +27072,63 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: lag-interface object that needs to be created or updated + description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterface.json) required: true schema: $ref: "#/definitions/lag-interface" + patch: + tags: + - Network + summary: update an existing lag-interface + description: | + Update an existing lag-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: lag-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/lag-interface" delete: tags: - Network @@ -20840,11 +27149,13 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -20864,7 +27175,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-interfaces" + $ref: "#/getDefinitions/lag-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -20872,6 +27183,7 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -20891,7 +27203,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vpls-pe" + $ref: "#/getDefinitions/vpls-pe" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -20899,6 +27211,7 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: prov-status in: query description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. @@ -20908,7 +27221,10 @@ paths: tags: - Network summary: create or update an existing vpls-pe - description: create or update an existing vpls-pe + description: | + Create or update an existing vpls-pe. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVplsPesVplsPe consumes: - application/json @@ -20924,12 +27240,51 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: body in: body - description: vpls-pe object that needs to be created or updated + description: vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPe.json) required: true schema: $ref: "#/definitions/vpls-pe" + patch: + tags: + - Network + summary: update an existing vpls-pe + description: | + Update an existing vpls-pe + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVplsPesVplsPe + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: equipment-name + in: path + required: true + type: string + example: __EQUIPMENT-NAME__ + - name: body + in: body + description: vpls-pe object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vpls-pe" delete: tags: - Network @@ -20950,6 +27305,7 @@ paths: in: path required: true type: string + example: __EQUIPMENT-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -20969,7 +27325,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vpls-pes" + $ref: "#/getDefinitions/vpls-pes" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}/relationship-list/relationship: @@ -20993,9 +27349,10 @@ paths: description: Unique id of multicast configuration. required: true type: string + example: __MULTICAST-CONFIGURATION-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkMulticastConfigurationsMulticastConfiguration.json) required: true schema: $ref: "#/definitions/relationship" @@ -21020,6 +27377,7 @@ paths: description: Unique id of multicast configuration. required: true type: string + example: __MULTICAST-CONFIGURATION-ID__ /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}: get: tags: @@ -21034,7 +27392,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/multicast-configuration" + $ref: "#/getDefinitions/multicast-configuration" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -21043,11 +27401,15 @@ paths: description: Unique id of multicast configuration. required: true type: string + example: __MULTICAST-CONFIGURATION-ID__ put: tags: - Network summary: create or update an existing multicast-configuration - description: create or update an existing multicast-configuration + description: | + Create or update an existing multicast-configuration. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkMulticastConfigurationsMulticastConfiguration consumes: - application/json @@ -21064,12 +27426,52 @@ paths: description: Unique id of multicast configuration. required: true type: string + example: __MULTICAST-CONFIGURATION-ID__ - name: body in: body - description: multicast-configuration object that needs to be created or updated + description: multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkMulticastConfigurationsMulticastConfiguration.json) required: true schema: $ref: "#/definitions/multicast-configuration" + patch: + tags: + - Network + summary: update an existing multicast-configuration + description: | + Update an existing multicast-configuration + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkMulticastConfigurationsMulticastConfiguration + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: multicast-configuration-id + in: path + description: Unique id of multicast configuration. + required: true + type: string + example: __MULTICAST-CONFIGURATION-ID__ + - name: body + in: body + description: multicast-configuration object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/multicast-configuration" delete: tags: - Network @@ -21091,6 +27493,7 @@ paths: description: Unique id of multicast configuration. required: true type: string + example: __MULTICAST-CONFIGURATION-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -21110,7 +27513,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/multicast-configurations" + $ref: "#/getDefinitions/multicast-configurations" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}/relationship-list/relationship: @@ -21134,20 +27537,23 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: cvlan-tag in: path description: See mis-na-virtualization-platform.yang required: true type: integer format: int64 + example: __CVLAN-TAG__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json) required: true schema: $ref: "#/definitions/relationship" @@ -21172,17 +27578,20 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: cvlan-tag in: path description: See mis-na-virtualization-platform.yang required: true type: integer format: int64 + example: __CVLAN-TAG__ /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}: get: tags: @@ -21197,7 +27606,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/cvlan-tag-entry" + $ref: "#/getDefinitions/cvlan-tag-entry" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -21206,17 +27615,20 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: cvlan-tag in: path description: See mis-na-virtualization-platform.yang required: true type: integer format: int64 + example: __CVLAN-TAG__ - name: vnf-name in: query description: Name of VNF. @@ -21276,7 +27688,10 @@ paths: tags: - Network summary: create or update an existing cvlan-tag-entry - description: create or update an existing cvlan-tag-entry + description: | + Create or update an existing cvlan-tag-entry. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry consumes: - application/json @@ -21293,23 +27708,78 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: cvlan-tag in: path description: See mis-na-virtualization-platform.yang required: true type: integer format: int64 + example: __CVLAN-TAG__ - name: body in: body - description: cvlan-tag-entry object that needs to be created or updated + description: cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json) required: true schema: $ref: "#/definitions/cvlan-tag-entry" + patch: + tags: + - Network + summary: update an existing cvlan-tag-entry + description: | + Update an existing cvlan-tag-entry + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-id + in: path + description: Unique ID of the interface + required: true + type: string + example: __INTERFACE-ID__ + - name: cvlan-tag + in: path + description: See mis-na-virtualization-platform.yang + required: true + type: integer + format: int64 + example: __CVLAN-TAG__ + - name: body + in: body + description: cvlan-tag-entry object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/cvlan-tag-entry" delete: tags: - Network @@ -21331,17 +27801,20 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: cvlan-tag in: path description: See mis-na-virtualization-platform.yang required: true type: integer format: int64 + example: __CVLAN-TAG__ - name: resource-version in: query description: resource-version for concurrency @@ -21361,7 +27834,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/cvlan-tags" + $ref: "#/getDefinitions/cvlan-tags" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -21370,11 +27843,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: vnf-name in: query description: Name of VNF. @@ -21451,14 +27926,16 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroup.json) required: true schema: $ref: "#/definitions/relationship" @@ -21483,11 +27960,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}: get: tags: @@ -21502,7 +27981,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/port-group" + $ref: "#/getDefinitions/port-group" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -21511,11 +27990,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: vnf-name in: query description: Name of VNF. @@ -21575,7 +28056,10 @@ paths: tags: - Network summary: create or update an existing port-group - description: create or update an existing port-group + description: | + Create or update an existing port-group. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroup consumes: - application/json @@ -21592,17 +28076,64 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: body in: body - description: port-group object that needs to be created or updated + description: port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroup.json) required: true schema: $ref: "#/definitions/port-group" + patch: + tags: + - Network + summary: update an existing port-group + description: | + Update an existing port-group + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVcesVcePortGroupsPortGroup + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-id + in: path + description: Unique ID of the interface + required: true + type: string + example: __INTERFACE-ID__ + - name: body + in: body + description: port-group object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/port-group" delete: tags: - Network @@ -21624,11 +28155,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-id in: path description: Unique ID of the interface required: true type: string + example: __INTERFACE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -21648,7 +28181,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/port-groups" + $ref: "#/getDefinitions/port-groups" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -21657,6 +28190,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -21718,19 +28252,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceLicensesLicense.json) required: true schema: $ref: "#/definitions/relationship" @@ -21755,16 +28292,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}: get: tags: @@ -21779,7 +28319,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/license" + $ref: "#/getDefinitions/license" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -21788,16 +28328,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ - name: vnf-name in: query description: Name of VNF. @@ -21842,7 +28385,10 @@ paths: tags: - Network summary: create or update an existing license - description: create or update an existing license + description: | + Create or update an existing license. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVcesVceLicensesLicense consumes: - application/json @@ -21859,22 +28405,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ - name: body in: body - description: license object that needs to be created or updated + description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceLicensesLicense.json) required: true schema: $ref: "#/definitions/license" + patch: + tags: + - Network + summary: update an existing license + description: | + Update an existing license + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVcesVceLicensesLicense + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: group-uuid + in: path + description: Unique ID for the license group the resource belongs to, should be uuid. + required: true + type: string + example: __GROUP-UUID__ + - name: resource-uuid + in: path + description: Unique ID of a license resource. + required: true + type: string + example: __RESOURCE-UUID__ + - name: body + in: body + description: license object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/license" delete: tags: - Network @@ -21896,16 +28496,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -21925,7 +28528,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/licenses" + $ref: "#/getDefinitions/licenses" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -21934,6 +28537,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -21995,19 +28599,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceEntitlementsEntitlement.json) required: true schema: $ref: "#/definitions/relationship" @@ -22032,16 +28639,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}: get: tags: @@ -22056,7 +28666,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/entitlement" + $ref: "#/getDefinitions/entitlement" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -22065,16 +28675,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ - name: vnf-name in: query description: Name of VNF. @@ -22119,7 +28732,10 @@ paths: tags: - Network summary: create or update an existing entitlement - description: create or update an existing entitlement + description: | + Create or update an existing entitlement. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVcesVceEntitlementsEntitlement consumes: - application/json @@ -22136,22 +28752,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ - name: body in: body - description: entitlement object that needs to be created or updated + description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceEntitlementsEntitlement.json) required: true schema: $ref: "#/definitions/entitlement" + patch: + tags: + - Network + summary: update an existing entitlement + description: | + Update an existing entitlement + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVcesVceEntitlementsEntitlement + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: group-uuid + in: path + description: Unique ID for the entitlement group the resource comes from, should be uuid. + required: true + type: string + example: __GROUP-UUID__ + - name: resource-uuid + in: path + description: Unique ID of an entitlement resource. + required: true + type: string + example: __RESOURCE-UUID__ + - name: body + in: body + description: entitlement object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/entitlement" delete: tags: - Network @@ -22173,16 +28843,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -22202,7 +28875,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/entitlements" + $ref: "#/getDefinitions/entitlements" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -22211,6 +28884,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -22272,9 +28946,10 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVce.json) required: true schema: $ref: "#/definitions/relationship" @@ -22299,6 +28974,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ /network/vces/vce/{vnf-id}: get: tags: @@ -22313,7 +28989,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vce" + $ref: "#/getDefinitions/vce" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -22322,6 +28998,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -22366,7 +29043,10 @@ paths: tags: - Network summary: create or update an existing vce - description: create or update an existing vce + description: | + Create or update an existing vce. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVcesVce consumes: - application/json @@ -22383,12 +29063,52 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: body in: body - description: vce object that needs to be created or updated + description: vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVce.json) required: true schema: $ref: "#/definitions/vce" + patch: + tags: + - Network + summary: update an existing vce + description: | + Update an existing vce + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVcesVce + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: body + in: body + description: vce object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vce" delete: tags: - Network @@ -22410,6 +29130,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -22429,7 +29150,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vces" + $ref: "#/getDefinitions/vces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/vnfcs/vnfc/{vnfc-name}/relationship-list/relationship: @@ -22453,9 +29174,10 @@ paths: description: Unique ID of vnfc. required: true type: string + example: __VNFC-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVnfcsVnfc.json) required: true schema: $ref: "#/definitions/relationship" @@ -22480,6 +29202,7 @@ paths: description: Unique ID of vnfc. required: true type: string + example: __VNFC-NAME__ /network/vnfcs/vnfc/{vnfc-name}: get: tags: @@ -22494,7 +29217,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vnfc" + $ref: "#/getDefinitions/vnfc" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -22503,6 +29226,7 @@ paths: description: Unique ID of vnfc. required: true type: string + example: __VNFC-NAME__ - name: vnfc-function-code in: query description: function code @@ -22540,7 +29264,10 @@ paths: tags: - Network summary: create or update an existing vnfc - description: create or update an existing vnfc + description: | + Create or update an existing vnfc. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkVnfcsVnfc consumes: - application/json @@ -22557,12 +29284,52 @@ paths: description: Unique ID of vnfc. required: true type: string + example: __VNFC-NAME__ - name: body in: body - description: vnfc object that needs to be created or updated + description: vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVnfcsVnfc.json) required: true schema: $ref: "#/definitions/vnfc" + patch: + tags: + - Network + summary: update an existing vnfc + description: | + Update an existing vnfc + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkVnfcsVnfc + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnfc-name + in: path + description: Unique ID of vnfc. + required: true + type: string + example: __VNFC-NAME__ + - name: body + in: body + description: vnfc object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vnfc" delete: tags: - Network @@ -22584,6 +29351,7 @@ paths: description: Unique ID of vnfc. required: true type: string + example: __VNFC-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -22603,7 +29371,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vnfcs" + $ref: "#/getDefinitions/vnfcs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/relationship-list/relationship: @@ -22627,14 +29395,16 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: subnet-id in: path description: Subnet ID, should be UUID. required: true type: string + example: __SUBNET-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSubnetsSubnet.json) required: true schema: $ref: "#/definitions/relationship" @@ -22659,11 +29429,13 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: subnet-id in: path description: Subnet ID, should be UUID. required: true type: string + example: __SUBNET-ID__ /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}: get: tags: @@ -22678,7 +29450,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/subnet" + $ref: "#/getDefinitions/subnet" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -22687,11 +29459,13 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: subnet-id in: path description: Subnet ID, should be UUID. required: true type: string + example: __SUBNET-ID__ - name: network-name in: query description: Name of the network, governed by some naming convention.. @@ -22746,7 +29520,10 @@ paths: tags: - Network summary: create or update an existing subnet - description: create or update an existing subnet + description: | + Create or update an existing subnet. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkL3NetworksL3NetworkSubnetsSubnet consumes: - application/json @@ -22763,17 +29540,64 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: subnet-id in: path description: Subnet ID, should be UUID. required: true type: string + example: __SUBNET-ID__ - name: body in: body - description: subnet object that needs to be created or updated + description: subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSubnetsSubnet.json) required: true schema: $ref: "#/definitions/subnet" + patch: + tags: + - Network + summary: update an existing subnet + description: | + Update an existing subnet + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkL3NetworksL3NetworkSubnetsSubnet + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: network-id + in: path + description: Network ID, should be uuid. Unique across A&AI. + required: true + type: string + example: __NETWORK-ID__ + - name: subnet-id + in: path + description: Subnet ID, should be UUID. + required: true + type: string + example: __SUBNET-ID__ + - name: body + in: body + description: subnet object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/subnet" delete: tags: - Network @@ -22795,11 +29619,13 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: subnet-id in: path description: Subnet ID, should be UUID. required: true type: string + example: __SUBNET-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -22819,7 +29645,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/subnets" + $ref: "#/getDefinitions/subnets" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -22828,6 +29654,7 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: network-name in: query description: Name of the network, governed by some naming convention.. @@ -22894,15 +29721,17 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: vlan-id-inner in: path description: id. required: true type: integer format: int64 + example: __VLAN-ID-INNER__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json) required: true schema: $ref: "#/definitions/relationship" @@ -22927,12 +29756,14 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: vlan-id-inner in: path description: id. required: true type: integer format: int64 + example: __VLAN-ID-INNER__ /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}: get: tags: @@ -22947,7 +29778,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/ctag-assignment" + $ref: "#/getDefinitions/ctag-assignment" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -22956,12 +29787,14 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: vlan-id-inner in: path description: id. required: true type: integer format: int64 + example: __VLAN-ID-INNER__ - name: network-name in: query description: Name of the network, governed by some naming convention.. @@ -23011,7 +29844,10 @@ paths: tags: - Network summary: create or update an existing ctag-assignment - description: create or update an existing ctag-assignment + description: | + Create or update an existing ctag-assignment. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment consumes: - application/json @@ -23028,18 +29864,66 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: vlan-id-inner in: path description: id. required: true type: integer format: int64 + example: __VLAN-ID-INNER__ - name: body in: body - description: ctag-assignment object that needs to be created or updated + description: ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json) required: true schema: $ref: "#/definitions/ctag-assignment" + patch: + tags: + - Network + summary: update an existing ctag-assignment + description: | + Update an existing ctag-assignment + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: network-id + in: path + description: Network ID, should be uuid. Unique across A&AI. + required: true + type: string + example: __NETWORK-ID__ + - name: vlan-id-inner + in: path + description: id. + required: true + type: integer + format: int64 + example: __VLAN-ID-INNER__ + - name: body + in: body + description: ctag-assignment object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/ctag-assignment" delete: tags: - Network @@ -23061,12 +29945,14 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: vlan-id-inner in: path description: id. required: true type: integer format: int64 + example: __VLAN-ID-INNER__ - name: resource-version in: query description: resource-version for concurrency @@ -23086,7 +29972,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/ctag-assignments" + $ref: "#/getDefinitions/ctag-assignments" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -23095,6 +29981,7 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: network-name in: query description: Name of the network, governed by some naming convention.. @@ -23161,14 +30048,16 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: segmentation-id in: path description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __SEGMENTATION-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json) required: true schema: $ref: "#/definitions/relationship" @@ -23193,11 +30082,13 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: segmentation-id in: path description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __SEGMENTATION-ID__ /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}: get: tags: @@ -23212,7 +30103,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/segmentation-assignment" + $ref: "#/getDefinitions/segmentation-assignment" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -23221,11 +30112,13 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: segmentation-id in: path description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __SEGMENTATION-ID__ - name: network-name in: query description: Name of the network, governed by some naming convention.. @@ -23275,7 +30168,10 @@ paths: tags: - Network summary: create or update an existing segmentation-assignment - description: create or update an existing segmentation-assignment + description: | + Create or update an existing segmentation-assignment. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment consumes: - application/json @@ -23292,17 +30188,64 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: segmentation-id in: path description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __SEGMENTATION-ID__ - name: body in: body - description: segmentation-assignment object that needs to be created or updated + description: segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json) required: true schema: $ref: "#/definitions/segmentation-assignment" + patch: + tags: + - Network + summary: update an existing segmentation-assignment + description: | + Update an existing segmentation-assignment + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: network-id + in: path + description: Network ID, should be uuid. Unique across A&AI. + required: true + type: string + example: __NETWORK-ID__ + - name: segmentation-id + in: path + description: Route Table Reference id, UUID assigned to this instance. + required: true + type: string + example: __SEGMENTATION-ID__ + - name: body + in: body + description: segmentation-assignment object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/segmentation-assignment" delete: tags: - Network @@ -23324,11 +30267,13 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: segmentation-id in: path description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __SEGMENTATION-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -23348,7 +30293,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/segmentation-assignments" + $ref: "#/getDefinitions/segmentation-assignments" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -23357,6 +30302,7 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: network-name in: query description: Name of the network, governed by some naming convention.. @@ -23423,9 +30369,10 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3Network.json) required: true schema: $ref: "#/definitions/relationship" @@ -23450,6 +30397,7 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ /network/l3-networks/l3-network/{network-id}: get: tags: @@ -23464,7 +30412,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-network" + $ref: "#/getDefinitions/l3-network" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -23473,6 +30421,7 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: network-name in: query description: Name of the network, governed by some naming convention.. @@ -23522,7 +30471,10 @@ paths: tags: - Network summary: create or update an existing l3-network - description: create or update an existing l3-network + description: | + Create or update an existing l3-network. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkL3NetworksL3Network consumes: - application/json @@ -23539,12 +30491,52 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: body in: body - description: l3-network object that needs to be created or updated + description: l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3Network.json) required: true schema: $ref: "#/definitions/l3-network" + patch: + tags: + - Network + summary: update an existing l3-network + description: | + Update an existing l3-network + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkL3NetworksL3Network + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: network-id + in: path + description: Network ID, should be uuid. Unique across A&AI. + required: true + type: string + example: __NETWORK-ID__ + - name: body + in: body + description: l3-network object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-network" delete: tags: - Network @@ -23566,6 +30558,7 @@ paths: description: Network ID, should be uuid. Unique across A&AI. required: true type: string + example: __NETWORK-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -23585,7 +30578,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-networks" + $ref: "#/getDefinitions/l3-networks" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/network-policies/network-policy/{network-policy-id}/relationship-list/relationship: @@ -23609,9 +30602,10 @@ paths: description: UUID representing unique key to this instance required: true type: string + example: __NETWORK-POLICY-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNetworkPoliciesNetworkPolicy.json) required: true schema: $ref: "#/definitions/relationship" @@ -23636,6 +30630,7 @@ paths: description: UUID representing unique key to this instance required: true type: string + example: __NETWORK-POLICY-ID__ /network/network-policies/network-policy/{network-policy-id}: get: tags: @@ -23650,7 +30645,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/network-policy" + $ref: "#/getDefinitions/network-policy" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -23659,6 +30654,7 @@ paths: description: UUID representing unique key to this instance required: true type: string + example: __NETWORK-POLICY-ID__ - name: network-policy-fqdn in: query description: Contrail FQDN for the policy @@ -23668,7 +30664,10 @@ paths: tags: - Network summary: create or update an existing network-policy - description: create or update an existing network-policy + description: | + Create or update an existing network-policy. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNetworkPoliciesNetworkPolicy consumes: - application/json @@ -23685,12 +30684,52 @@ paths: description: UUID representing unique key to this instance required: true type: string + example: __NETWORK-POLICY-ID__ - name: body in: body - description: network-policy object that needs to be created or updated + description: network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNetworkPoliciesNetworkPolicy.json) required: true schema: $ref: "#/definitions/network-policy" + patch: + tags: + - Network + summary: update an existing network-policy + description: | + Update an existing network-policy + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNetworkPoliciesNetworkPolicy + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: network-policy-id + in: path + description: UUID representing unique key to this instance + required: true + type: string + example: __NETWORK-POLICY-ID__ + - name: body + in: body + description: network-policy object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/network-policy" delete: tags: - Network @@ -23712,6 +30751,7 @@ paths: description: UUID representing unique key to this instance required: true type: string + example: __NETWORK-POLICY-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -23731,7 +30771,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/network-policies" + $ref: "#/getDefinitions/network-policies" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/generic-vnfs/generic-vnf/{vnf-id}/relationship-list/relationship: @@ -23755,9 +30795,10 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnf.json) required: true schema: $ref: "#/definitions/relationship" @@ -23782,6 +30823,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -23803,19 +30845,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -23840,16 +30885,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -23871,24 +30919,28 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -23913,21 +30965,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -23942,7 +30998,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -23951,21 +31007,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -24095,7 +31155,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -24112,27 +31175,88 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -24154,21 +31278,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -24195,24 +31323,28 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -24237,21 +31369,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -24266,7 +31402,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -24275,21 +31411,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -24419,7 +31559,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -24436,27 +31579,88 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -24478,21 +31682,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -24512,7 +31720,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -24521,16 +31729,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: vnf-name in: query description: Name of VNF. @@ -24644,7 +31855,10 @@ paths: tags: - Network summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -24661,22 +31875,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - Network + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - Network @@ -24698,16 +31966,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -24727,7 +31998,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -24736,11 +32007,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -24860,19 +32133,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -24897,16 +32173,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -24921,7 +32200,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -24930,16 +32209,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: vnf-name in: query description: Name of VNF. @@ -25062,7 +32344,10 @@ paths: tags: - Network summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -25079,22 +32364,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - Network + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - Network @@ -25116,16 +32455,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -25145,7 +32487,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -25154,11 +32496,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -25278,14 +32622,16 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -25310,11 +32656,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -25336,19 +32684,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -25373,16 +32724,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -25397,7 +32751,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -25406,16 +32760,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -25534,7 +32891,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -25551,22 +32911,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -25588,16 +33002,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -25624,19 +33041,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -25661,16 +33081,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -25685,7 +33108,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -25694,16 +33117,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -25822,7 +33248,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -25839,22 +33268,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -25876,16 +33359,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -25905,7 +33391,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -25914,11 +33400,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -26021,7 +33509,10 @@ paths: tags: - Network summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface consumes: - application/json @@ -26038,17 +33529,64 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - Network + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - Network @@ -26070,11 +33608,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -26094,7 +33634,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -26103,6 +33643,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -26207,14 +33748,16 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -26239,11 +33782,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -26265,24 +33810,28 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -26307,21 +33856,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -26343,29 +33896,34 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -26390,26 +33948,31 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -26424,7 +33987,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -26433,26 +33996,31 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -26592,7 +34160,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -26609,32 +34180,100 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -26656,26 +34295,31 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -26702,29 +34346,34 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -26749,26 +34398,31 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -26783,7 +34437,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -26792,26 +34446,31 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -26951,7 +34610,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -26968,32 +34630,100 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -27015,26 +34745,31 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -27054,7 +34789,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -27063,21 +34798,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: vnf-name in: query description: Name of VNF. @@ -27201,7 +34940,10 @@ paths: tags: - Network summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -27218,27 +34960,88 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - Network + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - Network @@ -27260,21 +35063,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -27294,7 +35101,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -27303,16 +35110,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -27442,24 +35252,28 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -27484,21 +35298,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -27513,7 +35331,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -27522,21 +35340,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: vnf-name in: query description: Name of VNF. @@ -27669,7 +35491,10 @@ paths: tags: - Network summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -27686,27 +35511,88 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - Network + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - Network @@ -27728,21 +35614,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -27762,7 +35652,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -27771,16 +35661,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -27910,19 +35803,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -27947,16 +35843,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -27978,24 +35877,28 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -28020,21 +35923,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -28049,7 +35956,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -28058,21 +35965,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -28201,7 +36112,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -28218,27 +36132,88 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -28260,21 +36235,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -28301,24 +36280,28 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -28343,21 +36326,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -28372,7 +36359,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -28381,21 +36368,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -28524,7 +36515,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -28541,27 +36535,88 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -28583,21 +36638,25 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -28617,7 +36676,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -28626,16 +36685,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -28748,7 +36810,10 @@ paths: tags: - Network summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface consumes: - application/json @@ -28765,22 +36830,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - Network + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - Network @@ -28802,16 +36921,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -28831,7 +36953,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -28840,11 +36962,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -28952,7 +37076,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-interface" + $ref: "#/getDefinitions/lag-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -28961,11 +37085,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -29063,7 +37189,10 @@ paths: tags: - Network summary: create or update an existing lag-interface - description: create or update an existing lag-interface + description: | + Create or update an existing lag-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface consumes: - application/json @@ -29080,17 +37209,64 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: lag-interface object that needs to be created or updated + description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json) required: true schema: $ref: "#/definitions/lag-interface" + patch: + tags: + - Network + summary: update an existing lag-interface + description: | + Update an existing lag-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: lag-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/lag-interface" delete: tags: - Network @@ -29112,11 +37288,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -29136,7 +37314,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-interfaces" + $ref: "#/getDefinitions/lag-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -29145,6 +37323,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -29249,14 +37428,16 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vf-module-id in: path description: Unique ID of vf-module. required: true type: string + example: __VF-MODULE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfVfModulesVfModule.json) required: true schema: $ref: "#/definitions/relationship" @@ -29281,11 +37462,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vf-module-id in: path description: Unique ID of vf-module. required: true type: string + example: __VF-MODULE-ID__ /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}: get: tags: @@ -29300,7 +37483,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vf-module" + $ref: "#/getDefinitions/vf-module" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -29309,11 +37492,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vf-module-id in: path description: Unique ID of vf-module. required: true type: string + example: __VF-MODULE-ID__ - name: vnf-name in: query description: Name of VNF. @@ -29436,7 +37621,10 @@ paths: tags: - Network summary: create or update an existing vf-module - description: create or update an existing vf-module + description: | + Create or update an existing vf-module. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfVfModulesVfModule consumes: - application/json @@ -29453,17 +37641,64 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vf-module-id in: path description: Unique ID of vf-module. required: true type: string + example: __VF-MODULE-ID__ - name: body in: body - description: vf-module object that needs to be created or updated + description: vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfVfModulesVfModule.json) required: true schema: $ref: "#/definitions/vf-module" + patch: + tags: + - Network + summary: update an existing vf-module + description: | + Update an existing vf-module + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfVfModulesVfModule + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: vf-module-id + in: path + description: Unique ID of vf-module. + required: true + type: string + example: __VF-MODULE-ID__ + - name: body + in: body + description: vf-module object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vf-module" delete: tags: - Network @@ -29485,11 +37720,13 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vf-module-id in: path description: Unique ID of vf-module. required: true type: string + example: __VF-MODULE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -29509,7 +37746,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vf-modules" + $ref: "#/getDefinitions/vf-modules" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -29518,6 +37755,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -29622,19 +37860,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLicensesLicense.json) required: true schema: $ref: "#/definitions/relationship" @@ -29659,16 +37900,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}: get: tags: @@ -29683,7 +37927,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/license" + $ref: "#/getDefinitions/license" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -29692,16 +37936,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ - name: vnf-name in: query description: Name of VNF. @@ -29789,7 +38036,10 @@ paths: tags: - Network summary: create or update an existing license - description: create or update an existing license + description: | + Create or update an existing license. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfLicensesLicense consumes: - application/json @@ -29806,22 +38056,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ - name: body in: body - description: license object that needs to be created or updated + description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLicensesLicense.json) required: true schema: $ref: "#/definitions/license" + patch: + tags: + - Network + summary: update an existing license + description: | + Update an existing license + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfLicensesLicense + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: group-uuid + in: path + description: Unique ID for the license group the resource belongs to, should be uuid. + required: true + type: string + example: __GROUP-UUID__ + - name: resource-uuid + in: path + description: Unique ID of a license resource. + required: true + type: string + example: __RESOURCE-UUID__ + - name: body + in: body + description: license object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/license" delete: tags: - Network @@ -29843,16 +38147,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the license group the resource belongs to, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of a license resource. required: true type: string + example: __RESOURCE-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -29872,7 +38179,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/licenses" + $ref: "#/getDefinitions/licenses" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -29881,6 +38188,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -29985,19 +38293,22 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json) required: true schema: $ref: "#/definitions/relationship" @@ -30022,16 +38333,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}: get: tags: @@ -30046,7 +38360,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/entitlement" + $ref: "#/getDefinitions/entitlement" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -30055,16 +38369,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ - name: vnf-name in: query description: Name of VNF. @@ -30152,7 +38469,10 @@ paths: tags: - Network summary: create or update an existing entitlement - description: create or update an existing entitlement + description: | + Create or update an existing entitlement. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement consumes: - application/json @@ -30169,22 +38489,76 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ - name: body in: body - description: entitlement object that needs to be created or updated + description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json) required: true schema: $ref: "#/definitions/entitlement" + patch: + tags: + - Network + summary: update an existing entitlement + description: | + Update an existing entitlement + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: group-uuid + in: path + description: Unique ID for the entitlement group the resource comes from, should be uuid. + required: true + type: string + example: __GROUP-UUID__ + - name: resource-uuid + in: path + description: Unique ID of an entitlement resource. + required: true + type: string + example: __RESOURCE-UUID__ + - name: body + in: body + description: entitlement object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/entitlement" delete: tags: - Network @@ -30206,16 +38580,19 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: group-uuid in: path description: Unique ID for the entitlement group the resource comes from, should be uuid. required: true type: string + example: __GROUP-UUID__ - name: resource-uuid in: path description: Unique ID of an entitlement resource. required: true type: string + example: __RESOURCE-UUID__ - name: resource-version in: query description: resource-version for concurrency @@ -30235,7 +38612,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/entitlements" + $ref: "#/getDefinitions/entitlements" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -30244,6 +38621,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -30341,7 +38719,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/generic-vnf" + $ref: "#/getDefinitions/generic-vnf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -30350,6 +38728,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: vnf-name in: query description: Name of VNF. @@ -30437,7 +38816,10 @@ paths: tags: - Network summary: create or update an existing generic-vnf - description: create or update an existing generic-vnf + description: | + Create or update an existing generic-vnf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkGenericVnfsGenericVnf consumes: - application/json @@ -30454,12 +38836,52 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: body in: body - description: generic-vnf object that needs to be created or updated + description: generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnf.json) required: true schema: $ref: "#/definitions/generic-vnf" + patch: + tags: + - Network + summary: update an existing generic-vnf + description: | + Update an existing generic-vnf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkGenericVnfsGenericVnf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id + in: path + description: Unique id of VNF. This is unique across the graph. + required: true + type: string + example: __VNF-ID__ + - name: body + in: body + description: generic-vnf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/generic-vnf" delete: tags: - Network @@ -30481,6 +38903,7 @@ paths: description: Unique id of VNF. This is unique across the graph. required: true type: string + example: __VNF-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -30500,7 +38923,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/generic-vnfs" + $ref: "#/getDefinitions/generic-vnfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/lag-links/lag-link/{link-name}/relationship-list/relationship: @@ -30524,9 +38947,10 @@ paths: description: Alphabetical concatenation of lag-interface names required: true type: string + example: __LINK-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLagLinksLagLink.json) required: true schema: $ref: "#/definitions/relationship" @@ -30551,6 +38975,7 @@ paths: description: Alphabetical concatenation of lag-interface names required: true type: string + example: __LINK-NAME__ /network/lag-links/lag-link/{link-name}: get: tags: @@ -30565,7 +38990,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-link" + $ref: "#/getDefinitions/lag-link" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -30574,11 +38999,15 @@ paths: description: Alphabetical concatenation of lag-interface names required: true type: string + example: __LINK-NAME__ put: tags: - Network summary: create or update an existing lag-link - description: create or update an existing lag-link + description: | + Create or update an existing lag-link. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkLagLinksLagLink consumes: - application/json @@ -30595,12 +39024,52 @@ paths: description: Alphabetical concatenation of lag-interface names required: true type: string + example: __LINK-NAME__ - name: body in: body - description: lag-link object that needs to be created or updated + description: lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLagLinksLagLink.json) required: true schema: $ref: "#/definitions/lag-link" + patch: + tags: + - Network + summary: update an existing lag-link + description: | + Update an existing lag-link + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkLagLinksLagLink + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: link-name + in: path + description: Alphabetical concatenation of lag-interface names + required: true + type: string + example: __LINK-NAME__ + - name: body + in: body + description: lag-link object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/lag-link" delete: tags: - Network @@ -30622,6 +39091,7 @@ paths: description: Alphabetical concatenation of lag-interface names required: true type: string + example: __LINK-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -30641,7 +39111,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-links" + $ref: "#/getDefinitions/lag-links" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/newvces/newvce/{vnf-id2}/relationship-list/relationship: @@ -30665,9 +39135,10 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvce.json) required: true schema: $ref: "#/definitions/relationship" @@ -30692,6 +39163,7 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -30713,19 +39185,22 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -30750,16 +39225,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -30781,24 +39259,28 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -30823,21 +39305,25 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -30852,7 +39338,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -30861,21 +39347,25 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -30947,7 +39437,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -30964,27 +39457,88 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id2 + in: path + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + required: true + type: string + example: __VNF-ID2__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -31006,21 +39560,25 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -31047,24 +39605,28 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -31089,21 +39651,25 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -31118,7 +39684,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -31127,21 +39693,25 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -31213,7 +39783,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -31230,27 +39803,88 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id2 + in: path + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + required: true + type: string + example: __VNF-ID2__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -31272,21 +39906,25 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -31306,7 +39944,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -31315,16 +39953,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: vnf-name in: query description: Name of VNF. @@ -31380,7 +40021,10 @@ paths: tags: - Network summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -31397,22 +40041,76 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - Network + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id2 + in: path + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + required: true + type: string + example: __VNF-ID2__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - Network @@ -31434,16 +40132,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -31463,7 +40164,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -31472,11 +40173,13 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -31538,19 +40241,22 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -31575,16 +40281,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -31599,7 +40308,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -31608,16 +40317,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: vnf-name in: query description: Name of VNF. @@ -31682,7 +40394,10 @@ paths: tags: - Network summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -31699,22 +40414,76 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - Network + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id2 + in: path + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + required: true + type: string + example: __VNF-ID2__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - Network @@ -31736,16 +40505,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -31765,7 +40537,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -31774,11 +40546,13 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -31840,14 +40614,16 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -31872,11 +40648,13 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -31898,19 +40676,22 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -31935,16 +40716,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -31959,7 +40743,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -31968,16 +40752,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -32038,7 +40825,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -32055,22 +40845,76 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id2 + in: path + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + required: true + type: string + example: __VNF-ID2__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -32092,16 +40936,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -32128,19 +40975,22 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -32165,16 +41015,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -32189,7 +41042,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -32198,16 +41051,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: vnf-name in: query description: Name of VNF. @@ -32268,7 +41124,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -32285,22 +41144,76 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id2 + in: path + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + required: true + type: string + example: __VNF-ID2__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -32322,16 +41235,19 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -32351,7 +41267,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -32360,11 +41276,13 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vnf-name in: query description: Name of VNF. @@ -32409,7 +41327,10 @@ paths: tags: - Network summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterface consumes: - application/json @@ -32426,17 +41347,64 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - Network + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id2 + in: path + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + required: true + type: string + example: __VNF-ID2__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - Network @@ -32458,11 +41426,13 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -32482,7 +41452,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -32491,6 +41461,7 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: vnf-name in: query description: Name of VNF. @@ -32530,7 +41501,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/newvce" + $ref: "#/getDefinitions/newvce" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -32539,6 +41510,7 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: vnf-name in: query description: Name of VNF. @@ -32568,7 +41540,10 @@ paths: tags: - Network summary: create or update an existing newvce - description: create or update an existing newvce + description: | + Create or update an existing newvce. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkNewvcesNewvce consumes: - application/json @@ -32585,12 +41560,52 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: body in: body - description: newvce object that needs to be created or updated + description: newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvce.json) required: true schema: $ref: "#/definitions/newvce" + patch: + tags: + - Network + summary: update an existing newvce + description: | + Update an existing newvce + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkNewvcesNewvce + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: vnf-id2 + in: path + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + required: true + type: string + example: __VNF-ID2__ + - name: body + in: body + description: newvce object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/newvce" delete: tags: - Network @@ -32612,6 +41627,7 @@ paths: description: Unique id of VNF, can't use same attribute name right now until we promote this new object required: true type: string + example: __VNF-ID2__ - name: resource-version in: query description: resource-version for concurrency @@ -32631,7 +41647,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/newvces" + $ref: "#/getDefinitions/newvces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/pnfs/pnf/{pnf-name}/relationship-list/relationship: @@ -32655,9 +41671,10 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnf.json) required: true schema: $ref: "#/definitions/relationship" @@ -32682,6 +41699,7 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship: put: tags: @@ -32703,14 +41721,16 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -32735,11 +41755,13 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -32761,24 +41783,28 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -32803,21 +41829,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -32839,29 +41869,34 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -32886,26 +41921,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -32920,7 +41960,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -32929,26 +41969,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -33005,7 +42050,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -33022,32 +42070,100 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -33069,26 +42185,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -33115,29 +42236,34 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -33162,26 +42288,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -33196,7 +42327,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -33205,26 +42336,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -33281,7 +42417,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -33298,32 +42437,100 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -33345,26 +42552,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -33384,7 +42596,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -33393,21 +42605,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -33448,7 +42664,10 @@ paths: tags: - Network summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -33465,27 +42684,88 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - Network + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - Network @@ -33507,21 +42787,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -33541,7 +42825,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -33550,16 +42834,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -33606,24 +42893,28 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -33648,21 +42939,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -33677,7 +42972,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -33686,21 +42981,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -33750,7 +43049,10 @@ paths: tags: - Network summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -33767,27 +43069,88 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - Network + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - Network @@ -33809,21 +43172,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -33843,7 +43210,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -33852,16 +43219,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -33908,19 +43278,22 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -33945,16 +43318,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -33976,24 +43352,28 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -34018,21 +43398,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -34047,7 +43431,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -34056,21 +43440,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -34116,7 +43504,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -34133,27 +43524,88 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -34175,21 +43627,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -34216,24 +43672,28 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -34258,21 +43718,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -34287,7 +43751,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -34296,21 +43760,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -34356,7 +43824,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -34373,27 +43844,88 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -34415,21 +43947,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -34449,7 +43985,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -34458,16 +43994,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -34497,7 +44036,10 @@ paths: tags: - Network summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface consumes: - application/json @@ -34514,22 +44056,76 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - Network + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - Network @@ -34551,16 +44147,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -34580,7 +44179,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -34589,11 +44188,13 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -34618,7 +44219,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/p-interface" + $ref: "#/getDefinitions/p-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -34627,11 +44228,13 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -34646,7 +44249,10 @@ paths: tags: - Network summary: create or update an existing p-interface - description: create or update an existing p-interface + description: | + Create or update an existing p-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterface consumes: - application/json @@ -34663,17 +44269,64 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: p-interface object that needs to be created or updated + description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterface.json) required: true schema: $ref: "#/definitions/p-interface" + patch: + tags: + - Network + summary: update an existing p-interface + description: | + Update an existing p-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfPInterfacesPInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the physical interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: p-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/p-interface" delete: tags: - Network @@ -34695,11 +44348,13 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the physical interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -34719,7 +44374,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/p-interfaces" + $ref: "#/getDefinitions/p-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -34728,6 +44383,7 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -34754,14 +44410,16 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -34786,11 +44444,13 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship: put: tags: @@ -34812,24 +44472,28 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/relationship" @@ -34854,21 +44518,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -34890,29 +44558,34 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -34937,26 +44610,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -34971,7 +44649,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -34980,26 +44658,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -35061,7 +44744,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList consumes: - application/json @@ -35078,32 +44764,100 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -35125,26 +44879,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -35171,29 +44930,34 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -35218,26 +44982,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -35252,7 +45021,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -35261,26 +45030,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -35342,7 +45116,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList consumes: - application/json @@ -35359,32 +45136,100 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -35406,26 +45251,31 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -35445,7 +45295,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlan" + $ref: "#/getDefinitions/vlan" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -35454,21 +45304,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -35514,7 +45368,10 @@ paths: tags: - Network summary: create or update an existing vlan - description: create or update an existing vlan + description: | + Create or update an existing vlan. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan consumes: - application/json @@ -35531,27 +45388,88 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: body in: body - description: vlan object that needs to be created or updated + description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json) required: true schema: $ref: "#/definitions/vlan" + patch: + tags: + - Network + summary: update an existing vlan + description: | + Update an existing vlan + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: vlan-interface + in: path + description: String that identifies the interface + required: true + type: string + example: __VLAN-INTERFACE__ + - name: body + in: body + description: vlan object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vlan" delete: tags: - Network @@ -35573,21 +45491,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: vlan-interface in: path description: String that identifies the interface required: true type: string + example: __VLAN-INTERFACE__ - name: resource-version in: query description: resource-version for concurrency @@ -35607,7 +45529,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vlans" + $ref: "#/getDefinitions/vlans" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -35616,16 +45538,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -35677,24 +45602,28 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/relationship" @@ -35719,21 +45648,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}: get: tags: @@ -35748,7 +45681,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vf" + $ref: "#/getDefinitions/sriov-vf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -35757,21 +45690,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -35826,7 +45763,10 @@ paths: tags: - Network summary: create or update an existing sriov-vf - description: create or update an existing sriov-vf + description: | + Create or update an existing sriov-vf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf consumes: - application/json @@ -35843,27 +45783,88 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: body in: body - description: sriov-vf object that needs to be created or updated + description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json) required: true schema: $ref: "#/definitions/sriov-vf" + patch: + tags: + - Network + summary: update an existing sriov-vf + description: | + Update an existing sriov-vf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: pci-id + in: path + description: PCI ID used to identify the sriov-vf + required: true + type: string + example: __PCI-ID__ + - name: body + in: body + description: sriov-vf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/sriov-vf" delete: tags: - Network @@ -35885,21 +45886,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: pci-id in: path description: PCI ID used to identify the sriov-vf required: true type: string + example: __PCI-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -35919,7 +45924,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/sriov-vfs" + $ref: "#/getDefinitions/sriov-vfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -35928,16 +45933,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -35989,19 +45997,22 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/relationship" @@ -36026,16 +46037,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship: put: tags: @@ -36057,24 +46071,28 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -36099,21 +46117,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}: get: tags: @@ -36128,7 +46150,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv4-address-list" + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -36137,21 +46159,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -36202,7 +46228,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv4-address-list - description: create or update an existing l3-interface-ipv4-address-list + description: | + Create or update an existing l3-interface-ipv4-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList consumes: - application/json @@ -36219,27 +46248,88 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: body in: body - description: l3-interface-ipv4-address-list object that needs to be created or updated + description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv4-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv4-address-list + description: | + Update an existing l3-interface-ipv4-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv4-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv4-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv4-address-list" delete: tags: - Network @@ -36261,21 +46351,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv4-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV4-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -36302,24 +46396,28 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/relationship" @@ -36344,21 +46442,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}: get: tags: @@ -36373,7 +46475,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l3-interface-ipv6-address-list" + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -36382,21 +46484,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -36447,7 +46553,10 @@ paths: tags: - Network summary: create or update an existing l3-interface-ipv6-address-list - description: create or update an existing l3-interface-ipv6-address-list + description: | + Create or update an existing l3-interface-ipv6-address-list. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList consumes: - application/json @@ -36464,27 +46573,88 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: body in: body - description: l3-interface-ipv6-address-list object that needs to be created or updated + description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json) required: true schema: $ref: "#/definitions/l3-interface-ipv6-address-list" + patch: + tags: + - Network + summary: update an existing l3-interface-ipv6-address-list + description: | + Update an existing l3-interface-ipv6-address-list + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: l3-interface-ipv6-address + in: path + description: IP address + required: true + type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ + - name: body + in: body + description: l3-interface-ipv6-address-list object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l3-interface-ipv6-address-list" delete: tags: - Network @@ -36506,21 +46676,25 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: l3-interface-ipv6-address in: path description: IP address required: true type: string + example: __L3-INTERFACE-IPV6-ADDRESS__ - name: resource-version in: query description: resource-version for concurrency @@ -36540,7 +46714,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -36549,16 +46723,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -36593,7 +46770,10 @@ paths: tags: - Network summary: create or update an existing l-interface - description: create or update an existing l-interface + description: | + Create or update an existing l-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface consumes: - application/json @@ -36610,22 +46790,76 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: l-interface object that needs to be created or updated + description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json) required: true schema: $ref: "#/definitions/l-interface" + patch: + tags: + - Network + summary: update an existing l-interface + description: | + Update an existing l-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: interface-name + in: path + description: Name given to the interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: l-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/l-interface" delete: tags: - Network @@ -36647,16 +46881,19 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: interface-name in: path description: Name given to the interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -36676,7 +46913,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/l-interfaces" + $ref: "#/getDefinitions/l-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -36685,11 +46922,13 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -36719,7 +46958,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-interface" + $ref: "#/getDefinitions/lag-interface" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -36728,11 +46967,13 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -36752,7 +46993,10 @@ paths: tags: - Network summary: create or update an existing lag-interface - description: create or update an existing lag-interface + description: | + Create or update an existing lag-interface. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterface consumes: - application/json @@ -36769,17 +47013,64 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: body in: body - description: lag-interface object that needs to be created or updated + description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterface.json) required: true schema: $ref: "#/definitions/lag-interface" + patch: + tags: + - Network + summary: update an existing lag-interface + description: | + Update an existing lag-interface + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterface + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: interface-name + in: path + description: Name that identifies the link aggregate interface + required: true + type: string + example: __INTERFACE-NAME__ + - name: body + in: body + description: lag-interface object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/lag-interface" delete: tags: - Network @@ -36801,11 +47092,13 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: interface-name in: path description: Name that identifies the link aggregate interface required: true type: string + example: __INTERFACE-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -36825,7 +47118,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/lag-interfaces" + $ref: "#/getDefinitions/lag-interfaces" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -36834,6 +47127,7 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -36853,7 +47147,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/pnf" + $ref: "#/getDefinitions/pnf" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -36862,6 +47156,7 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: inv-status in: query description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. @@ -36871,7 +47166,10 @@ paths: tags: - Network summary: create or update an existing pnf - description: create or update an existing pnf + description: | + Create or update an existing pnf. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPnfsPnf consumes: - application/json @@ -36888,12 +47186,52 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: body in: body - description: pnf object that needs to be created or updated + description: pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnf.json) required: true schema: $ref: "#/definitions/pnf" + patch: + tags: + - Network + summary: update an existing pnf + description: | + Update an existing pnf + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPnfsPnf + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: pnf-name + in: path + description: unique name of Physical Network Function. + required: true + type: string + example: __PNF-NAME__ + - name: body + in: body + description: pnf object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/pnf" delete: tags: - Network @@ -36915,6 +47253,7 @@ paths: description: unique name of Physical Network Function. required: true type: string + example: __PNF-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -36934,7 +47273,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/pnfs" + $ref: "#/getDefinitions/pnfs" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/physical-links/physical-link/{link-name}/relationship-list/relationship: @@ -36958,9 +47297,10 @@ paths: description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ required: true type: string + example: __LINK-NAME__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPhysicalLinksPhysicalLink.json) required: true schema: $ref: "#/definitions/relationship" @@ -36985,6 +47325,7 @@ paths: description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ required: true type: string + example: __LINK-NAME__ /network/physical-links/physical-link/{link-name}: get: tags: @@ -36999,7 +47340,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/physical-link" + $ref: "#/getDefinitions/physical-link" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -37008,6 +47349,7 @@ paths: description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ required: true type: string + example: __LINK-NAME__ - name: circuit-id in: query description: Circuit it @@ -37017,7 +47359,10 @@ paths: tags: - Network summary: create or update an existing physical-link - description: create or update an existing physical-link + description: | + Create or update an existing physical-link. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkPhysicalLinksPhysicalLink consumes: - application/json @@ -37034,12 +47379,52 @@ paths: description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ required: true type: string + example: __LINK-NAME__ - name: body in: body - description: physical-link object that needs to be created or updated + description: physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPhysicalLinksPhysicalLink.json) required: true schema: $ref: "#/definitions/physical-link" + patch: + tags: + - Network + summary: update an existing physical-link + description: | + Update an existing physical-link + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkPhysicalLinksPhysicalLink + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: link-name + in: path + description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ + required: true + type: string + example: __LINK-NAME__ + - name: body + in: body + description: physical-link object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/physical-link" delete: tags: - Network @@ -37061,6 +47446,7 @@ paths: description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ required: true type: string + example: __LINK-NAME__ - name: resource-version in: query description: resource-version for concurrency @@ -37080,7 +47466,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/physical-links" + $ref: "#/getDefinitions/physical-links" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/relationship-list/relationship: @@ -37104,9 +47490,10 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfiguration.json) required: true schema: $ref: "#/definitions/relationship" @@ -37131,6 +47518,7 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}/relationship-list/relationship: put: tags: @@ -37152,14 +47540,16 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ - name: vig-address-type in: path description: indicates whether the VIG is for AVPN or INTERNET required: true type: string + example: __VIG-ADDRESS-TYPE__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json) required: true schema: $ref: "#/definitions/relationship" @@ -37184,11 +47574,13 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ - name: vig-address-type in: path description: indicates whether the VIG is for AVPN or INTERNET required: true type: string + example: __VIG-ADDRESS-TYPE__ /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}: get: tags: @@ -37203,7 +47595,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vig-server" + $ref: "#/getDefinitions/vig-server" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -37212,16 +47604,21 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ - name: vig-address-type in: path description: indicates whether the VIG is for AVPN or INTERNET required: true type: string + example: __VIG-ADDRESS-TYPE__ put: tags: - Network summary: create or update an existing vig-server - description: create or update an existing vig-server + description: | + Create or update an existing vig-server. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer consumes: - application/json @@ -37238,17 +47635,64 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ - name: vig-address-type in: path description: indicates whether the VIG is for AVPN or INTERNET required: true type: string + example: __VIG-ADDRESS-TYPE__ - name: body in: body - description: vig-server object that needs to be created or updated + description: vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json) required: true schema: $ref: "#/definitions/vig-server" + patch: + tags: + - Network + summary: update an existing vig-server + description: | + Update an existing vig-server + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: ipsec-configuration-id + in: path + description: UUID of this configuration + required: true + type: string + example: __IPSEC-CONFIGURATION-ID__ + - name: vig-address-type + in: path + description: indicates whether the VIG is for AVPN or INTERNET + required: true + type: string + example: __VIG-ADDRESS-TYPE__ + - name: body + in: body + description: vig-server object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/vig-server" delete: tags: - Network @@ -37270,11 +47714,13 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ - name: vig-address-type in: path description: indicates whether the VIG is for AVPN or INTERNET required: true type: string + example: __VIG-ADDRESS-TYPE__ - name: resource-version in: query description: resource-version for concurrency @@ -37294,7 +47740,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/vig-servers" + $ref: "#/getDefinitions/vig-servers" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -37303,6 +47749,7 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}: get: tags: @@ -37317,7 +47764,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/ipsec-configuration" + $ref: "#/getDefinitions/ipsec-configuration" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -37326,11 +47773,15 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ put: tags: - Network summary: create or update an existing ipsec-configuration - description: create or update an existing ipsec-configuration + description: | + Create or update an existing ipsec-configuration. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfiguration consumes: - application/json @@ -37347,12 +47798,52 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ - name: body in: body - description: ipsec-configuration object that needs to be created or updated + description: ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfiguration.json) required: true schema: $ref: "#/definitions/ipsec-configuration" + patch: + tags: + - Network + summary: update an existing ipsec-configuration + description: | + Update an existing ipsec-configuration + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkIpsecConfigurationsIpsecConfiguration + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: ipsec-configuration-id + in: path + description: UUID of this configuration + required: true + type: string + example: __IPSEC-CONFIGURATION-ID__ + - name: body + in: body + description: ipsec-configuration object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/ipsec-configuration" delete: tags: - Network @@ -37374,6 +47865,7 @@ paths: description: UUID of this configuration required: true type: string + example: __IPSEC-CONFIGURATION-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -37393,7 +47885,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/ipsec-configurations" + $ref: "#/getDefinitions/ipsec-configurations" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/route-table-references/route-table-reference/{route-table-reference-id}/relationship-list/relationship: @@ -37417,9 +47909,10 @@ paths: description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __ROUTE-TABLE-REFERENCE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkRouteTableReferencesRouteTableReference.json) required: true schema: $ref: "#/definitions/relationship" @@ -37444,6 +47937,7 @@ paths: description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __ROUTE-TABLE-REFERENCE-ID__ /network/route-table-references/route-table-reference/{route-table-reference-id}: get: tags: @@ -37458,7 +47952,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/route-table-reference" + $ref: "#/getDefinitions/route-table-reference" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -37467,6 +47961,7 @@ paths: description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __ROUTE-TABLE-REFERENCE-ID__ - name: route-table-reference-fqdn in: query description: FQDN entry in the route table. @@ -37476,7 +47971,10 @@ paths: tags: - Network summary: create or update an existing route-table-reference - description: create or update an existing route-table-reference + description: | + Create or update an existing route-table-reference. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkRouteTableReferencesRouteTableReference consumes: - application/json @@ -37493,12 +47991,52 @@ paths: description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __ROUTE-TABLE-REFERENCE-ID__ - name: body in: body - description: route-table-reference object that needs to be created or updated + description: route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkRouteTableReferencesRouteTableReference.json) required: true schema: $ref: "#/definitions/route-table-reference" + patch: + tags: + - Network + summary: update an existing route-table-reference + description: | + Update an existing route-table-reference + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkRouteTableReferencesRouteTableReference + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: route-table-reference-id + in: path + description: Route Table Reference id, UUID assigned to this instance. + required: true + type: string + example: __ROUTE-TABLE-REFERENCE-ID__ + - name: body + in: body + description: route-table-reference object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/route-table-reference" delete: tags: - Network @@ -37520,6 +48058,7 @@ paths: description: Route Table Reference id, UUID assigned to this instance. required: true type: string + example: __ROUTE-TABLE-REFERENCE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -37539,7 +48078,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/route-table-references" + $ref: "#/getDefinitions/route-table-references" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/instance-groups/instance-group/{id}/relationship-list/relationship: @@ -37563,9 +48102,10 @@ paths: description: Instance Group ID, UUID assigned to this instance. required: true type: string + example: __ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkInstanceGroupsInstanceGroup.json) required: true schema: $ref: "#/definitions/relationship" @@ -37590,6 +48130,7 @@ paths: description: Instance Group ID, UUID assigned to this instance. required: true type: string + example: __ID__ /network/instance-groups/instance-group/{id}: get: tags: @@ -37604,7 +48145,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/instance-group" + $ref: "#/getDefinitions/instance-group" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -37613,6 +48154,7 @@ paths: description: Instance Group ID, UUID assigned to this instance. required: true type: string + example: __ID__ - name: description in: query description: Descriptive text to help identify the usage of this instance-group @@ -37632,7 +48174,10 @@ paths: tags: - Network summary: create or update an existing instance-group - description: create or update an existing instance-group + description: | + Create or update an existing instance-group. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkInstanceGroupsInstanceGroup consumes: - application/json @@ -37649,12 +48194,52 @@ paths: description: Instance Group ID, UUID assigned to this instance. required: true type: string + example: __ID__ - name: body in: body - description: instance-group object that needs to be created or updated + description: instance-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkInstanceGroupsInstanceGroup.json) required: true schema: $ref: "#/definitions/instance-group" + patch: + tags: + - Network + summary: update an existing instance-group + description: | + Update an existing instance-group + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkInstanceGroupsInstanceGroup + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: id + in: path + description: Instance Group ID, UUID assigned to this instance. + required: true + type: string + example: __ID__ + - name: body + in: body + description: instance-group object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/instance-group" delete: tags: - Network @@ -37676,6 +48261,7 @@ paths: description: Instance Group ID, UUID assigned to this instance. required: true type: string + example: __ID__ - name: resource-version in: query description: resource-version for concurrency @@ -37695,7 +48281,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/instance-groups" + $ref: "#/getDefinitions/instance-groups" "default": description: Response codes found in [response codes](https://wiki.onap.org/). /network/zones/zone/{zone-id}/relationship-list/relationship: @@ -37719,9 +48305,10 @@ paths: description: Code assigned by AIC to the zone required: true type: string + example: __ZONE-ID__ - name: body in: body - description: relationship object that needs to be created or updated + description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkZonesZone.json) required: true schema: $ref: "#/definitions/relationship" @@ -37746,6 +48333,7 @@ paths: description: Code assigned by AIC to the zone required: true type: string + example: __ZONE-ID__ /network/zones/zone/{zone-id}: get: tags: @@ -37760,7 +48348,7 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/zone" + $ref: "#/getDefinitions/zone" "default": description: Response codes found in [response codes](https://wiki.onap.org/). parameters: @@ -37769,6 +48357,7 @@ paths: description: Code assigned by AIC to the zone required: true type: string + example: __ZONE-ID__ - name: design-type in: query description: Design of zone [Medium/Large?] @@ -37783,7 +48372,10 @@ paths: tags: - Network summary: create or update an existing zone - description: create or update an existing zone + description: | + Create or update an existing zone. + # + Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below operationId: createOrUpdateNetworkZonesZone consumes: - application/json @@ -37800,12 +48392,52 @@ paths: description: Code assigned by AIC to the zone required: true type: string + example: __ZONE-ID__ - name: body in: body - description: zone object that needs to be created or updated + description: zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkZonesZone.json) required: true schema: $ref: "#/definitions/zone" + patch: + tags: + - Network + summary: update an existing zone + description: | + Update an existing zone + # + Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations. + The PUT operation will entirely replace an existing object. + The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs. + # + Other differences between PUT and PATCH are: + # + - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values. + - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent. + - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this. + operationId: UpdateNetworkZonesZone + consumes: + - application/json + - application/xml + produces: + - application/json + - application/xml + responses: + "default": + description: Response codes found in [response codes](https://wiki.onap.org/). + parameters: + - name: zone-id + in: path + description: Code assigned by AIC to the zone + required: true + type: string + example: __ZONE-ID__ + - name: body + in: body + description: zone object that needs to be created or updated. + required: true + schema: + $ref: "#/patchDefinitions/zone" delete: tags: - Network @@ -37827,6 +48459,7 @@ paths: description: Code assigned by AIC to the zone required: true type: string + example: __ZONE-ID__ - name: resource-version in: query description: resource-version for concurrency @@ -37846,24 +48479,30 @@ paths: "200": description: successful operation schema: - $ref: "#/definitions/zones" + $ref: "#/getDefinitions/zones" "default": description: Response codes found in [response codes](https://wiki.onap.org/). definitions: - search: + aai-internal: properties: - edge-tag-query-result: - type: object - $ref: "#/definitions/edge-tag-query-result" - edge-tag-query-request: - type: object - $ref: "#/definitions/edge-tag-query-request" - search-results: - type: object - $ref: "#/definitions/search-results" - sdn-zone-response: - type: object - $ref: "#/definitions/sdn-zone-response" + property-name: + type: string + property-value: + type: string + action: + properties: + action-type: + type: string + action-data: + type: array + items: + $ref: "#/definitions/action-data" + action-data: + properties: + property-name: + type: string + property-value: + type: string actions: description: | APIs that are more action related than REST (e.g., notify, update). @@ -37874,103 +48513,301 @@ definitions: notify: type: object $ref: "#/definitions/notify" - relationship-data: + allotted-resource: + description: | + Represents a slice or partial piece of a resource that gets separately allotted + ###### Related Nodes + - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY) + - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY) + - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE) + - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY) + - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY) + - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT required: - - relationship-key - - relationship-value + - id properties: - relationship-key: + id: type: string - description: A keyword provided by A&AI to indicate an attribute. - relationship-value: + description: Allotted Resource id UUID assigned to this instance. + description: type: string - description: Value of the attribute. - related-to-property: - properties: - property-key: + description: The descriptive information assigned to this allotted resource instance + selflink: type: string - description: Key part of a key/value pair - property-value: + description: Link back to more information in the controller + model-invariant-id: type: string - description: Value part of a key/value pair - relationship: - properties: - related-to: + description: the ASDC model id for this resource or service model. + model-version-id: type: string - description: A keyword provided by A&AI to indicate type of node. - related-link: + description: the ASDC model version for this resource or service model. + persona-model-version: type: string - description: URL to the object in A&AI. - relationship-data: + description: the ASDC model version for this resource or service model. + resource-version: + type: string + description: Concurrency value + orchestration-status: + type: string + description: Orchestration status + operational-status: + type: string + description: Indicator for whether the resource is considered operational + type: + type: string + description: Generic description of the type of allotted resource. + role: + type: string + description: role in the network that this resource will be providing. + tunnel-xconnects: type: array - items: - $ref: "#/definitions/relationship-data" - related-to-property: + items: + $ref: "#/definitions/tunnel-xconnect" + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + allotted-resources: + description: | + This object is used to store slices of services being offered + properties: + allotted-resource: type: array items: - $ref: "#/definitions/related-to-property" - relationship-list: + $ref: "#/definitions/allotted-resource" + availability-zone: + description: | + Availability zone, a collection of compute hosts/pservers + ###### Related Nodes + - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE) + - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE + required: + - availability-zone-name + - hypervisor-type properties: - relationship: + availability-zone-name: + type: string + description: Name of the availability zone. Unique across a cloud region + hypervisor-type: + type: string + description: Type of hypervisor. Source of truth should define valid values. + operational-status: + type: string + description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + availability-zones: + description: | + Collection of availability zones + properties: + availability-zone: type: array items: + $ref: "#/definitions/availability-zone" + az-and-dvs-switches: + properties: + dvs-switches: + type: object + $ref: "#/definitions/dvs-switches" + availability-zone: + type: object + $ref: "#/definitions/availability-zone" + business: + description: | + Namespace for business related constructs + properties: + connectors: + type: array + items: + $ref: "#/definitions/connector" + customers: + type: array + items: + $ref: "#/definitions/customer" + class-of-service: + description: | + ###### Related Nodes + - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE) + required: + - cos + properties: + cos: + type: string + description: unique identifier of probe + probe-id: + type: string + description: identifier of probe + probe-type: + type: string + description: type of probe + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: $ref: "#/definitions/relationship" - ctag-pool: + classes-of-service: description: | - A collection of C tags (vlan tags) grouped for a specific purpose. - ###### Default Delete Scope - THIS_NODE_ONLY + class-of-service of probe + properties: + class-of-service: + type: array + items: + $ref: "#/definitions/class-of-service" + cloud-infrastructure: + description: | + Namespace for cloud infrastructure. + properties: + complexes: + type: array + items: + $ref: "#/definitions/complex" + cloud-regions: + type: array + items: + $ref: "#/definitions/cloud-region" + network-profiles: + type: array + items: + $ref: "#/definitions/network-profile" + pservers: + type: array + items: + $ref: "#/definitions/pserver" + virtual-data-centers: + type: array + items: + $ref: "#/definitions/virtual-data-center" + cloud-region: + description: | + cloud-region designates an installation of a cloud cluster or region or instantiation ###### Related Nodes - - TO availability-zone (Many2Many) - - FROM complex (is composed of ctag-pool) - - FROM vpls-pe + - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE) + - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP + - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE required: - - target-pe - - availability-zone-name - - ctag-pool-purpose + - cloud-owner + - cloud-region-id properties: - target-pe: + cloud-owner: type: string - description: The Target provider edge router - availability-zone-name: + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + cloud-region-id: type: string - description: Name of the availability zone - ctag-pool-purpose: + description: Identifier used by the vendor for the region. Second part of composite key + cloud-type: type: string - description: Describes what the intended purpose of this pool is. - ctag-values: + description: Type of the cloud (e.g., openstack) + owner-defined-type: type: string - description: Comma separated list of ctags + description: Cloud-owner defined type indicator (e.g., dcp, lcp) + cloud-region-version: + type: string + description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE. + identity-url: + type: string + description: URL of the keystone identity service + cloud-zone: + type: string + description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED. + complex-name: + type: string + description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + volume-groups: + type: array + items: + $ref: "#/definitions/volume-group" + tenants: + type: array + items: + $ref: "#/definitions/tenant" + flavors: + type: array + items: + $ref: "#/definitions/flavor" + group-assignments: + type: array + items: + $ref: "#/definitions/group-assignment" + snapshots: + type: array + items: + $ref: "#/definitions/snapshot" + images: + type: array + items: + $ref: "#/definitions/image" + dvs-switches: + type: array + items: + $ref: "#/definitions/dvs-switch" + oam-networks: + type: array + items: + $ref: "#/definitions/oam-network" + availability-zones: + type: array + items: + $ref: "#/definitions/availability-zone" relationship-list: type: array items: $ref: "#/definitions/relationship" - ctag-pools: + cloud-regions: properties: - ctag-pool: + cloud-region: type: array items: - $ref: "#/definitions/ctag-pool" + $ref: "#/definitions/cloud-region" complex: description: | Collection of physical locations that can house cloud-regions. - ###### Default Delete Scope - ERROR_4_IN_EDGES_OR_CASCADE - ###### Related Nodes - - TO ctag-pool (comprises complex, Many2Many) - - TO l3-network (Many2Many) - - FROM availability-zone - - FROM cloud-region - - FROM oam-network - - FROM pserver - - FROM pnf - - FROM vce - - FROM vpls-pe - - FROM volume-group - - FROM zone + ###### Related Nodes + - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE) + - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY) + - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY) + - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE + - COMPLEX is DELETED when these are DELETED CTAG-POOL required: - physical-location-id - physical-location-type @@ -38036,43 +48873,59 @@ definitions: type: array items: $ref: "#/definitions/complex" - volume-group: + configuration: description: | - Persistent block-level storage. - ###### Default Delete Scope - THIS_NODE_ONLY + Port Mirror Configuration. ###### Related Nodes - - TO complex (Many2Many) - - TO tenant (Many2Many) - - FROM cloud-region (is composed of volume-group) - - FROM vf-module - - FROM generic-vnf + - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE) + - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY) + - CONFIGURATION is DELETED when these are DELETED METADATUM + - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK required: - - volume-group-id - - volume-group-name - - vnf-type + - configuration-id + - configuration-type + - configuration-sub-type + - orchestration-status + - operational-status + - configuration-selflink + - model-customization-id properties: - volume-group-id: + configuration-id: type: string - description: Unique ID of volume-group. - volume-group-name: + description: UUID assigned to configuration. + management-option: type: string - description: Name of the volume group. - heat-stack-id: + description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well. + configuration-name: type: string - description: Heat stack id corresponding to this volume-group - vnf-type: + description: Name of the configuration. + configuration-type: type: string - description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + description: port-mirroring-configuration. + configuration-sub-type: + type: string + description: vprobe, pprobe. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. orchestration-status: type: string - description: Orchestration status of this volume-group - model-customization-id: + description: Orchestration status of the configuration. + operational-status: type: string - description: captures the id of all the configuration used to customize the resource for the service. - vf-module-model-customization-id: + description: Indicator for whether the resource is considered operational. + configuration-selflink: type: string - description: helps relate the volume group to the vf-module whose components will require the volume group + description: URL to endpoint where AAI can get more details from SDN-GC. + model-customization-id: + type: string + description: id of the configuration used to customize the resource resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. @@ -38080,474 +48933,641 @@ definitions: type: array items: $ref: "#/definitions/relationship" - volume-groups: + metadata: + type: array + items: + $ref: "#/definitions/metadatum" + configurations: description: | - Collection of persistent block-level storage. + Collection of configurations properties: - volume-group: + configuration: type: array items: - $ref: "#/definitions/volume-group" - volume: + $ref: "#/definitions/configuration" + connector: description: | - Ephemeral Block storage volume. - ###### Default Delete Scope - THIS_NODE_ONLY + Collection of resource instances used to connect a variety of disparate inventory widgets ###### Related Nodes - - FROM vserver (is composed of volume) + - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY) + - CONNECTOR is DELETED when these are DELETED METADATUM required: - - volume-id - - volume-selflink + - resource-instance-id properties: - volume-id: - type: string - description: Unique ID of block storage volume relative to the vserver. - volume-selflink: + resource-instance-id: type: string - description: URL to endpoint where AAI can get more details + description: Unique id of resource instance. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. relationship-list: type: array items: $ref: "#/definitions/relationship" - volumes: + metadata: + type: array + items: + $ref: "#/definitions/metadatum" + connectors: description: | - Collection of ephemeral Block storage volumes. + Collection of resource instances used to connect a variety of disparate inventory widgets properties: - volume: + connector: type: array items: - $ref: "#/definitions/volume" - l3-interface-ipv4-address-list: + $ref: "#/definitions/connector" + constrained-element-set: description: | - IPv4 Address Range - ###### Default Delete Scope - THIS_NODE_ONLY + This is how we would capture constraints defining allowed sets of elements. ###### Related Nodes - - TO instance-group (Many2Many) - - TO l3-network (Many2Many) - - TO subnet (Many2Many) - - FROM l-interface (is composed of l3-interface-ipv4-address-list) - - FROM vlan (is composed of l3-interface-ipv4-address-list) + - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE) + - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE) + - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET required: - - l3-interface-ipv4-address + - constrained-element-set-uuid + - constraint-type + - check-type properties: - l3-interface-ipv4-address: + constrained-element-set-uuid: type: string - description: IP address - l3-interface-ipv4-prefix-length: - type: integer - format: int64 - description: Prefix length, 32 for single address - vlan-id-inner: - type: integer - format: int64 - description: Inner VLAN tag - vlan-id-outer: - type: integer - format: int64 - description: Outer VLAN tag - is-floating: - type: boolean - description: Indicator of fixed or floating address - resource-version: + constraint-type: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - neutron-network-id: + check-type: type: string - description: Neutron network id of the interface that address belongs to - neutron-subnet-id: + resource-version: type: string - description: Neutron id of subnet that address belongs to + element-choice-sets: + type: array + items: + $ref: "#/definitions/element-choice-set" relationship-list: type: array items: $ref: "#/definitions/relationship" - l3-interface-ipv6-address-list: + constrained-element-sets: + properties: + constrained-element-set: + type: array + items: + $ref: "#/definitions/constrained-element-set" + ctag-assignment: description: | - IPv6 Address Range - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - TO instance-group (Many2Many) - - TO l3-network (Many2Many) - - TO subnet (Many2Many) - - FROM l-interface (is composed of l3-interface-ipv6-address-list) - - FROM vlan (is composed of l3-interface-ipv6-address-list) + - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY) required: - - l3-interface-ipv6-address + - vlan-id-inner properties: - l3-interface-ipv6-address: - type: string - description: IP address - l3-interface-ipv6-prefix-length: - type: integer - format: int64 - description: Prefix length, 128 for single address vlan-id-inner: type: integer format: int64 - description: Inner VLAN tag - vlan-id-outer: - type: integer - format: int64 - description: Outer VLAN tag - is-floating: - type: boolean - description: Indicator of fixed or floating address + description: id. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - neutron-network-id: - type: string - description: Neutron network id of the interface that address belongs to - neutron-subnet-id: - type: string - description: Neutron id of subnet that address belongs to relationship-list: type: array items: $ref: "#/definitions/relationship" - vlan: + ctag-assignments: + properties: + ctag-assignment: + type: array + items: + $ref: "#/definitions/ctag-assignment" + ctag-pool: description: | - Definition of vlan - ###### Default Delete Scope - CASCADE_TO_CHILDREN + A collection of C tags (vlan tags) grouped for a specific purpose. ###### Related Nodes - - TO l3-interface-ipv4-address-list (comprises vlan, Many2Many) - - TO l3-interface-ipv6-address-list (comprises vlan, Many2Many) - - TO multicast-configuration (Many2Many) - - TO logical-link (Many2Many) - - FROM l-interface (is composed of vlan) - - FROM service-instance - - FROM allotted-resource + - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE) + - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY) required: - - vlan-interface - - in-maint + - target-pe + - availability-zone-name + - ctag-pool-purpose properties: - vlan-interface: + target-pe: type: string - description: String that identifies the interface - vlan-id-inner: - type: integer - format: int64 - description: Inner VLAN tag - vlan-id-outer: - type: integer - format: int64 - description: Outer VLAN tag - resource-version: + description: The Target provider edge router + availability-zone-name: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - speed-value: + description: Name of the availability zone + ctag-pool-purpose: type: string - description: Captures the numeric part of the speed - speed-units: + description: Describes what the intended purpose of this pool is. + ctag-values: type: string - description: Captures the units corresponding to the speed - vlan-description: + description: Comma separated list of ctags + resource-version: type: string - description: Used to describe (the service associated with) the vlan - backdoor-connection: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + ctag-pools: + properties: + ctag-pool: + type: array + items: + $ref: "#/definitions/ctag-pool" + customer: + description: | + customer identifiers to provide linkage back to BSS information. + ###### Related Nodes + - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE) + - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION + required: + - global-customer-id + - subscriber-name + - subscriber-type + properties: + global-customer-id: type: string - description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device. - vpn-id: + description: Global customer id used across ECOMP to uniquely identify customer. + subscriber-name: type: string - description: This indicates the customers VPN ID associated with this vlan - orchestration-status: + description: Subscriber name, an alternate way to retrieve a customer. + subscriber-type: type: string - description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C. - in-maint: - type: boolean + description: Subscriber type, a way to provide VID with only the INFRA customers. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + service-subscriptions: + type: array + items: + $ref: "#/definitions/service-subscription" relationship-list: type: array items: $ref: "#/definitions/relationship" - l3-interface-ipv4-address-list: + customers: + description: | + Collection of customer identifiers to provide linkage back to BSS information. + properties: + customer: type: array items: - $ref: "#/definitions/l3-interface-ipv4-address-list" - l3-interface-ipv6-address-list: + $ref: "#/definitions/customer" + cvlan-tag-entry: + required: + - cvlan-tag + properties: + cvlan-tag: + type: integer + format: int64 + description: See mis-na-virtualization-platform.yang + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: type: array - items: - $ref: "#/definitions/l3-interface-ipv6-address-list" - vlans: + items: + $ref: "#/definitions/relationship" + cvlan-tags: properties: - vlan: + cvlan-tag-entry: type: array items: - $ref: "#/definitions/vlan" - sriov-vf: + $ref: "#/definitions/cvlan-tag-entry" + dvs-switch: description: | - SR-IOV Virtual Function (not to be confused with virtual network function) - ###### Default Delete Scope - THIS_NODE_ONLY + Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI. ###### Related Nodes - - FROM l-interface (is composed of sriov-vf) + - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) required: - - pci-id + - switch-name + - vcenter-url properties: - pci-id: - type: string - description: PCI ID used to identify the sriov-vf - vf-vlan-filter: - type: string - description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM. - vf-mac-filter: - type: string - description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM. - vf-vlan-strip: - type: boolean - description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM. - vf-vlan-anti-spoof-check: - type: boolean - description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs. - vf-mac-anti-spoof-check: - type: boolean - description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs. - vf-mirrors: + switch-name: type: string - description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports. - vf-broadcast-allow: - type: boolean - description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM - vf-unknown-multicast-allow: - type: boolean - description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM - vf-unknown-unicast-allow: - type: boolean - description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM - vf-insert-stag: - type: boolean - description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM. - vf-link-status: + description: DVS switch name + vcenter-url: type: string - description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto. + description: URL used to reach the vcenter resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - neutron-network-id: - type: string - description: Neutron network id of the interface relationship-list: type: array items: $ref: "#/definitions/relationship" - sriov-vfs: + dvs-switches: description: | - Collection of SR-IOV Virtual Functions. + Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs. properties: - sriov-vf: + dvs-switch: type: array items: - $ref: "#/definitions/sriov-vf" - l-interface: + $ref: "#/definitions/dvs-switch" + edge-prop-names: description: | - Logical interfaces, e.g., a vnic. - ###### Default Delete Scope - CASCADE_TO_CHILDREN - ###### Related Nodes - - TO instance-group (Many2Many) - - TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many) - - TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many) - - TO l-interface (comprises l-interface, One2Many) - - TO logical-link (Many2Many) - - TO vlan (comprises l-interface, Many2Many) - - TO sriov-vf (comprises l-interface, One2One) - - FROM generic-vnf (is composed of l-interface) - - FROM lag-interface (is composed of l-interface) - - FROM newvce (is composed of l-interface) - - FROM p-interface (is composed of l-interface) - - FROM vserver (is composed of l-interface) - - FROM l-interface (is composed of l-interface) - required: - - interface-name - - is-port-mirrored - - in-maint + Internal map to define the properties of an edge and interpret the map EdgeRules properties: - interface-name: + edgeLabel: type: string - description: Name given to the interface - interface-role: + direction: type: string - description: E.g., CUSTOMER, UPLINK, etc. - v6-wan-link-ip: + multiplicityRule: type: string - description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B. - selflink: + isParent: + type: boolean + usesResource: + type: boolean + hasDelTarget: + type: boolean + SVC-INFRA: + type: boolean + SVC-INFRA-REV: + type: boolean + edge-tag-query-request: + properties: + edge-tag: type: string - description: URL to endpoint where AAI can get more details - interface-id: + result-detail: type: string - description: ID of interface - macaddr: + start-node-type: type: string - description: MAC address for the interface - network-name: + start-node-filter: + type: array + items: + $ref: "#/definitions/start-node-filter" + include-node-filter: + type: array + items: + $ref: "#/definitions/include-node-filter" + secondary-filter: + type: array + items: + $ref: "#/definitions/secondary-filter" + edge-tag-query-result: + properties: + tagged-inventory-item-list: + type: array + items: + $ref: "#/definitions/tagged-inventory-item-list" + element-choice-set: + description: | + This is how we would capture constraints defining allowed sets of elements. + ###### Related Nodes + - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE) + - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT + required: + - element-choice-set-uuid + - element-choice-set-name + properties: + element-choice-set-uuid: type: string - description: Name of the network - management-option: + element-choice-set-name: type: string - description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER - interface-description: + cardinality: type: string - description: Human friendly text regarding this interface. - is-port-mirrored: - type: boolean resource-version: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - in-maint: - type: boolean - vlans: + model-elements: type: array items: - $ref: "#/definitions/vlan" - sriov-vfs: + $ref: "#/definitions/model-element" + relationship-list: type: array items: - $ref: "#/definitions/sriov-vf" - l-interfaces: + $ref: "#/definitions/relationship" + element-choice-sets: + properties: + element-choice-set: type: array - items: - $ref: "#/definitions/l-interface" + items: + $ref: "#/definitions/element-choice-set" + entitlement: + description: | + Metadata for entitlement group. + ###### Related Nodes + - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + required: + - group-uuid + - resource-uuid + properties: + group-uuid: + type: string + description: Unique ID for the entitlement group the resource comes from, should be uuid. + resource-uuid: + type: string + description: Unique ID of an entitlement resource. + resource-version: + type: string + description: Concurrency value relationship-list: type: array items: $ref: "#/definitions/relationship" - l3-interface-ipv4-address-list: - type: array - items: - $ref: "#/definitions/l3-interface-ipv4-address-list" - l3-interface-ipv6-address-list: + entitlements: + description: | + Entitlements, keyed by group-uuid and resource-uuid, related to license management + properties: + entitlement: type: array items: - $ref: "#/definitions/l3-interface-ipv6-address-list" - l-interfaces: + $ref: "#/definitions/entitlement" + esr-ems: description: | - Collection of logical interfaces. + Persist EMS address information used by EMS driver. + ###### Related Nodes + - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many) + - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO + required: + - ems-id properties: - l-interface: + ems-id: + type: string + description: Unique ID of EMS. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + esr-system-info-list: + type: object + $ref: "#/definitions/esr-system-info-list" + relationship-list: + type: object + $ref: "#/definitions/relationship-list" + esr-ems-list: + properties: + esr-ems: type: array items: - $ref: "#/definitions/l-interface" - vserver: + $ref: "#/definitions/esr-ems" + esr-system-info: description: | - Virtual Servers, aka virtual machine or VM. - ###### Default Delete Scope - CASCADE_TO_CHILDREN - ###### Related Nodes - - TO flavor (Many2One) - - TO image (Many2One) - - TO l-interface (comprises vserver, Many2Many) - - TO pserver (Many2One) - - TO volume (comprises vserver, Many2Many) - - TO vnfc (Many2Many) - - TO snapshot (One2One) - - TO vf-module (Many2One) - - FROM generic-vnf - - FROM tenant (is composed of vserver) - - FROM vce + Persist common address information of external systems. + ###### Related Nodes + - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info) + - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info) + - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info) + - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info) required: - - vserver-id - - vserver-name - - vserver-selflink - - in-maint - - is-closed-loop-disabled + - esr-system-info-id + - user-name + - password + - system-type properties: - vserver-id: + esr-system-info-id: type: string - description: Unique identifier for this vserver relative to its tenant - vserver-name: + description: Unique ID of esr system info. + system-name: type: string - description: Name of vserver - vserver-name2: + description: name of external system. + type: type: string - description: Alternative name of vserver - prov-status: + description: type of external systems. + vendor: type: string - description: Trigger for operational monitoring of this resource by Service Assurance systems. - vserver-selflink: + description: vendor of external systems. + version: type: string - description: URL to endpoint where AAI can get more details - in-maint: + description: version of external systems. + service-url: + type: string + description: url used to access external systems. + user-name: + type: string + description: username used to access external systems. + password: + type: string + description: password used to access external systems. + system-type: + type: string + description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm. + protocol: + type: string + description: protocol of third party SDNC, for example netconf/snmp. + ssl-cacert: + type: string + description: ca file content if enabled ssl on auth-url. + ssl-insecure: type: boolean - is-closed-loop-disabled: + description: Whether to verify VIM's certificate. + ip-address: + type: string + description: service IP of ftp server. + port: + type: string + description: service port of ftp server. + cloud-domain: + type: string + description: domain info for authentication. + default-tenant: + type: string + description: default tenant of VIM. + passive: type: boolean + description: ftp passive mode or not. + remote-path: + type: string + description: resource or performance data file path. + system-status: + type: string + description: the status of external system. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - volumes: - type: array - items: - $ref: "#/definitions/volume" relationship-list: type: array items: $ref: "#/definitions/relationship" - l-interfaces: + esr-system-info-list: + description: | + Collection of persistent block-level external system auth info. + properties: + esr-system-info: type: array - items: - $ref: "#/definitions/l-interface" - vservers: + items: + $ref: "#/definitions/esr-system-info" + esr-thirdparty-sdnc: description: | - Collection of virtual Servers, aka virtual machines or VMs. + Persist SDNC address information used by ONAP SDNC. + ###### Related Nodes + - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One) + - TO pnf( esr-thirdparty-sdnc has pnf, One2Many) + - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO + required: + - thirdparty-sdnc-id properties: - vserver: + thirdparty-sdnc-id: + type: string + description: Unique ID of SDNC. + location: + type: string + description: used for DC type to indicate the location of SDNC, such as Core or Edge. + product-name: + type: string + description: password used to access SDNC server. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + esr-system-info-list: + type: object + $ref: "#/definitions/esr-system-info-list" + relationship-list: + type: object + $ref: "#/definitions/relationship-list" + esr-thirdparty-sdnc-list: + properties: + esr-thirdparty-sdnc: type: array items: - $ref: "#/definitions/vserver" - tenant: + $ref: "#/definitions/esr-thirdparty-sdnc" + esr-vnfm: description: | - Openstack tenant - ###### Default Delete Scope - THIS_NODE_ONLY + Persist VNFM address information used by VF-C. ###### Related Nodes - - TO l3-network (Many2Many) - - TO service-subscription (Many2Many) - - TO vserver (comprises tenant, One2Many) - - FROM cloud-region (is composed of tenant) - - FROM group-assignment - - FROM volume-group + - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One) + - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO required: - - tenant-id - - tenant-name + - vnfm-id properties: - tenant-id: + vnfm-id: type: string - description: Unique id relative to the cloud-region. - tenant-name: + description: Unique ID of VNFM. + vim-id: type: string - description: Readable name of tenant + description: indecate the VIM to deploy VNF. + certificate-url: + type: string + description: certificate url of VNFM. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - vservers: + esr-system-info-list: + type: object + $ref: "#/definitions/esr-system-info-list" + relationship-list: + type: object + $ref: "#/definitions/relationship-list" + esr-vnfm-list: + properties: + esr-vnfm: type: array - items: - $ref: "#/definitions/vserver" + items: + $ref: "#/definitions/esr-vnfm" + evc: + description: | + evc object is an optional child object of the Configuration object. + ###### Related Nodes + - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE) + required: + - evc-id + properties: + evc-id: + type: string + description: Unique/key field for the evc object + forwarding-path-topology: + type: string + description: Point-to-Point, Multi-Point + cir-value: + type: string + description: Commited Information Rate + cir-units: + type: string + description: CIR units + connection-diversity-group-id: + type: string + description: Diversity Group ID + service-hours: + type: string + description: formerly Performance Group + esp-evc-circuit-id: + type: string + description: EVC Circuit ID of ESP EVC + esp-evc-cir-value: + type: string + description: Committed Information Rate (For ESP) + esp-evc-cir-units: + type: string + description: CIR units (For ESP) + esp-itu-code: + type: string + description: Identifies ESP + collector-pop-clli: + type: string + description: Collector POP CLLI (from the hostname of the access pnf) + inter-connect-type-ingress: + type: string + description: Interconnect type on ingress side of EVC. + tagmode-access-ingress: + type: string + description: tagode for collector side of EVC + tagmode-access-egress: + type: string + description: tagMode for network side of EVC relationship-list: type: array items: $ref: "#/definitions/relationship" - tenants: + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + evcs: + properties: + evc: + type: array + items: + $ref: "#/definitions/evc" + external-system: description: | - Collection of openstack tenants. + Namespace for external system. properties: - tenant: + esr-ems-list: + type: object + $ref: "#/definitions/esr-ems-list" + esr-vnfm-list: + type: object + $ref: "#/definitions/esr-vnfm-list" + esr-thirdparty-sdnc-list: + type: object + $ref: "#/definitions/esr-thirdparty-sdnc-list" + extra-properties: + description: | + Extra properties for inventory item for response list + properties: + extra-property: type: array items: - $ref: "#/definitions/tenant" + $ref: "#/definitions/extra-property" + extra-property: + properties: + property-name: + type: string + property-value: + type: string flavor: description: | Openstack flavor. - ###### Default Delete Scope - ERROR_IF_ANY_IN_EDGES ###### Related Nodes - - FROM cloud-region (is composed of flavor) - - FROM vserver + - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE) + - FLAVOR cannot be deleted if linked to VSERVER required: - flavor-id - flavor-name @@ -38602,143 +49622,400 @@ definitions: type: array items: $ref: "#/definitions/flavor" - group-assignment: + forwarder: description: | - Openstack group-assignment used to store exclusivity groups (EG). - ###### Default Delete Scope - THIS_NODE_ONLY + Entity describing a sequenced segment of forwarding path ###### Related Nodes - - TO tenant (Many2Many) - - TO pserver (One2Many) - - FROM cloud-region (is composed of group-assignment) + - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE) + - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE) + - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE) + - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE) + - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE) + - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION required: - - group-id - - group-type - - group-name + - sequence properties: - group-id: + sequence: + type: integer + format: int32 + description: Unique ID of this segmentation + forwarder-role: type: string - description: Group id, expected to be unique across cloud-region. - group-type: + description: ingress, intermediate, egress + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + resource-version: type: string - description: Group type - the type of group this instance refers to - group-name: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + forwarder-evc: + description: | + forwarder object is an optional child object of the Configuration object. + ###### Related Nodes + - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE) + required: + - forwarder-evc-id + properties: + forwarder-evc-id: type: string - description: Group name - name assigned to the group - group-description: + description: Key for forwarder-evc object + circuit-id: type: string - description: Group description - description of the group - resource-version: + description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC + ivlan: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + description: Internal VLAN. + svlan: + type: string + description: SVLAN value for ingress of egress forwarder. + cvlan: + type: string + description: CVLAN value for ingress of egress forwarder. relationship-list: type: array items: $ref: "#/definitions/relationship" - group-assignments: + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + forwarder-evcs: + properties: + forwarder-evc: + type: array + items: + $ref: "#/definitions/forwarder-evc" + forwarders: + properties: + forwarder: + type: array + items: + $ref: "#/definitions/forwarder" + forwarding-path: description: | - Collection of openstack group assignments + Entity that describes the sequenced forwarding path between interfaces of services or resources + ###### Related Nodes + - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE) + - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE) + - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE) + - FORWARDING-PATH is DELETED when these are DELETED FORWARDER + - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION + required: + - forwarding-path-id + - forwarding-path-name properties: - group-assignment: + forwarding-path-id: + type: string + description: Unique ID of this FP + forwarding-path-name: + type: string + description: Name of the FP + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + selflink: + type: string + description: the self link for this FP + forwarders: + type: array + items: + $ref: "#/definitions/forwarder" + forwarding-paths: + properties: + forwarding-path: type: array items: - $ref: "#/definitions/group-assignment" - snapshot: + $ref: "#/definitions/forwarding-path" + generic-vnf: description: | - Openstack snapshot - ###### Default Delete Scope - THIS_NODE_ONLY + General purpose VNF ###### Related Nodes - - FROM cloud-region (is composed of snapshot) - - FROM vserver + - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE) + - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY) + - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY) + - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE) + - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY) + - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY) + - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY) + - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY) + - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE required: - - snapshot-id + - vnf-id + - vnf-name + - vnf-type + - in-maint + - is-closed-loop-disabled properties: - snapshot-id: + vnf-id: type: string - description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. - snapshot-name: + description: Unique id of VNF. This is unique across the graph. + vnf-name: type: string - description: Snapshot name - snapshot-architecture: + description: Name of VNF. + vnf-name2: type: string - description: Operating system architecture - snapshot-os-distro: + description: Alternate name of VNF. + vnf-type: type: string - description: The common name of the operating system distribution in lowercase - snapshot-os-version: + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + service-id: type: string - description: The operating system version as specified by the distributor. - application: + description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED + regional-resource-zone: type: string - description: The application that the image instantiates. - application-vendor: + description: Regional way of organizing pservers, source of truth should define values + prov-status: type: string - description: The vendor of the application. - application-version: + description: Trigger for operational monitoring of this resource by Service Assurance systems. + operational-status: type: string - description: The version of the application. - snapshot-selflink: + description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. + license-key: type: string - description: URL to endpoint where AAI can get more details - prev-snapshot-id: + description: OBSOLETE - do not use + equipment-role: type: string - description: This field contains the UUID of the previous snapshot (if any). + description: Client should send valid enumerated value + orchestration-status: + type: string + description: Orchestration status of this VNF, used by MSO. + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + management-option: + type: string + description: identifier of managed by company or customer + ipv4-oam-address: + type: string + description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf. + ipv4-loopback0-address: + type: string + description: v4 Loopback0 address + nm-lan-v6-address: + type: string + description: v6 Loopback address + management-v6-address: + type: string + description: v6 management address + vcpu: + type: integer + format: int64 + description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases + vcpu-units: + type: string + description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases + vmemory: + type: integer + format: int64 + description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases + vmemory-units: + type: string + description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases + vdisk: + type: integer + format: int64 + description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases + vdisk-units: + type: string + description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases + in-maint: + type: boolean + is-closed-loop-disabled: + type: boolean resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + summary-status: + type: string + description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD. + encrypted-access-flag: + type: boolean + description: indicates whether generic-vnf access uses SSH + entitlement-assignment-group-uuid: + type: string + description: UUID of the Entitlement group used for licensing VNFs, OBSOLETE - See child relationships. + entitlement-resource-uuid: + type: string + description: UUID of the specific entitlement resource. OBSOLETE - See child relationships. + license-assignment-group-uuid: + type: string + description: UUID of the license assignment group. OBSOLETE - See child relationships. + license-key-uuid: + type: string + description: UUID of the actual license resource. OBSOLETE - See child relationships. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + model-customization-id: + type: string + description: captures the id of all the configuration used to customize the resource for the service. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + as-number: + type: string + description: as-number of the VNF + regional-resource-subzone: + type: string + description: represents sub zone of the rr plane + nf-type: + type: string + description: Generic description of the type of NF + nf-function: + type: string + description: English description of Network function that the specific VNF deployment is providing + nf-role: + type: string + description: role in the network that this model will be providing + nf-naming-code: + type: string + description: string assigned to this model used for naming purposes + selflink: + type: string + description: Path to the controller object. relationship-list: type: array items: $ref: "#/definitions/relationship" - snapshots: + l-interfaces: + type: array + items: + $ref: "#/definitions/l-interface" + lag-interfaces: + type: array + items: + $ref: "#/definitions/lag-interface" + vf-modules: + type: array + items: + $ref: "#/definitions/vf-module" + licenses: + type: array + items: + $ref: "#/definitions/license" + entitlements: + type: array + items: + $ref: "#/definitions/entitlement" + generic-vnfs: description: | - Collection of openstack snapshots + Collection of VNFs properties: - snapshot: + generic-vnf: type: array items: - $ref: "#/definitions/snapshot" - metadatum: + $ref: "#/definitions/generic-vnf" + group-assignment: description: | - Key/value pairs - ###### Default Delete Scope - THIS_NODE_ONLY + Openstack group-assignment used to store exclusivity groups (EG). ###### Related Nodes - - FROM image (is composed of metadatum) - - FROM model-ver (is composed of metadatum) - - FROM service-instance (is composed of metadatum) - - FROM connector (is composed of metadatum) + - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY) required: - - metaname - - metaval + - group-id + - group-type + - group-name properties: - metaname: + group-id: type: string - metaval: + description: Group id, expected to be unique across cloud-region. + group-type: + type: string + description: Group type - the type of group this instance refers to + group-name: + type: string + description: Group name - name assigned to the group + group-description: type: string + description: Group description - description of the group resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - metadata: + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + group-assignments: description: | - Collection of metadatum (key/value pairs) - ###### Default Delete Scope - THIS_NODE_ONLY + Collection of openstack group assignments properties: - metadatum: + group-assignment: type: array items: - $ref: "#/definitions/metadatum" + $ref: "#/definitions/group-assignment" + host-route: + description: | + ###### Related Nodes + - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE) + required: + - host-route-id + - route-prefix + - next-hop + properties: + host-route-id: + type: string + description: host-route id + route-prefix: + type: string + description: subnet prefix + next-hop: + type: string + description: Could be ip-address, hostname, or service-instance + next-hop-type: + type: string + description: Should be ip-address, hostname, or service-instance to match next-hop + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + host-routes: + properties: + host-route: + type: array + items: + $ref: "#/definitions/host-route" image: description: | Openstack image. - ###### Default Delete Scope - ERROR_4_IN_EDGES_OR_CASCADE ###### Related Nodes - - TO metadatum (comprises image, Many2Many) - - FROM cloud-region (is composed of image) - - FROM vserver + - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE) + - IMAGE cannot be deleted if linked to VSERVER + - IMAGE is DELETED when these are DELETED METADATUM required: - image-id - image-name @@ -38792,24 +50069,205 @@ definitions: type: array items: $ref: "#/definitions/image" - dvs-switch: + include-node-filter: + properties: + include-node-type: + type: string + instance-filter: description: | - Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI. - ###### Default Delete Scope - THIS_NODE_ONLY + InstanceFilter for performing a named-query or model query + instance-filters: + description: | + InstanceFilters for performing a named-query or model query + properties: + instance-filter: + type: array + items: + $ref: "#/definitions/instance-filter" + instance-group: + description: | + General mechanism for grouping instances ###### Related Nodes - - TO availability-zone (Many2Many) - - FROM cloud-region (is composed of dvs-switch) + - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) required: - - switch-name - - vcenter-url + - id + - description + - type properties: - switch-name: + id: type: string - description: DVS switch name - vcenter-url: + description: Instance Group ID, UUID assigned to this instance. + description: type: string - description: URL used to reach the vcenter + description: Descriptive text to help identify the usage of this instance-group + type: + type: string + description: Only valid value today is lower case ha for high availability + sub-type: + type: string + description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby] + resource-version: + type: string + description: Concurrency value + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + instance-groups: + description: | + Collection of openstack route table references + properties: + instance-group: + type: array + items: + $ref: "#/definitions/instance-group" + inventory: + properties: + search: + type: object + $ref: "#/definitions/search" + actions: + type: object + $ref: "#/definitions/actions" + cloud-infrastructure: + type: object + $ref: "#/definitions/cloud-infrastructure" + business: + type: object + $ref: "#/definitions/business" + service-design-and-creation: + type: object + $ref: "#/definitions/service-design-and-creation" + network: + type: object + $ref: "#/definitions/network" + aai-internal: + type: object + $ref: "#/definitions/aai-internal" + nodes: + type: array + items: + $ref: "#/definitions/aai-internal" + inventory-item: + properties: + inventory-item-type: + type: string + inventory-item-link: + type: string + inventory-item-data: + type: array + items: + $ref: "#/definitions/inventory-item-data" + tagged-inventory-item-list: + type: array + items: + $ref: "#/definitions/tagged-inventory-item-list" + inventory-item-data: + properties: + property-name: + type: string + property-value: + type: string + inventory-response-item: + description: | + Inventory item for response list + properties: + model-name: + type: string + extra-properties: + type: object + $ref: "#/definitions/extra-properties" + inventory-response-items: + type: object + $ref: "#/definitions/inventory-response-items" + inventory-response-items: + description: | + Container for inventory items in response list + properties: + inventory-response-item: + type: array + items: + $ref: "#/definitions/inventory-response-item" + ipsec-configuration: + description: | + IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C + ###### Related Nodes + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE) + - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE) + - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER + required: + - ipsec-configuration-id + properties: + ipsec-configuration-id: + type: string + description: UUID of this configuration + requested-vig-address-type: + type: string + description: Indicate the type of VIG server like AVPN, INTERNET, BOTH + requested-encryption-strength: + type: string + description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc + requested-dmz-type: + type: string + description: can offer a shared DMZ or a DMZ specific to a customer + shared-dmz-network-address: + type: string + description: Network address of shared DMZ + requested-customer-name: + type: string + description: If the DMZ is a custom DMZ, this field will indicate the customer information + ike-version: + type: string + description: can be 1 or 2 + ikev1-authentication: + type: string + description: Contains values like md5, sha1, sha256, sha384 + ikev1-encryption: + type: string + description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc + ikev1-dh-group: + type: string + description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14 + ikev1-am-group-id: + type: string + description: Group name defined in VIG for clients using aggressive mode + ikev1-am-password: + type: string + description: pre-shared key for the above group name + ikev1-sa-lifetime: + type: string + description: Lifetime for IKEv1 SA + ipsec-authentication: + type: string + description: md5, sha1, sha256, sha384 + ipsec-encryption: + type: string + description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc + ipsec-sa-lifetime: + type: string + description: Life time for IPSec SA + ipsec-pfs: + type: string + description: enable PFS or not + xauth-userid: + type: string + description: user ID for xAuth, sm-user, ,nmteHostName + xauth-user-password: + type: string + description: Encrypted using the Juniper $9$ algorithm + dpd-interval: + type: string + description: The time between DPD probe + dpd-frequency: + type: string + description: Maximum number of DPD before claiming the tunnel is down resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. @@ -38817,206 +50275,998 @@ definitions: type: array items: $ref: "#/definitions/relationship" - dvs-switches: + vig-servers: + type: array + items: + $ref: "#/definitions/vig-server" + ipsec-configurations: + properties: + ipsec-configuration: + type: array + items: + $ref: "#/definitions/ipsec-configuration" + key-data: + properties: + key-name: + type: string + key-value: + type: string + l-interface: description: | - Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs. + Logical interfaces, e.g., a vnic. + ###### Related Nodes + - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE) + - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY) + - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE) + - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE) + - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE) + - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN + - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK + required: + - interface-name + - is-port-mirrored + - in-maint properties: - dvs-switch: + interface-name: + type: string + description: Name given to the interface + interface-role: + type: string + description: E.g., CUSTOMER, UPLINK, etc. + v6-wan-link-ip: + type: string + description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B. + selflink: + type: string + description: URL to endpoint where AAI can get more details + interface-id: + type: string + description: ID of interface + macaddr: + type: string + description: MAC address for the interface + network-name: + type: string + description: Name of the network + management-option: + type: string + description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER + interface-description: + type: string + description: Human friendly text regarding this interface. + is-port-mirrored: + type: boolean + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + in-maint: + type: boolean + vlans: + type: array + items: + $ref: "#/definitions/vlan" + sriov-vfs: + type: array + items: + $ref: "#/definitions/sriov-vf" + l-interfaces: + type: array + items: + $ref: "#/definitions/l-interface" + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + l3-interface-ipv4-address-list: type: array items: - $ref: "#/definitions/dvs-switch" - oam-network: + $ref: "#/definitions/l3-interface-ipv4-address-list" + l3-interface-ipv6-address-list: + type: array + items: + $ref: "#/definitions/l3-interface-ipv6-address-list" + l-interfaces: description: | - OAM network, to be deprecated shortly. Do not use for new purposes. - ###### Default Delete Scope - ERROR_IF_ANY_IN_EDGES + Collection of logical interfaces. + properties: + l-interface: + type: array + items: + $ref: "#/definitions/l-interface" + l3-interface-ipv4-address-list: + description: | + IPv4 Address Range ###### Related Nodes - - TO complex (Many2Many) - - TO service-capability (Many2Many) - - FROM cloud-region (is composed of oam-network) + - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) required: - - network-uuid + - l3-interface-ipv4-address + properties: + l3-interface-ipv4-address: + type: string + description: IP address + l3-interface-ipv4-prefix-length: + type: integer + format: int64 + description: Prefix length, 32 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: + type: string + description: Neutron network id of the interface that address belongs to + neutron-subnet-id: + type: string + description: Neutron id of subnet that address belongs to + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + l3-interface-ipv6-address-list: + description: | + IPv6 Address Range + ###### Related Nodes + - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + required: + - l3-interface-ipv6-address + properties: + l3-interface-ipv6-address: + type: string + description: IP address + l3-interface-ipv6-prefix-length: + type: integer + format: int64 + description: Prefix length, 128 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: + type: string + description: Neutron network id of the interface that address belongs to + neutron-subnet-id: + type: string + description: Neutron id of subnet that address belongs to + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + l3-network: + description: | + Generic network definition + ###### Related Nodes + - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY) + - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY) + - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY) + - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY) + - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET + required: + - network-id - network-name - - cvlan-tag + - is-bound-to-vpn + - is-provider-network + - is-shared-network + - is-external-network properties: - network-uuid: + network-id: type: string - description: UUID of the network. Unique across a cloud-region + description: Network ID, should be uuid. Unique across A&AI. network-name: type: string - description: Name of the network. - cvlan-tag: + description: Name of the network, governed by some naming convention.. + network-type: + type: string + description: Type of the network - who defines these values? + network-role: + type: string + description: Role the network plans - who defines these values? + network-technology: + type: string + description: Network technology - who defines these values? + neutron-network-id: + type: string + description: Neutron network id of this Interface + is-bound-to-vpn: + type: boolean + service-id: + type: string + description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED + network-role-instance: type: integer format: int64 - description: cvlan-id - ipv4-oam-gateway-address: + description: network role instance + resource-version: type: string - description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network - ipv4-oam-gateway-address-prefix-length: - type: integer - format: int32 - description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + contrail-network-fqdn: + type: string + description: Contrail FQDN for the network + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + model-customization-id: + type: string + description: captures the id of all the configuration used to customize the resource for the service. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + physical-network-name: + type: string + description: Name associated with the physical network. + is-provider-network: + type: boolean + is-shared-network: + type: boolean + is-external-network: + type: boolean + selflink: + type: string + description: Path to the controller object. + operational-status: + type: string + description: Indicator for whether the resource is considered operational. + subnets: + type: array + items: + $ref: "#/definitions/subnet" + ctag-assignments: + type: array + items: + $ref: "#/definitions/ctag-assignment" + segmentation-assignments: + type: array + items: + $ref: "#/definitions/segmentation-assignment" + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding + l3-networks: + properties: + l3-network: + type: array + items: + $ref: "#/definitions/l3-network" + lag-interface: + description: | + Link aggregate interface + ###### Related Nodes + - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY) + - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY) + - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE) + - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE + - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK + required: + - interface-name + - in-maint + properties: + interface-name: + type: string + description: Name that identifies the link aggregate interface + interface-description: + type: string + description: Human friendly text regarding this interface. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + interface-id: + type: string + description: ID of interface + interface-role: + type: string + description: Role assigned to this Interface, should use values as defined in ECOMP Yang models. + prov-status: + type: string + description: Trigger for operational monitoring of this resource by Service Assurance systems. + in-maint: + type: boolean relationship-list: type: array items: $ref: "#/definitions/relationship" - oam-networks: + l-interfaces: + type: array + items: + $ref: "#/definitions/l-interface" + lag-interfaces: description: | - Collection of OAM networks, to be deprecated shortly. Do not use for new purposes. + Collection of link aggregate interfaces. properties: - oam-network: + lag-interface: type: array items: - $ref: "#/definitions/oam-network" - availability-zone: + $ref: "#/definitions/lag-interface" + lag-link: description: | - Availability zone, a collection of compute hosts/pservers - ###### Default Delete Scope - ERROR_IF_ANY_IN_EDGES - ###### Related Nodes - - TO complex (Many2Many) - - TO service-capability (Many2Many) - - FROM cloud-region (is composed of availability-zone) - - FROM ctag-pool - - FROM dvs-switch - - FROM generic-vnf - - FROM pserver - - FROM vce + LAG links can connect lag-interfaces + ###### Related Nodes + - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY) required: - - availability-zone-name - - hypervisor-type + - link-name properties: - availability-zone-name: + link-name: type: string - description: Name of the availability zone. Unique across a cloud region - hypervisor-type: + description: Alphabetical concatenation of lag-interface names + resource-version: type: string - description: Type of hypervisor. Source of truth should define valid values. + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + lag-links: + description: | + Collection of link aggregation connections + properties: + lag-link: + type: array + items: + $ref: "#/definitions/lag-link" + license: + description: | + Metadata for license group. + ###### Related Nodes + - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + required: + - group-uuid + - resource-uuid + properties: + group-uuid: + type: string + description: Unique ID for the license group the resource belongs to, should be uuid. + resource-uuid: + type: string + description: Unique ID of a license resource. + resource-version: + type: string + description: Concurrency value + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + licenses: + description: | + Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management + properties: + license: + type: array + items: + $ref: "#/definitions/license" + line-of-business: + description: | + describes a line-of-business + ###### Related Nodes + - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY) + required: + - line-of-business-name + properties: + line-of-business-name: + type: string + description: Name of the line-of-business (product) + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + lines-of-business: + description: | + Collection of lines-of-business + properties: + line-of-business: + type: array + items: + $ref: "#/definitions/line-of-business" + logical-link: + description: | + Logical links generally connect l-interfaces but are used to express logical connectivity between two points + ###### Related Nodes + - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY) + - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY) + - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY) + - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY) + - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY) + - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY) + - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + required: + - link-name + - link-type + properties: + link-name: + type: string + description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ + link-type: + type: string + description: Type of logical link, e.g., evc + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + ip-version: + type: string + description: v4, v6, or ds for dual stack + routing-protocol: + type: string + description: For example, static or BGP + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. operational-status: type: string - description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values. + description: Indication of operational status of the logical link. + prov-status: + type: string + description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. + link-role: + type: string + description: Indication of the network use of the logical link. + link-name2: + type: string + description: Alias or alternate name (CLCI or D1 name). + link-id: + type: string + description: UUID of the logical-link, SDNC generates this. + circuit-id: + type: string + description: Circuit id + purpose: + type: string + description: Reason for this entity, role it is playing + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + logical-links: + description: | + Collection of logical connections + properties: + logical-link: + type: array + items: + $ref: "#/definitions/logical-link" + metadata: + description: | + Collection of metadatum (key/value pairs) + properties: + metadatum: + type: array + items: + $ref: "#/definitions/metadatum" + metadatum: + description: | + Key/value pairs + ###### Related Nodes + - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE) + - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE) + - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + required: + - metaname + - metaval + properties: + metaname: + type: string + metaval: + type: string + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model: + description: | + Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version + ###### Related Nodes + - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY) + - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE) + - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT + - MODEL is DELETED when these are DELETED MODEL-VER + required: + - model-invariant-id + - model-type + properties: + model-invariant-id: + type: string + description: Unique identifier corresponding to the main definition of a model in ASDC + model-type: + type: string + description: Type of the model, e.g., service, resource, widget, etc. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-vers: + type: array + items: + $ref: "#/definitions/model-ver" relationship-list: type: array items: $ref: "#/definitions/relationship" - availability-zones: + model-and-named-query-search: description: | - Collection of availability zones + ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query properties: - availability-zone: + query-parameters: + type: object + $ref: "#/definitions/query-parameters" + instance-filters: + type: object + $ref: "#/definitions/instance-filters" + secondary-filts: + type: object + $ref: "#/definitions/secondary-filts" + top-node-type: + type: string + secondary-filter-cut-point: + type: string + model-constraint: + description: | + This is how we would capture constraints defining allowed sets of elements. + ###### Related Nodes + - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE) + - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET + required: + - model-constraint-uuid + - constrained-element-set-uuid-to-replace + properties: + model-constraint-uuid: + type: string + constrained-element-set-uuid-to-replace: + type: string + constrained-element-sets: + type: array + items: + $ref: "#/definitions/constrained-element-set" + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-constraints: + properties: + model-constraint: type: array items: - $ref: "#/definitions/availability-zone" - cloud-region: + $ref: "#/definitions/model-constraint" + model-element: description: | - cloud-region designates an installation of a cloud cluster or region or instantiation - ###### Default Delete Scope - THIS_NODE_ONLY - ###### Related Nodes - - TO complex (Many2One) - - TO l3-network (Many2Many) - - TO tenant (comprises cloud-region, One2Many) - - TO image (comprises cloud-region, One2Many) - - TO flavor (comprises cloud-region, One2Many) - - TO availability-zone (comprises cloud-region, One2Many) - - TO oam-network (comprises cloud-region, One2Many) - - TO dvs-switch (comprises cloud-region, One2Many) - - TO volume-group (comprises cloud-region, One2Many) - - TO group-assignment (comprises cloud-region, One2Many) - - TO snapshot (comprises cloud-region, One2Many) - - TO zone (Many2One) - - FROM pserver - - FROM logical-link + Defines how other models combine to make up a higher-level model. + ###### Related Nodes + - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE) + - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE) + - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT required: - - cloud-owner - - cloud-region-id + - model-element-uuid + - new-data-del-flag + - cardinality properties: - cloud-owner: + model-element-uuid: type: string - description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname - cloud-region-id: + new-data-del-flag: type: string - description: Identifier used by the vendor for the region. Second part of composite key - cloud-type: + description: Indicates whether this element was created as part of instantiation from this model + cardinality: type: string - description: Type of the cloud (e.g., openstack) - owner-defined-type: + description: How many of this type of element are required/allowed + linkage-points: type: string - description: Cloud-owner defined type indicator (e.g., dcp, lcp) - cloud-region-version: + resource-version: type: string - description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE. - identity-url: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-elements: + type: array + items: + $ref: "#/definitions/model-element" + description: Defines how other models combine to make up a higher-level model + model-constraints: + type: array + items: + $ref: "#/definitions/model-constraint" + description: Describes new constraints on this model element that are not part of that model's definition + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + model-elements: + properties: + model-element: + type: array + items: + $ref: "#/definitions/model-element" + model-ver: + description: | + Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models + ###### Related Nodes + - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT + - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM + required: + - model-version-id + - model-name + - model-version + properties: + model-version-id: type: string - description: URL of the keystone identity service - cloud-zone: + description: Unique identifier corresponding to one version of a model in ASDC + model-name: type: string - description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED. - complex-name: + description: Name of the model, which can change from version to version. + model-version: type: string - description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED. + description: Version + model-description: + type: string + description: Description resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - volume-groups: + model-elements: type: array items: - $ref: "#/definitions/volume-group" - tenants: + $ref: "#/definitions/model-element" + metadata: type: array items: - $ref: "#/definitions/tenant" - flavors: + $ref: "#/definitions/metadatum" + relationship-list: type: array items: - $ref: "#/definitions/flavor" - group-assignments: + $ref: "#/definitions/relationship" + model-vers: + properties: + model-ver: + type: array + items: + $ref: "#/definitions/model-ver" + models: + description: | + Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models + properties: + model: + type: array + items: + $ref: "#/definitions/model" + multicast-configuration: + description: | + ###### Related Nodes + - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY) + required: + - multicast-configuration-id + - multicast-protocol + - rp-type + properties: + multicast-configuration-id: + type: string + description: Unique id of multicast configuration. + multicast-protocol: + type: string + description: protocol of multicast configuration + rp-type: + type: string + description: rp type of multicast configuration + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: type: array items: - $ref: "#/definitions/group-assignment" - snapshots: + $ref: "#/definitions/relationship" + multicast-configurations: + description: | + multicast configuration of generic-vnf ip-address + properties: + multicast-configuration: + type: array + items: + $ref: "#/definitions/multicast-configuration" + named-queries: + properties: + named-query: + type: array + items: + $ref: "#/definitions/named-query" + named-query: + description: | + TBD + ###### Related Nodes + - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT + required: + - named-query-uuid + - named-query-name + - named-query-version + properties: + named-query-uuid: + type: string + named-query-name: + type: string + named-query-version: + type: string + required-input-param: + type: string + description: + type: string + resource-version: + type: string + named-query-elements: type: array items: - $ref: "#/definitions/snapshot" - images: + $ref: "#/definitions/named-query-element" + relationship-list: type: array items: - $ref: "#/definitions/image" - dvs-switches: + $ref: "#/definitions/relationship" + named-query-element: + description: | + TBD + ###### Related Nodes + - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE) + - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP + required: + - named-query-element-uuid + properties: + named-query-element-uuid: + type: string + property-collect-list: + type: string + resource-version: + type: string + property-limit-desc: + type: string + do-not-output: + type: string + named-query-elements: type: array items: - $ref: "#/definitions/dvs-switch" - oam-networks: + $ref: "#/definitions/named-query-element" + related-lookups: type: array items: - $ref: "#/definitions/oam-network" - availability-zones: + $ref: "#/definitions/related-lookup" + property-constraints: type: array items: - $ref: "#/definitions/availability-zone" + $ref: "#/definitions/property-constraint" relationship-list: type: array items: $ref: "#/definitions/relationship" - cloud-regions: + named-query-elements: properties: - cloud-region: + named-query-element: type: array items: - $ref: "#/definitions/cloud-region" + $ref: "#/definitions/named-query-element" + network: + description: | + Namespace for network inventory resources. + properties: + logical-links: + type: array + items: + $ref: "#/definitions/logical-link" + site-pair-sets: + type: array + items: + $ref: "#/definitions/site-pair-set" + vpn-bindings: + type: array + items: + $ref: "#/definitions/vpn-binding" + vpls-pes: + type: array + items: + $ref: "#/definitions/vpls-pe" + multicast-configurations: + type: array + items: + $ref: "#/definitions/multicast-configuration" + vces: + type: array + items: + $ref: "#/definitions/vce" + vnfcs: + type: array + items: + $ref: "#/definitions/vnfc" + l3-networks: + type: array + items: + $ref: "#/definitions/l3-network" + network-policies: + type: array + items: + $ref: "#/definitions/network-policy" + generic-vnfs: + type: array + items: + $ref: "#/definitions/generic-vnf" + lag-links: + type: array + items: + $ref: "#/definitions/lag-link" + newvces: + type: array + items: + $ref: "#/definitions/newvce" + pnfs: + type: array + items: + $ref: "#/definitions/pnf" + physical-links: + type: array + items: + $ref: "#/definitions/physical-link" + ipsec-configurations: + type: array + items: + $ref: "#/definitions/ipsec-configuration" + route-table-references: + type: array + items: + $ref: "#/definitions/route-table-reference" + instance-groups: + type: array + items: + $ref: "#/definitions/instance-group" + zones: + type: array + items: + $ref: "#/definitions/zone" + network-policies: + properties: + network-policy: + type: array + items: + $ref: "#/definitions/network-policy" + network-policy: + description: | + ###### Related Nodes + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE) + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY) + required: + - network-policy-id + properties: + network-policy-id: + type: string + description: UUID representing unique key to this instance + network-policy-fqdn: + type: string + description: Contrail FQDN for the policy + heat-stack-id: + type: string + description: ID for the openStack Heat instance + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" network-profile: description: | Network profile populated by SDN-GP for SNMP - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - FROM generic-vnf + - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) required: - nm-profile-name properties: @@ -39041,19 +51291,301 @@ definitions: type: array items: $ref: "#/definitions/network-profile" + newvce: + description: | + This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce. + ###### Related Nodes + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE) + - NEWVCE is DELETED when these are DELETED L-INTERFACE + required: + - vnf-id2 + - vnf-name + - vnf-type + properties: + vnf-id2: + type: string + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + vnf-name: + type: string + description: Name of VNF. + vnf-name2: + type: string + description: Alternate name of VNF. + vnf-type: + type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + prov-status: + type: string + description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. + operational-status: + type: string + description: Indicator for whether the resource is considered operational + license-key: + type: string + description: OBSOLETE - do not use + ipv4-oam-address: + type: string + description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address). + equipment-role: + type: string + description: Client should send valid enumerated value. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + ipv4-loopback0-address: + type: string + description: v4 Loopback0 address + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO. + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + l-interfaces: + type: array + items: + $ref: "#/definitions/l-interface" + newvces: + description: | + This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce. + properties: + newvce: + type: array + items: + $ref: "#/definitions/newvce" + notification-event: + properties: + cambria.partition: + type: string + notification-event-header: + type: object + $ref: "#/definitions/notification-event-header" + notification-event-header: + properties: + id: + type: string + timestamp: + type: string + source-name: + type: string + domain: + type: string + sequence-number: + type: string + severity: + type: string + event-type: + type: string + version: + type: string + action: + type: string + entity-type: + type: string + top-entity-type: + type: string + entity-link: + type: string + status: + type: string + notify: + required: + - event-id + properties: + event-id: + type: string + node-type: + type: string + event-trigger: + type: string + key-data: + type: array + items: + $ref: "#/definitions/key-data" + selflink: + type: string + oam-network: + description: | + OAM network, to be deprecated shortly. Do not use for new purposes. + ###### Related Nodes + - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY) + - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + required: + - network-uuid + - network-name + - cvlan-tag + properties: + network-uuid: + type: string + description: UUID of the network. Unique across a cloud-region + network-name: + type: string + description: Name of the network. + cvlan-tag: + type: integer + format: int64 + description: cvlan-id + ipv4-oam-gateway-address: + type: string + description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network + ipv4-oam-gateway-address-prefix-length: + type: integer + format: int32 + description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + oam-networks: + description: | + Collection of OAM networks, to be deprecated shortly. Do not use for new purposes. + properties: + oam-network: + type: array + items: + $ref: "#/definitions/oam-network" + operational-environment: + description: | + It is a logical partition of the cloud which allows to have multiple environments in the production AIC. + ###### Related Nodes + - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE) + - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE) + required: + - operational-environment-id + - operational-environment-name + - operational-environment-type + - operational-environment-status + - tenant-context + - workload-context + properties: + operational-environment-id: + type: string + description: UUID of an operational environment + operational-environment-name: + type: string + description: Operational Environment name + operational-environment-type: + type: string + description: Operational Environment Type. + operational-environment-status: + type: string + description: Status + tenant-context: + type: string + description: Tenant Context. + workload-context: + type: string + description: Workload Context. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + operational-environments: + description: | + a logical partition of the cloud which allows to have multiple environments in the production AIC. + properties: + operational-environment: + type: array + items: + $ref: "#/definitions/operational-environment" + overloaded-model: + description: | + Allows for legacy POST of old-style and new-style models + required: + - model-invariant-id + - model-name-version-id + - model-type + - model-name + - model-id + - model-version + properties: + model-invariant-id: + type: string + description: Unique identifier corresponding to the main definition of a model in ASDC + model-name-version-id: + type: string + description: Unique identifier corresponding to one version of a model in ASDC + model-type: + type: string + description: Type of the model, e.g., service, resource, widget, etc. + model-name: + type: string + description: Name of the model, which can change from version to version. + model-id: + type: string + description: Invariant unique ID which does not change from version to version + model-version: + type: string + description: Version + model-description: + type: string + description: Description + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-vers: + type: object + $ref: "#/definitions/model-vers" + relationship-list: + type: object + $ref: "#/definitions/relationship-list" + owning-entities: + description: | + Collection of owning-entities + properties: + owning-entity: + type: array + items: + $ref: "#/definitions/owning-entity" + owning-entity: + description: | + describes an owning-entity + ###### Related Nodes + - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE) + required: + - owning-entity-id + - owning-entity-name + properties: + owning-entity-id: + type: string + description: UUID of an owning entity + owning-entity-name: + type: string + description: Owning entity name + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" p-interface: description: | Physical interface (e.g., nic) - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO l-interface (comprises p-interface, Many2Many) - - TO physical-link (Many2Many) - - TO logical-link (Many2One) - - FROM lag-interface - - FROM pserver (is composed of p-interface) - - FROM pnf (is composed of p-interface) - - FROM vpls-pe (is composed of p-interface) + - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE) + - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE) + - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY) + - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE) + - P-INTERFACE is DELETED when these are DELETED L-INTERFACE + - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK required: - interface-name - in-maint @@ -39103,82 +51635,313 @@ definitions: type: array items: $ref: "#/definitions/p-interface" - lag-interface: + physical-link: description: | - Link aggregate interface - ###### Default Delete Scope - CASCADE_TO_CHILDREN - ###### Related Nodes - - TO logical-link (Many2Many) - - TO lag-link (Many2Many) - - TO p-interface (Many2Many) - - TO l-interface (comprises lag-interface, Many2Many) - - FROM generic-vnf (is composed of lag-interface) - - FROM pserver (is composed of lag-interface) - - FROM pnf (is composed of lag-interface) - - FROM vpls-pe (is composed of lag-interface) + Collection of physical connections, typically between p-interfaces + ###### Related Nodes + - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE) required: - - interface-name + - link-name + properties: + link-name: + type: string + description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + circuit-id: + type: string + description: Circuit it + dual-mode: + type: string + description: Dual access mode (e.g., primary, secondary + management-option: + type: string + description: To provide information on who manages this circuit. A&AI or 3rd party transport provider + service-provider-name: + type: string + description: Name of the service Provider on this link. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + physical-links: + description: | + Collection of physical connections, typically between p-interfaces + properties: + physical-link: + type: array + items: + $ref: "#/definitions/physical-link" + platform: + description: | + describes a platform + ###### Related Nodes + - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY) + required: + - platform-name + properties: + platform-name: + type: string + description: Name of the platform + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + platforms: + description: | + Collection of platforms + properties: + platform: + type: array + items: + $ref: "#/definitions/platform" + pnf: + description: | + PNF represents a physical network function. typically equipment used in the D1 world. + ###### Related Nodes + - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY) + - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE + required: + - pnf-name - in-maint properties: - interface-name: + pnf-name: type: string - description: Name that identifies the link aggregate interface - interface-description: + description: unique name of Physical Network Function. + pnf-name2: type: string - description: Human friendly text regarding this interface. + description: name of Physical Network Function. + pnf-name2-source: + type: string + description: source of name2 + pnf-id: + type: string + description: id of pnf + equip-type: + type: string + description: Equipment type. Source of truth should define valid values. + equip-vendor: + type: string + description: Equipment vendor. Source of truth should define valid values. + equip-model: + type: string + description: Equipment model. Source of truth should define valid values. + management-option: + type: string + description: identifier of managed by company or customer + ipaddress-v4-oam: + type: string + description: ipv4-oam-address with new naming convention for IP addresses + sw-version: + type: string + description: sw-version is the version of SW for the hosted application on the PNF. + in-maint: + type: boolean + frame-id: + type: string + description: ID of the physical frame (relay rack) where pnf is installed. + serial-number: + type: string + description: Serial number of the device + ipaddress-v4-loopback-0: + type: string + description: IPV4 Loopback 0 address + ipaddress-v6-loopback-0: + type: string + description: IPV6 Loopback 0 address + ipaddress-v4-aim: + type: string + description: IPV4 AIM address + ipaddress-v6-aim: + type: string + description: IPV6 AIM address + ipaddress-v6-oam: + type: string + description: IPV6 OAM address + inv-status: + type: string + description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - speed-value: + prov-status: type: string - description: Captures the numeric part of the speed - speed-units: + description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV] + nf-role: type: string - description: Captures the units corresponding to the speed + description: Nf Role is the role performed by this instance in the network. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + p-interfaces: + type: array + items: + $ref: "#/definitions/p-interface" + lag-interfaces: + type: array + items: + $ref: "#/definitions/lag-interface" + pnfs: + description: | + Collection of Physical Network Functions. + properties: + pnf: + type: array + items: + $ref: "#/definitions/pnf" + port-group: + description: | + Used to capture the network interfaces of this VCE + ###### Related Nodes + - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE) + - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG + required: + - interface-id + - orchestration-status + properties: interface-id: type: string - description: ID of interface + description: Unique ID of the interface + neutron-network-id: + type: string + description: Neutron network id of this Interface + neutron-network-name: + type: string + description: Neutron network name of this Interface interface-role: type: string description: Role assigned to this Interface, should use values as defined in ECOMP Yang models. - prov-status: + resource-version: type: string - description: Trigger for operational monitoring of this resource by Service Assurance systems. - in-maint: - type: boolean + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + port-group-id: + type: string + description: Unique ID for port group in vmware + port-group-name: + type: string + description: Likely to duplicate value of neutron network name + switch-name: + type: string + description: DVS or standard switch name (should be non-null for port groups associated with DVS) + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + cvlan-tags: + type: array + items: + $ref: "#/definitions/cvlan-tag-entry" relationship-list: type: array items: $ref: "#/definitions/relationship" - l-interfaces: + port-groups: + properties: + port-group: + type: array + items: + $ref: "#/definitions/port-group" + project: + description: | + describes the project + ###### Related Nodes + - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY) + required: + - project-name + properties: + project-name: + type: string + description: Name of the project deploying a service + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: type: array items: - $ref: "#/definitions/l-interface" - lag-interfaces: + $ref: "#/definitions/relationship" + projects: description: | - Collection of link aggregate interfaces. + Collection of projects properties: - lag-interface: + project: type: array items: - $ref: "#/definitions/lag-interface" + $ref: "#/definitions/project" + properties: + description: | + Property holder for query properties or instance properties + properties: + property-name: + type: string + property-value: + type: string + property-constraint: + description: | + TBD + ###### Related Nodes + - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + required: + - property-constraint-uuid + - constraint-type + - property-name + - property-value + properties: + property-constraint-uuid: + type: string + constraint-type: + type: string + property-name: + type: string + property-value: + type: string + resource-version: + type: string + property-constraints: + properties: + property-constraint: + type: array + items: + $ref: "#/definitions/property-constraint" pserver: description: | Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver. - ###### Default Delete Scope - ERROR_4_IN_EDGES_OR_CASCADE - ###### Related Nodes - - TO complex (Many2One) - - TO cloud-region (Many2One) - - TO availability-zone (Many2One) - - TO lag-interface (comprises pserver, Many2Many) - - TO p-interface (comprises pserver, Many2Many) - - TO zone (Many2One) - - FROM generic-vnf - - FROM group-assignment - - FROM vserver - - FROM logical-link + ###### Related Nodes + - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE) + - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE) + - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE) + - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE) + - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER + - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE + - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT required: - hostname - in-maint @@ -39280,245 +52043,396 @@ definitions: type: array items: $ref: "#/definitions/pserver" - virtual-data-center: + query-parameters: description: | - Virtual organization of cloud infrastructure elements in a data center context - ###### Default Delete Scope - CASCADE_TO_CHILDREN + QueryParameters for performing a named-query or model query + properties: + named-query: + type: object + $ref: "#/definitions/named-query" + overloaded-model: + type: object + $ref: "#/definitions/overloaded-model" + related-lookup: + description: | + TBD ###### Related Nodes - - TO generic-vnf (Many2Many) - - TO logical-link (Many2Many) - - FROM connector + - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) required: - - vdc-id - - vdc-name + - related-lookup-uuid + - source-node-type + - source-node-property + - target-node-type + - target-node-property properties: - vdc-id: + related-lookup-uuid: type: string - description: Unique ID of the vdc - vdc-name: + source-node-type: + type: string + source-node-property: + type: string + target-node-type: + type: string + target-node-property: + type: string + property-collect-list: type: string - description: Name of the virtual data center resource-version: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: $ref: "#/definitions/relationship" - virtual-data-centers: - description: | - Virtual organization of cloud infrastructure elements in a data center context + related-lookups: properties: - virtual-data-center: + related-lookup: type: array items: - $ref: "#/definitions/virtual-data-center" - cloud-infrastructure: - description: | - Namespace for cloud infrastructure. + $ref: "#/definitions/related-lookup" + related-to-property: properties: - complexes: - type: array - items: - $ref: "#/definitions/complex" - cloud-regions: - type: array - items: - $ref: "#/definitions/cloud-region" - network-profiles: - type: array - items: - $ref: "#/definitions/network-profile" - pservers: + property-key: + type: string + description: Key part of a key/value pair + property-value: + type: string + description: Value part of a key/value pair + relationship: + properties: + related-to: + type: string + description: A keyword provided by A&AI to indicate type of node. + related-link: + type: string + description: URL to the object in A&AI. + relationship-data: type: array - items: - $ref: "#/definitions/pserver" - virtual-data-centers: + items: + $ref: "#/definitions/relationship-data" + relationship-data: + required: + - relationship-key + - relationship-value + properties: + relationship-key: + type: string + description: A keyword provided by A&AI to indicate an attribute. + relationship-value: + type: string + description: Value of the attribute. + relationship-list: + properties: + relationship: type: array - items: - $ref: "#/definitions/virtual-data-center" - connector: + items: + $ref: "#/definitions/relationship" + reserved-prop-names: description: | - Collection of resource instances used to connect a variety of disparate inventory widgets - ###### Default Delete Scope - CASCADE_TO_CHILDREN - ###### Related Nodes - - TO virtual-data-center (Many2Many) - - TO metadatum (comprises connector, Many2Many) - - FROM service-instance - required: - - resource-instance-id + Internal map to define some reserved properties of a vertex properties: - resource-instance-id: + last-mod-source-of-truth: type: string - description: Unique id of resource instance. - resource-version: + aai-node-type: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - model-invariant-id: + aai-created-ts: + type: integer + format: int64 + aai-unique-key: type: string - description: the ASDC model id for this resource or service model. - model-version-id: + aai-last-mod-ts: + type: integer + format: int64 + source-of-truth: type: string - description: the ASDC model version for this resource or service model. - persona-model-version: + aai-uri: type: string - description: the ASDC model version for this resource or service model. - widget-model-id: + response-list: + description: | + Response container for the results of a named-query or model query + properties: + inventory-response-items: + type: object + $ref: "#/definitions/inventory-response-items" + result-data: + properties: + resource-type: type: string - description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. - widget-model-version: + description: The specific type of node in the A&AI graph + resource-link: type: string - description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + description: The URL to the specific resource + route-table-reference: + description: | + Openstack route table reference. + ###### Related Nodes + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY) + required: + - route-table-reference-id + - route-table-reference-fqdn + properties: + route-table-reference-id: + type: string + description: Route Table Reference id, UUID assigned to this instance. + route-table-reference-fqdn: + type: string + description: FQDN entry in the route table. + resource-version: + type: string + description: Concurrency value relationship-list: type: array items: $ref: "#/definitions/relationship" - metadata: - type: array - items: - $ref: "#/definitions/metadatum" - connectors: + route-table-references: description: | - Collection of resource instances used to connect a variety of disparate inventory widgets + Collection of openstack route table references properties: - connector: + route-table-reference: type: array items: - $ref: "#/definitions/connector" - tunnel-xconnect: + $ref: "#/definitions/route-table-reference" + route-target: description: | - Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted - ###### Default Delete Scope - THIS_NODE_ONLY + Route target information ###### Related Nodes - - FROM allotted-resource (is composed of tunnel-xconnect) + - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE) required: - - id - - bandwidth-up-wan1 - - bandwidth-down-wan1 - - bandwidth-up-wan2 - - bandwidth-down-wan2 + - global-route-target + - route-target-role properties: - id: - type: string - description: Allotted Resource id UUID assigned to this instance. - bandwidth-up-wan1: - type: string - description: The WAN uplink bandwidth for WAN1 - bandwidth-down-wan1: - type: string - description: The WAN downlink bandwidth for WAN1 - bandwidth-up-wan2: + global-route-target: type: string - description: The WAN uplink bandwidth for WAN2 - bandwidth-down-wan2: + description: Number used to identify an RT, globally unique in the network + route-target-role: type: string - description: The WAN downlink bandwidth for WAN2 + description: Role assigned to this route target resource-version: type: string - description: Concurrency value + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: $ref: "#/definitions/relationship" - tunnel-xconnects: + route-targets: description: | - This object is used to store the specific tunnel cross connect aspects of an allotted resource + Collection of route target information properties: - tunnel-xconnect: + route-target: type: array items: - $ref: "#/definitions/tunnel-xconnect" - allotted-resource: + $ref: "#/definitions/route-target" + routing-instance: description: | - Represents a slice or partial piece of a resource that gets separately allotted - ###### Default Delete Scope - CASCADE_TO_CHILDREN - ###### Related Nodes - - TO generic-vnf (Many2Many) - - TO l3-network (Many2Many) - - TO instance-group (Many2Many) - - TO network-policy (One2One) - - TO vlan (Many2Many) - - TO tunnel-xconnect (comprises allotted-resource, One2One) - - FROM service-instance (is composed of allotted-resource) - - FROM service-instance + ###### Related Nodes + - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE) + - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE) + - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR required: - - id + - routing-instance-id properties: - id: + routing-instance-id: type: string - description: Allotted Resource id UUID assigned to this instance. - description: + description: Unique id of routing instance + rpm-owner: type: string - description: The descriptive information assigned to this allotted resource instance - selflink: + description: rpm owner + resource-version: type: string - description: Link back to more information in the controller - model-invariant-id: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + site-pairs: + type: array + items: + $ref: "#/definitions/site-pair" + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + routing-instances: + description: | + set of probes related to generic-vnf routing instance + properties: + routing-instance: + type: array + items: + $ref: "#/definitions/routing-instance" + sdn-zone-response: + properties: + oam-networks: + type: object + $ref: "#/definitions/oam-networks" + az-and-dvs-switches: + type: array + items: + $ref: "#/definitions/az-and-dvs-switches" + search: + properties: + edge-tag-query-result: + type: object + $ref: "#/definitions/edge-tag-query-result" + edge-tag-query-request: + type: object + $ref: "#/definitions/edge-tag-query-request" + search-results: + type: object + $ref: "#/definitions/search-results" + sdn-zone-response: + type: object + $ref: "#/definitions/sdn-zone-response" + search-results: + properties: + result-data: + type: array + items: + $ref: "#/definitions/result-data" + secondary-filt: + description: | + SecondaryFilt for performing a named-query or model query + secondary-filter: + properties: + property-name: type: string - description: the ASDC model id for this resource or service model. - model-version-id: + filter-type: type: string - description: the ASDC model version for this resource or service model. - persona-model-version: + property-value: type: string - description: the ASDC model version for this resource or service model. + secondary-filts: + description: | + SecondaryFilts for performing a named-query or model query + properties: + secondary-filt: + type: array + items: + $ref: "#/definitions/secondary-filt" + segmentation-assignment: + description: | + Openstack segmentation assignment. + ###### Related Nodes + - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + required: + - segmentation-id + properties: + segmentation-id: + type: string + description: Route Table Reference id, UUID assigned to this instance. resource-version: type: string description: Concurrency value - orchestration-status: + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + segmentation-assignments: + description: | + Collection of openstack segmentation assignments + properties: + segmentation-assignment: + type: array + items: + $ref: "#/definitions/segmentation-assignment" + service: + description: | + Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services. + required: + - service-id + - service-description + properties: + service-id: type: string - description: Orchestration status - operational-status: + description: This gets defined by others to provide a unique ID for the service, we accept what is sent. + service-description: type: string - description: Indicator for whether the resource is considered operational - type: + description: Description of the service + service-selflink: type: string - description: Generic description of the type of allotted resource. - role: + description: URL to endpoint where AAI can get more details + resource-version: type: string - description: role in the network that this resource will be providing. - tunnel-xconnects: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + service-version: + type: string + description: service version + relationship-list: type: array items: - $ref: "#/definitions/tunnel-xconnect" + $ref: "#/definitions/relationship" + service-capabilities: + description: | + Collection of service capabilities. + properties: + service-capability: + type: array + items: + $ref: "#/definitions/service-capability" + service-capability: + description: | + Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this. + ###### Related Nodes + - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK + required: + - service-type + - vnf-type + properties: + service-type: + type: string + description: This gets defined by others to provide a unique ID for the service, we accept what is sent. + vnf-type: + type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: $ref: "#/definitions/relationship" - allotted-resources: + service-design-and-creation: description: | - This object is used to store slices of services being offered + Namespace for objects managed by ASDC properties: - allotted-resource: + vnf-images: type: array - items: - $ref: "#/definitions/allotted-resource" + items: + $ref: "#/definitions/vnf-image" + services: + type: array + items: + $ref: "#/definitions/service" + service-capabilities: + type: array + items: + $ref: "#/definitions/service-capability" + models: + type: array + items: + $ref: "#/definitions/model" + named-queries: + type: array + items: + $ref: "#/definitions/named-query" service-instance: description: | Instance of a service - ###### Default Delete Scope - CASCADE_TO_CHILDREN - ###### Related Nodes - - TO cvlan-tag (Many2Many) - - TO pnf (One2Many) - - TO connector (Many2Many) - - TO metadatum (comprises service-instance, Many2Many) - - TO logical-link (Many2Many) - - TO vlan (One2Many) - - TO service-instance (One2Many) - - TO ctag-assignment (One2Many) - - TO instance-group (Many2Many) - - TO allotted-resource (comprises service-instance, Many2Many) - - TO allotted-resource (Many2Many) - - FROM generic-vnf - - FROM l3-network - - FROM service-subscription (is composed of service-instance) - - FROM vce - - FROM service-instance + ###### Related Nodes + - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY) + - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY) + - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY) + - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY) + - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY) + - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY) + - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY) + - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY) + - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY) + - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE) + - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY) + - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM + - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK required: - service-instance-id properties: @@ -39596,12 +52510,11 @@ definitions: service-subscription: description: | Object that group service instances. - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO service-instance (comprises service-subscription, Many2Many) - - FROM customer (is composed of service-subscription) - - FROM tenant + - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE) + - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE) + - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE required: - service-type properties: @@ -39630,73 +52543,116 @@ definitions: type: array items: $ref: "#/definitions/service-subscription" - customer: + services: + description: | + Collection of service model definitions. Likely to be deprecated in favor of models from ASDC. + properties: + service: + type: array + items: + $ref: "#/definitions/service" + site-pair: description: | - customer identifiers to provide linkage back to BSS information. - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO service-subscription (comprises customer, Many2Many) + - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE) + - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE) + - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE required: - - global-customer-id - - subscriber-name - - subscriber-type + - site-pair-id properties: - global-customer-id: + site-pair-id: type: string - description: Global customer id used across ECOMP to uniquely identify customer. - subscriber-name: + description: unique identifier of probe + source-ip: type: string - description: Subscriber name, an alternate way to retrieve a customer. - subscriber-type: + description: Prefix address + destination-ip: type: string - description: Subscriber type, a way to provide VID with only the INFRA customers. + description: Prefix address + ip-version: + type: string + description: ip version, v4, v6 + destination-hostname: + type: string + description: Hostname of the destination equipment to which SLAs are measured against. + destination-equip-type: + type: string + description: The type of destinatination equipment. Could be Router, etc. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - service-subscriptions: + classes-of-service: type: array items: - $ref: "#/definitions/service-subscription" + $ref: "#/definitions/class-of-service" relationship-list: type: array items: $ref: "#/definitions/relationship" - customers: + site-pair-set: description: | - Collection of customer identifiers to provide linkage back to BSS information. + Set of instances for probes used to measure service level agreements + ###### Related Nodes + - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE) + - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE + required: + - site-pair-set-id properties: - customer: + site-pair-set-id: + type: string + description: Unique id of site pair set. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + routing-instances: type: array - items: - $ref: "#/definitions/customer" - business: + items: + $ref: "#/definitions/routing-instance" + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + site-pair-sets: description: | - Namespace for business related constructs + Collection of sets of instances for probes related to generic-vnf properties: - connectors: + site-pair-set: type: array - items: - $ref: "#/definitions/connector" - customers: + items: + $ref: "#/definitions/site-pair-set" + site-pairs: + description: | + probe within a set + properties: + site-pair: type: array - items: - $ref: "#/definitions/customer" - vnf-image: + items: + $ref: "#/definitions/site-pair" + snapshot: description: | - Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge. - ###### Default Delete Scope - ERROR_IF_ANY_IN_EDGES + Openstack snapshot ###### Related Nodes - - FROM generic-vnf + - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE) required: - - vnf-image-uuid - - application - - application-vendor + - snapshot-id properties: - vnf-image-uuid: + snapshot-id: type: string - description: Unique ID of this asset + description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. + snapshot-name: + type: string + description: Snapshot name + snapshot-architecture: + type: string + description: Operating system architecture + snapshot-os-distro: + type: string + description: The common name of the operating system distribution in lowercase + snapshot-os-version: + type: string + description: The operating system version as specified by the distributor. application: type: string description: The application that the image instantiates. @@ -39706,9 +52662,12 @@ definitions: application-version: type: string description: The version of the application. - selflink: + snapshot-selflink: type: string description: URL to endpoint where AAI can get more details + prev-snapshot-id: + type: string + description: This field contains the UUID of the previous snapshot (if any). resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. @@ -39716,542 +52675,1106 @@ definitions: type: array items: $ref: "#/definitions/relationship" - vnf-images: + snapshots: description: | - Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge. + Collection of openstack snapshots properties: - vnf-image: + snapshot: type: array items: - $ref: "#/definitions/vnf-image" - service: + $ref: "#/definitions/snapshot" + sriov-pf: description: | - Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services. - ###### Default Delete Scope - ERROR_IF_ANY_IN_EDGES + SR-IOV Physical Function + ###### Related Nodes + - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE) + - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE) required: - - service-id - - service-description + - pf-pci-id properties: - service-id: - type: string - description: This gets defined by others to provide a unique ID for the service, we accept what is sent. - service-description: + pf-pci-id: type: string - description: Description of the service - service-selflink: - type: string - description: URL to endpoint where AAI can get more details + description: Identifier for the sriov-pf resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - service-version: - type: string - description: service version relationship-list: type: array items: $ref: "#/definitions/relationship" - services: + sriov-pfs: description: | - Collection of service model definitions. Likely to be deprecated in favor of models from ASDC. + Collection of SR-IOV Physical Functions. properties: - service: + sriov-pf: type: array items: - $ref: "#/definitions/service" - service-capability: + $ref: "#/definitions/sriov-pf" + sriov-vf: description: | - Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this. - ###### Default Delete Scope - ERROR_IF_ANY_IN_EDGES + SR-IOV Virtual Function (not to be confused with virtual network function) ###### Related Nodes - - FROM availability-zone - - FROM oam-network + - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE) required: - - service-type - - vnf-type + - pci-id properties: - service-type: + pci-id: type: string - description: This gets defined by others to provide a unique ID for the service, we accept what is sent. - vnf-type: + description: PCI ID used to identify the sriov-vf + vf-vlan-filter: type: string - description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM. + vf-mac-filter: + type: string + description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM. + vf-vlan-strip: + type: boolean + description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM. + vf-vlan-anti-spoof-check: + type: boolean + description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs. + vf-mac-anti-spoof-check: + type: boolean + description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs. + vf-mirrors: + type: string + description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports. + vf-broadcast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM + vf-unknown-multicast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM + vf-unknown-unicast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM + vf-insert-stag: + type: boolean + description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM. + vf-link-status: + type: string + description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: + type: string + description: Neutron network id of the interface relationship-list: type: array items: $ref: "#/definitions/relationship" - service-capabilities: + sriov-vfs: description: | - Collection of service capabilities. + Collection of SR-IOV Virtual Functions. properties: - service-capability: + sriov-vf: type: array items: - $ref: "#/definitions/service-capability" - element-choice-set: + $ref: "#/definitions/sriov-vf" + start-node-filter: + properties: + property-name: + type: string + property-value: + type: string + subnet: description: | - This is how we would capture constraints defining allowed sets of elements. - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO model-element (comprises element-choice-set, One2Many) - - FROM constrained-element-set (is composed of element-choice-set) + - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST required: - - element-choice-set-uuid - - element-choice-set-name + - subnet-id + - dhcp-enabled properties: - element-choice-set-uuid: + subnet-id: type: string - element-choice-set-name: + description: Subnet ID, should be UUID. + subnet-name: type: string - cardinality: + description: Name associated with the subnet. + neutron-subnet-id: + type: string + description: Neutron id of this subnet + gateway-address: + type: string + description: gateway ip address + network-start-address: + type: string + description: network start address + cidr-mask: + type: string + description: cidr mask + ip-version: + type: string + description: ip version + orchestration-status: type: string + description: Orchestration status of this VNF, mastered by MSO + dhcp-enabled: + type: boolean + dhcp-start: + type: string + description: the start address reserved for use by dhcp + dhcp-end: + type: string + description: the last address reserved for use by dhcp resource-version: type: string - model-elements: - type: array - items: - $ref: "#/definitions/model-element" + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: $ref: "#/definitions/relationship" - element-choice-sets: + subnets: properties: - element-choice-set: + subnet: type: array items: - $ref: "#/definitions/element-choice-set" - constrained-element-set: + $ref: "#/definitions/subnet" + tagged-inventory-item-list: + properties: + inventory-item: + type: array + items: + $ref: "#/definitions/inventory-item" + tenant: description: | - This is how we would capture constraints defining allowed sets of elements. - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Openstack tenant ###### Related Nodes - - TO element-choice-set (comprises constrained-element-set, One2Many) - - FROM model-element (is composed of constrained-element-set) - - FROM model-constraint (is composed of constrained-element-set) + - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY) + - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY) + - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE) + - TENANT cannot be deleted if linked to VSERVER required: - - constrained-element-set-uuid - - constraint-type - - check-type + - tenant-id + - tenant-name properties: - constrained-element-set-uuid: - type: string - constraint-type: + tenant-id: type: string - check-type: + description: Unique id relative to the cloud-region. + tenant-name: type: string + description: Readable name of tenant resource-version: type: string - element-choice-sets: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + vservers: type: array items: - $ref: "#/definitions/element-choice-set" + $ref: "#/definitions/vserver" relationship-list: type: array items: $ref: "#/definitions/relationship" - constrained-element-sets: + tenants: + description: | + Collection of openstack tenants. properties: - constrained-element-set: + tenant: type: array items: - $ref: "#/definitions/constrained-element-set" - model-constraint: + $ref: "#/definitions/tenant" + tunnel-xconnect: description: | - This is how we would capture constraints defining allowed sets of elements. - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted ###### Related Nodes - - TO constrained-element-set (comprises model-constraint, One2Many) - - FROM model-element (is composed of model-constraint) + - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE) required: - - model-constraint-uuid - - constrained-element-set-uuid-to-replace + - id + - bandwidth-up-wan1 + - bandwidth-down-wan1 + - bandwidth-up-wan2 + - bandwidth-down-wan2 properties: - model-constraint-uuid: + id: type: string - constrained-element-set-uuid-to-replace: + description: Allotted Resource id UUID assigned to this instance. + bandwidth-up-wan1: type: string - constrained-element-sets: - type: array - items: - $ref: "#/definitions/constrained-element-set" + description: The WAN uplink bandwidth for WAN1 + bandwidth-down-wan1: + type: string + description: The WAN downlink bandwidth for WAN1 + bandwidth-up-wan2: + type: string + description: The WAN uplink bandwidth for WAN2 + bandwidth-down-wan2: + type: string + description: The WAN downlink bandwidth for WAN2 resource-version: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - model-constraints: + description: Concurrency value + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + tunnel-xconnects: + description: | + This object is used to store the specific tunnel cross connect aspects of an allotted resource properties: - model-constraint: + tunnel-xconnect: type: array items: - $ref: "#/definitions/model-constraint" - model-element: + $ref: "#/definitions/tunnel-xconnect" + update: description: | - Defines how other models combine to make up a higher-level model. - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team. + required: + - update-node-type + properties: + update-node-type: + type: string + update-node-key: + type: array + items: + $ref: "#/definitions/update-node-key" + update-node-uri: + type: string + action: + type: array + items: + $ref: "#/definitions/action" + update-node-key: + properties: + key-name: + type: string + key-value: + type: string + vce: + description: | + Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated. ###### Related Nodes - - TO model-ver (Many2One) - - TO model-element (comprises model-element, One2Many) - - TO model-constraint (comprises model-element, One2Many) - - TO constrained-element-set (comprises model-element, One2Many) - - FROM model-ver (is composed of model-element) - - FROM element-choice-set (is composed of model-element) - - FROM model-element (is composed of model-element) + - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY) + - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY) + - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP required: - - model-element-uuid - - new-data-del-flag - - cardinality + - vnf-id + - vnf-name + - vnf-type properties: - model-element-uuid: + vnf-id: type: string - new-data-del-flag: + description: Unique id of VNF. This is unique across the graph. + vnf-name: type: string - description: Indicates whether this element was created as part of instantiation from this model - cardinality: + description: Name of VNF. + vnf-name2: type: string - description: How many of this type of element are required/allowed - linkage-points: + description: Alternate name of VNF. + vnf-type: type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + service-id: + type: string + description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED. + regional-resource-zone: + type: string + description: Regional way of organizing pservers, source of truth should define values + prov-status: + type: string + description: Trigger for operational monitoring of this resource by Service Assurance systems. + operational-status: + type: string + description: Indicator for whether the resource is considered operational + license-key: + type: string + description: OBSOLETE - do not use + equipment-role: + type: string + description: Network role being played by this VNF + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + vpe-id: + type: string + description: Unique ID of VPE connected to this VCE. + v6-vce-wan-address: + type: string + description: Valid v6 IP address for the WAN Link on this router. Implied length of /64. + ipv4-oam-address: + type: string + description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - model-elements: + ipv4-loopback0-address: + type: string + description: Loopback0 address + entitlement-resource-uuid: + type: string + description: OBSOLETE - see child relationships + port-groups: type: array items: - $ref: "#/definitions/model-element" - description: Defines how other models combine to make up a higher-level model - model-constraints: + $ref: "#/definitions/port-group" + licenses: type: array items: - $ref: "#/definitions/model-constraint" - description: Describes new constraints on this model element that are not part of that model's definition + $ref: "#/definitions/license" + entitlements: + type: array + items: + $ref: "#/definitions/entitlement" relationship-list: type: array items: $ref: "#/definitions/relationship" - model-elements: + vces: + description: | + Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated. properties: - model-element: + vce: type: array items: - $ref: "#/definitions/model-element" - model-ver: + $ref: "#/definitions/vce" + vf-module: description: | - Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models - ###### Default Delete Scope - ERROR_4_IN_EDGES_OR_CASCADE + a deployment unit of VNFCs ###### Related Nodes - - TO model-element (comprises model-ver, One2Many) - - TO metadatum (comprises model-ver, One2Many) - - FROM model (is composed of model-ver) - - FROM model-element + - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY) + - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY) + - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE) + - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY) + - VF-MODULE cannot be deleted if linked to VNFC required: - - model-version-id - - model-name - - model-version + - vf-module-id + - is-base-vf-module properties: - model-version-id: + vf-module-id: type: string - description: Unique identifier corresponding to one version of a model in ASDC - model-name: + description: Unique ID of vf-module. + vf-module-name: type: string - description: Name of the model, which can change from version to version. - model-version: + description: Name of vf-module + heat-stack-id: type: string - description: Version - model-description: + description: Heat stack id corresponding to this instance. + orchestration-status: type: string - description: Description + description: orchestration status of this vf-module, mastered by MSO + is-base-vf-module: + type: boolean resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - model-elements: + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + model-customization-id: + type: string + description: captures the id of all the configuration used to customize the resource for the service. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + contrail-service-instance-fqdn: + type: string + description: the Contrail unique ID for a service-instance + module-index: + type: integer + format: int32 + description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit + selflink: + type: string + description: Path to the controller object. + relationship-list: type: array items: - $ref: "#/definitions/model-element" - metadata: + $ref: "#/definitions/relationship" + vf-modules: + description: | + Collection of vf-modules, a deployment unit of VNFCs + properties: + vf-module: type: array - items: - $ref: "#/definitions/metadatum" + items: + $ref: "#/definitions/vf-module" + vig-server: + description: | + vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607 + ###### Related Nodes + - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE) + required: + - vig-address-type + properties: + vig-address-type: + type: string + description: indicates whether the VIG is for AVPN or INTERNET + ipaddress-v4-vig: + type: string + description: v4 IP of the vig server + ipaddress-v6-vig: + type: string + description: v6 IP of the vig server + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: $ref: "#/definitions/relationship" - model-vers: + vig-servers: properties: - model-ver: + vig-server: type: array items: - $ref: "#/definitions/model-ver" - model: + $ref: "#/definitions/vig-server" + vip-ipv4-address-list: description: | - Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version - ###### Default Delete Scope - ERROR_4_IN_EDGES_OR_CASCADE + IPv4 Address Range ###### Related Nodes - - TO model-ver (comprises model, One2Many) - - FROM named-query - - FROM named-query-element - - FROM instance-group + - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY) + - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY) required: - - model-invariant-id - - model-type + - vip-ipv4-address properties: - model-invariant-id: + vip-ipv4-address: type: string - description: Unique identifier corresponding to the main definition of a model in ASDC - model-type: + description: IP address + vip-ipv4-prefix-length: + type: integer + format: int64 + description: Prefix length, 32 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + resource-version: type: string - description: Type of the model, e.g., service, resource, widget, etc. + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: + type: string + description: Neutron network id of the interface that address belongs to + neutron-subnet-id: + type: string + description: Neutron id of subnet that address belongs to + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + vip-ipv6-address-list: + description: | + IPv6 Address Range + ###### Related Nodes + - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY) + - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY) + required: + - vip-ipv6-address + properties: + vip-ipv6-address: + type: string + description: IP address + vip-ipv6-prefix-length: + type: integer + format: int64 + description: Prefix length, 128 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - model-vers: + neutron-network-id: + type: string + description: Neutron network id of the interface that address belongs to + neutron-subnet-id: + type: string + description: Neutron id of subnet that address belongs to + relationship-list: type: array items: - $ref: "#/definitions/model-ver" + $ref: "#/definitions/relationship" + virtual-data-center: + description: | + Virtual organization of cloud infrastructure elements in a data center context + ###### Related Nodes + - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + required: + - vdc-id + - vdc-name + properties: + vdc-id: + type: string + description: Unique ID of the vdc + vdc-name: + type: string + description: Name of the virtual data center + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: $ref: "#/definitions/relationship" - models: + virtual-data-centers: description: | - Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models + Virtual organization of cloud infrastructure elements in a data center context properties: - model: + virtual-data-center: type: array items: - $ref: "#/definitions/model" - related-lookup: + $ref: "#/definitions/virtual-data-center" + vlan: description: | - TBD - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Definition of vlan ###### Related Nodes - - FROM named-query-element (is composed of related-lookup) + - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE) + - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST + - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK required: - - related-lookup-uuid - - source-node-type - - source-node-property - - target-node-type - - target-node-property + - vlan-interface + - in-maint properties: - related-lookup-uuid: + vlan-interface: type: string - source-node-type: + description: String that identifies the interface + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + resource-version: type: string - source-node-property: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + speed-value: type: string - target-node-type: + description: Captures the numeric part of the speed + speed-units: type: string - target-node-property: + description: Captures the units corresponding to the speed + vlan-description: type: string - property-collect-list: + description: Used to describe (the service associated with) the vlan + backdoor-connection: type: string - resource-version: + description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device. + vpn-id: + type: string + description: This indicates the customers VPN ID associated with this vlan + orchestration-status: type: string + description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C. + in-maint: + type: boolean relationship-list: type: array items: $ref: "#/definitions/relationship" - related-lookups: + l3-interface-ipv4-address-list: + type: array + items: + $ref: "#/definitions/l3-interface-ipv4-address-list" + l3-interface-ipv6-address-list: + type: array + items: + $ref: "#/definitions/l3-interface-ipv6-address-list" + vlans: properties: - related-lookup: + vlan: type: array items: - $ref: "#/definitions/related-lookup" - property-constraint: + $ref: "#/definitions/vlan" + vnf: description: | - TBD - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Abstract vnf class + required: + - vnf-id + properties: + vnf-id: + type: string + description: Unique id of VNF. This is unique across the graph. + vnf-image: + description: | + Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge. ###### Related Nodes - - FROM named-query-element (is composed of property-constraint) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE) + - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF required: - - property-constraint-uuid - - constraint-type - - property-name - - property-value + - vnf-image-uuid + - application + - application-vendor properties: - property-constraint-uuid: + vnf-image-uuid: type: string - constraint-type: + description: Unique ID of this asset + application: type: string - property-name: + description: The application that the image instantiates. + application-vendor: type: string - property-value: + description: The vendor of the application. + application-version: type: string + description: The version of the application. + selflink: + type: string + description: URL to endpoint where AAI can get more details resource-version: type: string - property-constraints: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/definitions/relationship" + vnf-images: + description: | + Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge. properties: - property-constraint: + vnf-image: type: array items: - $ref: "#/definitions/property-constraint" - named-query-element: + $ref: "#/definitions/vnf-image" + vnfc: description: | - TBD - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO named-query-element (comprises named-query-element, Many2Many) - - TO model (Many2One) - - TO property-constraint (comprises named-query-element, One2Many) - - TO related-lookup (comprises named-query-element, One2Many) - - FROM named-query (is composed of named-query-element) - - FROM named-query-element (is composed of named-query-element) + - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY) required: - - named-query-element-uuid + - vnfc-name + - vnfc-function-code + - vnfc-type + - in-maint + - is-closed-loop-disabled properties: - named-query-element-uuid: + vnfc-name: type: string - property-collect-list: + description: Unique ID of vnfc. + vnfc-function-code: type: string - resource-version: + description: function code + vnfc-type: type: string - property-limit-desc: + description: type + prov-status: type: string - do-not-output: + description: prov status of this vnfc + orchestration-status: type: string - named-query-elements: + description: Orchestration status of this VNF, mastered by APP-C + ipaddress-v4-oam-vip: + type: string + description: Oam V4 vip address of this vnfc + in-maint: + type: boolean + is-closed-loop-disabled: + type: boolean + group-notation: + type: string + description: Group notation of VNFC + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: type: array items: - $ref: "#/definitions/named-query-element" - related-lookups: + $ref: "#/definitions/relationship" + vnfcs: + description: | + virtual network components associated with a vserver from application controller. + properties: + vnfc: + type: array + items: + $ref: "#/definitions/vnfc" + volume: + description: | + Ephemeral Block storage volume. + ###### Related Nodes + - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume) + required: + - volume-id + - volume-selflink + properties: + volume-id: + type: string + description: Unique ID of block storage volume relative to the vserver. + volume-selflink: + type: string + description: URL to endpoint where AAI can get more details + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: type: array items: - $ref: "#/definitions/related-lookup" - property-constraints: + $ref: "#/definitions/relationship" + volume-group: + description: | + Persistent block-level storage. + ###### Related Nodes + - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + required: + - volume-group-id + - volume-group-name + - vnf-type + properties: + volume-group-id: + type: string + description: Unique ID of volume-group. + volume-group-name: + type: string + description: Name of the volume group. + heat-stack-id: + type: string + description: Heat stack id corresponding to this volume-group + vnf-type: + type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + orchestration-status: + type: string + description: Orchestration status of this volume-group + model-customization-id: + type: string + description: captures the id of all the configuration used to customize the resource for the service. + vf-module-model-customization-id: + type: string + description: helps relate the volume group to the vf-module whose components will require the volume group + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: type: array items: - $ref: "#/definitions/property-constraint" + $ref: "#/definitions/relationship" + volume-groups: + description: | + Collection of persistent block-level storage. + properties: + volume-group: + type: array + items: + $ref: "#/definitions/volume-group" + volumes: + description: | + Collection of ephemeral Block storage volumes. + properties: + volume: + type: array + items: + $ref: "#/definitions/volume" + vpls-pe: + description: | + VPLS Provider Edge routers. + ###### Related Nodes + - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE + required: + - equipment-name + properties: + equipment-name: + type: string + prov-status: + type: string + description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. + ipv4-oam-address: + type: string + description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address). + equipment-role: + type: string + description: Client should send valid enumerated value, e.g., VPLS-PE. + vlan-id-outer: + type: integer + format: int64 + description: Temporary location for stag to get to VCE + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: $ref: "#/definitions/relationship" - named-query-elements: + p-interfaces: + type: array + items: + $ref: "#/definitions/p-interface" + lag-interfaces: + type: array + items: + $ref: "#/definitions/lag-interface" + vpls-pes: + description: | + Collection of VPLS Provider Edge routers properties: - named-query-element: + vpls-pe: type: array items: - $ref: "#/definitions/named-query-element" - named-query: + $ref: "#/definitions/vpls-pe" + vpn-binding: description: | - TBD - ###### Default Delete Scope - CASCADE_TO_CHILDREN + VPN binding ###### Related Nodes - - TO model (One2Many) - - TO named-query-element (comprises named-query, One2One) + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE) + - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK + - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET required: - - named-query-uuid - - named-query-name - - named-query-version + - vpn-id + - vpn-name properties: - named-query-uuid: + vpn-id: type: string - named-query-name: + description: VPN ID, globally unique within A&AI + vpn-name: type: string - named-query-version: + description: VPN Name + vpn-platform: type: string - required-input-param: + description: the platform associated with the VPN example AVPN, Mobility + vpn-type: type: string - description: + description: Type of the vpn, should be taken from enumerated/valid values + route-distinguisher: type: string + description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network. resource-version: type: string - named-query-elements: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + route-targets: type: array items: - $ref: "#/definitions/named-query-element" + $ref: "#/definitions/route-target" relationship-list: type: array items: $ref: "#/definitions/relationship" - named-queries: + description: l3-networks relate to vpn-bindings + vpn-bindings: properties: - named-query: + vpn-binding: type: array items: - $ref: "#/definitions/named-query" - service-design-and-creation: + $ref: "#/definitions/vpn-binding" + vserver: description: | - Namespace for objects managed by ASDC + Virtual Servers, aka virtual machine or VM. + ###### Related Nodes + - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE) + - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE) + - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE) + - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE) + - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE) + - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY) + - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY) + - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY) + - VSERVER is DELETED when these are DELETED L-INTERFACE + - VSERVER deletion means associated objects of these types are also DELETED:VOLUME + required: + - vserver-id + - vserver-name + - vserver-selflink + - in-maint + - is-closed-loop-disabled properties: - vnf-images: + vserver-id: + type: string + description: Unique identifier for this vserver relative to its tenant + vserver-name: + type: string + description: Name of vserver + vserver-name2: + type: string + description: Alternative name of vserver + prov-status: + type: string + description: Trigger for operational monitoring of this resource by Service Assurance systems. + vserver-selflink: + type: string + description: URL to endpoint where AAI can get more details + in-maint: + type: boolean + is-closed-loop-disabled: + type: boolean + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + volumes: type: array items: - $ref: "#/definitions/vnf-image" - services: + $ref: "#/definitions/volume" + relationship-list: type: array items: - $ref: "#/definitions/service" - service-capabilities: + $ref: "#/definitions/relationship" + l-interfaces: type: array items: - $ref: "#/definitions/service-capability" - models: + $ref: "#/definitions/l-interface" + vservers: + description: | + Collection of virtual Servers, aka virtual machines or VMs. + properties: + vserver: type: array - items: - $ref: "#/definitions/model" - named-queries: + items: + $ref: "#/definitions/vserver" + zone: + description: | + A zone is a grouping of assets in a location homing to the same connections into the CBB + ###### Related Nodes + - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + required: + - zone-id + - zone-name + - design-type + - zone-context + properties: + zone-id: + type: string + description: Code assigned by AIC to the zone + zone-name: + type: string + description: English name associated with the zone + design-type: + type: string + description: Design of zone [Medium/Large?] + zone-context: + type: string + description: Context of zone [production/test] + status: + type: string + description: Status of a zone. + resource-version: + type: string + description: Concurrency value + relationship-list: type: array items: - $ref: "#/definitions/named-query" - logical-link: + $ref: "#/definitions/relationship" + zones: description: | - Logical links generally connect l-interfaces but are used to express logical connectivity between two points - ###### Default Delete Scope - THIS_NODE_ONLY - ###### Related Nodes - - TO lag-link (Many2Many) - - TO pnf (Many2Many) - - TO logical-link (One2Many) - - TO generic-vnf (Many2Many) - - TO pserver (Many2Many) - - TO cloud-region (Many2Many) - - TO vpn-binding (Many2Many) - - FROM l-interface - - FROM lag-interface - - FROM p-interface - - FROM service-instance - - FROM virtual-data-center - - FROM vlan - - FROM logical-link - required: - - link-name - - link-type + Collection of zones properties: - link-name: + zone: + type: array + items: + $ref: "#/definitions/zone" +patchDefinitions: + aai-internal: + properties: + property-name: type: string - description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ - link-type: + property-value: type: string - description: Type of logical link, e.g., evc - speed-value: + action: + properties: + action-type: type: string - description: Captures the numeric part of the speed - speed-units: + action-data: + type: array + items: + $ref: "#/patchDefinitions/action-data" + action-data: + properties: + property-name: type: string - description: Captures the units corresponding to the speed - ip-version: + property-value: type: string - description: v4, v6, or ds for dual stack - routing-protocol: + actions: + description: | + APIs that are more action related than REST (e.g., notify, update). + properties: + update: + type: object + $ref: "#/patchDefinitions/update" + notify: + type: object + $ref: "#/patchDefinitions/notify" + allotted-resource: + description: | + Represents a slice or partial piece of a resource that gets separately allotted + ###### Related Nodes + - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY) + - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY) + - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE) + - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY) + - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY) + - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT + required: + - id + properties: + id: type: string - description: For example, static or BGP - resource-version: + description: Allotted Resource id UUID assigned to this instance. + description: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + description: The descriptive information assigned to this allotted resource instance + selflink: + type: string + description: Link back to more information in the controller model-invariant-id: type: string description: the ASDC model id for this resource or service model. @@ -40261,51 +53784,72 @@ definitions: persona-model-version: type: string description: the ASDC model version for this resource or service model. - widget-model-id: + allotted-resources: + description: | + This object is used to store slices of services being offered + properties: + allotted-resource: + type: array + items: + $ref: "#/patchDefinitions/allotted-resource" + availability-zone: + description: | + Availability zone, a collection of compute hosts/pservers + ###### Related Nodes + - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE) + - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE + required: + - availability-zone-name + - hypervisor-type + properties: + availability-zone-name: type: string - description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. - widget-model-version: + description: Name of the availability zone. Unique across a cloud region + hypervisor-type: type: string - description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + description: Type of hypervisor. Source of truth should define valid values. operational-status: type: string - description: Indication of operational status of the logical link. - prov-status: - type: string - description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. - link-role: - type: string - description: Indication of the network use of the logical link. - link-name2: - type: string - description: Alias or alternate name (CLCI or D1 name). - link-id: - type: string - description: UUID of the logical-link, SDNC generates this. - circuit-id: - type: string - description: Circuit id - purpose: - type: string - description: Reason for this entity, role it is playing - relationship-list: - type: array - items: - $ref: "#/definitions/relationship" - logical-links: + description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values. + availability-zones: description: | - Collection of logical connections + Collection of availability zones properties: - logical-link: + availability-zone: type: array items: - $ref: "#/definitions/logical-link" + $ref: "#/patchDefinitions/availability-zone" + az-and-dvs-switches: + properties: + dvs-switches: + type: object + $ref: "#/patchDefinitions/dvs-switches" + availability-zone: + type: object + $ref: "#/patchDefinitions/availability-zone" + business: + description: | + Namespace for business related constructs + properties: + connectors: + type: array + items: + $ref: "#/patchDefinitions/connector" + customers: + type: array + items: + $ref: "#/patchDefinitions/customer" class-of-service: description: | - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - FROM site-pair (is composed of class-of-service) + - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE) required: - cos properties: @@ -40318,13 +53862,6 @@ definitions: probe-type: type: string description: type of probe - resource-version: - type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - relationship-list: - type: array - items: - $ref: "#/definitions/relationship" classes-of-service: description: | class-of-service of probe @@ -40332,257 +53869,1733 @@ definitions: class-of-service: type: array items: - $ref: "#/definitions/class-of-service" - site-pair: + $ref: "#/patchDefinitions/class-of-service" + cloud-infrastructure: description: | - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Namespace for cloud infrastructure. + properties: + complexes: + type: array + items: + $ref: "#/patchDefinitions/complex" + cloud-regions: + type: array + items: + $ref: "#/patchDefinitions/cloud-region" + network-profiles: + type: array + items: + $ref: "#/patchDefinitions/network-profile" + pservers: + type: array + items: + $ref: "#/patchDefinitions/pserver" + virtual-data-centers: + type: array + items: + $ref: "#/patchDefinitions/virtual-data-center" + cloud-region: + description: | + cloud-region designates an installation of a cloud cluster or region or instantiation ###### Related Nodes - - TO class-of-service (comprises site-pair, Many2Many) - - FROM routing-instance (is composed of site-pair) + - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE) + - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP + - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE required: - - site-pair-id + - cloud-owner + - cloud-region-id properties: - site-pair-id: + cloud-owner: type: string - description: unique identifier of probe - source-ip: + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + cloud-region-id: type: string - description: Prefix address - destination-ip: + description: Identifier used by the vendor for the region. Second part of composite key + cloud-type: type: string - description: Prefix address - ip-version: + description: Type of the cloud (e.g., openstack) + owner-defined-type: type: string - description: ip version, v4, v6 - destination-hostname: + description: Cloud-owner defined type indicator (e.g., dcp, lcp) + cloud-region-version: type: string - description: Hostname of the destination equipment to which SLAs are measured against. - destination-equip-type: + description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE. + identity-url: type: string - description: The type of destinatination equipment. Could be Router, etc. - resource-version: + description: URL of the keystone identity service + cloud-zone: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - classes-of-service: + description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED. + complex-name: + type: string + description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED. + cloud-regions: + properties: + cloud-region: type: array - items: - $ref: "#/definitions/class-of-service" - relationship-list: + items: + $ref: "#/patchDefinitions/cloud-region" + complex: + description: | + Collection of physical locations that can house cloud-regions. + ###### Related Nodes + - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE) + - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY) + - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY) + - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE + - COMPLEX is DELETED when these are DELETED CTAG-POOL + required: + - physical-location-id + - physical-location-type + - street1 + - city + - postal-code + - country + - region + properties: + physical-location-id: + type: string + description: Unique identifier for physical location, e.g., CLLI + data-center-code: + type: string + description: Data center code which can be an alternate way to identify a complex + complex-name: + type: string + description: Gamma complex name for LCP instance. + identity-url: + type: string + description: URL of the keystone identity service + complexes: + description: | + Collection of physical locations that can house cloud-regions. + properties: + complex: type: array - items: - $ref: "#/definitions/relationship" - site-pairs: + items: + $ref: "#/patchDefinitions/complex" + configuration: description: | - probe within a set + Port Mirror Configuration. + ###### Related Nodes + - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE) + - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY) + - CONFIGURATION is DELETED when these are DELETED METADATUM + - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK + required: + - configuration-id + - configuration-type + - configuration-sub-type + - orchestration-status + - operational-status + - configuration-selflink + - model-customization-id properties: - site-pair: + configuration-id: + type: string + description: UUID assigned to configuration. + management-option: + type: string + description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well. + configuration-name: + type: string + description: Name of the configuration. + configuration-type: + type: string + description: port-mirroring-configuration. + configuration-sub-type: + type: string + description: vprobe, pprobe. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + orchestration-status: + type: string + description: Orchestration status of the configuration. + operational-status: + type: string + description: Indicator for whether the resource is considered operational. + configuration-selflink: + type: string + description: URL to endpoint where AAI can get more details from SDN-GC. + model-customization-id: + type: string + description: id of the configuration used to customize the resource + configurations: + description: | + Collection of configurations + properties: + configuration: type: array items: - $ref: "#/definitions/site-pair" - routing-instance: + $ref: "#/patchDefinitions/configuration" + connector: description: | - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Collection of resource instances used to connect a variety of disparate inventory widgets ###### Related Nodes - - TO site-pair (comprises routing-instance, Many2Many) - - FROM site-pair-set (is composed of routing-instance) + - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY) + - CONNECTOR is DELETED when these are DELETED METADATUM required: - - routing-instance-id + - resource-instance-id properties: - routing-instance-id: + resource-instance-id: type: string - description: Unique id of routing instance - rpm-owner: + description: Unique id of resource instance. + connectors: + description: | + Collection of resource instances used to connect a variety of disparate inventory widgets + properties: + connector: + type: array + items: + $ref: "#/patchDefinitions/connector" + constrained-element-set: + description: | + This is how we would capture constraints defining allowed sets of elements. + ###### Related Nodes + - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE) + - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE) + - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET + required: + - constrained-element-set-uuid + - constraint-type + - check-type + properties: + constrained-element-set-uuid: type: string - description: rpm owner - resource-version: + constraint-type: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - site-pairs: + check-type: + type: string + constrained-element-sets: + properties: + constrained-element-set: type: array - items: - $ref: "#/definitions/site-pair" - relationship-list: + items: + $ref: "#/patchDefinitions/constrained-element-set" + ctag-assignment: + description: | + ###### Related Nodes + - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY) + required: + - vlan-id-inner + properties: + vlan-id-inner: + type: integer + format: int64 + description: id. + ctag-assignments: + properties: + ctag-assignment: type: array - items: - $ref: "#/definitions/relationship" - routing-instances: + items: + $ref: "#/patchDefinitions/ctag-assignment" + ctag-pool: description: | - set of probes related to generic-vnf routing instance + A collection of C tags (vlan tags) grouped for a specific purpose. + ###### Related Nodes + - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE) + - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY) + required: + - target-pe + - availability-zone-name + - ctag-pool-purpose properties: - routing-instance: + target-pe: + type: string + description: The Target provider edge router + availability-zone-name: + type: string + description: Name of the availability zone + ctag-pool-purpose: + type: string + description: Describes what the intended purpose of this pool is. + ctag-values: + type: string + description: Comma separated list of ctags + ctag-pools: + properties: + ctag-pool: type: array items: - $ref: "#/definitions/routing-instance" - site-pair-set: + $ref: "#/patchDefinitions/ctag-pool" + customer: description: | - Set of instances for probes used to measure service level agreements - ###### Default Delete Scope - CASCADE_TO_CHILDREN + customer identifiers to provide linkage back to BSS information. ###### Related Nodes - - TO routing-instance (comprises site-pair-set, Many2Many) - - FROM generic-vnf + - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE) + - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION required: - - site-pair-set-id + - global-customer-id + - subscriber-name + - subscriber-type properties: - site-pair-set-id: + global-customer-id: type: string - description: Unique id of site pair set. - resource-version: + description: Global customer id used across ECOMP to uniquely identify customer. + subscriber-name: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - routing-instances: + description: Subscriber name, an alternate way to retrieve a customer. + subscriber-type: + type: string + description: Subscriber type, a way to provide VID with only the INFRA customers. + customers: + description: | + Collection of customer identifiers to provide linkage back to BSS information. + properties: + customer: type: array - items: - $ref: "#/definitions/routing-instance" - relationship-list: + items: + $ref: "#/patchDefinitions/customer" + cvlan-tag-entry: + required: + - cvlan-tag + properties: + cvlan-tag: + type: integer + format: int64 + description: See mis-na-virtualization-platform.yang + cvlan-tags: + properties: + cvlan-tag-entry: type: array - items: - $ref: "#/definitions/relationship" - site-pair-sets: + items: + $ref: "#/patchDefinitions/cvlan-tag-entry" + dvs-switch: description: | - Collection of sets of instances for probes related to generic-vnf + Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI. + ###### Related Nodes + - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + required: + - switch-name + - vcenter-url properties: - site-pair-set: + switch-name: + type: string + description: DVS switch name + vcenter-url: + type: string + description: URL used to reach the vcenter + dvs-switches: + description: | + Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs. + properties: + dvs-switch: type: array items: - $ref: "#/definitions/site-pair-set" - route-target: + $ref: "#/patchDefinitions/dvs-switch" + edge-prop-names: description: | - Route target information - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Internal map to define the properties of an edge and interpret the map EdgeRules + properties: + edgeLabel: + type: string + direction: + type: string + multiplicityRule: + type: string + isParent: + type: boolean + usesResource: + type: boolean + hasDelTarget: + type: boolean + SVC-INFRA: + type: boolean + SVC-INFRA-REV: + type: boolean + edge-tag-query-request: + properties: + edge-tag: + type: string + result-detail: + type: string + start-node-type: + type: string + start-node-filter: + type: array + items: + $ref: "#/patchDefinitions/start-node-filter" + include-node-filter: + type: array + items: + $ref: "#/patchDefinitions/include-node-filter" + secondary-filter: + type: array + items: + $ref: "#/patchDefinitions/secondary-filter" + edge-tag-query-result: + properties: + tagged-inventory-item-list: + type: array + items: + $ref: "#/patchDefinitions/tagged-inventory-item-list" + element-choice-set: + description: | + This is how we would capture constraints defining allowed sets of elements. ###### Related Nodes - - FROM vpn-binding (is composed of route-target) + - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE) + - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT required: - - global-route-target - - route-target-role + - element-choice-set-uuid + - element-choice-set-name properties: - global-route-target: + element-choice-set-uuid: type: string - description: Number used to identify an RT, globally unique in the network - route-target-role: + element-choice-set-name: type: string - description: Role assigned to this route target - resource-version: + cardinality: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - relationship-list: + element-choice-sets: + properties: + element-choice-set: type: array - items: - $ref: "#/definitions/relationship" - route-targets: + items: + $ref: "#/patchDefinitions/element-choice-set" + entitlement: description: | - Collection of route target information + Metadata for entitlement group. + ###### Related Nodes + - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + required: + - group-uuid + - resource-uuid properties: - route-target: + group-uuid: + type: string + description: Unique ID for the entitlement group the resource comes from, should be uuid. + resource-uuid: + type: string + description: Unique ID of an entitlement resource. + entitlements: + description: | + Entitlements, keyed by group-uuid and resource-uuid, related to license management + properties: + entitlement: type: array items: - $ref: "#/definitions/route-target" - vpn-binding: + $ref: "#/patchDefinitions/entitlement" + esr-ems: description: | - VPN binding - ###### Default Delete Scope - ERROR_4_IN_EDGES_OR_CASCADE + Persist EMS address information used by EMS driver. ###### Related Nodes - - TO route-target (comprises vpn-binding, One2Many) - - FROM l3-network - - FROM logical-link + - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many) + - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO required: - - vpn-id - - vpn-name + - ems-id properties: - vpn-id: + ems-id: type: string - description: VPN ID, globally unique within A&AI - vpn-name: + description: Unique ID of EMS. + esr-ems-list: + properties: + esr-ems: + type: array + items: + $ref: "#/patchDefinitions/esr-ems" + esr-system-info: + description: | + Persist common address information of external systems. + ###### Related Nodes + - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info) + - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info) + - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info) + - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info) + required: + - esr-system-info-id + - user-name + - password + - system-type + properties: + esr-system-info-id: type: string - description: VPN Name - vpn-platform: + description: Unique ID of esr system info. + system-name: type: string - description: the platform associated with the VPN example AVPN, Mobility - vpn-type: + description: name of external system. + type: type: string - description: Type of the vpn, should be taken from enumerated/valid values - route-distinguisher: + description: type of external systems. + vendor: type: string - description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network. - resource-version: + description: vendor of external systems. + version: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - route-targets: + description: version of external systems. + service-url: + type: string + description: url used to access external systems. + user-name: + type: string + description: username used to access external systems. + password: + type: string + description: password used to access external systems. + system-type: + type: string + description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm. + protocol: + type: string + description: protocol of third party SDNC, for example netconf/snmp. + ssl-cacert: + type: string + description: ca file content if enabled ssl on auth-url. + ssl-insecure: + type: boolean + description: Whether to verify VIM's certificate. + ip-address: + type: string + description: service IP of ftp server. + port: + type: string + description: service port of ftp server. + cloud-domain: + type: string + description: domain info for authentication. + default-tenant: + type: string + description: default tenant of VIM. + passive: + type: boolean + description: ftp passive mode or not. + remote-path: + type: string + description: resource or performance data file path. + system-status: + type: string + description: the status of external system. + esr-system-info-list: + description: | + Collection of persistent block-level external system auth info. + properties: + esr-system-info: type: array - items: - $ref: "#/definitions/route-target" - relationship-list: + items: + $ref: "#/patchDefinitions/esr-system-info" + esr-thirdparty-sdnc: + description: | + Persist SDNC address information used by ONAP SDNC. + ###### Related Nodes + - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One) + - TO pnf( esr-thirdparty-sdnc has pnf, One2Many) + - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO + required: + - thirdparty-sdnc-id + properties: + thirdparty-sdnc-id: + type: string + description: Unique ID of SDNC. + location: + type: string + description: used for DC type to indicate the location of SDNC, such as Core or Edge. + product-name: + type: string + description: password used to access SDNC server. + esr-thirdparty-sdnc-list: + properties: + esr-thirdparty-sdnc: type: array - items: - $ref: "#/definitions/relationship" - description: l3-networks relate to vpn-bindings - vpn-bindings: + items: + $ref: "#/patchDefinitions/esr-thirdparty-sdnc" + esr-vnfm: + description: | + Persist VNFM address information used by VF-C. + ###### Related Nodes + - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One) + - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO + required: + - vnfm-id properties: - vpn-binding: + vnfm-id: + type: string + description: Unique ID of VNFM. + vim-id: + type: string + description: indecate the VIM to deploy VNF. + certificate-url: + type: string + description: certificate url of VNFM. + esr-vnfm-list: + properties: + esr-vnfm: type: array items: - $ref: "#/definitions/vpn-binding" - vpls-pe: + $ref: "#/patchDefinitions/esr-vnfm" + evc: description: | - VPLS Provider Edge routers. - ###### Default Delete Scope - CASCADE_TO_CHILDREN + evc object is an optional child object of the Configuration object. ###### Related Nodes - - TO complex (Many2Many) - - TO ctag-pool (Many2Many) - - TO p-interface (comprises vpls-pe, Many2Many) - - TO lag-interface (comprises vpls-pe, Many2Many) + - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE) required: - - equipment-name + - evc-id properties: - equipment-name: + evc-id: + type: string + description: Unique/key field for the evc object + forwarding-path-topology: + type: string + description: Point-to-Point, Multi-Point + cir-value: + type: string + description: Commited Information Rate + cir-units: + type: string + description: CIR units + connection-diversity-group-id: + type: string + description: Diversity Group ID + service-hours: + type: string + description: formerly Performance Group + esp-evc-circuit-id: + type: string + description: EVC Circuit ID of ESP EVC + esp-evc-cir-value: + type: string + description: Committed Information Rate (For ESP) + esp-evc-cir-units: + type: string + description: CIR units (For ESP) + esp-itu-code: + type: string + description: Identifies ESP + collector-pop-clli: + type: string + description: Collector POP CLLI (from the hostname of the access pnf) + inter-connect-type-ingress: + type: string + description: Interconnect type on ingress side of EVC. + tagmode-access-ingress: + type: string + description: tagode for collector side of EVC + tagmode-access-egress: + type: string + description: tagMode for network side of EVC + evcs: + properties: + evc: + type: array + items: + $ref: "#/patchDefinitions/evc" + external-system: + description: | + Namespace for external system. + properties: + esr-ems-list: + type: object + $ref: "#/patchDefinitions/esr-ems-list" + esr-vnfm-list: + type: object + $ref: "#/patchDefinitions/esr-vnfm-list" + esr-thirdparty-sdnc-list: + type: object + $ref: "#/patchDefinitions/esr-thirdparty-sdnc-list" + extra-properties: + description: | + Extra properties for inventory item for response list + properties: + extra-property: + type: array + items: + $ref: "#/patchDefinitions/extra-property" + extra-property: + properties: + property-name: + type: string + property-value: type: string + flavor: + description: | + Openstack flavor. + ###### Related Nodes + - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE) + - FLAVOR cannot be deleted if linked to VSERVER + required: + - flavor-id + - flavor-name + - flavor-selflink + properties: + flavor-id: + type: string + description: Flavor id, expected to be unique across cloud-region. + flavor-name: + type: string + description: Flavor name + flavor-vcpus: + type: integer + format: int32 + description: Number of CPUs + flavor-ram: + type: integer + format: int32 + description: Amount of memory + flavor-disk: + type: integer + format: int32 + description: Disk space + flavor-ephemeral: + type: integer + format: int32 + description: Amount of ephemeral disk space + flavor-swap: + type: string + description: amount of swap space allocation + flavor-is-public: + type: boolean + description: whether flavor is available to all users or private to the tenant it was created in. + flavor-selflink: + type: string + description: URL to endpoint where AAI can get more details + flavor-disabled: + type: boolean + description: Boolean as to whether this flavor is no longer enabled + flavors: + description: | + Collection of openstack flavors. + properties: + flavor: + type: array + items: + $ref: "#/patchDefinitions/flavor" + forwarder: + description: | + Entity describing a sequenced segment of forwarding path + ###### Related Nodes + - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE) + - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE) + - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE) + - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE) + - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE) + - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION + required: + - sequence + properties: + sequence: + type: integer + format: int32 + description: Unique ID of this segmentation + forwarder-role: + type: string + description: ingress, intermediate, egress + forwarder-evc: + description: | + forwarder object is an optional child object of the Configuration object. + ###### Related Nodes + - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE) + required: + - forwarder-evc-id + properties: + forwarder-evc-id: + type: string + description: Key for forwarder-evc object + circuit-id: + type: string + description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC + ivlan: + type: string + description: Internal VLAN. + svlan: + type: string + description: SVLAN value for ingress of egress forwarder. + cvlan: + type: string + description: CVLAN value for ingress of egress forwarder. + forwarder-evcs: + properties: + forwarder-evc: + type: array + items: + $ref: "#/patchDefinitions/forwarder-evc" + forwarders: + properties: + forwarder: + type: array + items: + $ref: "#/patchDefinitions/forwarder" + forwarding-path: + description: | + Entity that describes the sequenced forwarding path between interfaces of services or resources + ###### Related Nodes + - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE) + - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE) + - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE) + - FORWARDING-PATH is DELETED when these are DELETED FORWARDER + - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION + required: + - forwarding-path-id + - forwarding-path-name + properties: + forwarding-path-id: + type: string + description: Unique ID of this FP + forwarding-path-name: + type: string + description: Name of the FP + forwarding-paths: + properties: + forwarding-path: + type: array + items: + $ref: "#/patchDefinitions/forwarding-path" + generic-vnf: + description: | + General purpose VNF + ###### Related Nodes + - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE) + - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY) + - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY) + - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE) + - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY) + - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY) + - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY) + - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY) + - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE + required: + - vnf-id + - vnf-name + - vnf-type + - in-maint + - is-closed-loop-disabled + properties: + vnf-id: + type: string + description: Unique id of VNF. This is unique across the graph. + vnf-name: + type: string + description: Name of VNF. + vnf-name2: + type: string + description: Alternate name of VNF. + vnf-type: + type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + service-id: + type: string + description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED + regional-resource-zone: + type: string + description: Regional way of organizing pservers, source of truth should define values prov-status: type: string - description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. - ipv4-oam-address: + description: Trigger for operational monitoring of this resource by Service Assurance systems. + operational-status: type: string - description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address). + description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path. + license-key: + type: string + description: OBSOLETE - do not use equipment-role: type: string - description: Client should send valid enumerated value, e.g., VPLS-PE. - vlan-id-outer: + description: Client should send valid enumerated value + orchestration-status: + type: string + description: Orchestration status of this VNF, used by MSO. + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + management-option: + type: string + description: identifier of managed by company or customer + ipv4-oam-address: + type: string + description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf. + ipv4-loopback0-address: + type: string + description: v4 Loopback0 address + nm-lan-v6-address: + type: string + description: v6 Loopback address + management-v6-address: + type: string + description: v6 management address + vcpu: type: integer format: int64 - description: Temporary location for stag to get to VCE - resource-version: + description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases + vcpu-units: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - relationship-list: + description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases + vmemory: + type: integer + format: int64 + description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases + vmemory-units: + type: string + description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases + vdisk: + type: integer + format: int64 + description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases + vdisk-units: + type: string + description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases + in-maint: + type: boolean + is-closed-loop-disabled: + type: boolean + generic-vnfs: + description: | + Collection of VNFs + properties: + generic-vnf: type: array - items: - $ref: "#/definitions/relationship" - p-interfaces: + items: + $ref: "#/patchDefinitions/generic-vnf" + group-assignment: + description: | + Openstack group-assignment used to store exclusivity groups (EG). + ###### Related Nodes + - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY) + required: + - group-id + - group-type + - group-name + properties: + group-id: + type: string + description: Group id, expected to be unique across cloud-region. + group-type: + type: string + description: Group type - the type of group this instance refers to + group-name: + type: string + description: Group name - name assigned to the group + group-description: + type: string + description: Group description - description of the group + group-assignments: + description: | + Collection of openstack group assignments + properties: + group-assignment: + type: array + items: + $ref: "#/patchDefinitions/group-assignment" + host-route: + description: | + ###### Related Nodes + - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE) + required: + - host-route-id + - route-prefix + - next-hop + properties: + host-route-id: + type: string + description: host-route id + route-prefix: + type: string + description: subnet prefix + next-hop: + type: string + description: Could be ip-address, hostname, or service-instance + next-hop-type: + type: string + description: Should be ip-address, hostname, or service-instance to match next-hop + host-routes: + properties: + host-route: + type: array + items: + $ref: "#/patchDefinitions/host-route" + image: + description: | + Openstack image. + ###### Related Nodes + - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE) + - IMAGE cannot be deleted if linked to VSERVER + - IMAGE is DELETED when these are DELETED METADATUM + required: + - image-id + - image-name + - image-os-distro + - image-os-version + - image-selflink + properties: + image-id: + type: string + description: Image id, expected to be unique across cloud region + image-name: + type: string + description: Image name + image-architecture: + type: string + description: Operating system architecture. + image-os-distro: + type: string + description: The common name of the operating system distribution in lowercase + image-os-version: + type: string + description: The operating system version as specified by the distributor. + application: + type: string + description: The application that the image instantiates. + application-vendor: + type: string + description: The vendor of the application. + application-version: + type: string + description: The version of the application. + image-selflink: + type: string + description: URL to endpoint where AAI can get more details + images: + description: | + Collectio of Openstack images. + properties: + image: + type: array + items: + $ref: "#/patchDefinitions/image" + include-node-filter: + properties: + include-node-type: + type: string + instance-filter: + description: | + InstanceFilter for performing a named-query or model query + instance-filters: + description: | + InstanceFilters for performing a named-query or model query + properties: + instance-filter: + type: array + items: + $ref: "#/patchDefinitions/instance-filter" + instance-group: + description: | + General mechanism for grouping instances + ###### Related Nodes + - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + required: + - id + - description + - type + properties: + id: + type: string + description: Instance Group ID, UUID assigned to this instance. + description: + type: string + description: Descriptive text to help identify the usage of this instance-group + type: + type: string + description: Only valid value today is lower case ha for high availability + sub-type: + type: string + description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby] + instance-groups: + description: | + Collection of openstack route table references + properties: + instance-group: + type: array + items: + $ref: "#/patchDefinitions/instance-group" + inventory: + properties: + search: + type: object + $ref: "#/patchDefinitions/search" + actions: + type: object + $ref: "#/patchDefinitions/actions" + cloud-infrastructure: + type: object + $ref: "#/patchDefinitions/cloud-infrastructure" + business: + type: object + $ref: "#/patchDefinitions/business" + service-design-and-creation: + type: object + $ref: "#/patchDefinitions/service-design-and-creation" + network: + type: object + $ref: "#/patchDefinitions/network" + aai-internal: + type: object + $ref: "#/patchDefinitions/aai-internal" + nodes: type: array items: - $ref: "#/definitions/p-interface" - lag-interfaces: + $ref: "#/patchDefinitions/aai-internal" + inventory-item: + properties: + inventory-item-type: + type: string + inventory-item-link: + type: string + inventory-item-data: + type: array + items: + $ref: "#/patchDefinitions/inventory-item-data" + tagged-inventory-item-list: + type: array + items: + $ref: "#/patchDefinitions/tagged-inventory-item-list" + inventory-item-data: + properties: + property-name: + type: string + property-value: + type: string + inventory-response-item: + description: | + Inventory item for response list + properties: + model-name: + type: string + extra-properties: + type: object + $ref: "#/patchDefinitions/extra-properties" + inventory-response-items: + type: object + $ref: "#/patchDefinitions/inventory-response-items" + inventory-response-items: + description: | + Container for inventory items in response list + properties: + inventory-response-item: + type: array + items: + $ref: "#/patchDefinitions/inventory-response-item" + ipsec-configuration: + description: | + IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C + ###### Related Nodes + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE) + - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE) + - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER + required: + - ipsec-configuration-id + properties: + ipsec-configuration-id: + type: string + description: UUID of this configuration + requested-vig-address-type: + type: string + description: Indicate the type of VIG server like AVPN, INTERNET, BOTH + requested-encryption-strength: + type: string + description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc + requested-dmz-type: + type: string + description: can offer a shared DMZ or a DMZ specific to a customer + shared-dmz-network-address: + type: string + description: Network address of shared DMZ + requested-customer-name: + type: string + description: If the DMZ is a custom DMZ, this field will indicate the customer information + ike-version: + type: string + description: can be 1 or 2 + ikev1-authentication: + type: string + description: Contains values like md5, sha1, sha256, sha384 + ikev1-encryption: + type: string + description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc + ikev1-dh-group: + type: string + description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14 + ikev1-am-group-id: + type: string + description: Group name defined in VIG for clients using aggressive mode + ikev1-am-password: + type: string + description: pre-shared key for the above group name + ikev1-sa-lifetime: + type: string + description: Lifetime for IKEv1 SA + ipsec-authentication: + type: string + description: md5, sha1, sha256, sha384 + ipsec-encryption: + type: string + description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc + ipsec-sa-lifetime: + type: string + description: Life time for IPSec SA + ipsec-pfs: + type: string + description: enable PFS or not + xauth-userid: + type: string + description: user ID for xAuth, sm-user, ,nmteHostName + xauth-user-password: + type: string + description: Encrypted using the Juniper $9$ algorithm + dpd-interval: + type: string + description: The time between DPD probe + dpd-frequency: + type: string + description: Maximum number of DPD before claiming the tunnel is down + ipsec-configurations: + properties: + ipsec-configuration: + type: array + items: + $ref: "#/patchDefinitions/ipsec-configuration" + key-data: + properties: + key-name: + type: string + key-value: + type: string + l-interface: + description: | + Logical interfaces, e.g., a vnic. + ###### Related Nodes + - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE) + - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY) + - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE) + - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE) + - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE) + - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN + - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK + required: + - interface-name + - is-port-mirrored + - in-maint + properties: + interface-name: + type: string + description: Name given to the interface + interface-role: + type: string + description: E.g., CUSTOMER, UPLINK, etc. + v6-wan-link-ip: + type: string + description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B. + selflink: + type: string + description: URL to endpoint where AAI can get more details + interface-id: + type: string + description: ID of interface + macaddr: + type: string + description: MAC address for the interface + network-name: + type: string + description: Name of the network + management-option: + type: string + description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER + interface-description: + type: string + description: Human friendly text regarding this interface. + is-port-mirrored: + type: boolean + l-interfaces: + description: | + Collection of logical interfaces. + properties: + l-interface: + type: array + items: + $ref: "#/patchDefinitions/l-interface" + l3-interface-ipv4-address-list: + description: | + IPv4 Address Range + ###### Related Nodes + - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + required: + - l3-interface-ipv4-address + properties: + l3-interface-ipv4-address: + type: string + description: IP address + l3-interface-ipv4-prefix-length: + type: integer + format: int64 + description: Prefix length, 32 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + l3-interface-ipv6-address-list: + description: | + IPv6 Address Range + ###### Related Nodes + - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + required: + - l3-interface-ipv6-address + properties: + l3-interface-ipv6-address: + type: string + description: IP address + l3-interface-ipv6-prefix-length: + type: integer + format: int64 + description: Prefix length, 128 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + l3-network: + description: | + Generic network definition + ###### Related Nodes + - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY) + - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY) + - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY) + - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY) + - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET + required: + - network-id + - network-name + - is-bound-to-vpn + - is-provider-network + - is-shared-network + - is-external-network + properties: + network-id: + type: string + description: Network ID, should be uuid. Unique across A&AI. + network-name: + type: string + description: Name of the network, governed by some naming convention.. + network-type: + type: string + description: Type of the network - who defines these values? + network-role: + type: string + description: Role the network plans - who defines these values? + network-technology: + type: string + description: Network technology - who defines these values? + neutron-network-id: + type: string + description: Neutron network id of this Interface + is-bound-to-vpn: + type: boolean + service-id: + type: string + description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED + network-role-instance: + type: integer + format: int64 + description: network role instance + l3-networks: + properties: + l3-network: + type: array + items: + $ref: "#/patchDefinitions/l3-network" + lag-interface: + description: | + Link aggregate interface + ###### Related Nodes + - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY) + - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY) + - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE) + - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE + - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK + required: + - interface-name + - in-maint + properties: + interface-name: + type: string + description: Name that identifies the link aggregate interface + interface-description: + type: string + description: Human friendly text regarding this interface. + lag-interfaces: + description: | + Collection of link aggregate interfaces. + properties: + lag-interface: + type: array + items: + $ref: "#/patchDefinitions/lag-interface" + lag-link: + description: | + LAG links can connect lag-interfaces + ###### Related Nodes + - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY) + required: + - link-name + properties: + link-name: + type: string + description: Alphabetical concatenation of lag-interface names + lag-links: + description: | + Collection of link aggregation connections + properties: + lag-link: + type: array + items: + $ref: "#/patchDefinitions/lag-link" + license: + description: | + Metadata for license group. + ###### Related Nodes + - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + required: + - group-uuid + - resource-uuid + properties: + group-uuid: + type: string + description: Unique ID for the license group the resource belongs to, should be uuid. + resource-uuid: + type: string + description: Unique ID of a license resource. + licenses: + description: | + Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management + properties: + license: + type: array + items: + $ref: "#/patchDefinitions/license" + line-of-business: + description: | + describes a line-of-business + ###### Related Nodes + - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY) + required: + - line-of-business-name + properties: + line-of-business-name: + type: string + description: Name of the line-of-business (product) + lines-of-business: + description: | + Collection of lines-of-business + properties: + line-of-business: + type: array + items: + $ref: "#/patchDefinitions/line-of-business" + logical-link: + description: | + Logical links generally connect l-interfaces but are used to express logical connectivity between two points + ###### Related Nodes + - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY) + - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY) + - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY) + - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY) + - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY) + - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY) + - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + required: + - link-name + - link-type + properties: + link-name: + type: string + description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ + link-type: + type: string + description: Type of logical link, e.g., evc + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + ip-version: + type: string + description: v4, v6, or ds for dual stack + routing-protocol: + type: string + description: For example, static or BGP + logical-links: + description: | + Collection of logical connections + properties: + logical-link: + type: array + items: + $ref: "#/patchDefinitions/logical-link" + metadata: + description: | + Collection of metadatum (key/value pairs) + properties: + metadatum: + type: array + items: + $ref: "#/patchDefinitions/metadatum" + metadatum: + description: | + Key/value pairs + ###### Related Nodes + - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE) + - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE) + - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + required: + - metaname + - metaval + properties: + metaname: + type: string + metaval: + type: string + model: + description: | + Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version + ###### Related Nodes + - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY) + - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE) + - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT + - MODEL is DELETED when these are DELETED MODEL-VER + required: + - model-invariant-id + - model-type + properties: + model-invariant-id: + type: string + description: Unique identifier corresponding to the main definition of a model in ASDC + model-type: + type: string + description: Type of the model, e.g., service, resource, widget, etc. + model-and-named-query-search: + description: | + ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query + properties: + query-parameters: + type: object + $ref: "#/patchDefinitions/query-parameters" + instance-filters: + type: object + $ref: "#/patchDefinitions/instance-filters" + secondary-filts: + type: object + $ref: "#/patchDefinitions/secondary-filts" + top-node-type: + type: string + secondary-filter-cut-point: + type: string + model-constraint: + description: | + This is how we would capture constraints defining allowed sets of elements. + ###### Related Nodes + - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE) + - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET + required: + - model-constraint-uuid + - constrained-element-set-uuid-to-replace + properties: + model-constraint-uuid: + type: string + constrained-element-set-uuid-to-replace: + type: string + constrained-element-sets: type: array items: - $ref: "#/definitions/lag-interface" - vpls-pes: + $ref: "#/patchDefinitions/constrained-element-set" + model-constraints: + properties: + model-constraint: + type: array + items: + $ref: "#/patchDefinitions/model-constraint" + model-element: description: | - Collection of VPLS Provider Edge routers + Defines how other models combine to make up a higher-level model. + ###### Related Nodes + - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE) + - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE) + - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT + required: + - model-element-uuid + - new-data-del-flag + - cardinality properties: - vpls-pe: + model-element-uuid: + type: string + new-data-del-flag: + type: string + description: Indicates whether this element was created as part of instantiation from this model + cardinality: + type: string + description: How many of this type of element are required/allowed + linkage-points: + type: string + model-elements: + properties: + model-element: type: array items: - $ref: "#/definitions/vpls-pe" + $ref: "#/patchDefinitions/model-element" + model-ver: + description: | + Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models + ###### Related Nodes + - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT + - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM + required: + - model-version-id + - model-name + - model-version + properties: + model-version-id: + type: string + description: Unique identifier corresponding to one version of a model in ASDC + model-name: + type: string + description: Name of the model, which can change from version to version. + model-version: + type: string + description: Version + model-description: + type: string + description: Description + model-vers: + properties: + model-ver: + type: array + items: + $ref: "#/patchDefinitions/model-ver" + models: + description: | + Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models + properties: + model: + type: array + items: + $ref: "#/patchDefinitions/model" multicast-configuration: description: | - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - FROM vlan + - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY) required: - multicast-configuration-id - multicast-protocol @@ -40597,13 +55610,6 @@ definitions: rp-type: type: string description: rp type of multicast configuration - resource-version: - type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - relationship-list: - type: array - items: - $ref: "#/definitions/relationship" multicast-configurations: description: | multicast configuration of generic-vnf ip-address @@ -40611,36 +55617,602 @@ definitions: multicast-configuration: type: array items: - $ref: "#/definitions/multicast-configuration" - cvlan-tag-entry: + $ref: "#/patchDefinitions/multicast-configuration" + named-queries: + properties: + named-query: + type: array + items: + $ref: "#/patchDefinitions/named-query" + named-query: + description: | + TBD + ###### Related Nodes + - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT + required: + - named-query-uuid + - named-query-name + - named-query-version + properties: + named-query-uuid: + type: string + named-query-name: + type: string + named-query-version: + type: string + required-input-param: + type: string + description: + type: string + named-query-element: + description: | + TBD + ###### Related Nodes + - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE) + - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP + required: + - named-query-element-uuid + properties: + named-query-element-uuid: + type: string + property-collect-list: + type: string + named-query-elements: + properties: + named-query-element: + type: array + items: + $ref: "#/patchDefinitions/named-query-element" + network: + description: | + Namespace for network inventory resources. + properties: + logical-links: + type: array + items: + $ref: "#/patchDefinitions/logical-link" + site-pair-sets: + type: array + items: + $ref: "#/patchDefinitions/site-pair-set" + vpn-bindings: + type: array + items: + $ref: "#/patchDefinitions/vpn-binding" + vpls-pes: + type: array + items: + $ref: "#/patchDefinitions/vpls-pe" + multicast-configurations: + type: array + items: + $ref: "#/patchDefinitions/multicast-configuration" + vces: + type: array + items: + $ref: "#/patchDefinitions/vce" + vnfcs: + type: array + items: + $ref: "#/patchDefinitions/vnfc" + l3-networks: + type: array + items: + $ref: "#/patchDefinitions/l3-network" + network-policies: + type: array + items: + $ref: "#/patchDefinitions/network-policy" + generic-vnfs: + type: array + items: + $ref: "#/patchDefinitions/generic-vnf" + lag-links: + type: array + items: + $ref: "#/patchDefinitions/lag-link" + newvces: + type: array + items: + $ref: "#/patchDefinitions/newvce" + pnfs: + type: array + items: + $ref: "#/patchDefinitions/pnf" + physical-links: + type: array + items: + $ref: "#/patchDefinitions/physical-link" + ipsec-configurations: + type: array + items: + $ref: "#/patchDefinitions/ipsec-configuration" + route-table-references: + type: array + items: + $ref: "#/patchDefinitions/route-table-reference" + instance-groups: + type: array + items: + $ref: "#/patchDefinitions/instance-group" + zones: + type: array + items: + $ref: "#/patchDefinitions/zone" + network-policies: + properties: + network-policy: + type: array + items: + $ref: "#/patchDefinitions/network-policy" + network-policy: + description: | + ###### Related Nodes + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE) + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY) + required: + - network-policy-id + properties: + network-policy-id: + type: string + description: UUID representing unique key to this instance + network-policy-fqdn: + type: string + description: Contrail FQDN for the policy + heat-stack-id: + type: string + description: ID for the openStack Heat instance + network-profile: + description: | + Network profile populated by SDN-GP for SNMP + ###### Related Nodes + - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) required: + - nm-profile-name + properties: + nm-profile-name: + type: string + description: Unique name of network profile. + community-string: + type: string + description: Encrypted SNMP community string + network-profiles: + description: | + Collection of network profiles + properties: + network-profile: + type: array + items: + $ref: "#/patchDefinitions/network-profile" + newvce: + description: | + This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce. + ###### Related Nodes + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE) + - NEWVCE is DELETED when these are DELETED L-INTERFACE + required: + - vnf-id2 + - vnf-name + - vnf-type + properties: + vnf-id2: + type: string + description: Unique id of VNF, can't use same attribute name right now until we promote this new object + vnf-name: + type: string + description: Name of VNF. + vnf-name2: + type: string + description: Alternate name of VNF. + vnf-type: + type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + prov-status: + type: string + description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. + operational-status: + type: string + description: Indicator for whether the resource is considered operational + license-key: + type: string + description: OBSOLETE - do not use + ipv4-oam-address: + type: string + description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address). + equipment-role: + type: string + description: Client should send valid enumerated value. + newvces: + description: | + This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce. + properties: + newvce: + type: array + items: + $ref: "#/patchDefinitions/newvce" + notification-event: + properties: + cambria.partition: + type: string + notification-event-header: + type: object + $ref: "#/patchDefinitions/notification-event-header" + notification-event-header: + properties: + id: + type: string + timestamp: + type: string + source-name: + type: string + domain: + type: string + sequence-number: + type: string + severity: + type: string + event-type: + type: string + version: + type: string + action: + type: string + entity-type: + type: string + top-entity-type: + type: string + entity-link: + type: string + status: + type: string + notify: + required: + - event-id + properties: + event-id: + type: string + node-type: + type: string + event-trigger: + type: string + key-data: + type: array + items: + $ref: "#/patchDefinitions/key-data" + selflink: + type: string + oam-network: + description: | + OAM network, to be deprecated shortly. Do not use for new purposes. + ###### Related Nodes + - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY) + - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + required: + - network-uuid + - network-name - cvlan-tag properties: + network-uuid: + type: string + description: UUID of the network. Unique across a cloud-region + network-name: + type: string + description: Name of the network. cvlan-tag: type: integer format: int64 - description: See mis-na-virtualization-platform.yang - resource-version: + description: cvlan-id + ipv4-oam-gateway-address: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - relationship-list: + description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network + ipv4-oam-gateway-address-prefix-length: + type: integer + format: int32 + description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network + oam-networks: + description: | + Collection of OAM networks, to be deprecated shortly. Do not use for new purposes. + properties: + oam-network: type: array - items: - $ref: "#/definitions/relationship" - cvlan-tags: + items: + $ref: "#/patchDefinitions/oam-network" + operational-environment: + description: | + It is a logical partition of the cloud which allows to have multiple environments in the production AIC. + ###### Related Nodes + - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE) + - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE) + required: + - operational-environment-id + - operational-environment-name + - operational-environment-type + - operational-environment-status + - tenant-context + - workload-context properties: - cvlan-tag-entry: + operational-environment-id: + type: string + description: UUID of an operational environment + operational-environment-name: + type: string + description: Operational Environment name + operational-environment-type: + type: string + description: Operational Environment Type. + operational-environment-status: + type: string + description: Status + tenant-context: + type: string + description: Tenant Context. + workload-context: + type: string + description: Workload Context. + operational-environments: + description: | + a logical partition of the cloud which allows to have multiple environments in the production AIC. + properties: + operational-environment: type: array items: - $ref: "#/definitions/cvlan-tag-entry" + $ref: "#/patchDefinitions/operational-environment" + overloaded-model: + description: | + Allows for legacy POST of old-style and new-style models + required: + - model-invariant-id + - model-name-version-id + - model-type + - model-name + - model-id + - model-version + properties: + model-invariant-id: + type: string + description: Unique identifier corresponding to the main definition of a model in ASDC + model-name-version-id: + type: string + description: Unique identifier corresponding to one version of a model in ASDC + model-type: + type: string + description: Type of the model, e.g., service, resource, widget, etc. + model-name: + type: string + description: Name of the model, which can change from version to version. + model-id: + type: string + description: Invariant unique ID which does not change from version to version + model-version: + type: string + description: Version + model-description: + type: string + description: Description + owning-entities: + description: | + Collection of owning-entities + properties: + owning-entity: + type: array + items: + $ref: "#/patchDefinitions/owning-entity" + owning-entity: + description: | + describes an owning-entity + ###### Related Nodes + - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE) + required: + - owning-entity-id + - owning-entity-name + properties: + owning-entity-id: + type: string + description: UUID of an owning entity + owning-entity-name: + type: string + description: Owning entity name + p-interface: + description: | + Physical interface (e.g., nic) + ###### Related Nodes + - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE) + - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE) + - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY) + - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE) + - P-INTERFACE is DELETED when these are DELETED L-INTERFACE + - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK + required: + - interface-name + - in-maint + properties: + interface-name: + type: string + description: Name that identifies the physical interface + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + port-description: + type: string + description: Nature of the services and connectivity on this port. + equipment-identifier: + type: string + description: CLEI or other specification for p-interface hardware. + interface-role: + type: string + description: Role specification for p-interface hardware. + interface-type: + type: string + description: Indicates the physical properties of the interface. + prov-status: + type: string + description: Trigger for operational monitoring of this resource by Service Assurance systems. + p-interfaces: + description: | + Collection of physical interfaces. + properties: + p-interface: + type: array + items: + $ref: "#/patchDefinitions/p-interface" + physical-link: + description: | + Collection of physical connections, typically between p-interfaces + ###### Related Nodes + - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE) + required: + - link-name + properties: + link-name: + type: string + description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + circuit-id: + type: string + description: Circuit it + dual-mode: + type: string + description: Dual access mode (e.g., primary, secondary + management-option: + type: string + description: To provide information on who manages this circuit. A&AI or 3rd party transport provider + service-provider-name: + type: string + description: Name of the service Provider on this link. + physical-links: + description: | + Collection of physical connections, typically between p-interfaces + properties: + physical-link: + type: array + items: + $ref: "#/patchDefinitions/physical-link" + platform: + description: | + describes a platform + ###### Related Nodes + - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY) + required: + - platform-name + properties: + platform-name: + type: string + description: Name of the platform + platforms: + description: | + Collection of platforms + properties: + platform: + type: array + items: + $ref: "#/patchDefinitions/platform" + pnf: + description: | + PNF represents a physical network function. typically equipment used in the D1 world. + ###### Related Nodes + - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY) + - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE + required: + - pnf-name + - in-maint + properties: + pnf-name: + type: string + description: unique name of Physical Network Function. + pnf-name2: + type: string + description: name of Physical Network Function. + pnf-name2-source: + type: string + description: source of name2 + pnf-id: + type: string + description: id of pnf + equip-type: + type: string + description: Equipment type. Source of truth should define valid values. + equip-vendor: + type: string + description: Equipment vendor. Source of truth should define valid values. + equip-model: + type: string + description: Equipment model. Source of truth should define valid values. + management-option: + type: string + description: identifier of managed by company or customer + ipaddress-v4-oam: + type: string + description: ipv4-oam-address with new naming convention for IP addresses + sw-version: + type: string + description: sw-version is the version of SW for the hosted application on the PNF. + in-maint: + type: boolean + frame-id: + type: string + description: ID of the physical frame (relay rack) where pnf is installed. + serial-number: + type: string + description: Serial number of the device + ipaddress-v4-loopback-0: + type: string + description: IPV4 Loopback 0 address + ipaddress-v6-loopback-0: + type: string + description: IPV6 Loopback 0 address + ipaddress-v4-aim: + type: string + description: IPV4 AIM address + ipaddress-v6-aim: + type: string + description: IPV6 AIM address + ipaddress-v6-oam: + type: string + description: IPV6 OAM address + inv-status: + type: string + description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. + pnfs: + description: | + Collection of Physical Network Functions. + properties: + pnf: + type: array + items: + $ref: "#/patchDefinitions/pnf" port-group: description: | Used to capture the network interfaces of this VCE - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO cvlan-tag (comprises port-group, Many2Many) - - FROM vce (is composed of port-group) + - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE) + - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG required: - interface-id - orchestration-status @@ -40657,120 +56229,913 @@ definitions: interface-role: type: string description: Role assigned to this Interface, should use values as defined in ECOMP Yang models. - resource-version: + port-groups: + properties: + port-group: + type: array + items: + $ref: "#/patchDefinitions/port-group" + project: + description: | + describes the project + ###### Related Nodes + - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY) + required: + - project-name + properties: + project-name: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - port-group-id: + description: Name of the project deploying a service + projects: + description: | + Collection of projects + properties: + project: + type: array + items: + $ref: "#/patchDefinitions/project" + properties: + description: | + Property holder for query properties or instance properties + properties: + property-name: type: string - description: Unique ID for port group in vmware - port-group-name: + property-value: type: string - description: Likely to duplicate value of neutron network name - switch-name: + property-constraint: + description: | + TBD + ###### Related Nodes + - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + required: + - property-constraint-uuid + - constraint-type + - property-name + - property-value + properties: + property-constraint-uuid: type: string - description: DVS or standard switch name (should be non-null for port groups associated with DVS) - orchestration-status: + constraint-type: type: string - description: Orchestration status of this VNF, mastered by MSO - heat-stack-id: + property-name: type: string - description: Heat stack id corresponding to this instance, managed by MSO - mso-catalog-key: + property-value: type: string - description: Corresponds to the SDN-C catalog id used to configure this VCE - cvlan-tags: + property-constraints: + properties: + property-constraint: + type: array + items: + $ref: "#/patchDefinitions/property-constraint" + pserver: + description: | + Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver. + ###### Related Nodes + - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE) + - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE) + - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE) + - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE) + - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER + - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE + - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT + required: + - hostname + - in-maint + properties: + hostname: + type: string + description: Value from executing hostname on the compute node. + ptnii-equip-name: + type: string + description: PTNII name + number-of-cpus: + type: integer + format: int32 + description: Number of cpus + disk-in-gigabytes: + type: integer + format: int32 + description: Disk size, in GBs + ram-in-megabytes: + type: integer + format: int32 + description: RAM size, in MBs + equip-type: + type: string + description: Equipment type. Source of truth should define valid values. + equip-vendor: + type: string + description: Equipment vendor. Source of truth should define valid values. + equip-model: + type: string + description: Equipment model. Source of truth should define valid values. + fqdn: + type: string + description: Fully-qualified domain name + pserver-selflink: + type: string + description: URL to endpoint where AAI can get more details + ipv4-oam-address: + type: string + description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device. + serial-number: + type: string + description: Serial number, may be queried + ipaddress-v4-loopback-0: + type: string + description: IPV4 Loopback 0 address + ipaddress-v6-loopback-0: + type: string + description: IPV6 Loopback 0 address + ipaddress-v4-aim: + type: string + description: IPV4 AIM address + ipaddress-v6-aim: + type: string + description: IPV6 AIM address + ipaddress-v6-oam: + type: string + description: IPV6 OAM address + inv-status: + type: string + description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. + pserver-id: + type: string + description: ID of Pserver + internet-topology: + type: string + description: internet topology of Pserver + in-maint: + type: boolean + pservers: + description: | + Collection of compute hosts. + properties: + pserver: + type: array + items: + $ref: "#/patchDefinitions/pserver" + query-parameters: + description: | + QueryParameters for performing a named-query or model query + properties: + named-query: + type: object + $ref: "#/patchDefinitions/named-query" + overloaded-model: + type: object + $ref: "#/patchDefinitions/overloaded-model" + related-lookup: + description: | + TBD + ###### Related Nodes + - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + required: + - related-lookup-uuid + - source-node-type + - source-node-property + - target-node-type + - target-node-property + properties: + related-lookup-uuid: + type: string + source-node-type: + type: string + source-node-property: + type: string + target-node-type: + type: string + target-node-property: + type: string + property-collect-list: + type: string + related-lookups: + properties: + related-lookup: + type: array + items: + $ref: "#/patchDefinitions/related-lookup" + related-to-property: + properties: + property-key: + type: string + description: Key part of a key/value pair + property-value: + type: string + description: Value part of a key/value pair + relationship: + properties: + related-to: + type: string + description: A keyword provided by A&AI to indicate type of node. + related-link: + type: string + description: URL to the object in A&AI. + relationship-data: + type: array + items: + $ref: "#/patchDefinitions/relationship-data" + related-to-property: + type: array + items: + $ref: "#/patchDefinitions/related-to-property" + relationship-data: + required: + - relationship-key + - relationship-value + properties: + relationship-key: + type: string + description: A keyword provided by A&AI to indicate an attribute. + relationship-value: + type: string + description: Value of the attribute. + reserved-prop-names: + description: | + Internal map to define some reserved properties of a vertex + properties: + last-mod-source-of-truth: + type: string + aai-node-type: + type: string + aai-created-ts: + type: integer + format: int64 + aai-unique-key: + type: string + aai-last-mod-ts: + type: integer + format: int64 + source-of-truth: + type: string + aai-uri: + type: string + response-list: + description: | + Response container for the results of a named-query or model query + properties: + inventory-response-items: + type: object + $ref: "#/patchDefinitions/inventory-response-items" + result-data: + properties: + resource-type: + type: string + description: The specific type of node in the A&AI graph + resource-link: + type: string + description: The URL to the specific resource + route-table-reference: + description: | + Openstack route table reference. + ###### Related Nodes + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY) + required: + - route-table-reference-id + - route-table-reference-fqdn + properties: + route-table-reference-id: + type: string + description: Route Table Reference id, UUID assigned to this instance. + route-table-reference-fqdn: + type: string + description: FQDN entry in the route table. + route-table-references: + description: | + Collection of openstack route table references + properties: + route-table-reference: + type: array + items: + $ref: "#/patchDefinitions/route-table-reference" + route-target: + description: | + Route target information + ###### Related Nodes + - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE) + required: + - global-route-target + - route-target-role + properties: + global-route-target: + type: string + description: Number used to identify an RT, globally unique in the network + route-target-role: + type: string + description: Role assigned to this route target + route-targets: + description: | + Collection of route target information + properties: + route-target: + type: array + items: + $ref: "#/patchDefinitions/route-target" + routing-instance: + description: | + ###### Related Nodes + - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE) + - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE) + - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR + required: + - routing-instance-id + properties: + routing-instance-id: + type: string + description: Unique id of routing instance + rpm-owner: + type: string + description: rpm owner + routing-instances: + description: | + set of probes related to generic-vnf routing instance + properties: + routing-instance: + type: array + items: + $ref: "#/patchDefinitions/routing-instance" + sdn-zone-response: + properties: + oam-networks: + type: object + $ref: "#/patchDefinitions/oam-networks" + az-and-dvs-switches: + type: array + items: + $ref: "#/patchDefinitions/az-and-dvs-switches" + search: + properties: + edge-tag-query-result: + type: object + $ref: "#/patchDefinitions/edge-tag-query-result" + edge-tag-query-request: + type: object + $ref: "#/patchDefinitions/edge-tag-query-request" + search-results: + type: object + $ref: "#/patchDefinitions/search-results" + sdn-zone-response: + type: object + $ref: "#/patchDefinitions/sdn-zone-response" + search-results: + properties: + result-data: + type: array + items: + $ref: "#/patchDefinitions/result-data" + secondary-filt: + description: | + SecondaryFilt for performing a named-query or model query + secondary-filter: + properties: + property-name: + type: string + filter-type: + type: string + property-value: + type: string + secondary-filts: + description: | + SecondaryFilts for performing a named-query or model query + properties: + secondary-filt: + type: array + items: + $ref: "#/patchDefinitions/secondary-filt" + segmentation-assignment: + description: | + Openstack segmentation assignment. + ###### Related Nodes + - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + required: + - segmentation-id + properties: + segmentation-id: + type: string + description: Route Table Reference id, UUID assigned to this instance. + segmentation-assignments: + description: | + Collection of openstack segmentation assignments + properties: + segmentation-assignment: + type: array + items: + $ref: "#/patchDefinitions/segmentation-assignment" + service: + description: | + Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services. + required: + - service-id + - service-description + properties: + service-id: + type: string + description: This gets defined by others to provide a unique ID for the service, we accept what is sent. + service-description: + type: string + description: Description of the service + service-selflink: + type: string + description: URL to endpoint where AAI can get more details + service-capabilities: + description: | + Collection of service capabilities. + properties: + service-capability: + type: array + items: + $ref: "#/patchDefinitions/service-capability" + service-capability: + description: | + Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this. + ###### Related Nodes + - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK + required: + - service-type + - vnf-type + properties: + service-type: + type: string + description: This gets defined by others to provide a unique ID for the service, we accept what is sent. + vnf-type: + type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + service-design-and-creation: + description: | + Namespace for objects managed by ASDC + properties: + vnf-images: type: array items: - $ref: "#/definitions/cvlan-tag-entry" - relationship-list: + $ref: "#/patchDefinitions/vnf-image" + services: type: array items: - $ref: "#/definitions/relationship" - port-groups: + $ref: "#/patchDefinitions/service" + service-capabilities: + type: array + items: + $ref: "#/patchDefinitions/service-capability" + models: + type: array + items: + $ref: "#/patchDefinitions/model" + named-queries: + type: array + items: + $ref: "#/patchDefinitions/named-query" + service-instance: + description: | + Instance of a service + ###### Related Nodes + - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY) + - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY) + - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY) + - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY) + - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY) + - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY) + - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY) + - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY) + - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY) + - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE) + - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY) + - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM + - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK + required: + - service-instance-id properties: - port-group: + service-instance-id: + type: string + description: Uniquely identifies this instance of a service + service-instance-name: + type: string + description: This field will store a name assigned to the service-instance. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + bandwidth-total: + type: string + description: Indicates the total bandwidth to be used for this service. + bandwidth-up-wan1: + type: string + description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device. + bandwidth-down-wan1: + type: string + description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device. + bandwidth-up-wan2: + type: string + description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device. + bandwidth-down-wan2: + type: string + description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device. + vhn-portal-url: + type: string + description: URL customers will use to access the vHN Portal. + service-instance-location-id: + type: string + description: An identifier that customers assign to the location where this service is being used. + service-instances: + description: | + Collection of service instances + properties: + service-instance: type: array items: - $ref: "#/definitions/port-group" - license: + $ref: "#/patchDefinitions/service-instance" + service-subscription: description: | - Metadata for license group. - ###### Default Delete Scope - THIS_NODE_ONLY + Object that group service instances. ###### Related Nodes - - FROM generic-vnf (is composed of license) - - FROM vce (is composed of license) + - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE) + - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE) + - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE required: - - group-uuid - - resource-uuid + - service-type properties: - group-uuid: + service-type: type: string - description: Unique ID for the license group the resource belongs to, should be uuid. - resource-uuid: + description: Value defined by orchestration to identify this service across ECOMP. + temp-ub-sub-account-id: type: string - description: Unique ID of a license resource. - resource-version: + description: This property will be deleted from A&AI in the near future. Only stop gap solution. + service-subscriptions: + description: | + Collection of objects that group service instances. + properties: + service-subscription: + type: array + items: + $ref: "#/patchDefinitions/service-subscription" + services: + description: | + Collection of service model definitions. Likely to be deprecated in favor of models from ASDC. + properties: + service: + type: array + items: + $ref: "#/patchDefinitions/service" + site-pair: + description: | + ###### Related Nodes + - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE) + - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE) + - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE + required: + - site-pair-id + properties: + site-pair-id: type: string - description: Concurrency value - relationship-list: + description: unique identifier of probe + source-ip: + type: string + description: Prefix address + destination-ip: + type: string + description: Prefix address + ip-version: + type: string + description: ip version, v4, v6 + destination-hostname: + type: string + description: Hostname of the destination equipment to which SLAs are measured against. + destination-equip-type: + type: string + description: The type of destinatination equipment. Could be Router, etc. + site-pair-set: + description: | + Set of instances for probes used to measure service level agreements + ###### Related Nodes + - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE) + - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE + required: + - site-pair-set-id + properties: + site-pair-set-id: + type: string + description: Unique id of site pair set. + site-pair-sets: + description: | + Collection of sets of instances for probes related to generic-vnf + properties: + site-pair-set: type: array - items: - $ref: "#/definitions/relationship" - licenses: + items: + $ref: "#/patchDefinitions/site-pair-set" + site-pairs: description: | - Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management + probe within a set properties: - license: + site-pair: type: array items: - $ref: "#/definitions/license" - entitlement: + $ref: "#/patchDefinitions/site-pair" + snapshot: description: | - Metadata for entitlement group. - ###### Default Delete Scope - THIS_NODE_ONLY + Openstack snapshot ###### Related Nodes - - FROM generic-vnf (is composed of entitlement) - - FROM vce (is composed of entitlement) + - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE) required: - - group-uuid - - resource-uuid + - snapshot-id properties: - group-uuid: + snapshot-id: type: string - description: Unique ID for the entitlement group the resource comes from, should be uuid. - resource-uuid: + description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. + snapshot-name: type: string - description: Unique ID of an entitlement resource. - resource-version: + description: Snapshot name + snapshot-architecture: type: string - description: Concurrency value - relationship-list: + description: Operating system architecture + snapshot-os-distro: + type: string + description: The common name of the operating system distribution in lowercase + snapshot-os-version: + type: string + description: The operating system version as specified by the distributor. + application: + type: string + description: The application that the image instantiates. + application-vendor: + type: string + description: The vendor of the application. + application-version: + type: string + description: The version of the application. + snapshot-selflink: + type: string + description: URL to endpoint where AAI can get more details + prev-snapshot-id: + type: string + description: This field contains the UUID of the previous snapshot (if any). + snapshots: + description: | + Collection of openstack snapshots + properties: + snapshot: type: array - items: - $ref: "#/definitions/relationship" - entitlements: + items: + $ref: "#/patchDefinitions/snapshot" + sriov-pf: description: | - Entitlements, keyed by group-uuid and resource-uuid, related to license management + SR-IOV Physical Function + ###### Related Nodes + - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE) + - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE) + required: + - pf-pci-id properties: - entitlement: + pf-pci-id: + type: string + description: Identifier for the sriov-pf + sriov-pfs: + description: | + Collection of SR-IOV Physical Functions. + properties: + sriov-pf: type: array items: - $ref: "#/definitions/entitlement" + $ref: "#/patchDefinitions/sriov-pf" + sriov-vf: + description: | + SR-IOV Virtual Function (not to be confused with virtual network function) + ###### Related Nodes + - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE) + required: + - pci-id + properties: + pci-id: + type: string + description: PCI ID used to identify the sriov-vf + vf-vlan-filter: + type: string + description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM. + vf-mac-filter: + type: string + description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM. + vf-vlan-strip: + type: boolean + description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM. + vf-vlan-anti-spoof-check: + type: boolean + description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs. + vf-mac-anti-spoof-check: + type: boolean + description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs. + vf-mirrors: + type: string + description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports. + vf-broadcast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM + vf-unknown-multicast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM + vf-unknown-unicast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM + vf-insert-stag: + type: boolean + description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM. + vf-link-status: + type: string + description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto. + sriov-vfs: + description: | + Collection of SR-IOV Virtual Functions. + properties: + sriov-vf: + type: array + items: + $ref: "#/patchDefinitions/sriov-vf" + start-node-filter: + properties: + property-name: + type: string + property-value: + type: string + subnet: + description: | + ###### Related Nodes + - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST + required: + - subnet-id + - dhcp-enabled + properties: + subnet-id: + type: string + description: Subnet ID, should be UUID. + subnet-name: + type: string + description: Name associated with the subnet. + neutron-subnet-id: + type: string + description: Neutron id of this subnet + gateway-address: + type: string + description: gateway ip address + network-start-address: + type: string + description: network start address + cidr-mask: + type: string + description: cidr mask + ip-version: + type: string + description: ip version + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO + dhcp-enabled: + type: boolean + dhcp-start: + type: string + description: the start address reserved for use by dhcp + dhcp-end: + type: string + description: the last address reserved for use by dhcp + subnets: + properties: + subnet: + type: array + items: + $ref: "#/patchDefinitions/subnet" + tagged-inventory-item-list: + properties: + inventory-item: + type: array + items: + $ref: "#/patchDefinitions/inventory-item" + tenant: + description: | + Openstack tenant + ###### Related Nodes + - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY) + - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY) + - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE) + - TENANT cannot be deleted if linked to VSERVER + required: + - tenant-id + - tenant-name + properties: + tenant-id: + type: string + description: Unique id relative to the cloud-region. + tenant-name: + type: string + description: Readable name of tenant + tenants: + description: | + Collection of openstack tenants. + properties: + tenant: + type: array + items: + $ref: "#/patchDefinitions/tenant" + tunnel-xconnect: + description: | + Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted + ###### Related Nodes + - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE) + required: + - id + - bandwidth-up-wan1 + - bandwidth-down-wan1 + - bandwidth-up-wan2 + - bandwidth-down-wan2 + properties: + id: + type: string + description: Allotted Resource id UUID assigned to this instance. + bandwidth-up-wan1: + type: string + description: The WAN uplink bandwidth for WAN1 + bandwidth-down-wan1: + type: string + description: The WAN downlink bandwidth for WAN1 + bandwidth-up-wan2: + type: string + description: The WAN uplink bandwidth for WAN2 + bandwidth-down-wan2: + type: string + description: The WAN downlink bandwidth for WAN2 + tunnel-xconnects: + description: | + This object is used to store the specific tunnel cross connect aspects of an allotted resource + properties: + tunnel-xconnect: + type: array + items: + $ref: "#/patchDefinitions/tunnel-xconnect" + update: + description: | + Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team. + required: + - update-node-type + properties: + update-node-type: + type: string + update-node-key: + type: array + items: + $ref: "#/patchDefinitions/update-node-key" + update-node-uri: + type: string + action: + type: array + items: + $ref: "#/patchDefinitions/action" + update-node-key: + properties: + key-name: + type: string + key-value: + type: string vce: description: | Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated. - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO availability-zone (Many2Many) - - TO complex (Many2Many) - - TO port-group (comprises vce, Many2Many) - - TO vserver (Many2Many) - - TO service-instance (Many2Many) - - TO entitlement (comprises vce, One2Many) - - TO license (comprises vce, One2Many) + - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY) + - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY) + - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP required: - vnf-id - vnf-name @@ -40824,47 +57189,239 @@ definitions: ipv4-oam-address: type: string description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE. - resource-version: + vces: + description: | + Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated. + properties: + vce: + type: array + items: + $ref: "#/patchDefinitions/vce" + vf-module: + description: | + a deployment unit of VNFCs + ###### Related Nodes + - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY) + - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY) + - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE) + - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY) + - VF-MODULE cannot be deleted if linked to VNFC + required: + - vf-module-id + - is-base-vf-module + properties: + vf-module-id: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - ipv4-loopback0-address: + description: Unique ID of vf-module. + vf-module-name: type: string - description: Loopback0 address - entitlement-resource-uuid: + description: Name of vf-module + heat-stack-id: type: string - description: OBSOLETE - see child relationships - port-groups: + description: Heat stack id corresponding to this instance. + orchestration-status: + type: string + description: orchestration status of this vf-module, mastered by MSO + is-base-vf-module: + type: boolean + vf-modules: + description: | + Collection of vf-modules, a deployment unit of VNFCs + properties: + vf-module: type: array - items: - $ref: "#/definitions/port-group" - licenses: + items: + $ref: "#/patchDefinitions/vf-module" + vig-server: + description: | + vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607 + ###### Related Nodes + - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE) + required: + - vig-address-type + properties: + vig-address-type: + type: string + description: indicates whether the VIG is for AVPN or INTERNET + ipaddress-v4-vig: + type: string + description: v4 IP of the vig server + ipaddress-v6-vig: + type: string + description: v6 IP of the vig server + vig-servers: + properties: + vig-server: type: array - items: - $ref: "#/definitions/license" - entitlements: + items: + $ref: "#/patchDefinitions/vig-server" + vip-ipv4-address-list: + description: | + IPv4 Address Range + ###### Related Nodes + - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY) + - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY) + required: + - vip-ipv4-address + properties: + vip-ipv4-address: + type: string + description: IP address + vip-ipv4-prefix-length: + type: integer + format: int64 + description: Prefix length, 32 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + vip-ipv6-address-list: + description: | + IPv6 Address Range + ###### Related Nodes + - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY) + - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY) + required: + - vip-ipv6-address + properties: + vip-ipv6-address: + type: string + description: IP address + vip-ipv6-prefix-length: + type: integer + format: int64 + description: Prefix length, 128 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + virtual-data-center: + description: | + Virtual organization of cloud infrastructure elements in a data center context + ###### Related Nodes + - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + required: + - vdc-id + - vdc-name + properties: + vdc-id: + type: string + description: Unique ID of the vdc + vdc-name: + type: string + description: Name of the virtual data center + virtual-data-centers: + description: | + Virtual organization of cloud infrastructure elements in a data center context + properties: + virtual-data-center: type: array - items: - $ref: "#/definitions/entitlement" - relationship-list: + items: + $ref: "#/patchDefinitions/virtual-data-center" + vlan: + description: | + Definition of vlan + ###### Related Nodes + - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE) + - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST + - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK + required: + - vlan-interface + - in-maint + properties: + vlan-interface: + type: string + description: String that identifies the interface + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + vlans: + properties: + vlan: type: array - items: - $ref: "#/definitions/relationship" - vces: + items: + $ref: "#/patchDefinitions/vlan" + vnf: description: | - Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated. + Abstract vnf class + required: + - vnf-id properties: - vce: + vnf-id: + type: string + description: Unique id of VNF. This is unique across the graph. + vnf-image: + description: | + Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge. + ###### Related Nodes + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE) + - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF + required: + - vnf-image-uuid + - application + - application-vendor + properties: + vnf-image-uuid: + type: string + description: Unique ID of this asset + application: + type: string + description: The application that the image instantiates. + application-vendor: + type: string + description: The vendor of the application. + application-version: + type: string + description: The version of the application. + selflink: + type: string + description: URL to endpoint where AAI can get more details + vnf-images: + description: | + Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge. + properties: + vnf-image: type: array items: - $ref: "#/definitions/vce" + $ref: "#/patchDefinitions/vnf-image" vnfc: description: | - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - FROM vserver - - FROM vf-module - - FROM generic-vnf + - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY) required: - vnfc-name - vnfc-function-code @@ -40897,13 +57454,6 @@ definitions: group-notation: type: string description: Group notation of VNFC - resource-version: - type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - relationship-list: - type: array - items: - $ref: "#/definitions/relationship" vnfcs: description: | virtual network components associated with a vserver from application controller. @@ -40911,190 +57461,710 @@ definitions: vnfc: type: array items: - $ref: "#/definitions/vnfc" - subnet: + $ref: "#/patchDefinitions/vnfc" + volume: description: | - ###### Default Delete Scope - ERROR_IF_ANY_IN_EDGES + Ephemeral Block storage volume. ###### Related Nodes - - FROM l3-interface-ipv4-address-list - - FROM l3-interface-ipv6-address-list - - FROM l3-network (is composed of subnet) + - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume) required: - - subnet-id - - dhcp-enabled + - volume-id + - volume-selflink properties: - subnet-id: - type: string - description: Subnet ID, should be UUID. - subnet-name: + volume-id: type: string - description: Name associated with the subnet. - neutron-subnet-id: + description: Unique ID of block storage volume relative to the vserver. + volume-selflink: type: string - description: Neutron id of this subnet - gateway-address: + description: URL to endpoint where AAI can get more details + volume-group: + description: | + Persistent block-level storage. + ###### Related Nodes + - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + required: + - volume-group-id + - volume-group-name + - vnf-type + properties: + volume-group-id: type: string - description: gateway ip address - network-start-address: + description: Unique ID of volume-group. + volume-group-name: type: string - description: network start address - cidr-mask: + description: Name of the volume group. + heat-stack-id: type: string - description: cidr mask - ip-version: + description: Heat stack id corresponding to this volume-group + vnf-type: type: string - description: ip version + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. orchestration-status: type: string - description: Orchestration status of this VNF, mastered by MSO - dhcp-enabled: + description: Orchestration status of this volume-group + model-customization-id: + type: string + description: captures the id of all the configuration used to customize the resource for the service. + vf-module-model-customization-id: + type: string + description: helps relate the volume group to the vf-module whose components will require the volume group + volume-groups: + description: | + Collection of persistent block-level storage. + properties: + volume-group: + type: array + items: + $ref: "#/patchDefinitions/volume-group" + volumes: + description: | + Collection of ephemeral Block storage volumes. + properties: + volume: + type: array + items: + $ref: "#/patchDefinitions/volume" + vpls-pe: + description: | + VPLS Provider Edge routers. + ###### Related Nodes + - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE + required: + - equipment-name + properties: + equipment-name: + type: string + prov-status: + type: string + description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. + ipv4-oam-address: + type: string + description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address). + equipment-role: + type: string + description: Client should send valid enumerated value, e.g., VPLS-PE. + vlan-id-outer: + type: integer + format: int64 + description: Temporary location for stag to get to VCE + vpls-pes: + description: | + Collection of VPLS Provider Edge routers + properties: + vpls-pe: + type: array + items: + $ref: "#/patchDefinitions/vpls-pe" + vpn-binding: + description: | + VPN binding + ###### Related Nodes + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE) + - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK + - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET + required: + - vpn-id + - vpn-name + properties: + vpn-id: + type: string + description: VPN ID, globally unique within A&AI + vpn-name: + type: string + description: VPN Name + vpn-platform: + type: string + description: the platform associated with the VPN example AVPN, Mobility + vpn-type: + type: string + description: Type of the vpn, should be taken from enumerated/valid values + route-distinguisher: + type: string + description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network. + vpn-bindings: + properties: + vpn-binding: + type: array + items: + $ref: "#/patchDefinitions/vpn-binding" + vserver: + description: | + Virtual Servers, aka virtual machine or VM. + ###### Related Nodes + - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE) + - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE) + - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE) + - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE) + - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE) + - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY) + - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY) + - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY) + - VSERVER is DELETED when these are DELETED L-INTERFACE + - VSERVER deletion means associated objects of these types are also DELETED:VOLUME + required: + - vserver-id + - vserver-name + - vserver-selflink + - in-maint + - is-closed-loop-disabled + properties: + vserver-id: + type: string + description: Unique identifier for this vserver relative to its tenant + vserver-name: + type: string + description: Name of vserver + vserver-name2: + type: string + description: Alternative name of vserver + prov-status: + type: string + description: Trigger for operational monitoring of this resource by Service Assurance systems. + vserver-selflink: + type: string + description: URL to endpoint where AAI can get more details + in-maint: type: boolean - dhcp-start: + is-closed-loop-disabled: + type: boolean + vservers: + description: | + Collection of virtual Servers, aka virtual machines or VMs. + properties: + vserver: + type: array + items: + $ref: "#/patchDefinitions/vserver" + zone: + description: | + A zone is a grouping of assets in a location homing to the same connections into the CBB + ###### Related Nodes + - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + required: + - zone-id + - zone-name + - design-type + - zone-context + properties: + zone-id: type: string - description: the start address reserved for use by dhcp - dhcp-end: + description: Code assigned by AIC to the zone + zone-name: type: string - description: the last address reserved for use by dhcp + description: English name associated with the zone + design-type: + type: string + description: Design of zone [Medium/Large?] + zone-context: + type: string + description: Context of zone [production/test] + status: + type: string + description: Status of a zone. + zones: + description: | + Collection of zones + properties: + zone: + type: array + items: + $ref: "#/patchDefinitions/zone" +getDefinitions: + aai-internal: + properties: + property-name: + type: string + property-value: + type: string + action: + properties: + action-type: + type: string + action-data: + type: array + items: + $ref: "#/getDefinitions/action-data" + action-data: + properties: + property-name: + type: string + property-value: + type: string + actions: + description: | + APIs that are more action related than REST (e.g., notify, update). + properties: + update: + type: object + $ref: "#/getDefinitions/update" + notify: + type: object + $ref: "#/getDefinitions/notify" + allotted-resource: + description: | + Represents a slice or partial piece of a resource that gets separately allotted + ###### Related Nodes + - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY) + - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY) + - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE) + - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY) + - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY) + - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT + required: + - id + properties: + id: + type: string + description: Allotted Resource id UUID assigned to this instance. + description: + type: string + description: The descriptive information assigned to this allotted resource instance + selflink: + type: string + description: Link back to more information in the controller + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. resource-version: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + description: Concurrency value + orchestration-status: + type: string + description: Orchestration status + operational-status: + type: string + description: Indicator for whether the resource is considered operational + type: + type: string + description: Generic description of the type of allotted resource. + role: + type: string + description: role in the network that this resource will be providing. + tunnel-xconnects: + type: array + items: + $ref: "#/getDefinitions/tunnel-xconnect" relationship-list: type: array items: - $ref: "#/definitions/relationship" - subnets: + $ref: "#/getDefinitions/relationship" + allotted-resources: + description: | + This object is used to store slices of services being offered properties: - subnet: + allotted-resource: type: array items: - $ref: "#/definitions/subnet" - ctag-assignment: + $ref: "#/getDefinitions/allotted-resource" + availability-zone: description: | - ###### Default Delete Scope - THIS_NODE_ONLY + Availability zone, a collection of compute hosts/pservers ###### Related Nodes - - FROM l3-network (is composed of ctag-assignment) - - FROM service-instance + - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE) + - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE required: - - vlan-id-inner + - availability-zone-name + - hypervisor-type properties: - vlan-id-inner: - type: integer - format: int64 - description: id. + availability-zone-name: + type: string + description: Name of the availability zone. Unique across a cloud region + hypervisor-type: + type: string + description: Type of hypervisor. Source of truth should define valid values. + operational-status: + type: string + description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: - $ref: "#/definitions/relationship" - ctag-assignments: + $ref: "#/getDefinitions/relationship" + availability-zones: + description: | + Collection of availability zones properties: - ctag-assignment: + availability-zone: type: array items: - $ref: "#/definitions/ctag-assignment" - segmentation-assignment: + $ref: "#/getDefinitions/availability-zone" + az-and-dvs-switches: + properties: + dvs-switches: + type: object + $ref: "#/getDefinitions/dvs-switches" + availability-zone: + type: object + $ref: "#/getDefinitions/availability-zone" + business: + description: | + Namespace for business related constructs + properties: + connectors: + type: array + items: + $ref: "#/getDefinitions/connector" + customers: + type: array + items: + $ref: "#/getDefinitions/customer" + class-of-service: description: | - Openstack segmentation assignment. - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - FROM l3-network (is composed of segmentation-assignment) + - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE) required: - - segmentation-id + - cos properties: - segmentation-id: + cos: type: string - description: Route Table Reference id, UUID assigned to this instance. + description: unique identifier of probe + probe-id: + type: string + description: identifier of probe + probe-type: + type: string + description: type of probe resource-version: type: string - description: Concurrency value + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: - $ref: "#/definitions/relationship" - segmentation-assignments: + $ref: "#/getDefinitions/relationship" + classes-of-service: description: | - Collection of openstack segmentation assignments + class-of-service of probe properties: - segmentation-assignment: + class-of-service: type: array items: - $ref: "#/definitions/segmentation-assignment" - l3-network: + $ref: "#/getDefinitions/class-of-service" + cloud-infrastructure: description: | - Generic network definition - ###### Default Delete Scope - CASCADE_TO_CHILDREN - ###### Related Nodes - - TO vpn-binding (Many2Many) - - TO subnet (comprises l3-network, Many2Many) - - TO service-instance (Many2Many) - - TO ctag-assignment (comprises l3-network, Many2Many) - - TO network-policy (Many2Many) - - TO segmentation-assignment (comprises l3-network, One2Many) - - TO route-table-reference (Many2Many) - - FROM cloud-region - - FROM complex - - FROM generic-vnf - - FROM l3-interface-ipv4-address-list - - FROM l3-interface-ipv6-address-list - - FROM tenant - - FROM vf-module - - FROM allotted-resource + Namespace for cloud infrastructure. + properties: + complexes: + type: array + items: + $ref: "#/getDefinitions/complex" + cloud-regions: + type: array + items: + $ref: "#/getDefinitions/cloud-region" + network-profiles: + type: array + items: + $ref: "#/getDefinitions/network-profile" + pservers: + type: array + items: + $ref: "#/getDefinitions/pserver" + virtual-data-centers: + type: array + items: + $ref: "#/getDefinitions/virtual-data-center" + cloud-region: + description: | + cloud-region designates an installation of a cloud cluster or region or instantiation + ###### Related Nodes + - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE) + - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP + - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE required: - - network-id - - network-name - - is-bound-to-vpn - - is-provider-network - - is-shared-network - - is-external-network + - cloud-owner + - cloud-region-id properties: - network-id: + cloud-owner: type: string - description: Network ID, should be uuid. Unique across A&AI. - network-name: + description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname + cloud-region-id: type: string - description: Name of the network, governed by some naming convention.. - network-type: + description: Identifier used by the vendor for the region. Second part of composite key + cloud-type: type: string - description: Type of the network - who defines these values? - network-role: + description: Type of the cloud (e.g., openstack) + owner-defined-type: type: string - description: Role the network plans - who defines these values? - network-technology: + description: Cloud-owner defined type indicator (e.g., dcp, lcp) + cloud-region-version: type: string - description: Network technology - who defines these values? - neutron-network-id: + description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE. + identity-url: type: string - description: Neutron network id of this Interface - is-bound-to-vpn: - type: boolean - service-id: + description: URL of the keystone identity service + cloud-zone: type: string - description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED - network-role-instance: - type: integer - format: int64 - description: network role instance + description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED. + complex-name: + type: string + description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + volume-groups: + type: array + items: + $ref: "#/getDefinitions/volume-group" + tenants: + type: array + items: + $ref: "#/getDefinitions/tenant" + flavors: + type: array + items: + $ref: "#/getDefinitions/flavor" + group-assignments: + type: array + items: + $ref: "#/getDefinitions/group-assignment" + snapshots: + type: array + items: + $ref: "#/getDefinitions/snapshot" + images: + type: array + items: + $ref: "#/getDefinitions/image" + dvs-switches: + type: array + items: + $ref: "#/getDefinitions/dvs-switch" + oam-networks: + type: array + items: + $ref: "#/getDefinitions/oam-network" + availability-zones: + type: array + items: + $ref: "#/getDefinitions/availability-zone" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + cloud-regions: + properties: + cloud-region: + type: array + items: + $ref: "#/getDefinitions/cloud-region" + complex: + description: | + Collection of physical locations that can house cloud-regions. + ###### Related Nodes + - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE) + - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY) + - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY) + - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE + - COMPLEX is DELETED when these are DELETED CTAG-POOL + required: + - physical-location-id + - physical-location-type + - street1 + - city + - postal-code + - country + - region + properties: + physical-location-id: + type: string + description: Unique identifier for physical location, e.g., CLLI + data-center-code: + type: string + description: Data center code which can be an alternate way to identify a complex + complex-name: + type: string + description: Gamma complex name for LCP instance. + identity-url: + type: string + description: URL of the keystone identity service + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + physical-location-type: + type: string + description: Type, e.g., central office, data center. + street1: + type: string + street2: + type: string + city: + type: string + state: + type: string + postal-code: + type: string + country: + type: string + region: + type: string + latitude: + type: string + longitude: + type: string + elevation: + type: string + lata: + type: string + ctag-pools: + type: array + items: + $ref: "#/getDefinitions/ctag-pool" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + complexes: + description: | + Collection of physical locations that can house cloud-regions. + properties: + complex: + type: array + items: + $ref: "#/getDefinitions/complex" + configuration: + description: | + Port Mirror Configuration. + ###### Related Nodes + - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE) + - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY) + - CONFIGURATION is DELETED when these are DELETED METADATUM + - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK + required: + - configuration-id + - configuration-type + - configuration-sub-type + - orchestration-status + - operational-status + - configuration-selflink + - model-customization-id + properties: + configuration-id: + type: string + description: UUID assigned to configuration. + management-option: + type: string + description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well. + configuration-name: + type: string + description: Name of the configuration. + configuration-type: + type: string + description: port-mirroring-configuration. + configuration-sub-type: + type: string + description: vprobe, pprobe. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. orchestration-status: type: string - description: Orchestration status of this VNF, mastered by MSO - heat-stack-id: + description: Orchestration status of the configuration. + operational-status: type: string - description: Heat stack id corresponding to this instance, managed by MSO - mso-catalog-key: + description: Indicator for whether the resource is considered operational. + configuration-selflink: type: string - description: Corresponds to the SDN-C catalog id used to configure this VCE - contrail-network-fqdn: + description: URL to endpoint where AAI can get more details from SDN-GC. + model-customization-id: type: string - description: Contrail FQDN for the network + description: id of the configuration used to customize the resource + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + metadata: + type: array + items: + $ref: "#/getDefinitions/metadatum" + configurations: + description: | + Collection of configurations + properties: + configuration: + type: array + items: + $ref: "#/getDefinitions/configuration" + connector: + description: | + Collection of resource instances used to connect a variety of disparate inventory widgets + ###### Related Nodes + - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY) + - CONNECTOR is DELETED when these are DELETED METADATUM + required: + - resource-instance-id + properties: + resource-instance-id: + type: string + description: Unique id of resource instance. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. model-invariant-id: type: string description: the ASDC model id for this resource or service model. @@ -41104,184 +58174,791 @@ definitions: persona-model-version: type: string description: the ASDC model version for this resource or service model. - model-customization-id: - type: string - description: captures the id of all the configuration used to customize the resource for the service. widget-model-id: type: string description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. widget-model-version: type: string description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. - physical-network-name: + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + metadata: + type: array + items: + $ref: "#/getDefinitions/metadatum" + connectors: + description: | + Collection of resource instances used to connect a variety of disparate inventory widgets + properties: + connector: + type: array + items: + $ref: "#/getDefinitions/connector" + constrained-element-set: + description: | + This is how we would capture constraints defining allowed sets of elements. + ###### Related Nodes + - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE) + - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE) + - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET + required: + - constrained-element-set-uuid + - constraint-type + - check-type + properties: + constrained-element-set-uuid: type: string - description: Name associated with the physical network. - is-provider-network: + constraint-type: + type: string + check-type: + type: string + resource-version: + type: string + element-choice-sets: + type: array + items: + $ref: "#/getDefinitions/element-choice-set" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + constrained-element-sets: + properties: + constrained-element-set: + type: array + items: + $ref: "#/getDefinitions/constrained-element-set" + ctag-assignment: + description: | + ###### Related Nodes + - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY) + required: + - vlan-id-inner + properties: + vlan-id-inner: + type: integer + format: int64 + description: id. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + ctag-assignments: + properties: + ctag-assignment: + type: array + items: + $ref: "#/getDefinitions/ctag-assignment" + ctag-pool: + description: | + A collection of C tags (vlan tags) grouped for a specific purpose. + ###### Related Nodes + - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE) + - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY) + required: + - target-pe + - availability-zone-name + - ctag-pool-purpose + properties: + target-pe: + type: string + description: The Target provider edge router + availability-zone-name: + type: string + description: Name of the availability zone + ctag-pool-purpose: + type: string + description: Describes what the intended purpose of this pool is. + ctag-values: + type: string + description: Comma separated list of ctags + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + ctag-pools: + properties: + ctag-pool: + type: array + items: + $ref: "#/getDefinitions/ctag-pool" + customer: + description: | + customer identifiers to provide linkage back to BSS information. + ###### Related Nodes + - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE) + - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION + required: + - global-customer-id + - subscriber-name + - subscriber-type + properties: + global-customer-id: + type: string + description: Global customer id used across ECOMP to uniquely identify customer. + subscriber-name: + type: string + description: Subscriber name, an alternate way to retrieve a customer. + subscriber-type: + type: string + description: Subscriber type, a way to provide VID with only the INFRA customers. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + service-subscriptions: + type: array + items: + $ref: "#/getDefinitions/service-subscription" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + customers: + description: | + Collection of customer identifiers to provide linkage back to BSS information. + properties: + customer: + type: array + items: + $ref: "#/getDefinitions/customer" + cvlan-tag-entry: + required: + - cvlan-tag + properties: + cvlan-tag: + type: integer + format: int64 + description: See mis-na-virtualization-platform.yang + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + cvlan-tags: + properties: + cvlan-tag-entry: + type: array + items: + $ref: "#/getDefinitions/cvlan-tag-entry" + dvs-switch: + description: | + Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI. + ###### Related Nodes + - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY) + required: + - switch-name + - vcenter-url + properties: + switch-name: + type: string + description: DVS switch name + vcenter-url: + type: string + description: URL used to reach the vcenter + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + dvs-switches: + description: | + Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs. + properties: + dvs-switch: + type: array + items: + $ref: "#/getDefinitions/dvs-switch" + edge-prop-names: + description: | + Internal map to define the properties of an edge and interpret the map EdgeRules + properties: + edgeLabel: + type: string + direction: + type: string + multiplicityRule: + type: string + isParent: type: boolean - is-shared-network: + usesResource: type: boolean - is-external-network: + hasDelTarget: type: boolean - selflink: + SVC-INFRA: + type: boolean + SVC-INFRA-REV: + type: boolean + edge-tag-query-request: + properties: + edge-tag: type: string - description: Path to the controller object. - operational-status: + result-detail: type: string - description: Indicator for whether the resource is considered operational. - subnets: + start-node-type: + type: string + start-node-filter: type: array - items: - $ref: "#/definitions/subnet" - ctag-assignments: + items: + $ref: "#/getDefinitions/start-node-filter" + include-node-filter: + type: array + items: + $ref: "#/getDefinitions/include-node-filter" + secondary-filter: + type: array + items: + $ref: "#/getDefinitions/secondary-filter" + edge-tag-query-result: + properties: + tagged-inventory-item-list: + type: array + items: + $ref: "#/getDefinitions/tagged-inventory-item-list" + element-choice-set: + description: | + This is how we would capture constraints defining allowed sets of elements. + ###### Related Nodes + - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE) + - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT + required: + - element-choice-set-uuid + - element-choice-set-name + properties: + element-choice-set-uuid: + type: string + element-choice-set-name: + type: string + cardinality: + type: string + resource-version: + type: string + model-elements: type: array items: - $ref: "#/definitions/ctag-assignment" - segmentation-assignments: + $ref: "#/getDefinitions/model-element" + relationship-list: type: array items: - $ref: "#/definitions/segmentation-assignment" + $ref: "#/getDefinitions/relationship" + element-choice-sets: + properties: + element-choice-set: + type: array + items: + $ref: "#/getDefinitions/element-choice-set" + entitlement: + description: | + Metadata for entitlement group. + ###### Related Nodes + - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + required: + - group-uuid + - resource-uuid + properties: + group-uuid: + type: string + description: Unique ID for the entitlement group the resource comes from, should be uuid. + resource-uuid: + type: string + description: Unique ID of an entitlement resource. + resource-version: + type: string + description: Concurrency value relationship-list: type: array items: - $ref: "#/definitions/relationship" - description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding - l3-networks: + $ref: "#/getDefinitions/relationship" + entitlements: + description: | + Entitlements, keyed by group-uuid and resource-uuid, related to license management properties: - l3-network: + entitlement: type: array items: - $ref: "#/definitions/l3-network" - network-policy: + $ref: "#/getDefinitions/entitlement" + esr-ems: description: | - ###### Default Delete Scope - THIS_NODE_ONLY + Persist EMS address information used by EMS driver. ###### Related Nodes - - FROM l3-network - - FROM allotted-resource + - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many) + - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO required: - - network-policy-id + - ems-id properties: - network-policy-id: + ems-id: type: string - description: UUID representing unique key to this instance - network-policy-fqdn: + description: Unique ID of EMS. + resource-version: type: string - description: Contrail FQDN for the policy - heat-stack-id: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + esr-system-info-list: + type: object + $ref: "#/getDefinitions/esr-system-info-list" + relationship-list: + type: object + $ref: "#/getDefinitions/relationship-list" + esr-ems-list: + properties: + esr-ems: + type: array + items: + $ref: "#/getDefinitions/esr-ems" + esr-system-info: + description: | + Persist common address information of external systems. + ###### Related Nodes + - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info) + - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info) + - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info) + - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info) + required: + - esr-system-info-id + - user-name + - password + - system-type + properties: + esr-system-info-id: type: string - description: ID for the openStack Heat instance + description: Unique ID of esr system info. + system-name: + type: string + description: name of external system. + type: + type: string + description: type of external systems. + vendor: + type: string + description: vendor of external systems. + version: + type: string + description: version of external systems. + service-url: + type: string + description: url used to access external systems. + user-name: + type: string + description: username used to access external systems. + password: + type: string + description: password used to access external systems. + system-type: + type: string + description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm. + protocol: + type: string + description: protocol of third party SDNC, for example netconf/snmp. + ssl-cacert: + type: string + description: ca file content if enabled ssl on auth-url. + ssl-insecure: + type: boolean + description: Whether to verify VIM's certificate. + ip-address: + type: string + description: service IP of ftp server. + port: + type: string + description: service port of ftp server. + cloud-domain: + type: string + description: domain info for authentication. + default-tenant: + type: string + description: default tenant of VIM. + passive: + type: boolean + description: ftp passive mode or not. + remote-path: + type: string + description: resource or performance data file path. + system-status: + type: string + description: the status of external system. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: - $ref: "#/definitions/relationship" - network-policies: + $ref: "#/getDefinitions/relationship" + esr-system-info-list: + description: | + Collection of persistent block-level external system auth info. properties: - network-policy: + esr-system-info: type: array items: - $ref: "#/definitions/network-policy" - vf-module: + $ref: "#/getDefinitions/esr-system-info" + esr-thirdparty-sdnc: description: | - a deployment unit of VNFCs - ###### Default Delete Scope - THIS_NODE_ONLY + Persist SDNC address information used by ONAP SDNC. ###### Related Nodes - - TO volume-group (One2One) - - TO l3-network (Many2Many) - - TO vnfc (One2Many) - - FROM vserver - - FROM generic-vnf (is composed of vf-module) + - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One) + - TO pnf( esr-thirdparty-sdnc has pnf, One2Many) + - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO required: - - vf-module-id - - is-base-vf-module + - thirdparty-sdnc-id properties: - vf-module-id: + thirdparty-sdnc-id: type: string - description: Unique ID of vf-module. - vf-module-name: + description: Unique ID of SDNC. + location: type: string - description: Name of vf-module - heat-stack-id: + description: used for DC type to indicate the location of SDNC, such as Core or Edge. + product-name: type: string - description: Heat stack id corresponding to this instance. - orchestration-status: + description: password used to access SDNC server. + resource-version: type: string - description: orchestration status of this vf-module, mastered by MSO - is-base-vf-module: - type: boolean + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + esr-system-info-list: + type: object + $ref: "#/getDefinitions/esr-system-info-list" + relationship-list: + type: object + $ref: "#/getDefinitions/relationship-list" + esr-thirdparty-sdnc-list: + properties: + esr-thirdparty-sdnc: + type: array + items: + $ref: "#/getDefinitions/esr-thirdparty-sdnc" + esr-vnfm: + description: | + Persist VNFM address information used by VF-C. + ###### Related Nodes + - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One) + - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO + required: + - vnfm-id + properties: + vnfm-id: + type: string + description: Unique ID of VNFM. + vim-id: + type: string + description: indecate the VIM to deploy VNF. + certificate-url: + type: string + description: certificate url of VNFM. resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - model-invariant-id: + esr-system-info-list: + type: object + $ref: "#/getDefinitions/esr-system-info-list" + relationship-list: + type: object + $ref: "#/getDefinitions/relationship-list" + esr-vnfm-list: + properties: + esr-vnfm: + type: array + items: + $ref: "#/getDefinitions/esr-vnfm" + evc: + description: | + evc object is an optional child object of the Configuration object. + ###### Related Nodes + - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE) + required: + - evc-id + properties: + evc-id: type: string - description: the ASDC model id for this resource or service model. - model-version-id: + description: Unique/key field for the evc object + forwarding-path-topology: type: string - description: the ASDC model version for this resource or service model. - persona-model-version: + description: Point-to-Point, Multi-Point + cir-value: type: string - description: the ASDC model version for this resource or service model. - model-customization-id: + description: Commited Information Rate + cir-units: type: string - description: captures the id of all the configuration used to customize the resource for the service. - widget-model-id: + description: CIR units + connection-diversity-group-id: type: string - description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. - widget-model-version: + description: Diversity Group ID + service-hours: type: string - description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. - contrail-service-instance-fqdn: + description: formerly Performance Group + esp-evc-circuit-id: type: string - description: the Contrail unique ID for a service-instance - module-index: + description: EVC Circuit ID of ESP EVC + esp-evc-cir-value: + type: string + description: Committed Information Rate (For ESP) + esp-evc-cir-units: + type: string + description: CIR units (For ESP) + esp-itu-code: + type: string + description: Identifies ESP + collector-pop-clli: + type: string + description: Collector POP CLLI (from the hostname of the access pnf) + inter-connect-type-ingress: + type: string + description: Interconnect type on ingress side of EVC. + tagmode-access-ingress: + type: string + description: tagode for collector side of EVC + tagmode-access-egress: + type: string + description: tagMode for network side of EVC + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + evcs: + properties: + evc: + type: array + items: + $ref: "#/getDefinitions/evc" + external-system: + description: | + Namespace for external system. + properties: + esr-ems-list: + type: object + $ref: "#/getDefinitions/esr-ems-list" + esr-vnfm-list: + type: object + $ref: "#/getDefinitions/esr-vnfm-list" + esr-thirdparty-sdnc-list: + type: object + $ref: "#/getDefinitions/esr-thirdparty-sdnc-list" + extra-properties: + description: | + Extra properties for inventory item for response list + properties: + extra-property: + type: array + items: + $ref: "#/getDefinitions/extra-property" + extra-property: + properties: + property-name: + type: string + property-value: + type: string + flavor: + description: | + Openstack flavor. + ###### Related Nodes + - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE) + - FLAVOR cannot be deleted if linked to VSERVER + required: + - flavor-id + - flavor-name + - flavor-selflink + properties: + flavor-id: + type: string + description: Flavor id, expected to be unique across cloud-region. + flavor-name: + type: string + description: Flavor name + flavor-vcpus: type: integer format: int32 - description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit - selflink: + description: Number of CPUs + flavor-ram: + type: integer + format: int32 + description: Amount of memory + flavor-disk: + type: integer + format: int32 + description: Disk space + flavor-ephemeral: + type: integer + format: int32 + description: Amount of ephemeral disk space + flavor-swap: type: string - description: Path to the controller object. + description: amount of swap space allocation + flavor-is-public: + type: boolean + description: whether flavor is available to all users or private to the tenant it was created in. + flavor-selflink: + type: string + description: URL to endpoint where AAI can get more details + flavor-disabled: + type: boolean + description: Boolean as to whether this flavor is no longer enabled + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: - $ref: "#/definitions/relationship" - vf-modules: + $ref: "#/getDefinitions/relationship" + flavors: description: | - Collection of vf-modules, a deployment unit of VNFCs + Collection of openstack flavors. properties: - vf-module: + flavor: type: array items: - $ref: "#/definitions/vf-module" + $ref: "#/getDefinitions/flavor" + forwarder: + description: | + Entity describing a sequenced segment of forwarding path + ###### Related Nodes + - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE) + - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE) + - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE) + - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE) + - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE) + - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION + required: + - sequence + properties: + sequence: + type: integer + format: int32 + description: Unique ID of this segmentation + forwarder-role: + type: string + description: ingress, intermediate, egress + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + forwarder-evc: + description: | + forwarder object is an optional child object of the Configuration object. + ###### Related Nodes + - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE) + required: + - forwarder-evc-id + properties: + forwarder-evc-id: + type: string + description: Key for forwarder-evc object + circuit-id: + type: string + description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC + ivlan: + type: string + description: Internal VLAN. + svlan: + type: string + description: SVLAN value for ingress of egress forwarder. + cvlan: + type: string + description: CVLAN value for ingress of egress forwarder. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + forwarder-evcs: + properties: + forwarder-evc: + type: array + items: + $ref: "#/getDefinitions/forwarder-evc" + forwarders: + properties: + forwarder: + type: array + items: + $ref: "#/getDefinitions/forwarder" + forwarding-path: + description: | + Entity that describes the sequenced forwarding path between interfaces of services or resources + ###### Related Nodes + - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE) + - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE) + - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE) + - FORWARDING-PATH is DELETED when these are DELETED FORWARDER + - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION + required: + - forwarding-path-id + - forwarding-path-name + properties: + forwarding-path-id: + type: string + description: Unique ID of this FP + forwarding-path-name: + type: string + description: Name of the FP + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + selflink: + type: string + description: the self link for this FP + forwarders: + type: array + items: + $ref: "#/getDefinitions/forwarder" + forwarding-paths: + properties: + forwarding-path: + type: array + items: + $ref: "#/getDefinitions/forwarding-path" generic-vnf: description: | General purpose VNF - ###### Default Delete Scope - CASCADE_TO_CHILDREN - ###### Related Nodes - - TO license-key-resource (Many2Many) - - TO l-interface (comprises generic-vnf, Many2Many) - - TO availability-zone (Many2Many) - - TO lag-interface (comprises generic-vnf, Many2Many) - - TO l3-network (Many2Many) - - TO pserver (Many2Many) - - TO vnf-image (Many2One) - - TO vserver (One2Many) - - TO service-instance (Many2Many) - - TO site-pair-set (Many2Many) - - TO network-profile (Many2Many) - - TO ipsec-configuration (Many2One) - - TO vf-module (comprises generic-vnf, One2Many) - - TO volume-group (One2Many) - - TO vnfc (One2Many) - - TO instance-group (Many2Many) - - TO entitlement (comprises generic-vnf, One2Many) - - TO license (comprises generic-vnf, One2Many) - - FROM virtual-data-center - - FROM logical-link - - FROM allotted-resource + ###### Related Nodes + - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE) + - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY) + - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY) + - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE) + - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY) + - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY) + - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY) + - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY) + - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE required: - vnf-id - vnf-name @@ -41431,27 +59108,27 @@ definitions: relationship-list: type: array items: - $ref: "#/definitions/relationship" + $ref: "#/getDefinitions/relationship" l-interfaces: type: array items: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" lag-interfaces: type: array items: - $ref: "#/definitions/lag-interface" + $ref: "#/getDefinitions/lag-interface" vf-modules: type: array items: - $ref: "#/definitions/vf-module" + $ref: "#/getDefinitions/vf-module" licenses: type: array items: - $ref: "#/definitions/license" + $ref: "#/getDefinitions/license" entitlements: type: array items: - $ref: "#/definitions/entitlement" + $ref: "#/getDefinitions/entitlement" generic-vnfs: description: | Collection of VNFs @@ -41459,15 +59136,732 @@ definitions: generic-vnf: type: array items: - $ref: "#/definitions/generic-vnf" + $ref: "#/getDefinitions/generic-vnf" + group-assignment: + description: | + Openstack group-assignment used to store exclusivity groups (EG). + ###### Related Nodes + - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY) + required: + - group-id + - group-type + - group-name + properties: + group-id: + type: string + description: Group id, expected to be unique across cloud-region. + group-type: + type: string + description: Group type - the type of group this instance refers to + group-name: + type: string + description: Group name - name assigned to the group + group-description: + type: string + description: Group description - description of the group + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + group-assignments: + description: | + Collection of openstack group assignments + properties: + group-assignment: + type: array + items: + $ref: "#/getDefinitions/group-assignment" + host-route: + description: | + ###### Related Nodes + - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE) + required: + - host-route-id + - route-prefix + - next-hop + properties: + host-route-id: + type: string + description: host-route id + route-prefix: + type: string + description: subnet prefix + next-hop: + type: string + description: Could be ip-address, hostname, or service-instance + next-hop-type: + type: string + description: Should be ip-address, hostname, or service-instance to match next-hop + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + host-routes: + properties: + host-route: + type: array + items: + $ref: "#/getDefinitions/host-route" + image: + description: | + Openstack image. + ###### Related Nodes + - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE) + - IMAGE cannot be deleted if linked to VSERVER + - IMAGE is DELETED when these are DELETED METADATUM + required: + - image-id + - image-name + - image-os-distro + - image-os-version + - image-selflink + properties: + image-id: + type: string + description: Image id, expected to be unique across cloud region + image-name: + type: string + description: Image name + image-architecture: + type: string + description: Operating system architecture. + image-os-distro: + type: string + description: The common name of the operating system distribution in lowercase + image-os-version: + type: string + description: The operating system version as specified by the distributor. + application: + type: string + description: The application that the image instantiates. + application-vendor: + type: string + description: The vendor of the application. + application-version: + type: string + description: The version of the application. + image-selflink: + type: string + description: URL to endpoint where AAI can get more details + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + metadata: + type: array + items: + $ref: "#/getDefinitions/metadatum" + images: + description: | + Collectio of Openstack images. + properties: + image: + type: array + items: + $ref: "#/getDefinitions/image" + include-node-filter: + properties: + include-node-type: + type: string + instance-filter: + description: | + InstanceFilter for performing a named-query or model query + instance-filters: + description: | + InstanceFilters for performing a named-query or model query + properties: + instance-filter: + type: array + items: + $ref: "#/getDefinitions/instance-filter" + instance-group: + description: | + General mechanism for grouping instances + ###### Related Nodes + - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + required: + - id + - description + - type + properties: + id: + type: string + description: Instance Group ID, UUID assigned to this instance. + description: + type: string + description: Descriptive text to help identify the usage of this instance-group + type: + type: string + description: Only valid value today is lower case ha for high availability + sub-type: + type: string + description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby] + resource-version: + type: string + description: Concurrency value + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + instance-groups: + description: | + Collection of openstack route table references + properties: + instance-group: + type: array + items: + $ref: "#/getDefinitions/instance-group" + inventory: + properties: + search: + type: object + $ref: "#/getDefinitions/search" + actions: + type: object + $ref: "#/getDefinitions/actions" + cloud-infrastructure: + type: object + $ref: "#/getDefinitions/cloud-infrastructure" + business: + type: object + $ref: "#/getDefinitions/business" + service-design-and-creation: + type: object + $ref: "#/getDefinitions/service-design-and-creation" + network: + type: object + $ref: "#/getDefinitions/network" + aai-internal: + type: object + $ref: "#/getDefinitions/aai-internal" + nodes: + type: array + items: + $ref: "#/getDefinitions/aai-internal" + inventory-item: + properties: + inventory-item-type: + type: string + inventory-item-link: + type: string + inventory-item-data: + type: array + items: + $ref: "#/getDefinitions/inventory-item-data" + tagged-inventory-item-list: + type: array + items: + $ref: "#/getDefinitions/tagged-inventory-item-list" + inventory-item-data: + properties: + property-name: + type: string + property-value: + type: string + inventory-response-item: + description: | + Inventory item for response list + properties: + model-name: + type: string + extra-properties: + type: object + $ref: "#/getDefinitions/extra-properties" + inventory-response-items: + type: object + $ref: "#/getDefinitions/inventory-response-items" + inventory-response-items: + description: | + Container for inventory items in response list + properties: + inventory-response-item: + type: array + items: + $ref: "#/getDefinitions/inventory-response-item" + ipsec-configuration: + description: | + IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C + ###### Related Nodes + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE) + - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE) + - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER + required: + - ipsec-configuration-id + properties: + ipsec-configuration-id: + type: string + description: UUID of this configuration + requested-vig-address-type: + type: string + description: Indicate the type of VIG server like AVPN, INTERNET, BOTH + requested-encryption-strength: + type: string + description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc + requested-dmz-type: + type: string + description: can offer a shared DMZ or a DMZ specific to a customer + shared-dmz-network-address: + type: string + description: Network address of shared DMZ + requested-customer-name: + type: string + description: If the DMZ is a custom DMZ, this field will indicate the customer information + ike-version: + type: string + description: can be 1 or 2 + ikev1-authentication: + type: string + description: Contains values like md5, sha1, sha256, sha384 + ikev1-encryption: + type: string + description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc + ikev1-dh-group: + type: string + description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14 + ikev1-am-group-id: + type: string + description: Group name defined in VIG for clients using aggressive mode + ikev1-am-password: + type: string + description: pre-shared key for the above group name + ikev1-sa-lifetime: + type: string + description: Lifetime for IKEv1 SA + ipsec-authentication: + type: string + description: md5, sha1, sha256, sha384 + ipsec-encryption: + type: string + description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc + ipsec-sa-lifetime: + type: string + description: Life time for IPSec SA + ipsec-pfs: + type: string + description: enable PFS or not + xauth-userid: + type: string + description: user ID for xAuth, sm-user, ,nmteHostName + xauth-user-password: + type: string + description: Encrypted using the Juniper $9$ algorithm + dpd-interval: + type: string + description: The time between DPD probe + dpd-frequency: + type: string + description: Maximum number of DPD before claiming the tunnel is down + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + vig-servers: + type: array + items: + $ref: "#/getDefinitions/vig-server" + ipsec-configurations: + properties: + ipsec-configuration: + type: array + items: + $ref: "#/getDefinitions/ipsec-configuration" + key-data: + properties: + key-name: + type: string + key-value: + type: string + l-interface: + description: | + Logical interfaces, e.g., a vnic. + ###### Related Nodes + - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE) + - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY) + - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE) + - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE) + - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE) + - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN + - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK + required: + - interface-name + - is-port-mirrored + - in-maint + properties: + interface-name: + type: string + description: Name given to the interface + interface-role: + type: string + description: E.g., CUSTOMER, UPLINK, etc. + v6-wan-link-ip: + type: string + description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B. + selflink: + type: string + description: URL to endpoint where AAI can get more details + interface-id: + type: string + description: ID of interface + macaddr: + type: string + description: MAC address for the interface + network-name: + type: string + description: Name of the network + management-option: + type: string + description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER + interface-description: + type: string + description: Human friendly text regarding this interface. + is-port-mirrored: + type: boolean + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + in-maint: + type: boolean + vlans: + type: array + items: + $ref: "#/getDefinitions/vlan" + sriov-vfs: + type: array + items: + $ref: "#/getDefinitions/sriov-vf" + l-interfaces: + type: array + items: + $ref: "#/getDefinitions/l-interface" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + l3-interface-ipv4-address-list: + type: array + items: + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" + l3-interface-ipv6-address-list: + type: array + items: + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" + l-interfaces: + description: | + Collection of logical interfaces. + properties: + l-interface: + type: array + items: + $ref: "#/getDefinitions/l-interface" + l3-interface-ipv4-address-list: + description: | + IPv4 Address Range + ###### Related Nodes + - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + required: + - l3-interface-ipv4-address + properties: + l3-interface-ipv4-address: + type: string + description: IP address + l3-interface-ipv4-prefix-length: + type: integer + format: int64 + description: Prefix length, 32 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: + type: string + description: Neutron network id of the interface that address belongs to + neutron-subnet-id: + type: string + description: Neutron id of subnet that address belongs to + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + l3-interface-ipv6-address-list: + description: | + IPv6 Address Range + ###### Related Nodes + - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY) + - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE) + - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + required: + - l3-interface-ipv6-address + properties: + l3-interface-ipv6-address: + type: string + description: IP address + l3-interface-ipv6-prefix-length: + type: integer + format: int64 + description: Prefix length, 128 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: + type: string + description: Neutron network id of the interface that address belongs to + neutron-subnet-id: + type: string + description: Neutron id of subnet that address belongs to + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + l3-network: + description: | + Generic network definition + ###### Related Nodes + - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY) + - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY) + - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY) + - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY) + - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY) + - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET + required: + - network-id + - network-name + - is-bound-to-vpn + - is-provider-network + - is-shared-network + - is-external-network + properties: + network-id: + type: string + description: Network ID, should be uuid. Unique across A&AI. + network-name: + type: string + description: Name of the network, governed by some naming convention.. + network-type: + type: string + description: Type of the network - who defines these values? + network-role: + type: string + description: Role the network plans - who defines these values? + network-technology: + type: string + description: Network technology - who defines these values? + neutron-network-id: + type: string + description: Neutron network id of this Interface + is-bound-to-vpn: + type: boolean + service-id: + type: string + description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED + network-role-instance: + type: integer + format: int64 + description: network role instance + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + contrail-network-fqdn: + type: string + description: Contrail FQDN for the network + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + model-customization-id: + type: string + description: captures the id of all the configuration used to customize the resource for the service. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + physical-network-name: + type: string + description: Name associated with the physical network. + is-provider-network: + type: boolean + is-shared-network: + type: boolean + is-external-network: + type: boolean + selflink: + type: string + description: Path to the controller object. + operational-status: + type: string + description: Indicator for whether the resource is considered operational. + subnets: + type: array + items: + $ref: "#/getDefinitions/subnet" + ctag-assignments: + type: array + items: + $ref: "#/getDefinitions/ctag-assignment" + segmentation-assignments: + type: array + items: + $ref: "#/getDefinitions/segmentation-assignment" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding + l3-networks: + properties: + l3-network: + type: array + items: + $ref: "#/getDefinitions/l3-network" + lag-interface: + description: | + Link aggregate interface + ###### Related Nodes + - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY) + - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY) + - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE) + - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE + - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK + required: + - interface-name + - in-maint + properties: + interface-name: + type: string + description: Name that identifies the link aggregate interface + interface-description: + type: string + description: Human friendly text regarding this interface. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + interface-id: + type: string + description: ID of interface + interface-role: + type: string + description: Role assigned to this Interface, should use values as defined in ECOMP Yang models. + prov-status: + type: string + description: Trigger for operational monitoring of this resource by Service Assurance systems. + in-maint: + type: boolean + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + l-interfaces: + type: array + items: + $ref: "#/getDefinitions/l-interface" + lag-interfaces: + description: | + Collection of link aggregate interfaces. + properties: + lag-interface: + type: array + items: + $ref: "#/getDefinitions/lag-interface" lag-link: description: | LAG links can connect lag-interfaces - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - FROM lag-interface - - FROM logical-link + - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY) required: - link-name properties: @@ -41480,7 +59874,7 @@ definitions: relationship-list: type: array items: - $ref: "#/definitions/relationship" + $ref: "#/getDefinitions/relationship" lag-links: description: | Collection of link aggregation connections @@ -41488,14 +59882,624 @@ definitions: lag-link: type: array items: - $ref: "#/definitions/lag-link" + $ref: "#/getDefinitions/lag-link" + license: + description: | + Metadata for license group. + ###### Related Nodes + - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + required: + - group-uuid + - resource-uuid + properties: + group-uuid: + type: string + description: Unique ID for the license group the resource belongs to, should be uuid. + resource-uuid: + type: string + description: Unique ID of a license resource. + resource-version: + type: string + description: Concurrency value + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + licenses: + description: | + Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management + properties: + license: + type: array + items: + $ref: "#/getDefinitions/license" + line-of-business: + description: | + describes a line-of-business + ###### Related Nodes + - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY) + required: + - line-of-business-name + properties: + line-of-business-name: + type: string + description: Name of the line-of-business (product) + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + lines-of-business: + description: | + Collection of lines-of-business + properties: + line-of-business: + type: array + items: + $ref: "#/getDefinitions/line-of-business" + logical-link: + description: | + Logical links generally connect l-interfaces but are used to express logical connectivity between two points + ###### Related Nodes + - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY) + - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY) + - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY) + - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY) + - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY) + - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY) + - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + required: + - link-name + - link-type + properties: + link-name: + type: string + description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ + link-type: + type: string + description: Type of logical link, e.g., evc + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + ip-version: + type: string + description: v4, v6, or ds for dual stack + routing-protocol: + type: string + description: For example, static or BGP + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + operational-status: + type: string + description: Indication of operational status of the logical link. + prov-status: + type: string + description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. + link-role: + type: string + description: Indication of the network use of the logical link. + link-name2: + type: string + description: Alias or alternate name (CLCI or D1 name). + link-id: + type: string + description: UUID of the logical-link, SDNC generates this. + circuit-id: + type: string + description: Circuit id + purpose: + type: string + description: Reason for this entity, role it is playing + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + logical-links: + description: | + Collection of logical connections + properties: + logical-link: + type: array + items: + $ref: "#/getDefinitions/logical-link" + metadata: + description: | + Collection of metadatum (key/value pairs) + properties: + metadatum: + type: array + items: + $ref: "#/getDefinitions/metadatum" + metadatum: + description: | + Key/value pairs + ###### Related Nodes + - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE) + - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE) + - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + required: + - metaname + - metaval + properties: + metaname: + type: string + metaval: + type: string + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model: + description: | + Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version + ###### Related Nodes + - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY) + - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE) + - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT + - MODEL is DELETED when these are DELETED MODEL-VER + required: + - model-invariant-id + - model-type + properties: + model-invariant-id: + type: string + description: Unique identifier corresponding to the main definition of a model in ASDC + model-type: + type: string + description: Type of the model, e.g., service, resource, widget, etc. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-vers: + type: array + items: + $ref: "#/getDefinitions/model-ver" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + model-and-named-query-search: + description: | + ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query + properties: + query-parameters: + type: object + $ref: "#/getDefinitions/query-parameters" + instance-filters: + type: object + $ref: "#/getDefinitions/instance-filters" + secondary-filts: + type: object + $ref: "#/getDefinitions/secondary-filts" + top-node-type: + type: string + secondary-filter-cut-point: + type: string + model-constraint: + description: | + This is how we would capture constraints defining allowed sets of elements. + ###### Related Nodes + - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE) + - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET + required: + - model-constraint-uuid + - constrained-element-set-uuid-to-replace + properties: + model-constraint-uuid: + type: string + constrained-element-set-uuid-to-replace: + type: string + constrained-element-sets: + type: array + items: + $ref: "#/getDefinitions/constrained-element-set" + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-constraints: + properties: + model-constraint: + type: array + items: + $ref: "#/getDefinitions/model-constraint" + model-element: + description: | + Defines how other models combine to make up a higher-level model. + ###### Related Nodes + - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE) + - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE) + - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE) + - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT + required: + - model-element-uuid + - new-data-del-flag + - cardinality + properties: + model-element-uuid: + type: string + new-data-del-flag: + type: string + description: Indicates whether this element was created as part of instantiation from this model + cardinality: + type: string + description: How many of this type of element are required/allowed + linkage-points: + type: string + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-elements: + type: array + items: + $ref: "#/getDefinitions/model-element" + description: Defines how other models combine to make up a higher-level model + model-constraints: + type: array + items: + $ref: "#/getDefinitions/model-constraint" + description: Describes new constraints on this model element that are not part of that model's definition + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + model-elements: + properties: + model-element: + type: array + items: + $ref: "#/getDefinitions/model-element" + model-ver: + description: | + Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models + ###### Related Nodes + - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE) + - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE) + - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT + - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM + required: + - model-version-id + - model-name + - model-version + properties: + model-version-id: + type: string + description: Unique identifier corresponding to one version of a model in ASDC + model-name: + type: string + description: Name of the model, which can change from version to version. + model-version: + type: string + description: Version + model-description: + type: string + description: Description + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-elements: + type: array + items: + $ref: "#/getDefinitions/model-element" + metadata: + type: array + items: + $ref: "#/getDefinitions/metadatum" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + model-vers: + properties: + model-ver: + type: array + items: + $ref: "#/getDefinitions/model-ver" + models: + description: | + Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models + properties: + model: + type: array + items: + $ref: "#/getDefinitions/model" + multicast-configuration: + description: | + ###### Related Nodes + - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY) + required: + - multicast-configuration-id + - multicast-protocol + - rp-type + properties: + multicast-configuration-id: + type: string + description: Unique id of multicast configuration. + multicast-protocol: + type: string + description: protocol of multicast configuration + rp-type: + type: string + description: rp type of multicast configuration + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + multicast-configurations: + description: | + multicast configuration of generic-vnf ip-address + properties: + multicast-configuration: + type: array + items: + $ref: "#/getDefinitions/multicast-configuration" + named-queries: + properties: + named-query: + type: array + items: + $ref: "#/getDefinitions/named-query" + named-query: + description: | + TBD + ###### Related Nodes + - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT + required: + - named-query-uuid + - named-query-name + - named-query-version + properties: + named-query-uuid: + type: string + named-query-name: + type: string + named-query-version: + type: string + required-input-param: + type: string + description: + type: string + resource-version: + type: string + named-query-elements: + type: array + items: + $ref: "#/getDefinitions/named-query-element" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + named-query-element: + description: | + TBD + ###### Related Nodes + - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE) + - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE) + - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP + required: + - named-query-element-uuid + properties: + named-query-element-uuid: + type: string + property-collect-list: + type: string + resource-version: + type: string + property-limit-desc: + type: string + do-not-output: + type: string + named-query-elements: + type: array + items: + $ref: "#/getDefinitions/named-query-element" + related-lookups: + type: array + items: + $ref: "#/getDefinitions/related-lookup" + property-constraints: + type: array + items: + $ref: "#/getDefinitions/property-constraint" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + named-query-elements: + properties: + named-query-element: + type: array + items: + $ref: "#/getDefinitions/named-query-element" + network: + description: | + Namespace for network inventory resources. + properties: + logical-links: + type: array + items: + $ref: "#/getDefinitions/logical-link" + site-pair-sets: + type: array + items: + $ref: "#/getDefinitions/site-pair-set" + vpn-bindings: + type: array + items: + $ref: "#/getDefinitions/vpn-binding" + vpls-pes: + type: array + items: + $ref: "#/getDefinitions/vpls-pe" + multicast-configurations: + type: array + items: + $ref: "#/getDefinitions/multicast-configuration" + vces: + type: array + items: + $ref: "#/getDefinitions/vce" + vnfcs: + type: array + items: + $ref: "#/getDefinitions/vnfc" + l3-networks: + type: array + items: + $ref: "#/getDefinitions/l3-network" + network-policies: + type: array + items: + $ref: "#/getDefinitions/network-policy" + generic-vnfs: + type: array + items: + $ref: "#/getDefinitions/generic-vnf" + lag-links: + type: array + items: + $ref: "#/getDefinitions/lag-link" + newvces: + type: array + items: + $ref: "#/getDefinitions/newvce" + pnfs: + type: array + items: + $ref: "#/getDefinitions/pnf" + physical-links: + type: array + items: + $ref: "#/getDefinitions/physical-link" + ipsec-configurations: + type: array + items: + $ref: "#/getDefinitions/ipsec-configuration" + route-table-references: + type: array + items: + $ref: "#/getDefinitions/route-table-reference" + instance-groups: + type: array + items: + $ref: "#/getDefinitions/instance-group" + zones: + type: array + items: + $ref: "#/getDefinitions/zone" + network-policies: + properties: + network-policy: + type: array + items: + $ref: "#/getDefinitions/network-policy" + network-policy: + description: | + ###### Related Nodes + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE) + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY) + required: + - network-policy-id + properties: + network-policy-id: + type: string + description: UUID representing unique key to this instance + network-policy-fqdn: + type: string + description: Contrail FQDN for the policy + heat-stack-id: + type: string + description: ID for the openStack Heat instance + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + network-profile: + description: | + Network profile populated by SDN-GP for SNMP + ###### Related Nodes + - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + required: + - nm-profile-name + properties: + nm-profile-name: + type: string + description: Unique name of network profile. + community-string: + type: string + description: Encrypted SNMP community string + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + network-profiles: + description: | + Collection of network profiles + properties: + network-profile: + type: array + items: + $ref: "#/getDefinitions/network-profile" newvce: description: | This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce. - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO l-interface (comprises newvce, Many2Many) + - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE) + - NEWVCE is DELETED when these are DELETED L-INTERFACE required: - vnf-id2 - vnf-name @@ -41546,11 +60550,11 @@ definitions: relationship-list: type: array items: - $ref: "#/definitions/relationship" + $ref: "#/getDefinitions/relationship" l-interfaces: type: array items: - $ref: "#/definitions/l-interface" + $ref: "#/getDefinitions/l-interface" newvces: description: | This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce. @@ -41558,20 +60562,364 @@ definitions: newvce: type: array items: - $ref: "#/definitions/newvce" + $ref: "#/getDefinitions/newvce" + notification-event: + properties: + cambria.partition: + type: string + notification-event-header: + type: object + $ref: "#/getDefinitions/notification-event-header" + notification-event-header: + properties: + id: + type: string + timestamp: + type: string + source-name: + type: string + domain: + type: string + sequence-number: + type: string + severity: + type: string + event-type: + type: string + version: + type: string + action: + type: string + entity-type: + type: string + top-entity-type: + type: string + entity-link: + type: string + status: + type: string + notify: + required: + - event-id + properties: + event-id: + type: string + node-type: + type: string + event-trigger: + type: string + key-data: + type: array + items: + $ref: "#/getDefinitions/key-data" + selflink: + type: string + oam-network: + description: | + OAM network, to be deprecated shortly. Do not use for new purposes. + ###### Related Nodes + - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY) + - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + required: + - network-uuid + - network-name + - cvlan-tag + properties: + network-uuid: + type: string + description: UUID of the network. Unique across a cloud-region + network-name: + type: string + description: Name of the network. + cvlan-tag: + type: integer + format: int64 + description: cvlan-id + ipv4-oam-gateway-address: + type: string + description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network + ipv4-oam-gateway-address-prefix-length: + type: integer + format: int32 + description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + oam-networks: + description: | + Collection of OAM networks, to be deprecated shortly. Do not use for new purposes. + properties: + oam-network: + type: array + items: + $ref: "#/getDefinitions/oam-network" + operational-environment: + description: | + It is a logical partition of the cloud which allows to have multiple environments in the production AIC. + ###### Related Nodes + - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE) + - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE) + required: + - operational-environment-id + - operational-environment-name + - operational-environment-type + - operational-environment-status + - tenant-context + - workload-context + properties: + operational-environment-id: + type: string + description: UUID of an operational environment + operational-environment-name: + type: string + description: Operational Environment name + operational-environment-type: + type: string + description: Operational Environment Type. + operational-environment-status: + type: string + description: Status + tenant-context: + type: string + description: Tenant Context. + workload-context: + type: string + description: Workload Context. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + operational-environments: + description: | + a logical partition of the cloud which allows to have multiple environments in the production AIC. + properties: + operational-environment: + type: array + items: + $ref: "#/getDefinitions/operational-environment" + overloaded-model: + description: | + Allows for legacy POST of old-style and new-style models + required: + - model-invariant-id + - model-name-version-id + - model-type + - model-name + - model-id + - model-version + properties: + model-invariant-id: + type: string + description: Unique identifier corresponding to the main definition of a model in ASDC + model-name-version-id: + type: string + description: Unique identifier corresponding to one version of a model in ASDC + model-type: + type: string + description: Type of the model, e.g., service, resource, widget, etc. + model-name: + type: string + description: Name of the model, which can change from version to version. + model-id: + type: string + description: Invariant unique ID which does not change from version to version + model-version: + type: string + description: Version + model-description: + type: string + description: Description + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-vers: + type: object + $ref: "#/getDefinitions/model-vers" + relationship-list: + type: object + $ref: "#/getDefinitions/relationship-list" + owning-entities: + description: | + Collection of owning-entities + properties: + owning-entity: + type: array + items: + $ref: "#/getDefinitions/owning-entity" + owning-entity: + description: | + describes an owning-entity + ###### Related Nodes + - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE) + required: + - owning-entity-id + - owning-entity-name + properties: + owning-entity-id: + type: string + description: UUID of an owning entity + owning-entity-name: + type: string + description: Owning entity name + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + p-interface: + description: | + Physical interface (e.g., nic) + ###### Related Nodes + - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE) + - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE) + - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY) + - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE) + - P-INTERFACE is DELETED when these are DELETED L-INTERFACE + - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK + required: + - interface-name + - in-maint + properties: + interface-name: + type: string + description: Name that identifies the physical interface + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + port-description: + type: string + description: Nature of the services and connectivity on this port. + equipment-identifier: + type: string + description: CLEI or other specification for p-interface hardware. + interface-role: + type: string + description: Role specification for p-interface hardware. + interface-type: + type: string + description: Indicates the physical properties of the interface. + prov-status: + type: string + description: Trigger for operational monitoring of this resource by Service Assurance systems. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + in-maint: + type: boolean + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + l-interfaces: + type: array + items: + $ref: "#/getDefinitions/l-interface" + p-interfaces: + description: | + Collection of physical interfaces. + properties: + p-interface: + type: array + items: + $ref: "#/getDefinitions/p-interface" + physical-link: + description: | + Collection of physical connections, typically between p-interfaces + ###### Related Nodes + - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE) + required: + - link-name + properties: + link-name: + type: string + description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ + speed-value: + type: string + description: Captures the numeric part of the speed + speed-units: + type: string + description: Captures the units corresponding to the speed + circuit-id: + type: string + description: Circuit it + dual-mode: + type: string + description: Dual access mode (e.g., primary, secondary + management-option: + type: string + description: To provide information on who manages this circuit. A&AI or 3rd party transport provider + service-provider-name: + type: string + description: Name of the service Provider on this link. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + physical-links: + description: | + Collection of physical connections, typically between p-interfaces + properties: + physical-link: + type: array + items: + $ref: "#/getDefinitions/physical-link" + platform: + description: | + describes a platform + ###### Related Nodes + - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY) + required: + - platform-name + properties: + platform-name: + type: string + description: Name of the platform + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + platforms: + description: | + Collection of platforms + properties: + platform: + type: array + items: + $ref: "#/getDefinitions/platform" pnf: description: | PNF represents a physical network function. typically equipment used in the D1 world. - ###### Default Delete Scope - CASCADE_TO_CHILDREN ###### Related Nodes - - TO p-interface (comprises pnf, Many2Many) - - TO lag-interface (comprises pnf, One2Many) - - TO complex (Many2One) - - TO instance-group (Many2Many) - - TO zone (Many2One) - - FROM logical-link - - FROM service-instance + - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY) + - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE required: - pnf-name - in-maint @@ -41644,15 +60992,15 @@ definitions: relationship-list: type: array items: - $ref: "#/definitions/relationship" + $ref: "#/getDefinitions/relationship" p-interfaces: type: array items: - $ref: "#/definitions/p-interface" + $ref: "#/getDefinitions/p-interface" lag-interfaces: type: array items: - $ref: "#/definitions/lag-interface" + $ref: "#/getDefinitions/lag-interface" pnfs: description: | Collection of Physical Network Functions. @@ -41660,183 +61008,371 @@ definitions: pnf: type: array items: - $ref: "#/definitions/pnf" - physical-link: + $ref: "#/getDefinitions/pnf" + port-group: description: | - Collection of physical connections, typically between p-interfaces - ###### Default Delete Scope - THIS_NODE_ONLY + Used to capture the network interfaces of this VCE ###### Related Nodes - - FROM p-interface + - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE) + - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG required: - - link-name + - interface-id + - orchestration-status properties: - link-name: + interface-id: type: string - description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ - speed-value: + description: Unique ID of the interface + neutron-network-id: type: string - description: Captures the numeric part of the speed - speed-units: + description: Neutron network id of this Interface + neutron-network-name: type: string - description: Captures the units corresponding to the speed - circuit-id: + description: Neutron network name of this Interface + interface-role: type: string - description: Circuit it - dual-mode: + description: Role assigned to this Interface, should use values as defined in ECOMP Yang models. + resource-version: type: string - description: Dual access mode (e.g., primary, secondary - management-option: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + port-group-id: type: string - description: To provide information on who manages this circuit. A&AI or 3rd party transport provider - service-provider-name: + description: Unique ID for port group in vmware + port-group-name: type: string - description: Name of the service Provider on this link. - resource-version: + description: Likely to duplicate value of neutron network name + switch-name: type: string - description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + description: DVS or standard switch name (should be non-null for port groups associated with DVS) + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + cvlan-tags: + type: array + items: + $ref: "#/getDefinitions/cvlan-tag-entry" relationship-list: type: array items: - $ref: "#/definitions/relationship" - physical-links: - description: | - Collection of physical connections, typically between p-interfaces + $ref: "#/getDefinitions/relationship" + port-groups: properties: - physical-link: + port-group: type: array items: - $ref: "#/definitions/physical-link" - vig-server: + $ref: "#/getDefinitions/port-group" + project: description: | - vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607 - ###### Default Delete Scope - THIS_NODE_ONLY + describes the project ###### Related Nodes - - FROM ipsec-configuration (is composed of vig-server) + - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY) required: - - vig-address-type + - project-name properties: - vig-address-type: - type: string - description: indicates whether the VIG is for AVPN or INTERNET - ipaddress-v4-vig: - type: string - description: v4 IP of the vig server - ipaddress-v6-vig: + project-name: type: string - description: v6 IP of the vig server + description: Name of the project deploying a service resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: - $ref: "#/definitions/relationship" - vig-servers: + $ref: "#/getDefinitions/relationship" + projects: + description: | + Collection of projects properties: - vig-server: + project: type: array items: - $ref: "#/definitions/vig-server" - ipsec-configuration: + $ref: "#/getDefinitions/project" + properties: description: | - IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C - ###### Default Delete Scope - CASCADE_TO_CHILDREN + Property holder for query properties or instance properties + properties: + property-name: + type: string + property-value: + type: string + property-constraint: + description: | + TBD ###### Related Nodes - - TO vig-server (comprises ipsec-configuration, One2Many) - - FROM generic-vnf + - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) required: - - ipsec-configuration-id + - property-constraint-uuid + - constraint-type + - property-name + - property-value properties: - ipsec-configuration-id: + property-constraint-uuid: type: string - description: UUID of this configuration - requested-vig-address-type: + constraint-type: type: string - description: Indicate the type of VIG server like AVPN, INTERNET, BOTH - requested-encryption-strength: + property-name: type: string - description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc - requested-dmz-type: + property-value: type: string - description: can offer a shared DMZ or a DMZ specific to a customer - shared-dmz-network-address: + resource-version: type: string - description: Network address of shared DMZ - requested-customer-name: + property-constraints: + properties: + property-constraint: + type: array + items: + $ref: "#/getDefinitions/property-constraint" + pserver: + description: | + Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver. + ###### Related Nodes + - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE) + - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE) + - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE) + - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE) + - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE) + - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER + - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE + - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT + required: + - hostname + - in-maint + properties: + hostname: type: string - description: If the DMZ is a custom DMZ, this field will indicate the customer information - ike-version: + description: Value from executing hostname on the compute node. + ptnii-equip-name: type: string - description: can be 1 or 2 - ikev1-authentication: + description: PTNII name + number-of-cpus: + type: integer + format: int32 + description: Number of cpus + disk-in-gigabytes: + type: integer + format: int32 + description: Disk size, in GBs + ram-in-megabytes: + type: integer + format: int32 + description: RAM size, in MBs + equip-type: type: string - description: Contains values like md5, sha1, sha256, sha384 - ikev1-encryption: + description: Equipment type. Source of truth should define valid values. + equip-vendor: type: string - description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc - ikev1-dh-group: + description: Equipment vendor. Source of truth should define valid values. + equip-model: type: string - description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14 - ikev1-am-group-id: + description: Equipment model. Source of truth should define valid values. + fqdn: type: string - description: Group name defined in VIG for clients using aggressive mode - ikev1-am-password: + description: Fully-qualified domain name + pserver-selflink: type: string - description: pre-shared key for the above group name - ikev1-sa-lifetime: + description: URL to endpoint where AAI can get more details + ipv4-oam-address: type: string - description: Lifetime for IKEv1 SA - ipsec-authentication: + description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device. + serial-number: type: string - description: md5, sha1, sha256, sha384 - ipsec-encryption: + description: Serial number, may be queried + ipaddress-v4-loopback-0: type: string - description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc - ipsec-sa-lifetime: + description: IPV4 Loopback 0 address + ipaddress-v6-loopback-0: type: string - description: Life time for IPSec SA - ipsec-pfs: + description: IPV6 Loopback 0 address + ipaddress-v4-aim: type: string - description: enable PFS or not - xauth-userid: + description: IPV4 AIM address + ipaddress-v6-aim: type: string - description: user ID for xAuth, sm-user, ,nmteHostName - xauth-user-password: + description: IPV6 AIM address + ipaddress-v6-oam: type: string - description: Encrypted using the Juniper $9$ algorithm - dpd-interval: + description: IPV6 OAM address + inv-status: type: string - description: The time between DPD probe - dpd-frequency: + description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI. + pserver-id: type: string - description: Maximum number of DPD before claiming the tunnel is down + description: ID of Pserver + internet-topology: + type: string + description: internet topology of Pserver + in-maint: + type: boolean resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + pserver-name2: + type: string + description: alternative pserver name + purpose: + type: string + description: purpose of pserver + prov-status: + type: string + description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV] relationship-list: type: array items: - $ref: "#/definitions/relationship" - vig-servers: + $ref: "#/getDefinitions/relationship" + p-interfaces: type: array items: - $ref: "#/definitions/vig-server" - ipsec-configurations: + $ref: "#/getDefinitions/p-interface" + lag-interfaces: + type: array + items: + $ref: "#/getDefinitions/lag-interface" + pservers: + description: | + Collection of compute hosts. properties: - ipsec-configuration: + pserver: type: array items: - $ref: "#/definitions/ipsec-configuration" + $ref: "#/getDefinitions/pserver" + query-parameters: + description: | + QueryParameters for performing a named-query or model query + properties: + named-query: + type: object + $ref: "#/getDefinitions/named-query" + overloaded-model: + type: object + $ref: "#/getDefinitions/overloaded-model" + related-lookup: + description: | + TBD + ###### Related Nodes + - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE) + required: + - related-lookup-uuid + - source-node-type + - source-node-property + - target-node-type + - target-node-property + properties: + related-lookup-uuid: + type: string + source-node-type: + type: string + source-node-property: + type: string + target-node-type: + type: string + target-node-property: + type: string + property-collect-list: + type: string + resource-version: + type: string + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + related-lookups: + properties: + related-lookup: + type: array + items: + $ref: "#/getDefinitions/related-lookup" + related-to-property: + properties: + property-key: + type: string + description: Key part of a key/value pair + property-value: + type: string + description: Value part of a key/value pair + relationship: + properties: + related-to: + type: string + description: A keyword provided by A&AI to indicate type of node. + related-link: + type: string + description: URL to the object in A&AI. + relationship-data: + type: array + items: + $ref: "#/getDefinitions/relationship-data" + related-to-property: + type: array + items: + $ref: "#/getDefinitions/related-to-property" + relationship-data: + required: + - relationship-key + - relationship-value + properties: + relationship-key: + type: string + description: A keyword provided by A&AI to indicate an attribute. + relationship-value: + type: string + description: Value of the attribute. + relationship-list: + properties: + relationship: + type: array + items: + $ref: "#/getDefinitions/relationship" + reserved-prop-names: + description: | + Internal map to define some reserved properties of a vertex + properties: + last-mod-source-of-truth: + type: string + aai-node-type: + type: string + aai-created-ts: + type: integer + format: int64 + aai-unique-key: + type: string + aai-last-mod-ts: + type: integer + format: int64 + source-of-truth: + type: string + aai-uri: + type: string + response-list: + description: | + Response container for the results of a named-query or model query + properties: + inventory-response-items: + type: object + $ref: "#/getDefinitions/inventory-response-items" + result-data: + properties: + resource-type: + type: string + description: The specific type of node in the A&AI graph + resource-link: + type: string + description: The URL to the specific resource route-table-reference: description: | Openstack route table reference. - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - FROM l3-network + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY) required: - route-table-reference-id - route-table-reference-fqdn @@ -41853,7 +61389,7 @@ definitions: relationship-list: type: array items: - $ref: "#/definitions/relationship" + $ref: "#/getDefinitions/relationship" route-table-references: description: | Collection of openstack route table references @@ -41861,303 +61397,738 @@ definitions: route-table-reference: type: array items: - $ref: "#/definitions/route-table-reference" - instance-group: + $ref: "#/getDefinitions/route-table-reference" + route-target: description: | - General mechanism for grouping instances - ###### Default Delete Scope - THIS_NODE_ONLY - ###### Related Nodes - - TO model (Many2Many) - - FROM l-interface - - FROM l3-interface-ipv4-address-list - - FROM l3-interface-ipv6-address-list - - FROM pnf - - FROM allotted-resource - - FROM generic-vnf - - FROM service-instance + Route target information + ###### Related Nodes + - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE) required: - - id - - description - - type + - global-route-target + - route-target-role properties: - id: - type: string - description: Instance Group ID, UUID assigned to this instance. - description: - type: string - description: Descriptive text to help identify the usage of this instance-group - type: + global-route-target: type: string - description: Only valid value today is lower case ha for high availability - sub-type: + description: Number used to identify an RT, globally unique in the network + route-target-role: type: string - description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby] + description: Role assigned to this route target resource-version: type: string - description: Concurrency value + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. relationship-list: type: array items: - $ref: "#/definitions/relationship" - instance-groups: + $ref: "#/getDefinitions/relationship" + route-targets: description: | - Collection of openstack route table references + Collection of route target information properties: - instance-group: + route-target: type: array items: - $ref: "#/definitions/instance-group" - zone: + $ref: "#/getDefinitions/route-target" + routing-instance: description: | - A zone is a grouping of assets in a location homing to the same connections into the CBB - ###### Default Delete Scope - THIS_NODE_ONLY ###### Related Nodes - - TO complex (Many2One) - - FROM cloud-region - - FROM pserver - - FROM pnf + - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE) + - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE) + - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR required: - - zone-id - - zone-name - - design-type - - zone-context + - routing-instance-id properties: - zone-id: + routing-instance-id: type: string - description: Code assigned by AIC to the zone - zone-name: + description: Unique id of routing instance + rpm-owner: type: string - description: English name associated with the zone - design-type: + description: rpm owner + resource-version: type: string - description: Design of zone [Medium/Large?] - zone-context: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + site-pairs: + type: array + items: + $ref: "#/getDefinitions/site-pair" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + routing-instances: + description: | + set of probes related to generic-vnf routing instance + properties: + routing-instance: + type: array + items: + $ref: "#/getDefinitions/routing-instance" + sdn-zone-response: + properties: + oam-networks: + type: object + $ref: "#/getDefinitions/oam-networks" + az-and-dvs-switches: + type: array + items: + $ref: "#/getDefinitions/az-and-dvs-switches" + search: + properties: + edge-tag-query-result: + type: object + $ref: "#/getDefinitions/edge-tag-query-result" + edge-tag-query-request: + type: object + $ref: "#/getDefinitions/edge-tag-query-request" + search-results: + type: object + $ref: "#/getDefinitions/search-results" + sdn-zone-response: + type: object + $ref: "#/getDefinitions/sdn-zone-response" + search-results: + properties: + result-data: + type: array + items: + $ref: "#/getDefinitions/result-data" + secondary-filt: + description: | + SecondaryFilt for performing a named-query or model query + secondary-filter: + properties: + property-name: type: string - description: Context of zone [production/test] - status: + filter-type: type: string - description: Status of a zone. + property-value: + type: string + secondary-filts: + description: | + SecondaryFilts for performing a named-query or model query + properties: + secondary-filt: + type: array + items: + $ref: "#/getDefinitions/secondary-filt" + segmentation-assignment: + description: | + Openstack segmentation assignment. + ###### Related Nodes + - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + required: + - segmentation-id + properties: + segmentation-id: + type: string + description: Route Table Reference id, UUID assigned to this instance. resource-version: type: string description: Concurrency value relationship-list: type: array items: - $ref: "#/definitions/relationship" - zones: + $ref: "#/getDefinitions/relationship" + segmentation-assignments: description: | - Collection of zones + Collection of openstack segmentation assignments properties: - zone: + segmentation-assignment: type: array items: - $ref: "#/definitions/zone" - network: + $ref: "#/getDefinitions/segmentation-assignment" + service: description: | - Namespace for network inventory resources. + Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services. + required: + - service-id + - service-description properties: - logical-links: + service-id: + type: string + description: This gets defined by others to provide a unique ID for the service, we accept what is sent. + service-description: + type: string + description: Description of the service + service-selflink: + type: string + description: URL to endpoint where AAI can get more details + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + service-version: + type: string + description: service version + relationship-list: type: array items: - $ref: "#/definitions/logical-link" - site-pair-sets: + $ref: "#/getDefinitions/relationship" + service-capabilities: + description: | + Collection of service capabilities. + properties: + service-capability: type: array - items: - $ref: "#/definitions/site-pair-set" - vpn-bindings: + items: + $ref: "#/getDefinitions/service-capability" + service-capability: + description: | + Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this. + ###### Related Nodes + - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY) + - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK + required: + - service-type + - vnf-type + properties: + service-type: + type: string + description: This gets defined by others to provide a unique ID for the service, we accept what is sent. + vnf-type: + type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: type: array items: - $ref: "#/definitions/vpn-binding" - vpls-pes: + $ref: "#/getDefinitions/relationship" + service-design-and-creation: + description: | + Namespace for objects managed by ASDC + properties: + vnf-images: type: array items: - $ref: "#/definitions/vpls-pe" - multicast-configurations: + $ref: "#/getDefinitions/vnf-image" + services: type: array items: - $ref: "#/definitions/multicast-configuration" - vces: + $ref: "#/getDefinitions/service" + service-capabilities: type: array items: - $ref: "#/definitions/vce" - vnfcs: + $ref: "#/getDefinitions/service-capability" + models: type: array items: - $ref: "#/definitions/vnfc" - l3-networks: + $ref: "#/getDefinitions/model" + named-queries: type: array items: - $ref: "#/definitions/l3-network" - network-policies: + $ref: "#/getDefinitions/named-query" + service-instance: + description: | + Instance of a service + ###### Related Nodes + - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY) + - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY) + - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY) + - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY) + - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY) + - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY) + - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY) + - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY) + - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY) + - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY) + - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE) + - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY) + - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM + - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK + required: + - service-instance-id + properties: + service-instance-id: + type: string + description: Uniquely identifies this instance of a service + service-instance-name: + type: string + description: This field will store a name assigned to the service-instance. + model-invariant-id: + type: string + description: the ASDC model id for this resource or service model. + model-version-id: + type: string + description: the ASDC model version for this resource or service model. + persona-model-version: + type: string + description: the ASDC model version for this resource or service model. + widget-model-id: + type: string + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: + type: string + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + bandwidth-total: + type: string + description: Indicates the total bandwidth to be used for this service. + bandwidth-up-wan1: + type: string + description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device. + bandwidth-down-wan1: + type: string + description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device. + bandwidth-up-wan2: + type: string + description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device. + bandwidth-down-wan2: + type: string + description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device. + vhn-portal-url: + type: string + description: URL customers will use to access the vHN Portal. + service-instance-location-id: + type: string + description: An identifier that customers assign to the location where this service is being used. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + selflink: + type: string + description: Path to the controller object. + orchestration-status: + type: string + description: Orchestration status of this service. + relationship-list: type: array items: - $ref: "#/definitions/network-policy" - generic-vnfs: + $ref: "#/getDefinitions/relationship" + metadata: type: array items: - $ref: "#/definitions/generic-vnf" - lag-links: + $ref: "#/getDefinitions/metadatum" + allotted-resources: type: array items: - $ref: "#/definitions/lag-link" - newvces: + $ref: "#/getDefinitions/allotted-resource" + service-instances: + description: | + Collection of service instances + properties: + service-instance: type: array - items: - $ref: "#/definitions/newvce" - pnfs: + items: + $ref: "#/getDefinitions/service-instance" + service-subscription: + description: | + Object that group service instances. + ###### Related Nodes + - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE) + - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE) + - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE + required: + - service-type + properties: + service-type: + type: string + description: Value defined by orchestration to identify this service across ECOMP. + temp-ub-sub-account-id: + type: string + description: This property will be deleted from A&AI in the near future. Only stop gap solution. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + service-instances: type: array items: - $ref: "#/definitions/pnf" - physical-links: + $ref: "#/getDefinitions/service-instance" + relationship-list: type: array items: - $ref: "#/definitions/physical-link" - ipsec-configurations: + $ref: "#/getDefinitions/relationship" + service-subscriptions: + description: | + Collection of objects that group service instances. + properties: + service-subscription: type: array - items: - $ref: "#/definitions/ipsec-configuration" - route-table-references: + items: + $ref: "#/getDefinitions/service-subscription" + services: + description: | + Collection of service model definitions. Likely to be deprecated in favor of models from ASDC. + properties: + service: type: array - items: - $ref: "#/definitions/route-table-reference" - instance-groups: + items: + $ref: "#/getDefinitions/service" + site-pair: + description: | + ###### Related Nodes + - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE) + - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE) + - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE + required: + - site-pair-id + properties: + site-pair-id: + type: string + description: unique identifier of probe + source-ip: + type: string + description: Prefix address + destination-ip: + type: string + description: Prefix address + ip-version: + type: string + description: ip version, v4, v6 + destination-hostname: + type: string + description: Hostname of the destination equipment to which SLAs are measured against. + destination-equip-type: + type: string + description: The type of destinatination equipment. Could be Router, etc. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + classes-of-service: type: array items: - $ref: "#/definitions/instance-group" - zones: + $ref: "#/getDefinitions/class-of-service" + relationship-list: type: array items: - $ref: "#/definitions/zone" - inventory: + $ref: "#/getDefinitions/relationship" + site-pair-set: + description: | + Set of instances for probes used to measure service level agreements + ###### Related Nodes + - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY) + - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE) + - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE + required: + - site-pair-set-id properties: - search: - type: object - $ref: "#/definitions/search" - actions: - type: object - $ref: "#/definitions/actions" - cloud-infrastructure: - type: object - $ref: "#/definitions/cloud-infrastructure" - business: - type: object - $ref: "#/definitions/business" - service-design-and-creation: - type: object - $ref: "#/definitions/service-design-and-creation" - network: - type: object - $ref: "#/definitions/network" - aai-internal: - type: object - $ref: "#/definitions/aai-internal" - nodes: + site-pair-set-id: + type: string + description: Unique id of site pair set. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + routing-instances: type: array items: - $ref: "#/definitions/" - edge-tag-query-result: + $ref: "#/getDefinitions/routing-instance" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + site-pair-sets: + description: | + Collection of sets of instances for probes related to generic-vnf properties: - tagged-inventory-item-list: + site-pair-set: type: array items: - $ref: "#/definitions/tagged-inventory-item-list" - tagged-inventory-item-list: + $ref: "#/getDefinitions/site-pair-set" + site-pairs: + description: | + probe within a set properties: - inventory-item: + site-pair: type: array items: - $ref: "#/definitions/inventory-item" - inventory-item: + $ref: "#/getDefinitions/site-pair" + snapshot: + description: | + Openstack snapshot + ###### Related Nodes + - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE) + required: + - snapshot-id properties: - inventory-item-type: + snapshot-id: type: string - inventory-item-link: + description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots. + snapshot-name: type: string - inventory-item-data: + description: Snapshot name + snapshot-architecture: + type: string + description: Operating system architecture + snapshot-os-distro: + type: string + description: The common name of the operating system distribution in lowercase + snapshot-os-version: + type: string + description: The operating system version as specified by the distributor. + application: + type: string + description: The application that the image instantiates. + application-vendor: + type: string + description: The vendor of the application. + application-version: + type: string + description: The version of the application. + snapshot-selflink: + type: string + description: URL to endpoint where AAI can get more details + prev-snapshot-id: + type: string + description: This field contains the UUID of the previous snapshot (if any). + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: type: array - items: - $ref: "#/definitions/inventory-item-data" - tagged-inventory-item-list: + items: + $ref: "#/getDefinitions/relationship" + snapshots: + description: | + Collection of openstack snapshots + properties: + snapshot: type: array items: - $ref: "#/definitions/tagged-inventory-item-list" - inventory-item-data: + $ref: "#/getDefinitions/snapshot" + sriov-pf: + description: | + SR-IOV Physical Function + ###### Related Nodes + - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE) + - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE) + required: + - pf-pci-id properties: - property-name: + pf-pci-id: type: string - property-value: + description: Identifier for the sriov-pf + resource-version: type: string - edge-tag-query-request: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + sriov-pfs: + description: | + Collection of SR-IOV Physical Functions. properties: - edge-tag: + sriov-pf: + type: array + items: + $ref: "#/getDefinitions/sriov-pf" + sriov-vf: + description: | + SR-IOV Virtual Function (not to be confused with virtual network function) + ###### Related Nodes + - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE) + required: + - pci-id + properties: + pci-id: type: string - result-detail: + description: PCI ID used to identify the sriov-vf + vf-vlan-filter: type: string - start-node-type: + description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM. + vf-mac-filter: type: string - start-node-filter: - type: array - items: - $ref: "#/definitions/start-node-filter" - include-node-filter: + description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM. + vf-vlan-strip: + type: boolean + description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM. + vf-vlan-anti-spoof-check: + type: boolean + description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs. + vf-mac-anti-spoof-check: + type: boolean + description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs. + vf-mirrors: + type: string + description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports. + vf-broadcast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM + vf-unknown-multicast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM + vf-unknown-unicast-allow: + type: boolean + description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM + vf-insert-stag: + type: boolean + description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM. + vf-link-status: + type: string + description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: + type: string + description: Neutron network id of the interface + relationship-list: type: array - items: - $ref: "#/definitions/include-node-filter" - secondary-filter: + items: + $ref: "#/getDefinitions/relationship" + sriov-vfs: + description: | + Collection of SR-IOV Virtual Functions. + properties: + sriov-vf: type: array items: - $ref: "#/definitions/secondary-filter" + $ref: "#/getDefinitions/sriov-vf" start-node-filter: properties: property-name: type: string property-value: type: string - include-node-filter: + subnet: + description: | + ###### Related Nodes + - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY) + - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST + required: + - subnet-id + - dhcp-enabled properties: - include-node-type: + subnet-id: type: string - secondary-filter: - properties: - property-name: + description: Subnet ID, should be UUID. + subnet-name: type: string - filter-type: + description: Name associated with the subnet. + neutron-subnet-id: type: string - property-value: + description: Neutron id of this subnet + gateway-address: type: string - search-results: + description: gateway ip address + network-start-address: + type: string + description: network start address + cidr-mask: + type: string + description: cidr mask + ip-version: + type: string + description: ip version + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO + dhcp-enabled: + type: boolean + dhcp-start: + type: string + description: the start address reserved for use by dhcp + dhcp-end: + type: string + description: the last address reserved for use by dhcp + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + subnets: properties: - result-data: + subnet: type: array items: - $ref: "#/definitions/result-data" - result-data: + $ref: "#/getDefinitions/subnet" + tagged-inventory-item-list: properties: - resource-type: + inventory-item: + type: array + items: + $ref: "#/getDefinitions/inventory-item" + tenant: + description: | + Openstack tenant + ###### Related Nodes + - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY) + - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY) + - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY) + - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE) + - TENANT cannot be deleted if linked to VSERVER + required: + - tenant-id + - tenant-name + properties: + tenant-id: type: string - description: The specific type of node in the A&AI graph - resource-link: + description: Unique id relative to the cloud-region. + tenant-name: type: string - description: The URL to the specific resource - sdn-zone-response: + description: Readable name of tenant + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + vservers: + type: array + items: + $ref: "#/getDefinitions/vserver" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + tenants: + description: | + Collection of openstack tenants. properties: - oam-networks: - type: object - $ref: "#/definitions/oam-networks" - az-and-dvs-switches: + tenant: type: array items: - $ref: "#/definitions/az-and-dvs-switches" - az-and-dvs-switches: + $ref: "#/getDefinitions/tenant" + tunnel-xconnect: + description: | + Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted + ###### Related Nodes + - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE) + required: + - id + - bandwidth-up-wan1 + - bandwidth-down-wan1 + - bandwidth-up-wan2 + - bandwidth-down-wan2 properties: - dvs-switches: - type: object - $ref: "#/definitions/dvs-switches" - availability-zone: - type: object - $ref: "#/definitions/availability-zone" + id: + type: string + description: Allotted Resource id UUID assigned to this instance. + bandwidth-up-wan1: + type: string + description: The WAN uplink bandwidth for WAN1 + bandwidth-down-wan1: + type: string + description: The WAN downlink bandwidth for WAN1 + bandwidth-up-wan2: + type: string + description: The WAN uplink bandwidth for WAN2 + bandwidth-down-wan2: + type: string + description: The WAN downlink bandwidth for WAN2 + resource-version: + type: string + description: Concurrency value + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + tunnel-xconnects: + description: | + This object is used to store the specific tunnel cross connect aspects of an allotted resource + properties: + tunnel-xconnect: + type: array + items: + $ref: "#/getDefinitions/tunnel-xconnect" update: description: | Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team. @@ -42169,275 +62140,789 @@ definitions: update-node-key: type: array items: - $ref: "#/definitions/update-node-key" + $ref: "#/getDefinitions/update-node-key" update-node-uri: type: string action: type: array items: - $ref: "#/definitions/action" - action: - properties: - action-type: - type: string - action-data: - type: array - items: - $ref: "#/definitions/action-data" - action-data: - properties: - property-name: - type: string - property-value: - type: string + $ref: "#/getDefinitions/action" update-node-key: properties: key-name: type: string key-value: type: string - notify: + vce: + description: | + Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated. + ###### Related Nodes + - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY) + - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY) + - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY) + - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP required: - - event-id + - vnf-id + - vnf-name + - vnf-type properties: - event-id: + vnf-id: type: string - node-type: + description: Unique id of VNF. This is unique across the graph. + vnf-name: type: string - event-trigger: + description: Name of VNF. + vnf-name2: type: string - key-data: - type: array - items: - $ref: "#/definitions/key-data" - selflink: + description: Alternate name of VNF. + vnf-type: type: string - key-data: - properties: - key-name: + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + service-id: type: string - key-value: + description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED. + regional-resource-zone: type: string - notification-event: - properties: - cambria.partition: + description: Regional way of organizing pservers, source of truth should define values + prov-status: type: string - notification-event-header: - type: object - $ref: "#/definitions/notification-event-header" - notification-event-header: + description: Trigger for operational monitoring of this resource by Service Assurance systems. + operational-status: + type: string + description: Indicator for whether the resource is considered operational + license-key: + type: string + description: OBSOLETE - do not use + equipment-role: + type: string + description: Network role being played by this VNF + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by MSO + heat-stack-id: + type: string + description: Heat stack id corresponding to this instance, managed by MSO + mso-catalog-key: + type: string + description: Corresponds to the SDN-C catalog id used to configure this VCE + vpe-id: + type: string + description: Unique ID of VPE connected to this VCE. + v6-vce-wan-address: + type: string + description: Valid v6 IP address for the WAN Link on this router. Implied length of /64. + ipv4-oam-address: + type: string + description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + ipv4-loopback0-address: + type: string + description: Loopback0 address + entitlement-resource-uuid: + type: string + description: OBSOLETE - see child relationships + port-groups: + type: array + items: + $ref: "#/getDefinitions/port-group" + licenses: + type: array + items: + $ref: "#/getDefinitions/license" + entitlements: + type: array + items: + $ref: "#/getDefinitions/entitlement" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + vces: + description: | + Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated. properties: - id: + vce: + type: array + items: + $ref: "#/getDefinitions/vce" + vf-module: + description: | + a deployment unit of VNFCs + ###### Related Nodes + - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY) + - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY) + - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE) + - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY) + - VF-MODULE cannot be deleted if linked to VNFC + required: + - vf-module-id + - is-base-vf-module + properties: + vf-module-id: type: string - timestamp: + description: Unique ID of vf-module. + vf-module-name: type: string - source-name: + description: Name of vf-module + heat-stack-id: type: string - domain: + description: Heat stack id corresponding to this instance. + orchestration-status: type: string - sequence-number: + description: orchestration status of this vf-module, mastered by MSO + is-base-vf-module: + type: boolean + resource-version: type: string - severity: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + model-invariant-id: type: string - event-type: + description: the ASDC model id for this resource or service model. + model-version-id: type: string - version: + description: the ASDC model version for this resource or service model. + persona-model-version: type: string - action: + description: the ASDC model version for this resource or service model. + model-customization-id: type: string - entity-type: + description: captures the id of all the configuration used to customize the resource for the service. + widget-model-id: type: string - top-entity-type: + description: the ASDC data dictionary widget model. This maps directly to the A&AI widget. + widget-model-version: type: string - entity-link: + description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget. + contrail-service-instance-fqdn: type: string - status: + description: the Contrail unique ID for a service-instance + module-index: + type: integer + format: int32 + description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit + selflink: type: string - reserved-prop-names: + description: Path to the controller object. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + vf-modules: description: | - Internal map to define some reserved properties of a vertex + Collection of vf-modules, a deployment unit of VNFCs properties: - last-mod-source-of-truth: + vf-module: + type: array + items: + $ref: "#/getDefinitions/vf-module" + vig-server: + description: | + vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607 + ###### Related Nodes + - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE) + required: + - vig-address-type + properties: + vig-address-type: type: string - aai-node-type: + description: indicates whether the VIG is for AVPN or INTERNET + ipaddress-v4-vig: type: string - aai-created-ts: + description: v4 IP of the vig server + ipaddress-v6-vig: + type: string + description: v6 IP of the vig server + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + vig-servers: + properties: + vig-server: + type: array + items: + $ref: "#/getDefinitions/vig-server" + vip-ipv4-address-list: + description: | + IPv4 Address Range + ###### Related Nodes + - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY) + - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY) + required: + - vip-ipv4-address + properties: + vip-ipv4-address: + type: string + description: IP address + vip-ipv4-prefix-length: type: integer format: int64 - aai-unique-key: - type: string - aai-last-mod-ts: + description: Prefix length, 32 for single address + vlan-id-inner: type: integer format: int64 - source-of-truth: + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + resource-version: type: string - aai-uri: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: type: string - edge-prop-names: + description: Neutron network id of the interface that address belongs to + neutron-subnet-id: + type: string + description: Neutron id of subnet that address belongs to + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + vip-ipv6-address-list: description: | - Internal map to define the properties of an edge and interpret the map EdgeRules + IPv6 Address Range + ###### Related Nodes + - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY) + - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY) + - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY) + required: + - vip-ipv6-address properties: - edgeLabel: + vip-ipv6-address: type: string - direction: + description: IP address + vip-ipv6-prefix-length: + type: integer + format: int64 + description: Prefix length, 128 for single address + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + is-floating: + type: boolean + description: Indicator of fixed or floating address + resource-version: type: string - multiplicityRule: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + neutron-network-id: type: string - isParent: - type: boolean - usesResource: - type: boolean - hasDelTarget: - type: boolean - SVC-INFRA: - type: boolean - SVC-INFRA-REV: - type: boolean - model-and-named-query-search: + description: Neutron network id of the interface that address belongs to + neutron-subnet-id: + type: string + description: Neutron id of subnet that address belongs to + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + virtual-data-center: description: | - ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query + Virtual organization of cloud infrastructure elements in a data center context + ###### Related Nodes + - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY) + required: + - vdc-id + - vdc-name properties: - query-parameters: - type: object - $ref: "#/definitions/query-parameters" - instance-filters: - type: object - $ref: "#/definitions/instance-filters" - secondary-filts: - type: object - $ref: "#/definitions/secondary-filts" - top-node-type: + vdc-id: type: string - secondary-filter-cut-point: + description: Unique ID of the vdc + vdc-name: type: string - query-parameters: + description: Name of the virtual data center + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + virtual-data-centers: description: | - QueryParameters for performing a named-query or model query + Virtual organization of cloud infrastructure elements in a data center context properties: - named-query: - type: object - $ref: "#/definitions/named-query" - overloaded-model: - type: object - $ref: "#/definitions/overloaded-model" - overloaded-model: + virtual-data-center: + type: array + items: + $ref: "#/getDefinitions/virtual-data-center" + vlan: description: | - Allows for legacy POST of old-style and new-style models + Definition of vlan + ###### Related Nodes + - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE) + - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY) + - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY) + - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY) + - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY) + - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE) + - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST + - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK required: - - model-invariant-id - - model-name-version-id - - model-type - - model-name - - model-id - - model-version + - vlan-interface + - in-maint properties: - model-invariant-id: + vlan-interface: type: string - description: Unique identifier corresponding to the main definition of a model in ASDC - model-name-version-id: + description: String that identifies the interface + vlan-id-inner: + type: integer + format: int64 + description: Inner VLAN tag + vlan-id-outer: + type: integer + format: int64 + description: Outer VLAN tag + resource-version: type: string - description: Unique identifier corresponding to one version of a model in ASDC - model-type: + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + speed-value: type: string - description: Type of the model, e.g., service, resource, widget, etc. - model-name: + description: Captures the numeric part of the speed + speed-units: type: string - description: Name of the model, which can change from version to version. - model-id: + description: Captures the units corresponding to the speed + vlan-description: type: string - description: Invariant unique ID which does not change from version to version - model-version: + description: Used to describe (the service associated with) the vlan + backdoor-connection: type: string - description: Version - model-description: + description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device. + vpn-id: type: string - description: Description + description: This indicates the customers VPN ID associated with this vlan + orchestration-status: + type: string + description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C. + in-maint: + type: boolean + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + l3-interface-ipv4-address-list: + type: array + items: + $ref: "#/getDefinitions/l3-interface-ipv4-address-list" + l3-interface-ipv6-address-list: + type: array + items: + $ref: "#/getDefinitions/l3-interface-ipv6-address-list" + vlans: + properties: + vlan: + type: array + items: + $ref: "#/getDefinitions/vlan" + vnf: + description: | + Abstract vnf class + required: + - vnf-id + properties: + vnf-id: + type: string + description: Unique id of VNF. This is unique across the graph. + vnf-image: + description: | + Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge. + ###### Related Nodes + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE) + - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF + required: + - vnf-image-uuid + - application + - application-vendor + properties: + vnf-image-uuid: + type: string + description: Unique ID of this asset + application: + type: string + description: The application that the image instantiates. + application-vendor: + type: string + description: The vendor of the application. + application-version: + type: string + description: The version of the application. + selflink: + type: string + description: URL to endpoint where AAI can get more details resource-version: type: string description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. - model-vers: - type: object - $ref: "#/definitions/model-vers" relationship-list: - type: object - $ref: "#/definitions/relationship-list" - instance-filters: + type: array + items: + $ref: "#/getDefinitions/relationship" + vnf-images: description: | - InstanceFilters for performing a named-query or model query + Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge. properties: - instance-filter: + vnf-image: type: array items: - $ref: "#/definitions/instance-filter" - instance-filter: + $ref: "#/getDefinitions/vnf-image" + vnfc: description: | - InstanceFilter for performing a named-query or model query - secondary-filts: + ###### Related Nodes + - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE) + - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY) + required: + - vnfc-name + - vnfc-function-code + - vnfc-type + - in-maint + - is-closed-loop-disabled + properties: + vnfc-name: + type: string + description: Unique ID of vnfc. + vnfc-function-code: + type: string + description: function code + vnfc-type: + type: string + description: type + prov-status: + type: string + description: prov status of this vnfc + orchestration-status: + type: string + description: Orchestration status of this VNF, mastered by APP-C + ipaddress-v4-oam-vip: + type: string + description: Oam V4 vip address of this vnfc + in-maint: + type: boolean + is-closed-loop-disabled: + type: boolean + group-notation: + type: string + description: Group notation of VNFC + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + vnfcs: description: | - SecondaryFilts for performing a named-query or model query + virtual network components associated with a vserver from application controller. properties: - secondary-filt: + vnfc: type: array items: - $ref: "#/definitions/secondary-filt" - secondary-filt: + $ref: "#/getDefinitions/vnfc" + volume: description: | - SecondaryFilt for performing a named-query or model query - properties: + Ephemeral Block storage volume. + ###### Related Nodes + - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume) + required: + - volume-id + - volume-selflink + properties: + volume-id: + type: string + description: Unique ID of block storage volume relative to the vserver. + volume-selflink: + type: string + description: URL to endpoint where AAI can get more details + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + volume-group: description: | - Property holder for query properties or instance properties + Persistent block-level storage. + ###### Related Nodes + - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE) + - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE) + - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY) + required: + - volume-group-id + - volume-group-name + - vnf-type properties: - property-name: + volume-group-id: type: string - property-value: + description: Unique ID of volume-group. + volume-group-name: type: string - response-list: + description: Name of the volume group. + heat-stack-id: + type: string + description: Heat stack id corresponding to this volume-group + vnf-type: + type: string + description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures. + orchestration-status: + type: string + description: Orchestration status of this volume-group + model-customization-id: + type: string + description: captures the id of all the configuration used to customize the resource for the service. + vf-module-model-customization-id: + type: string + description: helps relate the volume group to the vf-module whose components will require the volume group + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + volume-groups: description: | - Response container for the results of a named-query or model query + Collection of persistent block-level storage. properties: - inventory-response-items: - type: object - $ref: "#/definitions/inventory-response-items" - inventory-response-items: + volume-group: + type: array + items: + $ref: "#/getDefinitions/volume-group" + volumes: description: | - Container for inventory items in response list + Collection of ephemeral Block storage volumes. properties: - inventory-response-item: + volume: type: array items: - $ref: "#/definitions/inventory-response-item" - inventory-response-item: + $ref: "#/getDefinitions/volume" + vpls-pe: description: | - Inventory item for response list + VPLS Provider Edge routers. + ###### Related Nodes + - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY) + - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE) + - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE + required: + - equipment-name properties: - model-name: + equipment-name: type: string - extra-properties: - type: object - $ref: "#/definitions/extra-properties" - inventory-response-items: - type: object - $ref: "#/definitions/inventory-response-items" - extra-properties: + prov-status: + type: string + description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems. + ipv4-oam-address: + type: string + description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address). + equipment-role: + type: string + description: Client should send valid enumerated value, e.g., VPLS-PE. + vlan-id-outer: + type: integer + format: int64 + description: Temporary location for stag to get to VCE + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + p-interfaces: + type: array + items: + $ref: "#/getDefinitions/p-interface" + lag-interfaces: + type: array + items: + $ref: "#/getDefinitions/lag-interface" + vpls-pes: description: | - Extra properties for inventory item for response list + Collection of VPLS Provider Edge routers properties: - extra-property: + vpls-pe: type: array items: - $ref: "#/definitions/extra-property" - extra-property: + $ref: "#/getDefinitions/vpls-pe" + vpn-binding: + description: | + VPN binding + ###### Related Nodes + - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY) + - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE) + - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK + - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET + required: + - vpn-id + - vpn-name properties: - property-name: + vpn-id: type: string - property-value: + description: VPN ID, globally unique within A&AI + vpn-name: type: string - vnf: + description: VPN Name + vpn-platform: + type: string + description: the platform associated with the VPN example AVPN, Mobility + vpn-type: + type: string + description: Type of the vpn, should be taken from enumerated/valid values + route-distinguisher: + type: string + description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network. + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + route-targets: + type: array + items: + $ref: "#/getDefinitions/route-target" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + description: l3-networks relate to vpn-bindings + vpn-bindings: + properties: + vpn-binding: + type: array + items: + $ref: "#/getDefinitions/vpn-binding" + vserver: description: | - Abstract vnf class + Virtual Servers, aka virtual machine or VM. + ###### Related Nodes + - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE) + - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE) + - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE) + - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE) + - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE) + - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY) + - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY) + - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE) + - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY) + - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY) + - VSERVER is DELETED when these are DELETED L-INTERFACE + - VSERVER deletion means associated objects of these types are also DELETED:VOLUME required: - - vnf-id + - vserver-id + - vserver-name + - vserver-selflink + - in-maint + - is-closed-loop-disabled properties: - vnf-id: + vserver-id: type: string - description: Unique id of VNF. This is unique across the graph. + description: Unique identifier for this vserver relative to its tenant + vserver-name: + type: string + description: Name of vserver + vserver-name2: + type: string + description: Alternative name of vserver + prov-status: + type: string + description: Trigger for operational monitoring of this resource by Service Assurance systems. + vserver-selflink: + type: string + description: URL to endpoint where AAI can get more details + in-maint: + type: boolean + is-closed-loop-disabled: + type: boolean + resource-version: + type: string + description: Used for optimistic concurrency. Must be empty on create, valid on update and delete. + volumes: + type: array + items: + $ref: "#/getDefinitions/volume" + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + l-interfaces: + type: array + items: + $ref: "#/getDefinitions/l-interface" + vservers: + description: | + Collection of virtual Servers, aka virtual machines or VMs. + properties: + vserver: + type: array + items: + $ref: "#/getDefinitions/vserver" + zone: + description: | + A zone is a grouping of assets in a location homing to the same connections into the CBB + ###### Related Nodes + - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE) + - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE) + required: + - zone-id + - zone-name + - design-type + - zone-context + properties: + zone-id: + type: string + description: Code assigned by AIC to the zone + zone-name: + type: string + description: English name associated with the zone + design-type: + type: string + description: Design of zone [Medium/Large?] + zone-context: + type: string + description: Context of zone [production/test] + status: + type: string + description: Status of a zone. + resource-version: + type: string + description: Concurrency value + relationship-list: + type: array + items: + $ref: "#/getDefinitions/relationship" + zones: + description: | + Collection of zones + properties: + zone: + type: array + items: + $ref: "#/getDefinitions/zone" |