Update ip pool name to be more generic

So both vFW and vDNS use cases can re-use the same ip pool

Change-Id: I0bc2fd317774bfe8aae04df1fc021c9fc585f186
Issue-ID: SDNC-761
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
Former-commit-id: fc05622ced5e65929ed30b82212630fb9998a9d7

diff --git a/installation/sdnc/src/main/resources/ipam.data.dump b/installation/sdnc/src/main/resources/ipam.data.dump
index 00362d2..94dd19b 100644 (file)
--- a/installation/sdnc/src/main/resources/ipam.data.dump
+++ b/installation/sdnc/src/main/resources/ipam.data.dump
@@ -40,7 +40,7 @@ CREATE TABLE `IPAM_IP_POOL` (
 
 LOCK TABLES `IPAM_IP_POOL` WRITE;
 /*!40000 ALTER TABLE `IPAM_IP_POOL` DISABLE KEYS */;
-INSERT INTO `IPAM_IP_POOL` VALUES (1,'2018-08-17 20:15:12',3,'10.0.0.0/8',4,'ACTIVE','private'),(2,'2018-08-17 20:19:29',2,'192.168.10.0/24',4,'ACTIVE','unprotected'),(3,'2018-08-17 20:20:08',1,'192.168.20.0/24',4,'ACTIVE','protected');
+INSERT INTO `IPAM_IP_POOL` VALUES (1,'2018-08-17 20:15:12',3,'10.0.0.0/8',4,'ACTIVE','management'),(2,'2018-08-17 20:19:29',2,'192.168.10.0/24',4,'ACTIVE','private1'),(3,'2018-08-17 20:20:08',1,'192.168.20.0/24',4,'ACTIVE','private2');
 /*!40000 ALTER TABLE `IPAM_IP_POOL` ENABLE KEYS */;
 UNLOCK TABLES;