[00:02:09] TimStarling: sorry, was afk. no platform meeting an hour ago [00:02:19] however, 1:1 now :) [00:06:56] Ryan_Lane: Okay so I'm going to start the first pass of installing etherpad lite. First question, should I install apache2 via apt? From puppet? [00:07:37] puppet would be best??? it's not the most straightforward thing to do [00:07:38] let me look for a sec [00:07:51] Sure, docs here https://github.com/Pita/etherpad-lite [00:08:12] Also could I get a wikitech account to document this with? [00:08:19] actually, it's fairly straightforward :D [00:08:24] johnduhart: sure [00:08:33] johnduhart: make it yourself, and I'll promote you [00:09:07] Ryan_Lane: Can't create an account [00:09:10] oh. lame [00:09:20] lemme make you one then :) [00:14:00] In the mean time I'll be writing it up on etherpad to post later http://etherpad.wikimedia.org/EtherpadLite [00:14:28] Ryan_Lane: Right so, where do I begin? [00:14:45] ah. I just added a new puppet class to use [00:14:59] so, if you click "configure" on your instance... [00:15:16] you can select misc::apache2 and click submit [00:15:35] Got a 500 error [00:15:41] then you can force a puppet run on your instance by doing "puppet -tv" as root [00:15:43] really? [00:15:46] Yes really [00:15:58] hmm. worked for me. [00:15:58] odd [00:16:05] one sec [00:16:24] can you try again? [00:16:31] I want to see the error in the apache log [00:17:00] ah ha [00:17:01] There [00:17:45] can you send me the URL on the "configure instance" page? [00:18:43] Ryan_Lane: https://labsconsole.wikimedia.org/w/index.php?title=Special:NovaInstance&action=configure&project=etherpad&instanceid=I-00000066 [00:19:58] This extension is in SVN right? Spotted another minor issue I might as well fix [00:21:02] Yup, checkingout now [00:22:26] much better. fixed in the interface now too [00:22:37] the extension is in svn yeah [00:22:47] the link "back to blah" is broken for configure :) [00:23:00] yup [00:23:02] :) [00:23:12] https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&component=OpenStackManager&product=MediaWiki%20extensions&list_id=45280 [00:23:25] oof [00:23:28] :) [00:24:13] https://bugzilla.wikimedia.org/show_bug.cgi?id=31873 [00:24:19] that's the bug for that issue [00:25:45] the hard part about fixing stuff in the extension is that it isn't easy to set up a development environment for it [00:25:57] it takes a shit-ton of architecture to test against [00:27:41] yeah same thing with CentralAuth [00:27:51] Ryan_Lane: We should create a lab for it!!! [00:28:03] I was actually planning on putting it in labs ;) [00:28:13] I had it in a virtualized environment before [00:30:06] Ryan_Lane: openstack, is that like pacemaker type stuff? [00:30:13] nope [00:30:14] crm, or whatever its called [00:30:17] it's like EC2 [00:30:33] ah. haven't ever played with EC2 instance yet actually [00:30:33] Amazon EC2, that is [00:30:47] it's like an entire EC2 stack on your own hardware [00:31:27] so basically its for managing a cluster setup? [00:31:38] one that can be managed via an API [00:31:44] but yep [00:32:11] so, mediawiki is managing the cluster via its API using the OpenStackManager extension [00:34:05] Ok ok so let's try this again [00:34:17] So we added the misc::apache class, and I run sudo puppet -tv [00:34:30] But it tells me -tv is an ambiguous option [00:34:37] puppetd -tv [00:34:38] sorry [00:34:40] AH! [00:35:21] so, document things like which apache modules are required, as you install them [00:35:36] A bunch of failed dependencies are normal right? [00:35:36] and which packages you install via apt [00:35:39] umm [00:35:40] right [00:35:45] shouldn't be :) [00:35:52] curious, debian or ubuntu? [00:35:54] lemme go in and run it :) [00:35:55] ubuntu [00:36:04] *troubled boo's slightly ;) [00:36:16] although im one to talk with a ubuntu desktop :D [00:36:21] we use ubuntu for everything ;) [00:36:43] debian all over here cept workstation, but not like there is much difference I guess :) [00:36:55] johnduhart: I didn't see any dependencies fail [00:37:03] I see this: err: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from source(s) puppet://virt1.wikimedia.org/plugins [00:37:09] but thats normal, until I fix it :) [00:37:23] and apache is running on the box, thankfully [00:37:38] but anyway, document all things installed or configured [00:37:44] then we'll go through and puppetize it [00:37:57] we can walk through it together, if you'd like [00:38:01] Yup, doing that here: http://etherpad.wikimedia.org/EtherpadLite [00:38:02] then we'll kill your instance ;) [00:38:06] I would like that a lot, lol [00:38:20] here's why we'll kill it: http://ryandlane.com/blog/2011/11/02/a-process-for-puppetization-of-a-service-using-nova/ [00:38:43] Ryan_Lane: I know that's why I asked about your blog before :) [00:38:45] we'll puppetize it on the second instance, using the documentation [00:38:54] then we'll kill that one, and install it just using puppet [00:38:59] on a new instance [00:39:07] then we know it just works! ^_^ [00:39:32] and you'll be the first volunteer to puppetize something for us [00:40:29] so you're kind of a guinea pig here. heh [00:40:53] Ryan_Lane: Question, since this isn't in a package how will puppetize it [00:41:03] we'll need to make a package too [00:41:43] is it a binary? [00:41:59] It's a node server(?) [00:42:00] have you made a debian package before? [00:42:02] nope [00:42:15] *johnduhart would really like to know though [00:42:19] I've never dealt with node [00:42:27] making debs is a pain in the ass [00:43:16] I'd imagine this one will be fairly straightforward [00:44:53] ugh, nodejs isn't in apt with lucid [00:44:59] *johnduhart looks for an ppm [00:45:09] ah, so it outputs a node server, which is then proxied to via apache [00:45:15] yup [00:45:38] why is nodejs needed? [00:45:59] the installation demo doesn't show it installed [00:46:09] To run the server? [00:46:17] oohhhh [00:46:19] they build node [00:46:45] Don't we use node somewhere in WMF? someone should of made a puppet thing already [00:46:57] we don't now [00:46:59] we will be [00:47:15] oh [00:47:29] well, the good thing is that you can likely pull the natty package and backport it to lucid [00:47:50] Yay [00:47:59] oh wait [00:48:20] that's 0.2 not .4 like it asks on the README, might be an issue [00:48:38] pull from ocelot then [00:48:45] or pangolin [00:49:05] you'll need to rebuild the package [00:49:11] as hardy [00:49:14] Right [00:49:27] err [00:49:28] not hardy [00:49:30] lucid [00:50:21] Okay, so let's start backporting that. Where should I look to begin that [00:50:44] deb-src http://us.archive.ubuntu.com/ubuntu/ oneric main universe [00:50:44] deb-src http://us.archive.ubuntu.com/ubuntu/ oneric universe [00:50:44] deb-src http://us.archive.ubuntu.com/ubuntu/ oneric multiverse [00:50:54] that needs to be added to the apt sources list [00:51:05] then you can do apt-get update, then apt-get source nodejs [00:51:16] or not [00:51:55] Can I do this on pad1 or should I spin up a new instance for this so we keep pad1 clean? [00:52:18] can do it on pad1 [00:52:23] pad1 is the dirty one ;) [00:52:30] heh okay [00:52:37] deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric main universe [00:52:38] deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric universe [00:52:38] deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric multiverse [00:53:26] I was missing an i before ;) [00:53:33] ah [00:53:48] silly naming conventions, why you so complex [00:54:04] why does ubuntu have to use such weird names? :) [00:54:27] one thing I like about debian over ubuntu. can't ever remember the names of ubuntu :) [00:54:32] we have a build host for making this stuff. I'm not sure how easy it'll be on that host [00:54:40] probably easy enough [00:54:44] you want to use pbuilder, though [00:55:20] I really need to make a proper build host [00:55:33] that's on my todo list :) [00:55:44] Okay, apt-get source'd it. Now what :) [00:55:55] sec [00:56:08] you need dpkg-buildpackage [00:56:24] which is installed, it seems [00:56:24] Let me document this too, hold on [00:56:39] you need pbuilder installed too [00:57:06] this is good to document for building stuff, but you won't need it in the future for etherpad-lite [00:57:21] unless you need to upgrade it [00:57:30] I mean just document in general backporting and building these packages [00:57:37] hopefully we'll have a build host that does it for you, then :) [00:57:42] ah. yeah. good idea [00:57:44] For me and any other volunteer [00:57:54] and ops. we hate building packages [00:58:44] you guys host your own mirror for custom packages too I assume? or just local fs dpkg -i? [00:58:55] custom repo [00:59:22] <^demon> We should change the wmf logo to a unicorn too. [00:59:29] dpkg -i is evil ;) [00:59:34] ^demon: heh [00:59:46] I was wondering how long it would take till someone asked about the unicorn :) [01:00:03] heh [01:00:16] im guessing the 3 lines are symbolic of ubuntu? [01:00:28] <^demon> I'm still wondering til someone comes along and makes it change it :( [01:00:55] <^demon> us change it, even [01:01:01] <^demon> Damn, I can't typoe this evening. [01:01:02] <^demon> Type. [01:01:02] Ryan_Lane: Okay so we up to the apt-get source part, let's continue http://etherpad.wikimedia.org/BackportPackage [01:01:03] <^demon> Fuck. [01:01:16] troubled: nah, that's on our wikimedia logo [01:01:17] ^demon: ya, can't even typo right tonight eh? ;) [01:01:59] johnduhart: so, if we are lucky, we just need to change changelog in the debian directory [01:02:39] I put this there:nodejs (0.4.9-2wm1) lucid-wikimedia; urgency=low [01:02:39] * backporting to lucid [01:02:39] -- Ryan Lane Wed, 02 Nov 2011 01:02:18 +0200 [01:02:41] err [01:02:42] nodejs (0.4.9-2wm1) lucid-wikimedia; urgency=low [01:02:42] * backporting to lucid [01:02:42] -- Ryan Lane Wed, 02 Nov 2011 01:02:18 +0200 [01:04:06] unfortunately deb building stuff is very specific about the format of the changelog [01:04:18] because debian hates every packager on the planet [01:05:07] there is a tool to update the changelog iirc, no? [01:05:13] dch or something [01:05:18] maybe [01:05:26] debchange - Tool for maintenance of the debian/changelog file in a source package [01:05:30] of course, now there are build dependencies [01:05:35] that are unmet [01:06:04] dch is the alias for debchange I guess, but it should adhear to policy iirc (been a loooong time since i tried it) [01:06:09] I'm seeing that by running: dpkg-buildpackage -rfakeroot -S [01:06:42] Ryan_Lane: So now what [01:06:58] most of those dependencies are likely bullshit [01:07:15] at least the version numbers anyway [01:07:44] so, I'm going to pull the natty version, and see what's there :) [01:07:47] if you stole it from a newer dist of the package, most likely :) [01:07:48] have I mentioned this sucks? [01:08:01] lol [01:08:02] don't blame you, deb building is.... [01:08:38] my eyes gloss just reading the policy about version numbering rules :) [01:12:21] heh [01:12:27] it was complaining about this missing: /usr/share/cdbs/1/rules/upstream-tarball.mk [01:12:37] so I just commented it out in the rules file [01:12:59] that's just to get the dsc file [01:13:14] this command: dpkg-buildpackage -rfakeroot -S [01:13:27] that's run in the nodejs-0.4.9 directory [01:13:50] then, I run: pbuilder create --distribution lucid [01:14:04] and pbuilder build ../nodejs_0.4.9-2wm1.dsc [01:14:36] Still get unmet dependencies [01:14:54] yeah. couldn't satisfy build dependencies in pbuilder either :( [01:15:08] The following packages have unmet dependencies: [01:15:08] pbuilder-satisfydepends-dummy: Depends: cdbs (>= 0.4.85~) but it is not installable [01:15:08] Depends: libv8-dev (>= 3.1.8.22) but it is not installable [01:15:08] Depends: libc-ares-dev (>= 1.7.3) but it is not installable [01:17:01] `apt-cache policy` explain why those aren't installable? or simply too high version number for current dist? [01:17:59] too high version for the distro [01:18:02] forgive me for being noisy, but I like a good "geeking out" :) [01:18:04] so, I'm finding the ones we have [01:18:11] libv8-dev (>= 2.0.3), [01:18:16] cdbs (>= 0.4.62), [01:18:21] libc-ares-dev (>= 1.7.0), [01:18:27] and changing that in the control file [01:18:36] then we'll see if it'll build with those versions [01:18:54] Are you in my home Ryan_Lane [01:18:58] nope [01:19:03] k [01:19:11] I'm on my build system [01:20:56] worst case we can't use lucid [01:20:57] Ryan_Lane: What's your opinion on ppas? [01:21:02] https://launchpad.net/~chris-lea/+archive/node.js [01:21:16] he have lucid packages? [01:21:22] we usually don't use ppas [01:21:52] he does have lucid packages [01:22:02] we can always pull the source deb from there if this doesn't work [01:22:06] and it didn't :) [01:27:02] Ryan_Lane: Okay so I have his src now, so I'll add the changelog entry and hopefully it'll build right? [01:27:31] hopefully, yeah. I was gonna look inside of it first :) [01:29:27] looks fine [01:31:10] https://github.com/tobert/nodejs-ubuntu-lucid [01:31:22] that may be even better [01:31:27] :o [01:31:36] Well the ppa seems to be very well updated imo [01:32:03] the git-hub thing is the oneric package's debian directory correctly updated :) [01:32:43] ah [01:32:47] *johnduhart wouldn't know better [01:34:34] Ryan_Lane: Okay so now I have that cloned in my ~/src dir, what now [01:34:52] modify the changelog, and try to build it :) [01:37:13] the good thing about using this, rather than the ppa version, is that it's easier to backport fixes later [01:37:14] Getting depedency errors [01:37:19] and everytime you have to rebuild, take a shot ;) [01:37:23] probably doing something wrong [01:37:47] what kind of dependency errors? [01:37:52] are you using pbuilder? [01:38:07] dpkg-buildpackage [01:38:15] oh, you may need packages installed just to run that [01:38:25] you can add -d to ignore them [01:38:38] cause what you really want is the dsc [01:38:47] :o [01:39:00] debian/rules:3: /usr/share/cdbs/1/rules/utils.mk: No such file or directory [01:39:00] debian/rules:4: /usr/share/cdbs/1/rules/debhelper.mk: No such file or directory [01:39:00] debian/rules:5: /usr/share/cdbs/1/class/autotools.mk: No such file or directory [01:39:09] yeah, you need cdbs package installed [01:39:14] did you do a "apt-get buildep "? [01:39:20] err build-dep [01:39:48] or would it help rather, if you are using a already made package as a starting point [01:45:27] Ryan_Lane: Cool dpkg ran, so now pbuilder? [01:45:33] yep [01:47:39] *johnduhart waits paitent for pbuilder create [01:48:19] Now for build [01:49:03] uhoh [01:49:20] chmod: cannot access `/tmp/buildd/nodejs-0.4.9/./configure': No such file or directory [01:50:12] This is just so much fun! [01:50:16] heh [01:50:56] *johnduhart pokes Ryan_Lane [01:51:14] Could you look at /home/johnduhart/src/nodejs-github since I probably did something wrong [01:51:46] hm [01:52:06] Was I supposed to checkout the 4.9 there and then gitclone that other repo to debian... [01:53:48] oops. sorry :) [01:54:08] it build for me :) [01:54:27] I wonder if it's how pbuilder is configured [01:55:00] I don't see that directory [01:55:06] dpkg -L does list some /etc files here for pbuilder [01:55:20] buildd-config.sh and pbuilderrc, specifically [01:56:30] although if this goes well, you wont need to run pbuilder anymore, you can just invoke johnduhart with `apt-johnduhart build-pkg` ;) [01:56:42] hehehe [01:56:44] johnduhart: I don't see that directory in your home dir [01:56:49] well, I already built it :) [01:56:55] this was more so you can see how it's done [01:56:56] Ryan_Lane: I nuked it and I'm trying again [01:57:00] ah ok [01:57:17] I'm about to leave for the night [01:58:06] back tomorrow. later guys [01:58:12] \o [01:58:14] seeya [02:00:43] huh, root can't read my home directory [02:01:19] O_o [02:01:47] I guess it's intential so that people can't read others homedirectories, but it means I can't sudo scripts [02:01:48] unless [02:02:27] weird, I always thought root had capability specifically for bypassing fs acls [02:02:49] ok, I just need to move it out of the home dir and into a dubdirectory [02:02:54] AHA! [02:02:56] although with stuff like apparmor and selinux, one never knows wth works these days [02:02:58] It's building :D [02:03:03] woot! [02:03:17] lmao I never checked out the source last time [02:03:56] so you were compiling with just a ./debian dir and no source? [02:04:01] yeah. [02:04:05] heh, smooth [02:12:28] johnduhart: so what is all this packaging for anyways? is this how you deploy stuff on the cluster to test your extensions and stuff? [02:12:35] <^demon|away> Down to 26 unidentified committers and 24 with a name but no e-mail \o/ [02:12:59] troubled: This is for deploying etherpad-lite to the production [02:13:10] ah [02:13:16] Which includes puppetization http://ryandlane.com/blog/ [02:13:17] i take it you just set this up today? [02:13:33] We started today, yes [02:13:36] only my second time in this channel, so im a little green :) [02:13:42] ah :) [02:15:59] ah, that page mentions NFS for home dirs, could explain why you cant read ~/ as root if they are squashing root or something [02:16:47] only a guess of course. sadly my eyes can't see into remote machine syslogs ;) [02:17:29] seems to confirm it at a glance: http://ryandlane.com/blog/2011/11/01/sharing-home-directories-to-instances-within-a-project-using-puppet-ldap-autofs-and-nova/ [02:18:30] although I dont see the squash option. still possibly the cause. shame Ryan left or i'd ask [02:20:55] ah, man says its default, could explain why i dont see it. so maybe after all [03:31:17] *johnduhart assembles a npm package [11:40:05] YAY [11:40:08] I did it! [11:40:22] *johnduhart packaged node and npm [11:43:11] npm? [11:44:47] Nikerabbit: package manager for node, needed for etherpadlite [11:44:57] Ah! [11:45:01] Are you packaging etherpadlite? [11:45:08] yes please please please [11:45:13] Once you do that [11:45:16] the bugs in current etherpad are driving me nuts [11:45:19] PLEASE put it in /trunk/debs [11:45:31] Sure [11:45:42] RoanKattouw: are there any deployments going on now? I was going to do the webfonts test [11:45:59] Then I can get Ryan to put it in the repo and puppetize etherpadlite (and hopefully test it on the virt cluster) [11:46:03] Nikerabbit: No, all yours [11:47:38] RoanKattouw: I'm doing all of that. Packaging and puppetizing [11:47:43] On labs [11:47:47] Oh, cool [11:47:58] Do you have access to the puppet git repo? [11:48:39] I think so [11:49:05] You may want to create a topic branch for the etherpadlite puppetization and publish your topic branch through gerrit [11:49:14] In case you want to do that, I wrote a guide https://labsconsole.wikimedia.org/wiki/User:Catrope/Topic_branches [11:49:41] (Cause it's what I did for my logmsgbot and LocalisationUpdate puppetizations, and Ryan and I fixed some issues while going through that, so it should be working now) [11:50:57] For instructions on how to set up a checkout of the puppet repo locally, see the main page of that same wiki [11:51:08] RoanKattouw: wow lots of errors [11:51:16] RoanKattouw: Cool thanks [11:51:18] Nikerabbit: From scap? [11:51:39] RoanKattouw: yeah [11:51:50] well, remote host id changex *3 and few others, so not so much [11:52:08] Are you getting permissions errors for cache/l10n or .git directories? [11:52:24] Remote host ID changed is a known side effect of upgrading the API Apaches to lucid [11:53:03] (Peter thought he'd upgraded all Apaches, we discovered yesterday that he'd forgotten the entire 290-301 range) [11:55:18] RoanKattouw: fortunately no [11:55:36] Hm OK [11:55:59] RoanKattouw: but I only did sync-dir WebFonts so... [11:56:09] Oh, right [11:56:22] So you got remote host ID changed for ... srv290, 291 and 292? [11:57:12] nope [11:57:20] 296,300 and 301 [11:57:30] 290 complained something about tty not present [11:58:26] 292 295 299 asked for password [12:01:39] RoanKattouw: hmm nothing is logging my syncs... that isn't normal right? [12:01:54] no, but it's known breakage [12:02:28] I see, since yesterday? [12:04:17] Since Monday I think [12:04:27] Or maybe Tuesday [12:04:42] I puppetized logmsgbot the same way Ryan puppetized nagios-wm [12:04:49] Using the ircecho package from our Debian repo [12:04:51] grrr fucking school proxies [12:04:56] git won't work [12:05:07] BUT... that package is only in the lucid repo (fenari runs hardy), and depends on a newer version of some Python library that isn't in hardy [12:06:16] Ryan pushed the package to the hardy repo, but then we discovered the Python lib issue, which isn't fixed yet [12:10:52] RoanKattouw: http 304 works, although browser still need to revalidate on each request... [12:11:15] Is it sending must-revaliate? [12:11:18] *must-revalidate [12:11:59] nope [12:12:14] but there is no Expires header either [12:12:47] So what is there? [12:13:00] Could you pastebin the response headers for both a 200 and a 304 response? [12:13:18] I'm testing with http://test.wikipedia.org/w/extensions-1.18/WebFonts/test.html [12:13:27] OK [12:13:33] I am going to make lunch now [12:13:39] I'll poke at it when I get back [12:14:11] hmm lol [12:14:14] This is what Firebug tells me [12:14:15] Last Modified Thu Nov 03 2011 13:13:25 GMT+0100 (CET) [12:14:17] Last Fetched Thu Nov 03 2011 13:13:25 GMT+0100 (CET) [12:14:18] Expires Thu Nov 03 2011 13:14:09 GMT+0100 (CET) [12:14:26] interesting [12:14:36] If your resources are cached for 44 seconds, you have a problem :D [12:14:51] I'll poke more after lunch [12:19:45] (note, those aren't request or response headers, but it's the cache metadata that Firebug exposes) [12:20:00] http://etherpad.wikimedia.org/qRtBb5GShr [12:28:41] yay, etherpad lite is working. sort of [12:57:48] Nikerabbit: Yeah so no caching headers are sent at all [12:57:56] No Expires, no Cache-Control, no nothing [13:00:59] RoanKattouw: only etag and date [13:01:18]