Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
IGI (based on EMI) Installation and Configuration | ||||||||
Line: 167 to 168 | ||||||||
After service installation to have a look if all were installed in a proper way, you could have a look to Service BDII_top Reference Card![]() | ||||||||
Changed: | ||||||||
< < | StoRM installation and Configuration | |||||||
> > | !StoRM installation and Configuration | |||||||
Changed: | ||||||||
< < | Have a look to the section Repository Settings of this documentation, ensure to have the common repo files. | |||||||
> > | Have a look to the section Repository Settings and ensure that you have the common repo files. | |||||||
Before starting the installation procedure remember to clean all yum cache and headers:
yum clean all | ||||||||
Changed: | ||||||||
< < | StoRM Prerequisites | |||||||
> > | StoRM Prerequisites | |||||||
Host certificate installation: | ||||||||
Changed: | ||||||||
< < | Hosts participating to the StoRM-SE (FE, BE and GridFTP hosts) must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively: | |||||||
> > | Hosts participating to the StoRM-SE (FE, BE and GridFTP hosts) must be configured with X.509 certificates signed by a trusted Certification Authority (CA). Usually the hostcert.pem and hostkey.pem certificates are located in the /etc/grid-security/ directory, and they must have permission 0644 and 0400 respectively: | |||||||
Check existence | ||||||||
Line: 200 to 201 | ||||||||
ACL SUPPORTIf you are installing a new StoRM this check must be done, if you are updating your install or your storage has ACL you can step out to this issue. | ||||||||
Changed: | ||||||||
< < | StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly. | |||||||
> > | StoRM uses the ACLs on files and directories to implement the security model. Doing so, StoRM uses the native access to the file system. Therefore in order to ensure a proper running, ACLs need to be enabled on the underlying file system (sometime they are enabled by default) and work properly. | |||||||
Check ACL:
| ||||||||
Line: 242 to 243 | ||||||||
This is valid for different file system types (i.e., ext3, xfs, gpfs and others).
EXTENDED ATTRIBUTE SUPPORT | ||||||||
Changed: | ||||||||
< < | StoRM uses the Extended Attributes (EA) on files to store some metadata related to the file (e.g. the checksum value); therefore in order to ensure a proper running, the EA support needs to be enabled on the underlying file system and work properly. | |||||||
> > | StoRM uses the Extended Attributes (EA) on files to store some metadata related to the file (e.g. the checksum value); therefore in order to ensure a proper running, the EA support needs to be enabled on the underlying file system and work properly. | |||||||
Note: Depending on OS kernel distribution, for Reiser3, ext2 and ext3 file systems, the default kernel configuration should not enable the EA.
Check Extended Attribute Support :
| ||||||||
Line: 273 to 274 | ||||||||
Changed: | ||||||||
< < | CAa installation: | |||||||
> > | CAs installation: | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
yum install ca-policy-egi-core Service installation | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
yum install emi-storm-backend-mp yum install emi-storm-frontend-mp yum install emi-storm-globus-gridftp-mp | ||||||||
Line: 290 to 291 | ||||||||
Service Configuration | ||||||||
Changed: | ||||||||
< < | To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter: | |||||||
> > | To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter: | |||||||
- ig-site-info.def![]() - ig-users.conf ![]() |