Added external_key column to IPAM_IP_ASSIGNMENT

external_key column is to store a keu uniquely identifying
the resource to a service, both within the ONAP and the
external system. That key will be set prior assignment,
and we be used during unassignment, to avoid having to
correlate to many values. The external_key *must* be unique,
at least per service. Hence lookup using both service-instance-id
and external_key will be used during unassign process.

Change-Id: I67691fc32b46bb6cbacd66402f5fda6456cd7e06
Issue-ID: CCSDK-463
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
Former-commit-id: b3cc6305655fee9a85d8ac42488e371b741a2f61

diff --git a/installation/sdnc/src/main/resources/ipam.data.dump b/installation/sdnc/src/main/resources/ipam.data.dump
index ededc73..7371077 100644 (file)
--- a/installation/sdnc/src/main/resources/ipam.data.dump
+++ b/installation/sdnc/src/main/resources/ipam.data.dump
@@ -57,6 +57,7 @@ CREATE TABLE `IPAM_IP_ASSIGNEMENT` (
   `service_instance_id` varchar(255) DEFAULT NULL,
   `vf_module_id` varchar(255) DEFAULT NULL,
   `prefix_id` varchar(255) DEFAULT NULL,
+  `external_key` varchar(255) DEFAULT NULL,
   `ip_address_id` varchar(255) DEFAULT NULL,
   `ip_address` varchar(255) DEFAULT NULL,
   `ip_address_type` varchar(255) DEFAULT NULL,