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.

Sign up for GitHub

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

Jump to bottom

Additional runtime eligibility constraints #3644

Closed
kostko opened this issue Jan 20, 2021 · 0 comments · Fixed by #3689
Closed

Additional runtime eligibility constraints #3644

kostko opened this issue Jan 20, 2021 · 0 comments · Fixed by #3689
Assignees
@kostko
Labels
c:breaking/consensus Category: breaking consensus changes c:consensus/cometbft Category: CometBFT c:registry Category: entity/node/runtime registry service

Comments

@kostko
Copy link
Member

kostko commented Jan 20, 2021 •
edited
Loading

We should add support for runtime eligibility constraints, separately for primary and backup nodes:

  • Validator set membership.
  • Maximum number of nodes per entity per role.

These constraints could be optionally enabled for a runtime and would not prevent registration but would determine what nodes are eligible for scheduling.
@kostko kostko added c:registry Category: entity/node/runtime registry service c:consensus/cometbft Category: CometBFT c:breaking/consensus Category: breaking consensus changes labels Jan 20, 2021
@kostko kostko self-assigned this Feb 8, 2021
@kostko kostko mentioned this issue Feb 10, 2021
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kostko kostko

Labels
c:breaking/consensus Category: breaking consensus changes c:consensus/cometbft Category: CometBFT c:registry Category: entity/node/runtime registry service
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add runtime scheduling constraints oasisprotocol/oasis-core
1 participant
@kostko