I just wrote up a story to add an ability to filter Tasks by the resources
that they reserved. This is needed for the migration plan tasks and will be
just as useful for other tasks.

The design requires storing ReservedResources permanently in the database.
The status of the task associated with the ReservedResource will be used to
determine if a ReservedResource is still active or not. Additionally it
will no longer be necessary to dispatch a task for removing the
ReservedResource. Pulp will no longer have to dispatch 2 tasks for every
single task with a reservation.

What questions or concerns do you have?

[0] https://pulp.plan.io/issues/5120
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Reply via email to