infrastructure proposal for TI donation

Koen Kooi koen at dominion.thruhere.net
Mon Nov 1 17:46:46 CET 2010


Op 31 okt 2010, om 14:57 heeft Koen Kooi het volgende geschreven:

> (this is NOT a voting proposal yet)
> 
> Hi,
> 
> At OEDEM we briefly discussed how to use the money that TI donated to the eV that was meant for angstrom infrastructure, but nothing solid came out of that except for a long VM vs real debate.
> 
> When I did the original budget proposal I based it on renting a single server for 24 months at strato to accompany the linuxtogo server.  For various reasons that came through as a "no strings attached" donation and there was some pushback at OEDEM from making it a purely angstrom thing, so here are my 2 proposals:
> 
> Proposal A:
> 1) rent a X3 rootserver at Hetzner for 24 months: 149 + 24*39 -> €1080
> 2) rent a EQ4 rootserver at Hetzner for 24 monhts: 149 + 24*49 -> €1325
> 
> The X3 would be used for "static"[1] content like the angstrom feeds, narcissus, OE git mirror, source mirror, etc. 
> The EQ4 would be used as an autobuilder for testing-next, release tags, invasive feature branches, etc.
> 
> Proposal B:
>  1) rent a Hetzner EQ4 rootserver at Hetzner for 24 monhts: 149 + 24*49 -> €1325
>  2) arrange an additional VM a OSOSL, donate €600 for hardware (e.g. disks, ram, cpu)
>  3) use the rest to pay for EC2 computing time (€500)
> 
> The EQ4 would be used as an autobuilder for testing-next, release tags, invasive feature branches, etc.
> The VM would be used for "static"[1] content like the angstrom feeds, narcissus, OE git mirror, source mirror, etc. 
> The EC2 budget can be used for people like Khem who might need to do a "quick check" on a large build and their own machines are too slow. 

Slight change to proposal B: the git mirror would live on the EQ4 so it can be in europe. Having a mirror on the same server as the original isn't going to accomplish much.

regards,

Koen










> 
> The general idea behind both proposals is to have a relatively slow system with decent disks (400GB or more) serve "static"[1] content and host narcissus and have a beefier version do continious builds on OE metadata to feed that to tinderbox.
> 
> I prefer proposal B because it splits the 2 servers across continents to spread the risks and allows for some headroom in the budget to help to specific developers if needed. Technically speaking we have even more headroom because of the Eukrea donations, but I don't know the conditions of that and we need to have money left for travel reimbursements.
> I left out things like root access, domains, etc on purpose to make this discussion more focussed.
> 
> I added Nils to CC: because I would like to have the Hetzner stuff managed by KC since they are doing a good job with the current linuxtogo server and I trust them. Nils, please speak up if you think that's a good idea or not.
> 
> I encourage people to come up with better proposals or tweaks to the above ones, but please keep the general idea in mind. The proposal to drink cocktails on an exotic island with all e.V. members was sadly shot down ;)
> 
> regards,
> 
> Koen
> 
> [1] No android stuff that sucks up all bandwidth like the past weeks at linuxtogo
> _______________________________________________
> Openembedded-members mailing list
> Openembedded-members at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members
> 




More information about the Openembedded-members mailing list