Tahoe-LAFS and Ports

Marko Niinimaki posted a question regarding what TCP ports Tahoe-LAFS uses. From docs/configuration.rst:

"tub.port = (integer, optional)

This controls which port the node uses to accept Foolscap connections from other nodes. If not provided, the node will ask the kernel for any available port. The port will be written to a separate file (named client.port or introducer.port), so that subsequent runs will re-use the same port."

Hopefully this answers Marko's question. I will be adding the question and its answer to the FAQ.

Volunteer Grid 2 Hits a Milestone

Shawn Willden announced VG2 hitting a major milestone.

"VG2 hit a milestone sometime early this morning or late last night: 20 nodes! 20 highly-available (95+% uptime), high capacity (500 GB - 1 TB) nodes, distributed all over the world. Well, we'll see if the newest nodes meet the availability standard, but their operators have committed to it.

According to the stats gatherer (which appears to have data on 16 of the nodes -- we'll get the others in there), we currently have just over 9 TB available storage space, right around 6 TB used, and we're uploading 140 GB per day.

Next goal: 32 nodes highly-reliable nodes." [0]

Congratulations to all the members of VG2 and good luck hitting your next milestone.

Welcome Page

Ted Rolle, Jr requested a couple of fixes to the welcome page. The first request was to order the nodes by nickname rather than by peer ID. This is ticket #1709. The second requested was to change 'To' to 'to'. This is ticket #1708 and has already been fixed.

New Web UI Concept

Tony Arcieri began work on a new Web UI using the Twitter Bootstrap CSS Framework. His work is built with a responsive layout which will allow to it degrade to the appropriate screen size. This would allow the web UI to fit comfortably in the screen of your smart phone. The response to the work has been favorable and a ticket exists at #1713 if you would like to review it or learn more.

AppArmor Profile

Mike Kazantsev created an AppArmor profile for Tahoe-LAFS. AppArmor is

"an effective and easy-to-use Linux application security system. AppArmor proactively protects the operating system and applications from external or internal threats, even zero-day attacks, by enforcing good behavior and preventing even unknown application flaws from being exploited. AppArmor security policies completely define what system resources individual applications can access, and with what privileges. A number of default policies are included with AppArmor, and using a combination of advanced static analysis and learning-based tools, AppArmor policies for even very complex applications can be deployed successfully in a matter of hours." [1]

Further information can be found on the Tahoe-LAFS AppArmor page. I would really like to see this profile incorporated into Debian and Ubuntu packages of Tahoe-LAFS.