Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Namespace UI #1737

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Namespace UI #1737

wants to merge 6 commits into from
+756 −183

Conversation

CannonLock
Copy link
Contributor

  • Show namespace capabilities
  • Show interaction between namespace and server capabilities

@CannonLock
Add Namespace capabilities view to Director
093cf49 
- Show namespace capabilities
- Show interaction between namespace and server capabilities
@CannonLock CannonLock requested a review from h2zh November 14, 2024 22:19
@CannonLock
Copy link
Contributor Author

Screenshot 2024-11-14 at 4 10 46 PM (2)

@CannonLock
Copy link
Contributor Author

Closes #1724

@CannonLock CannonLock mentioned this pull request Nov 15, 2024
Open
@CannonLock CannonLock linked an issue Nov 15, 2024 that may be closed by this pull request
Web UI at Director displays Origin capabilities but not namespace capabilities #1724
Open
@CannonLock
Add Namespaces to the director UI
78ae774 
- Add namespace card and capabilities table to director UI
- Design InformationSpanHeader
@CannonLock
Copy link
Contributor Author

CannonLock commented Nov 18, 2024 •
edited
Loading

New namespace card with the nested capabilities. Should give easy insight to what caches and origins provide what capabilities for this namespace.

Screenshot 2024-11-18 at 4 12 43 PM (2)

@CannonLock
Add Namespaces to the director UI
0ac23a2 
- Add iconography to the server list to indicate type
@CannonLock
Copy link
Contributor Author

Closes #1210

@h2zh
Copy link
Collaborator

h2zh commented Nov 19, 2024

New namespace card with the nested capabilities. Should give easy insight to what caches and origins provide what capabilities for this namespace.

Screenshot 2024-11-18 at 4 12 43 PM (2)

There are multiple "issuer" showing up here. I think it'd be better to differentiate them here in case causing further confusion. Here are my two cents to avoid semantic overload:

  1. Change "issuer" under "token generation" to another word, like "generator". Also change its occurrences everywhere else
  2. Add tool-tip to "issuer" and "generator", explaining their difference in Pelican project. For example:
  • Token Generator: a server that performs the technical task of creating the token
  • Token Issuer: a server as a trusted authority that vouches for the authenticity of the token

Could you take a quick look and share your thoughts on the necessity of this change @jhiemstrawisc

@CannonLock CannonLock linked an issue Nov 19, 2024 that may be closed by this pull request
Link namespaces in director UI to registry UI's corresponding page(s) #1210
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@h2zh h2zh Awaiting requested review from h2zh

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@CannonLock @h2zh