15:01:21 #startmeeting XenAPI 15:01:21 Meeting started Wed Mar 19 15:01:21 2014 UTC and is due to finish in 60 minutes. The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:24 o/ 15:01:25 The meeting name has been set to 'xenapi' 15:01:28 howdy people 15:01:30 hows things? 15:01:32 Just me today again I think! 15:01:41 I'm lurking. 15:01:44 Well, I've got an orange and a can of diet coke 15:01:54 so that's got to be classified as "good" right? 15:02:03 yup 15:02:12 any specific topics? 15:02:22 its almost time to gather summit like thoughts 15:02:22 CI is broken :( 15:02:30 oh yeah 15:02:33 #topic CI 15:02:49 the CI died :( nasty new features 15:02:57 I'm going to blame Xavier Queralt for fixing a bug in tempest 15:03:02 https://review.openstack.org/#/c/78194/ 15:03:07 so, should we look at getting my change in htere? 15:03:16 Broke XenAPI and we urgently need John's change and mine 15:03:26 can we please exclude that test for now? 15:03:31 while we get this fixed? 15:03:32 #link https://review.openstack.org/#/c/81497/1 15:03:38 I suppose we can now we know what's wrong 15:03:42 let me exclude it now... hang on... 15:04:02 you have tabs in there by the way 15:04:20 I just uploaded one without the tabs?? 15:04:22 damn :P 15:05:15 excluded. 15:05:19 Next tempest runs won't try it 15:05:38 cool 15:05:41 I suppose I should re-run the failed jobs 15:05:45 yeah 15:05:50 What do you think we should do there? 15:05:59 re-running failed jobs will push them all on the queue and slow down results for new jobs 15:06:05 until the queue is drained 15:06:30 sweet 15:06:38 so… fixing it 15:06:39 so should I re-run them and delay results for new tests? 15:06:46 seems like its those two changes 15:07:10 yes 15:07:17 what's you change? 15:07:18 lets link them here 15:07:23 oh - I linked to patch #1 of mine 15:07:27 that's why you saw tabs :) 15:07:36 #link https://review.openstack.org/#/c/81497/5 15:07:50 #link https://review.openstack.org/#/c/81252/ 15:08:01 johnthetubaguy: can you update yours to say partial-bug rather than closes-bug? 15:08:23 erm, well it closes the bug from a nova perspective, probably just need to reword the bug 15:08:39 I've added devstack to the list 15:08:44 in the bug 15:09:08 yeah, OK, so its closes-bug then? from a nova point of view? 15:09:54 yes, but closes-bug assumes that it's the only part of the bug 15:09:56 which it isn't 15:10:02 which is why both changes need partial-bug 15:10:29 erm… but it would be close form Nova, its independent for each project, so it leaves devstack open till it closes 15:10:42 there isn't another nova patch, as far as we know, is what I mean 15:10:55 Oh, ok. I thought that closes-bug be the whole bug 15:11:12 only on a per project, seems independent 15:11:20 fine 15:11:24 cool 15:11:51 Then can you remove your -1 and poke Matt until he agrees so we can get it in? 15:12:27 I can try, will ask the other cores over here to take a look at least 15:12:38 I meant agrees to remove his -1 15:12:47 right 15:12:59 so, we should be good, assuming that all works 15:13:01 ? 15:13:24 Well I've already excluded the test 15:13:30 so that should mean we're ok from that perspective 15:13:57 true true 15:15:23 I've now re-queued all of the failed tests in the last 24 hours 15:15:45 nice, thank you 15:15:48 any more on CI? 15:16:17 nah guess not 15:16:34 #topic Juno Summit 15:17:22 anyone got things to raise this time? 15:17:31 we should start and etherpad again... 15:17:34 no - too early 15:17:50 too many other things going on ATM - can't think about Juno! 15:17:58 OK 15:18:15 #topic Open Discussion 15:18:18 Any other issues? 15:18:25 any rc1 looking bugs? 15:18:32 no, don't think so 15:18:38 I think we're generally good ATM 15:19:33 likewise from what I can see at the moment 15:19:57 are we all done then? 15:20:17 think so 15:20:28 oh 15:20:33 will probably have to rebuild CI soon 15:20:38 why is that? 15:20:42 I'd built it with the smallest flavor thinking "it's not doing much" 15:20:48 ah 15:20:49 but it's run out of the 512M ram ;) 15:20:57 heavily into swap now 15:21:02 is it standard flavor? 15:21:18 don't remember 15:21:28 snapshot then rebuild, or resize it if its standard 15:21:39 its standard if its 512, so just resize it 15:22:07 seems that nodepool is using 50% of the memory(!) pretty huge 15:22:14 wow 15:22:19 I've got a script that'll rebuild it 15:22:25 so the only thing we'd lose is queue state 15:22:32 unless I update it to copy the DB cross rebuilds 15:22:48 in which case we'd just lose gerrit stream watching for 30 minutes or so 15:22:48 yeah, but snapshot then rebuild and you don't loose the queue right? 15:22:51 or just resize 15:23:11 anyways, good to test your script! 15:23:25 assuming its in a git repo somewhere 15:23:25 dunno what I'll do - I'll figure it out. 15:23:34 cool, any more for any more? 15:23:51 (note resize can be quite slow) 15:24:18 thanks bob 15:24:22 #endmeeting