perfsonar-dev - More Notes about perfSONAR 1.0 installation at ESnet.
Subject: perfsonar development work
List archive
- From: Joe Metzger <>
- To: Joe Metzger <>
- Cc:
- Subject: More Notes about perfSONAR 1.0 installation at ESnet.
- Date: Tue, 29 Aug 2006 15:39:48 -0500
Additional perfSONAR 1.0 Installation notes.
--
The installation script should ask for additional Java command line
parameters. These should then be used whenever the install script
invokes Java, or when it creates scripts that invoke Java (axis.sh,
MAAxisDeploy.sh, etc....)
Somebody may want to use "-Djava.net.preferIPv4Stack=true
-Djava.net.preferIPv4Addresses" or other command line
arguments that are neccessary in their environmnet.
---
All of the Axis Distributions I tried were missing
xmlsec.jar, mail.jar and activation.jar. Since we are
distributing these, we should provide some references
about what version we are distributing (and what it is
compatiable with if possible.)
Also, we need to have a 'pre-install' step
that copies those into the Axis directory and restarts
tomcat so that the Install doesn't ALWAYS FAIL ON THE
FIRST ATTEMPT.
----
install.pl moves files from client/* to xml/*.
This means YOU ALWAYS GET ERRORS ON SECOND OR LATER INSTALL
attempts.
It should copy, not move.
----
The install docs need more info about eXist.
The readme (and install process) should clearly state
at what point exist needs to be running.
How do I push my RRDMA configuration into the Exist DB?
Does it happen automagically? Or do I need to do it manually?
How do I update the config in exist when the underlying
RRD Database installation changes? (ie nightly updates)
How can I verify that my RRDMA configuration is stored properly?
(I will have more to say about exist after I figure it out...)
--Joe
Joe Metzger wrote:
FYI,
These notes are not complete, because I still don't have a stable installation. :-)
Recommendations for improving perfSONAR 1.0
---
The existing configuration script (install.pl) should be turned into an
installation script. The first question it asks should be where do you
want to install the application. It should create that directory and
and required sub-directories if neccessary and install all files into
that directory.
The user should be able to delete the temporary directory he unzip'd the
tarball in once the install is complete
---
The FIRST test in the testing procedure should be to go to the
Happy-Axis page and verify axis is happy, and then click on
the services link and verify that the perfSONAR service is deployed.
It would be nice to also include some suggestions about what
to do if/when the service isn't there.
IE, if it says it is running JDK 1.4.2, figure out how
to uninstall the old Java, and reinstall with JDK 1.5.0...
---
The install scripts need more info about eXist.
IE, at what point should you actually start eXist?
(The current doc's don't suggest starting it at all...)
How do I push my RRDMA configuration into the Exist DB?
Does it happen automagically? Or do I need to do it manually?
How can I verify that your RRDMA configuration is stored properly?
----
The test process should include a simple wild-carded get-key
query that will fetch all of the keys for all the interfaces
in the RRDMA. This will allow people to verify that their
local configuration is getting stored properly.
---
The use of date -dtoday '+%s' in scripts/ma-store-key.sh
is not portable. It doesn't work on Freebsd.
Perl is required so `perl -e print time` is a lot more
portable (or test the date command and then use the appropriate
arguments.).
---
I will send more info if/when I figure out my remaining problems....
--Joe
- Notes about perfSONAR 1.0 installation, Joe Metzger, 08/28/2006
- More Notes about perfSONAR 1.0 installation at ESnet., Joe Metzger, 08/29/2006
Archive powered by MHonArc 2.6.16.