-
Notifications
You must be signed in to change notification settings - Fork 115
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
go/runtime/registry: Simplify creation of provisioners #5975
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for oasisprotocol-oasis-core canceled.
|
f241f9d
to
6ab9c9e
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5975 +/- ##
==========================================
- Coverage 65.57% 65.31% -0.26%
==========================================
Files 632 632
Lines 64840 64855 +15
==========================================
- Hits 42517 42363 -154
- Misses 17394 17537 +143
- Partials 4929 4955 +26 ☔ View full report in Codecov by Sentry. |
Yes I believe so: For example, running a ParaTime client node for an SGX-enabled ParaTime like Cipher doesn't require having SGX on the ParaTime client node.. |
fe62fe7
to
40b7b6e
Compare
40b7b6e
to
8cd3f6f
Compare
8cd3f6f
to
4dccda0
Compare
Trying to remove the bundle registry dependency from the
createProvisioner
function, as nodes should generally not have any bundles stored locally upon their initial startup.These changes also decouple the creation of provisioners from TEE selection. Previously, only client nodes could choose the TEE in which a component would run. Now, node operators can specify the TEE for each component, provided the component supports the chosen TEE. If no TEE is specified, it is automatically selected, with TDX and SGX taking precedence over ELF.
How to configure nonSGX client:
How to configure SGX client:
How to mock SGX: