Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
VOMS System Administrator Guide
| ||||||||
Line: 125 to 125 | ||||||||
The gLite 3.2 YAIM configuration should work in your EMI installation. Just check that no gLite-specific paths are referenced in your configuration and possibly integrate it with the new options provided by EMI VOMS. | ||||||||
Added: | ||||||||
> > | ![]() | |||||||
In order to configure VOMS, place the YAIM configuration files in your favorite directory and launch the following command:
/opt/glite/yaim/bin/yaim -c -s site-info.def -n VOMS | ||||||||
Added: | ||||||||
> > |
0.0.0.0.1 Upgrading a VOMS Oracle installationOn Oracle, a database schema upgrade is required when upgrading from gLite 3.2 or EMI 1. The schema upgrade should be performed before running the YAIM configuration following this procedure:
| |||||||
0.0.0.0.1 Known issues for the gLite 3.2 to EMI upgrade0.0.0.0.1.1 AUP is not shown correctly after upgrade to EMI | ||||||||
Line: 156 to 169 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
0.0.1 Configuration |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
VOMS System Administrator Guide
| ||||||||
Line: 277 to 277 | ||||||||
mysql -uroot -p | ||||||||
Deleted: | ||||||||
< < | 0.0.0.0.1 Migrating database accountsTBD | |||||||
0.1 TroubleshootingSee the VOMS known issues page. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
VOMS System Administrator Guide
| ||||||||
Line: 158 to 159 | ||||||||
0.0.1 Configuration | ||||||||
Added: | ||||||||
> > | 0.0.0.1 TOMCAT file limitsIt is safe to configuretomcat to have a reasonable limit for the number of open files that can be opened
by the tomcat process. The default file limit can be modified by editing the /etc/security/limits.conf file:
tomcat soft nofile 63536 tomcat hard nofile 63536 | |||||||
0.0.0.1 Configuring the database backend | ||||||||
Line: 178 to 190 | ||||||||
Create the necessary users and databases in Oracle. Please see the Oracle manuals for details. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | 0.0.0.0.0.1 Oracle instantclient library pathIn order to properly configure the library load path for the VOMS oracle backend, create a file namedoracle-x86_64.conf in the /etc/ld.so.conf.d directory, with the following content: | |||||||
Added: | ||||||||
> > | /usr/lib/oracle/10.2.0.4/client64/libIn case you use a different version of the the instantclient libraries (not recommended) , adjust the above accordingly. | |||||||
0.0.0.1 Configuring the VOMS server with YAIM |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
VOMS System Administrator Guide
| ||||||||
Line: 180 to 180 | ||||||||
0.0.0.1 Configuring the VOMS server with YAIM | ||||||||
Changed: | ||||||||
< < | 0.0.0.0.1 YAIM siteinfo and
| |||||||
> > | Check the VOMS YAIM configuration guide. | |||||||
0.1 Service operation |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
VOMS System Administrator Guide
| ||||||||
Changed: | ||||||||
< < | Introduction | |||||||
> > | 1 Introduction | |||||||
Changed: | ||||||||
< < | Quickstart guide | |||||||
> > | The Virtual Organization Membership Service (VOMS) is an attribute authority which serves as central repository for VO user authorization information, providing support for sorting users into group hierarchies, keeping track of their roles and other attributes in order to issue trusted attribute certificates and SAML assertions used in the Grid environment for authorization purposes. | |||||||
Changed: | ||||||||
< < | Prerequisistes and recommendations | |||||||
> > | VOMS is composed of two main components: | |||||||
Changed: | ||||||||
< < | Hardware | |||||||
> > |
0.1 Quickstart guideThis quickstart guide covers the MySQL installation of VOMS.
0.2 Prerequisistes and recommendations0.2.1 Hardware | |||||||
| ||||||||
Changed: | ||||||||
< < | Software | |||||||
> > | 0.0.1 Software | |||||||
Changed: | ||||||||
< < | Operating system | |||||||
> > | 0.0.0.1 Operating system | |||||||
| ||||||||
Changed: | ||||||||
< < | Preinstalled software | |||||||
> > | 0.0.0.1 Preinstalled softwareBesides the usual OS and EMI release packages, you will need theoracle-instantclient-basic package,
version 10.2.0.4, installed on the system (in case of an Oracle-based installation).
All the other dependencies are resolved by the installation of the VOMS metapackages, i.e.:
0.1 Recommended deployment scenariosA single-node installation, with the hardware recommendations given above should serve well most scenarios. It is not recommended to deploy a large number of VOs (> 20) on a single installation. This is due to an architectural limitation of VOMS (i.e., independent web applications and service for each VO) that will be solved in a future VOMS release.0.2 Installation instruction0.2.1 Software repositoriesFollow the general EMI 1 or 2 installation instructions. VOMS requires that the OS and EPEL repositories are active and correctly configured on the target machine. If oracle is used, a repository where Oracle packages are available should also be provided. Otherwise Oracle packages need to be installed manually.0.2.2 Clean installation
0.2.3 Upgrade installation0.2.3.1 Upgrade from gLite 3.2 VOMS0.2.3.1.1 Install and configure a SL5 or SL6 X86_64 EPEL machineIn order to install the EMI VOMS metapackage you will need a clean SL5 or SL6 X86_64 machine with the EPEL repository configured and the emi release package correctly installed. SL5, as configured by gLite 3.2, is not suitable for installing the EMI VOMS since gLite uses the DAG repository, which is alternative and incompatible with EPEL. Once you have a clean machine configured, install theemi-voms-mysql metapackage without launching yaim configuration.
0.2.3.1.2 VOMS database dump and YAIM configurationOn your existing gLite 3.2 VOMS node dump the VOMS database for all the VOs issuing the following command:mysqldump -uroot -p<MYSQL_ROOT_PASSWORD> --all-databases --flush-privileges > voms_database_dump.sqlYou will then copy the dump file on the new EMI VOMS node. Remember to save your YAIM configuration (in most cases, site-info.def and services/glite-voms in your siteinfo directory) and
copy it on the new EMI VOMS node.
0.2.3.1.3 Restoring the VOMS database on the EMI nodeYou should now have themysql daemon installed in your EMI machine (it was installed as a dependency of the emi-voms-mysql metapackage).
Follow the instructions in this section to properly configure the mysql root account.
Once the root account is configured and working (check that you can login issuing the command mysql -uroot -p<MYSQL_ROOT_PASSWORD> ), you can restore the VOMS database
issuing the following command:
mysql -uroot -p<PASSWORD> < voms_database_dump.sql 0.2.3.1.4 Configuring VOMS on the EMI nodeThe gLite 3.2 YAIM configuration should work in your EMI installation. Just check that no gLite-specific paths are referenced in your configuration and possibly integrate it with the new options provided by EMI VOMS. In order to configure VOMS, place the YAIM configuration files in your favorite directory and launch the following command:/opt/glite/yaim/bin/yaim -c -s site-info.def -n VOMS 0.2.3.1.5 Known issues for the gLite 3.2 to EMI upgrade0.2.3.1.5.1 AUP is not shown correctly after upgrade to EMIAfter upgrading a gLite 3.2 VOMS Admin the URL pointing to the default AUP text (/var/glite/etc/voms-admin/https://<voms-hostname>:8443/voms/<vo>/aup/load.actionThe default URL for the new aup is: file:/etc/voms-admin/<vo>/vo-aup.txt 0.2.3.2 Upgrade from EMI 1 VOMS0.2.3.2.1 Upgrading an SL5 EMI 1 installation
0.2.4 Configuration0.2.4.1 Configuring the database backend0.2.4.1.1 MySQL configurationMake sure that the MySQL administrator password that you specify in the YAIM VOMS configuration files matches the password that is set for the root MySQL account. Yaim configuration script does not set it for you. If you want to set a MySQL administrator password:
0.2.4.1.2 Oracle configurationCreate the necessary users and databases in Oracle. Please see the Oracle manuals for details.0.2.4.2 Configuring the VOMS server with YAIM 0.2.4.2.1 YAIM siteinfo and
| |||||||
Changed: | ||||||||
< < | Depending on the database backend that your installation will use, you will need | |||||||
> > | In order to migrate VOMS to a different machine, the following items will need to be migrated: | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Changed: | ||||||||
< < | installed on your system. | |||||||
> > | 0.0.0.1 VOMS configuration migration | |||||||
Changed: | ||||||||
< < | Recommended deployment scenarios | |||||||
> > | To migrate VOMS configuration, just archive the contents of the YAIM configuration directory and move this archive to the new installation. In case YAIM is not used, you will need to archive and move the following directories: | |||||||
Changed: | ||||||||
< < | Installation instruction | |||||||
> > | /etc/voms/* (EMI1 VOMS) /etc/voms-admin/* (EMI1 VOMS Admin) | |||||||
Changed: | ||||||||
< < | Software repositories | |||||||
> > | $GLITE_LOCATION/etc/voms/* (gLite 3.2 VOMS) $GLITE_LOCATION_VAR/etc/voms-admin/* (glite 3.2 VOMS Admin) | |||||||
Changed: | ||||||||
< < | Clean installation | |||||||
> > | 0.0.0.1 VOMS database migration (MySQL backend) | |||||||
Changed: | ||||||||
< < | Upgrade installation | |||||||
> > | In order to dump the contents of the VOMS datbase issue the following command on the original VOMS installation machine: | |||||||
Changed: | ||||||||
< < | Upgrade from gLite 3.2 VOMS | |||||||
> > | mysqldump -uroot -p<MYSQL_ROOT_PASSWORD> --all-databases --flush-privileges > voms_database_dump.sql | |||||||
Changed: | ||||||||
< < | Upgrade from EMI 1 VOMS | |||||||
> > | This database dump contains all the VOMS data and can be moved to the new VOMS installation machine. | |||||||
Changed: | ||||||||
< < | Configuration | |||||||
> > | To restore the database contents on the new VOMS installation machine, ensure that: | |||||||
Changed: | ||||||||
< < | --++ Service operation | |||||||
> > | The database content can then be restored using the following command:
mysql -uroot -p<PASSWORD> < voms_database_dump.sql | |||||||
Changed: | ||||||||
< < | Validation and monitoring | |||||||
> > | 0.0.0.0.1 Migrating database accounts | |||||||
Changed: | ||||||||
< < | Migration | |||||||
> > | TBD | |||||||
Deleted: | ||||||||
< < | --++ Troubleshooting | |||||||
Added: | ||||||||
> > | 0.1 Troubleshooting | |||||||
Added: | ||||||||
> > | See the VOMS known issues page. | |||||||
-- AndreaCeccanti - 2012-03-03 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > | VOMS System Administrator Guide
IntroductionQuickstart guidePrerequisistes and recommendationsHardware
SoftwareOperating system
Preinstalled softwareDepending on the database backend that your installation will use, you will need
Recommended deployment scenariosInstallation instructionSoftware repositoriesClean installationUpgrade installationUpgrade from gLite 3.2 VOMSUpgrade from EMI 1 VOMSConfiguration--++ Service operationValidation and monitoringMigration--++ Troubleshooting -- AndreaCeccanti - 2012-03-03 |