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

[YUNIKORN-2579] Remove maxAllocations from AllocationAsk #137

Closed
wants to merge 1 commit into from

Conversation

craigcondit
Copy link
Contributor

What is this PR for?

Remove maxAllocations from the AllocationAsk object so that we can enforce 1:1 mappings between asks and allocations.

What type of PR is it?

  • - Bug Fix
  • - Improvement
  • - Feature
  • - Documentation
  • - Hot Fix
  • - Refactoring

Todos

  • - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/YUNIKORN-2579

How should this be tested?

Screenshots (if appropriate)

Questions:

  • - The licenses files need update.
  • - There is breaking changes for older versions.
  • - It needs documentation.

@craigcondit craigcondit self-assigned this Apr 23, 2024
Copy link
Contributor

@chia7712 chia7712 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@craigcondit This idea is good to simplify the code base, and I notice that ExecutionTimeoutMilliSeconds seems to be unused too. Should we remove it? BTW, removing it can't simplify code base since there is no facility for it.

si.proto Show resolved Hide resolved
@craigcondit
Copy link
Contributor Author

I notice that ExecutionTimeoutMilliSeconds seems to be unused too. Should we remove it? BTW, removing it can't simplify code base since there is no facility for it.

That would probably be best left to another PR. This one is part of an epic to merge ask and allocation. When that is done, there will likely be further optimizations / simplifications of the interface.

@craigcondit craigcondit deleted the YUNIKORN-2579 branch April 23, 2024 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants