Difference between revisions of "Federated AAI Configuration"
Line 3: | Line 3: | ||
== OpenNebula == | == OpenNebula == | ||
[[Fedcloud-tf:WorkGroups:_Federated_AAI:OpenNebula|OpenNebula]] | The full OpenNebula configuration including AAI settings: [[Fedcloud-tf:WorkGroups:_Federated_AAI:OpenNebula|OpenNebula Configuration]] | ||
== OpenStack<br> == | == OpenStack<br> == |
Revision as of 11:09, 22 August 2013
This page lists various AAI configurations for individual Cloud technologies.
OpenNebula
The full OpenNebula configuration including AAI settings: OpenNebula Configuration
OpenStack
Keystone
The generic documentation about how to enable VOMS support for Keystone can be found here[1].
When it comes to configuration, you will need the following files as a member of EGI FCTF.
/etc/keystone/voms.json
{ "fedcloud.egi.eu": { "tenant": "EGI_FCTF" }, "ops": { "tenant": "EGI_ops" } }
Of course, the Keystone tenants EGI_FCTF and EGI_ops need to exist prior to using this mapping for the first time.
In order to accept VOMS proxy certificates for VOs fedcloud.egi.eu and ops, the following files need to be created.
/etc/grid-security/vomsdir/ ├── fedcloud.egi.eu │ ├── voms1.egee.cesnet.cz.lsc │ └── voms2.grid.cesnet.cz.lsc └── ops ├── lcg-voms.cern.ch.lsc └── voms.cern.ch.lsc
They have to contain the following:
/etc/grid-security/vomsdir/fedcloud.egi.eu/voms1.egee.cesnet.cz.lsc:
/DC=org/DC=terena/DC=tcs/C=CZ/O=CESNET/CN=voms1.egee.cesnet.cz /C=NL/O=TERENA/CN=TERENA eScience SSL CA
/etc/grid-security/vomsdir/fedcloud.egi.eu/voms2.grid.cesnet.cz.lsc:
/DC=org/DC=terena/DC=tcs/C=CZ/O=CESNET/CN=voms2.grid.cesnet.cz /C=NL/O=TERENA/CN=TERENA eScience SSL CA
/etc/grid-security/vomsdir/ops/lcg-voms.cern.ch.lsc:
/DC=ch/DC=cern/OU=computers/CN=lcg-voms.cern.ch /DC=ch/DC=cern/CN=CERN Trusted Certification Authority
/etc/grid-security/vomsdir/ops/voms.cern.ch.lsc:
/DC=ch/DC=cern/OU=computers/CN=voms.cern.ch /DC=ch/DC=cern/CN=CERN Trusted Certification Authority