User Tools

Site Tools


main:faq:vo_enrollment_from_vmops_dashboard

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

main:faq:vo_enrollment_from_vmops_dashboard [2019/05/31 15:37]
7dec9e27b58a2d54a2a96a538813e805058cb792ed68e744a68d87708e39628c@egi.eu [When will a user be able to deploy VMs?]
main:faq:vo_enrollment_from_vmops_dashboard [2019/06/03 15:01] (current)
84f464f99bd105183e28266cde96f6d7bdc2804663c23b97e7bde0520f656155@egi.eu Minor editing
Line 1: Line 1:
-===== How to request ​VO membership ​with VMOPs dashboard =====+===== How to request ​for membership ​to a VO from within the VMOPs dashboard =====
  
-The VMOps dashboard ​currently supports ​list of [[main:​faq:​which_vos_are_supported_by_the_vmops_dashboard|specific VOs]] that a user must be a member of in order to be able to deploy VMs through ​the dashboard.+In order to be able to deploy VMs through the dashboard, users must be member ​of a least one of the [[main:​faq:​which_vos_are_supported_by_the_vmops_dashboard|specific VOs]] that the VMOps dashboard ​supports.
  
-These supported VOs are also displayed ​in the VMOps dashboard home page as shown bellow and are also displayed ​in the user menu popup dialog in the upper right corner of the dashboard:+These supported VOs are displayed ​on the VMOps dashboard home pageas shown bellowand are also displayed ​on the user menu popup dialogin the upper-right corner of the dashboard:
  
 {{:​main:​faq:​vmopsdashboard_homepage_accountinfo.png?​500|}} {{:​main:​faq:​vmopsdashboard_profile_supportedvos.png?​400|}} {{:​main:​faq:​vmopsdashboard_homepage_accountinfo.png?​500|}} {{:​main:​faq:​vmopsdashboard_profile_supportedvos.png?​400|}}
  
-In this list we can see that we already have membership ​to the fedcloud.egi.eu and demo.fedcloud.egi.eu VOs. If we want to become a member of another VO we should ​locate the VO in the list of the supported VOs and click on the **enrollment** link. +In the examples listed above, ​we see that the user is a membership ​of the fedcloud.egi.eu and demo.fedcloud.egi.eu VOs. If the user wishes ​to become a member of another VO, they must locate the VO in question ​in the list of supported VOs and click on the **enrollment** link. The enrollment ​link will redirect ​the user to an external service, where they may initiate ​the process of becoming a member of the specific VO, by requesting membership.
- +
-This link will redirect ​us to an external service ​to request VO membership and start the process of becoming a member of the specific VO.+
  
 ===== VO Membership Request Process ===== ===== VO Membership Request Process =====
  
-As mentioned above, when we click the **enrollment** link we navigate ​to a page where a membership request form for the specific VO exists. Usually, this page belongs to the [[http://​italiangrid.github.io/​voms/​index.html|VOMS server]] instance of the specific VO, although there are cases where other type of services handle such requests ​(eg. [[https://​perun.egi.eu/​|PERUN]],​ [[https://​aai.egi.eu/​registry/​co_enrollment_flows/​select/​co:​2|EGI AAI]] etc).+As mentioned above, when users click on the **enrollment** link, they are navigated ​to the membership request form for the specific VO. Usually, this form is hosted by the [[http://​italiangrid.github.io/​voms/​index.html|VOMS server]] instance of the specific VO, although there are cases where other types of services handle such requests, such as [[https://​perun.egi.eu/​|PERUN]],​ [[https://​aai.egi.eu/​registry/​co_enrollment_flows/​select/​co:​2|EGI AAI]]etc.
  
-In the case that VOMS or Perun instance handles the VO memebrship registrationit will be required ​from us to own a personal X.509 access ​certificate obtained by a [[https://​www.eugridpma.org/​members/​membership|recognised]] Certification Authority, in order to access these services. ​+In most cases, such as that of VOMS managed VOsusers are required to own a personal X.509 certificateobtained by a [[https://​www.eugridpma.org/​members/​membership|recognised]] Certification Authority, in order to access these services. ​
  
-For this example we will assume that a VOMS server handles ​the VO we want to join. In that case we will navigate to page like the one below:+In the following ​examplewe will assume that a user wants to join the //​MyFavoriteVO// ​VO, whose registration form is hosted by VOMS server and looks like the one below:
 {{ :​main:​faq:​vmopsdashboard_voms_server.png?​700 |}} {{ :​main:​faq:​vmopsdashboard_voms_server.png?​700 |}}
  
-After filling the fields ​remember to add to the description that you want to use the cloud infrastructure,​ so that the VO manager that will handle our request will set the appropriate ​roles to our membership ​(eg grant you the VM Operator role).+After filling ​in the required ​fields, the user must provide a message ​to the VO administrator in the designated area, indicating their desire ​to make use of the cloud infrastructure,​ so that the VO administrator knows to set the appropriate membership ​roles, which in this case is the **VM Operator** role. After submitting the form, the user will most likely receive a confirmation email concerning their request. Likewise, the administrator of the VO will be notified about the request, so that it may be processed.
  
-After submitting the form, it is most likely to receive a confirmation email that our request is registered. Likewise, the manager of the VO will be notified and will process our request. ​The amount of time it takes for each VO manager ​to accept ​or reject a request depends on the applied acceptance policies of each VO and also to human factorssuch as the time of day of the requesthow much occupied the VO manager might be at the time etc.+The amount of time it takes for a request ​to be accepted ​or rejected may vary with each VO and span from a few minutes ​to days; howeverin most cases, requests are accepted or rejected within ​the day. Users will always receive an email response upon the completion ​of the processregardless of its outcome.
  
-For the aforementioned reasons the time needed for accepting or rejecting a VO membership request spans from a few minutes to days. In most cases the requests are quickly accepted or rejected within the day. Regardless if the request is accepted or rejected, we will still get an email response. 
 ===== When will a user be able to deploy VMs? ===== ===== When will a user be able to deploy VMs? =====
  
-If a user followed ​the process ​above and was accepted ​as a VO member, the only thing that is left is for the membership information to be propagated to the rest of the EGI services. The duration ​for something like this depends on the internal mechanisms that each VO uses to share their information with the rest of the infrastructure. ​+In order for the new VO membership to be recognized by the VMOps dashboard, users will have to **log out and re-log in** to the dashboard, after the the enrollment ​process ​has been completed ​and the user has been accepted. Howeverin order to effectively reach the dashboard, ​membership information ​has to have been propagated to the rest of the relevant ​EGI services, first, such as the [[https://​www.egi.eu/​services/​check-in/​|EGI Check-in service]]. The timescale ​for this final step depends on the internal mechanisms that each VO employs in order to share their information with the rest of the infrastructure. ​
  
-This means that if we relogin ​to the VMOps dashboard right after the confirmation email arrives, ​we might still be unable to use the VO to deploy VMs. It usually ​needs a day for the infrastructure to collect the new information regarding ​the VO memberships,​ so it is suggested ​to try to deploy VMs the next day of the VO membership request.+What this means is that even if a user re-logs in to the VMOps dashboard right after the confirmation email arrives, ​they might still be unable to use the new VO to deploy VMs. It usually ​takes up to 24h for the infrastructure to collect the new information regarding VO memberships,​ so it is suggested ​that users plan their enrollment a day ahead, when possible.
main/faq/vo_enrollment_from_vmops_dashboard.1559317064.txt.gz · Last modified: 2019/05/31 15:37 by 7dec9e27b58a2d54a2a96a538813e805058cb792ed68e744a68d87708e39628c@egi.eu