Attendees:
David van Enckevort (BBMRI NL)
Jim Dowling (KTH)
Miroslav Ruda (CESNET)
Enol Fernandez (EGI.eu)
Diego Scardaci (EGI.eu)
Vincenzo Spinoso (EGI.eu)
BioBankCloud and FedCloud presentations:
(slides on indico)
Relevant topics of discussion:
- PaaS uses Karamel to create the stacks on EC2/Bare metal/OpenStack and jclouds for talking with IaaS services
EGI is looking into supporting jclouds, two possible options
* (short term) since OpenStack is already supported on jclouds, add the EGI auth mechanisms into jclouds (so OpenStack sites of EGI are accesible).
* (longer term) add OCCI support into jclouds so all the providers can be accessed
Both options to be explored. Switch from jclouds in BioBankCloud is not feasible. Will send information on timelines as soon as possible to BioBankCloud people
- Two main user groups in BioBankCloud: sysadmins and regular users. Sysadmins are the ones deploying the stacks into the providers and are the ones needing credentials for the infrastructure, not expected that the regular users need credentials.
- Auth in BioBankCloud is done against a local user "database", LDAP could be an option. BioBankCloud will check how to support Shibboleth (6M timeframe). EGI is also transitioning to a shibboleth based AAI and will provide a proxy IdP that can be used by BioBankCloud to perform authentication against it. X509 certificates are not considered at the moment.
- Chef recipes for the actual configuration of stacks are obtained from github
should not be a problem in EGI, all VMs should have outbout connectivity
There are minutes attached to this event.
Show them.
