[Jenkins-infra] Fwd: [support.osuosl.org #21424] cabbage.jenkins-ci.org (22.214.171.124) hang
R. Tyler Croy
tyler at monkeypox.org
Fri Sep 14 17:40:41 UTC 2012
On Thu, 13 Sep 2012, Kohsuke Kawaguchi wrote:
> To put the context to this, the suggestion from Justin appears to be
> to retire the physical hardware and move the system into a virtual
> machine, which I assume would be better maintained.
> I think this would be great so long as we can get adequate storage
> space and adequate computing power.
> I say "adequate storage" because getting by with just 20GB has been
> a soar point, and we need another 60GB or so right now to serve as
> the fallback mirror, not to mention a room for growth.
> And the same goes for "adequate computing power" because our plan
> was to use this machine to run Confluence or Wiki over time.
> I wouldn't worry too much about I/O bandwidth because even
> JIRA/Confluence would be primarily memory bound and not I/O bound.
> I was going to suggest that we purchase a new disk for this
> computer, so FWIW I'm willing to send some money to OSUOSL if that
> makes it easier for us to get a comparable system in VM.
The conerns I have for using VMs are as follows:
* How many can we have? If we weren't going to use phsyical hardware for some
of these tasks then I would want to use multiple VMs. In effect, 1 for
fallback mirror, 1 for Confluence, 1 for JIRA, etc
* I've not been terribly pleased with the RAM allocations in these VMs, what
is the upper bound of what we can have in a single VM host.
* What are the maximum disk sizes for the VMs that we can request? (assuming
we would have difficulty growing the disk after the machine has been
provisioned, we'd want to get the sizing right at the start).
* How easy would it be to have VM snapshots created regularly, this would
make backups much easier, which I wouldn't mind :)
- R. Tyler Croy
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: Digital signature
More information about the Jenkins-infra