Present: @evgeni, @ehelms, @ekohl, @lpramuk
Done
Nothing completed
Doing
Update Redmine and move to new infrastructure · Issue #1681 · theforeman/foreman-infra · GitHub
Scaleway has been having network issues, which are noticable. It was already planned to migrate the machines, but the priority has been increased.
Current status summarized in Update Redmine and move to new infrastructure · Issue #1681 · theforeman/foreman-infra · GitHub but tl;dr is that a box has been provisioned on our Conova box running CentOS Stream 9. It’s updated to Redmine 5, running Ruby 3.
@ekohl is looking at replacing the legacy prprocessor: Update Redmine and move to new infrastructure · Issue #1681 · theforeman/foreman-infra · GitHub
Investigate Copr as the build system · Issue #1795 · theforeman/foreman-infra · GitHub
@ehelms has made a lot of progress. We now build using COPR both for PRs and have https://stagingyum.theforeman.org which replaces the staging repository from Koji.
Comps in COPR doesn’t appear to work: The use of a comps file does not result in a filtered repository · Issue #2901 · fedora-copr/copr · GitHub
Signing is still an open debate: Investigate Copr as the build system · Issue #1795 · theforeman/foreman-infra · GitHub
Migrate Discourse off of Scaleway VM · Issue #1710 · theforeman/foreman-infra · GitHub
Moved from To do to Doing. Similar to Redmine there are connection issues. We’re looking at hosting on our Conova machine, but are currently limited by the physical memory on it. Looking at buying addition memory, then look at the actual migration.