Difference between revisions of "Agile testbed"

From PDP/Grid Wiki
Jump to navigationJump to search
Line 15: Line 15:
 
The testbed sports a mixture of older and newer hardware. The flagships are the two blades blade13 and blade14 in Cabinet 08. They have a Fibre Channel interface to the Compellent, on which they share a 1024 GiB multipath block device.
 
The testbed sports a mixture of older and newer hardware. The flagships are the two blades blade13 and blade14 in Cabinet 08. They have a Fibre Channel interface to the Compellent, on which they share a 1024 GiB multipath block device.
  
Two somewhat older machines, arrone and aulnes, have no Fibre Channel interface but they share an iSCSI target on storage.testbed, which is a FreeNAS box with about 2 TB of data.
+
Two somewhat older machines, arrone and aulnes, have no Fibre Channel interface but they share an iSCSI target on storage.testbed, which is a [http://www.freenas.org/ FreeNAS] box with about 2 TB of data.
  
 
These four machines all run [http://www.debian.org/releases/stable/ Debian squeeze] with [http://www.linux-kvm.org/page/Main_Page KVM] for virtualization, managed by [http://libvirt.org/ libvirt].
 
These four machines all run [http://www.debian.org/releases/stable/ Debian squeeze] with [http://www.linux-kvm.org/page/Main_Page KVM] for virtualization, managed by [http://libvirt.org/ libvirt].
  
 
These hosts cannot be accessed directly; they live in a LAN with no inbound connectivity. The management host '''bleek.nikhef.nl''' is the entry point to the entire testbed. It takes care of network address translation (NAT) of the 10.198.0.0/16 range used inside the testbed, resolving hostnames and handing out ip addresses (with dnsmasq), serving home directories, and serving VM installation details such as kickstart files (Red Hat/Fedora) and preseed configuratios (Debian).  
 
These hosts cannot be accessed directly; they live in a LAN with no inbound connectivity. The management host '''bleek.nikhef.nl''' is the entry point to the entire testbed. It takes care of network address translation (NAT) of the 10.198.0.0/16 range used inside the testbed, resolving hostnames and handing out ip addresses (with dnsmasq), serving home directories, and serving VM installation details such as kickstart files (Red Hat/Fedora) and preseed configuratios (Debian).  
 +
 +
Access to bleek.nikhef.nl is restricted to users who have a home directory with their ssh pulic key in ~/.ssh/authorized_keys.
 +
 +
Since all access has to go through bleek, it is convenient to set up ssh to proxy connections to *.testbed through bleek in combination with sharing connections, in ~/.ssh/config:
 +
 +
Host *.testbed
 +
CheckHostIP no
 +
ProxyCommand ssh -q -A bleek.nikhef.nl /usr/bin/nc %h %p 2>/dev/null
 +
Host *.nikhef.nl
 +
ControlMaster auto
 +
ControlPath /tmp/%h-%p-%r.shared
 +
  
 
There are some more machines with an earlier setup using Xen on CentOS 5, but these will be phased out and reinstalled.
 
There are some more machines with an earlier setup using Xen on CentOS 5, but these will be phased out and reinstalled.
Line 66: Line 78:
 
| DHCP,DNS,NFS,LDAP
 
| DHCP,DNS,NFS,LDAP
 
|}
 
|}
 
  
 
== Network ==
 
== Network ==

Revision as of 21:30, 20 February 2013