Bug 1408363
Summary: | Need a VM for signing packages | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Nigel Babu <nigelb> |
Component: | project-infrastructure | Assignee: | Nigel Babu <nigelb> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | bugs, gluster-infra, mscherer, nigelb |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-31 02:10:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nigel Babu
2016-12-23 05:24:34 UTC
So, 1 CPU, 1G of ram, 10G of disk ? Sounds good. Does it GPG signing need anything more in terms of CPU? Signing consumes very little CPU. 1 CPU, 1G ram is more than enough. You may want more disk to keep an archive of the signed packages. Might come in handy if you ever want to compare what's on d.g.o. We will not store anything on that VM, no ? (since it will not be accessible for the internet). And we can surely get a log of what was signed to not be forced to keep all data. So I installed the VM, and it can be accessed by ansible for later configuration. So the VM was created, anything more needed on that ? Nope. Closing. I'll open a new one if we need anything more on it. |