GridSeed: working notes
GridSeed testbed
The GridSeed main testbed is currently installed at SISSA/Democritos. It consists of several VMs running on hosts:
neon.hpc.sissa.it
gridseed07.env
gridseed08.env
gridseed09.env
gridseed10.env
gridseed11.env
All VMs are currently run and managed with VirtualBox (which see).
GridSeed VMs (up and running)
As of 2010-02-02, the following hosts are up and running:
| Host | Role | IP | Host | Location |
|---|---|---|---|---|
| master | hosts central network services | 10.10.0.1 | neon | /root/.VirtualBox/Machines/master/master.xml |
| ca | CA repository and web interface | alias for master | ||
| voms | "gridseed" VO VOMS server | alias for master | ||
| myproxy | MyProxy server (gLite PX node) | alias for master | ||
| dhcp | DHCP server | alias for master | ||
| dns | DNS server | alias for master | ||
| gateway | router/gateway | alias for master | ||
| central-1 | hosts Grid central services | 10.10.0.2 | gridseed07 | /vmware/central-1/central-1.xml |
| bdii | gLite site-BDII(?) | alias for central-1 | ||
| top-bdii | gLite top-BDII instance | alias for central-1 | ||
| top-lfc | "central" LFC server | alias for central-1 | ||
| lfc | "local" LFC server | alias for central-1 | ||
| wms | gLite WMS | 10.10.0.3 | gridseed07 | /vmware/wms/wms.xml |
| ce-1 | lcg-CE and TORQUE server | 10.10.1.254 | gridseed09 | /vmware/ce-1/ce-1.xml |
| ce-1wn1 | gLite WN for ce-1 | 10.10.1.1 | gridseed09 | /vmware/ce-1wn1/ce-1wn1.xml |
| ce-1wn2 | gLite WN for ce-1 | 10.10.1.2 | gridseed09 | /vmware/ce-1wn2/ce-1wn2.xml |
| se-1 | StoRM SRM server | 10.10.1.253 | gridseed08 | /vmware/se-1/se-1.xml |
| ce-2 | CREAM-CE and TORQUE server | 10.10.2.254 | gridseed10 | /vmware/ce-2/ce-2/ce-2.xml |
| ce-2wn1 | WN for ce-2 | 10.10.2.1 | gridseed10 | /vmware/ce-2wn1/ce-2wn1.xml |
| se-2 | DPM SRM server | 10.10.2.253 | gridseed10 | /vmware/se-2/vbox.xml |
| arc-ce | ARC 0.8.x front-end | 10.10.0.82 | gridseed08 | /vmware/arc-ce.xml |
| ui-1 | gLite + ARC UI | 10.10.0.21 | gridseed08 | /vmware/ui-1/ui-1.xml |
GridSeed VMs (off)
Some other virtual machines exists, but not running ATM:
| Host | Role | IP | Host | Location |
|---|---|---|---|---|
| nagios | EGEE SA1 Nagios server | 10.10.0.9 | neon | /vmware/nagios/nagios.vmx |
| nagios-ui | ??? | (not registered in DNS) | gridseed07 | /vmware/nagios-ui/nagios-ui.vmx |
| ce-3 | lcg-CE and TORQUE server | 10.10.3.254 | gridseed11 | /vmware/ce-3/ce-3.vmx |
| test | fresh SL4 installation(?) | 10.10.0.254 | gridseed10 | /vmware/test/vbox.xml |
| template | clean-up SL4.x installation | 10.10.255.254 | gridseed10 | /vmware/template/vbox.xml |
More hosts are registered in the DNS than actually deployed as VMs.
Template VMs (off)
These VMs should be copied to add a new node to GRIDSEED; instructions to do so are in the NewHost page.
| Host | Role | IP | Host | Location |
|---|---|---|---|---|
| centos5 | fresh CentOS5 install | 10.10.0.253 | neon | /vmware/centos5/ |
| test | fresh SL4 installation(?) | 10.10.0.254 | gridseed10 | /vmware/test/vbox.xml |
| template | clean-up SL4.x installation | 10.10.255.254 | gridseed10 | /vmware/template/vbox.xml |
Questions/FIXME's
- what's the difference between
lfcandtop-lfc? As far as I know, you cannot run two separate LFC instances on one host - why are some Grid services running on
masterand some oncentral-1?
How to...
Connect to the testbed
Complete instructions can be found at: http://doc.escience-lab.org/index.php/Main/SSHtunnel
The procedure of connectiong to neon can be
almost automated with the following one-liner::
alias neon='nc -z localhost 2222 || (ssh democritos.sissa.it -N -L 2222:neon.hpc.sissa.it:22 & \ sleep 4); ssh localhost -t -p 2222 -X'
Connecting directly to master can also be automated with a
one-liner::
alias master='nc -z localhost 2222 || (ssh democritos.sissa.it -N -L 2222:neon.hpc.sissa.it:22 & \ sleep 4); ssh localhost -t -p 2222 -X ssh root@master -X'
List all machines currently registered in DNS
On any GridSeed machine, run the command::
host -t AXFR grid.seed
More hosts are registered in the DNS than actually deployed as VMs, so this command will return a lot of unused usernames.
List all VMs installed, and their running status
The location and status of all GridSeed VMs can be printed with the script::
/opt/gridseed/bin/list-VM
Here is a sample output::
--------- neon --------- running master ************************* gridseedenv ************************* --------- gridseed07--------- running central-1 running wms --------- gridseed08--------- running se-1 running ui-1 --------- gridseed09--------- running ce-1wn2 running ce-1wn1 running ce-1 running ui-2 --------- gridseed10--------- running se-2 running ce-2wn1 off test off template running ce-2 --------- gridseed11--------- running arc_ce off ce-3
List all DNS names currently _up_
On any GridSeed machine, run the command::
host -t AXFR grid.seed \
| cut -d. -f1 \
| grep '^[a-z]' \
| (while read host;
do ping -c 1 -W 1 $host >/dev/null && echo $host;
done)

