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

Collect persistent volumes from cluster #177

Closed
5 tasks done
jandegen opened this issue Jun 21, 2023 · 2 comments · Fixed by #195
Closed
5 tasks done

Collect persistent volumes from cluster #177

jandegen opened this issue Jun 21, 2023 · 2 comments · Fixed by #195
Assignees
Labels
documented feature A new feature or change for the application REQ.19 The user can gather information about volumes. All volumes can be viewed in a list...
Milestone

Comments

@jandegen
Copy link
Contributor

jandegen commented Jun 21, 2023

User story

  1. As a developer
  2. I want / need to collect and persist information about volumes
  3. So that those information can be displayed in the frontend

Acceptance criteria

  • Claimed persistent volumes are collected
  • Unused/not claimed persistent volumes are collected
  • Claimed persistent volumes are linked to the parent resources
  • All information collected is persisted in the database
  • Claimed volumes have a name and path based on volume mounts of the parent

Linked Issues

  • Blocked by:
  • Related to:
  • Implements

Additional information

  • Concentrate on Kubernetes persistent volumes, no external volume resources

Definition of done (DoD)

DoD general criteria

  • Feature has been fully implemented
  • All acceptance criteria were met
  • Product owner approved features
  • All tests are passing
  • Pull request to "develop" branch is merged & closed
  • Bill of materials is updated with new dependencies
@jandegen jandegen added the feature A new feature or change for the application label Jun 21, 2023
@jandegen jandegen moved this to Sprint Backlog in amos2023ss04-feature-board Jun 28, 2023
@jandegen jandegen moved this from Sprint Backlog to Product Backlog in amos2023ss04-feature-board Jun 28, 2023
@jandegen jandegen changed the title Collect volumes Collect persistent volumes from cluster Jun 28, 2023
@jandegen jandegen added the REQ.19 The user can gather information about volumes. All volumes can be viewed in a list... label Jun 28, 2023
@PhlppKrmr PhlppKrmr added this to the Sprint 11 milestone Jun 28, 2023
@PhlppKrmr PhlppKrmr moved this from Product Backlog to Sprint Backlog in amos2023ss04-feature-board Jun 28, 2023
@lifesbest23 lifesbest23 self-assigned this Jun 28, 2023
@lifesbest23 lifesbest23 moved this from Sprint Backlog to In Progress in amos2023ss04-feature-board Jul 2, 2023
@lifesbest23
Copy link
Contributor

Generating relevant test data for the new cases are still to be done.

lifesbest23 added a commit that referenced this issue Jul 5, 2023
…ersistent-volumes-from-cluster' into feat/#177-collect-persistent-volumes-from-cluster
@jandegen jandegen moved this from In Progress to Product Backlog in amos2023ss04-feature-board Jul 5, 2023
@jandegen
Copy link
Contributor Author

jandegen commented Jul 5, 2023

Not merged yet

@PhlppKrmr PhlppKrmr moved this from Product Backlog to Sprint Backlog in amos2023ss04-feature-board Jul 5, 2023
@lifesbest23 lifesbest23 moved this from Sprint Backlog to In Progress in amos2023ss04-feature-board Jul 5, 2023
lifesbest23 added a commit that referenced this issue Jul 7, 2023
…lumes-from-cluster

Feat/#177 collect persistent volumes from cluster
@lifesbest23 lifesbest23 moved this from In Progress to Awaiting Review in amos2023ss04-feature-board Jul 7, 2023
@jandegen jandegen moved this from Awaiting Review to Feature Archive in amos2023ss04-feature-board Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documented feature A new feature or change for the application REQ.19 The user can gather information about volumes. All volumes can be viewed in a list...
Projects
Status: Feature Archive
Development

Successfully merging a pull request may close this issue.

3 participants