On Sun, May 07, 2006 at 04:09:36PM -0700, Bernard Li wrote:
> Hi Ted:
>  
> [...] if you have a previous version of OSCAR installed, you at least
> should run /opt/oscar/scripts/start_over such that your headnode is
> cleaned of any cruft (not 100% though).  We strongly encourage users
> to do a clean re-install of the headnode OS prior to testing new
> versions of OSCAR.

Darn. I had read the description of start_over--about a month ago, in
the 4.2 docs--but had mentally tagged it with this phrase from the
description: "to recover from irresolvable errors", and didn't think of
it in connection with going to a new version. (I'm not claiming this was
logical.)

Executing scripts/start_over got rid of the
/usr/lib/perl5/site_perl/OSCAR/PackMan.pm from 4.2, that didn't have
either repo() or output_callback().

It also got rid of a number of things I had added manually early on,
to get things going, notably perl-Qt. Section 5.1.1 of the 4.2 docs says:
    When installing Linux, it is not necessary to perform a
    "custom" install since OSCAR will usually install all
    the software on which it depends.  ... Typically, a
    "Workstation" install yields a sufficient installation
    for OSCAR to install successfully.
so I had done a basic (FC5-x86_64) Linux install, with the expectation
that the OSCAR install would take care of all its dependencies.

But when configure is run, no RPMs have yet been installed:

    Configuring OSCAR version 5.0a1r4732
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking how to create a ustar tar archive... gnutar
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking for Perl environment... checking for perl... perl
    checking for puic... no
    configure: WARNING: *** You will not be able to build the OSCAR wizard
    configure: WARNING: *** You need to install Perl-Qt to be able to build the 
wizard
    configure: WARNING: *** Developer checkouts from Subversion *MUST* have puic
    configure: error: Cannot continue

(Note: Not having perl-Qt was a problem (albeit non-fatal) even when I
was building from the 4.2 distribution rather than Subversion.)

To be on the safe side, I preinstall perl-XML-Simple and perl-Tk as
well. I haven't checked carefully whether this is actually necessary.

Various other little things had to be fixed. I copied various RPMs
from */distro/rhel4* to */distro/fc5*, but found, for example, that
some rhel4 Python RPMs require python2.3, even when the corresponding
fc5 RPMs require python2.4. In these cases I rebuilt from the source
RPMs. It's not obvious why some of those RPMs require a specific Python
version rather than simply a sufficiently-new version.

By midday Tuesday it seemed that I was down to just one remaining
problem:
    --> Running transaction check
    --> Processing Dependency: /usr/bin/python2.3 for package: apitest
    --> Finished Dependency Resolution
    Error: Missing Dependency: /usr/bin/python2.3 is needed by package apitest
    Oscar Wizard preparation script failed to complete at ./install_cluster 
line 226.

This took from then until this morning to solve. It seems that one of the
files left untouched by the start_over script was
/var/cache/yum/distro_fedora-5-x86_64/headers/apitest-0.2.5+1-4.x86_64.hdr
left over from the 4.2 build.

Removing that file and simply rerunning install_cluster wasn't enough,
so I did:
    scripts/start_over
    rm -rf /var/cache/yum/distro_fedora-5-x86_64
    rm -rf /var/cache/yum/oscar_fc-5-x86_64
    rm -rf /tftpboot/distro/fedora-5-x86_64{repodata,repocache}
    make clean
    make distclean
and then a new build, which worked, in that I now have the OSCAR Wizard
GUI on my screen.

Of course, it may self-destruct as soon as I get brave enough to click
on something other than a Help button, but I wanted to report where I
was at a time when things were looking good.


Following the start over sequence just above, I execute a script I call
file-teardown, to put things back to the way subversion expects them
to be. Then I run svn update (I'm now at 4770) and examine the output
to see whether I need to modify file-setup and file-teardown (e.g. new
x86_64 files available). Then I run file-setup:

    #! /bin/sh
    #
    # The purpose of this script is to set up files required for fc5-x86_64
    # It needs to be run ahead of autogen.sh
    #
    # Ultimately, the required files will simply live in the repository, but
    # for now they will be generated, copied from rhel4-x86_64, or obtained
    # by whatever method seems good at the time.
    #
    cd /home/ted/proj/oscar/oscar-5.0-beta
    # 
    mkdir -p packages/apitest/distro/fc5-x86_64
    chown ted:ted packages/apitest/distro/fc5-x86_64
    cp -p ../apitest-1.0.0-12.noarch.rpm \
          ../python-elementtree-1.2.6-4.2.1.x86_64.rpm \
          ../python-twisted-1.3.0-5.fc5.x86_64.rpm \
          packages/apitest/distro/fc5-x86_64

    mkdir -p packages/openmpi/distro/fc5-x86_64
    chown ted:ted packages/openmpi/distro/fc5-x86_64
    cp -p packages/openmpi/distro/rhel4-x86_64/openmpi-1.0.2-1.x86_64.rpm \
          packages/openmpi/distro/fc5-x86_64

    mkdir -p packages/sge/distro/fc5-x86_64
    chown ted:ted packages/sge/distro/fc5-x86_64
    cp -p packages/sge/distro/rhel4-x86_64/sge-6.0u8-1.x86_64.rpm \
          packages/sge/distro/fc5-x86_64

    mkdir -p packages/sis/distro/fc5-x86_64
    chown ted:ted packages/sis/distro/fc5-x86_64
    cp -p packages/sis/distro/rhel4-x86_64/atftp-server-0.7-4oscar.x86_64.rpm \
          
packages/sis/distro/rhel4-x86_64/bittorrent-4.2.2-1.2.el4.rf.noarch.rpm \
          
packages/sis/distro/rhel4-x86_64/python-crypto-2.0-1.2.el4.rf.x86_64.rpm \
          
packages/sis/distro/rhel4-x86_64/python-khashmir-4.4.0-1.2.el4.test.noarch.rpm \
          packages/sis/distro/rhel4-x86_64/syslinux-2.11-1.x86_64.rpm \
          packages/sis/distro/rhel4-x86_64/udpcast-20060325-1.x86_64.rpm \
          packages/sis/distro/fc5-x86_64

    mkdir -p share/prereqs/oda/distro/fc5-x86_64
    chown ted:ted share/prereqs/oda/distro/fc5-x86_64
    cp -p 
share/prereqs/oda/distro/rhel3-x86_64/mysql-server-3.23.58-1.x86_64.rpm \
          share/prereqs/oda/distro/fc5-x86_64

    rpm -Uhv 
share/prereqs/perl-Qt/distro/fc5-x86_64/perl-Qt-3.009b2-4.x86_64.rpm \
             
share/prereqs/perl-XML-Simple/distro/fc5-x86_64/perl-XML-Simple-2.14-2.rf.noarch.rpm
 \
             
share/prereqs/perl-Tk/distro/fc5-x86_64/perl-Tk-804.026-1.oscar.x86_64.rpm

The script file-teardown undoes this:

    #! /bin/sh
    #
    # The purpose of this script is to remove directories and files set up by
    # file-setup, so that--together with make clean and make distclean--a clean
    # environment can be restored.
    # Must be done _after_ the makes, since they expect things to be still 
there.
    #
    cd /home/ted/proj/oscar/oscar-5.0-beta
    # 
    rm -rf packages/apitest/distro/fc5-x86_64

    rm -rf packages/openmpi/distro/fc5-x86_64

    rm -rf packages/sge/distro/fc5-x86_64

    rm -rf packages/sis/distro/fc5-x86_64

    rm -rf share/prereqs/oda/distro/fc5-x86_64

    rpm -e perl-Qt perl-XML-Simple perl-Tk

After file-setup, it's straightforward:

    ./autogen.sh
    ./configure
    rm -rf /opt/oscar/*
    make install
    cd /opt/oscar
    ./install_cluster eth0

The last line used to be
    OSCAR_VERBOSE=1 ./install_cluster eth0
but I'm hoping not to have to use that any more.

I've made a couple of simplifications above. I mostly do builds as "ted"
and only do the parts I have to as "root", and verbose commands entered
from the keyboard actually go in like this:
    (<command>; echo $?) 2>&1 | tee <seq#>.log
which is not too onerous, since they are generally just reentered from
the bash command history.


With regard to scripts/start_over, I suggest putting something at the
beginning of Detailed Cluster Installation Procedure like this:

    Unless this is the very first actual or partial OSCAR
    install since the installation of the operating system,
    you need to consult Section n.nn, Starting over--installing
    OSCAR again.

and the script should zap a few more things, as noted above.


Thanks for helping me get this far!


-- 
Ted Powell <[EMAIL PROTECTED]>   http://psg.com/~ted/
"If you don't look, you don't know."
    Dr. Sam Ting, Nobel laureate experimental physicist.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to