MaaS: DHCP iprange fix: use dynamic, not reserved

Without the 'type' parameter set to 'dynamic', MaaS was configured
to reserve the IP range instead of allocating it dynamically.

This led to IP exhaustion warnings in MaaS dashboard, as well as
wrongful IP allocation.

Change-Id: I1f2b90bf4cd2393cfab6d4bc17771cef009701c0
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>

diff --git a/mcp/reclass/classes/cluster/baremetal-mcp-ocata-ovs-ha/infra/maas.yml b/mcp/reclass/classes/cluster/baremetal-mcp-ocata-ovs-ha/infra/maas.yml
index a7a502f..b2813f9 100644 (file)
--- a/mcp/reclass/classes/cluster/baremetal-mcp-ocata-ovs-ha/infra/maas.yml
+++ b/mcp/reclass/classes/cluster/baremetal-mcp-ocata-ovs-ha/infra/maas.yml
@@ -40,6 +40,7 @@ parameters:
           iprange:
             start: 192.168.11.5
             end: 192.168.11.250
+            type: dynamic
       machines:
         kvm01:
           interface: