Open fkr opened 1 year ago
1st step:
2nd step:
The unit tests are running successfully now, however launching sgx-enabled workloads is not possible, neither via horizon nor via api.
I will get in touch with @mleberec in order to establish contacts between OSISM and the intel engineers.
@fkr - thanks. @berendt - give me a ping to follow up.
Prepared patch sets & first documentation is available in the https://github.com/osism/secured-cloud-management-stack repository.
167e3380c946ffb07622a8c8079fa1b22b8c5543
CUSTOM_SGX_EPC_MB
inventory class every few minutes. For development purposes we solved this by being fast with creating the class and spawning the instances. This needs a proper fix in the placement API long term.security_driver
in libvirt for the time being.We should probably see about getting in touch with nova people before vPTG so that we can discuss upstreaming the effort during the d-cycle.
Legal requirements have been solved, the Intel Repository now carries a valid LICENSE file.
Nova patch set was rebased on an upstream commit from 2024
New base commit is 6531ed6310c4c11ee807e10d1a0fa91658c3afea
3209f6551652cff7bef0b9d9719ab940dd05a0f8
thanks @gndrmnn for keeping this updated.
The patchset from Intel (https://github.com/intel/secured-cloud-management-stack/) for bringing SGX needs to forward-porting and retesting. This story is about making sure stories that cover:
of the patchset exist. The stories should be small enough so that each can be finished in one sprint.
Definition of Done: