<div dir="ltr"><div>Yes a 'summary' or 'result' field would be distinctly valuable from the progress reporting. Whatever data gets put in a 'summary' field I think needs to be structured in a way that the CLI can parse and show it beautifully. I don't have a clear idea of what that looks like across different plugin types, but if there are ideas of a structure getting those written out would be good. Is adding a field like that the kind of thing that would go in the MVP [0] for Pulp3 or on the future feature list [1]? </div>As an update on the current state of things. The "result" field was removed as part of [2]. <div> [0]: <a href="https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viable_Product">https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viable_Product</a> [1]: <a href="https://pulp.plan.io/projects/pulp/wiki/31+_Ideas_(post_MVP)">https://pulp.plan.io/projects/pulp/wiki/31+_Ideas_(post_MVP)</a> [2]: <a href="https://pulp.plan.io/issues/2675">https://pulp.plan.io/issues/2675</a> </div><div>-Brian </div></div><div class="gmail_extra"> <div class="gmail_quote">On Mon, Apr 24, 2017 at 3:48 PM, Jeff Ortel <<a href="mailto:jortel@redhat.com" target="_blank">jortel@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> 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]: <a href="https://github.com/pulp/pulp/blob/3.0-dev/app/pulp/app/models/progress.py#L15" rel="noreferrer" target="_blank">https://github.com/pulp/pulp/blob/3.0-dev/app/pulp/app/models/progress.py#L15</a> > [1]: <a href="https://pulp.plan.io/issues/2675" rel="noreferrer" target="_blank">https://pulp.plan.io/issues/2675</a> > > -Brian > > > _______________________________________________ > Pulp-dev mailing list > <a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> > <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a> > _______________________________________________ Pulp-dev mailing list <a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a> </blockquote></div> </div>