NLSRC - Deploy all v0.1 local compulsory services

Deployed, monitorable, documented and supportable services: will enable initial operations activities, including test campaigns; will (later) enable test users to interact with our systems; will provide the SOG with valuable operating experience; and will provide stakeholders with a tangible, assessable demonstration of SRCNet's progress so far. Deploying all local compulsory services is one requirement for SRCNet to "confirm" that an SRC will be a v0.1 node. A sufficient number of nodes must be "confirmed" for SRCnet to begin the v0.1 phase of work. This will be a landmark achievement for SRCNet. 

For this SRC, all v0.1 local compulsory services are: AC1: Deployed locally AC2: Local integration test(s) are completed to check the connection with global services - as informed by deployment documentation ( to be populated ) AC3: Monitorable via the centralised service monitoring dashboards and shown to be running successfully AC4: Documented - meaning that any SRC-specific deployment instructions / troubleshooting are captured and (where applicable) added to ska-src-docs-operator AC5: Supportable - meaning that an operator (a SOG member if possible) is able to access the service deployment and provide support next PI AC6: Deployed via a GitOps Tool (e.g. ArgoCD, FluxCD) OR repeatable deployment methods fully documented with deployment velocity expectations (e.g. new versions are deployed within 1 working day) v0.1 local compulsory services: Rucio Storage Element (configured to use SKA IAM) JupyterHub (specifically JupyterHub, not another service that provides Jupyter Notebooks) at least one Visualisation Service out of: CARTA, VisIVO, Aladin note: CANFAR can provide this visualisation service SODA Service Data Management API (see via features under SP-4654 ) cavern see description  a Orchestrator Service (e.g. Kubernetes) perfSONAR Local Service Monitoring stack (e.g. Prometheus)

  AC1 AC2 AC3 AC4 AC5 AC6   Service Deployed Integrated Monitorable/Running Documented Supportable GitOps (or ...) Notes Rucio Storage Element done done done (but the central service and validation criteria should be specified) TBD ( the level of detail needs to be clairfied and agreed upon)   done     JupyterHub TBD TBD TBD TBD TBD   In the EoI we agreed to  std. Jupyter notebooks (in line with the docs at that time) and not a Hub. Std. notebooks are better aligned with platform and can be provided if agreed upon. How/where do we discuss this? Visualisation Service In progress In progress In progress In progress In progress   We will likely provide Aladin. SODA Service TBD TBD TBD TBD TBD   Procedural (incl. ownership), functional and security descriptions are missing atm. for this intended services. Also, in the EoI this was grouped in the options with the other visualization services. Data Management API TBD TBD TBD TBD TBD   This service appears to not yet be ready from a development perspective. Hence, we can not deploy it at this time.  cavern TBD TBD TBD TBD TBD   It is unlikely that this can be deployed on the chosen platform for NL-SRC. Hence this requires discussion and potential alternatives. Orchestrator Service N/A N/A N/A N/A N/A   Not applicable for NL-SRC perfSONAR done done done (but the central service and validation criteria should be specified) TBD ( the level of detail needs to be clairfied and agreed upon)   done     Local Service Monitoring TBD TBD TBD TBD TBD   Likely it is done at NL-SRC, but the service needs a definition as well as a description and validation criteria.