Generate VM setup params JSON file using cloud-init #139
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the first step to fixing #79. Currently only the
/var/lib/cloud/instance/moodle_on_azure_configs.jsonfile is generated on the controller and the VMSS VMs. Next step is to use this JSON file in the setup scripts (install_moodle.shandsetup_webserver.sh), replacing all the many cmdline params. Ultimately, we'll update the bash scripts (or migrate to equivalent Python scripts) so that multiple sites can be configured and served, addressing #78.This is just an informational PR. No need to do a thorough review. I confirmed generation of the file through cloud-init on the controller VM and the VMSS VM.