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

Committee scheduler should check runtime versions for eligibility #3611

Closed
kostko opened this issue Jan 11, 2021 · 0 comments · Fixed by #3673
Closed

Committee scheduler should check runtime versions for eligibility #3611

kostko opened this issue Jan 11, 2021 · 0 comments · Fixed by #3673
Assignees
Labels
c:breaking/consensus Category: breaking consensus changes c:consensus/tendermint Category: Tendermint-based consensus c:runtime/compute Category: runtime compute worker

Comments

@kostko
Copy link
Member

kostko commented Jan 11, 2021

Since the runtime descriptors can be updated, the committee scheduler should take into account the version of the runtime self-reported by the compute node when scheduling. Nodes with incompatible version should not be eligible for scheduling. For TEE-based runtimes, the TEE attestation should be checked as well.

This will make it easier to perform runtime upgrades.

@kostko kostko added the c:runtime/compute Category: runtime compute worker label Jan 11, 2021
@kostko kostko changed the title Executor should check runtime version Committee scheduler should check runtime versions for eligibility Jan 18, 2021
@kostko kostko added c:breaking/consensus Category: breaking consensus changes c:consensus/tendermint Category: Tendermint-based consensus labels Jan 18, 2021
@kostko kostko self-assigned this Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:breaking/consensus Category: breaking consensus changes c:consensus/tendermint Category: Tendermint-based consensus c:runtime/compute Category: runtime compute worker
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant