The last update was nearly two months ago and our migration to discourse allows me to provide a slightly better formatted status on the roadmap. If anyone has any new items that feel need to be added to this list of
items please let me know as I’d like to capture the breadth of our infrastrucre/CI/deployment.
Rails 5.X
Status: Complete
Action Items
- None
Updates
- Rails 5 SCL has been built. This repository lives on Copr.
- Foreman, Plugins and Katello have all been rebuilt on Rails 5.1 and nightly repositories have been officially updated with passing builds.
- Foreman 1.17 and Katello 3.6 are branched and based off of the Rails 5.1 and Ruby 2.4 stack updates
Historical
- Proposal for building Rails 5.1 SCL sent to list –
https://groups.google.com/forum/#!topic/foreman-dev/xyo-Q2afuCI - Discussion on vendorizing vs. building SCL
https://groups.google.com/forum/#!topic/foreman-dev/xJyxMx1lXy4
https://groups.google.com/forum/#!topic/foreman-dev/xJyxMx1lXy4 - Notice of current state of core running on 5.1:
https://groups.google.com/forum/#!topic/foreman-dev/kCMCCNZUN4w
https://groups.google.com/forum/#!topic/foreman-dev/kCMCCNZUN4w
need rh-ror50 or custom built SCL
Packaging Automation
Status: green
Updates
- Proposal and task breakout sent to discourse – Packaging Automation Proposal RFC
- Work has begun to make Obal meet foreman-packaging needs
Jenkins Migration
Status: Blocked
Updates
- None
Action Items
- Migrate Jenkins master to EL7
- redirect from HTTP needs adding
Completed
- Jenkins now has HTTPS interface: https://ci.theforeman.org/
Jenkins Job Updates
Status: In Progress
Updates
- Foreman nightly release pipeline job created and in JJB
- Foreman plugins nightly release pipeline created and has replaced former Foreman plugins release jobs
- Katello nightly release pipeline created and has replaced former
- Top level symlink ‘ci’ added to foreman-infra
Action Items
- Move all jobs into JJB
- Update jobs to run tests with all plugins installed
- Update hammer core tests to run tests also for the major plugins (atleast foreman and katello)
- Add job for running hammer integration tests against live foreman/katello
Historical
Q: What is the benefit for this effort?
A: modern approach, more secure, provides more efficient jobs, jobs that
are protected against crashes and restarts
Running Container Stack
Status: In Progress
Updates
- On going work to re-factor tooling and add a PR testing job
- Updated to latest Openshift 3.7.1
- Fixes submitted to ansible-container
Action Items
- address Github issues created from initial merge remove current hacks in deployment
- build up test suite for verifying container stack
- add Jenkins job to build containers nightly
Historical
- Container effort repository – https://github.com/theforeman/forklift/tree/master/containers
Merging katello and foreman installers
Status: red
Updates
- None
Action Items
- Move all checks/hooks to foreman-installer
- Add katello modules to foreman-installer Puppetfile
- Move bin/{foreman-proxy-certs-generate,katello-certs-check} to foreman-installer or foreman-maintain
- Migrate scenarios
- Sort out the packaging
- Add deprecation notices to katello-installer / wipe master branch
Updated yum/debian repository structure
Status: blocked
Updates
- None
Action Items
- Email thread discussing re-structure of repositories
- agree on layout
- re-factor mash scripts for new deployment
- re-factor sync scripts to yum/deb repositories
- update foreman release RPM for new repositories
Move package building from Koji to Copr
Status: red
Updates
- De-prioritized in favor of packaging automation changes
Action Items
- Phase 1: Submit builds in paralel - only rubygems and nodejs
- Phase 2: Submit builds in paralel - foreman-core packages
- Phase 3: Migrate to Copr
Migration off of Openshift V2
Status: red
Updates
- Redmine – moved to stand alone server and off of Openshift entirely
- prprocessor – moved to Redmine server
- etherpad – didn’t get moved off of Openshift V2, is currently dead with no way to recover database from the last two months