search

CLARIAH / clariah-plus

This is the project planning repository for the CLARIAH-PLUS project. It groups all technical documents and discussions pertaining to CLARIAH-PLUS in a central place and should facilitate findability, transparency and project planning, for the project as a whole.
9 stars 6 forks source link

Define service description, requirements and components for Distribution & Deployment #44

Open proycon opened 2 years ago

proycon commented 2 years ago

This epic is still rather vague, a precise definition and description needs to be drafted, including a workflow visual schema. In the SDRv1 we called this "Scalable Multimedia Processes" for a while, but that felt too specific so during the tech day we opted for a more generic "(FAIR) Distribution & Deployment" instead.

I think the primary concern for this epic is to agree on, provide and communicate the software & infrastructure guidelines and to set up a (possibly proof-of-concept) implementation of a infrastructure. Most of the implementation is firmly in the scope of WP2 I'd say.

I'm (again) risking a formulation of this epic that this rather broad so it encompasses most of the provisioning services WP2 delivers, but I think that's not a bad thing. Services such as monitoring, CD/CI are strongly interconnected with deployment. @roelandordelman and @tvermaut may want to check what they think of this.

ddeboer commented 2 years ago

An important question that needs to be answered explicitly: what do we want the ‘CLARIAH infrastructure’ to be?

In other words, is CLARIAH infrastructure to be a real thing or more of a concept (or umbrella term)?

proycon commented 2 years ago

On 22-01-28 12:48, David de Boer wrote:

An important question that needs to be answered explicitly: what do we want the ‘CLARIAH infrastructure’ to be?

  • Either a single container cluster, using the same abstraction layer (e.g. a Kubernetes cluster) that runs on hardware provided by CLARIAH partners. Delegates from the partners that are part of CLARIAH’s Distribution & Deployment (D&D) team collaborate on setting up that cluster.
  • Or a multitude of CLARIAH-compliant infrastructures that is run by each partner individually. Each partner sets up their own cluster, following the CLARIAH requirements. The role of the D&D team is limited to PoCs and writing documentation and requirements.

Good to make explicit indeed. I would say the mostly latter. Though a part of that still entails setting up some central provisioning services like the docker registry, authentication provider etc...

@mmisworking What do you say ?