Niclas Hedhman wrote:
Gang,
I was a bit tired of the Http Facility so I moved on to looking at a Console facility. The idea is to allow for a telnet interface into Merlin's internals, so that we can do stuff like;
* Hot-deploy of blocks.
* Reloading of containers with new classes
* Check security settings.
* Restart Merlin remotely.
* Remote troubleshooting
And what else we may come up with.
Currently though, I have only implemented
* List which threads are running. * Traversal of the model * List children in a 'node' of the model (like 'dir') * Print out the entire structure under a node. * Plus 'login', 'dummy', 'echo' and 'help'
This can either be deployed as a normal facility, or inside the Kernel root container, which allows any part of the application container to be fully manipulated.
The code so far exists in planet/facilities/console, and the interesting stuff is in the commands/ project.
If you want to try, check out the code, and go to planet/facilities/console, and run;
ant
then start merlin;
merlin blocks/default/target/deliverables/blocks/avalon-console-default-SNAPSHOT.block
Login into it via telnet localhost 3333
and the password is yabadabadoo
make sure the interface connects to localhost only or sysadms will scream about having non-crypted ports open.
I personally think that a simple CLI would be a much more friendly way to do stuff, mysqladmin style as sysadmins trust SSH more than anything else.
-- Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
