[Jenkins-infra] A random thought for reducing ci.j.io cost

Oleg Nenashev o.v.nenashev at gmail.com
Fri Feb 7 22:00:22 UTC 2020


I am +1 for such setup for non-mission-critical payload, e.g. pull request
builds. We can always auto-reschedule them if the instance goes down. I am
pretty sure we can have a high continuous load on such first-priority
agents, and that it will reduce the net cost. Still needs testing and a
sign-off from the security team.

There are also some other ideas for cost cutting we discussed in the
mailing lists and Jira tickets, it would be great to do the joint
brainstorming at the next Infra team meetings.



On Fri, Feb 7, 2020 at 4:47 PM Marky Jackson <marky.r.jackson at gmail.com>
wrote:

> Huge +1 from me
>
> > On Feb 7, 2020, at 1:22 PM, R. Tyler Croy <rtyler at brokenco.de> wrote:
> >
> > We've been discussing some cost-mitigation measures with the Jenkins
> board
> > recently, and one of the big areas of cost for our infra is
> ci.jenkins.io.
> >
> > An idea that struck me yesterday was that we could just spend a few
> thousand
> > dollars on a couple intel NUCs, keep those as "always on" agents, and
> then
> > use AWS/Azure/GCP for burst capacity on top of that.
> >
> > In my home lab, I already have a cabinet with a few machines, cheap solar
> > power, and a gigabit connection to the public internet. It would be
> relatively
> > little effort for me to provision a few NUCs on their own network
> segment here.
> >
> > The downsides that come to mind would be: physical infrastructure, a
> dependency
> > on Tyler's Great Little Datacenter, some personal cost to me (another
> network
> > switch and perhaps some electrical work to ensure the circuit will
> support even more
> > computers), and each machine would not have its own public IPv4 (though
> they
> > would all have public IPv6s).
> >
> > The upside is that we've have basically some fixed cost executors, and
> even if
> > they fail, service availability would not completely disappear since we
> can
> > still burst into the cloud.
> >
> >
> > In terms of space, I believe I could fit up to 8 more NUCs in the
> cabinet. The
> > one I have right now has 8 cores and 32GB of RAM, which I think can
> easily
> > handle a couple core builds ;)
> >
> >
> >
> >
> > Let me know what you all think!
> >
> > --
> > GitHub:  https://github.com/rtyler
> >
> > GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
> > _______________________________________________
> > Jenkins-infra mailing list
> > Jenkins-infra at lists.jenkins-ci.org
> > http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20200207/decd2ef3/attachment.html>


More information about the Jenkins-infra mailing list