On Fri, Jun 30, 2017 at 1:35 AM, Eric D Helms <[email protected]> wrote:
> Thanks for setting this up Greg. > > I wanted to send out a few notes ahead of time so that folks can do any > background reading, using the work I'll be presenting or think about > questions they might have. If you want to send along questions ahead of > time you'd like addressed (or to ensure I cover) please feel free to reply > here and I'll do my best to work them into the presentation. > > Rough Topics I'll be covering: > > * Brief presentation on why containers, the technologies involved in > build and deploy > * Architecture presentation of service breakdown > * How the PR[1] works > * Current state and future Roadmap > I would be happy if you could also cover: - Smart proxy features (and how it works - e.g. a container per feature with base container etc). - Dev vs Production (whats in scope vs not) - Installer - do we still need it in a context of a Kubernetes application? - SCL ? can we move away from it? - reuse? for example, https://github.com/manageiq?q=container have some basic ruby / rails containers etc - application scaling ? (e.g. more dynflow workers etc). sorry for the long list :) thanks, Ohad > > > Thanks, > Eric > > > [1] https://github.com/theforeman/forklift/pull/424 > > On Thu, Jun 29, 2017 at 10:15 AM, Greg Sutcliffe <[email protected] > > wrote: > >> Hi all, >> >> Running Foreman in a container is a question that comes up from time to >> time in the Foreman community. Eric Helms has been experimenting with >> running the whole Foreman stack (core, proxies, plugins) inside >> Kubernetes, and wants to show you how it looks. We'll be holding a deep >> dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in >> here: >> >> https://www.youtube.com/watch?v=mPjUvNAYp1c >> >> As always, we welcome your contributions to the video - do join us live >> on YouTube Live chat or in our IRC channel to put your questions to >> Eric! >> >> Cheers, >> Greg >> -- >> IRC / Twitter: @gwmngilfen >> Diaspora: [email protected] >> >> -- >> 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. >> > > > > -- > Eric D. Helms > Red Hat Engineering > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
