Bug 977165
| Summary: | [Docs] [Tracker] Trusted Compute Pools feature based on OpenAttestation | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Zac Dover <zdover> | |
| Component: | Documentation | Assignee: | Zac Dover <zdover> | |
| Status: | CLOSED DUPLICATE | QA Contact: | ecs-bugs | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.3.0 | CC: | aburden, acathrow, dfediuck, gang.wei, iheim, lpeer, thildred, zdover | |
| Target Milestone: | --- | Keywords: | FutureFeature | |
| Target Release: | 3.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | sla | |||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 929057 | |||
| : | 978623 978629 978630 978631 978632 (view as bug list) | Environment: | ||
| Last Closed: | 2014-04-04 17:21:10 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 929057 | |||
| Bug Blocks: | 978623, 978629, 978630, 978631, 978632 | |||
|
Description
Zac Dover
2013-06-24 00:51:39 UTC
Itamar Heim 2013-06-24 04:30:43 EDT This will work for RHEL only, not RHEV-H Customer will need to deploy open attestation service on their own, as well as deploy open attestation agent on the RHEL hosts Hey Gang, I'm trying to figure out what is required to document this feature. Here are some questions I have. - from RHEVM side, is there anything to do to make a host "trusted"? - does the RHEVM just ask all hosts if they are "trusted", and then decide based on their response where to run VM? Thank you for your help! From email conversations about this bug with Doron: "The integration with OAT requires using the config utility in order to update the relevant information, the same way we do with the manage-domains. So the user should be using engine-config instead of manually updating the DB. What we need to document is the relevant ~3-4 keys and what they mean, as well as the meaning of the checkbox we have in the UI. What we can do, is possibly add a tooltip with a question mark in the UI which will indicate that this requires OAT setup." Here are the values that have to be added to the table of rhevm-config values: SecureConnectionWithOATServers default value: true PollUri default value: "AttestationService/resources/PollHosts" Comment: this is determined by the OAT installation. AttestationTruststore default value: TrustStore.jks. AttestationPort default value: 8443 AttestationServer default value: "". Adding missing entries; AttestationTruststorePass: "The password used to access trust store" (Value Type: String) default value: "password". AttestationFirstStageSize: "Attestation size for first stage" (Value Type: Integer) default value: 10. Comment: used for quick initialization. Do not change unless you know why. I've done the Administration Guide part of this. The other two clones belong to zdover, so I'll re-assign the tracker to him. *** This bug has been marked as a duplicate of bug 978631 *** clear the needinfo flag. |