Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "HOWTO16 How to enable a Virtual Organisation on a EGI Federated Cloud"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}}  
{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}}  


[[Category:Operations_Manuals]]
<br>
 
 
= Support a new Virtual Organisation in the EGI Federated Cloud =
'''This process is for user communities without an existing Virtual Organization, if you already have a VO, see [[Fedcloud-tf:Support_a_new_Virtual_Organisation#Support_an_already_existing_Virtual_Organisation_in_the_EGI_Federated_Cloud | Support an already existing Virtual Organisation in the EGI Federated Cloud]].'''
 
In order to register a new Virtual Organization in the EGI Federated Cloud, you need to gather the following information:
 
* Name of the new VO
* Contact information for the VO manager (full name and an e-mail address)
* Brief description of the VO and its user community
 
and open a GGUS ticket for the [https://ggus.eu/?mode=ticket_submit EGI Federated Cloud SU] with the subject
 
New VO Registration Request - VO_NAME
 
where ''VO_NAME'' represents the VO name of your choice in compliance with EGI's guidelines.
 
The Support Team will inform you on how and when to register the new VO with the [https://operations-portal.egi.eu/vo/registration EGI Operations Portal].
 
= Support an already existing Virtual Organisation in the EGI Federated Cloud =
'''This process is for user communities with an existing Virtual Organization, if you do not have a VO, see [[Fedcloud-tf:Support_a_new_Virtual_Organisation#Support_a_new_Virtual_Organisation_in_the_EGI_Federated_Cloud | Support a new Virtual Organisation in the EGI Federated Cloud]].'''
 
In order to register an existing Virtual Organization in the EGI Federated Cloud, you need to provide the following information:


* Name of the VO (as registered in the [http://operations-portal.egi.eu/vo/search EGI Operations Portal])
This page provides information how to enable a Virtual Organisation on a EGI Federated Cloud


and open a GGUS ticket for the [https://ggus.eu/?mode=ticket_submit EGI Federated Cloud SU] with the subject


Existing VO Registration Request - VO_NAME


where ''VO_NAME'' represents the VO name registered with the EGI.
= OpenNebula  =


The Support Team will contact you and guide you through the rest of the process.
Assuming that you are using ''OpenNebula v4.x'', ''rOCCI-server v1.0.x'' and [[Fedcloud-tf:ResourceProviders:OpenNebula#Integration_with_Perun|Integration with Perun]], you have to perform the following steps to support a new Virtual Organization:


= Enable a Virtual Organisation on a EGI Federated Cloud site using OpenNebula =
*Configure [[Fedcloud-tf:Support a new Virtual Organisation#VOMS.2FGridSite|VOMS/GridSite]]
Assuming that you are using ''OpenNebula v4.x'', ''rOCCI-server v1.0.x'' and [[Fedcloud-tf:ResourceProviders:OpenNebula#Integration_with_Perun | Integration with Perun]], you have to perform the following steps to support a new Virtual Organization:
*Create a new group in [[Fedcloud-tf:Support a new Virtual Organisation#OpenNebula|OpenNebula]]


* Configure [[Fedcloud-tf:Support_a_new_Virtual_Organisation#VOMS/GridSite | VOMS/GridSite]]
== VOMS/GridSite ==
* Create a new group in [[Fedcloud-tf:Support_a_new_Virtual_Organisation#OpenNebula | OpenNebula]]


== VOMS/GridSite ==
For each allowed VO, you need a subdirectory in /etc/grid-security/vomsdir/ that contains the ''lsc'' files of all truted VOMS servers for the given VO. The ''lsc'' files must be named as the fully qualified host name of the VOMS server with an ''lsc'' extension and must contain:  
For each allowed VO, you need a subdirectory in /etc/grid-security/vomsdir/ that contains the ''lsc'' files of all truted VOMS servers for the given VO. The ''lsc'' files must be named as the fully qualified host name of the VOMS server with an ''lsc'' extension and must contain:


* First line: subject DN of the VOMS server host certificate
*First line: subject DN of the VOMS server host certificate  
* Second line: subject DN of the CA that issued the VOMS server host certificate
*Second line: subject DN of the CA that issued the VOMS server host certificate


For example, for the ''fedcloud.egi.eu'' VO, these would be:
For example, for the ''fedcloud.egi.eu'' VO, these would be:  
<pre>
<pre>$ cat /etc/grid-security/vomsdir/fedcloud.egi.eu/voms1.egee.cesnet.cz.lsc
$ cat /etc/grid-security/vomsdir/fedcloud.egi.eu/voms1.egee.cesnet.cz.lsc
/DC=org/DC=terena/DC=tcs/OU=Domain Control Validated/CN=voms1.egee.cesnet.cz
/DC=org/DC=terena/DC=tcs/OU=Domain Control Validated/CN=voms1.egee.cesnet.cz
/C=NL/O=TERENA/CN=TERENA eScience SSL CA
/C=NL/O=TERENA/CN=TERENA eScience SSL CA
Line 57: Line 29:
/DC=org/DC=terena/DC=tcs/OU=Domain Control Validated/CN=voms2.grid.cesnet.cz
/DC=org/DC=terena/DC=tcs/OU=Domain Control Validated/CN=voms2.grid.cesnet.cz
/C=NL/O=TERENA/CN=TERENA eScience SSL CA
/C=NL/O=TERENA/CN=TERENA eScience SSL CA
</pre>
</pre>  
== OpenNebula  ==


== OpenNebula ==
For each allowed VO, you need to create a group in OpenNebula with a matching name. All groups with names matching known VOs are automatically populated and managed by Perun, see [[Fedcloud-tf:ResourceProviders:OpenNebula#Integration_with_Perun|Integration with Perun]] for details.  
For each allowed VO, you need to create a group in OpenNebula with a matching name. All groups with names matching known VOs are automatically populated and managed by Perun, see [[Fedcloud-tf:ResourceProviders:OpenNebula#Integration_with_Perun | Integration with Perun]] for details.


For example, for the ''fedcloud.egi.eu'' VO, the command to create the appropriate group would be:
For example, for the ''fedcloud.egi.eu'' VO, the command to create the appropriate group would be:  
<pre>
<pre># the OpenNebula front-end
# the OpenNebula front-end
$ onegroup create fedcloud.egi.eu
$ onegroup create fedcloud.egi.eu
</pre>
</pre>  
= OpenStack  =
 
Assuming that you are using the [http://ifca.github.io/keystone-voms/ Keystone VOMS module] the steps needed are listed in the [https://keystone-voms.readthedocs.org/en/latest/configuration.html#allowed-vos VOMS module documentation].
 
== Keystone V2  ==
 
The configuration for the Keystone V2 authentitaion is as follows:


= Enable a Virtual Organisation on a EGI Federated Cloud site using OpenStack =
*Configure your LSC files according to the [http://italiangrid.github.io/voms/documentation/voms-clients-guide/3.0.3/#voms-trust VOMS documentation]
*Create a tenant for your new VO:


Assuming that you are using the [http://ifca.github.io/keystone-voms/ Keystone VOMS module] the steps needed are listed in the [https://keystone-voms.readthedocs.org/en/latest/configuration.html#allowed-vos VOMS module documentation].
$ keystone tenant-create --name &lt;tenant_name&gt; --description "Tenant for VO &lt;vo&gt;"


== Keystone V2 ==
*Add the mapping to your <code>voms.json</code> mapping. It must be proper JSON (you can check its correctness with [http://jsonlint.com/ online] or with <code>python -mjson.tool /etc/keystone/voms.json</code>). Edit the file, and add an entry like this:
The configuration for the Keystone V2 authentitaion is as follows:


* Configure your LSC files according to the [http://italiangrid.github.io/voms/documentation/voms-clients-guide/3.0.3/#voms-trust VOMS documentation]
* Create a tenant for your new VO:
$ keystone tenant-create --name <tenant_name> --description "Tenant for VO <vo>"
* Add the mapping to your <code>voms.json</code> mapping. It must be proper JSON (you can check its correctness with [http://jsonlint.com/ online] or with <code>python -mjson.tool /etc/keystone/voms.json</code>). Edit the file, and add an entry like this:
  {
  {
    "voname|FQAN": {
    "voname|FQAN": {
        "tenant": "tenant_name"
        "tenant": "tenant_name"
    }
    }
  }
  }
* Note that you can use the FQAN from the incoming proxy, so you can map a group within a VO into a tenant, like this:
 
*Note that you can use the FQAN from the incoming proxy, so you can map a group within a VO into a tenant, like this:
 
  {
  {
    "dteam": {
    "dteam": {
        "tenant": "dteam"
        "tenant": "dteam"
    },
    },
    "/dteam/NGI_IBERGRID": {
    "/dteam/NGI_IBERGRID": {
        "tenant": "dteam_ibergrid"
        "tenant": "dteam_ibergrid"
    }
    }
  }
  }


* Restart the Apache server, and it's done.
*Restart the Apache server, and it's done.
 
[[Category:Operations_Manuals]]

Revision as of 15:44, 11 May 2015

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home • Manuals • Procedures • Training • Other • Contact ► For: VO managers • Administrators




This page provides information how to enable a Virtual Organisation on a EGI Federated Cloud


OpenNebula

Assuming that you are using OpenNebula v4.x, rOCCI-server v1.0.x and Integration with Perun, you have to perform the following steps to support a new Virtual Organization:

VOMS/GridSite

For each allowed VO, you need a subdirectory in /etc/grid-security/vomsdir/ that contains the lsc files of all truted VOMS servers for the given VO. The lsc files must be named as the fully qualified host name of the VOMS server with an lsc extension and must contain:

  • First line: subject DN of the VOMS server host certificate
  • Second line: subject DN of the CA that issued the VOMS server host certificate

For example, for the fedcloud.egi.eu VO, these would be: 

$ cat /etc/grid-security/vomsdir/fedcloud.egi.eu/voms1.egee.cesnet.cz.lsc
/DC=org/DC=terena/DC=tcs/OU=Domain Control Validated/CN=voms1.egee.cesnet.cz
/C=NL/O=TERENA/CN=TERENA eScience SSL CA

$ cat /etc/grid-security/vomsdir/fedcloud.egi.eu/voms2.grid.cesnet.cz.lsc 
/DC=org/DC=terena/DC=tcs/OU=Domain Control Validated/CN=voms2.grid.cesnet.cz
/C=NL/O=TERENA/CN=TERENA eScience SSL CA

OpenNebula

For each allowed VO, you need to create a group in OpenNebula with a matching name. All groups with names matching known VOs are automatically populated and managed by Perun, see Integration with Perun for details.

For example, for the fedcloud.egi.eu VO, the command to create the appropriate group would be: 

# the OpenNebula front-end
$ onegroup create fedcloud.egi.eu

OpenStack

Assuming that you are using the Keystone VOMS module the steps needed are listed in the VOMS module documentation.

Keystone V2

The configuration for the Keystone V2 authentitaion is as follows:

  • Configure your LSC files according to the VOMS documentation
  • Create a tenant for your new VO:
$ keystone tenant-create --name <tenant_name> --description "Tenant for VO <vo>"
  • Add the mapping to your voms.json mapping. It must be proper JSON (you can check its correctness with online or with python -mjson.tool /etc/keystone/voms.json). Edit the file, and add an entry like this:
{
   "voname|FQAN": {
       "tenant": "tenant_name"
   }
}
  • Note that you can use the FQAN from the incoming proxy, so you can map a group within a VO into a tenant, like this:
{
   "dteam": {
       "tenant": "dteam"
   },
   "/dteam/NGI_IBERGRID": {
       "tenant": "dteam_ibergrid"
   }
}
  • Restart the Apache server, and it's done.
Retrieved from "https://wiki.egi.eu/w/index.php?title=HOWTO16_How_to_enable_a_Virtual_Organisation_on_a_EGI_Federated_Cloud&oldid=79431"