you should get a shell in osconsole, from there you can ssh into
any machines that we have
currently we have voslab3 through voslab17 and voslab23
please login as vosluser, and not as root unless you have to.
Sudo is already set up on those machines to allow vosluser to have
become root.
you can ssh as vosluser between our voslab machines, public keys
have already been set up.
The current set up of voslab:
Integrator/console machine=voslab4
Validator machine = voslab23
Apache servers = voslab6,voslab7
Tomcat servers = voslab8, volab9
mysql =
voslab10
lvs
=voslab5
The machines voslab10-17 hasn't been set up
Starting the services:
Before starting the services, you need to start up the mendosus
infrastructure. Go to voslab4, the console machine. Go to
/home/vosluser/projects/vivo/scripts and do "./vivo stop" to stop the
vivo if it's running. "./vivo start" to start up the infrastructure.
"./vivo operator &" to bring up the operator console.
Bring up lvs if you want to use lvs. Go to
/home/vosluser/projects/vivo/scripts and do "./lvs.up" to bring up the
lvs, and "lvs.down" to bring down lvs.
Starting up services seperately. Go to
/home/vosluser/projects/vivo/multi-tier/rubis/scripts/ ,you can find
different scripts to start up mysql,tomcat, and web servers. To run the
scripts you need to be in the directory one above the scripts, because
it needs to read the rubis.properties file.
After starting up the services, you can verify by pointing a
browser to apache servers if you're not using lvs, and point to lvs
machine if you are using lvs. Firefox is install on voslab4, and lynx
is on almost all the machines.
Starting up experiments: In the same script directory, there are
two scripts run_val.pl and run_no_val.pl to start up a set of
experiments, one is a validation version, the other one is non
validation. These scripts restart or start up the services and the
CLIENTS workload. There're two versions of clients, with lvs or without
lvs, you can specify it in the rubis.properties file with the client
command.