Moodle on VMSS Flex #256
Draft
Moodle on VMSS Flex #256
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added info on SSH key generation
added notes about hardcoded SKUs in the pre-defined templates
small tweak re: SSH key pair requirements for Azure
setup_nfs_ha.sh: Added static port assignments to NFS to allow access through a loadbalancer. Ports 111 (TCP/UDP), 2049 (TCP/UDP), 2000 (TCP/UDP), 2001 (TCP), and 2002 (UDP) are the ports required.
* Reread sysctl tunables for static NFS port setup_nfs_ha.sh: Modified to prevent needing a reboot for static port assignments to take effect. * Increased DRBD resync performance setup_nfs_ha.sh: Edited the DRBD configuration to increase the resync speed. This should decrease the amount of time it takes for the initial sync to complete.
Add highly available NFS option
Fixing Moodle directory permissions
Adding code to deal with nfs type backend storage Signed-off-by: Adrian Joian <[email protected]>
In order to improve overall performance multiple outbound IPs have been added to the ARM templates therefore a switch to the Standard Loadbalancer SKU is required. Signed-off-by: Adrian Joian <[email protected]>
A couple of fixes related to performance and bugs
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.
Using 'Standard' LoadBalancer SKU for migration scenario as well, align to other fresh deployment scenarios.
Migration flow uses assessment based VMSS sku and not all of them support Accelerated Networking. By default, Accelerated Networking will be disabled in migration flow and enabled as per need.
Using a different version of grunt
Move fully configurable deploy to later in the README
naioja
force-pushed
the
master
branch
2 times, most recently
from
5c199d9 to
2afa403
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deploy Moodle components using VMSS Flex: