15:00:13 #startmeeting XenAPI 15:00:14 Meeting started Wed May 29 15:00:13 2013 UTC. The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:17 The meeting name has been set to 'xenapi' 15:00:24 hi 15:00:30 hands up for the XenAPI meeting? 15:01:22 o/ 15:01:58 and matelakat too :) 15:01:58 hi 15:02:12 cool, hello 15:02:35 #topic actions from last meeting 15:02:44 matelakat: how did that documenting go? 15:03:12 As I said, it is a low priority, haven't even touched it. 15:03:24 *grin* 15:03:31 OK, lets leave that off the actions for next week, its got boring 15:03:37 focusing on quantum, and saying hello to smokestack 15:03:43 #topic blueprints 15:03:55 so I have made progress with xenapi-server-log 15:04:09 assuming someone configures the logging correctly 15:04:13 I can now read the logs 15:04:20 you mean with the xenstore key? 15:04:34 #link https://blueprints.launchpad.net/nova/+spec/xenapi-server-log 15:04:42 well, its needs more than the xenstore key, but yes 15:05:06 #link https://review.openstack.org/#/c/30301/ 15:05:28 Ah - this was WIP 15:05:29 got a few other bits till its finished, but the core proof of concept seems OK 15:05:31 is it still WIP? 15:05:42 or are you raedy for someone to look at it? 15:05:42 nope, its up for review 15:05:46 okay cool 15:05:51 I'll have a butchers :) 15:05:54 cool 15:06:13 its not that sophisticated, but its a step forward 15:06:22 I think we need to worry about deleting old logs too 15:06:41 that probably shouldn't be the job of logrotate, but I can't quite decide 15:06:57 anyhow, its baby steps forward 15:07:02 sounds good to me 15:07:26 so, next one I wanted to touch on was devstack refactor 15:07:35 #link https://blueprints.launchpad.net/devstack/+spec/xenapi-devstack-cleanup 15:07:40 matelakat: how is that going? 15:08:10 At the moment a quantum patch is waiting, after that, I would like to push the network cleanup. 15:08:20 We could discuss what we want in that. 15:08:33 remove internal xapi interface 15:08:41 sensible defaults 15:08:42 yes, I had some people talking about that inside rax 15:09:00 Oh, is someone using that if? 15:09:04 so, remove that guest install network thing, yes please 15:09:20 guest install network? 15:09:30 that internal xapi interface 15:09:32 I am not sure if we are speaking about the same stuff. 15:09:35 it has many names 15:09:52 current eth0 on bridge xapi 15:09:57 Another job would be to modify how the vm is built. 15:10:13 lets just get the network decided I think 15:10:16 first 15:10:18 y 15:10:24 so default config, what you thinking? 15:10:25 But that will be another change. 15:10:41 Default config - let's talk about that 15:10:52 I recon something like eth0 = management, eth1 = data, eth2 = public 15:10:58 that is the domU 15:11:01 Let's look at the doc. 15:11:08 doc? 15:11:22 my goal is to align devstack with the official docs 15:11:26 you know, the diagram. 15:11:43 we probably need to change that now though 15:11:50 IOW make devstack as close to what we'd recommend people deploying 15:11:52 anyways, let me find a link 15:11:59 #link http://docs.openstack.org/grizzly/openstack-compute/install/apt/content/introduction-to-xen.html#xenapi-deployment-architecture 15:12:10 BobBall: yes, but it needs to be simple no change for devs 15:12:12 what is IOW Bob? 15:12:31 matelakat: cool that looks good 15:12:44 I think managment network should be dhcp (i.e. home router) 15:12:49 yes. 15:12:59 then the tenant and public can default to host local private networks? 15:13:01 IOW = in other words 15:13:23 obviously you could create VLANS, etc, if you wish to do multi box setup 15:13:41 does that sound like what you were thinking? 15:13:50 I would leave it as an exercise for the user. 15:14:19 I meant the VLAN and the physical game. 15:14:21 erm, would be good to create the default host local networks auto-magically though? 15:14:22 I agree - don't add complexity to devstack... we can get it to install on whateverthehostisrunning 15:14:29 host-local sure, yes 15:14:30 ah right, absolutaly, no VLAN creation 15:14:48 The change that has been accepted is already doing this host local stuff. 15:15:01 the other Ubuntu installer stuff, that should probably default to eth0 dhcp to match the above 15:15:14 y 15:15:15 then autodetect the management ip address on eth0 15:15:21 y 15:15:38 I would just assume a default install of XS I guess (plus XD optimisations / EXT SR) 15:15:51 As documented. 15:15:53 idd 15:15:54 sounds like we agree on the network defaults? 15:16:13 Static IP could be another job. 15:16:32 what you mean? make it work with a static IP? 15:16:33 for now, let's assume dhcp on MGT network. 15:16:41 +1 for dhcp for now 15:16:44 yes, make it work without DHCP 15:17:02 Okay, so that's an agreement. 15:17:12 yeah, lets ignore that for now, we need to worry about proxies too in the complex case 15:17:13 Although the quantum case would need another diagram. 15:17:22 yes, that is worth doing 15:17:38 #action: need new doc diagram for quantum setup 15:17:50 matelakat: you mentioned ubuntu install changes? 15:18:20 I would like to see the snapshotted VM not connected to any networks. 15:18:36 Other than that: always update boot parameters 15:18:42 in what sense? for the install? 15:18:45 I meant kernel parameters. 15:19:08 At the moment, we are creating a VM with 4 interfaces, and preseed that VM 15:19:14 And than snap it. 15:19:16 OFFLINE=true gets close to that in localrc in the domU I think, for refresh 15:19:32 OFFLINE=true???? 15:19:34 ah, hang on, not sure I get what you mean 15:19:52 OFFLINE=true stops the git pulls and apt-get updates, etc 15:19:53 I've not seen that one before :P 15:19:58 ahhh 15:20:16 create a VM with one interface, preseed it -> remove the interface from the VM -> snap it 15:20:56 Goal: You can change the network configuration without cleaning up the templates. 15:21:07 Makes sense? 15:21:09 ah, yes, good point 15:21:19 very much to me too 15:21:23 Okay. 15:21:28 that would really help the retry loop 15:21:32 I am not sure, if it is all one change. 15:21:43 We'll see how big it is. 15:21:59 I lost intrested half way through adding those snapshots after getting the test times down to something I could bare 15:22:18 cool, so that sounds like pleanty 15:22:32 and that should leave us in a good place for Havana I guess? 15:22:42 Now, file some actions please, I like to see the bot doing its job. 15:22:57 lol, probably best to update the blueprint though? 15:23:02 sure. 15:23:30 Let me check my trello board. 15:23:47 Oh, separate volume for cinder in devstack 15:23:59 I just updated the BP 15:24:03 #link √ 15:24:05 Okay. 15:24:07 oops 15:24:12 #link https://blueprints.launchpad.net/devstack/+spec/xenapi-devstack-cleanup 15:24:30 So, one more thing that I have is: separate vhd for cinder volumes 15:24:33 Work items: 15:24:33 Get rid of VLAN configuration: DONE 15:24:33 Add proxy settings for Ubuntu install: DONE 15:24:33 Better network defaults: TODO 15:24:33 Reconfigure networking without Ubuntu VM re-install: TODO 15:24:34 Separate Hypervisor setup: TODO 15:24:56 matelakat: sure, but is that critical? 15:25:24 I would like to see that, because with the loopback device, you get kernel lockups. 15:25:38 ah, yes, that old fella 15:25:41 Which is not really a good experiment. 15:25:55 s/experiment/experience/g 15:26:25 cool 15:26:30 so lets move on to Quantum 15:26:34 Okay, move. 15:26:36 I saw L2 got into master 15:26:42 hows DHCP? 15:26:46 That's really good thing. 15:26:55 :) 15:27:00 We have issues with Quantum with oslo.config 15:27:19 That was a separate issue changing [OVS] -> [ovs] 15:27:36 oh, thats not specific to XenAPI, but yes 15:27:45 So that was sort of blocking me 15:28:04 Apart from that, a ci job is here: 15:28:20 #link https://github.com/citrix-openstack/qa/blob/master/xenserver-quantum-devstack.sh 15:28:37 Also blocked by a stupid commit I made :) 15:28:50 I didn't say that. 15:29:01 oh 15:29:03 but you thought it! :D 15:29:18 Bob's change just highlighted some other issues, but he likes to be punished by himself. 15:29:26 lol 15:29:39 Just to fill John in on the details... 15:29:40 OK, so you got DHCP working? 15:29:52 define "working" 15:30:05 instances get IP addresses from DHCP? 15:30:10 y 15:30:19 cool, whats broken? 15:30:31 devstack had some libvirt specific variables which were used in common code - I removed the libvirt specific variables and apparently committed it without testing it (although I know I tested something!) - so the upshot is that devstack is currently broken for XenServer and all non-libvirt hypervisors 15:30:43 oops 15:30:51 #link https://review.openstack.org/30703 15:30:58 I will not update my repo today then... 15:31:19 Update it. 15:32:04 so, I hear OVS plugin is getting deprecated 15:32:20 do we know what the plan is getting XCP working with the new one? 15:32:29 Which is the new one? 15:32:45 I need some details. 15:33:00 Was it on the ML ? 15:33:14 it was hinted to on the ML 15:33:19 let me check 15:33:38 I wouldn't care about the future plans. 15:33:41 its called ML2 15:33:44 At the moment. 15:34:03 ML2 is my second revision - It's not even born. 15:34:12 "However - do you have any idea about how this kind of feature will play with ML2 and deprecation of OVS plugin?" 15:34:23 was in a thread on VXLAN 15:34:56 Ah, how good is that. So that's why quantum folks accepted the L2 patch. 15:35:00 :-) 15:35:11 https://blueprints.launchpad.net/quantum/+spec/modular-l2 15:35:16 haha 15:36:04 Let's keep an eye on it. 15:36:08 Thanks John. 15:36:25 I need some time to parse that change. 15:36:35 well seems like its the new thing, I would ask salvatore 15:37:18 it may require almost zero changes 15:37:19 anyways 15:37:40 #topic Docs 15:37:47 any updated for Xen Doc Day yesterday? 15:37:51 nothing from me 15:38:11 not from me either 15:38:16 #link https://review.openstack.org/#/c/20105/9/quantum/plugins/ml2/README: It currently works with the existing openvswitch, linuxbridge, and hyperv L2 15:38:18 but what would you hope we could do for the xen doc day? 15:38:29 .. agents 15:38:44 So this ML2 seems to be higher up in the hierarchy. 15:38:46 so ML2 is on top of OVS? 15:38:52 ah, I keep meaning to join in that effort and work on XS OS docs 15:39:09 I think ML2 is the new things to configure OVS rather than the current OVS plugin 15:39:27 Okay, so as long as Agent stays, we don't care. 15:40:17 hopefully 15:41:20 #topic Bugs and QA 15:41:37 pass 15:41:58 So the biggest one is the devstack bug 15:42:25 Ah QA 15:42:48 I am trying to reproduce the Smoke things 15:42:56 And I am at around 80% 15:43:18 namely here: #link https://github.com/dprince/firestack/blob/master/example_xen.bash#L71 15:43:36 Who's gonna pick up the devstack one? 15:44:00 which devstack one? 15:44:03 the one that I introduced? 15:44:06 I would like to get quantum and smoke done this week. 15:44:25 Yes, let's call it Bob-Bug-2013/00000001 15:44:37 Wow - that's kind. suggesting that it's the first bug. 15:44:40 So that we have enough digits for the year. 15:45:01 My issue with me looking at it is the next few days are likely to be busy 15:45:14 but I can say I'll take it 15:45:19 I'll see what I can do tomorrow 15:45:40 We can try to do some pair programming 15:46:18 Sure - although I might fix it tomorrow morning before you get in the office ;) 15:46:34 well, that sounds good 15:46:37 suggests Bob-Bug-2013/00000002 15:46:45 how is smokestack then? 15:47:46 Let's say environment setup phase. 15:48:22 learning - from my side. 15:48:44 All we need is to be able to fix any issues in puppet manifests at the moment. 15:49:09 And I would say we are not really far from being able to do that (hack -> test) cycle. 15:49:25 As I said, I would like to get it done this week. 15:49:39 Any other Q? 15:50:48 nope 15:51:18 are we done with the meeting now? 15:51:40 John has disappeared. 15:51:45 What a chairman! 15:51:54 and now we can't stop the meeting 15:52:00 Oh Bob 15:52:12 that means we have to keep going until John is back 15:52:16 It seems, that we have to stay here till the end of the time. 15:52:18 he is here 15:52:19 sorry 15:52:23 Oh. 15:52:36 one more thing 15:52:43 #topic open discussion 15:52:44 Good old SJ. 15:53:01 anything around diskimage-builder? 15:53:05 anyone looking at that 15:53:13 Not really. 15:53:14 fraid not 15:53:16 I noticed it was going for incubation / oslo inclusion 15:53:18 OK 15:53:28 I guess it doesn't do our style VHD 15:53:48 What is the exact use-case for that? 15:54:06 hi, folks, how about https://etherpad.openstack.org/linked-template-image , any thoughts? 15:54:12 I've gotta run - sorry guys - was expecting us to be done by now! Mate, will be back on later if you want to email me. 15:54:47 matelakat: not sure 15:54:50 DuncanT: around? 15:55:09 zhiyan, is it about XenAPI? 15:55:53 ok, so we are done with XenAPI I guess 15:55:57 matelakat: no, just about cinder requirement/dependency: Attaching a volume to a host 15:56:00 johnthetubaguy: Is it some debootstrap thingie? 15:56:03 sorry got distracted at the end 15:56:07 matelakat: yep 15:56:18 I think its about bootstrapping OpenStack 15:56:23 zhiyan: Give it 5 minutes, we aren't due to start yet! 15:56:25 so building images, and everything 15:56:29 zhiyan: I guess cinder meeting is the next, within few minutes. 15:56:38 yup, we almost done here 15:56:44 matelatat: any thing else? 15:56:45 DuncanT: oh, sorry, :) 15:56:53 Okay, let's give the room to the cinder folks. 15:56:55 #endmeeting