Updates identified below.<br><br><div class="gmail_quote">On Mon, Jan 14, 2013 at 9:46 PM, knuttila @<a href="http://dslextreme.com">dslextreme.com</a> <span dir="ltr"><<a href="mailto:knuttila@dslextreme.com" target="_blank">knuttila@dslextreme.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<div><br></div><div>First a short self introduction and then on the main event. My name is Kim Knuttila and</div>
<div>I've been around open source work for a while now. There. That was quick. ;-)</div><div><br></div>
<div>The company I work for is interested in possibly using Tahoe as part of a "cloudy" sort of </div><div>deployment. And while we don't expect to be limited to one target platform, one of our early </div>
<div>
interests is using deployed 64 bit Win7 boxen. To that end, we are trying to build local </div><div>storage nodes on them, and running into some... hmm... "challenges". </div><div><br></div><div>(no doubt some of our challenges are of our own creation -- we are not all up to speed</div>
<div>on "all things tahoe" -- we're more than happy to be "educated" further ;-)</div><div><br></div><div>The machine is a decent dell box, with a fresh clean install of 64bit win7. I installed</div>
<div>a couple of other useful things (firefox/chrome, sshd, ssh, turn off the firewall), and </div><div>then we begin.</div><div><br></div><div>Instructions were followed from here:</div><div><br></div><div> <a href="https://tahoe-lafs.org/trac/tahoe-lafs/wiki/AdvancedInstall" target="_blank">https://tahoe-lafs.org/trac/tahoe-lafs/wiki/AdvancedInstall</a> </div>
<div><br></div><div>The first few steps went fine. (well, step 3's example code doesn't work with the current</div><div>release -- there's an "allmydata-tahoe-1.9.2" directory in the middle -- but no biggie)</div>
<div><br></div><div>Step 4 blunts its nose into the wall. The root cause is needing a 64bit twisted -- but the </div><div>symptom is "Unable to find vcvarsall.bat". "google is your friend" on this sort of thing.</div>
<div>Some rummaging, and you find there's a couple of ways to make the message go </div><div>away.</div><div><br></div><div>Current solution -- basically, go to Twisted Matrix <u>(</u><a href="http://twistedmatrix.com/trac/" target="_blank">http://twistedmatrix.com/trac/</a>) and look for</div>
<div>the current win7 64bit version. I used: "Twisted-12.3.0.win-amd64-py.2.7.msi". </div><div><br></div><div>Aside: it turns out that you can install the 32bit Twisted version as well, and it will make </div><div>
the message go away. Not sure if anything actually works -- we did that last week</div><div>without final success.</div><div><br></div><div>But with this addition, the rest of the build step will complete with no indication of error.</div>
<div>That brings us to the end of Step 4.</div><div><br></div></blockquote><div><br></div><div>Up to here, it's still accurate. User error begins now ;-)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div></div><div>Step 5 won't work -- at least as far as I can see. The python file named "tahoe" appears to</div><div>need a "c:\Python27\python.exe" in front of it. (I'm a linux guy -- on any unix, we can use</div>
<div>the shell trick of marking a file executable, and giving the name of the interpreter in the</div><div>first line. What is the equivalent trick for DOS/Win7?) In any event, if you want to actually</div><div>run tahoe, you do something like:</div>
<div><br></div><div>c:\Python27\python.exe <tt style="font-size:13px">C:\<span style="background-color:rgb(204,255,204);background-repeat:initial initial">tahoe</span>-lafs\bin\tahoe create-client C:\tahoelafsbase</tt></div>
<div><br></div><div>Rather than:</div><div><tt style="font-size:13px"><br></tt></div><div><tt style="font-size:13px">C:\<span style="background-color:rgb(204,255,204);background-repeat:initial initial">tahoe</span>-lafs\bin\tahoe create-client C:\tahoelafsbase</tt></div>
<div><tt style="font-size:13px"><br></tt></div><div><tt style><font face="arial, helvetica, sans-serif">as described.</font></tt></div><div><tt style><font face="arial, helvetica, sans-serif"><br>
</font></tt></div><div><tt style><font face="arial, helvetica, sans-serif">Yes, we did some path tricks, and wrote some cheesy bat files to paper</font></tt></div><div><tt style><font face="arial, helvetica, sans-serif">over some of this, but it's awkward. (the silly part is I'm sure it's </font></tt></div>
<div><tt style><font face="arial, helvetica, sans-serif">do-able under win7/dos, but I've not run across the formula in casual</font></tt></div><div><tt style><font face="arial, helvetica, sans-serif">googling)</font></tt></div>
<div><tt style><font face="arial, helvetica, sans-serif"><br></font></tt></div></blockquote><div><br></div><div>My bad. We had a bug-let in our path. The python bits now work just fine.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><tt style><font face="arial, helvetica, sans-serif"></font></tt></div><div><tt style><font face="arial, helvetica, sans-serif">The last bit comes from trying to fire it up. I'm missing a bit of notes here, but somewhere</font></tt></div>
<div><tt style><font face="arial, helvetica, sans-serif">we got a message moaning about a missing win32 api. I googled that, and came across</font></tt></div><div><tt style><font face="arial, helvetica, sans-serif">a blog who was following similar footsteps for a different application. Anyway, we installed</font></tt></div>
<div><tt style><font face="arial, helvetica, sans-serif">the </font></tt><span style="font-family:arial,helvetica,sans-serif">pywin32 pieces from </span><font face="arial, helvetica, sans-serif">sourceforge and all that went away.</font></div>
<div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">On the execution side, we're starting with getting a client up and attached to our test </font></div><div>
<font face="arial, helvetica, sans-serif">grid to see if we can pull files we've stuffed in there. The next step will be to have the box</font></div><div><font face="arial, helvetica, sans-serif">participate as a storage node. (the rest of the grid is centos, and there's ~18 of them)</font></div>
<div><font face="arial, helvetica, sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">I'm sure we'll have more questions (duh). </font></div><div><font face="arial, helvetica, sans-serif"><br>
</font></div><div><font face="arial, helvetica, sans-serif">At this point, we're interested in hearing from folks using windows to run. Please feel free</font></div><div><font face="arial, helvetica, sans-serif">to critique the steps we've followed, and the general direction. We're happy to chase/build/test</font></div>
<div><font face="arial, helvetica, sans-serif">things as well. (we have a few bored-boxen that could use some work)</font></div><div><br></div></blockquote><div><br></div><div><br></div><div>This days progress has us successfully with a create-client on the box, with a fairly decent</div>
<div>test of it's functionality. (i.e. puts, gets, rms, etc)</div><div><br></div><div>We've moved on to do a create-node, and are in the middle of testing that. It's on the grid as</div><div>far as the introducer is concerned.</div>
<div><br></div><div>--krk.</div><div><br></div><div>---</div><div>Kim Knuttila </div></div>