[00:47] *** ballen is now known as ballen|away [05:11] *** heavysixer has joined #arpnetworks [05:14] *** heavysixer has quit IRC (Client Quit) [05:34] *** heavysixer has joined #arpnetworks [07:08] *** visinin has joined #arpnetworks [07:22] *** heavysixer has quit IRC () [09:30] *** heavysixer has joined #arpnetworks [09:36] *** timburke has quit IRC (Remote closed the connection) [09:36] *** timburke has joined #arpnetworks [09:38] *** timburke has quit IRC (Client Quit) [09:39] *** timburke has joined #arpnetworks [09:43] *** heavysixer has quit IRC () [09:49] *** timburke_ has joined #arpnetworks [09:49] *** timburke_ has quit IRC (Read error: 104 (Connection reset by peer)) [09:54] *** timburke_ has joined #arpnetworks [09:55] *** timburke has quit IRC (Read error: 145 (Connection timed out)) [10:06] *** timburke_ is now known as timburke [11:19] *** ballen|away is now known as ballen [11:32] *** heavysixer has joined #arpnetworks [12:26] up_the_irons: are you doing authentication in your Sinatra app? [12:40] ballen: no [12:41] hmm looking for the best auth lib for Sinatra [12:41] yeah, dunno [12:41] * up_the_irons reads scrollback [12:41] one that I can rip apart and make it work on a key/value db [12:44] mhoran: ballen: I could hotplug a drive, sure, but it'll look like USB. Would rather attach it permanently [12:44] ballen: mhoran: KVM supports memory ballooning [12:44] ah, was just thinking of a case where running a site that couldn't be brought down [12:44] and running out of storage [12:44] ballen: for a live migration, the host and target must be running the exact same VM parameters [12:45] yea I figured that out after I said it [12:45] ballen: it doesn't make sense for the HD to be larger anyway, b/c all live migration implementations require the disk to actually be shared (same disk) [12:46] ah right [12:47] bleh be so much easier than designing an app to be able to migrate live across servers [12:47] mhoran: ballen: I'm working on live migrations across regions as well (first step: migrate into a different data center within the same city, then try into a different metro region) [12:49] thats hot [12:50] the hardest part, actually, i just getting the live migration from machine to machine; once that is done, data center to data center is not that hard, b/c if it is seen as the same network anyway, the servers don't care that they are in the same cabinet 2 ft away, or thousands of feet away [12:50] right [12:51] fyi, you wouldn't use a single VM for a site that couldn't experience a lot of downtime, that'd be scaling vertically; which is generally bad. if your site really can't be down, you'd build a cluster for it [12:51] yes yes [12:52] just alot easier to program for scalling vertically [12:52] but much more expensive [12:52] sure, cause we've all grown up programming for vertical platforms [12:52] we're "used" to it [12:53] yea [12:53] i imagine the next generation will have an easier time w/ clustering, or building an app that scales horizontally [12:53] I hop so [12:53] hope* [12:53] assuming education adapts [12:53] which it is normally slow todo [12:54] most coders don't learn their chops through formal education anyway though [12:54] i didn't either [12:54] but i still stayed in school [12:54] yea likewsie [12:54] likewise [12:54] cuz it's important on so many levels [12:54] :) [12:57] *** timburke has quit IRC (Read error: 54 (Connection reset by peer)) [12:57] *** timburke_ has joined #arpnetworks [12:57] http://gist.github.com/40246 [12:57] If i rip datamapper out and replace it with Redis goodness that'll due [12:59] looks promising [13:09] *** ballen is now known as ballen|away [13:51] i hate rspec [13:51] i used to like it, but now, i fucking hate rspec [13:52] it won't run any specs [13:52] nothing [13:52] nada [13:52] just returns to the prompt silently [13:57] up_the_irons: Cool, cool and cool. [13:57] heh [13:58] They're building out some cool clusters at my alma mater. [13:58] There's actually one there now which just idles. Unfortunate. [13:59] But there's a new prof working in bioinformatics, they had to buy a new CRAC unit to accomodate his cluster. [13:59] Pretty exciting. They also were planning to hire a dedicated cluster sysadmin, but I think they ran out of money. [14:00] Unfortunately, all but two people on that staff, including the manager, are idiots. [14:11] cool, and not cool [14:11] cd $food [15:03] *** heavysixer has quit IRC () [16:05] *** heavysixer has joined #arpnetworks [17:05] *** heavysixer has quit IRC () [17:28] *** heavysixer has joined #arpnetworks [17:33] *** ballen|away is now known as ballen [18:37] *** ballen is now known as ballen|away [19:18] *** ballen|away is now known as ballen [19:27] *** heavysixer has quit IRC () [19:58] *** heavysixer has joined #arpnetworks [20:00] *** ballen is now known as ballen|away [20:07] *** heavysixer has quit IRC () [20:53] *** ballen|away is now known as ballen [22:50] *** timburke_ has quit IRC ("Leaving") [22:55] *** timburke has joined #arpnetworks [23:10] *** visinin has quit IRC ("sleep") [23:27] http://ohm.keyvalue.org/ [23:27] only the most freaking cool library ever [23:27] going to save me sooo much time on this project [23:37] ballen: nice [23:37] don't have to figure out all my key/value schema now [23:37] even though I already do have that figured out [23:37] it'll take less code now [23:38] also trying to get authlogic to work with Sinatra [23:39] is what you're building online anywhere? [23:40] nah just starting to plan it out [23:40] really should be working on my thesis [23:40] but meh [23:42] haha [23:43] seems like authlogic depends on active_record a little bit [23:43] which sucks [23:43] eeeww [23:43] f that [23:44] yea [23:44] so I may just stick with home brew auth [23:44] for now [23:44] and build it out if needed [23:44] ballen: so does this Ohm basically let you store ruby objects inside Redis? [23:44] umm [23:44] its basically lets you work with models as you would in Rails [23:45] gotcha [23:45] class User < Ohm::Model [23:45] attribute :login [23:45] end [23:45] now the User model has an login attribute [23:45] when you save the model [23:46] you can only access it by id [23:46] say you want to access it by login [23:46] you add index :login [23:46] now you can do User.find(:login, 'name') [23:47] index creates a Set [23:47] where attribute is just a single hash in the db [23:48] also could add something like set :admins, Admin [23:49] and now you'd have @user.admins [23:49] interesting [23:49] similar to rails [23:49] all its doing its creating new sets in the backgroud so it can index the data in a way that lets you search for it [23:50] so each time you add an index or set its add a decent amount of duplicate db to db [23:50] duplicate data to the db* [23:50] but such is life with key/value db's [23:51] right [23:51] so like "index :login", creates a key that is "login" with value that is an id, that then let's you look up "User" [23:52] exactly [23:52] theres also list and counter [23:53] ah [23:53] list is not indexable [23:53] either FIFO, FILO, etc [23:53] counter is just a serial data type [23:54] cool thing about counters in redis is that they're atom, you don't have to worry to much about multiple clients incr or decr [23:59] SHA512 enough for password hashing?