Hi Adam, the idea of numbering the plays and tasks is different than the indeterminate status of the tasks.
It's also possible to number what host number is coming back pretty easily, theoretically. Play 1/45: ASDF Task 5/10: JKL Host [35%]: asdf.example.com => result etc Those kinds of things are more available to the system and possible. On Fri, Sep 5, 2014 at 6:09 PM, Adam Heath <a...@brainfood.com> wrote: > Something like "Play (7 of 12) Task (4 of 15)". There's no way to have > any kind of time estimate, but a simple X of Y count seems useful. > > > On 09/05/2014 04:52 PM, Jason Harris wrote: > >> >> >> On Friday, September 5, 2014 8:56:13 PM UTC+2, Michael DeHaan wrote: >> >> Thanks, I've locked the topic to save folks from trying to comment >> on it, as we don't see those comments. >> >> >> Well, at least it was a place where people could feel they could leave >> some sort of feedback and feel they could say "Yes... we really really want >> this feature..." I guess we just bring this up periodically in the forums >> then? >> >> This isn't really possible in any sort of clean way and we've >> explained why already on several occasions. >> >> >> Well surely at the top level having a progress bar for the whole playbook >> is possible? There is nothing technical stopping that. Right? >> >> And surely when we have async tasks right now (which I use) instead of >> just printing down the screen right now something like: >> >> TASK: [bitnami_rubystack | Install rubystack] >> ********************************* >> >> <job 409801362883.2948> polling, 990s remaining >> >> <job 409801362883.2948> polling, 980s remaining >> >> <job 409801362883.2948> polling, 970s remaining >> >> <job 409801362883.2948> polling, 960s remaining >> >> <job 409801362883.2948> polling, 950s remaining >> >> <job 409801362883.2948> polling, 940s remaining >> >> <job 409801362883.2948> polling, 930s remaining >> >> <job 409801362883.2948> polling, 920s remaining >> >> >> It could have a better output where there is just a single line which is >> counting down? >> >> Also with the async process can't the last line of the current task be >> captured and displayed? and just written over each time? sort of like >> periodically doing the async connect and grabbing 'tail --lines 1 >> progresslog" and displaying that? >> >> I don't know the details but there must be something that can be done! >> and it is very very clear that users want something like this. I wanted it >> from practically the moment I started using ansible and it is likely my top >> issue with ansible. >> >> (In any case thanks for ansible, I really like most of it!) >> >> Cheers, >> Jas >> >> >> On Fri, Sep 5, 2014 at 2:40 PM, Jason Harris <jason.f...@gmail.com >> <javascript:>> wrote: >> >> Hi, >> >> I just wanted to bring up progress bars again and monitoring >> of long running tasks. >> >> There is something approaching 50 +1's to the bug report / >> request https://github.com/ansible/ansible/issues/3887 >> <https://github.com/ansible/ansible/issues/3887> >> >> It would be really nice to have progress bars at various >> levels. When running a playbook and you are not debugging it, >> it would be very nice to have the option to be able to instead >> of getting screenfuls of output to instead have a progress >> bar, much like git or mercurial do (and details would just be >> sent to some log file). Eg to see a video of the kind of >> progress indicator I am talking about see: >> https://github.com/noamraph/tqdm >> <https://github.com/noamraph/tqdm> >> >> On the other extreme it would be nice to have progress >> indicators / feedback mechanisms for some of the really long >> running tasks to figure out if they have hung or not. I don't >> know any of the details of the internals of ansible or how to >> make this work, but from the bug report this is obviously a >> very highly desired feature which many people want... >> >> Other threads about this: >> https://groups.google.com/forum/#!msg/ansible-devel/ >> cvbyUMspqE0/DMLaYR8DfUoJ >> <https://groups.google.com/forum/#%21msg/ansible-devel/ >> cvbyUMspqE0/DMLaYR8DfUoJ> >> >> Thanks, >> Jason >> -- You received this message because you are subscribed >> to the >> Google Groups "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from >> it, send an email to ansible-proje...@googlegroups.com >> <javascript:>. >> To post to this group, send email to >> ansible...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/ >> dded9e93-da99-49ad-80ad-167eb21919e5%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/ >> dded9e93-da99-49ad-80ad-167eb21919e5%40googlegroups. >> com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ansible-project+unsubscr...@googlegroups.com <mailto: >> ansible-project+unsubscr...@googlegroups.com>. >> To post to this group, send email to ansible-project@googlegroups.com >> <mailto:ansible-project@googlegroups.com>. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/ansible-project/050a3903-34ff-4fe9-b832- >> b53365e28ae5%40googlegroups.com <https://groups.google.com/d/ >> msgid/ansible-project/050a3903-34ff-4fe9-b832- >> b53365e28ae5%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/ansible-project/540A34B6.2050601%40brainfood.com. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgx-f0KyqL7gCV1PMX5y1Nnfng%2BK7cEOp4Trt0mdH103eA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
