Tryggve Milestone definitions

M4 Deployment of core functionality code base in a production-like environment demonstrated - 2018-12

Demonstrating automated deployment of microservices that enables the core processes of submitter access and upload, data ingestion, and data access, in at least one type of hosting environment that is to be used in any of the production instances. Also demonstrating data upload, data ingestion, and data access functionality of the deployment(s).

Core functionality

• Storage:

  • DB - PostgreSQL;
  • S3 - ceph, NetApp, Minio etc. (alternative to S3 is NFS);

• MQ Broker: RabbitMQ

• Microservices

  • From "LocalEGA"
    • Inbox, Ingest, Mapper, Verify
  • From EGA Data API
    • Key server, FileDatabase, Edge, RES

Production-like environment

• In at least one of Kubernetes, Openshift or Docker Swarm
• [Security set-up definition?]

M7 At least one sensitive data archiving instance technically ready to join the Federated EGA - 2019-05

There exists a deployment that is ready to receive submission datasets, and upon messaging through the interfaces between Central EGA and the local instance, ingest uploaded datasets, and message back to Central EGA through the interfaces, to support the full data and metadata submission process of EGA.

M5 Dataset mirroring and/or access between Sensitive Data Archiving instances - 2019-10

What is it we want to achieve? Is there demand? NorTwinCan use-case, but that is dependent on the parties having hosting infrastructure solutions in place

M6 Pilot services operational in Nordic Nodes - 2020-10

This should happen long before then... Change date?