-
Notifications
You must be signed in to change notification settings - Fork 15
Add command to create and start a confidential instance #235
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
Conversation
Failed to retrieve llama text: POST 504: 504 Gateway Time-outThe server didn't respond in time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some general comments on the code.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #235 +/- ##
==========================================
- Coverage 41.39% 39.53% -1.87%
==========================================
Files 18 18
Lines 1551 1667 +116
Branches 257 282 +25
==========================================
+ Hits 642 659 +17
- Misses 890 989 +99
Partials 19 19 ☔ View full report in Codecov by Sentry. |
@olethanh you can squash & merge whenever you want for me |
if an user passed the --hypervisor option, the question was still asked
5153556
to
6c6980c
Compare
aleph instance create
aleph instance confidential-init-session
command to init the confidential sessions (get platform certificate, generate session certificate and upload them)aleph instance confidential-start
command to fetch the measurement from the server and start the VM (get measurements from server, validate them again locally calculated one and send the secret to the server)I tested command separately against staging pyaleph and aleph-vm but the whole flow need to be thoroughly tested.