Overall, big +1 from me - it'll make my life easier too. Whilst I appreciate Katello is a big project in it's own right, it's never felt good to me that it lives in it's own world despite every other plugin being in the Foreman namespace. Obviously there's historical reasons for that, but tradition for tradtion's sake is no argument at all :)
Some thoughts on the various points: # foreman-bats -> forklift merge This does indeed feel like duplication of effort. It's also an area where we have some flexibility, since we *can* choose to disable some types of test in the short term if we need to (obviously thats not ideal though). The path forward is clearly to get forklift where it needs to be before removing bats for good, +1 there. There's also the CentOS CI project, but I'll send a separate mail about that since it's additional to bats/forklift rather than integral. # katello-packaging -> foreman-packaging Overall, in favour, it makes it possible for me to do better metrics on Katello usage. About 1/3rd of our substantial budget from Rackspace goes on bandwidth, but what I can't see is how much of that is our own consumption for package building and testing. It may be worth looking into caching / internal Rackspace-IP mirrors for our builders before we take the plunge on this. As for the modules / installer, +1 in general, no specific comments :) If I can help at all from an infra perspective, let me know, especially if you need insights into the Rackspace usage etc. Greg -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
