Infrastructure SIG Meeting notes 2022-11-03

Present: @evgeni (chair), @ekohl (notes), @ehelms, @pcreech

News since last meeting

Resolved issues

CentOS CI: completed. Only issue is that bats results overwrite eachother, making debugging harder.

In progress

Allow building on RHEL in our Koji setup · Issue #1670 · theforeman/foreman-infra · GitHub

@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.

Investigate Azure's FOSS credits program · Issue #1671 · theforeman/foreman-infra · GitHub

We’ve gotten credits. Now have to document it and start using it. Developers working on Azure integration are also welcome to use this.

Allow use of Jenkinsfiles · Issue #1683 · theforeman/foreman-infra · GitHub

Moved back to To do since there’s no progress and not being actively worked on.

Need a new owner for Discourse · Issue #1709 · theforeman/foreman-infra · GitHub

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.

To do

move EL Jenkins nodes to EL8 · Issue #1706 · theforeman/foreman-infra · GitHub

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.

Update Foreman to 3.4 · Issue #1676 · theforeman/foreman-infra · GitHub

To be done after Foreman has migrated to the new infra.

Update Redmine and move to new infrastructure · Issue #1681 · theforeman/foreman-infra · GitHub

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.

Move Koji off of current AWS account to a new account or new infrastructure (e.g. Copr). · Issue #1795 · theforeman/foreman-infra · GitHub is opened to look into this.

Migrate Jenkins off of Rackspace · Issue #1684 · theforeman/foreman-infra · GitHub

@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.

1 Like