Add support to use config-drive

Add support to explicitly request config-drive
for BMC and Undercloud type instances.

NOTE: config-drive is always disabled for the
virtual barmetal intances. This is already hard
coded in virtual-baremetal-servers.yaml and
virtual-baremetal-servers-volume.yaml.

Related-Bug: #1929384
Closes-Bug: #1929419
Change-Id: I1f6454363b5d8a5c325afe194ed1484ff618f729

templates/bmc.yaml

@@ -93,6 +93,11 @@ parameters:
     type: number
     description: Number of baremetal nodes to deploy
 
+  config_drive:
+    type: boolean
+    default: false
+    description: If True, enable config drive on the server.
+
 resources:
   bmc_port:
     type: OS::OVB::BMCPort
@@ -132,6 +137,7 @@ resources:
       key_name: {get_param: key_name}
       networks: {get_attr: [bmc_port, port]}
       name: {get_param: bmc_prefix}
+      config_drive: {get_param: config_drive}
       user_data_format: RAW
       user_data:
         str_replace:

templates/undercloud.yaml

@@ -19,6 +19,10 @@ parameters:
     type: json
   external_net:
     type: string
+  config_drive:
+    type: boolean
+    default: false
+    description: If True, enable config drive on the server.
 
 resources:
   undercloud_ports:
@@ -38,6 +42,7 @@ resources:
       name: {get_param: undercloud_name}
       user_data_format: {get_param: undercloud_user_data_format}
       user_data: {get_param: undercloud_user_data}
+      config_drive: {get_param: config_drive}
 
   undercloud_floating_ip:
     type: OS::OVB::UndercloudFloating