search

c-scale-community / workflow-automated-river-forecasts

Porting and deploying the Seasonal River Discharge Forecasts use case to C-SCALE
Apache License 2.0
1 stars 0 forks source link

Access to EODC's OpenStack #9

Closed backeb closed 2 years ago

tclark-eodc commented 3 years ago

The first step forward here is for the users administrating the VMs to create an EODC account. This can be done via eodc.eu/register The EODC accounts can then be federated with the EGI Check-in accounts.

In parallel to the user account creation we can begin setting up the project within our openstack environment.

@sperna - Could you please confirm the initial resource requirements?

enolfc commented 3 years ago

@tclark-eodc : could this registration be avoided if we rely on EGI VOs? e.g. user could be created on-the-fly if getting the right membership to the group you are t support. We could check to do a pre-provisioning of users if needed too, although this is not available right now in Check-in, we did something similar in the past with Perun and OpenNebula systems.

tclark-eodc commented 3 years ago

@enolfc - Account creation is possible in this way, but would miss the step of users agreeing to the EODC terms and conditions for use. Our cloud is still quite loosely federated, and EGI VOs for authorization are not directly supported. We can support check-in only for authentication at the moment. Adding authorization from Check-in is planned but since this use case wanted to kick off early, we are working with the setup we have today.

enolfc commented 3 years ago

thanks @tclark-eodc !

So in the future we can expect AuthZ to be done via Check-in, but it's not clear to me how T&C agreement should be handled. I'm aware there some work in progress to improve the federated management of this kind of AUP terms, but I assume we will not have this implemented in the short term.

I think we should clarify this asap

sperna commented 3 years ago

@tclark-eodc : resources requirements remain 25 TB. Furthermore there are no specific software installations required for now. We plan to do all with dockers.

I just created an EODC account: Frederiek.sperna@deltares.nl can you tell me how to federate that with the EGI check-in accounts?

Thanks!

sperna commented 3 years ago

Dear @tclark-eodc Can you give an update on the status of the VMWare for use-case 4>

I have an EODC account: Frederiek.sperna@deltares.nl

Can you tell me how to federate that with the EGI check-in accounts?

And next step: How to connect to the VMWare

Also - will the VMWare be LINUX? I will update this issue with software requirements.

cc to :@avgils

tclark-eodc commented 3 years ago

@sperna Thanks for your patience, I've been out of office the last weeks.

I can see your EODC Account. To move ahead with federating this account with EGI Check-in: Go to sign in to an EODC service and select EGI as provider on the left hand side. As an example service, you could use our gitlab. Proceed through the sign-in with the EGI Check-in provider of your choice. As the final step, you'll be asked to link your EGI Check-in userID with your EODC account.

We use openstack rather than VMware. This allows you to create and manage your own VMs within a preconfigured quota of resources. Linux is supported and recommended.

The project within openstack will be setup in the next days so you can take a look around. I'll send you a welcome email with further details, links to our How-Tos etc. once this is in place. In regards to the resources, I'm missing the resource requirements you need in terms of CPU + RAM. This can be adjusted as needed later, but what would a good starting point look like for you?

########## Edit 15.07 - Welcome email with access guide sent to @sperna