Fotis Nikolaidis

Signed-off-by: Fotis Nikolaidis This PR follows the discussion on https://github.com/apptainer/sif/pull/149 == Use-Case == Singularity/Apptainer supports the capability to use PGP keys for signing and verifying containers, thus improving the level...

Signed-off-by: Fotis Nikolaidis What problem does this PR solve? Issue Number: close #xxx Problem Summary: What is changed and how it works? Proposal: xxx What's Changed: Related changes Need to...

For the management of lifecycle, this solution seems to be cleaner than the current one. https://github.com/ohsu-comp-bio/funnel/blob/master/compute/hpc_backend.go

Fix Running Dependencies

1

For the moment, we consider a frisbee.service running when the pod becomes running. This, however, can cause issues for process that take long time to init. Instead, use the pod.container[app].status.started...

Validate that a reference callable exists

1

This is a bit tricky and cannot be done at the admission level, because it requires access to the referenced template. Instead, it must be done at the scenario level,...

For the moment dependencies to referenced templates must be loaded manually. This, however, can be annoying. We need to simplify the process

Because the controller is downloaded from the "release" where the scenarios are accessed by the repo, there can be significant drifts. One solution is to put all the changes into...

Such events can be used to: 1) Abort the experiment if executed 2) Abort the experiment if not executed 3) Used as Grafana annotations to facilitate understanding of multi-stage workflows.

Error: Ingress.extensions "chaos-dashboard" is invalid: spec: Invalid value: []networking.IngressRule(nil): either `defaultBackend` or `rules` must be specified helm.go:84: [debug] Ingress.extensions "chaos-dashboard" is invalid: spec: Invalid value: []networking.IngressRule(nil): either `defaultBackend` or `rules`...