The work Sebastian mentions here [1] and talked about in my deep dive have now been merged to Forklift.
Does this mean it's developer or production ready? No, there is still a chunk of work as outlined by [2] but this does push us closer to having a more stable version of this working. What does this mean for me then? If you are interested in container work, you can now more easily collaborate on the work by: 1) Testing and using it and filing issues at [3] 2) Tackling one of the open issues at [2] 3) Open PRs to Forklift master with fixes and enhancements Eric [1] https://github.com/theforeman/forklift/pull/424 [2] https://github.com/theforeman/forklift/projects/1 [3] https://github.com/theforeman/forklift/issues/new On Wed, Jun 21, 2017 at 9:10 AM, Sebastian Gräßl <sebast...@validcode.me> wrote: > Hej all, > > There have been a few requests and questions about official containers > already > and it may increase with the push of container infrastructure. > There have also been conversations in the past about containers and > even though Foreman has it's focus more on lower decks of the > infrastructure, > putting more effort into documenting and taking action to easily start a > Foreman > or Katello container either as standalones or in combination with services > in other containers. > > Eric has already done great work in forklift[1] to build images with > ansible-container and setting up containers in Open Shift. > There are also other repositories that on GitHub to build foreman and > smart-proxy images[2][3] and > there are probably a few local experiments around as well. > > Once Eric's PR is merged, I'm going to building scripts and jobs for/in > Jenkins. > > There is already an image on Docker Hub[4], which should, when ready, > be replaced by the new nightly ones and pushed regularly. > > Meanwhile it might be good to have a discussion on what the expectations > are on how the images can be used. > > All the best, > Sebastian > > [1] https://github.com/theforeman/forklift/pull/424 > [2] https://github.com/HearstAT/docker_foreman_dev > [3] https://github.com/HearstAT/docker_foreman_smart_proxy_chef > [4] https://hub.docker.com/r/foreman/foreman/ > > -- > 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 foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering -- 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 foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
