15:00:16 #startmeeting XenAPI 15:00:17 Meeting started Wed Apr 29 15:00:16 2015 UTC and is due to finish in 60 minutes. The chair is BobBall. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:21 The meeting name has been set to 'xenapi' 15:00:24 o/ 15:00:27 Good morning! 15:00:30 Or afternoon 15:00:38 Hi johnthetubaguy 15:00:47 How are things? 15:00:51 Busier now I imagine! 15:01:19 #topic CI 15:01:24 yeah, busy busy 15:01:34 So the main issue with the CI this week ishas been that the gerrit stream keeps getting reset 15:01:55 it seems that zuul has also been suffering from it (periods of up to 10 minutes where we can't contact review.openstack.org) 15:02:16 oh yeah, I heard about some of that in -infra 15:02:21 but the OSCI didn't restart as nicely as Zuul 15:02:30 ah, doh 15:02:35 I've now added a cronjob to ensure it's running every 30 minutes 15:02:36 simplest fix 15:02:52 Medium term I still plan to move to the zuul+jenkins way of doing things 15:03:00 so didn't want to invest in a more complicated solution 15:03:01 yeah, that sounds like a good plan 15:03:19 Apart from that pass rates look good when we're running 15:03:23 so I'm going to re-enable voting 15:03:34 but restrict tests to just Nova 15:03:50 since I haven't asked for voting permissions to be added to the other repos (devstack/tempest) 15:04:14 I think that covers that really 15:04:23 the libvirt+xen CI is an interesting one too 15:04:24 :) 15:04:29 oh, one sec 15:04:37 http://jenkins.openstack.xenproject.org/job/dsvm-tempest-xen/buildTimeTrend 15:04:41 humz? 15:04:54 I think turbo hipster folks are running zuul, not sure what they can share 15:04:59 but its worth exploring that 15:05:12 Well I'm running zuul for libvirt+xen CI 15:05:31 I do want to investigate a combined zuul for several 3rd party CIs where we can 15:05:32 ah, cool, so step one already done 15:05:50 so my plan is to move the XenServer CI to share the jenkins+zuul with libvirt+xen 15:06:03 and from there it's a simple step to integrate with or integrate other peoples 3rd party CIs 15:06:24 the only issue is access as several CIs are running within a firewall rather than in a public cloud like the XS and libvirt/xen CIs 15:06:42 -only+main :) 15:06:51 Anyway; pass rate for libvirt+xen is looking good too. 15:07:09 The jobs you can see there have mostly suffered from common problems -infra have also been struggling with 15:07:35 for example the period 24 hours agoish where the RAX mirror was broken 15:07:50 good signs 15:08:00 are there any major bloopers left? 15:08:13 Next step is I'm planning to write a simple tool to analyse the results and compare to see which jobs we fail that jenkins passed 15:08:53 None of the tools I'm aware of currently do quite what we need 15:09:03 basically to investigate disagreements between the systems 15:09:07 elastaicrecheck is good, but yeah, that could be not quite what you want 15:09:26 We don't have a logserver that can be used to run elasticrecheck 15:09:28 actually it might be able to compare tempest failures, but it takes quite a bit of infrastructurure 15:09:32 our logs are stored in swift for cost reasons 15:09:50 That to :) 15:10:07 Anyway - a simple script that pulls results from gerrit + a jenkins server should be straight forward to write 15:10:11 so I'll have a bash at that soon 15:10:20 so I can convince myself mostly that the results we're seeing are god. 15:10:23 good* 15:10:48 A quick check of the results doesn't show any tempest jobs that fail more often than others, so if we do have an issue it's a generic libvirt+xen one 15:11:07 I think that's it for CI 15:11:13 unless you have any more johnthetubaguy ? 15:11:22 nothing from me, thats sounds good 15:11:39 Oh - one more - we're likely to have a meeting next week or the week after to explain how the CI is set up 15:12:05 basically just following asselin's puppet scripts with some tweaks and hacks that I'm going to upstream at some point :) 15:13:01 Think that's it. 15:13:11 #topic XenServer Dundee 15:13:21 dundee? 15:13:24 next version? 15:13:28 Just to let you know that an alpha for "Dundee" has been released. 15:13:46 This is an Open Source XenServer release 15:13:53 based on the latest trunk code 15:14:29 ah, centos7 15:14:30 and, for legal reasons, may not have any correspondance with the next Citrix XenServer release 15:14:41 python2.7 ? 15:14:42 e.g. features in this alpha may not be present in the next XenServer release ;) 15:14:45 Yes 15:15:09 ah, yeah, that old cookie, well thats probably accurate too, in general 15:15:24 yes 15:15:45 Anyway, the C7 work is definitely the biggest item in there 15:15:50 but I think it's also upgraded Xen 15:16:09 but still using the 3.10 64-bit kernel from 6.5 15:16:29 ah, cool 15:16:34 that makes sense 15:16:44 *nod* 15:16:53 Anyway, that's all for that from me. 15:16:58 #topic Recruiting 15:17:16 Going well - but again, if you know anyone in Nanjing who wants to work on OpenStack let me know. 15:17:25 That's all. 15:17:29 #topic AOB 15:17:35 Anything from you johnthetubaguy ? 15:17:44 Or anyone who has been lurking? 15:17:49 nothing really, liberty is open, I guess thats the big thing 15:18:01 did you get the help from our side on the CI yet? 15:18:08 I disabled the test 15:18:15 Yes, I probably should have talked more on that. 15:18:21 jg0 was ready to help 15:18:27 but I couldn't build a dev CI environment 15:18:44 as the -infra modules (specifically project-config) have evolved and our scripts aren't compatible now 15:19:02 I need to do a rebasing round to be able to deploy a dev CI for jg0 to investigat.e 15:19:19 But with summit prep that rebasing has taken a back seat :) 15:19:46 oh, we have mostly chosen the summit sessions now 15:19:59 did you need anything in the Nova design summit track? 15:19:59 Excellent 15:20:04 I was guessing no? 15:20:14 I'd say not this time, no. 15:20:22 We'll have a lot to ask / talk about next summit I'm sure. 15:20:33 https://etherpad.openstack.org/p/liberty-nova-summit-ideas 15:20:39 cools 15:20:49 oh, xenapi pool support 15:21:04 are we ready to kill that, seems to pop up now and again 15:21:19 I'm happy for it to be removed yees 15:21:35 OK, maybe its a good on boarding task for new devs 15:21:50 quite possibly :) 15:22:02 cools, nothing more comes to mind right now 15:22:10 OK great 15:22:29 Next meeting is week before summit and one then week after summit 15:22:35 #topic Next Meeting 15:22:54 I'm assuming we won't need both as we'll be talking lots at the summit 15:22:57 preference for one or the other? 15:23:13 oh, good question 15:23:31 I should be alive for both of those, in theory 15:23:44 possibly post summit would be better? 15:23:50 OK - let's aim for post summit 15:24:04 cool, thanks BobBall 15:24:05 Oh drat 15:24:07 No, I can't 15:24:13 I'll be in Nanjing week after summit. 15:24:18 hehe, the one before then, thats fine 15:24:18 Let's shoot for pre-summit :) 15:24:35 Next meeting 13th May then! 15:24:43 Thanks johnthetubaguy 15:24:50 catch you later! 15:25:16 #endmeeting