[Pulp-dev] No 'result' field for a Task in Pulp3

Jeff Ortel jortel at redhat.com
Mon Apr 24 19:48:29 UTC 2017

On 03/28/2017 12:16 PM, Brian Bouterse wrote:
> Today on a call an observation was made that Pulp3 does not need 'results' for a task. All non-error info
> about what happened during a task is associated with it's associated "Progress Report" objects [0].

The progress report is a snapshot of what a running task is currently doing and metrics on how much progress
has been made.  In part so users can know progress is begin made and estimate the task's completion.  The
"result" report /could/ provide an indicator of success and a summary/detail of work completed.  These two
things seem completely different.  I'm not advocating for a "result", just pointing out the differences.

> Is there a use case where 'result' is meaningful that we preclude by removing it?
> I created the task [1] to rename 'result' to 'error' since we still need a field to track fatal exceptions
> which was one of the purposes of the results field in the existing pulp3 design. Feel free to comment on if we
> should do [1] either here or in Redmine.
> [0]: https://github.com/pulp/pulp/blob/3.0-dev/app/pulp/app/models/progress.py#L15
> [1]: https://pulp.plan.io/issues/2675
> -Brian
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 847 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170424/76a41b1d/attachment.sig>

More information about the Pulp-dev mailing list