D3.2: Initial Implementation of the Platform - Demonstration
This document accompanies the Work Package 3 deliverable D3.2 ("Initial implementation of the platform"), available in video format (screen recording) at https://www.youtube.com/watch?v=TnlUOG3lOu4&feature=youtu.be.
The goal of this document is to provide an explanation of the various sections of the demonstration video as well as some background for the use cases and tools.
This document will also highlight the main aspects of ScienceMesh's platform and how it already enables some of the use-cases in the context of Work Package 4 (remote sharing, collaborative editing of documents and access to data science environments).
The initial platform consists of two main components:
- a. The IOP (Inter-Operability Platform)
- b. The "Central Service"
The IOP component is a software package which is deployed on each one of the sites, as to allow them to interact with other components of the ScienceMesh. The IOP guarantees compatibility of the use-cases across multiple vendor EFSS (Enterprise File Sync and Share) platforms and allows them to speak the common language of the CS3APIs3, essential to the cross-integration of the various micro-services which constitute the platform. The IOP also provides monitoring information about the health of a mesh node and is continuously reporting these metrics to the Central Service component.
The Central Service is a collection of different software solutions which will be deployed as a single package. This service is a lightweight management service for the ScienceMesh federation that enables the monitoring and site registration, allowing the operation team of the ScienceMesh to:
- Register and get an API key which will allow a node to effectively become part of the Mesh;
- Have access monitoring dashboards (through Grafana) and helpful insights (Prometheus) as well as information which will help the governing bodies ensure a fair distribution of resources within the federation.
These two use-cases are implemented through the Mentix service. Another component of the Central Service is the Mesh Directory service, which allows the nodes to establish trust relationships between end-users and bootstrap the process through arbitrary communication channels, thanks to the invitation workflow.