Project

Profile

Help

Story #7977

As a user I'd like the pulp content landing page to be less cluttered

Added by wibbit 9 months ago. Updated 23 days ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Q4-2021

Description

Currently when view the pulp content landing page /pulp/content/ you are greeted with a list of all distributors that are hosted on the system (I believe).

Though the distributors support a directory structure, the landing page does not make use of this information.

Within our estate, within a year we could easily see ~30k distributors being created based on our current cadence (not including file and container distributors).

This will result in the landing page both being slow to load, and arguably unusable.

An example.

Say we have 4 distributors below.

/release/rpm/rhel7/some_repo
/release/rpm/rhel7/some_repo2
/trunk/rpm/rhel7/some_repo
/upstream/rpm/rhel7/some_repo

The landing page as it stands will have 4 hyper links.

/release/rpm/rhel7/some_repo
/release/rpm/rhel7/some_repo2
/trunk/rpm/rhel7/some_repo
/upstream/rpm/rhel7/some_repo

Would it be possible to have this landing page to look more like.

/release
/trunk
/upstream

Which links to the next depth (just as traversing a normal directory, or web site).

History

#1 Updated by fao89 9 months ago

  • Quarter set to Q1-2021

#2 Updated by daviddavis 5 months ago

  • Quarter changed from Q1-2021 to Q2-2021

#3 Updated by dkliban@redhat.com about 2 months ago

  • Description updated (diff)

#4 Updated by rchan 24 days ago

  • Quarter changed from Q2-2021 to Q4-2021

#5 Updated by wibbit 23 days ago

Morning all, just providing a little more context.

We've been running Pulp3 in production now for 2 months.

index.html is now at 2.6M with 18.5k hyper links, extrapolating out to 1 year, would bring us to 120k links and a 16M index file, however that's conservative, as of this week, we are starting to to ingest additional repositories (rhel8 not just rhel7), and expect to be supporting more plugins beyond rpm.

In our situation we can start deleting old releases (once I've written the tooling), not sure if that's the case for all users.

Please register to edit this issue

Also available in: Atom PDF