15:03:56 #startmeeting XenAPI 15:03:57 Meeting started Wed Nov 19 15:03:56 2014 UTC and is due to finish in 60 minutes. The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:58 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:04:00 The meeting name has been set to 'xenapi' 15:04:09 BobBall: hows things going? 15:04:26 Not too bad 15:04:28 Not too bad at all 15:04:39 #topic XenServer CI 15:04:47 Oh yes - first subject of the day :) 15:04:49 CI is going well 15:04:55 cool 15:04:55 Good passes recently 15:05:00 https://review.openstack.org/#/c/133975/ 15:05:06 I know there were some snapshot issues matel was digging on 15:05:15 that's the test change I've been rechecking 15:05:35 no snapshot issues in the CI 15:05:40 is that a seperate subject? 15:05:51 or is that Matel's neutron CI you're talking about? 15:06:27 ah, it could well be 15:06:55 I don't remember the details, just some 'bad' snapshots were created 15:07:20 Speaking of matel - here he is 15:07:31 BobBall: thats quite a lot of passes on that patch 15:07:36 What are the CI snapshot issues you've seen? :) 15:07:38 maybe its worth a whirl? 15:07:41 johnthetubaguy: not enough for my liking :) 15:07:46 lol, OK 15:08:13 So far only 8 passes. If the fail rate was 10% then we still probably wouldn't have hit it 15:08:19 yet a 10% fail rate is huge 15:08:46 sorry guys, what's the topic? 15:08:59 topic is CI 15:09:07 15:05 < johnthetubaguy> I know there were some snapshot issues matel was digging on 15:09:11 just curious about the snapshot issues you saw the other day? 15:09:14 I was trying to understand what they were 15:10:06 Ah, I re-generated the image later, and haven't looked at it since then. 15:10:16 Gimme a sec, let me see how bad is the situation 15:10:53 oh I see 15:11:02 it was snapshot issues with RAX in the image generatio 15:11:13 not snapshot issues seen in tempest failures? 15:11:15 yeah, upstream code bug 15:11:29 need to put the fix up, but it should be deployed everywhere now 15:11:37 I suspect it confused nodepool a bit 15:11:43 yeah 15:11:55 it will have tried to use a snapshot that wasn't actually a success 15:11:58 matel was working on us using the latest nodepool code 15:12:09 because there are a bunch of error handling improvements 15:12:15 nova would delete it, but not if you delete the instance first, :( 15:12:32 THe problem happened when I used nodepool to bake an image and launch instances of it. 15:13:05 I see 15:13:06 No stuck/building instances now. 15:13:06 fair enough 15:13:14 Joy. 15:13:21 So things seem to be OK ATM 15:13:26 yes 15:13:31 Even better. 15:13:33 cool 15:13:37 sounds like we fixed it 15:13:40 awesomeness 15:13:45 any more on the CI? 15:14:02 matel has been working on something 15:14:14 I am looking at using neutron 15:14:55 Using the next XS candidate seems to work - as it has a newer Openvswitch 15:15:09 Altough I still haven't passed all the smoke tests 15:15:20 Again, they are failing around volumes. 15:15:30 ..And securoty groups 15:15:46 So that's what I'm working on. 15:16:00 ... And I documented the osci deployment 15:16:02 Some changes were needed to devstack etc right? 15:16:07 all upstream now? 15:16:29 all good stuff 15:16:41 With the actual tips, it's not working. 15:17:08 BobBall: I don't quite get what you mean. 15:17:27 the changes needed to get neutron working 15:17:30 I thought there were some? 15:17:42 There were, they are merged AFAIK 15:17:50 But it's still not passing. 15:18:07 Let me look at the reviewboard 15:18:26 Yes, my devstack changes have been approves 15:18:37 Ah ok good 15:18:39 so nothing outstanding 15:18:46 just us needing to continue to investigate 15:18:49 SO it means, that if you deploy a neutron from upstream, you should be able to contribute to the investigation 15:18:50 cool, its a good problem to look into 15:18:54 Yes, exactly 15:19:06 looking like we might kill off nova-network in lima 15:19:15 #topic Open Discussion 15:19:25 so, any more things to talk about? 15:19:43 Not from my side 15:19:51 kill off? 15:19:59 surely the plan was to deprecate for at least 1 release 15:20:10 is the plan to formally deprecate for Kilo then and remvoe in Lima? 15:20:34 if all goes to plan, possibly, although it might be a release later than all that 15:21:16 yes 15:21:19 that might make more sense 15:21:27 actually getting rid of nova-network is going to be hard work :) 15:21:33 But fair enough 15:21:37 we'll just see where it goes 15:21:56 I'm aiming to have our CI running on Neutron before the end of Kilo 15:22:05 yeah, sounds like a good plan 15:22:10 so doesn't matter much 15:22:10 oh 15:22:24 matel - do we want to ask about quark? 15:22:25 anyways, any more for any more? 15:22:39 quark - not yet. 15:22:49 Let's try to give a go to bare neutron 15:22:56 ..or 15:22:59 Okies 15:23:08 johnthetubaguy: does quark support security groups? 15:23:21 .. maybe that's a question 15:23:29 Indeed. 15:23:43 Does RAX offer security groups as a product offering? 15:24:21 not right now 15:24:39 it kinda upsets the scalability of OVS before you start worrying about other things 15:24:49 heh. Fun. 15:24:50 BobBall: but what problems are you seeing? 15:25:04 johnthetubaguy: all tests using secgroups are failing 15:25:14 it's more matel but I think it's that tempest tests security groups and they don't work with OVS plain 15:25:17 johnthetubaguy: I'll look at where the issue lies 15:25:51 hmm, OK 15:26:04 we don't use upstream ML2 OVS driver though 15:26:11 we use quark 15:26:19 which is quite a different beast 15:26:29 Indeed. Sorry, brb. 15:26:52 johnthetubaguy: I would like to use upsteram components 15:27:10 matel: agreed 15:27:13 johnthetubaguy: If something is not possible with them, maybe we should use quark as well 15:27:20 quark is open source, but its sure not upstream right now 15:27:24 But give it a first go. 15:27:35 Is it owned by OS? 15:27:42 or is it a rackerlabs projects? 15:27:43 yeah, quark doesn't support security groups yet, so its not really the right answer for this either 15:27:57 I don't know for sure 15:28:16 tbh, I'm afraid that I'm gonna run into some serious issues there, but that's just my feeling. 15:28:33 I hope I'll be more clever next week. 15:28:57 Ah, johnthetubaguy. 15:29:15 Could you take a look at: https://github.com/citrix-openstack/install-nodepool/blob/2014-11/README.md 15:29:16 back 15:29:25 well, that stuff is confusing, getting something working without security groups will be a cool think anyways 15:29:36 Just a quick read, to make sure it makes sense. 15:29:57 OK, I'm on it. 15:30:03 matel: it looks very close to what I did when I tried to set the thing up 15:30:11 Yeah - we can have an exclusion list for now until we figure out how to do security groups with OVS 15:30:18 matel: I will try get someone to help out with that 15:30:43 johnthetubaguy: do you need help to read? 15:30:56 yeah 15:31:07 Oh, I didn't know that. 15:31:17 well, I need to find some time from somewhere 15:31:32 aye 15:32:00 ok, I'm done for today. 15:32:04 As am I 15:32:15 cools 15:32:16 thanks all 15:32:19 #endmeeting