Register VO to get compute and data resources

[backeb]

To register a VO please follow instructions in https://github.com/c-scale-community/discussions/discussions/2#discussioncomment-604917

Specifically: procedure to create VOs in EGI: PROC14

@sustr4 @enolfc @melanger please support @MilutinMM in following the process

[backeb]

To register the VO, I suggest providing the following information for RETURN:

country: Netherlands ⬅️ @melanger please indicate which ISO code to use category: Research domain: Land and/or Climate ⬅️ @melanger I presume we can only use one, @MilutinMM please indicate which is more appropriate

@MilutinMM please schedule a meeting with @enolfc who will help you register the VO in the Operations Portal

[melanger]

@backeb I suggest the two-letter country codes (ISO 3166-1 alpha-2), which is nl or NL for Netherlands.

[sustr4]

Hi, just a few notes and confirmations

country

can be selected by users individually. I'd suggest that rather than a VO-wide country setting.

domain: Land and/or Climate arrow_left @melanger I presume we can only use one

Yes, domain (same as country or category attributes) should be single-value.

[MilutinMM]

Hi @backeb, @sustr4, and @enolfc, thanks for the initiative. The domain "Land" would be more appropriate in my case. Let me know if you need any other info!

[backeb]

@MilutinMM could you please follow the instructions in https://github.com/c-scale-community/discussions/discussions/2#discussioncomment-687327 to register a VO. Let me know if anything is unclear. For help please arrange a meeting with @enolfc

[MilutinMM]

Hi @backeb, I registered a VO (return c-scale.eu) and still waiting for an email from GGUS helpdesk to notify me about the registration. Do you know how long usually take to get that email?

[backeb]

Hi @backeb, I registered a VO (return c-scale.eu) and still waiting for an email from GGUS helpdesk to notify me about the registration. Do you know how long usually take to get that email?

@sebastian-luna-valero @enolfc could you follow up with EGI operations team?

[enolfc]

I see the GGUS ticket https://ggus.eu/index.php?mode=ticket_info&ticket_id=152011 for VO HighResLandSurf.c-scale.eu is already closed. Is that the one? If so, you should have received some notification already. If that's not the VO, I don't see anything in the tickets about any other c-scale VO, so we would need to investigate where this was lost.

[oonkjbr]

Dear @backeb , @enolfc , Please note that for this use case we expect that it in first place will be deployed on the HPC-HTC federation. For that setup the user management will at least initially be different and follow the CO setup in SRAM. It may still be useful to have a VO for this use case later e.g., for scale-out, data access via WP2 and potential integration between these VO's and the SRAM CO's. The latter is formally out of scope for C-SCALE, but I am interested in exploring it if resources allow. best regards, Raymond

[MilutinMM]

Hi @enolfc , "HighResLandSurf.c-scale.eu" is a different VO. I have created "return c-scale.eu." When i think now, i probably used space instead of a dot between "return" and "c-scale.eu." Not sure if that is the reason for not initiating a ticket...

[enolfc]

Ok, so I'm not seeing any ticket or notification about return c-scale.eu so I think there may be indeed an issue with the name containing a space. @MilutinMM could you make a new request with the right name?

[backeb]

Ok, so I'm not seeing any ticket or notification about return c-scale.eu so I think there may be indeed an issue with the name containing a space. @MilutinMM could you make a new request with the right name?

I will add a suggested VO naming convention to the post: https://github.com/c-scale-community/discussions/discussions/2#discussioncomment-687327

[backeb]

Dear @backeb , @enolfc , Please note that for this use case we expect that it in first place will be deployed on the HPC-HTC federation. For that setup the user management will at least initially be different and follow the CO setup in SRAM. It may still be useful to have a VO for this use case later e.g., for scale-out, data access via WP2 and potential integration between these VO's and the SRAM CO's. The latter is formally out of scope for C-SCALE, but I am interested in exploring it if resources allow. best regards, Raymond

@oonkjbr I think what's important is that we have a well-documented, logical process for users / communities to get access resources. If the idea is to abstract VO/CO in SRAM set up away from the users then how should we coordinate access and resource provision? Could / should we use an online form?

[MilutinMM]

Hi @enolfc, @backeb ,and @oonkjbr Thank you for the support! I have re-registered the return.c-scale.eu VO, and received the ticket from GGUS-helpdesk.