Remove cs8 builders

[singiamtel]

Not used anymore

As discussed over coffee break with @ktf @davidrohr

They have to be removed as required checks before merging

[ktf]

@Barthelemy should comment about QualityControl on CS8.

[Barthelemy]

Hi,

Could you give me a bit of context ?

Thankyou

[singiamtel]

Hi @Barthelemy,

we're deprecating the cs8 builders as we need the computing to test the FullCI workflow in Alma 9. cs8 is EOL, and our production workload is not running in cs8 in any case (as far as I know). QualityControl is already being tested in Alma 9 so we believe it should be fine to remove this tester too

What's your opinion on this? Is it okay to go ahead and remove it? (To clarify, we only want to delete build/QualityControl/o2-cs8, not build/QualityControl/o2-dataflow-cs8)

Cheers,
Sergio

[Barthelemy]

The whole FLP farm is on CS8 and we are not sure we are going to move to alma 9 because there is a severe issue with PDA and we depend on other people to fix it.

In QualityControl we use o2-dataflow-cs8 and o2-cs8.

I would not remove them until we know that we are moving to alma 9 or rhel 9 in the FLP farm. Otherwise we are not testing on the systems we are running onto.

[ktf]

Ok, fair enough. @singiamtel let's keep anything which includes QC / dataflow to cs8, then.

[davidrohr]

Hi Barth, just for my understanding: I thought FLPs use the dataflow defaults. How are you using both o2 and o2-dataflow defaults for QC then? Kind Regards David Rohr Sent from my mobile. (Excuse the typos!)

…

On 22 November 2024 09:05:41 CET, "Barthélémy von Haller" ***@***.***> wrote: The whole FLP farm is on CS8 and we are not sure we are going to move to alma 9 because there is a severe issue with PDA and we depend on other people to fix it. In QualityControl we use `o2-dataflow-cs8` and `o2-cs8`. I would not remove them until we know that we are moving to alma 9 or rhel 9 in the FLP farm. Otherwise we are not testing on the systems we are running onto. -- Reply to this email directly or view it on GitHub: #1424 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[Barthelemy]

@davidrohr good point. Actually we run on both FLPs and EPNs and thus it must be tested on both CS8 and Alma 9. I propose to keep o2-dataflow-cs8 on CS8 and have o2-cs8 on Alma.

[davidrohr]

EPNs run a different build that is tested in the FullCI already. Kind Regards David Rohr Sent from my mobile. (Excuse the typos!)

…

On 22 November 2024 09:25:46 CET, "Barthélémy von Haller" ***@***.***> wrote: @davidrohr good point. Actually we run on both FLPs and EPNs and thus it must be tested on both CS8 and Alma 9. I propose to keep o2-dataflow-cs8 on CS8 and have o2-cs8 on Alma. -- Reply to this email directly or view it on GitHub: #1424 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[Barthelemy]

ok, so you are saying that QualityControl/O2fst/o2 running on Alma 9 + build/QualityControl/o2-dataflow-cs8 on CS8 is enough ?
(+mac but that's different)

[davidrohr]

Yes, except that currently fst is still on alma8 and we will move to alma9 when epns move to alma9. Kind Regards David Rohr Sent from my mobile. (Excuse the typos!)

…

On 22 November 2024 09:30:45 CET, "Barthélémy von Haller" ***@***.***> wrote: ok, so you are saying that `QualityControl/O2fst/o2` running on Alma 9 + `build/QualityControl/o2-dataflow-cs8 ` on CS8 is enough ? (+mac but that's different) -- Reply to this email directly or view it on GitHub: #1424 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[Barthelemy]

ok, then it sounds good. @singiamtel could you update this pr accordingingly ?
Thank you

[singiamtel]

Ciao Barth,

Just to confirm, this should be the new status of the testers?

(Updated to reflect @davidrohr's comments)

• AliceO2Group/AliceO2
  • build_O2_o2-cs8 -> Removed
  • build_O2_o2-dataflow-cs8
• alisw/alidist
  • build_O2_alidist-cs8 -> Removed
  • build_O2_alidist-dataflow-cs8
• AliceO2Group/QualityControl
  • build_QualityControl_o2-cs8 -> Removed
  • build_QualityControl_o2-dataflow-cs8
  • build_QualityControl_O2fst_o2 -> Migrated from slc7 to slc9-gpu-builder

And all the other cs8 checks stay untouched

• AliceO2Group/Configuration
  • build_Configuration_o2-dataflow
• AliceO2Group/InfoLogger
  • build_InfoLogger_o2-dataflow
• AliceO2Group/Monitoring
  • build_Monitoring_o2-dataflow
• AliceO2Group/ReadoutCard
  • build_ReadoutCard_o2-dataflow

[davidrohr]

• build/QualityControl/O2fst/o2 -> Migrated from slc7 to slc9

Isn't the current fst build on the slc8-gpu-builder container?

[singiamtel]

I think it's on SLC7

https://github.com/alisw/ali-bot/blob/master/ci/repo-config/mesosdaq/slc7/qualitycontrol-fullsystest.env

[davidrohr]

Indeed, but that is just wrong. The FST test for the EPNs should use the GPU builder container as for O2 and for alidist.
Currently EPNs are on ALMA8, and we plan to move to ALMA9.

[singiamtel]

Indeed, but that is just wrong. The FST test for the EPNs should use the GPU builder container as for O2 and for alidist. Currently EPNs are on ALMA8, and we plan to move to ALMA9.

So it should've been using slc8-gpu-builder and we should migrate it now to use slc9-gpu-builder?

[davidrohr]

Right now, the EPNs are on ALMA8, so all FullCI / FST builders should run with the slc8-gpu-builder.
So we should switch the qualitycontrol/fst from slc7 to slc8-gpu-builder.

And we remove all the -cs8 builders (not the -cs8-dataflow) to get some free resources.

In the next step, for preparing the EPNs for ALMA9, we have to duplicate all FullCI/FST builders in AliceO2 / QC / alidist from slc8-gpu-builder to slc9-gpu-builder.
And then, once EPNs are migrated, we will remove all old builders using slc8-gpu-builder container.

[singiamtel]

@Barthelemy Can these two checks also be migrated to cs8?

• build_O2_Common
• build_QualityControl_o2

(Both currently running under slc7)