1 / 15

LCG-1 Deployment and usage experience

Explore deployment and usage experience of LCG software at SINP MSU, covering architecture, installation systems, PC clusters, and future plans.

millermary
Download Presentation

LCG-1 Deployment and usage experience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LCG-1 Deployment and usage experience Lev Shamardin SINP MSU, Moscow shamardin@theory.sinp.msu.ru

  2. LCG Geography • LCG covers a number of sites both in Europe and US • LCG-1 testbed covers 13 sites including SINP MSU Lev Shamardin

  3. LCG-1 • LCG-1 is the production version of the LCG software which is now installed on the 13 LCG-1 sites and running in production mode • New LCG-2 is expected in production in November Lev Shamardin

  4. LCG-1 Architecture • Minimal LCG-1 site must have a Computing Element with worker nodes and a Storage Element • There are no limitations to the number of other components installed on each site • These components do not have to be registered in LCG-1 LCG-1 site MDS west RB MDS east LCG-1 site LCG-1 site Lev Shamardin

  5. LCG-1 Architecture • Current version LCG-1 is based on the EDG middleware with MDS information system • R-GMA is not yet stable enough for the production usage • LCG-2 will be using new R-GMA information system Lev Shamardin

  6. LCFGng and LCG-1 deployment • The base middleware LCFGng configuration profiles are stored in the central LCG CVS repository • Sites create their own site-specific profiles based on the CVS configuration • No manual installation supported yet Lev Shamardin

  7. SINP MSU PC Farm non-interactive nodes • 20 dual-CPU PIII nodes • Two 1.2 TB fileservers • Gigabit Ethernet uplinks to the fileservers • Fast Ethernet links to the nodes PC Farm batch master node switch Storage Storage Lev Shamardin

  8. Software installation system on SINP MSU PC Farm • Based on Etherboot network boot package • Nodes are installed with anaconda kickstart • Nodes without a boot ROM are installed using a fake linux “kernel” or a boot disk • Supports both completely unattended automatic installation and manual installation configuration server node DHCP TFTP NFS file server Lev Shamardin

  9. LCFGng support on SINP MSU PC Farm • LCFGng server was installed for configuring and installing LCG-1 nodes • LCFGng enabled nodes configuration is controlled from the LCFGng server • Nodes configuration and health status information provided with LCFGng components can be observed on the web configuration server node DHCP TFTP LCFG, HTTP NFS file server LCFGng server Lev Shamardin

  10. non-interactive nodes PC Farm batch master node LCG-1 switch Storage Storage Current LCG-1 status in SINP MSU • For the LCG-1 testbed part of the PC Farm was configured as LCG-1 nodes • These nodes are logically disconnected from the main farm • Installed LCG-1 components are: Computing Element with several Worker Nodes, Storage Element, Resource Broker, BDII and User Interface • MyProxy and MDS servers are coming soon Lev Shamardin

  11. MSU PC Clusters • LCG middleware installation on the SRCC MSU (Scientific Research Computing Center) parallel cluster • Site specifics: • Exotic batch system. Interface for the globus package is ready but was not completely tested • Only manual node configuration can be done • Middleware for the worker nodes must be installed on the shared filesystem • Connect the Physical faculty and the faculty of Computing Mathematics and Cybernetics clusters to the SINP MSU Resource Broker • Experience with SRCC is required, similar site-specific limitations Lev Shamardin

  12. Conclusion • What difficulties will emerge if a site wants to install the LCG middleware • What LCG can give you right now • Future plans Lev Shamardin

  13. Difficulties • At the moment the only documented way to install LCG software requires using the LCFGng configuration server • Using LCFGng is not possible in a number of cases, in general due to the administrative reasons • Minimal stand-alone site must be running quite a big number of nodes supporting the infrastructure • The minimal set is: • Resource Broker • BDII & MDS • Computing Element with Worker Nodes • Storage Element(s) • MyProxy if long-time jobs support is required • This gives us at least 5 nodes will be supporting the infrastructure Lev Shamardin

  14. What LCG-1 can give you right now • Convenient way for job balancing between several sites • Common way of user authentication and authorization for job submission • Some basic accounting • Data replication Lev Shamardin

  15. Future plans • SINP MSU Site is one of the sites participating in the LCG-1 • New Russian sites will be connected to the SINP MSU Resource Broker in the nearest future • IHEP Protvino will be connected soon • ITEP and JINR Dubna in future • Internal MSU sites (SRCC and others) as soon as manual installation is possible Lev Shamardin

More Related