Hello,
I am trying to create a Globus-Oscar Package. I had a few questions regarding
the packaging,as I have reached midway of the package creation.
Here is what I did.

1. I created rpms for junit, apache-ant (pre-requisites for Globus) and Globus
with installtion directory as /opt (Oscar default).

2. Created a package area as suggested by Howto and put rpms in RPMS area.

3. Wrote a config.xml (attached for viewing)

4. Wrote a configurator.html for configuartion as suggested. The reason for
writing the configurator is that Globus installtion cannot proceed without Java
being installed and JAVA_HOME being set. Also I want the check with user if
Apache-ant has been installed or not. If not then we install it.

5. I wrote the post_configure as suggested. So the documentation says that a
globus.conf file will be generated. Now I want to read this conf file which
would have a user "yes", "no" (on whether JAVA or ANT is installed) for
questions and then decide which rpm to install.

6. I couldnt locate in the document the next step to be done to read the conf
file and decide on the rpm to install. Or do the rpms have to be intelligent
enough to read the .conf file. As the next script after post_configure is
post_server_rpm_install, which is post rpm installtion, I need to decide based
on results of post_configure whether or not to install apache-ant. Also if java
hasnt been installed then I should not proceed with rpm installtions.

7. Also I need the setup script to generate a folder /opt/globus for me. Is that
possible ( I mean conferring to the Oscar standards).


I hope I have explained my problem. Please let me know how I can proceed with
the packaging.
I have attached the config.xml, configurator.html and post_configure script for
your viewing.

Thanks in advance.
Regards,
Kshitij Limaye



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
<?xml version="1.0" encoding="ISO-8859-1"?>
<oscar>
	<name>Globus Toolkit</name>
	<version>
		<major>3</major>
		<minor>2</minor>
		<subversion>1</subversion>
		<release>1</release>
		<epoch>1</epoch>
	</version>
	<class>third-party</class>
	<summary>Globus Toolkit 3.2 Installer</summary>
	<license>GPL</license>
	<group>Application/System</group>
	<url>http://www-unix.globus.org/toolkit/survey/index.php?download=gt3.2-all-source-installer.tar.gz</url>
	<packager>
		<name>Kshitij Limaye</name>
		<email>[EMAIL PROTECTED]</email>
	</packager>
	<description> Globus Toolkit has become a defacto standard for Grid installtions. This package installs the the               needed pre-requisite softwares and the Globbus Toolkit version 3.2 on the head node of the OSCAR Cluster.
	</description>
	<rpmlist>
		<filter group="oscar_server" distribution="redhat" distribution_version="9" architecture=’ia32’/>
		<rpm>ant-oscar1.0-1.i386.rpm</rpm>
		<rpm>junit-oscar1-.0-1.i386.rpm</rpm>
		<rpm>gt-oscar-3.2-1.i386.rpm</rpm>
	</rpmlist>
</oscar>
<html>
        <head>
                <title>Globus Toolkit 3.2 configuration Settings</title>
        </head>
<body>
        <form>
        <center>
                <h2>Setup globus toolkit 3.2 Configuration File</H2>
        </center>
        <br>
        <p> Do you have Java installed with JAVA_HOME set?<br>
        <input name="java" value="yes"><br>
        <br>
        <p> Do you have Apache ant installed with ANT_HOME set?<br>
        <input name="ant" value="no"><br>
        </form>
</body>
</html>
#!/usr/bin/env perl
# ’post_configure’ -- reads Configurator result to setup ’/etc/ssslib.conf’
use XML::Simple;
use Carp;
my @fields = (java, ant);
my $conf = ">/etc/globus.conf";
my $xml_data = "$ENV{OSCAR_PACKAGE_HOME}/.configurator.values";
my $ref = XMLin($xml_data) or croak("Error: unable to open ($xml_data)");
open(CONF, $conf) or croak("Error: unable to open ($conf)\n");
print CONF "# SSSLib configuration file\n# Generated by OSCAR\n\n";
foreach $key (@fields) {
if( defined($ref->{"$key"}) ) {
print CONF $key, "=", $ref->{$key}, "\n";
}
}
print CONF "\n";
close(CONF);

Reply via email to