Project

Profile

Help

Story #5120

As a user, I can filter tasks by their 'reserved_resources'

Added by dkliban@redhat.com over 1 year ago. Updated about 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 56
Quarter:

Description

User migrating from Pulp 2 will create an instance of a Migration Plan in Pulp 3 by uploading the migration plan as JSON. Then the user is going to dispatch a task to execute the Migration Plan. All the progress from running the migration plan task is going to be recorded using Progress Reports for the Task. While the user is currently able to perform a GET on a specific Task to check progress, the user is unable to find a Task associated with a particular Migration Plan. This makes it difficult to know if a specific Migration Plan has been executed or not.

The ReservedResource object is ephemeral. As a result, the Task API does not include the reserved resources. A filter for tasks on 'reserved_resources' would require the following changes:

- Add a ReservedResourceRecord model that has the same fields as ReservedResource
- Create an instance of ReservedResourceRecord when creating ReservedResource
- Add a 'reserved_resources' field to the TaskSerializer that will get data from the ReservedResourceRecord table
- Extend the TaskFilter with a 'reserved_resources' filter


Related issues

Has duplicate Migration Plugin - Story #5080: As a user, I can track which tasks were using a specific Migration PlanCLOSED - DUPLICATE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 0c51cba1 View on GitHub
Added by Lubos Mjachky over 1 year ago

Implement filter for duplicated reserved_resources

closes #5120 https://pulp.plan.io/issues/5120

History

#1 Updated by dkliban@redhat.com over 1 year ago

  • Tracker changed from Issue to Story
  • % Done set to 0

#2 Updated by dkliban@redhat.com over 1 year ago

  • Description updated (diff)

#3 Updated by daviddavis over 1 year ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

I would probably call it a TaskResource since it's not reserved once the task is finished. Also this could be used in the future to store other resources that the task acts upon but does not need to explicitly lock. But other than that I think this task is ready to be worked on. Setting to groomed.

#4 Updated by dkliban@redhat.com over 1 year ago

  • Description updated (diff)
  • Groomed changed from Yes to No
  • Sprint Candidate changed from Yes to No

#5 Updated by dkliban@redhat.com over 1 year ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

#6 Updated by rchan over 1 year ago

  • Sprint set to Sprint 56

#7 Updated by rchan over 1 year ago

  • Sprint/Milestone set to 3.0.0

#8 Updated by ipanova@redhat.com over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to lmjachky

#9 Updated by ttereshc over 1 year ago

  • Has duplicate Story #5080: As a user, I can track which tasks were using a specific Migration Plan added

#10 Updated by ipanova@redhat.com over 1 year ago

  • Description updated (diff)

#11 Updated by lmjachky over 1 year ago

  • Status changed from ASSIGNED to POST

#12 Updated by Anonymous over 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#13 Updated by bmbouter about 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF