Machine independent manifest #981
Unanswered
brad-intel
asked this question in
Q&A
Replies: 1 comment 14 replies
-
I don't think there is much more that can be done -- what you're already doing (finalize the manifest on the machine right before execution) seems to be reasonable for CI/CD purposes. Generally, you list three kinds of cases:
If I misunderstood some points, or you have some proposal, feel free to reply. |
Beta Was this translation helpful? Give feedback.
14 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When creating a manifest for an application, the manifest details such as enclave size, number of threads and/or CPU instruction set cannot be determined at build time (especially when using CI/CD). That forces us to finalise the manifest before execution and sign the binaries there as well. For AI workloads that takes quite a bit of time.
What would be the best approach to have the manifest machine independent (or capable of dynamically adjusting)?
Beta Was this translation helpful? Give feedback.
All reactions