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

Add allocated field in queue status to indicate allocated resources of queue. #2571

Closed
jiangkaihua opened this issue Nov 18, 2022 · 5 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jiangkaihua
Copy link
Contributor

What would you like to be added:

  • a new filed in queue.status called allocated, which indicated already allocated resources in a queue, like:
    "status": {
        "allocated": {
            "cpu": "3",
            "ephemeral-storage": "6442450944",
            "memory": "600Mi"
        },
        "reservation": {},
        "running": 1,
        "state": "Open"
    }

Why is this needed:

  • In our scenario, volcano queue was involved in to split manage cluster resources. We configure Capability field to restrict the upper limit of each queue, a hard restriction according to which we cloud calculate cost allocation. But in some cases, we did not know whether should we apply workload to one queue, because we were unaware of allocated resources in the queue and idle resources left within Capability, causing jobs pending and autoScaler enlarge the cluster meaninglessly.

  • So we want to add a new field Allocated in queue.Status, so that we can watch allocated resources in a queue, and apply jobs according used resources.

@stale
Copy link

stale bot commented Mar 18, 2023

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 18, 2023
@wangyang0616
Copy link
Member

The PR corresponding to the current issue has been incorporated into the main line. I understand that this issue can be closed, right? @jiangkaihua

@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 24, 2023
@stale
Copy link

stale bot commented Aug 10, 2023

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 10, 2023
@Monokaix
Copy link
Member

/close

@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 29, 2024
@volcano-sh-bot
Copy link
Contributor

@Monokaix: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants