Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
public:lofar_cluster [2009-11-06 11:46] – grit | public:lofar_cluster [2020-10-20 14:16] (current) – Bernard Asabere | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== The LOFAR Cluster | + | ====== The LOFAR Clusters |
- | This page describes the LOFAR cluster | + | This page describes the LOFAR clusters |
- | We welcome authorized users on this cluster. For the time being the users are bound to only a part of the cluster. This part is called a subcluster. Various users groups have been granted access to a specific subcluster. Users can utilized a standard login environment (see below) and they can access the cluster resources using one of the two frontends " | + | We welcome authorized users on the LOFAR clusters. |
- | ===== LOFAR Cluster layout (brief) | + | ===== CEP3 ===== |
- | The Lofar cluster is devided into 8 subclusters. Each subcluster is a processing | + | CEP3 is the processing |
+ | ===== CEP4 ===== | ||
+ | CEP4 is the main storage and processing cluster for online applications. It is not accessible by other users than LOFAR staff. Information on CEP4 can be found [[: | ||
- | ==== Frontend | + | ===== User Access ===== |
- | A frontend has 2 Intel Xeon L5420 quad core processors, 16GB internal meomory, 2 GbE interfaces and 2TB disks in RAID5 configuration. | + | ==== Access through portal |
- | There are actually two identical frontends: '' | + | |
- | ==== Processing units ==== | + | You can access the Lofar cluster through the portal. On your own system, try: |
+ | < | ||
+ | > ssh -X portal.lofar.eu | ||
- | The compute elements have 2 Intel Xeon L5420 quad core processors, 16GB internal meomory, 2 GbE interfaces and 1TB disks in RAID0 configuration. They can be accessed by secure shell and they are grouped. | + | </ |
+ | to connect. We maintain a ssh whitelist, so only registered institutes are able to login. Please send an email to //grit at astron.nl// or //rbokhorst at astron.nl// to add your institute or personal IP number to this white list. When you are logged in for the first time, you'll have an empty home directory. | ||
- | ==== Storage Units ==== | + | To get onto the CEP3 cluster, you first have to login to the frontend node '' |
- | The storage nodes are HP DL180G5 boxes, having 2 Intel Xeon L5420 quad core processors, 16GB internal memory, 6 GbE network interfaces and 24TB disks. | + | For more sophisticated useage |
- | The disks are devided into 4 partitions | + | |
- | + | ||
- | ===== Available Subclusters ===== | + | |
- | + | ||
- | The current subcluster assignment is: | + | |
- | + | ||
- | lfe001: | + | |
- | + | ||
- | This script shows the subcluster definitions | + | |
- | + | ||
- | sub lce-nodes | + | |
- | ==== ========= | + | |
- | sub1 lce001-lce009 | + | |
- | sub2 lce010-lce018 | + | |
- | sub3 lce019-lce027 | + | |
- | sub4 lce028-lce036 | + | |
- | sub5 lce037-lce045 | + | |
- | sub6 lce046-lce054 | + | |
- | sub7 lce055-lce063 | + | |
- | sub8 lce064-lce072 | + | |
- | + | ||
- | The lce-nodes ar ethe compute/ | + | |
- | + | ||
- | ===== User Access ===== | + | |
- | + | ||
- | ==== Access through portal to Cluster frontend ==== | + | |
- | + | ||
- | + | ||
- | You can access the Lofar cluster through the portal: "**ssh -X portal.lofar.eu**" | + | |
- | We maintain a ssh whitelist, so only known institutes are able to login. | + | |
- | Please send an email to grit at astron.nl or h.paas at rug.nl to add your institute or personal IP number. | + | |
- | Once logged in, you'll find an empty home directory. You'll have to login at one of the two frontends " | + | |
==== LOGIN environment ==== | ==== LOGIN environment ==== | ||
- | See [[public: | + | See [[:public: |
==== Do and Don'ts ==== | ==== Do and Don'ts ==== | ||
**DON' | **DON' | ||
- | * Store data on the '' | + | |
- | * Pump around large amounts of data | + | * :!: Store data in your '' |
+ | * Pump around large amounts of data between nodes. | ||
* Leave unused data on the systems. Clean it up, so others can make use of the available disk space. | * Leave unused data on the systems. Clean it up, so others can make use of the available disk space. | ||
- | | + | |
**DO:** | **DO:** | ||
+ | |||
* Help improve the system by sending suggestions for improvements or new packages to the administrators | * Help improve the system by sending suggestions for improvements or new packages to the administrators | ||
- | |||
- | |||
- | ===== Old Stuff ===== | ||
- | |||
- | ===== The lioffen processing cluster ===== | ||
- | |||
- | |||
- | ==== Hardware setup ==== | ||
- | |||
- | The 10-node post processing cluster has '' | ||
- | |||
- | Each node has 2-Gbyte of physical RAM, and another 2-Gbyte swap space. Each node contains two AMD Opteron 2-GHz CPUs with 1 Mbyte cache. They are currently running Ubuntu 7.10 (Gutsy). | ||
- | |||
- | ==== Usage ==== | ||
- | |||
- | The offline nodes are used for processing the CS1 data products that are stored on the lifs-nodes. To this purpose, all disks of all lifs-nodes are NFS mounted on all offline nodes. | ||
- | |||
- | |||
- | ==== Environment | ||
- | |||
- | There is a login environment with some startup-scripts that make it easier to use several available tools. Please see [[public: | ||
- | |||
- | |||
- | |||
- | |||
- | ==== Disks and NFS mounts | ||
- | |||
- | The big disks on the off-line storage nodes ('' | ||
- | |||
- | On each node is a 360 Gbyte ''/ | ||
- | |||
- | Finally, there is the NFS mounted ''/ | ||
- | |||
- | |||
- | ==== Applications | ||
- | |||
- | Most applications can be found in directory ''/ | ||
- | * See [[public: | ||
- | |||
- | ===== listfen 32-bit cluster ===== | ||
- | |||
- | The old 32 bit offline cluster has been removed. Only frontend " | ||
- | |||
- | ==== LIFS storage nodes ==== | ||
- | |||
- | There are 12 old 1TB storage nodes, lifs001 till lifs012. They are still in use for development and testing. Lifs001 till lifs008 are used by the Observatory to store recent observations. Lifs009 til lifs012 hold datasets that are a result of some kind of processing. We are already observing with the new cluster hardware. The lifs nodes will be removed the end of November. | ||
- | |||
- | |||
- | |||
- | |||
- | ==== Offline processing clusters ==== | ||
- | |||
- | The disks of the offline storage nodes are NFS mounted on all these offline nodes. These systems are in use for offline processing (i.e. when data has been transfered from the central storage facility). | ||
- | |||
- | |||
- | ==== Offline storage cluster ==== | ||
- | |||
- | This cluster acts as a temporary data buffer. Data is copied from the online storage systems to these systems, so that the online systems can be used to store new data. These systems are accessable from the offline processing clusters, allowing post-processing of the data. | ||
- | More information can be found [[databuffercluster|on this page]]. | ||
- | |||
- | ====== Bootleg mechanism ====== | ||
- | |||
- | The new cluster is subject to the “bootleg” deployment regime. This service and installation facility was developed by Harm Paas of the CIT department of the RUG University in Groningen. He already had many years of experience with this system at the Computer Science Faculty. One server in the CEP domain is capable of installing many cluster nodes at once in less than 10 minutes. The administration of all nodes is done on this single Bootleg server. | ||
- | |||
- | The way the CEP cluster has been set up is as follows: | ||
- | We are using Ubuntu Linux LTS-8.04 as Operating System within the whole cluster. Bootleg takes care of all of the server management in the cluster by creating new images, administering servers, keeping track of updates and correct start up of servers by sending them new images when it finds outdated versions at boot time. | ||
- | |||
- | Bootleg also administers machine profiles: Depending on the function of the server in the cluster it needs other settings and profiles. | ||
- | This management strategy implies that we have to keep track of all programs installed in the Linux system itself, so we will be able to add them to the image. We plan to build fresh images every month (at the maintenance days). | ||
- | |||
- | We are also able to respond quickly on extra-program demands for system programs. Within bootleg there is a mechanism to roll-out extra programs through the cluster from a central administration point (CAP). | ||
- | |||
- | From the CAP we order to deploy a program or a settings-change and after | ||
- | 1 minute the whole cluster will be updated with the change. | ||
- | So if you need extra system programs, simply ask, and you get it almost instantly on every server in the cluster! | ||
- | |||
- | For an application program change or addition there is another method. | ||
- | Of course you develop your programs in your own user space and/or svn repositories. So you have completely control over all of this. | ||
- | Program releases for the cluster itself reside on a central disk. | ||
- | Normally we (as system administrators) are not involved in the application program deployment. | ||
- | Only if a completely new package is added under a new directory name we | ||
- | need to make this available in the cluster by connecting it in the O.S. | ||
- | via a link to the newly created package name. | ||
- | So there is a clear interface between system programs and applications: | ||
- | The connection between them is at a well defined point, the /opt directory is intended for this. | ||
- | The same goes for database content (mysql, postgresql, ...) . | ||
- | Although it might involve OS program installation and services, the database content itself will never be on the Linux system image but stored on a separate data server. | ||
- | Again: Simply ask, we can connect your program and make it available cluster-wide. | + | ===== Contributed Software ===== |
+ | Some groups or people would like their favourite tools or pipelines added to the cluster software. That can usually be accomodated, | ||