Project

Profile

Help

Story #5231

Story #3821: As a user, I can migrate from Pulp 2 to Pulp 3

As a user, I can query Pulp 2->Pulp 3 mapping for migrated content

Added by ttereshc about 2 years ago. Updated over 1 year ago.

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

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 57
Quarter:

Description

Create a new endpoint to query the Pulp2-Pulp3 mapping for content.

Required info (agreed with Katello):

pulp2_content_id (e.g. '6168ebd6-0ffb-48b9-8ebb-e5f1775d1e0c')
pulp2_content_type (e.g. 'iso')
pulp3_content_href (e.g. '/pulp/api/v3/content/file/files/6d382246-4838-4350-a9ea-33e5de25ca11/d3cf852f-d7ff-40e0-b95b-5e35f74aacf8')
pulp3_content_type (e.g. 'file')
pulp3_created (time of creation in Pulp 3) (e.g."2019-07-22T10:06:48.881666Z")

This information can be found on Pulp2Content model.

Add ability to filter by content types and creation time.
Ask Katello if any other filters are needed,

Associated revisions

Revision 8bb46ecc View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: Pulp2Content can't be queried using REST API

Solution: add REST API for Pulp2Content

This patch adds a ViewSet, a Filter, and a Serializer for Pulp2Content model. This enables REST API users to retrieve a list of Pulp2Content as well as individual units. Lots of filters for filtering are also available.

fixes: #5231 https://pulp.plan.io/issues/5231

Revision 8bb46ecc View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: Pulp2Content can't be queried using REST API

Solution: add REST API for Pulp2Content

This patch adds a ViewSet, a Filter, and a Serializer for Pulp2Content model. This enables REST API users to retrieve a list of Pulp2Content as well as individual units. Lots of filters for filtering are also available.

fixes: #5231 https://pulp.plan.io/issues/5231

Revision 8bb46ecc View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: Pulp2Content can't be queried using REST API

Solution: add REST API for Pulp2Content

This patch adds a ViewSet, a Filter, and a Serializer for Pulp2Content model. This enables REST API users to retrieve a list of Pulp2Content as well as individual units. Lots of filters for filtering are also available.

fixes: #5231 https://pulp.plan.io/issues/5231

History

#1 Updated by ttereshc about 2 years ago

  • Description updated (diff)

#2 Updated by dkliban@redhat.com about 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dkliban@redhat.com
  • Groomed changed from No to Yes
  • Sprint set to Sprint 57

#3 Updated by jsherril@redhat.com about 2 years ago

Being able to filter by pulp2 ids would be great! We'd want to say something like 'here's 500 pulp ids for a given content type, give me all the pulp3 ids that correspond to them'

#4 Updated by dkliban@redhat.com about 2 years ago

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

Applied in changeset commit:pulp-2to3-migrate|8bb46ecc8c53339545be866653006aa48f7c2458.

#5 Updated by bmbouter almost 2 years ago

  • Sprint/Milestone set to 3.0.0

#6 Updated by bmbouter almost 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

#7 Updated by ttereshc over 1 year ago

  • Project changed from Pulp to Migration Plugin
  • Sprint/Milestone deleted (3.0.0)

#8 Updated by ttereshc over 1 year ago

  • Status changed from CLOSED - CURRENTRELEASE to MODIFIED

#9 Updated by ttereshc over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
  • Sprint/Milestone set to 0.1.0

Please register to edit this issue

Also available in: Atom PDF