Created this issue to facilitate & track the upcoming changes in Azure to support multiple VMSS.
Present state:
Currently Muchos deployment on Azure is based on single Virtual Machine Scale Set - VMSS. All VM instances in a single VMSS are of the same size (CPU, RAM and disks). This can be a constraint if a user wants to use different resource size for leader nodes as compared to worker nodes. In multiple VMSS users can configure different resource size for each VMSS. Also, there are several other advantages which will be documented as part of the multi VMSS PR (Part 2). By default, this feature will be turned off in muchos.props.
Implementation:
The total no of files changed in the PR eventually grew up in size, so decided to split them into logical parts as highlighted below. Once the first PR has been merged I'll post the next one and finally the last part.
Created this issue to facilitate & track the upcoming changes in Azure to support multiple VMSS.
Present state: Currently Muchos deployment on Azure is based on single Virtual Machine Scale Set - VMSS. All VM instances in a single VMSS are of the same size (CPU, RAM and disks). This can be a constraint if a user wants to use different resource size for leader nodes as compared to worker nodes. In multiple VMSS users can configure different resource size for each VMSS. Also, there are several other advantages which will be documented as part of the multi VMSS PR (Part 2). By default, this feature will be turned off in muchos.props.
Implementation: The total no of files changed in the PR eventually grew up in size, so decided to split them into logical parts as highlighted below. Once the first PR has been merged I'll post the next one and finally the last part.
Part1 - Refactoring of single VMSS code PR: https://github.com/apache/fluo-muchos/pull/393
Part2 - Add support (optional) for multiple VMSS feature PR: #394
Part3 - Add validation checks for Azure deployments PR: #395