[Jenkins-infra] Fwd: [support.osuosl.org #21424] cabbage.jenkins-ci.org (140.211.15.130) hang

Kohsuke Kawaguchi kkawaguchi at cloudbees.com
Fri Sep 14 19:03:14 UTC 2012


On 09/14/2012 10:40 AM, R. Tyler Croy wrote:
> 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 :)

I don't have answer for any of those. But as you say, the other VMs we 
have in OSUOSL are fairly capacity constrained, so one would expect new 
VMs will be in a similar league.

I think it boils down to which route is the least overhead for us --- if 
we constantly need to talk to OSUOSL about this or that, it would end up 
more work than swapping the disk.

-- 
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins


More information about the Jenkins-infra mailing list