- Jenkins plugins update to latest
- Jenkins updated to 2.361.1 & all plugins to latest
- Decommissioned deb-node01.jenkins.osuosl.theforeman.org
- Generated Foreman Infra documentation
- Added a swapfile on discourse01
- CentOS CI migration completed
- AAAA record added to community.theforeman.org
- Automation of packaging bumping plugins · Issue #1693 · theforeman/foreman-infra · GitHub
- Rename node01.conova.t.o to virt01.conova.t.o · Issue #1667 · theforeman/foreman-infra · GitHub
- Document libvirt setup used on conova hardware node · Issue #1708 · theforeman/foreman-infra · GitHub
- move ci.centos.org workloads from legacy cico api to new duffy api · Issue #1769 · theforeman/foreman-infra · GitHub
CentOS CI: completed. Only issue is that bats results overwrite eachother, making debugging harder.
@evgeni created a new machine in AWS, sitting next to the Koji infrastructure. It’s hooked up to Puppet which manages a basic webserver with reposynced. Now looking at how Koji can use it without exposing the webserver to the internet.
We’ve gotten credits. Now have to document it and start using it. Developers working on Azure integration are also welcome to use this.
Moved back to To do since there’s no progress and not being actively worked on.
Amit has left the project so a new new owner is needed.
Migrate Puppetserver to stand-alone instance · Issue #1685 · theforeman/foreman-infra · GitHub & Migrate Foreman instance to new infrastructure · Issue #1686 · theforeman/foreman-infra · GitHub
Planned to be executed after Foreman 3.5 has branched. See the migration plan for more details.
Will be easier after the new Foreman infra is live. Did find an issue with dnf cron, Puppet module updated to a version that’s compatible.
To be done after Foreman has migrated to the new infra.
Discussion if we want to keep Redmine, but at best we’ll need to keep it running for quite a while as an archive.
Rebuild Koji in new infrastructure and with new architecture · Issue #1435 · theforeman/foreman-infra · GitHub
We have to migrate to a new AWS account (due to RH internal billing). That may be a good chance to rebuild the Koji infrastructure. We could also look into using COPR instead of our own Koji instance. In the next couple of months we’ll need to migrate the AWS account. The benefit of using COPR is that we don’t have to maintain infrastructure and the COPR team is eager for us to use it. COPR also allows cloning of repositories which means we could actually easily present a real repository for PR testing.
@ekohl wants to take this on after Foreman infra has migrated. Aimed at completing this before the end of the month. On our Conova node there’s still capacity and will be the target.