Return to README.maint CVS log

Up to [Development] / projects / failsafe / FailSafe-mgr

Updated/corrected instructions.

README for maintainers: $Date: 2000/07/07 00:16:17 $
===========================================================================


BUILDING FROM A SOURCE TREE

After populating your workarea, first make sure you have recent Rhino
(sysadm_base-dev) installed, as it installs a sysadm_base.m4 file which
contains macro definitions which are used by aclocal (the first step below).

You will also need FailSafe headers & libraries.  For now, you get these
from the FailSafe team, but that should change shortly.  (In fact, that's
probably wrong even now.)

You will need to run the following commands before running "make":

    aclocal
    autoheader
    automake --add-missing
    autoconf
    setenv EXTRA_INCS "-I/path/to/fs/inc -I/path/to/fs/os"
    setenv EXTRA_LIBS "-L/path/to/fs/lib" 
    ./configure --prefix=/usr --sysconfdir=/etc

(You may also need --with-JAVAPATH=/usr/jdk118/bin, etc.)

At this point, you should be able to run "make rpm".

This works on the following systems:

    RedHat 6.2
        autoconf-2.13
        automake-1.4
        gettext-0.10.35
        gmake-3.78.1
        libtool-1.3.4

OK, that was a short list.



Organization: Silicon Graphics Inc.
X-Mailer: Mozilla 4.7C-SGI [en] (X11; I; IRIX 6.5-ALPHA-1276148920 IP32)
X-Accept-Language: en
Sender: owner-admgui@cthulhu

RCU wrote:
> 
> Mayank, Vidula, and Kirthiga,
> 
> My team has fleshed out some details on FailSafe GUI Linux work.
> We'll most likely need to slip our original dates slightly.  We're
> now aiming for these dates, assuming that the FailSafe 2.0 APIs
> (headers, libraries, CLI arguments) have NOT changed between IRIX
> and Linux:
> 
>   ALPHA--GUI packaged in installable rpms     May 26, Friday
>     and runs, but help may be missing,
>     code not yet scrubbed, a few other
>     pieces may be missing
> 
>   BETA--help in place (based on FailSafe      June 16, Friday
>     Administrators Guide scrubbed by SuSE),
>     code scrubbed (no patent/copyright/legal
>     encumbrances), bugs found in testing
>     fixed
> 
>   FREEZE--bugs found in testing fixed         July 7, Friday
> 
> ** Vidula, how important is i18n in first release?
> 
> We believe i18n work, though potentially substantial, should
> be part of the first open-source FailSafe drop, such that the
> Linux community can immediately start localizing FailSafe GUI.
> Because of potential impact on the build and basic functionality,
> i18n work should go in before alpha, but we haven't scheduled it;
> I'll keep you apprised of changes to the May 26 alpha target as
> we learn more about the work required.  Also it'll help us focus
> our work to understand how important i18n is in first release.
> 
> ** Mayank, Rusty needs the following resources:
> 
> 1) Names of your Linux cluster(s) and machines that Rusty can
> use to install server-side GUI upon and test the GUI
> 

The 2 clusters are:

1) ciel.engr and akash.engr running Suse 6.4
2) pathfinder.engr and challenger.engr running Redhat 6.2

Both these clusters are actively used by Franck and Subodh. How long
would you need them, what kind of testing will be done, would you need
Failsafe to be functioning on them, would you need to create some
resource groups on them? Some of these answers will help us determine if
these machines can be shared.


> 2) Paths to appropriate rpms/tarballs for FailSafe headers and
> libraries that Rusty can use to build the server-side GUI
> 

pioneer.engr:/tmp/SuSe/

cas-1.0-3587.src.rpm
ci-1.0-3035.src.rpm 
failsafe-1.0-1571.src.rpm

The sgibuild environment will be needed to compile these sources so you
will also find SaParam.tar in this directory.

Please let us know in case you need help with this.

> Also, where should we clone the FailSafe GUI tree?  We observe
> that bonnie:/proj/chaos/linux/1.0/isms/FailSafe-mgr exists,
> but with a dummy Makefile. 

yes that is the correct location.

 We'd expect to clone the latest
> GUI from FailSafe 2.0 patch 3901 into this location; does
> this sound reasonable?
> 

yes that sounds right.

Thanks.
-- 
Mayank Vasa
MTS, CSBU
(650) 933 4654




PRODUCT VERSION NUMBER

The version is stored in configure.in.  The value set there is available in
C/C++ files through config.h and Java files through
packages/com/sgi/fsmgr/fsPackageP.properties (which is generated from
fsPackageP.properties.in at configure time).  The
/var/sysadm/products/.../version link is created by the top-level Makefile.am.