1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
*********************************************************
* How to migrate from the RLS to the LFC *
*********************************************************
Author : Sophie Lemaitre <Sophie.Lemaitre@cern.ch>
Date : 20/03/2005
Overview
========
The LCG File Catalog (LFC) is a data management solution provided by LCG.
The LFC allows to see the files in a typical hierarchical file system :
users can create directories and files as well as symlinks to them.
They can also create file replicas.
As a usual file system, permissions and Access Control Lists can be defined
on each of the files and directories.
Each of the files/directories have a GUID attached to them, which ensures
their uniqueness.
RLS to LFC Migration
====================
The Grid Deployment group provides a script to migrate the entries from the LRC and RMC into the LFC.
For efficiency reasons, the script will directly query the LRC and RMC databases, before using the LFC client calls to
insert the entries in the LFC.
The RLS entries, as well as their attributes that were defined by default in the LRC/RMC, will be migrated.
If user-defined attributes have been defined, they won't be migrated to the LFC.
However, if the RLS user-defined attributes fit in the LFC model, the script can be modified by the Grid Deployment group
to migrate them as well.
The Alias names that are stored in the RMC will be parsed in case they contain "/".
Everything between two "/" will be considered as a directory and will be created as such, as the LFC doesn't allow a file name
to contain any slashes.
Requirements
============
- LFC server running :
----------------------
We assume you have an instance of an LFC server running on a given machine, with a database backend (Oracle or MySQL).
For this, please refer to the LFC Administrator's guide or the installation notes provided with the LFC RPMs.
We also assume you have created a base hierarchy as described in the LFC Installation guide.
We recommend that you create the following directories :
- /grid
- /grid/<VO> for each VO you plan on supporting.
- LFC-client :
--------------
The LFC client must be installed on the machine where the migration script will be run.
For this, please refer to the LFC Administrator's guide or the installation notes provided with the LFC RPMs.
The LFC_HOST should be set to the full hostname of the LFC server :
> export LFC_HOST=<full_LFC_server_hostname>
- Perl DBI and DBD modules :
----------------------------
As the script is written in Perl, Perl should be installed on the machine where the migration script will be run.
The perl DBI module must also be installed.
And, depending on the RLS database backend vendor (Oracle or MySQL), either the Oracle or MySQL DBD module must be installed as well.
- For Oracle :
--------------
To query the RLS database, there has to be a "tnsnames.ora" file containing its description.
The following environment variables should be set :
- $TNS_ADMIN : directory where the "tnsnames.ora" file resides.
- $ORACLE_HOME
Running the migration script
============================
The migration script should be run as a user having the right to write into the <path> directory.
In other words, the primary group of the user should be the group owning the LFC <path> directory.
To run the migration script, you need to specify the following parameters :
- RLS database vendor : "Oracle" or "MySQL"
- Host : either the RLS Oracle database SID or the RLS MySQL server host
- LRC and RMC usernames,
- LRC and RMC passwords,
- Path : the directory where the RLS entries will be migrated,
Examples :
----------
For Oracle :
> cd RLS-migration/bin
> ./migrate_RLS_entries --db-vendor Oracle --sid rlsdev01 \
--lrc-user lcg2_alice_lrc --lrc-passwd lcg2lrcalice \
--rmc-passwd lcg2rmcalice --rmc-user lcg2_alice_rmc \
--path /grid/atlas &> migration.out &
The "migration.out" file will contain the commands issued, as well as the potential errors.
For MySQL :
> cd RLS-migration/bin
> ./migrate_RLS_entries --db-vendor MySQL --host localhost \
--lrc-user lrc_user --lrc-passwd lrc_password \
--rmc-user rmc_user --rmc-passwd rmc_password \
--path /grid/zeus &> migration.out &
The "migration.out" file will contain the commands issued, as well as the potential errors.
Contacts
========
For information, help, or in case you want the script to be modified to integrate the user-defined
attributes to the migration script, please contact :
Sophie.Lemaitre@cern.ch
|
