WaveMaker Enterprise Setup on AzureCloud using VHD
Prerequisites
- Access to Azure to create VM and other resources. For more details, see Azure resource documentation.
- An Azure Virtual Network (VNet) represents your network in the cloud. We are assuming an Azure Virtual Network (VNet) is already built or existed. For the creation of a virtual network, see Azure Virtual Network Creation.
- Create fixed vhd with ubuntu 16.04 OS.
- Install AzCopy for copying the files from local to Azure storage account container. For installing AzCopy to respective devices, see Download AzCopy from Azure.
- Install Azure CLI to login to the Azure account. For installing Azure CLI, see Install Azure CLI from Azure.
- Assuming storage account container is already created. If not done already, for creating the container, see Creating a Container in Azure.
Creation of Network Security Groups
- For creating network security groups, see Creating NSG in Azure.
- For WME setup in Azure, it requires two security groups , including:
Creating Network Security Group for Platform Virtual Machine
- Provide necessary information, including name and region, by selecting the resource group.
- Provide tags that are name-value pairs for the network security group for categorizing the resources.
- Create a network security group for a platform virtual machine with the provided information.
- After creating the network security group under settings, select inbound security rules, create a rule for developer network access and select protocol TCP and add a rule to a network security group.
If you want ssh access to only desired networks, create another rule and provide your network IPs for ssh access.
Create another rule to open additional ports to access a Platform Virtual Machine from the Studio Workspace/App Deployment Virtual Machine. Next, select a destination.
If you select the destination as a virtual network, the security rule is applied to Virtual Machines irrespective of the virtual network of the platform Virtual Machine. If you choose the destination as an application security group, it applies only to the VMs connected to that application security group. If you select the destination as IP Addresses, the rules apply to the respected IP address resources. For more information, see Filter Network Traffic in Azure.
Next, select protocol as TCP and select the Allow action. Provide Priority after the public access ports. Click save and add the rule to the network security group.
Creation of Network Security Group for Studio Workspace/App Deployment Virtual Machine
Applies to Workspace Virtual Machine / AppDeployment Virtual Machine
- Provide necessary information, including name and region, by selecting the resource group.
- Provide tags that are name-value pairs for the network security group for categorizing the resources.
- Create a network security group for a platform virtual machine with the provided information.
Create a security rule to open additional ports to access the Platform Virtual Machine and select a destination. Note that restrictions apply to Virtual machines based on the destination selection.
If you select the destination as a virtual network, the security rule is applied to Virtual Machines irrespective of the virtual network of the platform Virtual Machine. If you choose the destination as an application security group, it applies only to the VMs connected to that application security group. If you select the destination as IP Addresses, the rules apply to the respected IP address resources. For more information, see Filter Network Traffic in Azure.
- If you want ssh access to only desired networks, create another rule and provide your network IPs for ssh access.
Copying VHD File to Azure
- Generate SAS in a storage account.
- Copy the VHD file from local to the respective created storage account container. Use the following example for copying the VHD to a container.
- AzCopy copy "localpath\filename.vhd", "container url and sas" --blob-type PageBlob
Example:
azcopy copy "C:\filename.vhd" "https://account.blob.core.windows.net/mycontainer1< generated sas >" --blob-type PageBlob
- The VHD file
WME-vhd-file.vhdshould be uploaded to the respected storage account container.
Creating the Disk Using VHD File
- Specifying the project details for the disk creation.
- Create a disk by providing necessary details, selecting the source type as storage blob, and selecting the OS disk size.
VM Creation by Using The Disk
- Provide necessary information to create VM using a disk.
- For Platform Virtual Machine, add root 50 GiB, storage 50 GiB. For wm-runtime, add 150 GiB and for wm-data, and if required add 50 GiB for /usr/local/content(/usr/local/content is optional not mandatory).
- For Studio Workspace/App Deployment Virtual Machine add root 50 GiB, storage 150 GiB for data.
- Select create VM option at the left top. create VM providing required details disks and networking.
- At Configure network security group select WME-SG-Platform-Public-and-Internal for Platform Virtual Machine and select WME-SG-Workspace-Internal for Studio Workspace/App Deployment Virtual Machine(Workspace Virtual Machine / AppDeployment Virtual Machine).
Mounting Disks in Virtual Machines
Mounting Disk in Platform Virtual Machines
- For ssh into the platform Virtual Machine use the following command.
- If you using the ssh key method for login use the following command.
ssh -i /path/to/ssh-privatekey username@ipaddress
- If you using the ssh username and password for login use the following command.
ssh username@ipaddress
- Check your list of block devices available by using the following command.
lsblk
- New volumes are raw block devices, and you must create a file system on them before you can mount and use them. For creating file systems use following command.
Command : mkfs -t ext4 /dev/<block-device-name_1>
mkfs -t ext4 /dev/<block-device-name_2>
Example :
mkfs -t ext4 /dev/sdd
mkfs -t ext4 /dev/sdc
- Use the
mkdircommand to create a mount point directory for the volume. The mount point is where the volume is located in the file system tree and where you read and write files after you mount the volume. For WME-Setup, create two directories using the following commands.
mkdir /wm-data /wm-runtime
- Use the following command to mount the volume at the directory.
Command :
mount /dev/<block-device-name_1> /wm-data
mount /dev/<block-device-name_2> /wm-runtime
Example :
mount /dev/sdc /wm-data
mount /dev/sdd /wm-runtime
- To mount an attached Azure Disks on every system reboot, add an entry for the device to the /etc/fstab file.
- Take UUID of disks for identification by using the command.
blkid
- Entry the UUID of the disks in fstab.use the following format.
UUID=your-block-device-UUID /wm-data ext4 defaults ,nofail 0 2
UUID=<block-device_1-UUID> /wm-runtime ext4 defaults ,nofail 0 2
Mounting Disks in Workspace Virtual Machine/AppDeployment Virtual Machine
Applies for StudioWorkspace Virtual Machine/AppDeployment Virtual Machine
- For ssh into the platform Virtual Machine use the following command.
- If you using the ssh key method for login use the following command.
ssh -i /path/to/ssh-privatekey username@ipaddress
- If you using the ssh username and password for login use the following command.
ssh username@ipaddress
- Check your list of block devices available by using the following command.
lsblk
- New volumes are raw block devices, and you must create a file system on them before you can mount and use them. For creating file systems use following command.
Command: mkfs -t ext4 /dev/< block-device-name >
Example: mkfs -t ext4 /dev/sdc
- Use the
mkdircommand to create a mount point directory for the volume. The mount point is where the volume is located in the file system tree and where you read and write files after you mount the volume. For WME-Setup, create two directories using the following commands.
mkdir /data
- Use the following command to mount the volume at the directory.
Command: mount /dev/block-device-name /data
Example: mount /dev/sdc /data
- To mount an attached Azure Disks on every system reboot, add an entry for the device to the /etc/fstab file.
- Take UUID of disks for identification by using the command.
blkid
- Entry the UUID of the disks in fstab.use the following format.
UUID=your-block-device-UUID /data ext4 defaults ,nofail 0 2
What's next
- Install prerequisites softwares based on OS.
- Start WME Installation process