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

tee: Add instructions for configuring DCAP on IBM Cloud #1047

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

anzoman
Copy link
Contributor

@anzoman anzoman commented Dec 10, 2024

After testing the SGX support on IBM Cloud we are adding the instructions for configuring DCAP on IBM Cloud.

@anzoman anzoman requested a review from ptrus December 10, 2024 07:17
Copy link

netlify bot commented Dec 10, 2024

Deploy Preview for oasisprotocol-docs ready!

Name Link
🔨 Latest commit 4ce4ae9
🔍 Latest deploy log https://app.netlify.com/sites/oasisprotocol-docs/deploys/6757eb072a275900084315c8
😎 Deploy Preview https://deploy-preview-1047--oasisprotocol-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@anzoman anzoman self-assigned this Dec 10, 2024
@@ -161,12 +161,16 @@ Some cloud providers require you to use their PCCS.
- Alibaba Cloud: See the [Alibaba Cloud documentation] for details on configuring the quote provider. The
documentation shows the required `sgx_default_qcnl.conf` changes.

- IBM Cloud: See the [IBM Cloud documentation] for details on configuring the quote provider. The
Copy link
Member

Choose a reason for hiding this comment

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

This is just for the VM instances, right?

I assume the bare metal instances don't need these changes to the config.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, just the VMs, for the bare-metal it works out of the box.

@gw0
Copy link
Contributor

gw0 commented Dec 10, 2024

After testing the SGX support on IBM Cloud

Didn't we confirm that currently SGX DCAP attestation on IBM VMs does not work? It supposedly works only on IBM bare-metal instances, but did we confirm this? If yes, I would expect that this PR adds a note to the list of cloud providers that only bare-metal instances work.

@anzoman
Copy link
Contributor Author

anzoman commented Dec 10, 2024

Didn't we confirm that currently SGX DCAP attestation on IBM VMs does not work?

Not entirely, the IBM Cloud team confirmed it works on their side, and stated the two tools (sgx-detect and attestation tool) are unexpectedly throwing the I/O error. We will probably need to run an actual node to confirm whether it works for real.

Also, this part of the docs never explicitly states that SGX works with IBM Cloud VMs, but just provides links to configure PCCS according to the docs. If we ever want to state that it works only for bare-metal, we should probably do it inside some support metrics (e.g., in https://docs.oasis.io/node/run-your-node/prerequisites/cloud-providers#known-providers where we already have a table with known providers).

@gw0
Copy link
Contributor

gw0 commented Dec 11, 2024

We will probably need to run an actual node to confirm whether it works for real.

As far as I know we developed the attestation-tool exactly for this purpose. If the attestation-tool does not work, something is misconfigured and the node should also not work.

this part of the docs never explicitly states that SGX works with IBM Cloud VMs

True, but adding these instructions for IBM Cloud and not mentioning where exactly is this supposed to work, you are implicitly suggesting it works on all IBM Cloud instances. Lets wait until we actually confirmed it works.

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.

3 participants