VMoodle

There is no case where a child site should be down relatively to a master. The case could be that a child site has been disabled from VMoodle registery, in case it will just answer "This VMoodle is not resolved or is fake". This would not affect any other site. Just think ther is only one moodle physically running, one apache, one mysql (or several as you may spread the databases upon distinct DB backends).

I have an interesting question, What will happen if one of the child site is down? Will that cause problem to the other children site or even the master site? Is each site quarantined from the other sites?

Is planned version for Moodle 2.9 ?

there should not be any trouble in child site login as far as accounts are using the same salt for all submoodles. What you just need to check is that the virtualized moodledata root dir has correct access permissions. This assumes that your top Moodledata container is able to give at least group access to all the moodledata. Usually this is what happens when VMoodle creates the moodle data directory using the "test Moodledata" knob. VMoodlized child moodle behave just as any moodle except the master $CFG values have beed shifted BEFORE starting setup.php....

everything is working fine except login section .... our user not able to login in child moodle site ... is this salt issue or lib/setuplib.php file mention in config.php file (in child moodle) ... if possible please provide config.php file example (child moodle site)

Certaintly John,
applying your modification, now it returns "Connection is OK"

I encountered the same error as stated by Jaime.
To fix it, you need to modify this file: /moodle/blocks/vmoodle/views/management.testcnx.php
just add the parameter type for each requiring parameters
$database->vdbtype = required_param('vdbtype', PARAM_RAW);
$database->vdbhost = required_param('vdbhost', PARAM_RAW);
$database->vdblogin = required_param('vdblogin', PARAM_RAW);
$database->vdbpass = required_param('vdbpass', PARAM_RAW);

I've installed vmoodle block for 2.4 on a moodle2.5
and above error is displayed pressing the "database connection test" button

creating a virtual clone on moodle2.5 I get this error:
Home
Coding error detected, it must be fixed by a programmer: required_param() requires $parname and $type to be specified (parameter: vdbtype)

Hi Tabea,
You need to make sure that in the admin settings the MySQLdump path is set properly.
The message you get indicates the Mysqldump executable is not in its default location, you may refere to your system administrator for the exact path .
best regards
Wafa

Hello,
I installed the plugin on Moodle 2.5+. Seems to be fine. But when making the Snapshot Moodle Master Step 1 I get following message: 'Database dump command /usr/bin/mysqldump does not match any executable' - what ca I do?
Cheers. Tabea

Hi Aparup
It seems i have a persistant trouble with this package as package info form gets empty (need sto hand fill field) and AMOS warning is raised... Are there any new rules for packaging i need to know ?
Cheers
Valery.

Hi Valery,
I was looking at your VMoodle block and I noticed that the English language strings are not available for translation at AMOS, which most likely means that there is something not quite right in the plugin code. I think you might want to contact David Mudrak about this.
In the meantime, I downloaded the files and I hope I will have the spanish translation of the English strings in a few days.
I also checked the documentation page at http://docs.moodle.org/23/en/VMoodle_Block, added a link to the spanish translation for the 2.3 page version (which seems to be newer than the 2.4 version), and corrected a couple of minor English typos, all of which you can see in the history tab of the page.
Thanks again for a very promising add-on for large Moodle sites (such as my University).

I tracked the MDL-34632 discussion : i think it would NOT solve this very special case : extra config scripts would probably be considered during the setup phase, as Petr says it would be eventually agreed such a possibility once the system has run at least basic setup (in which database and moodledata attachement). VMoodle needs to work even before, as shifts the complete working environment.
About the question of making a local plugin : anyway needs VMoodle be monitored and operated from somewhere, thus a block was interesting to give at least an accesspoint to backoffice. Maybe the local plugin could now add adequate Admin links to do it... yeah that seems a good idea indeed, as the position of this bloc in the GUI was not so pretty.... i'll take some time ASAP to consider this architecture shift.

Hi Valery,
i've moved this into the 'Other' category as this plugin cannot be installed easily by an automated system.
Perhaps if we can work on MDL-34632 sometime we won't need patching to config.php but can instead use a callback as a hook (if not events).
I think a video showing how this is/was used will be really useful in the long description here for anyone looking at this as it can seem complicated.
In future it would be great if this was transformed into a local plugin using those events/hooks etc.