Add a new CI pipeline to test FLUO and Rook Ceph

[surajssd]

No description provided.

[invidian]

How is it different from #959 and #894? Also why one aggregate issue instead of two?

[surajssd]

This to put them together in one pipeline. Those are individual things to do that will be triggered by the pipeline created in this issue.

So both of them are blocked on this.

[invidian]

Why do they need to be in a separate pipeline then?

[surajssd]

Because in a normal pipeline this can disturb other tests as we have seen previously. I had a chat with @iaguis about this offline IIRC.

[invidian]

Hm, we already have a concept of disruptive tests in our e2e framework, do we need another one? Disruptive tests should run serially and they can do whatever they want with the cluster, as long they revert the changes back to the original state before they finish (so next test can run too).

IMO we could have one node for testing OpenEBS and 3 nodes for Ceph (if that's really needed, can't be stretch it a bit and run Ceph on just one for testing?). I'm afraid about that number of pipelines and dividing test code between them will create hard to maintain solution. I prefer to have one, slower pipeline which does all (as pipelines are already slow), rather than multiple, which only does part of the job.

[surajssd]

How do you propose to test FLUO?

[invidian]

How do you propose to test FLUO?

• To begin the test, all nodes should have updates disabled in FLUO via label/annotation.
• Then we could either run a cluster with Flatcar version specified (latest - 1) OR we could re-configure node to use higher version channel (stable -> beta or stable -> alpha).
• In test code, we trigger an update (either via pod or via removal of label) and we wait until node gets drained, updated and rebooted.
• Test should verify, that node came back and have different Flatcar version now.

[surajssd]

• A pipeline is added and is functional.
• Tests for rook-ceph are here: Add test for rook-ceph which consumes packet_fluo pipeline #1084
• WIP tests for FLUO.

[iaguis]

Can this be closed now that #1142 is merged?