Skip to content

Migration compatibility for WorkloadBuilder service#245

Merged
venu-sivanadham merged 41 commits into
Azure:masterfrom
venu-sivanadham:merge_to_moodle_master
Apr 8, 2021
Merged

Migration compatibility for WorkloadBuilder service#245
venu-sivanadham merged 41 commits into
Azure:masterfrom
venu-sivanadham:merge_to_moodle_master

Conversation

@venu-sivanadham
Copy link
Copy Markdown
Member

Workload builder service can migrate(lift & shift) Moodle application running on on-premises VMWare infrastructure to Azure.
Workload builder service uses ARM templates from this Moodle repo to prepare the infra in Azure. Below changes are made in this repo to support migration flow:

  1. Added migration specific entry-point/wrapper template which will invoke main template with appropriate parameters.
  2. Added another wrapper template to create file-share storage account. In migration flow, the Moodle code/config/data will be migration from on-prem to azure file-share as 1st step before creating complete infrastructure.
  3. Added few parameters to azuredeploy template to support migration flow.
  4. Changes to install_moodle.sh to skip fresh Moodle installation commands. And also added couple of helper functions to update Moodle config settings in the migrated config file.

venu-sivanadham and others added 30 commits October 28, 2020 21:27
Migration specific entry point arm templates
Migration Flow: Moodle DB import functionality
added php version input parameter and other minor fixes
included escape chars for config value replacement
* Update install_moodle.sh

* Update azuredeploy-migration.json

* reverted moodle base path

* .
* removed non-required params
* changed all param types to string
* change output type to string
Updated artifacts location from 'Azure' repo to 'venu-sivanadham' to make sure nested arm templates are called from same repo.
Storage account in eastus2euap doesn't support kind 'FileStorage'. Hence for that, we change the location to westus2.
Space was missing in password argument
venu-sivanadham and others added 10 commits February 26, 2021 18:14
Use nearest prod region if deployment resource group location is eastus2euap
location southeastasia will be used for deployment if RG is located in 'eastus2euap' location.
location southeastasia will be used for deployment if RG is located in 'eastus2euap' location.
Added 8.0 as allowed mysqlversion in parameters
Taking latest changes from Azure/Moodle repo
"type": "string"
},
"fileServerDiskSize": {
"defaultValue": "100",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if we should default to 1024GB for max IOPS across the board. Thoughts @naioja ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make sense, and changed it to 1024 GB as default file server size.

Comment thread nested/storageAccount.json
Copy link
Copy Markdown
Contributor

@UmakanthOS UmakanthOS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Left a couple of comments but no need to address them.

@venu-sivanadham venu-sivanadham merged commit 5f0a36d into Azure:master Apr 8, 2021
naioja pushed a commit that referenced this pull request Dec 29, 2025
Workload builder service can migrate(lift & shift) Moodle application running on on-premises VMWare infrastructure to Azure. Workload builder service uses ARM templates from this Moodle repo to prepare the infra in Azure. Below changes are made in this repo to support migration flow:

- Added migration specific entry-point/wrapper template which will invoke main template with appropriate parameters.
- Added another wrapper template to create file-share storage account. In migration flow, the Moodle code/config/data will be migration from on-prem to azure file-share as 1st step before creating complete infrastructure.
- Added few parameters to azuredeploy template to support migration flow.
- Changes to install_moodle.sh to skip fresh Moodle installation commands. And also added couple of helper functions to update Moodle config settings in the migrated config file.
vibehero100 pushed a commit to vibehero100/Moodle that referenced this pull request Apr 7, 2026
Workload builder service can migrate(lift & shift) Moodle application running on on-premises VMWare infrastructure to Azure. Workload builder service uses ARM templates from this Moodle repo to prepare the infra in Azure. Below changes are made in this repo to support migration flow:

- Added migration specific entry-point/wrapper template which will invoke main template with appropriate parameters.
- Added another wrapper template to create file-share storage account. In migration flow, the Moodle code/config/data will be migration from on-prem to azure file-share as 1st step before creating complete infrastructure.
- Added few parameters to azuredeploy template to support migration flow.
- Changes to install_moodle.sh to skip fresh Moodle installation commands. And also added couple of helper functions to update Moodle config settings in the migrated config file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants