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.

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

UI support for Host Volumes #6362

Closed
DingoEatingFuzz opened this issue Sep 21, 2019 · 1 comment · Fixed by #7151
Closed

UI support for Host Volumes #6362

DingoEatingFuzz opened this issue Sep 21, 2019 · 1 comment · Fixed by #7151
Assignees
Labels

Comments

@DingoEatingFuzz
Copy link
Contributor

Background

Host volumes are client-local volumes that can optionally mounted by Nomad as specified in the client config. Jobs can then be specified to require host volumes, forcing the scheduler to place the allocations for said job on clients with matching host volumes.

See how this looks in the CLI here: #6011
And how it looks in client and job specs here: #5923

UI Requirements

  1. Show host volumes for a client on the Client Detail page, including the same information that is shown in the CLI.
  2. Explore adding host volumes to faceted search on the Client List page.
  3. Show host volume requirements on the Task Group page.
  4. Show host volume usage on the Allocation and Task Detail pages.

Implementation notes

We know that Container Storage Interface support is coming, so we should be mindful of this when designing changes to especially the task group/allocation/task pages.

Host volumes is distinct from CSI, but they both relate to storage so there is bound to be some user flow overlap.

@DingoEatingFuzz DingoEatingFuzz added this to the 0.10.1 milestone Sep 21, 2019
@DingoEatingFuzz DingoEatingFuzz self-assigned this Sep 21, 2019
@schmichael schmichael modified the milestones: 0.10.1, 0.10.2 Nov 5, 2019
@DingoEatingFuzz DingoEatingFuzz modified the milestones: 0.10.2, 0.10.3 Nov 20, 2019
@schmichael schmichael removed this from the 0.10.4 milestone Feb 5, 2020
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants