IssueRaiser

Provide mechanism for streaming logs from modules

# Proposal: Provide mechanism for streaming logs from modules *Author*: Monty Taylor <@emonty> IRC: mordred *Date*: 2018/01/04 - Status: New - Proposal type: core design - Targeted Release: 2.6 - Estimated time to implement: not too terribly long - agreeing on the design is the hard part ## Motivation Long running tasks can be a black hole of despair for a user, and waiting until one is complete to be able to see what happened can often be frustrating. We have a hacked-in version of output streaming for command/shell modules in our ansible-playbook invocations in Zuul v3: https://github.com/openstack-infra/zuul/blob/feature/zuulv3/zuul/ansible/library/command.py https://github.com/openstack-infra/zuul/blob/feature/zuulv3/zuul/ansible/callback/zuul_stream.py#L118-L167 but it would be better if such a facility was available to all ansible users, and for a facility to exist for module authors to be able to do something similar. Assuming we can agree on an overall approach, we can implement the majority of this as an update to the existing zuul streaming code and then forklift it over when it's working well. (most of the code is in standalone classes with minimal amounts of updates to the guts of existing Ansible objects) ### Problems What problems exist that this proposal will solve? - Output from long-running tasks is not available until the task is complete - Modules that use third-party libraries that have python stdlib logging based logging can't wire up those l

Posted by emonty on Jan 4, 2018, 8:13 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments

github (Sysadmin)

Provide mechanism for streaming logs from modules

emontyJan 4, 2018, 8:13 PM

# Proposal: Provide mechanism for streaming logs from modules *Author*: Monty Taylor <@emonty> IRC: mordred *Date*: 2018/01/04 - Status: New - Proposal type: core design - Targeted Release: 2.6 - Estimated time to implement: not too terribly long - agreeing on the design is the hard part ## Motivation Long running tasks can be a black hole of despair for a user, and waiting until one is complete to be able to see what happened can often be frustrating. We have a hacked-in version of output streaming for command/shell modules in our ansible-playbook invocations in Zuul v3: https://github.com/openstack-infra/zuul/blob/feature/zuulv3/zuul/ansible/library/command.py https://github.com/openstack-infra/zuul/blob/feature/zuulv3/zuul/ansible/callback/zuul_stream.py#L118-L167 but it would be better if such a facility was available to all ansible users, and for a facility to exist for module authors to be able to do something similar. Assuming we can agree on an overall approach, we can implement the majority of this as an update to the existing zuul streaming code and then forklift it over when it's working well. (most of the code is in standalone classes with minimal amounts of updates to the guts of existing Ansible objects) ### Problems What problems exist that this proposal will solve? - Output from long-running tasks is not available until the task is complete - Modules that use third-party libraries that have python stdlib logging based logging can't wire up those l

Comments (0)

No comments yet. Start the discussion.

Comment on this issue