08:27:00 #startmeeting MediaWiki - Deployment Meeting 08:27:00 Meeting started Thu Apr 5 15:27:37 2012 UTC. The chair is lwade. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:27:00 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:27:00 #chair gregdek dfederlein hspencer 08:27:00 Current chairs: dfederlein gregdek hspencer lwade 08:27:00 even on a single instance we want some front end caching. 08:27:00 #action design doc for MediaWiki and scaling procedures 08:28:00 #info We need a design document and some planning around the platform 08:28:00 great 08:28:00 #undo 08:28:00 Removing item from minutes: 08:28:00 err 08:28:00 no that's fine 08:28:00 did that undo me or you? 08:28:00 oh ok :S 08:28:00 no idea 08:28:00 lol 08:28:00 crap 08:28:00 sorry 08:28:00 s'ok, we can spam it into the logs :D 08:28:00 irc://irc.freenode.net/#info We need a design document and some planning around the platform 08:28:00 err 08:28:00 copy paste sucks in colloquy 08:28:00 #action dfederlein and lwade to create a design document 08:28:00 I'll stop now 08:28:00 there we go 08:29:00 gregdek, were you chasing a registration for hostname or something? 08:29:00 FYI, Eutester in here in 30m. 08:29:00 dfederlein, when you do the design doc 08:29:00 lwade: not actively chasing that yet. 08:29:00 i would like to work with you on that 08:29:00 i have an idea 08:29:00 awesome 08:29:00 lets put hspencer in that 08:30:00 hspencer: very cool 08:30:00 But hspencer, it would probably be a good idea if we can get wiki.eucalyptus.com set aside. 08:30:00 #action hspencer to help with design 08:30:00 gregdek, ? 08:30:00 what you mean? 08:30:00 gregdek, i thought i was a hired hitman 08:30:00 :-D 08:30:00 take projects OUT! 08:30:00 We already have it but if we can take it off the old wiki 08:30:00 lwade, what you mean? 08:30:00 we have data on the old wiki we need, as long as we have an IP I can get to we're good 08:31:00 ah i see 08:31:00 until we migrate off 08:31:00 We looked at this a while back 08:31:00 where is the current media wiki being held? 08:31:00 or ran 08:31:00 the old wiki has a few items but mainly they will be ditched 08:31:00 useful ones going into KB 08:31:00 ok 08:31:00 a couple we might want to move 08:31:00 but tbh they all need rework anyhow 08:31:00 so would it hurt to deploy a new one? 08:32:00 and migrate data? 08:32:00 #info existing articles won't be migrated but rather created anew 08:32:00 or just keep the old one and just scale it out 08:32:00 ? 08:32:00 I don't think there is anything to migrate 08:32:00 We're looking at a completely different wiki? 08:32:00 wait, what? 08:33:00 * lwade is confused 08:33:00 To be clear: my thought is "set up MW, move most of what's on projects to MW". 08:33:00 hspencer, by Wiki do you mean projects or the old wiki ? 08:33:00 yea 08:33:00 That's true, we do have an old wiki on open. 08:33:00 i am confused 08:33:00 I don't even think about that one. 08:34:00 maybe i am the one thats off 08:34:00 me neither 08:34:00 it's good as gone tbh 08:34:00 :P 08:34:00 86 it 08:34:00 k, so maybe i need to understand what we want to do 08:34:00 we want to install irc, hspencer 08:34:00 LOL!! 08:34:00 hspencer; build an uber-awesome MediaWiki platform for community 08:34:00 k 08:35:00 with bacon 08:35:00 well, i think thats easy 08:35:00 and 08:35:00 i may have a design plan that will promote AWS and Euca even more 08:35:00 :-) 08:35:00 but thats separate 08:35:00 do we have the tasks mapped out as to what we need to do to migrate data from wiki "X" to wiki "Y" 08:35:00 ? 08:36:00 nope 08:36:00 and what is wiki "X"? wiki "Y"? 08:36:00 Ok 08:36:00 so Wiki X is not really a wiki, per se 08:36:00 but redmine 08:36:00 k 08:36:00 and Wiki Y is the MediaWiki instance we want to put into production 08:36:00 forgive me if this info has already been covered 08:36:00 k 08:37:00 alright 08:37:00 nope, s'ok 08:37:00 this is exactly what we want to map out 08:37:00 so far, we have a platform design we should work on 08:37:00 k 08:37:00 to actually get MediaWiki built and designed for scale 08:37:00 i don't think that will be an issue 08:37:00 not too much emphasis on that last bit 08:37:00 same 08:37:00 we already have http://173.205.188.71/wiki/index.php/Main_Page for testing too 08:38:00 we jue need to think about underlying DB, any HA etc. 08:38:00 :-D 08:38:00 thats where my plan comes in 08:38:00 ;) 08:38:00 so 08:38:00 dfederlein, should i draw something up 08:38:00 and send it to you? 08:38:00 well, i can send it to the group 08:39:00 yes please 08:40:00 yes plz 08:40:00 can has? 08:40:00 use google sketchup 08:40:00 we can watch you drawing it :P 08:40:00 or something 08:41:00 is sketchup still actively defveloped? 08:41:00 Napkin + scanner. 08:41:00 I thought that was going away with orkut and a bunch of other services 08:42:00 yea 08:42:00 i can do that 08:42:00 i hope you guys like it 08:42:00 so pretty much 08:42:00 no idea dfederlein 08:42:00 we will use AWS 08:42:00 for the web page and use ElastiCache 08:42:00 THAT'S A CRAZY IDEA!? 08:43:00 ElastiCache will pull information from a database setup we have running at CoreSite 08:43:00 i think this is what folks would like to see for use case scenarios 08:43:00 Love it! 08:44:00 who's gonna pay for the AWS-time ? :D 08:44:00 * scotm lurking and loving what he's reading. 08:44:00 lwade, we got an account 08:44:00 lwade: you are, right? 08:44:00 heh 08:44:00 ;) 08:44:00 we have an account for IT 08:45:00 don't WikiPedia use ElastiCache ? 08:45:00 T-15 mins until we need the room. 08:45:00 ok, ty 08:46:00 * lwade has really no background in ElastiCache 08:46:00 One thing I feel obliged to point out: 08:46:00 Once we make a firm decision, I would like to move quickly. 08:47:00 Using AWS will help this 08:47:00 OK. 08:47:00 they have some good pre-built AMI's for MediaWiki instances too 08:47:00 so this could be quite nice 08:47:00 If we go this route, we need your time hspencer 08:48:00 lwade, my time is expensive 08:48:00 i am not a cheap date 08:49:00 not what obino told me 08:49:00 you just can't pimp me out 08:49:00 LOL!! 08:49:00 hspencer: I've got a bottle of Courvoisier with your name on it. 08:49:00 that works 08:49:00 settled, easy. 08:49:00 THE POWER OF COMMUNITY. 08:49:00 (mostly fueled by booze.) 08:49:00 hspencer, you've been working on some ElastiCache implementation for Eucalyptus haven't you? 08:49:00 My job description: turning alcohol into code. 08:50:00 :P 08:50:00 Ok 08:50:00 OK, we have 10m left. Who's got what ball, and when do we bring it back together? 08:50:00 So I think we have a phase1 here 08:50:00 which is design 08:51:00 It sounds like lwade, hspencer and dfederlein are going to work on a design here 08:51:00 using hspencer's ElastiCache plan 08:51:00 yep 08:51:00 #info use Amazon ElastiCache in our MediaWiki platform design 08:52:00 ok 08:52:00 Are we willing to put a date on this first cut of design ? 08:52:00 How about 13th April ? 08:52:00 i am a whore for Courvoisier 08:53:00 i will probably have a draft done by tomorrow 08:53:00 but yea 08:53:00 13th sounds good 08:53:00 oh sweet 08:53:00 ok 13th for something, platform wise, that we can implement on 08:53:00 to me, this wouldn't necessarily be the details of MediaWiki 08:53:00 but rather the infrastructure for it 08:54:00 Ok 08:54:00 lets work off what you're thinking hspencer 08:54:00 and we can go from there, I think we need to see your master plan first 08:54:00 then we can start designing the components (e.g. the DB backend etc.) 08:54:00 k guys, i gotta go here in a min 08:54:00 Does this sound ok to peeps? 08:55:00 got an engineering meeting 08:55:00 but yea 08:55:00 I like it. 08:55:00 sounds good to me 08:55:00 Ok, lets run with it and see where it goes ;) 08:55:00 #action hspencer, dfederlein and lwade to work on design documentation for April 13th 08:55:00 It would be good to have something up by end of June 08:55:00 latest 08:56:00 Ok, thanks guys 08:56:00 #endmeeting