- Add Q3 report entry on the Intelligent Download Service Manager GSoC project

Submitted by:	Ambarisha Bhatlapenumarthi <b.ambarisha@gmail.com>
This commit is contained in:
Gabor Pali 2013-09-23 17:54:16 +00:00
parent 66898d8a22
commit f0189d805a
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=42691

View file

@ -19,7 +19,7 @@
<!-- XXX: keep updating the number of entries -->
<p>Thanks to all the reporters for the excellent work! This report
contains 8 entries and we hope you enjoy reading it.</p>
contains 9 entries and we hope you enjoy reading it.</p>
<!-- XXX: set date for the next set of submissions -->
<p>The deadline for submissions covering between October and
@ -56,6 +56,12 @@
<description>Documentation</description>
</category>
<category>
<name>soc</name>
<description>Google Summer of Code</description>
</category>
<project cat='kern'>
<title>AES-NI Improvements for GELI</title>
@ -401,4 +407,61 @@
<task>Test 10.0-CURRENT and report problems.</task>
</help>
</project>
<project cat='soc'>
<title>Download Manager Service for the Ports Collection</title>
<contact>
<person>
<name>
<given>Ambarisha</given>
<common>Bhatlapenumarthi</common>
</name>
<email>ambarisha@freebsd.org</email>
</person>
<person>
<name>
<given>Xin</given>
<common>Li</common>
</name>
<email>delphij@freebsd.org</email>
</person>
</contact>
<links>
<url href="https://wiki.freebsd.org/SummerOfCode2013/IntellegentDownloadManager">Project wiki page</url>
<url href="https://wiki.freebsd.org/IdeasPage/IDMS">More information on DMS</url>
</links>
<body>
<p>This is a Google Summer of Code 2013 project that aims to
replace the <tt>fetch(1)</tt>-based method for getting
distribution files, such as source tarballs, for the third-party
applications (ports) with an intelligent Download Manager
Service (see links for more information).</p>
<p>All the modules highlighted in the project wiki have been
completed (see links). Specifically:</p>
<ul>
<li>A service which receives and serves download requests. It
samples download speeds from different mirrors and uses this
information to pick the best mirror on the next request. It
can migrate jobs between mirrors if it realizes that a
complete download from a different mirror would be faster than
proceeding with the mirror it is currently using.</li>
<li>A status dump feature has also been added to the client
(<tt>dmget</tt>) which dumps the information about active
downloads, speeds from mirrors, etc.</li>
</ul>
</body>
<help>
<task>The implementation (especially job migration and dumping
status) has not been tested thoroughly. Test the code, write more
unit and regression tests.</task>
</help>
</project>
</report>