Hi enrique
Most of your questions would have a "yes" answer :
Actual projets using VMoodle in 1.9 :
- Ministery of Education France : Pairformance Program (35 moodles - full network)
- Université Paris Descartes (Paris V) : 12 Discipline centers + 1 global node
- Rectorat de Strasbourg : 30 High Shools and colleges + 1 federal node, raising 50 moodle in 2012
- Institut IPeria : 14 moodles training
One fo the master trak of VMoodle was actually using full power of MNET concept to split a huge moodle in smaller subsets, but keeping the global system consistance. The origin of the feature was the Pairformance program that was adressing 800.000 registered users splitted into 30 smaller subnodes. Main purpose was to :
- keep the whole platform safe from big joins (users, capabilities, ontexts, etc)
- give an administrative consistance and autonomy of organisation
- save a lot of technical effort by maintaining only one code base for a whole system. (it's real !!)
Actually full SSO and roaming is possible, however adding some small fixes to MNET. We will study the status of Moodle 2 MNET changes to chek if thos points have been resolved, and convert fix strategy appropriately.
This is a real good idea to have a component that could make "federal" answers. There was plan of mine to make a special technical entral hub for that, in order to anwser to questions like :
Where is John right now (on which node) ?
or for centralizing Moodle instant messaging.
These topics were not ordered yet by my stakeholders.
Thes issue in generalizing a peer to peers instant "My course" exploration is of course performance. In big Moodle arrays, you might shoot as many MNET calls as available peers. I tried some kinda architecture on the MNET distributed resource repository for Moodle 1.9 we developped for Intel. In that case (was a n2 omplexity exploration) was the result catastrophic.
If an appropriate strategy of remote enrol using MNET enrol is used, some kinda global course catalog could be displayed to users.
You will have to proceed to a real "topoogy" design to solve macro-architectural behaviours and service policy, but that's fine...
We are starting conversion work right now.