EDG Testbed installation and configuration with LCFGng Maite Barroso - WP4

EDG Testbed installation and configuration with LCFG - n° 2 Contents u Current EDG Testbed structure and configuration u EDG configuration files n Description n Where to get them n How to use them u Upgrade of a basic LCFG server and client to an EDG testbed server and client

EDG Testbed installation and configuration with LCFG - n° 3 EDG Logical Machine Types 1.User Interface (UI) 2.Resource Broker (RB) 3.Information Service (IS) 4.Computing Element (CE) n Gatekeeper (Front-end Node) n Worker Nodes (WN) 5.Storage Element (SE) 6.Replica Catalog (RC)

EDG Testbed installation and configuration with LCFG - n° 4 EDG Testbed Configuration UI User Interface SE Storage Element CE Computing Element RB Resource Broker WN Worker Node WN Worker Node WN Worker Node WN Worker Node WN Worker Node WN Worker Node Proxy Proxy renewal MDS Meta Data Server RC Replica Catalog Minimal Testbed LCFG Installation Server

EDG Testbed installation and configuration with LCFG - n° 5 EDG Configuration files u EDG configuration files stored in the DataGrid cvs repository: u In the main directory edg-release/edg-release/ u Two types of LCFGng files needed: n RPM configuration files: list of RPMS to be installed on a node n Component configuration files: files containing the configuration information associated to each LCFG component in LCFG syntax (key-value pairs)

EDG Testbed installation and configuration with LCFG - n° 6 RPM configuration files

EDG Testbed installation and configuration with LCFG - n° 7 RPM config files u Stored in the cvs directory edg-release/rpmlist/  They are built following a hierarchical structure of files containing standard cpp directives like #define, #include, #ifdef, comments with /* */, etc... u These files should be located in the LCFGng server, in the directory: /opt/local/linux/6.2/rpmcfg u They include two types of files: n header files (.h) n template configurations

EDG Testbed installation and configuration with LCFG - n° 8 RPM config files: header files (I) u The RPM config file is a list of RPMs specifications, each of the following form: [prefix]rpmname-version-release[/arch][:flags] u version-release wildcards are supported : * as the release field will imply the latest version/release of the specified RPM found in the RPM repository u [prefix] n + used to replace a previously listed package with another version or release of the same package n - used to remove an already listed package u [/arch] overrides the default architecture

EDG Testbed installation and configuration with LCFG - n° 9 RPM config files: header files (II) u [:flags] consists of one or more single character flags as defined below: n :f install this package without making any checks at all. n :d install this package without making any dependency checks. n :r reboot this machine when this RPM is installed, removed or upgraded. (not yet fully implemented). n :i ignore any already installed RPM matching the given RPM spec. n :c preserve this RPM's config files across upgrades. n :t install this package without invoking trigger scripts. n :s install this package without running any pre or postinstall scripts. NOTE: for more detailed information, use man updaterpms

EDG Testbed installation and configuration with LCFG - n° 10 RPM config files: header files (III)  Example: ComputingElement-rpm.h /* ComputingElement.h ======================================================== Customized list for a ComputingElement - Globus 2 BETA 21 */ #ifdef OPENPBS openpbs-*-*:s #endif globus_common-gcc32dbg_dev globus_common-gcc32dbg_pgm globus_common-gcc32dbg_rtl globus_common-gcc32dbgpthr_dev globus_common-gcc32dbgpthr_rtl cyrus-sasl :s

EDG Testbed installation and configuration with LCFG - n° 11 RPM config files: template configuration (I) u One template per machine-type: s BASE-rpm: Base list for minimal system BASE-rpm s CE-rpm: Computing Element list CE-rpm s NM-rpm: Network Monitoring list NM-rpm s RB-rpm: Resource Broker list RB-rpm s RC-rpm: Replica Catalogue list RC-rpm s SE-rpm: Storage Element list SE-rpm s UI-rpm: User Interface list UI-rpm s WN-rpm: Worker Node list WN-rpm

EDG Testbed installation and configuration with LCFG - n° 12 RPM config files: template configuration (II) u Each template is organized in a hierarchical way, with a list of #includes of the needed header files. An example, CE-rpm: /* CE-rpm ===================================================== ComputingElement high-level RPM list */ /* RedHat updates */ #include "rh62-release-rpm.h" #include "rh62-updates-rpm.h“ /* LCFG support */ #include "lcfg-common-rpm.h" #include "lcfg-client-rpm.h" /* OpenSSH */ #include "openssh-rpm.h“ /* ComputingElement specific packages */ #include "ComputingElement-rpm.h" Rh62 list of RPMs LCFG list of RPMs Computing Element specific list of RPMs

EDG Testbed installation and configuration with LCFG - n° 13 RPM config files: template configuration (III)  But they can also contain lists of RPMs, without including them from any file. An example, CE-rpm: /* Packages added to satisfy dependencies */ libxml u Or overwrite a previously defined RPM version: +jade :s +sgml-common-0.1-7:s +docbook-3.1-3:s +stylesheets-0.13rh-4:s +openldap-servers :s u Or include #define directives: /* Define architecture */ #define ISARCH_i386 1 #define ARCH i686

EDG Testbed installation and configuration with LCFG - n° 14 Component configuration files

EDG Testbed installation and configuration with LCFG - n° 15 Component config files: format (I) u Contain the needed configuration information expressed in LCFG syntax, key- value pairs known as resources: hardware.keytable us u The key specifies the LCFG component and the parameter, e.g. hardware.keytable u Types n Existing types: integer, boolean and string (default) n u References to other component’s resources: updaterpms.rpmcfg NOTE: Remember that a machine DOES NOT have access to other machines resources. u The + symbol indicates that the new definition overrides any precedent one: +hardware.keytable en u If you don’t want to overrride but to add, use the EXTRA macro instead: EXTRA(hardware.keytable )en

EDG Testbed installation and configuration with LCFG - n° 16 Component config files: format (II) u More complex structures can also be usercomment_$ userhome_$ users usercomment_$ userhome_$ u Example: auth.users edginfo mysql auth.usercomment_edginfo EDG Info user auth.userhome_edginfo /tmp auth.usercomment_mysql user for mysql auth.userhome_mysql /home/mysql u To add a new element use the macro EXTRA: EXTRA(auth.users) postgres auth.usercomment_postgres user for postgres auth.userhome_postgres /home/postgres

EDG Testbed installation and configuration with LCFG - n° 17 Component config files u Stored in the cvs directory edg-release/source/ u These files should be located in the LCFGng server, in the directory: /var/obj/conf/server/source u Organized in a hierarchical way, using simple inheritance by file inclussion: n One file per functional entity to be configured, e.g. FabricMonitoring-cfg.h, Users-cfg.h, pbs-cfg.h FabricMonitoring-cfg.hUsers-cfg.hpbs-cfg.h n One file per machine type, e.g. ComputingElement-cfg.h, WorkerNode-cfg.hComputingElement-cfg.h WorkerNode-cfg.h n One file per site, with the site dependent configuration information, e.g. site-cfg.hsite-cfg.h n Last level on the hierarchy: one file per machine, file named after the unqualified DNS name of the client, containing the host dependent configuration information, e.g. testbed006

EDG Testbed installation and configuration with LCFG - n° 18 Component config files: example 1 testbed006 /* testbed006 ============================================== COMPUTING ELEMENT- NG VERSION */ /* Host specific definitions */ #define HOSTNAME testbed006 /* Some useful macros */ #include "macros-cfg.h" /* Site specific definitions */ #include "site-cfg.h" /* Basic RH62 client resources */ #include "redhat62-cfg.h" /* Users */ #include "Users-cfg.h" /* Computing Element specific resources */ #include "ComputingElement-cfg.h" +auth.rootpwd a1Z1WykXTe2PU Config files per machine type Site config files Specific host configuration Feature/component configuration (Linux, users…)

EDG Testbed installation and configuration with LCFG - n° 19 Component config files: example 2 /* globus */ EXTRA(profile.components) globus profile.version_globus 1 globus.ng_reconfig configure EXTRA(boot.services) globus /* globus.conf content */ globus.globusconfenabled yes globus.globusconf /etc/globus.conf /* inet: add gatekeeper service to /etc/services,enable mount */ EXTRA(inet.etcservices) gatekeeper inet.etcsrvconf_gatekeeper globus-gatekeeper 2119/tcp EXTRA(inet.allow) mountd portmap gatekeeper inet.allow_mountd SITE_ALLOWED_NETWORKS inet.allow_portmap SITE_ALLOWED_NETWORKS inet.allow_gatekeeper ALL Globus component configuration needed in a Computing Element ComputingElement-cfg.h inet component configuration needed in a Computing Element

EDG Testbed installation and configuration with LCFG - n° 20 Component config files: example 3 /*site-cfg.h ============= SITE SPECIFIC CONFIGURATION ============ */ /* COMMON GRID DEFINITIONS */ #define GRID_RB_II_HOST lxshare0315.cern.ch #define GRID_RB_II_PORT 2170 /* COMMON SITE DEFINITIONS */ /* FQDN of your LCFG server */ #define SITE_LCFG_SERVER lxshare0315.cern.ch /* Your domain */ #define SITE_LOCALDOMAIN cern.ch /* Sysadmin */ #define SITE_MAILROOT /* The gateway/router */ #define SITE_GATEWAYS /* Allowed networks (useful for tcpwrappers) */ #define SITE_ALLOWED_NETWORKS , , /* DNS */ #define SITE_NAMESERVERS site-cfg.h

EDG Testbed installation and configuration with LCFG - n° 21 SERVER UPGRADE 1)Assume LCFGng base server up & running 2)Populate the RPM repository at /opt/local/linux/6.2/RPMS with all needed RPMs from EDG central repository (don’t forget to generate the header files!) 3)Copy the needed RPM config files from cvs (edg-release/rpmlist) to the LCFGng server, /opt/local/linux/6.2/rpmcfg. This files normally don’t need to be modified. 4)Copy the needed component config files from cvs (edg- release/source) to the LCFGng server, /var/obj/conf/server/source.

EDG Testbed installation and configuration with LCFG - n° 22 SERVER UPGRADE 5) Adapt them to configure your clients: 5.1) Change the file site-cfg.h with your site settings. 5.2) Create/modify the configuration file for every client, naming it with its unqualified DNS name, e.g. testbed006 (template configuration files called testbed00x can be found in cvs). sDecide what type of machine you want to have, e.g. Computing Element sInclude the needed config files according to your machine type, e.g. ComputingElement-cfg.h for a Computing Element sAdd the host-dependent configuration (host name, root password…) 5.3) Compile and generate the XML node profile /usr/sbin/mkxprof –v –s testbed ) If it is a new client, edit /etc/dhcpd.conf and add entries for your client machine. Don’t forget to restart the service afterwards!

EDG Testbed installation and configuration with LCFG - n° 23 CLIENT UPGRADE 5) Reboot the client 6) Check that all the components started in the correct way: have a look to the log files located at: /var/obj/log/component_name 7) You can always start/stop/restart the components manually: /etc/obj/component_name start