Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
cta
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Harbor Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
dCache
cta
Commits
316ae547
Commit
316ae547
authored
9 years ago
by
Giuseppe Lo Presti
Browse files
Options
Downloads
Patches
Plain Diff
First draft of the upgrade instructions, need some reviewing
parent
ec538fce
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ReleaseNotes
+90
-40
90 additions, 40 deletions
ReleaseNotes
with
90 additions
and
40 deletions
ReleaseNotes
+
90
−
40
View file @
316ae547
...
...
@@ -19,63 +19,113 @@
Packaging changes
-----------------
- CASTOR 2.1.15-10 has been recompiled against xrootd 4.2.1.
During the upgrade the xrootd 4.2.1 RPMs will need to be available,
otherwise the upgrade will because of missing dependencies.
otherwise the upgrade will
fail
because of missing dependencies.
Upgrade Instructions from 2.1.15-9
----------------------------------
Disk servers
------------
Stager
------
The upgrade of the stager to 2.1.15-10 can be performed online while the system is running.
However, one need to make sure that after the 2nd step, the xrootd daemons in the
diskservers are NOT restarted until the RPMs are upgraded at the 4th step.
Instructions
------------
1. Upgrade the STAGER database using the stager_2.1.15-9_to_2.1.15-10.sql
upgrade script available from:
- http://cern.ch/castor/DIST/CERN/savannah/CASTOR.pkg/2.1.15-*/2.1.15-10/dbupgrades
2. Configure the diskservers with the appropriate public keys for xroot, as
detailed below in the disk servers section, and update the xrd.cf.server
config file accordingly. If the tape servers are configured to use the
XROOT protocol, then the Tape servers section below must be followed as well.
3. Upgrade the software on the head nodes.
Note: All daemons involved in the upgrade will be restarted automatically.
4. Upgrade the software on the diskservers.
Note: All daemons involved in the upgrade will be restarted automatically.
5. Test the instance by running the test suite available from:
- http://cern.ch/castor/DIST/CERN/savannah/CASTOR.pkg/2.1.15-*/2.1.15-10/testsuite
6. Congratulations you have successfully upgraded to the 2.1.15-10 release
of CASTOR.
Central services (CUPV, VMGR, VDQM, Nameserver)
-----------------------------------------------
The upgrade of the central services to 2.1.15-10 can be performed online while
the system is running.
Instructions
------------
1. Apply the appropriate database upgrade scripts from:
- http://cern.ch/castor/DIST/CERN/savannah/CASTOR.pkg/2.1.15-*/2.1.15-10/dbupgrades
2. Update the software to use the 2.1.15-10 RPMs. Note: All
daemons involved in the upgrade will be restarted automatically.
3. Upgrade complete.
Disk servers' xrootd configuration
----------------------------------
The XROOT libxrdxcastor2acc.so authorisation plugin is responsible for
authenticating disk server to disk server requests. The location of the
corresponding public key is specified by the following parameter within
/etc/xrd.cf.server:
The XROOT libxrdxcastor2acc.so authorisation plugin is responsible for
authenticating disk server to disk server requests. The location of the
corresponding public key is specified by the following parameter within
/etc/xrd.cf.server:
xcastor2.publickey default /opt/xrootd/keys/pkey.pem
xcastor2.publickey default /opt/xrootd/keys/pkey.pem
The following example shell commands can be modified accordingly (the second
line) to produce a pair of public and private keys for signing and
authenticating disk server to disk server XROOT requests:
The following example shell commands can be modified accordingly (the second
line) to produce a pair of public and private keys for signing and
authenticating disk server to disk server XROOT requests:
openssl genrsa -out key.pem 512
openssl req -new -subj "/C=CH/ST=Geneva/L=Geneva/O=CERN/OU=IT/CN=castor-xroot-hostname.cern.ch/emailAddress=castor-operations@cern.ch" -inform PEM -key key.pem -outform PEM -out certreq.pem
openssl x509 -days 3650 -signkey key.pem -in certreq.pem -req -out cert.pem
openssl x509 -pubkey -in cert.pem > pkey.pem
rm -rf cert.pem certreq.pem
chmod 0400 key.pem
openssl genrsa -out key.pem 512
openssl req -new -subj "/C=CH/ST=Geneva/L=Geneva/O=CERN/OU=IT/CN=castor-xroot-hostname.cern.ch/emailAddress=castor-operations@cern.ch" -inform PEM -key key.pem -outform PEM -out certreq.pem
openssl x509 -days 3650 -signkey key.pem -in certreq.pem -req -out cert.pem
openssl x509 -pubkey -in cert.pem > pkey.pem
rm -rf cert.pem certreq.pem
chmod 0400 key.pem
Tape servers' configuration
---------------------------
Tape servers
------------
When the tapeserverd daemon is configured to use the XROOT protocol it will
need to sign its XROOT requests so that the CASTOR disk servers will be able
to authenticate it. The tapeserverd daemon signs its XROOT requests using a
private key. The location of the private key is specified by the following
parameter within /etc/castor/castior.conf:
When the tapeserverd daemon is configured to use the XROOT protocol it will
need to sign its XROOT requests so that the CASTOR disk servers will be able
to authenticate it. The tapeserverd daemon signs its XROOT requests using a
private key. The location of the private key is specified by the following
parameter within /etc/castor/castior.conf:
TapeServer XrootPrivateKey /opt/xrootd/keys/tape_key.pem
TapeServer XrootPrivateKey /opt/xrootd/keys/tape_key.pem
The XROOT libxrdxcastor2acc.so authorisation plugin is responsible for
authenticating tape server requests when they arrive at a CASTOR disk server.
The plugin authenticates the requests using a public key. The location of
the public key is specified by the following parameter within
/etc/xrd.cf.server:
The XROOT libxrdxcastor2acc.so authorisation plugin is responsible for
authenticating tape server requests when they arrive at a CASTOR disk server.
The plugin authenticates the requests using a public key. The location of
the public key is specified by the following parameter within
/etc/xrd.cf.server:
xcastor2.publickey tape /opt/xrootd/keys/tape_pkey.pem
xcastor2.publickey tape /opt/xrootd/keys/tape_pkey.pem
The following example shell commands can be modified accordingly (the second
line) to produce a pair of public and private keys for signing and
authenticating tapeserverd XROOT requests:
The following example shell commands can be modified accordingly (the second
line) to produce a pair of public and private keys for signing and
authenticating tapeserverd XROOT requests:
openssl genrsa -out tape_key.pem 512
openssl req -new -subj "/C=CH/ST=Geneva/L=Geneva/O=CERN/OU=IT/CN=castor-xroot-hostname.cern.ch/emailAddress=castor-operations@cern.ch" -inform PEM -key tape_key.pem -outform PEM -out certreq.pem
openssl x509 -days 3650 -signkey tape_key.pem -in certreq.pem -req -out cert.pem
openssl x509 -pubkey -in cert.pem > tape_pkey.pem
rm -rf cert.pem certreq.pem
chmod 0400 tape_key.pem
openssl genrsa -out tape_key.pem 512
openssl req -new -subj "/C=CH/ST=Geneva/L=Geneva/O=CERN/OU=IT/CN=castor-xroot-hostname.cern.ch/emailAddress=castor-operations@cern.ch" -inform PEM -key tape_key.pem -outform PEM -out certreq.pem
openssl x509 -days 3650 -signkey tape_key.pem -in certreq.pem -req -out cert.pem
openssl x509 -pubkey -in cert.pem > tape_pkey.pem
rm -rf cert.pem certreq.pem
chmod 0400 tape_key.pem
------------
- 2.1.15-9 -
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment