On Sunday, September 7, 2014 5:22:49 AM UTC+2, Michael DeHaan wrote:
Of course it is your prerogative, and there are development schedules and
all sorts of things to consider, and maybe this clashes with your
commercial offering (i.e. from the press release: Tower's real-time
output of
Right in my original email this was a progress bar at the top level. I was
thinking a playbook has something like 50 plays in it, I would like to see
a progress bar of 1 through 50 multiplied by the number of hosts...
Right, some lines from the latest command would not quite be a progress
No, bringing it up periodically can't really help it make it be true any
better.
Please read my last comment I made in the ticket.
The most important point is point #1 -- nearly all of the modules involved
have absolutely no API or notion of what percentage complete they are, but
the other
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
On Saturday, September 6, 2014 3:48:35 PM UTC+2, Michael DeHaan wrote:
No, bringing it up periodically can't really help it make it be true any
better.
Well I work professionally as a developer (like I am sure the vast majority
of the people on this list) and I can say the weight of user
Of course it is your prerogative, and there are development schedules and
all sorts of things to consider, and maybe this clashes with your
commercial offering (i.e. from the press release: Tower's real-time
output of Ansible Playbooks includes dynamic progress bars that show you
the status
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
It would be really nice to have progress bars at various levels. When
running a playbook
Thanks, I've locked the topic to save folks from trying to comment on it,
as we don't see those comments.
This isn't really possible in any sort of clean way and we've explained why
already on several occasions.
On Fri, Sep 5, 2014 at 2:40 PM, Jason Harris jason.f.har...@gmail.com
wrote:
See docs on async for how to report if things are still running for long
running tasks, as well as how to set timeouts.
On Fri, Sep 5, 2014 at 2:56 PM, Michael DeHaan mich...@ansible.com wrote:
Thanks, I've locked the topic to save folks from trying to comment on it,
as we don't see those
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
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
11 matches
Mail list logo
