YAIM: The glite configuration tool

Similar documents
YAIM Overview. Bruce Becker Meraka Institute. Co-ordination & Harmonisation of Advanced e-infrastructures for Research and Education Data Sharing

EMI Componets Installation And Configuration

CREAM Computing Element Overview

EMI Deployment Planning. C. Aiftimiei D. Dongiovanni INFN

CE+WN+siteBDII Installation and configuration

WLCG Lightweight Sites

Installation Guide. How to install the Active Security monitoring component for int.eu.grid JRA1

glite Grid Services Overview

I Tier-3 di CMS-Italia: stato e prospettive. Hassen Riahi Claudio Grandi Workshop CCR GRID 2011

AMGA Metadata catalogue service for managing mass data of high-energy physics

A unified user experience for MPI jobs in EMI

glite UI Installation

Argus Vulnerability Assessment *1

INNOVER-EAST. WP5 Dissemination. Deliverable D5.3 Basic Dissemination Material

EGEE-II. Document identifier: Document link:

Argus Authorization Service

Edinburgh (ECDF) Update

Jozef Cernak, Marek Kocan, Eva Cernakova (P. J. Safarik University in Kosice, Kosice, Slovak Republic)

Research Infrastructures Use and Further Needed Development

EUROPEAN MIDDLEWARE INITIATIVE

The EU DataGrid Testbed

Bob Jones. EGEE and glite are registered trademarks. egee EGEE-III INFSO-RI

Tel-Aviv University GRID Status

University of Energy and Natural Resources, Sunyani. Name: UBA, Felix. How to get ROMS Summer school August, 2016

Future of Grid parallel exploitation

Data Storage. Paul Millar dcache

Integrating the IEKP Linux cluster as a Tier-2/3 prototype centre into the LHC Computing Grid

Faculty of Engineering Computer Engineering Department Islamic University of Gaza Network Lab # 7 Permissions

Adaptive MAC (TDMA/CSMA)

Argus: The Simplified Policy Language

Dynamic management of virtual infrastructures

dcache Introduction Course

EUROPEAN MIDDLEWARE INITIATIVE

Platform Analytics Version for LSF. Administering SC

Lessons Learned in the NorduGrid Federation

itec People & Events Directory

Astrophysics and the Grid: Experience with EGEE

Overview of HEP software & LCG from the openlab perspective

PoS(EGICF12-EMITC2)081

LCG Installation LCFGng

DISCERN Libraries User Guide

Horizon 2020 INFRADEV Design studies. RICHFIELDS Working Packages 2 Deliverable D2.2. Project identity. Date delivered: M6

The EGEE-III Project Towards Sustainable e-infrastructures

AGATA Analysis on the GRID

MyProxy Server Installation

EUROPEAN MIDDLEWARE INITIATIVE

where the Web was born Experience of Adding New Architectures to the LCG Production Environment

Operation of Site Running StratusLab toolkit v1.0

Wellington City Council Funding Portal Quick Reference Guide for Applicants

ATLAS Tier-3 UniGe

Service Level Agreement Metrics

Cluster Nazionale CSN4

EUROPEAN MIDDLEWARE INITIATIVE

Monitoring System for the GRID Monte Carlo Mass Production in the H1 Experiment at DESY

The INFN Tier1. 1. INFN-CNAF, Italy

E G E E - I I. Document identifier: Date: 10/08/06. Document status: Document link:

Introduction to Grid Infrastructures

ASTRONOMY & PARTICLE PHYSICS CLUSTER

Transfer Manager.NET Installation Guide

LHCb experience running jobs in virtual machines

Work Package 6 Dissemination and Exploitation Involved Partners: Planet Media, City Passenger, LTU, CTI

First Experience with LCG. Board of Sponsors 3 rd April 2009

The European Research Council

SGS11: Swiss Grid School 2011 Argus The EMI Authorization Service

StoRM configuration. namespace.xml

GRID COMPUTING APPLIED TO OFF-LINE AGATA DATA PROCESSING. 2nd EGAN School, December 2012, GSI Darmstadt, Germany

Testing SLURM open source batch system for a Tierl/Tier2 HEP computing facility

Beob Kyun KIM, Christophe BONNAUD {kyun, NSDC / KISTI

Understanding StoRM: from introduction to internals

Lesson 6: Portlet for job submission

CMS users data management service integration and first experiences with its NoSQL data storage

dcache Introduction Course

D4.10 Final parmerasa Multi-core System Software

Preemptive PREventivE Methodology and Tools to protect utilities

EU Projects. Christoph Witzig

UCD Centre for Cybersecurity & Cybercrime Investigation

LS-DYNA Installation Guide Windows and Linux

Logic Networks on the Grid: Handling 15 Million Jobs

Logo and Templates Deliverable 7.3

Newsletters published twice a year

Project selection Use-case collection Characteristics scoring. Principal Components Analysis (PCA) Biplot and numerical representation Clustering

CMS Belgian T2. G. Bruno UCL, Louvain, Belgium on behalf of the CMS Belgian T2 community. GridKa T1/2 meeting, Karlsruhe Germany February

Erasmus+ 2017/18 Timeline, Checklist & FAQs

CRAB tutorial 08/04/2009

The glite middleware. Presented by John White EGEE-II JRA1 Dep. Manager On behalf of JRA1 Enabling Grids for E-sciencE

Learning Perl Through Examples Part 2

Integrating interoperable automation technologies across the IIoT Layered Databus Architecture

etrustex Web access Java Script version User Guide for EC EGREFFE Users

Modular Queries and Unit Testing

Quick Start Guide To Mobility Tool+ For Key Action 1 School Staff Mobility Projects Version 1

Status of KISTI Tier2 Center for ALICE

Document Version: EMI Component Version: Date:

The Role and Functions of European Grid Infrastructure

Shell and Utility Commands

Branch Change PS_BRCHCHNG_FILE Application Branch Exchange

PYTHON TRAINING COURSE CONTENT

Grid Operations meeting

Challenges in the field of Research Infrastructures, ESFRI

AUDIO WEAVER DESIGNER USERS GUIDE

The EPIKH, GILDA and GISELA Projects

Transcription:

YAIM: The glite configuration tool Sara Bertocco INFN Padova EMI is partially funded by the European Commission under Grant Agreement RI-261611 28 August 2012 GridKa School

YAIM documentation Guide for Administrators https://twiki.cern.ch/twiki/bin/view/lcg/yaimguide400 YAIM in EMI https://twiki.cern.ch/twiki/bin/view/emi/emiyaim Dissemination level http://en.wikipedia.org/wiki/yaim Old, but nice https://twiki.cern.ch/twiki/bin/view/egee/yaim 2 2

Yaim: Yet Another Installation Manager YAIM implements a configuration method for the glite software. The aim of YAIM is to provide a simple configuration method that can be used to set up a simple Grid Site but can be easily adapted and extended to meet the need of larger sites. YAIM is not more than, just a set of bash scripts and functions. YAIM is distributed in rpm form and it usually resides in /opt/glite/yaim. 3

Modular structure Yaim is modular: glite-yaim-core contains common functions and definitions glite-yaim-<module_name> implement the functionality to configure specific node types Each service metapackage installs the appropriate yaim module 4

YAIM Configuration Files (1) users.conf (for pool accounts configuration) groups.conf (for pool accounts configuration) wn-list.conf site-info.def (main configuration file of YAIM) vo.d (specific VO conf.) services/glite-<node_name> (specific service conf., overwrite defaults) services/nodes/<host_name.domain_name> (host specific) site-info.pre (contains defaults) site-info.post (contains defaults) Documentation: https://twiki.cern.ch/twiki/bin/view/lcg/site-info_configuration_variables#site_info_def 5

YAIM Configuration Files (2) YAIM distributes an example of relevant configuration files under /opt/glite/yaim/examples/siteinfo/siteinfo.def. In case the system administrator is interested in using these files, it should move them to a safer location. site-info.def is the main configuration file of YAIM. It is in the format of key-value pairs. Since YAIM is mainly bash, all the configuration files have to follow the bash syntax. A good syntax test for the site-info.def is to source it 6

YAIM Configuration Files (3) Configuration file sourcing flow: 1. /opt/glite/yaim/defaults/site-info.pre 2. /opt/glite/yaim/defaults/glite-node-type.pre 3. siteinfo_dir/site-info.def 4. siteinfo_dir/services/glite-node-type 5. siteinfo_dir/nodes/machine.domain 6. /opt/glite/yaim/defaults/site-info.post 7. /opt/glite/yaim/defaults/glite-node-type.post 8. siteinfo_dir/vo.d/vo_name 9. /opt/glite/yaim/node-info.d/glite-node-type 7

Node Type Definition The configuration steps for a specific node type are defined in /opt/glite/yaim/node-info.d/glite-<nodename> This file contains the ordered list of yaim scripts run to configure the specified node type. 8

YAIM usage /opt/glite/yaim/bin/yaim <action> <parameters> Actions: -c --configure : Configure already installed services. Compulsory parameters: -s, -n -r --runfunction : Execute a configuration function. Compulsory parameters: -s, -f Optional parameters : -n -v --verify : checks that the required variables for a given nodetype are all defined. Compulsory parameters: -s -n -d --debug : Define a loglevel, overwrites YAIM_LOGGING_LEVEL defined in site-info.def. Values: 1-7 -e --explain : Explains what the functions are doing by printing out the comments found inside them. Compulsory parameters: -s -n -a --available : Prints out the available configuration targets. Compulsory parameter: -s -p --package : Creates an rpm package from the configuration directory structure, that can be installed on other nodes. It installs under: /opt/glite/yaim/examples/siteinfo/mysiteinfo-${site_info_version} Compulsory parameter: -s -h --help : Prints out this help. Specify only one action at a time! Parameters: -s --siteinfo: : Location of the site-info.def file -n --nodetype : Name of the node type(s) to configure -f --function : Name of the functions(s) to execute 9

Examples Check what can you configure: /opt/glite/yaim/bin/yaim -a -s /etc/yaim/site-info.def Configuration: /opt/glite/yaim/bin/yaim -c -s /etc/yaim/site-info.def -n creamce Running a function: /opt/glite/yaim/bin/yaim -r -d 6 -s /etc/yaim/site-info.def -n creamce -f config_cream_ce Verify your site-info.def: /opt/glite/yaim/bin/yaim -v -s /etc/yaim/site-info.def -n creamce Create an rpm package from site-info.def: /opt/glite/yaim/bin/yaim -p -s /etc/yaim/site-info.def 10

HOW TO customize YAIM Yaim configuration scripts are installed in /opt/glite/yaim/functions Customization scripts must be created in /opt/glite/yaim/functions/local If you create in the suddirectory local a script with the same name of a script already existing one in functions, the local script will overwrite the functions one. This is usefull to apply fixes or customizations locally. Be careful to verify code alignment after updates 11

Questions? 12