Changed the default multicast address. 37/102337/2
authorSebastien Premont-Tendland <sebastien.premont@bell.ca>
Mon, 17 Feb 2020 16:14:02 +0000 (11:14 -0500)
committerSebastien Premont-Tendland <sebastien.premont@bell.ca>
Tue, 25 Feb 2020 19:33:19 +0000 (14:33 -0500)
commitdffb358f81f2816a931dca067f47bd49823ac5bc
tree8777b37115d302fa677ef87cf77502710d864852
parent319521c8bcc13a37268ec6279d1eba6db90568d5
Changed the default multicast address.

There's an issue with macOS when docker is installed and a multicast
address different than 224.0.0.1 is used.
https://stackoverflow.com/questions/46341715/hazelcast-multicast-does-not-work-because-of-vboxnet-which-is-used-by-docker-mac

Re-organized the test hazelcast yaml since we now fill the cluster-name
and instance-name information from the ClusterInfo object during
creation. No need to pass it in the config file anymore. This is causing
every file to be the exact same thus the consolidation.

Also fix an issue with test case using the same hazelcast service in two
different threads causing intermittent issue during the build process.

Issue-ID: CCSDK-2119
Signed-off-by: Sebastien Premont-Tendland <sebastien.premont@bell.ca>
Change-Id: I7f8328bfd93cdcabe8ab2fa844cbf9dd57f1493a
ms/blueprintsprocessor/modules/commons/processor-core/src/test/kotlin/org/onap/ccsdk/cds/blueprintsprocessor/core/cluster/HazlecastClusterServiceTest.kt
ms/blueprintsprocessor/modules/commons/processor-core/src/test/resources/hazelcast/hazelcast-5679.yaml [deleted file]
ms/blueprintsprocessor/modules/commons/processor-core/src/test/resources/hazelcast/hazelcast-5680.yaml [deleted file]
ms/blueprintsprocessor/modules/commons/processor-core/src/test/resources/hazelcast/hazelcast-5681.yaml [deleted file]
ms/blueprintsprocessor/modules/commons/processor-core/src/test/resources/hazelcast/hazelcast-5682.yaml
ms/blueprintsprocessor/modules/commons/processor-core/src/test/resources/hazelcast/hazelcast-cluster.yaml [new file with mode: 0644]