Difference between revisions of "VMoodle Block"

Jump to: navigation, search
(Created page with "{{Moodle 2.3}} VMoodle is a non standard infrastructure embedded within a Moodle block. It provides technical toolset to deploy and manage a set of virtualized Moodles from a si...")
 
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Moodle 2.3}}
+
'''IMPORTANT NOTE : From version 2.8 and upper, the core implementation of VMoodle block is now handled by the local VMoodle plugin, in order to lower the core footprint of the installation. This documentation is subject to revision.'''
  
VMoodle is a non standard infrastructure embedded within a Moodle block. It provides technical toolset to deploy and manage a set of virtualized Moodles from a single codebase. All virtualized moodles will run their own instance independantely one from each other, or according themselves in building a Moodle Network cooperation strategy.  
+
See [[VMoodle_Local|VMoodle local plugin]] for actualized documentation.
  
This work is the result of a couple of years of developement with the participation of Intel Corp.
+
VMoodle is a non standard infrastructure embedded within a Moodle block. It provides a technical toolset to deploy and manage a set of virtualized Moodles from a single codebase. All virtualized moodles will run their own instance independently from each other, or according themselves in building a Moodle Network cooperation strategy.  
  
One of the key effect of using VMoodling virtualisation is that maintenance of multiple Moodle running with similar equipement get much easyer and saves a lot of time.
+
This work is the result of a couple of years of development with the participation of Intel Corp.
  
Moodle virtualisation process is achieved using a dynamic configuration definition, stored in a Moodle moodle instance so called "master instance". Virtualising such configuration allows dynamic switching of database and moodledata context when entering a Moodle page.  
+
One of the key effect of using VMoodling virtualisation is that maintenance of multiple Moodle running with similar equipment gets much easier and saves a lot of time.
  
As was mentioned above, all the Moodle clones are completely independant and WILL NOT share any data. Using many instances with an adequate MNET strategy allows making string and powerfull distributed Moodle configuration aiming at huge organisations.
+
Moodle virtualisation process is achieved using a dynamic configuration definition, stored in a Moodle instance called "master instance". Virtualising such configuration allows dynamic switching of database and moodledata context when entering a Moodle page.
 +
 
 +
As was mentioned above, all the Moodle clones are completely independent and WILL NOT share any data. Using many instances with an adequate [[MNet]] strategy allows for the making of strong and powerful distributed Moodle configurations, aimed at large organizations.
  
 
==Installation==
 
==Installation==
 +
  
 
===Compatibility===
 
===Compatibility===
  
VMoodle supports now MySQL databases and (less tested) PostGre.
+
VMoodle supports now [[MySQL]] databases and (less tested) [[PostgreSQL]].
  
Note that Moodle do not support PostGre schemas at install time.
+
Note that Moodle do not support PostGres schemas at install time.
  
 
===Prerequisites===
 
===Prerequisites===
  
The VMoodle blocks provides a complete and complex virtualisation process for Moodles and a set of network level administration capabilities. For the block running properly, some non standard features of Moodle must be obtained. These are not numerous and easy to patch within a standard 1.9 codebase.
+
The VMoodle plugin set provides a complete and complex virtualisation process for Moodles and a set of network level administration capabilities. For the block running properly, compared to the original version in Moodle 1.9, Moodle 2 version of Moodle will need less core changes to operate in full feature range.
  
* The VMoodle bloc uses extensively block bound XMLRPC calls. Standard Moodle DO NOT provide support for block level XMLRPC. [http://tracker.moodle.org/browse/MDL-23194]. This point is still under discussion for 1.9 old codebase, and being resolved in Moodle 2.0.
+
The VMoodle plugin set uses two components :  
* The block is extensible, i.e. provides some parts that admit sub-plugins (typically like the resource module, but resource handling is done by standard code). Sub-plugins are supported in modules, but not in blocks. Moodle.org WILL NOT soluce this requirement. [http://tracker.moodle.org/browse/MDL-20378]
 
* VMoodle based networks in a virtualisation configuration are intended to build coherent distributed platforms within an institutional environement. Urbanisation of such systems will often take some benefit of using extensively XMLRPC interactions between nodes for enhancing the distributed consistance. Standard Moodle codebase ensures MNET keys are renewed when a user jumps from a node to a remote node, but key ARE NOT renewed automatically when coming to obsolescence. The effect is that after a key has gone away, all services based on XMLRPC will be broken untill key exchange has not been restored again. The VMoodle block provides an "automatic MNET key rotation" enhancement that  fixes this situation. [http://tracker.moodle.org/browse/MDL-23195]
 
  
VMoodle distribution is provided with adequate patchs for all these requirements.
+
* the VMoodle block (this block) : Is used to provide access to the VMoodle management.
 +
* the VMoodle Local component : provides all the backoffice and implementation for VMoodling.
  
IMPORTANT NOTE : On Mysql, VMoodle provides Moodle instance capturing for making deployement templates. This assumes the master Moodle controlling deployments need having a Myslq user that has DATABASE CREATE permission.
+
==== Special MNET reinforcement ====
  
===Block Installation===
+
VMoodle based networks in a virtualisation configuration are intended to build coherent distributed platforms within an institutional environment. Urbanisation of such systems will often take some benefit of using extensively [https://docs.moodle.org/23/en/admin/environment/php_extension/xmlrpc XMLRPC] interactions between nodes for enhancing the distributed consistence. Standard Moodle codebase ensures [[MNet]] keys are renewed when a user jumps from a node to a remote node, but key ARE NOT renewed automatically when coming to obsolescence. The effect is that after a key has gone away, all services based on [https://docs.moodle.org/23/en/admin/environment/php_extension/xmlrpc XMLRPC] will be broken until key exchange has not been restored again. The VMoodle block provides an "automatic [[MNet]] key rotation" enhancement that  fixes this situation. [http://tracker.moodle.org/browse/MDL-23195]. This point is not resolved in Moodle 2.0 architecture and still needs a patch in the [[MNet]] core library.
  
VMoodle block will install just as a usual Moodle block. Subplugins patch can be installed later, causing sub-plugins to be installed in a second stage :
+
VMoodle distribution is provided with adequate patches for this requirement.
  
# Unzip the block code in the "blocks" folder of your Moodle install.
+
IMPORTANT NOTE : On [[MySQL]], VMoodle provides Moodle instance capturing for making deployment templates. This assumes the master Moodle controlling deployments needs having a [[MySQL]] user that has DATABASE CREATE permission.
# Trigger the administraton/notification menu.
 
  
==VMoodle Block Features==
+
===Block Installation (quick install)===
  
===Features Adressing the "Moodle Factory" Administration===
+
First install the [[VMoodle_Local|local VMoodle component]]
  
* Virtualisation Hook for the standard 'config.php' file
+
VMoodle block will install just as a usual Moodle [[Blocks|block]].
* Deployment of new instances from within the Master instance administration
 
* Moodle snapshot to create platform templates for further deployment
 
* On demand Moodle deployment
 
* Deployement of virtualized Moodle within a Moodle Network strategy
 
  
===Features Adressing the "MNetwork Level Administration"===
+
# Unzip the block code in the "blocks" folder of your Moodle install.
 
+
# Trigger the administration/notification menu.
Multiplying instances will ever raise issues of administration because increasing the amount of information to be managed and complexity of the system. The VMoodle block provides a super-administration toolset allowing distributing administration commands across a Moodle Network so getting things faster even when the number of Moodle gets quite high. This administration layer provides a command framework for extensibility.
 
 
 
* SQL orders can be distributed on all managed nodes
 
* Role comparison and sync between many nodes
 
* Capability resync between many nodes
 
* Massive upgrade of all nodes when upgrading or installing new plugins.
 
 
 
====Access to Mnetwork Level Administration====
 
 
 
You may access to the MNET level administration clicking on the link "Administrate" showing in the footer of the "VMoodle" bloc instance.
 
 
 
Three subservices are available :
 
 
 
* [[Moodle Instance Management|Managing virtual instances and deployment]] : lists nodes and allows enabling, disabling snapshoting and deleting a node, ...
 
* [[Super-administration|Super-administration]] : a set of primitives that can be processed simultaneously on distributed Moodles.
 
* [[MNET Service Template|MNET Services Template]] : A form to define a template or MNET services settings to be applyed as a default to any new Moodle clone.
 
  
 
==See Also==
 
==See Also==
Line 71: Line 52:
  
  
 +
[[es:Bloque VMoodle]]
 
[[fr:VMoodle]]
 
[[fr:VMoodle]]
 +
[[Category:Contributed code]]

Latest revision as of 12:56, 18 June 2016

IMPORTANT NOTE : From version 2.8 and upper, the core implementation of VMoodle block is now handled by the local VMoodle plugin, in order to lower the core footprint of the installation. This documentation is subject to revision.

See VMoodle local plugin for actualized documentation.

VMoodle is a non standard infrastructure embedded within a Moodle block. It provides a technical toolset to deploy and manage a set of virtualized Moodles from a single codebase. All virtualized moodles will run their own instance independently from each other, or according themselves in building a Moodle Network cooperation strategy.

This work is the result of a couple of years of development with the participation of Intel Corp.

One of the key effect of using VMoodling virtualisation is that maintenance of multiple Moodle running with similar equipment gets much easier and saves a lot of time.

Moodle virtualisation process is achieved using a dynamic configuration definition, stored in a Moodle instance called "master instance". Virtualising such configuration allows dynamic switching of database and moodledata context when entering a Moodle page.

As was mentioned above, all the Moodle clones are completely independent and WILL NOT share any data. Using many instances with an adequate MNet strategy allows for the making of strong and powerful distributed Moodle configurations, aimed at large organizations.

Installation

Compatibility

VMoodle supports now MySQL databases and (less tested) PostgreSQL.

Note that Moodle do not support PostGres schemas at install time.

Prerequisites

The VMoodle plugin set provides a complete and complex virtualisation process for Moodles and a set of network level administration capabilities. For the block running properly, compared to the original version in Moodle 1.9, Moodle 2 version of Moodle will need less core changes to operate in full feature range.

The VMoodle plugin set uses two components :

  • the VMoodle block (this block) : Is used to provide access to the VMoodle management.
  • the VMoodle Local component : provides all the backoffice and implementation for VMoodling.

Special MNET reinforcement

VMoodle based networks in a virtualisation configuration are intended to build coherent distributed platforms within an institutional environment. Urbanisation of such systems will often take some benefit of using extensively XMLRPC interactions between nodes for enhancing the distributed consistence. Standard Moodle codebase ensures MNet keys are renewed when a user jumps from a node to a remote node, but key ARE NOT renewed automatically when coming to obsolescence. The effect is that after a key has gone away, all services based on XMLRPC will be broken until key exchange has not been restored again. The VMoodle block provides an "automatic MNet key rotation" enhancement that fixes this situation. [1]. This point is not resolved in Moodle 2.0 architecture and still needs a patch in the MNet core library.

VMoodle distribution is provided with adequate patches for this requirement.

IMPORTANT NOTE : On MySQL, VMoodle provides Moodle instance capturing for making deployment templates. This assumes the master Moodle controlling deployments needs having a MySQL user that has DATABASE CREATE permission.

Block Installation (quick install)

First install the local VMoodle component

VMoodle block will install just as a usual Moodle block.

  1. Unzip the block code in the "blocks" folder of your Moodle install.
  2. Trigger the administration/notification menu.

See Also

VMoodle Virtualization block Modules and Plugins database entry.