Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1319950 - [RFE] Repository Discovery for Docker
Summary: [RFE] Repository Discovery for Docker
Keywords:
Status: CLOSED DUPLICATE of bug 1268026
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 23:02 UTC by Partha Aji
Modified: 2019-04-01 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-26 14:13:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Partha Aji 2016-03-21 23:02:54 UTC
Satellite provides the ability to search repositories in Docker Hub/External Registries when one does Containers -> New Container -> <select compute resource> -> Docker Hub/External registry

This functionality could be ideally leveraged in the following workflow
1) Content -> Products
2) Click on Repo Discovery (or may be a new one for Docker Repos),
3) Use the Docker Hub/External Registry to search repositories in those registries (output like -> https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=busybox&starCount=0 )
4) Have the user select the repository they want from the search. They select the product and click "Create Selected"
5) New Repositories created in Library.'



Potential Issues
1) Search likely requires V1 support in Docker Hub/External Registries since that endpoint is not supported in V2 registries
2) The search results contain minimal information, like the a 40 character description, and the repo owner. We may want to provide the user the url on the repo specs in docker hub

Comment 2 Tom McKay 2017-01-26 14:13:54 UTC

*** This bug has been marked as a duplicate of bug 1268026 ***


Note You need to log in before you can comment on or make changes to this bug.