See Progress status when running Puppet Run

Hi everyone,

I was wondering, is there a way to see the progress of a deployment when
running a "Puppet Run" (via puppet kick or mcollective)??
I think this would be a nice feature, because right now the only way too
see this is directly looking at the log files. It would be nice to have a
"progress bar" of the deployment.

Cheers,
Cesar

We discussed this last week, because we want to implement progress bar
for the foreman installer itself (it's puppet based).

Short answer - you can't really do it. Puppet is a declarative language
and you can't tell where the deployment process is. Katello installer is
"faking" progress bars by watching logs and since it already knows
approximate target log size, it shows progress.

But for your own deployments, Foreman can't calculate this. Each host
has unique setup. What we could do is draw a fake progress bar - each
class applied one part. But applying ssh keys can consume no time while
apache2 httpd complex deployment can take minutes. The result would be
quite funky.

LZ

··· On Tue, Jul 16, 2013 at 08:36:46AM -0700, MrTeleBird wrote: > Hi everyone, > > I was wondering, is there a way to see the progress of a deployment when > running a "Puppet Run" (via puppet kick or mcollective)?? > I think this would be a nice feature, because right now the only way too > see this is directly looking at the log files. It would be nice to have a > "progress bar" of the deployment. > > Cheers, > Cesar > > -- > 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/groups/opt_out. > >


Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

Pulp has a spinner type feature to show that something is happening.
Would that be useful?

– bk

··· On 07/16/2013 03:42 PM, Lukas Zapletal wrote: > We discussed this last week, because we want to implement progress bar > for the foreman installer itself (it's puppet based). > > Short answer - you can't really do it. Puppet is a declarative language > and you can't tell where the deployment process is. Katello installer is > "faking" progress bars by watching logs and since it already knows > approximate target log size, it shows progress. > > But for your own deployments, Foreman can't calculate this. Each host > has unique setup. What we could do is draw a fake progress bar - each > class applied one part. But applying ssh keys can consume no time while > apache2 httpd complex deployment can take minutes. The result would be > quite funky. > > LZ > > On Tue, Jul 16, 2013 at 08:36:46AM -0700, MrTeleBird wrote: >> Hi everyone, >> >> I was wondering, is there a way to see the progress of a deployment when >> running a "Puppet Run" (via puppet kick or mcollective)?? >> I think this would be a nice feature, because right now the only way too >> see this is directly looking at the log files. It would be nice to have a >> "progress bar" of the deployment. >> >> Cheers, >> Cesar >> >> -- >> 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/groups/opt_out. >> >> >

I hate spinners :slight_smile:

LZ

··· On Tue, Jul 16, 2013 at 03:44:24PM -0400, Bryan Kearney wrote: > Pulp has a spinner type feature to show that something is happening. > Would that be useful? > > -- bk > > On 07/16/2013 03:42 PM, Lukas Zapletal wrote: > >We discussed this last week, because we want to implement progress bar > >for the foreman installer itself (it's puppet based). > > > >Short answer - you can't really do it. Puppet is a declarative language > >and you can't tell where the deployment process is. Katello installer is > >"faking" progress bars by watching logs and since it already knows > >approximate target log size, it shows progress. > > > >But for your own deployments, Foreman can't calculate this. Each host > >has unique setup. What we could do is draw a fake progress bar - each > >class applied one part. But applying ssh keys can consume no time while > >apache2 httpd complex deployment can take minutes. The result would be > >quite funky. > > > >LZ > > > >On Tue, Jul 16, 2013 at 08:36:46AM -0700, MrTeleBird wrote: > >>Hi everyone, > >> > >>I was wondering, is there a way to see the progress of a deployment when > >>running a "Puppet Run" (via puppet kick or mcollective)?? > >>I think this would be a nice feature, because right now the only way too > >>see this is directly looking at the log files. It would be nice to have a > >>"progress bar" of the deployment. > >> > >>Cheers, > >>Cesar > >> > >>-- > >>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/groups/opt_out. > >> > >> > > > > -- > 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/groups/opt_out. > >


Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

Yes, but better then the "hmm… I wonder if anything is happening"

– bk

··· On 07/16/2013 03:46 PM, Lukas Zapletal wrote: > I hate spinners :-) > > LZ > > On Tue, Jul 16, 2013 at 03:44:24PM -0400, Bryan Kearney wrote: >> Pulp has a spinner type feature to show that something is happening. >> Would that be useful? >> >> -- bk >> >> On 07/16/2013 03:42 PM, Lukas Zapletal wrote: >>> We discussed this last week, because we want to implement progress bar >>> for the foreman installer itself (it's puppet based). >>> >>> Short answer - you can't really do it. Puppet is a declarative language >>> and you can't tell where the deployment process is. Katello installer is >>> "faking" progress bars by watching logs and since it already knows >>> approximate target log size, it shows progress. >>> >>> But for your own deployments, Foreman can't calculate this. Each host >>> has unique setup. What we could do is draw a fake progress bar - each >>> class applied one part. But applying ssh keys can consume no time while >>> apache2 httpd complex deployment can take minutes. The result would be >>> quite funky. >>> >>> LZ >>> >>> On Tue, Jul 16, 2013 at 08:36:46AM -0700, MrTeleBird wrote: >>>> Hi everyone, >>>> >>>> I was wondering, is there a way to see the progress of a deployment when >>>> running a "Puppet Run" (via puppet kick or mcollective)?? >>>> I think this would be a nice feature, because right now the only way too >>>> see this is directly looking at the log files. It would be nice to have a >>>> "progress bar" of the deployment. >>>> >>>> Cheers, >>>> Cesar >>>> >>>> -- >>>> 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/groups/opt_out. >>>> >>>> >>> >> >> -- >> 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/groups/opt_out. >> >> >

A status bar is psychologically useful, even if it isn't accurate.

If we know that there are 40 points, but have no idea how long each
takes you can just have it move as it passes through each point.

Two additional tricks.

  1. We can have half ticks that move during an arbitrary time that is
    half a timeout value
  2. We can frontload the first 1/3 of the bar, with the first 2/3 of
    the points. It's a psychological trick used by UI designers to make
    the wait more bearable.

Cheers,
Brian

··· On Tue, Jul 16, 2013 at 3:54 PM, Bryan Kearney wrote: > Yes, but better then the "hmm.. I wonder if anything is happening" > > -- bk > > > On 07/16/2013 03:46 PM, Lukas Zapletal wrote: >> >> I hate spinners :-) >> >> LZ >> >> On Tue, Jul 16, 2013 at 03:44:24PM -0400, Bryan Kearney wrote: >>> >>> Pulp has a spinner type feature to show that something is happening. >>> Would that be useful? >>> >>> -- bk >>> >>> On 07/16/2013 03:42 PM, Lukas Zapletal wrote: >>>> >>>> We discussed this last week, because we want to implement progress bar >>>> for the foreman installer itself (it's puppet based). >>>> >>>> Short answer - you can't really do it. Puppet is a declarative language >>>> and you can't tell where the deployment process is. Katello installer is >>>> "faking" progress bars by watching logs and since it already knows >>>> approximate target log size, it shows progress. >>>> >>>> But for your own deployments, Foreman can't calculate this. Each host >>>> has unique setup. What we could do is draw a fake progress bar - each >>>> class applied one part. But applying ssh keys can consume no time while >>>> apache2 httpd complex deployment can take minutes. The result would be >>>> quite funky. >>>> >>>> LZ >>>> >>>> On Tue, Jul 16, 2013 at 08:36:46AM -0700, MrTeleBird wrote: >>>>> >>>>> Hi everyone, >>>>> >>>>> I was wondering, is there a way to see the progress of a deployment >>>>> when >>>>> running a "Puppet Run" (via puppet kick or mcollective)?? >>>>> I think this would be a nice feature, because right now the only way >>>>> too >>>>> see this is directly looking at the log files. It would be nice to have >>>>> a >>>>> "progress bar" of the deployment. >>>>> >>>>> Cheers, >>>>> Cesar >>>>> >>>>> -- >>>>> 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/groups/opt_out. >>>>> >>>>> >>>> >>> >>> -- >>> 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/groups/opt_out. >>> >>> >> > > -- > 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/groups/opt_out. > >

Yes, I agree that it would be better to see that something is happening. I
think in gheneral would be nice to have some space where current catalogue
runs, either automatic or started via puppet run, are display, ideally with
some status bar.
Cheers

The issue is harder than simply implementing the UI part - Puppet doesn't
send it's report to the master (and then to Foreman) until the run is
complete. As such, you'd need a way to get the data from the client while
the run is happening. Off the top of my head, you might be able to do that
with central syslog logging to the foreman box, or by modifying the puppet
core codebase substanstially to log remotely during the run. Either way,
it'll be messy, I think.

Greg

··· On 17 July 2013 08:56, MrTeleBird wrote:

Yes, I agree that it would be better to see that something is happening. I
think in gheneral would be nice to have some space where current catalogue
runs, either automatic or started via puppet run, are display, ideally with
some status bar.
Cheers