Difference between revisions of "Agile testbed"

From PDP/Grid Wiki
Jump to navigationJump to search
Line 169: Line 169:
 
  ipmi-oem -h host.ipmi.nikhef.nl -u username -p password dell get-system-info service-tag
 
  ipmi-oem -h host.ipmi.nikhef.nl -u username -p password dell get-system-info service-tag
  
== Accessing the machines ==
+
Most 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].
  
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.
+
See [[NDPF_Node_Functions#P4CTB|the official list]] of machines for the most current view.
  
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.
+
== Accessing the machines ==
  
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].
+
Access to the hardware is either by
 +
# ssh access from within the testbed or
 +
# IPMI Serial-over-LAN
  
There are some more machines with an earlier setup using Xen on CentOS 5, but these will be phased out and reinstalled.
+
The only machine that can be reached from outside the testbed (but still only from within certain networks) is the head node.
 
 
[[NDPF_Node_Functions#P4CTB|The testbed]] currently consists of the following physical machines:
 
bleek, toom, kudde and span.
 
  
  
 
=== The head node ===
 
=== The head node ===
  
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 configurations (Debian).  
+
The testbed lives on 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 configurations (Debian).  
  
 
Access to bleek.nikhef.nl is restricted to users who have a home directory with their ssh pulic key in ~/.ssh/authorized_keys.
 
Access to bleek.nikhef.nl is restricted to users who have a home directory with their ssh pulic key in ~/.ssh/authorized_keys.
Line 202: Line 201:
 
The user identities on bleek are managed in the [[NDPFDirectoryImplementation|Nikhef central LDAP directory]], as is customary on many of the testbed VMs. The home directories are located on bleek and NFS exported to those VMs that wish to use them (but not to the Virtual hosts, who don't need them).
 
The user identities on bleek are managed in the [[NDPFDirectoryImplementation|Nikhef central LDAP directory]], as is customary on many of the testbed VMs. The home directories are located on bleek and NFS exported to those VMs that wish to use them (but not to the Virtual hosts, who don't need them).
  
==== Backup ====
+
== Services running in the testbed ==
 +
 
 +
There is a number of services being maintained in the testbed, most of them running on '''bleek.nikhef.nl'''.
 +
 
 +
=== Backup ===
  
 
The home directories and other precious data on bleek are backed up to Sara with the Tivoli Software Manager system.
 
The home directories and other precious data on bleek are backed up to Sara with the Tivoli Software Manager system.

Revision as of 13:42, 21 February 2013