1. IaaS Layer – Solutions for “Enablers”
Fernando Aguilar

2. Introduction: LifeWatch
LifeWatch is an e-science and technology infrastructure for biodiversity and ecosystem research to support the scientific community and other users. ERIC from 17th March.
Its mission is to advance Biodiversity and Ecosystem Research and to provide major contributions to addressing the big environmental challenges (e.g. Climate Change)
Knowledge-based solutions to environmental managers for its preservation, by providing access through a pan-European distributed e-Infrastructure to a multitude of sets of data, services and tools enabling the construction and operation of Virtual Research Environments (Virtual Laboratories & Decision-support Applications). Cloud Computing fit very well.
Example of relevant case studies:
Invasive species
Evolution of wetlands
Evaluating the ecological quality of habitats
Members: Spain, Italy, Netherlands, Belgium, Portugal, Greece, etc.

3. LifeWatch Architecture
Service Oriented Approach. Exploiting common e-infrastructures. Cloud-based services.
Cloud resources, best option to provide the e-infrastructure layer required.
Analysis and processing tools can be deployed and executed.
EGI-LFW-CC: Support, Ecological Observatories, Workflows & Vlabs, Citizen Science.

4. Roles in LifeWatch INDIGO D2.6
Along this line, an important concept in the EU-OSC model are the roles of the actors in these structure, and we propose the following basic categories:
Service Providers (including also “aggregators”), for example
Enablers (knowing how to exploit the services, including if needed extra services/tools)
Solvers (providing the solutions closer to the final user, integrating “specific” knowledge)
Users/Customers (directly or indirectly, i.e. reselling, exploiting the solutions in the Cloud).
The corresponding software components, at all levels, that are instantiated in the different resources are of course a relevant part of the ecosystem services, and must not be forgotten in this scheme.
The figure below shows an example of how a Service Oriented Architecture, like the one proposed for adoption in the LifeWatch ESFRI, can be matched to this scheme.
INDIGO D2.6
Figure 2: Example of adaptation of a SOA scheme to the Cloud layers

5. LifeWatch Requirements on IaaS
Long Standing Virtual Machines.
Enabler: LifeWatch general services (e.g. Project Management, Identity Provider, Data Management Services…).
Solver: Technical support for LifeWatch Groups (e.g. Setting up GeoServer, RstudioServer, etc.).
Flexibility to manage resources: modify resources, storage, etc.
Examples:
GBIF.es: Biodiversity data catalogue, Citizen Science applications, etc.
VLIZ (Flanders Marine Institute): GeoServer, MongoDB.
General Requirements: OpenProject, Digital Knowledge Preservation Framework, Jupyter.

6. How INDIGO-DC can support Enablers?
Example: LifeWatch (Potential) IdP, manage users and roles.
Problem: Give access to a specific role (Solvers).
INDIGO Solutions:
INDIGO IAM: Providing AAI for LifeWatch.
OpenStack Identity Authentication Library.
Keystone AAI Support
WaTTS - OpenNebula
OCCI

7. How INDIGO-DC can support Enablers?
Example: VLIZ has a list of Docker Images in DockerHub. They need resources to run.
Problem: Homogeneous set of images across providers.
INDIGO Solutions:
RepoSync: synchronize Docker Images from DockerHub to OpenStack or OpenNebula.
Nova-Docker: Docker Driver for OpenStack.
ONEDock: support for Docker in OpenNebula.

8. How INDIGO-DC can support Enablers?
Example: GBIF.es has a complete architecture to deploy their system

9. How INDIGO-DC can support Enablers?
Example: GBIF.es has a complete architecture to deploy their system
Problem:
Provide an easy way to define and deploy complex topologies.
Deploy these complex topologies in different sites easily.
INDIGO Solutions:
TOSCA custom Types: Define the resources needed, images, topology, etc.
Heat Translator, TOSCA Parser, IM to deploy in OpenStack/OpenNebula.

10. Thank you!
Fernando Aguilar