Scripts for seperate CR machines

[tdawson]

Content Resolver runs refresh.sh in a loop.
In order to run c10s on a seperate machine, we need two new versions of refresh.sh.

• refresh-eln.sh - This is basically the same as the original refresh.sh but it runs content resolver with --labels eln,eln-extras
• refresh-c10s.sh - Very close to refresh.sh but with --labels c10s and it syncs to the /c10s/ directory.

[tdawson]

Until this get's merged, the current Content Resolver is going to wipe out the /c10s/ directory each time it finishes. That's not too much of a problem, it should give us several hours to see how things look.

[yselkowitz]

What would the plan be for when/while we branch c11s? There will certainly be some overlap when both c10s and c11s are being tracked in CR (and with them being in a separate instance, and CS providing only one snapshot per day, perhaps they could be allowed to overlap even longer). Would you make yet another instance for c11s, or use a single instance for all active CS versions? If the latter, the a location should be more generic than /c10s/.

[tdawson]

I was thinking of having a separate machine for c11s, which would be in the /c11s/ directory.
Although the machine I put this on could handle both c10s and c11s, so having them both run on one machine is a possibility.
I agree, if we have them both running on the same machine, we should have a more generic directory. Maybe /cs/ ?

[tdawson]

It looks like it works. Ya!!
https://tiny.distro.builders/c10s/views.html

[yselkowitz]

Are you planning on deploying the CS instance fairly soon after merging this? If so, let's merge the ELN changes into refresh.sh and add only the CS script.

A dedicated CS instance should be able to handle multiple versions, particularly given that CS composes are (only) nightly. Do you think we really need separate instances for each version, and how much harder will that make standing up c11s when the time comes?

[tdawson]

Are you planning on deploying the CS instance fairly soon after merging this? If so, let's merge the ELN changes into refresh.sh and add only the CS script.

Yes, I would like to have this running by end of work day today.
That sounds good. I'll make that change.

A dedicated CS instance should be able to handle multiple versions, particularly given that CS composes are (only) nightly. Do you think we really need separate instances for each version, and how much harder will that make standing up c11s when the time comes?

I don't think we need separate instances. One machine should be able to do them both. Especially since they don't have to do extras. I'll make a change so that this goes into /cs/ then when c11s comes around, we just need to add it's tag to the labels option.

I think standing up a new instance this size would require fedora infra to set it up. For this project, I lucked out because Adam had a second machine he never shut down.

[tdawson]

Changes made.
Let me know what you think. If everything is good I'll do a rebase so the git commit is cleaner.