================= Moodle deployment ================= Responsibilities ================ * Linux sysadmins operate the server hardware, the Linux host system and all components within the Linux container * Luca Boesch manages the Moodle application. .. * Linux sysadmins are the gatekeeper for any modifications on Moodle (hardware, software, application). Linux updates ============= Linux system updates and upgrades are done by the Linux sysadmins in line with the normal procedure used for all other Linux systems. Moodle updates ============== Updates of the moodle application are done by Luca Boesch. .. Regular updates --------------- Regular updates are typically small updates: * to the Moodle application through the Moodle git repository or any of its submodules * any change of configuration to the Linux container (e.g. package selection or package configuration) Regular updates are deployed once per week with the following procedure: * Luca sends pull requests, if any, every week by email to its-moodle-webadmin@lists.bfh.ch until Tuesday 11:00. * Pull requests are done from from moodle-bsl3:bfh branch to moodle.bfh.ch:bfh. * The moodle-bsl3:bfh must be fast-forward to moodle.bfh.ch:bfh, contain atomic commits with proper commit message and signed-off lines only. * Proposed commits for merging must be tested before sending the pull requuest by Luca on moodle-test.bfh.ch with a snapshot of the database of the same day of the pull request. * Linux sysadmins will check the commits to be pulled. * If the commits are ok, the Linux sysadmins will merge and deploy the commits on moodle.bfh.ch on Tuesday, 12:00. * If the commits are not ok, the Linux Sysadmins will provide a reasoning until Tuesday, 12:00 and Luca has time to correct them until the next deployment window on Tuesday, 11:00 in the following week (by submitting a new pull request). * There is no re-check for same-day deployment. Any updates to the moodle upstream branch (and subsequent merging to the moodle branch) are done by the Linux sysadmins upon request by Luca. Emergency Updates ----------------- Emergency updates are updates where: * a commit fixes a critical security problem. * a commit fixes a regression of an important feature with a major impact on the user base. By definition all updates are non-emergency updates and follow the regular update procedure, unless at least either one of the two reasons above are fulfilled. Emergency updates are handled like regular updates, except that the Linux sysadmins will respond to the pull request from Luca with an out-of-schedule check, merge, and deploy of commits at the earliest possible time. Note: Moodle point releases (e.g. 3.4.x to 3.4.x+1) are not considered a security update and follow the regular update procedure. Major Upgrades -------------- Moodle major releases (e.g. 3.x to 3.x+1) are considered major upgrades and follow an extensive upgrade planning (involving coordination with Moodle super users) and require automated tests (selenium etc.). Further details are to be documented here. raw:: html — Daniel Baumann Tue Aug 22 11:30:58 2017 +0200