When setting up a generalised MNET network, it must be possible to build mnet links on a large scale between the different tenants.

This tool makes it possible to carry out key exchanges between a tenant (the one on which the tool is applied) and a tenant designated as the target. In a star topology, each secondary tenant should be connected to the main instance. In a “full” topology, each tenant must connect with every other tenant. In so-called “subnetwork” topologies, tenants must connect to all the tenants of their subnetwork and to the main platform, at least for remote administration services.

Note that the service opening structure is defined by the central VMoodle settings, which define the “service map” with respect to the main instance, and the service map “with respect to” the peers of the subnetwork.

Script action:

The script activates the “forced” key exchange between the caller and the target, and proceeds to activate the services of the service map corresponding to the situation.

Running this script resets the key of the tenant on which it is executed if the option

Example:

  \$sudo -u www-data /usr/bin/php local/vmoodle/cli/init_mnet_node.php --host=http://my.virtual.moodle.org --bindhost=http://my.master.moodle.org

To connect all the secondary tenants:

  \$sudo -u www-data /usr/bin/php local/vmoodle/cli/init_mnet_node.php --bindhost=subs

• -b, –bindhost Tenant to connect. (see details below)
• -n, –newkey Renews the local key (startmnet) before the operation.
• -H, –host Runs the command on this vmoodle tenant
• -h, –help Displays help
• -d, –debug Enables debug mode

If BindHost is a vmoodle host definition, then the connection operation connects this host to the main site and to all the hosts belonging to the same vmoodle subnetwork.

If BindHost has the special value “subs”, then the operation connects the main site to the Host host

Back to the technical guide - Back to the component index - Back to the plugins index - Back to the catalogue