[Jenkins-infra] Fwd: [support.osuosl.org #21424] cabbage.jenkins-ci.org (220.127.116.11) hang
R. Tyler Croy
tyler at monkeypox.org
Fri Sep 14 19:51:00 UTC 2012
On Fri, 14 Sep 2012, Kohsuke Kawaguchi wrote:
> 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 didn't think you would know the answer, I was more hoping you'd proxy the
questions along to the OSUOSL :)
> 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.
Let's decide something depending on their answers to the questions above,
some things become easier, some things become harder with the move. Given the
capital investment that physical hardware is, it's easier to go physical->VM
than the other way around :)
- R. Tyler Croy
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: Digital signature
More information about the Jenkins-infra