This project provides a DiscoveryStrategy for Hazelcast 3.6-RC+1 enabled applications running on Azure. It will provide all Hazelcast instances by returning VMs within your Azure resource group that are tagged with a specified value.
To add this plugin to your java project, add the following to either you maven pom or gradle configuration.
repositories {
jcenter()
}
dependencies {
compile 'com.hazelcast.azure:hazelcast-azure:1.0'
}
<dependencies>
<dependency>
<groupId>com.hazelcast.azure</groupId>
<artifactId>hazelcast-azure</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
compile 'com.hazelcast.azure:hazelcast-azure:1.0'
Check the releases for the latest version.
Ensure you've added the hazelcast hazelcast-azure
package in your maven or gradle configuration as mentioned above.
In your Hazelcast configuration, use the AzureDiscoveryStrategy
:
<network>
<join>
<multicast enabled="false"/>
<tcp-ip enabled="false" />
<aws enabled="false"/>
<discovery-strategies>
<discovery-strategy enabled="true" class="com.hazelcast.azure.AzureDiscoveryStrategy">
<properties>
<property name="client-id">CLIENT_ID</property>
<property name="client-secret">CLIENT_SECRET</property>
<property name="tenant-id">TENANT_ID</property>
<property name="subscription-id">SUB_ID</property>
<property name="cluster-id">HZLCAST001</property>
<property name="group-name">GROUP-NAME</property>
</properties>
</discovery-strategy>
</discovery-strategies>
</join>
</network>
You'll need to setup Azure Active Directory Service Principal credentials for your Azure Subscription for this plugin to work. With the credentials, fill in the placeholder values above.
client-id
- The Azure Active Directory Service Principal client IDclient-secret
- The Azure Active Directory Service Principal client secrettenant-id
- The Azure Active Directory tenant idsubscription-id
- The Azure subscription idcluster-id
- The name of the tag on the hazelcast vm resourcesgroup-name
- The Azure resource group name of the cluster. You can find this in the Azure portal or CLI.
With every Hazelcast Virtual Machine you deploy in your resource group, you need to ensure that each VM is tagged with the value of cluster-id
defined in your Hazelcast configuration. The only requirement is that every VM can access each other either by private or public IP address.
Read more about how you can tag your virtual machines.
You can also use the Azure Hazelcast Template to automatically deploy a Hazelcast cluster which uses this plugin.