UMD:Documentation

From EGIWiki
Jump to: navigation, search
Introduction Prerequisites Repository Products Capabilities


UMD Documentation for operations and sites

1 Introduction

This space is aimed at Resource Infrastructure Providers (sites), both part of the current infrastructure as well as to new ones.

It contains information about supported middleware products, supported hardware platforms and OSs, hardware requirements, deployment scenarios, installation and configuration or links to the proper administration manuals where available.


2 Middleware Products in UMD

2.1 Local services

A site to be integrated into the grid infrastructure is required to have a minimum set of services that are listed next:

  1. Compute Element
  2. Storage Element
  3. Site Information node
  4. Accounting node
  5. Authorization service
  6. A set of Worker Nodes
  7. User Interface: is the site users entry point for the grid resources.

2.1.1 Compute Element

The Compute Element constitutes the site frontend to it's local cluster of Worker Nodes. UMD provides 2 alternative products that can be deployed as Compute Elements:

  • CREAM CE
  • ARC CE

2.1.2 Storage Element

The Storage Element constitutes the site frontend to it's local data storage. UMD provides 3 alternative products that can be deployed as Storage Elements:

  • dCache
  • DPM
  • StoRM

2.1.3 Site Information node

The Site Information node gathers the site resource information and publishes it to the outside. UMD provides the following product:

  • Site-BDII

2.1.4 Accouting node

This service collects compute usage records in the local cluster of Worker Nodes, and publishes a summary of those records into an accounting portal. UMD provides the following product:

  • APEL

2.1.5 Authorization service

This service holds the local policies for users and VO's to access each resource at the site UMD provides the following product:

  • ARGUS

2.1.6 Worker Nodes

Set of nodes in the local cluster allocated to accept and run grid jobs. These nodes will have installed all middleware client tools and APIs. UMD provides the following product:

  • WN

2.1.7 User Interface

Local desktops or workstations that are the users entry point to the grid resources. These nodes will have installed all middleware client tools and APIs. UMD provides the following product:

  • UI


2.2 Global services


Starting actions

  • Define the scope of the documentation
    • Platform, i.e. to which level of services do sites need to deploy software to service their users
      • Example: Small site
        • Compute element
          • Describe the list of components and products that comprise the described solution
          • Describe which functional capabilities this solution satisfies (e.g. Job Execution & Parallel Job)
          • Provide hardware requirements necessary for this solution in its various scales (e.g. larger and ultimate edition)
        • Storage Element
        • Information System
        • etc.
      • Medium site
        • ...
        • And of course ultimate site (GRNET)

Roles and responsibilities

  • DMSU
    • Documentation resources and location
    • Specific configuration settings for the different deployment scenarios
    • Known issues that affect pertinent scenarios
  • TSA1.3
    • Getting a sense of and collect the deployment scenarios
    • Use cases and scenarios for the deployment scenarios
    • source in concrete documentation contribution from site admins
    • Editorial contributions to this Wiki page
  • TSA 2.2
    • in general, same as TSA1.3
  • TSA2.3
    • in general, same as TSA1.3
  • TSA2.4/IT Support
    • Maintenance and sanity check (against vandalising if at all)
    • Proper linkage and basic dissemination
  • Anyone / individual contributions
    • Use the discussions page for this Wiki page