Merge pull request #9 from majguo/master

[MVP release] Deploy a tWAS cluster on Azure VMs

Author: git4rk

README.md

@@ -1,4 +1,38 @@
-# Deploy RHEL 7.4 VMs on Azure with IBM WebSphere Application Server ND Traditional V9.0.5.1 cluster pre-installed
- - [Create cluster with specified number of nodes](https://github.com/majguo/arm-rhel-was-nd-cluster/tree/master/arm-rhel-was-nd-cluster)
- - [Add additional nodes to the exsiting cluster](https://github.com/majguo/arm-rhel-was-nd-cluster/tree/master/add-nodes)
+# Deploy RHEL 8.3 VMs on Azure with IBM WebSphere Application Server ND Traditional V9.0.5 cluster pre-installed
 
+## Prerequisites
+
+1. Register an [Azure subscription](https://azure.microsoft.com/).
+1. The virtual machine offer which includes the image of RHEL8.3 with IBM WebSphere and JDK pre-installed is used as image reference to deploy virtual machine on Azure. Before the offer goes live in Azure Marketplace, your Azure subscription needs to be added into white list to successfully deploy VM using ARM template of this repo.
+1. Install [Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest).
+1. Install [PowerShell Core](https://docs.microsoft.com/powershell/scripting/install/installing-powershell-core-on-linux?view=powershell-7.1).
+1. Install [Maven](https://maven.apache.org/download.cgi).
+1. Install [`jq`](https://stedolan.github.io/jq/download/).
+
+## Steps of deployment
+
+1. Checkout [azure-javaee-iaas](https://github.com/Azure/azure-javaee-iaas)
+   1. Change to directory hosting the repo project & run `mvn clean install`
+1. Checkout [arm-ttk](https://github.com/Azure/arm-ttk) under the specified parent directory
+1. Checkout this repo under the same parent directory and change to directory hosting the repo project
+1. Build the project by replacing all placeholder `${<place_holder>}` with valid values
+
+   ```bash
+   mvn -Dgit.repo=<repo_user> -Dgit.tag=<repo_tag> -DibmUserId=<ibmUserId> -DibmUserPwd=<ibmUserPwd> -Ddynamic=<true|false> -DnumberOfNodes=<numberOfNodes> -DvmSize=<vmSize> -DdmgrVMPrefix=<dmgrVMPrefix> -DmanagedVMPrefix=<managedVMPrefix> -DdnsLabelPrefix=<dnsLabelPrefix> -DadminUsername=<adminUsername> -DadminPasswordOrKey=<adminPassword|adminSSHPublicKey> -DauthenticationType=<password|sshPublicKey> -DwasUsername=<wasUsername> -DwasPassword=<wasPassword> -Dtest.args="-Test All" -Ptemplate-validation-tests clean install
+   ```
+
+1. Change to `./target/arm` directory
+1. Using `deploy.azcli` to deploy
+
+   ```bash
+   ./deploy.azcli -n <deploymentName> -i <subscriptionId> -g <resourceGroupName> -l <resourceGroupLocation>
+   ```
+
+## After deployment
+
+1. If you check the resource group in [azure portal](https://portal.azure.com/), you will see multiple VMs and related resources specified for the cluster created
+1. To open IBM WebSphere Integrated Solutions Console in browser for further administration:
+   1. Login to Azure Portal
+   1. Open the resource group you specified to deploy WebSphere Cluster
+   1. Navigate to "Deployments > specified_deployment_name > Outputs"
+   1. Copy value of property `adminSecuredConsole` and browse it with credentials you specified in cluster creation