Hi,
> =============================================================================
> == Running OSCAR wizard_prep script
> =============================================================================
>
> Available Distro Pools:
> $VAR1 = 'redhat-el-server-5-i386';
> $VAR2 = {
> 'url' => '/tftpboot/distro/redhat-el-server-5-i386.url',
> 'oscar_repo' =>
> 'file:/tftpboot/oscar/rhel-5-i386,file:/tftpboot/oscar/common-rpms',
> 'distro_repo' => 'file:/tftpboot/distro/redhat-el-server-5-i386',
> 'os' => {
> 'compat_distro' => 'rhel',
> 'compat_distrover' => '5',
> 'distro' => 'redhat-el-server',
> 'pkg' => 'rpm',
> 'arch' => 'i386',
> 'distro_version' => '5'
> }
> };
> --> Writing pre-oscar rpmlist...
> --> Bootstrapping OSCAR smart package manager
> Error: packages/yume is not a directory or doesn't contain a prereq.cfg file!
> Usage:
> /opt/oscar/scripts/install_prereq --dumb|--smart [--verbose]
> prereq_path
>
> Install prerequisites located in prereq_path. They should have
> the same directory structure like normal OSCAR packages but
> need to contain the configuration file prereq.cfg
> This file is required because prereqs are installed before
> config.xml files can be parsed.
> One of --smart|--dumb must be selected! --dumb installs packages
> listed in the prereq.cfg file with the base package manager and
> is unable to resolve dependencies. It should be used for
> bootstrapping a smart package manager. --smart installs prereqs
> with the help of a smart package manager like yum(e).
> The prereq_path arguments must be paths relative to the
> $OSCAR_HOME environment variable's value!
> Could not bootstrap smart package manager!
> Oscar Wizard preparation script failed to complete at ./install_cluster line
> 279.
> [EMAIL PROTECTED] oscar]#
We have to take care of the case that there is no the packages/ path on the
nightly tarball. Looks like that some scripts are still looking for the path.
Regards,
- DongInn
DongInn Kim wrote:
> Hi,
>
> I found another problem on the crispy nightly tarball.
>> [EMAIL PROTECTED] tftpboot]# cd /opt/oscar/
>> [EMAIL PROTECTED] oscar]# env OSCAR_VERBOSE=3 ./install_cluster eth0
>> --> Setting env variable OSCAR_UI to gui
>> --> Setting env variable OSCAR_HOME to /opt/oscar
>> Checking your system...
>> Success: network-check.pl
>> Success: tftpboot-check.pl
>> Success: display-check.pl
>> Success: ssh-check.pl
>> Success: su-check.pl
>> Success: debrepo-check.pl
>> Success: selinux-check.pl
>> System checked
>> ln: creating symbolic link `/opt/oscar/packages/oda/prereq.cfg' to
>> `/opt/oscar/packages/oda/prereqs/mysql.cfg': No such file or directory
>> ERROR: failed to get oscar version '/opt/oscar/dist/get-oscar-version.sh
>> /opt/oscar/VERSION --full' - No such file or directory at ./install_cluster
>> line 177.
>
> Well, apparently we have not double checked to see if the nightly tarball
> simply works or not.
> We have to fix this problem ASAP.
>
> Regards,
>
> - DongInn
>
>
> Erich Focht wrote:
>> Hi,
>>
>> the 5.1 branch called "crispy" is now available as nightly build (thanks
>> DongInn for enabling it). It is a first preview of the future 5.1 release
>> and contains major changes in the way how OSCAR packages (opkgs) are
>> installed and treated.
>>
>> The basic idea behind the new structure is that opkgs as well as the basic
>> OSCAR installation come packaged in the distribution's native package
>> management format. This way the OSCAR infrastructure doesn't need to care
>> about resolving dependencies and binary package lists. Everything is coming
>> as RPM or DEB in repositories and is upgradeable (in theory).
>>
>> Each OSCAR package is represented by three meta-packages:
>>
>> opkg-<NAME> : the so called API metapackage, contains the OSCAR API scripts,
>> the documentation (if available) and the testing scripts.
>>
>> opkg-<NAME>-server: contains the binary package dependencies of the RPMs or
>> DEBs
>> which need to be installed on the master node for the
>> opkg.
>>
>> opkg-<NAME>-client: contains as dependencies the binary packages which need
>> to
>> be installed on the client nodes (the image).
>>
>> In addition the the opkg-* packages we have oscar-base, oscar-libs,
>> oscar-scripts,
>> oscar-server and oscar-client. They contain the base OSCAR scripts, libs,
>> etc...
>>
>> "crispy" contains support for the RPM based distributions:
>> rhel-5-i386
>> rhel-5-x86_64
>> suse-10.2-x86_64
>> ydl-5-ppc64 (yellow dog linux for the PS3)
>> ALL these distros are new for OSCAR, which shows that the infrastructure is
>> now
>> quite flexible. And the PS3 support is something quite unique, a big thanks
>> to
>> DongInn and Bernard for it!
>>
>> The base tarball is not there any more, you just have to download the
>> repository
>> tarballs for the distros you need, and the common-rpms repository tarball.
>>
>> A very basic HOWTO:
>> -------------------
>> 1) download the repo tarballs you are interested in from
>> http://oscar.openclustergroup.org/filebrowser/49/crispy
>> For example:
>> oscar-repo-common-rpms-5.0.9a1r6551nightly-20071113.tar.gz
>> oscar-repo-rhel-5-x86_64-5.0.9a1r6551nightly-20071113.tar.gz
>>
>> 2) unpack the tarballs:
>> mkdir -p /tftpboot/oscar
>> tar xzfC oscar-repo-common-rpms-*.tar.gz /tftpboot/oscar/
>> tar xzfC oscar-repo-rhel-5-x86_64-*.tar.gz /tftpboot/oscar/
>>
>> 3) install yume (supposing yum is already there):
>> yum install createrepo /tftpboot/oscar/common-rpms/yume*.rpm
>>
>> 4) set up the distro repository in /tftpboot/distro/... Look at
>> http://svn.oscar.openclustergroup.org/trac/oscar/wiki/InstallGuidePreparing#DistributionRepositories
>> for instructions.
>>
>> 5) install oscar-base rpm
>> yume --repo /tftpboot/oscar/common-rpms install oscar-base
>>
>> 6) start installation, for example:
>> cd /opt/oscar
>> env OSCAR_VERBOSE=3 ./install_cluster eth0
>>
>>
>> That's it. Don't expect this to be perfect. There is a known bug (and more
>> unknown ones) with systemimager which rewrites the image's systemconfig.conf
>> in wrong way. You can fix this by manually editing
>> /var/lib/systemimager/scripts/<IMAGENAME>.master
>> and removing/commenting out the IF block starting after the comment line:
>> # Fix device names in boot-loader configuration
>> Do this before deploying the client nodes!
>> A fix is underway and will come with the systemimager 4.0.2 release.
>>
>> Regards,
>> Erich
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Oscar-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/oscar-devel
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Oscar-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oscar-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
