blogs

SimpleCA for MyProxy : NOTES

| | | |

IMPORTANT SimpleCA Storage LOCATIONS

The private key of the CA is stored in /root/.globus/simpleCA//private/cakey.pem
The public CA certificate is stored in /root/.globus/simpleCA//cacert.pem

The distribution package built for this CA is stored in

/root/.globus/simpleCA//globus_simple_ca_74f9a25f_setup-0.18.tar.gz

This file must be distributed to any host wishing to request
certificates from this CA.

Creating a PAM-retrievable User Credential Inside MyProxy

| |

Creating a User Credential Inside MyProxy

myproxy-admin-adduser -c "Jill Gemmill" -l jgemmill-n -a


Retrieved using myproxy-logon and BlazerID password



owner:

/O=Grid/OU=GlobusTest/OU=simpleCA-juster.lab.ac.uab.edu/OU=lab.ac.uab.edu/CN=Jill Gemmill

username: jgemmill

retrieval policy: *

timeleft: 8759:28:04 (365.0 days)

juster:/etc # cd /etc/grid-security


A private key and a certificate request has been generated with the subject:


/O=Grid/OU=GlobusTest/OU=simpleCA-juster.lab.ac.uab.edu/OU=lab.ac.uab.edu/CN=Jill Gemmill

BackupExec Quirk: restart media server after adding unix hosts

|

[phpwiki]
It seems you need to restart the backup server after you add new unix
hosts. I added some hosts at the start of the week and after that all the
backups started failing with

"The connection to the data backup has been lost"

This happened for both existing (and working unix agents) and the new ones
I defined.

It took a little while to figure this out. At first I thought it might be
firewall related but looking at the network traffic showed that wasn't the
case. The debug output of agent.be (see agent.be -help) wasn't all that
useful and seemed to indicate normal operation.

VMware Server e.x.p. MUI notes

|

[phpwiki]
After installing the new free VMware Server product I couldn't get the
vmware-mui-distrib tarball to install. It kept aborting with the message
"Failure" after saying it detected an previous install of vmware. Duh!, I
had put it there.

The previous install wasn't actually the problem though. I found the
[limited instrux for the new release|http://www.vmware.com/support/server/doc/releasenotes_server_beta.html#install]
and the said make sure libdb.so.3 is installed, which comes in the
compat-db rpm, btw. I installed it, still no luck.

Looking at the perl code it seemed to be looking for a previous install of

Certs needed to install MyProxy G4

| | | | | | | |

Need a server cert that has no password. Commands are:

(1) change directory into the grid-security directory: cd /etc/grid-security

(2) Generate the server key (with password): openssl genrsa -des3 -out server.key 1024

(3) Generate certificate *without a password*: openssl rsa -in server.key -out server.pem

(4) Create CSR (Certificate Signing Request) to affirm that the server key is valid. The server.pem is used in place of server.key as we don’t require a password:
openssl req -new -key server.pem -out server.csr

The information you are about to be asked to enter information will be incorporated into your certificate request as the Distinguished Name or a DN of the signed cert. [ If you enter ‘.’, the field will be left blank ]

[Devel] Ok, few DAKOTA issues here,

Ok, few DAKOTA issues here,

1) I tried running DAKOTA on CAHABA (note: mpirun in CAHABA is taken from /usr/local/lam/7.0.5/pgi/4.0/PBSPro/5.4.0/bin/mpirun) for some example test cases given along with the distribution and it gave me the same MPI_Init error message at the end.

so i used mpich mpirun in CAHABA i.e (mpirun taken from /usr/local/mpich/1.2.6/gnu/3.4.0/PBSPro/5.4.0/smp/bin/mpirun) and it ran without any MPI_Init error message at the end. This worked even for np greater than 1 as well.

on cahaba:
/usr/local/mpich/1.2.6/gnu/3.4.0/PBSPro/5.4.0/smp/bin/mpirun -np 2 dakota -i dakota_pce.in

Procedure to update packages on Rocks

Hi,

Listed below is a outline of the steps to be followed to update RPM packages on medusa.

1) Download or create the RPM and put this rpm in /home/install/contrib/4.1/arch/RPMS

2) Install it on the front end as follows:

# rpm -Uvh /path/to/created-or-downloaded RPM

3) Once the required RPM is installed on the front-end it requires to distributed to the compute nodes.This is done as follows:

# /home/install/site-profiles/4.1/nodes

# cp skeleton.xml extend-compute.xml

Inside extend-compute.xml, add the package name by changing the section from:

Optimization with DAKOTA

To understand and use DAKOTA (Design and Analysis Kit for Optimization and Terascale Applications) toolkit certain basic concepts of optimization
should be known,

In mathematics, optimization is concerned with finding the maxima and minima of functions, possibly subject to constraints. Example: maximize the profit of a manufacturing operation while ensuring that none of the resources exceed certain limits and also satisfying as much of the demand faced as possible. Optimization has many practical applications in logistics and design problems.

In computer science, optimization is the process of improving a system in certain ways to increase the effective execution speed and/or bandwidth, or to reduce memory requirements. Despite its name, optimization does not necessarily mean finding the optimum solution to a problem. Often this is not possible, and heuristic algorithms must be used instead.

javaspaces

[phpwiki]
found out about
[javaspaces|http://webapp.lab.ac.uab.edu/bookmarks/tag/javaspaces] today
through some features in the up coming dakota interface. seems to be an
interesting framework for a distributed memory space in java that can be
treated as a container for distrubuted processes. the driving application
or job creates tasks that are handled by workers, who select the task out
of the job space. this allows a model of processing where workers
contribute what they can to the job execution. faster workers process more
tasks that slower works.

In the simple example of the

Mambo modifications

Mambo has now been modified to work with options similar to limbo
like external authorization, auto login and auto user registration.

The names of the variables respectively are
1) $mosConfig_ect_auth

2) $mosConfig_auto_login

3) $mosConfig_auto_user_registration

The files that have been modified for this to work are includes/mambo.php, index.php and modules/mod_login.php.

However, currently the entire mambo directory is being protected by shibboleth, and the anonymous user scenario is still not in place, which i am currently working on.

Syndicate content