User Tools
local:vmoodle:install
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
local:vmoodle:install [2018/02/21 16:31] admin [Update the main configuration file of Moodle] |
local:vmoodle:install [2023/01/31 16:46] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | <html><!-- nomoodle --></html>{{ :logo-apl.png?nolink |}}<html><!-- /nomoodle --></html> | ||
| ===== VMoodle (local) : Installation===== | ===== VMoodle (local) : Installation===== | ||
| Line 113: | Line 114: | ||
| This key allows remote users to become site administrators of the local moodle. This is forbidden by standard Mnet rules but VMoodle implementation propose patchs to override. | This key allows remote users to become site administrators of the local moodle. This is forbidden by standard Mnet rules but VMoodle implementation propose patchs to override. | ||
| - | ==== Mise en oeuvre du cron virtualisé ==== | + | ==== Cron setup in virtualized environements ==== |
| - | === Mise en place à partir de cron simples === | + | === Using unitary crons for each nodes === |
| - | Un plate-forme Moodle fonctionne avec une tâche cron associée qui effectue tout un ensemble de tâches automatiques et cadencées sur les données de Moodle. | + | A Moodle site has a unique cron task that performs a lot of distinct delayed and scheduled processings in moodle. |
| - | La mise en oeuvre de plates-formes virtualisées nécessite également de mettre en oeuvre ces tâches pour chacune des instances virtuelles qui sont créées dans la virtualisation. | + | A standard way of setting up would setup a cron line for each of the virtual moodle an installation contains. |
| - | En HTTP, vous pouvez enregistrer vos tâches cron sur les domaines d'exploitation propres de vos instances, comme vous le feriez pour des plates-formes standard. Par contre, pour une mise en oeuvre par script serveur utiliser le script standard /admin/cli/cron.php n'est pas possible, car ce type d'appel ne fournit aucune informations permettant au basculement virtuel de se faire. | + | If you use the HTTP method to run crons, f.e. |
| - | Pour obtenir un basculement effectif de l'instance de service, utilisez à la place le script : | + | */10 * * * * wget -O /dev/null -q http://virtual1.mymoodles.edu |
| + | |||
| + | then you can register as many ''wget'' calls pointing all your subdomains, as yo'll do for independant standard moodles. If you use the command line method you will have to run the VMoodle enabled cron script, and tell in the command line for which host you are running the script: | ||
| /local/vmoodle/cli/cron.php --host=http://my_virtual.mymoodledomain.com | /local/vmoodle/cli/cron.php --host=http://my_virtual.mymoodledomain.com | ||
| - | en précisant explicitement la racine wwwroot que vous voulez adresser. | + | You will provide the "official" wwwroot the virtual site is attached to. |
| - | === Utilisation de l'ordonnanceur de cron === | + | === Using the VCron hyper rotator === |
| - | VMoodle fournit en plus un ordonnanceur de cron qui est lancé sur l'installation principale, et est capable de faire "tourner" automatiquement le déclenchement des crons virtuels de toutes les instances. Vous pouvez utiliser ce script en mode HTTP ou en mode script : | + | The VMoodle implementation provides a vcron scheduler that will be lauched in the master moodle host context, and will automatically rotate and schedule all submoodle crons. VCron scheduler can operate using HTTP calls or command line execs (internally configured) and can itself be invoked through HTTP: |
| wget http://main.mymoodledomain.com/local/vmoodle/vcron.php | wget http://main.mymoodledomain.com/local/vmoodle/vcron.php | ||
| - | ou | + | or in command line |
| sudo -uwww-data php /root/to/moodle/local/vmoodle/cli/vcron.php | sudo -uwww-data php /root/to/moodle/local/vmoodle/cli/vcron.php | ||
| - | La fréquence de rotation de l'ordonnanceur de cron doit être très rapide afin de permettre que chaque site virtuel soit activé suffisamment souvent. | + | You may internally configure the vcron settings to raise the number of virtual moodle processed per cron run. |
| + | the basic calculation for vcron rotation is : | ||
| - | ---- | + | With a "run per turn" of 1 and 20 virtual moodles and a cron period of 1 minute per turn, each vmoodle will be processed once per 20 minutes. Raising the "run per turn" to 2 will divided the effective cron period to 10 minutes per vmoodle instance. |
| + | For very large moodle arrays, it may be worth having a separated machine to process the crons for all the moodle instances. Cron processes may ovelap one on each other, but will not pull down theusual user's page distribution too much. | ||
| + | |||
| + | A very advanced feature (undocumented here) allow to distribute the vcron scheduling on several clusters. | ||
| + | |||
| + | ---- | ||
| <html><!-- nomoodle --></html> | <html><!-- nomoodle --></html> | ||
local/vmoodle/install.1519227063.txt.gz · Last modified: 2024/04/04 15:50 (external edit)
