[volunteergrid2-l] Slashdot post

[Marco Tedaldi]

On 03.04.2012 14:20, Shawn Willden wrote:
> What if we were to just admit everyone to the grid, with the understanding
> that for the first few months (say, six?) members are somewhat
> "probationary" and can have their access revoked?  We've done the
> new-introducer-furl dance a couple of times and it went pretty smoothly, so
> I think removing someone from the grid isn't too difficult.
> 
Yes. but I'm not sure, how mucht this was just "good luck". Because for
example I will be on vacation during the next 2 weeks. I might have
internet access only from time to time and I'm not sure, if checking my
tahoe-mails will be the highest priority than...

> On a related note:  We have one member node right now which isn't meeting
> the storage requirements.

thats my node and it has already bitten me .-(

>  I think we should give that node a deadline to
> get upgraded.  If it hasn't been upgraded by the deadline, then we should
> ask that it be removed from the grid.  How about three months?  That's a
> deadline of July 3rd.
> 
sounds reasonable to me. Since the prices for harddrives seem to be
reasonable once again, this should be no big issue.
I'm about to replace my server hardware anyway. Not because it is old
(ok, that too. at least, it is related). when I built that thing in 2002
it was great hardware. Athlon XP 2500+, 512MB or RAM, 2 100MBit Ethernet
onboard, SATA onboard (which was quite uncommon at that time).

when I installed a 1TB HD 2 years ago, I could solve the hang at
scan-time with an inofficially patched bios.

but for /home over NFS, 100MBit just does not cut it anymore. And
installing a 1GBit PCI card (there is no PCIe, 2002, remmeber?) was a
funny experience since my client hung up on login to the GUI (huge page
issue on the server since PCI, which connects the SATA-Controller as
well as the NIC is the bottleneck)...

Now I got an less ancient mainboard/processor/ram frem a friend. And
this hardware not waits to be installed into the old case (no worries,
the Power supply and chassis fan have been replaced recently).

This would solve the issues almost entrirely. I than have plenty of
SATA-Ports to attach  more disks (with my actual system I would have to
add a PCI-SATA-card which would clog the bandwith of the PCI even more).
And I have 4 or 5 160GB sata disks which would make a nice storage for
my images as a raid 5 and free up the space on my 1TB drive for tahoe.

> Does this approach make sense?  We haven't had to take any action like
> removing nodes up until now (though Jody did decide to remove one of his
> nodes because he didn't feel it could be reliable enough), but I think as
> we grow we'll need to get a little more firm about it.
> 

sounds good to me.
Couldn't we create something like a "furl-distributor"?
A webserver, that serves the furl as a text file. Protected by
individual username/passowrd combinations. https.
So on the client we could create a little cron-job that fetches that
file with wget on a regular basis and replaces it in the config file if
needed and restart tahoe.

That way, changing the furl could be automated and the distribution to
other members can be controled.


best regards

Marco