Israel Fruchter

@yaronkaikov can you clarify where the monitoring images should be found ? on which account ? and why aren't they public ?

I've check the latest runs of this PR, and the issue with the nemesis panel isn't there anymore:  once I'll find the right image for GCE, this is good...

@soyacz Move the offending yaml to the configuration folder, and we can merge this

I better to look at such a pipeline like that: https://jenkins.scylladb.com/job/scylla-staging/job/avi/job/avi-regression-latency-650gb-grow-shrink/2/pipeline-graph/ and then on: https://jenkins.scylladb.com/job/scylla-staging/job/avi/job/avi-regression-latency-650gb-grow-shrink/2/pipeline-console/?selected-node=508 and see it's failing cause if this: ``` [111](https://jenkins.scylladb.com/job/scylla-staging/job/avi/job/avi-regression-latency-650gb-grow-shrink/2/pipeline-console/?start-byte=0&selected-node=494#log-111) 19:41:52 + echo 'need to choose...

> > I better to look at such a pipeline like that: https://jenkins.scylladb.com/job/scylla-staging/job/avi/job/avi-regression-latency-650gb-grow-shrink/2/pipeline-graph/ > > and then on: https://jenkins.scylladb.com/job/scylla-staging/job/avi/job/avi-regression-latency-650gb-grow-shrink/2/pipeline-console/?selected-node=508 > > and see it's failing cause if this: > >...

We should create a new step on the pipeline as early as possible that would validate the job parameter and fail fast if they are incorrect

coming back to this one: - parameter validation, we should be done by argus where we have better control on how form are built, now it can do rebuild, which...

So we need to refresh the session, and fall back to the next keyspace if we fail to find it.

we probably gonna defer to SMI to implement it, and then SCT to identify and send it as is

this is gonna be handled by https://github.com/scylladb/scylla-machine-image/issues/462 we would have work to adapt, so we don't compress it again, but that's it, the rest would be done of of the...