Explicitly assign security group to VMs 01/31601/1
authorGary Wu <gary.i.wu@huawei.com>
Tue, 13 Feb 2018 15:09:42 +0000 (07:09 -0800)
committerGary Wu <gary.i.wu@huawei.com>
Tue, 13 Feb 2018 15:09:42 +0000 (07:09 -0800)
The default behavior for VMs without explicit
security group assignments is different in TLAB,
resulting in unreachable VMs.  This change
explicitly assigns the created security group
onap_sg to the VMs.

Change-Id: Iac635ea9a271d91f16427f4d15aa108773e6e256
Issue-ID: INT-414
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
kubernetes/config/docker/init/src/config/dcaegen2/heat/onap_dcae.yaml

index 12191bf..1a07ef2 100644 (file)
@@ -315,6 +315,8 @@ resources:
     properties:
       network: { get_resource: oam_onap }
       fixed_ips: [{"subnet": { get_resource: oam_onap_subnet }, "ip_address": { get_param: dcae_ip_addr }}]
+      security_groups:
+      - { get_resource: onap_sg }
 
   dcae_c_floating_ip:
     type: OS::Neutron::FloatingIP