19:11:29 <LinuxJedi> #startmeeting
19:11:30 <openstack> Meeting started Tue May  1 19:11:29 2012 UTC.  The chair is LinuxJedi. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:11:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:11:31 <mtaylor> whee!
19:11:38 <soren> Thanks everyone. SEe yo unext week.
19:11:43 <mtaylor> great!
19:12:05 <mtaylor> so - first item, as you may have noticed, we did some work on meetbot
19:12:10 <LinuxJedi> http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2012-05-01.log appears to be the previous meeting
19:12:49 <heckj> found'em
19:12:50 <LinuxJedi> doh, I mean http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-18.01.log.txt
19:13:30 <heckj> Linked into the wiki - I thin the MIME types at eavesdrop aren't working for the HTML though - it's forcing my browser to download rather than display directly for the HTML
19:14:06 <LinuxJedi> heckj: already a bug open for that
19:14:11 <clarkb> things are just going to break today for LinuxJedi I think
19:14:18 <heckj> cool, thanks LinuxJedi!
19:14:34 <LinuxJedi> heckj: I'm already doing a 12-14 hour day today though so unlikely it will get fixed before tomorrow morning
19:15:04 <heckj> no worries
19:15:07 <mtaylor> LinuxJedi: bah. I thought you usually did 20 hour days!
19:15:21 <LinuxJedi> mtaylor: I'm slipping ;)
19:15:33 <mtaylor> hehe
19:16:31 <LinuxJedi> mtaylor: plus my wife gets pissed if I work too much now
19:16:36 <LinuxJedi> mtaylor: anyway, meeting is running :)
19:16:42 <clarkb> but yes voting has been added. use the '#startvote some question? option1 option2' command to begin a voting session then vote using #vote option1
19:16:57 <mtaylor> clarkb: ++
19:17:00 <clarkb> check vote status with #showvote and end voting with #endvote
19:17:16 <mtaylor> this makes me happy. thanks clarkb
19:17:56 <LinuxJedi> #startvote do we love voting? yes no
19:17:57 <openstack> Begin voting on: do we love voting? Valid vote options are yes, no.
19:17:58 <openstack> Vote using '#vote OPTION'. Only your last vote counts.
19:18:03 <LinuxJedi> #vote yes
19:18:04 <mtaylor> #vote yes
19:18:08 <clarkb> #vote no
19:18:11 <clarkb> #showvote
19:18:12 <openstack> yes (2): mtaylor, LinuxJedi
19:18:13 <openstack> no (1): clarkb
19:18:19 <LinuxJedi> awesome
19:18:21 <soren> #vote whuh?
19:18:22 <LinuxJedi> #endvote
19:18:22 <Shrews> #vote yes
19:18:23 <openstack> soren: whuh? is not a valid option. Valid options are yes, no.
19:18:23 <Shrews> #vote yes
19:18:24 <openstack> Voted on "do we love voting?" Results are
19:18:24 <Shrews> #vote yes
19:18:25 <openstack> yes (2): mtaylor, LinuxJedi
19:18:26 <openstack> no (1): clarkb
19:18:26 <soren> Aw.
19:18:37 <Shrews> #showvote
19:18:46 <mtaylor> LinuxJedi ended the vote already
19:18:52 <Shrews> damn
19:19:00 * Shrews wanted to break it
19:19:00 <LinuxJedi> anyway, that was a quick demo ;)
19:19:14 <LinuxJedi> Shrews: I believe clarkb has a test channel to break it on
19:19:31 <clarkb> #testmeetbot here on freenode
19:19:45 <clarkb> I dno't promise the bot will always be listening through :)
19:20:33 <mtaylor> jeblair is hiking in the utah desert this week, but he's going to be looking at some improvements to the gerrit trigger plugin when he gets back
19:20:37 <LinuxJedi> I also brought the irclogs back to meetbot today and knocked up a quick 30 second homepage on http://eavesdrop.openstack.org/ to be themed at a later date
19:21:14 <mtaylor> specifically, support for matrix jobs, dependent jobs, and optimistic branch prediction-based building (all of which kind of tie in together)
19:22:29 <mtaylor> and in addition to beating his head against a brickwall trying to get new trystack machines properly stood up, devananda is going to poke at openvz support on our build slaves
19:22:47 <mtaylor> LinuxJedi: what're you up to these days?
19:23:14 <LinuxJedi> mtaylor: so, we not have meetbot under puppet control, which mostly works great apart from the logging blip just now
19:23:33 <LinuxJedi> I've done lots of CI docs
19:23:53 <LinuxJedi> including a couple of useful howtos for people wanting to work with CI stuff
19:24:19 <LinuxJedi> Jenkins job filler has had a lot of work done to it, but there are still a few things to be sorted out
19:24:51 <LinuxJedi> Stackforge gerrit managed to run out of disk which was a barrel of fun
19:24:56 <mtaylor> whee!
19:25:06 <mtaylor> (Shrews is adding some logrotation there)
19:25:17 <LinuxJedi> yes, it was all mysql backups
19:25:34 <LinuxJedi> and the puppet server on stackforge fell over which caused some more fun
19:25:53 <LinuxJedi> I've worked on adding the Ceilometer project to Stackforge, that should be ready tomorrow
19:26:15 <LinuxJedi> and that is about all I remember off the top of my head
19:26:20 <mtaylor> sounds like a good week
19:26:55 <LinuxJedi> mtaylor: two things that came up, lists and whether or not to do translations for logs
19:27:27 <LinuxJedi> mtaylor: I argued for translations for logs with error codes, but I'm not sure if that is a CI thing or a "something else" thing
19:27:28 <mtaylor> yes... someone from dreamhost is going to help with mailinglists, right?
19:27:36 <clarkb> I was looking at nova and its use of gettext and it looks like nova will currently attempt to put translations in the logs
19:27:52 <clarkb> with error codes
19:27:56 <LinuxJedi> mtaylor: I believe so, I'm a little behind catching up on that to be honest.
19:31:01 <mtaylor> we've had a few issues arise with the wiki over the last week, which brings up that we need to actually manage it
19:31:41 <mtaylor> annegentle requested that we migrate to mediawiki, and suggested that our friends at wikipedia might be interested in helping us with that
19:31:57 <annegentle> woo woo
19:32:29 <LinuxJedi> mtaylor: we inherited another server?
19:32:52 <mtaylor> well, we have it now already - we just don't do anything with it
19:33:03 <LinuxJedi> ah, fair enough
19:33:16 <LinuxJedi> mtaylor: this also falls into "what should be docs and what should be wiki"
19:33:25 <LinuxJedi> similar problem to what we had in Drizzle
19:33:36 <mtaylor> I don't have any specific action plan at the moment - just that it's one of those things we should probably actually, you know, care for
19:34:04 <LinuxJedi> :)
19:34:48 <mtaylor> also "manage the wiki" really menas "ensure that someone is managing the wiki"
19:35:10 <LinuxJedi> ah, like the mailing lists then ;)
19:35:14 <mtaylor> yup
19:35:29 * LinuxJedi is less concerned now
19:35:38 <mtaylor> goal for this week from me is to try to finish getting the tox alignment done and then turning jenkins job filler on for the rest of the projects
19:35:53 <mtaylor> our jenkins job divergence is a little silly at the moment
19:36:11 <LinuxJedi> mtaylor: is that wise considering Jim just turned it off for everything?
19:36:13 <mtaylor> as part of that, we're also making sure that when jenkins runs the tests it grabs xunit output
19:36:25 <mtaylor> LinuxJedi: well, what I mean is...
19:36:42 <mtaylor> LinuxJedi: get the tox alignment done this week _so_that_ we _could_ turn on the jenkins job filler
19:36:53 <LinuxJedi> ah! ok then :)
19:37:05 <mtaylor> LinuxJedi: now that you bring it up though... the bit we can't do in puppet at the moment (override messages)
19:37:24 <mtaylor> LinuxJedi: did jeblair talk to you about his idea to just have a python script do that bit?
19:37:26 <LinuxJedi> mtaylor: I'm planning on fixing the remaining issues with the job filler this week
19:37:31 <LinuxJedi> mtaylor: no
19:38:00 <mtaylor> LinuxJedi: idea: rather than implementing all of the things directly inside of ruby/puppet extension ... just drop a python script on the box and run that
19:38:09 <LinuxJedi> I'm sure I could do it in ruby, but I'm also sure I will kill someone in the process
19:38:25 <LinuxJedi> mtaylor: cool :)
19:39:13 <mtaylor> anyway - if you get that stuff going, and I get the projects ready for it
19:39:23 <mtaylor> maybe next week we can actually move them all to puppet/git management
19:39:49 <LinuxJedi> ++
19:41:04 <mtaylor> oh - one more thing...
19:41:34 <mtaylor> although it's mildly hp specific... we finally got our internal legal stuff done which allowed those of us who work for hp to sign the google cla for gerrit
19:41:44 <mtaylor> which means our patches to gerrit are finally starting to go upstream
19:42:05 <LinuxJedi> yay :)
19:42:22 * LinuxJedi upstreams a patch to re-write it in Python ;)
19:42:35 <mtaylor> hehe... that's actually just a git reset command ...
19:42:46 <LinuxJedi> lol :)
19:42:47 <mtaylor> that would be a re-re-write
19:43:01 <LinuxJedi> indeed :)
19:43:30 <mtaylor> that's all I've got ... anybody else out there have anything?
19:44:03 <LinuxJedi> I really do plan on having the stackforge www up this week
19:44:10 * clarkb is working on getting i8ln working now
19:44:12 <LinuxJedi> if only as a basic holding page
19:44:26 <mtaylor> w00t to both things
19:44:37 <clarkb> looks like Horizon is pushing hard to use transifex so it looks like we will be starting there
19:44:43 <mtaylor> fine by me
19:44:59 <soren> What, Gerrit used to be written in Python?
19:45:05 <mtaylor> soren: yup
19:45:17 <soren> Hm. Interesting.
19:45:25 <mtaylor> soren: check out the v1.0 tag in the repo
19:45:31 <mtaylor> it's a django app
19:45:36 <soren> Neat.
19:45:42 <clarkb> also, to fix nova i8ln whats the easiest way to stand up a quick dev/test environment for nova/openstack
19:45:47 <clarkb> devstack?
19:45:49 * LinuxJedi can only guess it because Android is Javaish (depending on your side of the Oracle suit)
19:45:53 <soren> I wonder what motivated the rewrite.
19:45:56 <mtaylor> clarkb: devstack
19:46:19 <soren> LinuxJedi: There's probably a connection there, yeah.
19:46:49 <mtaylor> also, jgit
19:47:02 <mtaylor> although python-git is pretty good these days
19:48:33 <LinuxJedi> anyway, anyone have anything else before I find out that meetbot is broken again?
19:49:00 <mtaylor> nope
19:49:37 <LinuxJedi> ok then
19:49:39 <LinuxJedi> #endmeeting