[Jenkins-infra] Rackspace open source sponsorship has lapsed

Olblak me at olblak.com
Tue Jan 28 14:10:03 UTC 2020


Hi Kohsuke, 
Thanks for sharing this information, this is definitely bad news but more timing reasons than really in term of complexity.
Basically that machines is okra only used for archives.jenkins.io <http://archives.jenkins-ci.org/>, it's just an apache service distributing artifacts as you can see here <https://github.com/jenkins-infra/jenkins-infra/blob/c4b731162b51a55b6c9a8de2f15d29b63953e8da/dist/role/manifests/okra.pp#L5>, the other services were already moved to azure

1) So we need to deploy a new virtual machine on Azure (jenkins-infra/azure <https://github.com/jenkins-infra/azure/>)
2) Transfer every artifacts from okra to the new azure machine
3) Add the new azure machine to puppet (jenkins-infra/jenkins-infra <https://github.com/jenkins-infra/jenkins-infra>)
4) Update the dns to use the new IP

> How big of an effort would that be
It's probably not more than a day of working

---
gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---


On Mon, Jan 27, 2020, at 11:51 PM, Kohsuke Kawaguchi wrote:
> Hi,
> 
> I just got an email from Rackspace that their OSS sponsorship program has ended at the end of 2019. I wish they could have told us before the program actually ended, instead of telling me after the fact.
> 
> Still, Rackspace gave us a generous cloud credit starting back in, what, like 2010 ish, and ever since then. So I'm very grateful to what they've given to the project.
> 
> In the past few years, we haven't really used this much, but we still apparently have some small stuff running on it.
> 
> I looked at the bill of 2019/10-2019/12, and without the credit, there would have been $400-$500ish charge per month. About $50 of them are block storage, $90 for compute, and the rest is bandwidth. In Jan, we'll likely incur cost in this range, which I will reimburse from SPI, as it's coming out of my credit card.
> 
> What exactly do we run on Rackspace today? Would it make sense to consolidate this into one of the clouds we already use to have one less thing to worry about? How big of an effort would that be? Should that wait until we sort out how we pay for our infra going forward?
> 
> 
> -- 
> Kohsuke Kawaguchi
> _______________________________________________
> 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/20200128/69b72d7b/attachment.html>


More information about the Jenkins-infra mailing list