130 likes | 147 Views
This overview provides detailed information on YAIM software for configuring Grid services using bash scripts and modularizing components. It explains YAIM's directory structure, command usage, configuration flow, and logging. Find templates and guides at the provided links.
E N D
Overview of YAIM AEGIS Training for Site Administrators Dusan Vudragovic SCL, Institute of Physics Belgrade Serbia dusan@scl.rs The SEE-GRID-SCI initiative is co-funded by the European Commission under the FP7 Research Infrastructures contract no. 211338
What is YAIM • YAIM = Yaim Ain't an Installation Manager • YAIM is software to configure Grid services • YAIM provides simple configuration methods • YAIM has been implemented as a set of bash scripts • To support the EGEE project's component based release model YAIM 4 has been modularized • YAIM core is supplemented by component specific scripts, distributed as separate RPMs YAIM’s logo – the yak The yak is a long-haired humped domestic bovine found in Tibet and throughout the Himalayan region of south Central Asia, as well as in Mongolia. The yak is not a gnu.
YAIM’s directory structure (1/2) • YAIM directory structure is created under/opt/glite/yaim • /functions/ - Functions (bash scripts) to configure node types • /functions/local/ - Site administrators can put here their own function definition files • /functions/pre/ - If this function exists, will be executed before the main function • /functions/post/ - If this function exists, will be executed after the main function • /node-info.d/ - Contains a file for each node type which defines the set of functions to be executed during the configuration of that node type
YAIM’s directory structure (2/2) • /defaults/ - Files that will be sourced before and after the main site-info.def; purpose is to give meaningful default values • /bin/ - The main YAIM executable • /log/ - YAIM's logfile • /examples/ - Configuration example
YAIM’s configuration directory structure • YAIM allows having the site's configuration in a well separated and protected place • The site-info.def file has to sit in a directory (ex.: /root/siteinfodir/) which could contain the followings • site-info.def - main configuration file of the site • services/ - files are sourced only when that given service is configured • nodes/ - files are sourced only when that given host is configured • vo.d/ - files can contain VO specific variables • users.conf, groups.conf - configurable via the USERS_CONF and GROUPS_CONF variables
The bin/yaim command(1/2) • Usage/opt/glite/yaim/bin/yaim <action> <parameters> • Actions-c | --configure – configure services-r | --runfunction – execute a configuration function -v | --verify – check variables definition -d | --debug – logging level -e | --explain – explains what the functions are doing -h | --help – help -a | --available –available configuration targets
The bin/yaim command(2/2) • Parameters-s | --siteinfo – location of the site-info.def file-n | --nodetype – node name to configure-f | --function – function to execute • Examples • Configuration./yaim –c –s /root/siteinfo/site-info.def –n SE_dpm_mysql –d 6 • Running a function separately ./yaim –r –s /root/siteinfo/site-info.def –n LFC_mysql –f config_gip • Verify your site-info.def./yaim –v –s /root/siteinfo/site-info.def –n SE_dpm_mysql
Configuration flow (1/2) • When launching the configuration the different configuration files will be sourced and will overwrite each other in the following order • /opt/glite/yaim/defaults/site-info.pre (Y) • /opt/glite/yaim/defaults/myservice.pre (S) • /root/siteinfo/site-info.def (S) • /opt/glite/yaim/defaults/site-info.post (Y) • /opt/glite/yaim/defaults/myservice.post (S) • /root/siteinfo/services/mysevice (S) • /root/siteinfo/nodes/mynode (S) • /root/siteinfo/vo.d/myvo (S) • /opt/glite/yaim/node-info.d/myservice (Y)
Configuration flow (2/2) • For each function myfunc defined in /opt/glite/yaim/node-info.d/myservice yaim executes the followings if they are defined • /opt/glite/yaim/functions/pre/myfunc • /opt/glite/yaim/functions/local/myfuncOR /opt/glite/yaim/functions/myfunc • /opt/glite/yaim/functions/post/myfunc
The log file • YAIM logs its output to/opt/glite/yaim/log/yaim/yaimlog • Each time the yaim command is executed an entry is added to this logfile containing the • command executed • the site-info.def and other config files used • the time and date information • the version of the installed YAIM RPMs
SEE-GRID-SCI YAIM template • SEE-GRID-SCI YAIM siteinfo directory template is available athttps://viewvc.scl.rs/viewvc/yaim/trunk/?root=seegrid
Other useful info • YAIM home pagehttp://www.yaim.info/ • YAIM 4 guide for sysadminshttps://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400 • YAIM Status Pagehttps://twiki.cern.ch/twiki/bin/view/LCG/YaimPlanning • gLite 3.1 Generic Installation & Configuration guidehttps://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide310