[katello] Keeping track of current dev environment status

Development
1

Hello all,

I know sometimes I wonder if I need any workarounds to spin up a working
katello dev environment. Sometimes we need to use koji repos, installer
patches, or have to librarian-puppet install. These workarounds are often
discussed on IRC, but its easy to miss these discussions.

I think a central place to keep track of "What do I need to do to spin up a
working dev environment?" would be beneficial to all katello devs and help
us not waste time trying different configurations.

Since I am on bats/pipeline duty these two weeks I started keeping track of
this on the bats duty etherpad [1]

What I am proposing is whoever is on bats/pipeline duty also keeps track of
what is needed to spin up a working centos7 dev environment, tests this
regularly, and updates the etherpad. Let me know what you all think of this
idea, and if everyone is willing to participate. Feedback welcome.

[1] http://pad-katello.rhcloud.com/p/bats-batting-order

Thanks,

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

2

For installer patches I highly recommend keeping an eye on
theforeman/foreman-installer and theforeman/puppet-* since they often
have workarounds submitted as pull requests. They are often applicable
to Katello as well.

ยทยทยท On Fri, Jun 17, 2016 at 11:33:25AM -0400, John Mitsch wrote: > I know sometimes I wonder if I need any workarounds to spin up a working > katello dev environment. Sometimes we need to use koji repos, installer > patches, or have to librarian-puppet install. These workarounds are often > discussed on IRC, but its easy to miss these discussions.