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

Support hierarchy queue #1033

Closed
hzxuzhonghu opened this issue Sep 7, 2020 · 15 comments
Closed

Support hierarchy queue #1033

hzxuzhonghu opened this issue Sep 7, 2020 · 15 comments
Assignees
Labels
area/scheduling kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@hzxuzhonghu
Copy link
Collaborator

hzxuzhonghu commented Sep 7, 2020

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

In order to better support fairshare scheduling, propose to support hierarchy queue.

There are two types of queues: parent queues and leaf queues.

Parent queues enable the management of resources across organizations and sub- organizations. They can contain more parent queues or leaf queues. They do not themselves accept any application submissions directly.

Leaf queues are the queues that live under a parent queue and accept applications. Leaf queues do not have any child queues, and therefore do not have any configuration property that ends with ".queues".

There is a top-level parent root queue that does not belong to any organization, but instead represents the cluster itself.

Using parent and leaf queues, administrators can specify capacity allocations for various organizations and sub-organizations.
@hzxuzhonghu
Copy link
Collaborator Author

/kind feature

@volcano-sh-bot volcano-sh-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 7, 2020
@william-wang
Copy link
Member

It's an important feature. With this feature, volcano can support more scenarios. Do we have a design document right now ?

@hzxuzhonghu
Copy link
Collaborator Author

No, just file it as a task of cncf community bridge

@championshuttler
Copy link

Hi @hzxuzhonghu , I'm interested in working on this project as part of community bridge. I also applied on the website for the same.
Thanks.

@hzxuzhonghu
Copy link
Collaborator Author

@championshuttler Welcome, it is better to send me a resume.

@danijak
Copy link

danijak commented Sep 29, 2020

Hello, @hzxuzhonghu
I have applied for the CNCF community bridge volcano project. I would love to contribute to the open-source volcano community.

@hzxuzhonghu
Copy link
Collaborator Author

@danijak Would want to know which project are you interested in and also expect a resume

@championshuttler
Copy link

@championshuttler Welcome, it is better to send me a resume.

@hzxuzhonghu , sent the resume on the email id you mentioned in your github bio. thanks

@hzxuzhonghu
Copy link
Collaborator Author

@danijak
Copy link

danijak commented Oct 2, 2020

@danijak Would want to know which project are you interested in and also expect a resume

@hzxuzhonghu I have sent my resume and project proposal on mail id(zhhxu2011@163.com) the same day. I want to work on the project "Implement hierarchy queue to better support fair-share". Please let me know if you have any questions, I hope the above is useful.

@stale
Copy link

stale bot commented Mar 3, 2021

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 3, 2021
@stale
Copy link

stale bot commented May 2, 2021

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed May 2, 2021
@k82cn k82cn added this to the v1.4 milestone Jul 19, 2021
@k82cn k82cn mentioned this issue Jul 19, 2021
@Thor-wl Thor-wl reopened this Oct 21, 2021
@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 21, 2021
@Thor-wl Thor-wl added area/scheduling priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed v1.2.0 labels Oct 21, 2021
@Thor-wl Thor-wl modified the milestones: v1.4, v1.5 Oct 21, 2021
@Thor-wl Thor-wl self-assigned this Oct 21, 2021
@william-wang william-wang removed this from the v1.5 milestone Dec 17, 2021
@stale
Copy link

stale bot commented Mar 17, 2022

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 17, 2022
@Thor-wl Thor-wl removed the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Mar 17, 2022
@stale stale bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 17, 2022
@stale
Copy link

stale bot commented Jun 19, 2022

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 Jun 19, 2022
@stale
Copy link

stale bot commented Sep 8, 2022

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/scheduling kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

8 participants