Ok,<br><br>i would do a "packaging farm" because i know some people who packages some big app, and the building time is about 20 hours :/<br>So, do you think there really is no solution for parrallel works over Internet ?
<br>(Maybe just with some computer with a big connection over Internet ...)<br><br>Thx<br><br><div><span class="gmail_quote">2006/9/30, Eric W. Biederman <<a href="mailto:firstname.lastname@example.org">email@example.com</a>
>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">"Maxence Dunnewind" <<a href="mailto:firstname.lastname@example.org">email@example.com
</a>> writes:<br><br>> HI,<br>> i'm working on a way for split Debian/Ubuntu packaging process throught<br>> internet.<br>> I'm looking for the best solution does beowulf can do it ?<br><br>Package building is essentially an embarrassingly parallel problem.
<br>You communicate at startup the package source that needs to be built.<br>You communicate when you are done the binary package that was built.<br><br>There doesn't need to be any intermediate communication that is<br>frequently seen on beowulf clusters. Plus until you get to grid
<br>computing beowulf cluster nodes don't communicate over the internet<br>(the latency and bandwith both hinder the application). So your best<br>solution is likely something closer to the seti@home model.<br><br>However I have a problem seeing multiple random machines distributed
<br>over the internet providing you much value either as the big problem<br>with a distribution like debian is the plethora of architecture it<br>supports. So the seti@home model doesn't quite work for you either.<br><br>
The simplest method is probably to have each maintainer build their<br>own binary packages, that is the least possible complication and<br>likely the best feedback for fixing problems.<br><br>For a compile farm beyond that you probably still want something like
<br>work requests submitted by the package maintainers, being picked up by<br>volunteer machines that can perform them. With some signatures thrown<br>in some things don't get wildly out of wack.<br><br>Trust would seem to be your big problem in this instance.
<br><br>Eric<br><br></blockquote></div><br><br clear="all"><br>-- <br>Maxence DUNNEWIND<br><a href="http://www.sos-sts.info">http://www.sos-sts.info</a> <=== Entraide étudiante<br><a href="http://www.ubuntu-fr.org">http://www.ubuntu-fr.org
</a> <=== La meilleure distribution Linux :)<br>Contact : <br><a href="mailto:firstname.lastname@example.org">email@example.com</a><br><a href="mailto:firstname.lastname@example.org">email@example.com</a>