Having just done something similar for something else, you should really look at doing CI in AWS lambda. It is remarkably cheap and (more importantly for my case) requires nearly zero devops once set up. If you suddenly have 10x the CI runs, they can all run in parallel for the same cost. No queues.
On Fri, Aug 11, 2017 at 10:14 AM, Adam Hunt <voxa...@gmail.com> wrote: > What sort of hardware would RIOT need for CI? Would a machine with, > for example, a pair of E5-2670 (eight cores @ 2.60 GHz), Xeons between > 64 and 128 GB of DDR3 ECC RAM, an SSD or two, and maybe some spinning > storage suffice or are we talking about something like a highly > available cluster consisting of half-dozen or more HP ProLiant DL380 > Gen10 machines each with a pair Xeon 8100s (28 cores @ 3.60 GHz), a > terabyte of DDR4 RAM, and a pile of blazing fast NVMe drives? > > I'm just thinking that if a machine or two with specs closer to the > first example would suffice than I imagine the RIOT community might be > able to find a way to make it happen. > > A word of warning… While I'm absolutely serious about trying to help > out in this area (and other) please know I'm currently trying get the > ball rolling and determine what type of resources the project could > most use; it'll take a bit of time to turn these early thoughts into > something real. Personally, I may not have piles of cash laying around > but I do have something else of value, time. > > Adam > > > On Fri, Aug 11, 2017 at 7:16 AM, Koen Zandberg <k...@bergzand.net> wrote: > > Hello, > > > > > > On 08/11/2017 03:49 PM, Stefan Schmidt wrote: > >> Hello. > >> > >> On 08/11/2017 02:03 PM, Oleg Hahm wrote: > >>> Hey Adam! > >>> > >>> Thanks for the pointer. That's definitely something we should consider. > >>> > >>> Cheers, > >>> Oleg > >>> > >>> On Fri, Aug 11, 2017 at 04:52:05AM -0700, Adam Hunt wrote: > >>>> I was going to suggest that you might talk to the Oregon State > >>>> University Open Source Lab (http://osuosl.org). OSUOSL offers free > >>>> hosting, email, VMs, colocation, FTP, backup, etc. (both managed and > >>>> unmanaged) to open source projects. I can't speak to what type of > >>>> computing power they offer but I know they've been working to stand up > >>>> an OpenStack cluster they may be able to help out with CI or in other > >>>> ways. > >> > >> They also offer to host a server of your own. We do that for the > >> Enlightenment project for several years now. Their connectivity and > >> general admin service has worked very well for us. > >> > >> We have a beefy server there hosting our own tons of git repos, web > >> services, downloads, CI, etc. I don't think there is any bandwidth > >> limitation or such. All in all a really nice service from them to the > >> open source communities. > >> > >> If it is something interesting for RIOT I have no idea but if you are > >> looking for something in that regard it is surely worth talking to them. > >> > >> regards > >> Stefan Schmidt > > > > To offer an alternative, I can offer the services of Studenten Net > > Twente[1]. Studenten Net Twente is a student associations of the > > University of Twente aimed at providing IT services. We have a history > > of supporting open source projects by offering FTP space and/or > > colocation services for free. > > > > As we use RIOT-os for an internal project, we'd love to return something > > to the project. If a host for CI or other services is needed, I can see > > if I can get a virtual machine or some real hardware available for > > RIOT-os infrastructure. > > > > Regards, > > Koen Zandberg > > > > 1. http://www.snt.utwente.nl/en/index.php > > _______________________________________________ > > devel mailing list > > devel@riot-os.org > > https://lists.riot-os.org/mailman/listinfo/devel > _______________________________________________ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
