SEE-GRID-SCI
Overview of YAIM
www.see-grid-sci.eu
AEGIS Training for Site Administrators
Dusan Vudragovic
SCL, Institute of Physics Belgrade
Serbia
[email protected]
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.
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
2
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
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
3
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
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
4
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
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
5
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
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
6
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
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
7
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
/opt/glite/yaim/defaults/myservice.pre
/root/siteinfo/site-info.def
/opt/glite/yaim/defaults/site-info.post
/opt/glite/yaim/defaults/myservice.post
/root/siteinfo/services/mysevice
/root/siteinfo/nodes/mynode
/root/siteinfo/vo.d/myvo
/opt/glite/yaim/node-info.d/myservice
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
(Y)
(S)
(S)
(Y)
(S)
(S)
(S)
(S)
(Y)
8
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/myfunc
OR
/opt/glite/yaim/functions/myfunc
 /opt/glite/yaim/functions/post/myfunc
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
9
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
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
10
SEE-GRID-SCI YAIM template
SEE-GRID-SCI YAIM siteinfo directory template is
available at
https://viewvc.scl.rs/viewvc/yaim/trunk/?root=seegrid
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
11
Other useful info
YAIM home page
http://www.yaim.info/
YAIM 4 guide for sysadmins
https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400
YAIM Status Page
https://twiki.cern.ch/twiki/bin/view/LCG/YaimPlanning
gLite 3.1 Generic Installation & Configuration guide
https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstall
Guide310
AEGIS Training for Site Administrators, Institute of Physics Belgrade, December 10-11, 2008
12