Integration of UNICORE Components into Linux Systems

Transcription

1 Mitglied der Helmholtz-Gemeinschaft Integration of UNICORE Components into Linux Systems Rebecca Breu

2 UNICORE Installation as of Now tgz or graphical installer all files installed into one directory Disadvantages: Not compliant to Linux file system structure System-wide acess to client executables has to be set up manually No automatic starting/stopping of server components No dependency check (namely: Sun Java >= 1.5) No update mechanism for new releases UCC gimmiks (Emacs mode, Bash completion) have to be configured manually Slide 2

3 Linux File System Structure Example: Where should files of UNICORE/X go? unicorex/lib/* unicorex/conf/* unicorex/data/* unicorex/logs/* unicorex/last PID unicorex/start.sh unicorex/stop.sh /usr/share/unicore-unicorex/ /etc/unicore-unicorex/ /var/lib/unicore-unicorex/ /var/log/unicore-unicorex/ /var/run/unicore-unicorex/unicore-unicorex.run /usr/bin/unicore-unicorex-start /usr/bin/unicore-unicorex-stop Slide 3

4 Linux File System Structure In order to be compliant to Linux file system structure: Installer needs to copy files to their according places Config files and start/stop scripts need to be adjusted so that files are found in their new locations Problem: Some UNICORE components still have hardcoded files, this will be fixed in next release Slide 4

5 UNICORE Installation as of Now tgz or graphical installer all files installed into one directory Disadvantages: Not compliant to Linux file system structure System-wide acess to client executables has to be set up manually Slide 5

6 UNICORE Installation as of Now tgz or graphical installer all files installed into one directory Disadvantages: Not compliant to Linux file system structure System-wide acess to client executables has to be set up manually No automatic starting/stopping of server components No dependency check (namely: Sun Java >= 1.5) No update mechanism for new releases UCC gimmiks (Emacs mode, bash completion) have to be configured manually Slide 5

7 Starting/Stopping of Services Script /etc/init.d/unicore-unicorex which takes one argument. Supported arguments must be at least: start, stop, restart Then, to start the UNICORE/X manually: /etc/init.d/unicore-unicorex start Automatic starting and stopping of services: Link S01unicore-unicorex to /etc/init.d/unicore-unicorex in each runlevel directory the service shall run (/etc/rc3.d, /etc/rc4.d,... ) Link K01unicore-unicorex to /etc/init.d/unicore-unicorex in each runlevel directory the service shall not run (/etc/rc0.d, /etc/rc6.d,... ) Slide 6

8 insserv We don t need to create the links in rc.d manually! Create init script /etc/init.d/unicore-unicorex and execute: insserv unicore - unicorex insserv reads special comments in the init script: #! / bin /sh ### BEGIN INIT INFO # Provides : unicore - unicorex # Required - Start : $network $local_fs # Required - Stop : # Should - Start : $named # Should - Stop : # Default - Start : # Default - Stop : ### END INIT INFO Slide 7

9 Example of an Init Script PATH =/ sbin :/ bin :/ usr / sbin :/ usr / bin case "$1" in start ) su unicore -c unicore - unicorex - start ;; stop ) su unicore -c unicore - unicorex - stop ;; restart force - reload ) su unicore -c unicore - unicorex - stop su unicore -c unicore - unicorex - start ;; *) echo " Usage : $0 { start stop restart }" exit 2 ;; esac What about start-stop-daemon? Slide 8

10 UNICORE Installation as of Now tgz or graphical installer all files installed into one directory Disadvantages: Not compliant to Linux file system structure System-wide acess to client executables has to be set up manually No automatic starting/stopping of server components Slide 9

11 UNICORE Installation as of Now tgz or graphical installer all files installed into one directory Disadvantages: Not compliant to Linux file system structure System-wide acess to client executables has to be set up manually No automatic starting/stopping of server components No dependency check (namely: Sun Java >= 1.5) No upgrade mechanism for new releases UCC gimmiks (Emacs mode, bash completion) have to be configured manually Slide 9

12 Packaging The packaging system of Linux distributions is intended to take care of all of the aforementioned issues. The big two package systems: RPM: SUSE, Redhat, Scientific Linux, Mandriva, Fedora deb: Debian, Ubuntu, Knoppix Packages need to have all information about integrating their software smoothly into the Linux system, and to remove it properly Meta information: RPM: spec file deb: control file, rules file and others Slide 10

13 Package Meta Information Package name and software group Version of the software and of the package ( ) Summary and description, links to webpages License, software author(s), packager, address Changelog for package, package-specific documentation Architecture (i386, amd64,... or architecture independent) Dependencies on other packages, conflicting or recommended packages, replacements How to install (copy files, create links and directories,... ) How to upgrade (replace files, restart services,... ) How to remove and purge (delete files,... ) Slide 11

14 Installation of a Package Install required packages and remove conflicting ones Additional maintenance before installing the package (e.g. stop running services, add users/groups) Unpack files from package to Linux file system Create additional files, directories, links, ask user about additional input, inform them about steps needed to be done manually Restart services, start newly installed service Slide 12

15 Removal of a Package Purge/Erase: Remove any traces of the software. Stop services Remove files that came with the software Remove additional files the software may have created (logfiles, data,... ) Remove symlinks, directories, users, groups... Remove: Don t remove configuration files and data, so that a re-install will get back the old state Slide 13

16 Upgrading of a Package Like removal+install, but: Check if new package is indeed newer Don t upgrade those configuration files that contain much site-specific information (make backup copies, ask user) Slide 14

17 Example Spec File I Buildroot : %{ _builddir }/%{ name }- root Name : unicore - unicorex Version : Release : 6 Summary : Unicorex for the Grid system UNICORE License : see / usr / share / doc / unicore - unicorex / copyright Distribution : SuSe Group : Converted / contrib / misc URL : http :// www. unicore.eu Requires : jre >= 1.5 BuildArch : noarch Packager : Rebecca Breu unicore - support@lists. sourceforge. net % define _rpmdir../ % define _rpmfilename %%{ NAME } -%%{ VERSION } -%%{ RELEASE }.%%{ ARCH }. r % define _unpackaged_files_terminate_build Slide 15

18 The Buildroot Directory unicore - unicorex - root -- etc -- init.d -- unicore - unicorex -- unicore - unicorex -- logging. properties -- security_policy. xml -- usr -- bin -- unicore - unicorex - start -- unicore - unicorex - stop -- share -- doc -- unicore - unicorex -- copyright -- unicore - unicorex -- SAMLtypes jar -- XmlSchema jar Slide 16

19 Example Spec File II % description UNICORE ( Uniform Interface to Computing Resources ) offers a ready - to - run Grid system including client and server software. [...] This package contains the unicorex for the server installation. % pre if! getent passwd unicore > / dev / null then useradd -- system -- shell / bin / sh unicore fi % install mkdir -p $RPM_BUILD_ROOT / var / run / unicore - unicorex mkdir -p $RPM_BUILD_ROOT / var / log / unicore - unicorex mkdir -p $RPM_BUILD_ROOT / var / lib / unicore - unicorex % post insserv unicore - unicorex Slide 17

20 Example Spec File III % clean rm - rf $RPM_BUILD_ROOT / var / % postun rm -rf / var / run / unicore - unicorex rm -rf / var / lib / unicore - unicorex rm -rf / var / log / unicore - unicorex insserv -r unicore - unicorex % changelog * Fri Dec Rebecca Breu <... > added nonpriviledged unicore user - dropped single file names in favour of wildcards * Thu Nov Rebecca Breu <... > added links in / etc / init.d/ rc3.d [...] Slide 18

21 Example Spec File IV % files % dir "/ etc / unicore - unicorex /" % config ( noreplace ) "/ etc / unicore - unicorex / security_policy. xml " % config ( noreplace ) "/ etc / unicore - unicorex / xnjs_legacy. xml " [...] % config ( noreplace ) "/ etc / unicore - unicorex / simpleuudb " % config ( noreplace ) "/ etc / unicore - unicorex / wsrflite. xml " % config ( noreplace ) "/ etc / unicore - unicorex / ucc. extensions " % config ( noreplace ) "/ etc / unicore - unicorex / simpleidb " % config % attr (755, -, -) "/ etc / init.d/ unicore - unicorex " % dir "/ usr / share / unicore - unicorex /" "/ usr / share / unicore - unicorex /*" % dir "/ usr / share / doc / unicore - unicorex /" "/ usr / share / doc / unicore - unicorex / copyright " % attr (755, -, -) "/ usr / bin / unicore - unicorex - start " % attr (755, -, -) "/ usr / bin / unicore - unicorex - stop " % dir % attr (-, unicore, -) "/ var / lib / unicore - unicorex /" % dir % attr (-, unicore, -) "/ var / run / unicore - unicorex /" % dir % attr (-, unicore, -) "/ var / log / unicore - unicorex /" Slide 19

22 Building an RPM Create spec file Sort all files into right places in the buildroot directory Create init.d script Change config files and start scripts so that they will work with the new directory structure etc. Build: rpmbuildroot -bb example.spec Slide 20

23 Other Cool Things to Do With Packages Get user input during installation Configure properly? Or at least warn user to configure manually... Try to get into a Linux Distro (e.g. Globus got into Debian Testing... ) Hard because we would need source packages which means rebuilding Maven structure with packages... Building our own repositories Not hard to do, users would get updates automatically Slide 21

24 Open Questions Do we want RPMs? Do we want DEBs? How to organise changes necessary for packaging? Slide 22