a multi-objective bisexual reproduction genetic algorithm for ...

102
mycapw
[enter]
During the above process, a hash number is generated and used as part of the
file name. Please note this number for use in the next steps. Run the script name
printed at the end of the prior install, substituting the hex hash number printed by the
above process in place of the shown below, adding the “-default” argument:
/usr/local/globus/setup/globus_simple_ca__setup/setup-gsi -default
y
q
The file /root/.globus/simpleCA/private/cakey.pem is the CA’s private key and
should not be given out to anyone else. The file /root/.globus/simpleCA/cacert.pem
contains the CA’s public key.
The following is used to install the CA’s certificate on each of the other grid
machines. /root/.globus/simpleCA/globus_simple_ca__setup-0.9.tar.gz is the
file containing the public CA key and other information needed to participate in this
grid. This must be copied to each of the other machines and installed using the gptbuild
command.
First, on machine m2, use ftp to copy the file
/root/.globus/simpleCA/globus_simple_ca__setup-0.9.tar.gz to the directory
/usr/src/ of each of the other grid machines. This can be done in two steps by ftp-ing
them to the directory /home/globususer on each of those machines using globususer
ID. Then, using root, this file can be moved to the directory /usr/src. Next, issue the
following commands on each of those machines as root:
gpt-build /usr/src/globus_simple_ca__setup-0.9.tar.gz
gpt-postinstall
/usr/local/globus/setup/globus_simple_ca__setup/setup-gsi -default
y
q
B.2.9 Requesting and Signing Gatekeeper Certificates for Servers
On each of the server machines (m2 and m3), we perform the following steps to
request and sign certificates:
grid-cert-request -host
Use ftp or e-mail (if available and using the adminca ID) to copy the file
/etc/grid-security/hostcert_request.pem to the CA machine and put it into the directory
/root. On the CA machine, as root, sign the certificate using the following: