Looked good. I had a few questions around remote management:
How do you envision deliving commands which are integrated with the
app? For example, the puppet run and reboot commands from core, and the
install package commands from katello.
What happens when the smart proxy goes down while iterating over the
commands? Where is state stored?
– bk
···
On 08/06/2015 10:14 AM, Eric D Helms wrote:
> Hi All,
>
> Today we had another installment of the Foreman community demo that
> featured:
>
> * New option in discovery image: fdi.initnet (lzap)
> * PXELess discovery update (lzap)
> * Updates in hammer - new command for building pxe default, listing all
> records by default (tstrachota)
> * Versioned API documentation at theforeman.org
> (tstrachota)
> * News in foreman remote execution (inecas)
> * rake foreman_tasks:cleanup (inecas)
> * discovered hosts status dashboard widget (stbenjam)
> * preview of upcoming UI changes to parameters (tbrisker)
> * new "Inherit" button in host edit form (sshtein)
>
> The recording can be watched at:
> https://www.youtube.com/watch?v=l6aIVPSfdww&feature=youtu.be
>
> If you have questions regrading what you see in the demo, please feel
> free to reply to this thread.
>
> --
> Eric D. Helms
> Red Hat Engineering
> Ph.D. Student - North Carolina State University
>
> --
> 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 foreman-users+unsubscribe@googlegroups.com
> .
> To post to this group, send email to foreman-users@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
> 1) How do you envision deliving commands which are integrated with the
> app? For example, the puppet run and reboot commands from core, and the
> install package commands from katello.
Commands (aka Job Templates) are another kind of templates like Provisioning
Template or Partition Table. So commands that comes from apps or plugins will
be shipped in a same way, which means db seed will be used. Hopefully we could
later enhance foreman_templates plugins so the definitions could be synced
from either community-templates or your own git repo.
> 2) What happens when the smart proxy goes down while iterating over the
> commands? Where is state stored?
All information is on Foreman server, orchestrated by dynflow. If smart proxy
goes down, we have timeout and retry mechanism and all other standard dynflow
recovery options. As a reaction to timeout we could even try running a command
through another proxy.
I hope this answers your questions
···
--
Marek
– bk
On 08/06/2015 10:14 AM, Eric D Helms wrote:
Hi All,
Today we had another installment of the Foreman community demo that
featured:
New option in discovery image: fdi.initnet (lzap)
PXELess discovery update (lzap)
Updates in hammer - new command for building pxe default, listing all
records by default (tstrachota)
> Hello
>
> trying to answer below in text.
>
> > 1) How do you envision deliving commands which are integrated with the
> > app? For example, the puppet run and reboot commands from core, and the
> > install package commands from katello.
>
> Commands (aka Job Templates) are another kind of templates like Provisioning
> Template or Partition Table. So commands that comes from apps or plugins will
> be shipped in a same way, which means db seed will be used. Hopefully we
> could
> later enhance foreman_templates plugins so the definitions could be synced
> from either community-templates or your own git repo.
The second part of the answer lies here is described here:
This should provide the mapping mechanism between the features of core/plugins,
and the remote execution templates.
>
> > 2) What happens when the smart proxy goes down while iterating over the
> > commands? Where is state stored?
>
> All information is on Foreman server, orchestrated by dynflow. If smart proxy
> goes down, we have timeout and retry mechanism and all other standard dynflow
> recovery options. As a reaction to timeout we could even try running a
> command
> through another proxy.
One thing that we don't do though, is sending the data to the foreman server
before the command on single host finishes: this could generate quite a lot of traffic
and processing overload: so the need for this would need to be justified pretty
well (and the right answer in that case might be using different provider if concerned).
– Ivan
···
----- Original Message -----
I hope this answers your questions
–
Marek
– bk
On 08/06/2015 10:14 AM, Eric D Helms wrote:
Hi All,
Today we had another installment of the Foreman community demo that
featured:
New option in discovery image: fdi.initnet (lzap)
PXELess discovery update (lzap)
Updates in hammer - new command for building pxe default, listing all
records by default (tstrachota)
