We are rewriting the syncing tool for Fedora ELN to be more resilient. Part of that is maintaining a database of the current state, so we can easily resume in the event that the process is terminated (crash, reboot, etc.) without missing any builds.
We would like to have a database set up on the Fedora Infra postgres servers that we can use for this purpose. We anticipate the resource requirements to be quite low: it's a single reader/writer process.
Our current plan is for it to retain historical data, which we anticipate will be less than 1 GiB of data per year (probably far less). If that turns out to be an incorrect estimate, we can implement a history retention and cleanup routine to avoid using up too much space.
As this rewrite is being done to facilitate the CentOS Stream 10 sync, we'd very much like to have this in place by 2023/08/31.
Where are you going to be accessing this from?
Our database servers are not publicly available.
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Reporter (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Would they be accessible from the CentOS Stream OpenShift instance at https://console-openshift-console.apps.stream.rdu2.redhat.com/k8s/cluster/projects ?
I don't think so. The stream.rdu2.redhat.com is inside a completely different datacenter with no interconnect but regular internet. Making 'holes' between the two requires reviews and approvals of at least 4 different security plans. I would think it would be (much) easier for Fabian or Brian to set up something in that site.
[edited: the above is my opinion and could be completely out of date with reality.]
@smooge is completely correct here.
So, I think you need a DB somewhere 'near' that cluster. Our database servers are in another datacenter and would be pretty impossible to reach from there. ;(
Sorry, I forgot to circle back here. We've arranged for another database, so this can be closed.
Super.
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.