15:04:03 #startmeeting oVirt Weekly Sync 15:04:03 Meeting started Wed Mar 26 15:04:03 2014 UTC. The chair is doron. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:04:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:04:46 * bkp here 15:04:49 #topic Agenda and roll Call 15:04:50 #info infra update 15:04:52 #info 3.3 updates 15:04:53 #info 3.4 status 15:04:55 #innfo 3.5 planning 15:04:56 #info conferences and workshops 15:04:58 #info other topics 15:05:20 #info this week the meeting is 1 hour later in US due to DST. 15:05:25 * sbonazzo here 15:05:33 I suggest we start 15:05:46 #topic infra update 15:05:49 orc_orc: here? 15:06:22 dcaro: here? 15:06:34 doron: yep 15:06:47 dcaro: can you give us some updates on ovirt infra? 15:07:40 doron: This week we have started adding slaves from openstack os1 cloud, also added the update_tracker hook to all the projects on gerrit, so you'll se now bugs updated for all the projects 15:08:49 #info ifra updates: Jenkins got new slaves from OS1 cloud. update_tracker hook added to all the projects on gerrit, so bugs are updates in all projects. 15:08:52 dcaro: thanks 15:08:56 moving on 15:09:04 #topic 3.3 updates 15:09:16 sbonazzo: anything relevant for 3.3? 15:09:40 doron: started preparing 3.3.5 release notes page for upcoming 3.3.5 RC 15:10:06 doron: scheduled for 2014-04-02 15:10:23 doron: no blockers for 3.3.5 up to now 15:10:39 #info oVirt 3.3.5 RC planned for April 2nd. Release notes preparation started. 15:10:44 sbonazzo: thanks 15:10:50 let's move to 3.4 15:10:56 #topic 3.4 status 15:11:03 sbonazzo: 3.4 status? 15:11:14 doron: 3.4.0 is pending final acceptance tests on node and vdsm 15:11:24 fabian_a: here? 15:11:25 doron once we have test result we can release it 15:11:31 fabiand: here? 15:11:41 * fabiand is here! 15:12:00 so 15:12:03 fabiand: do we have the ability to install the new node somewhere and make sure vdsm is running?? 15:12:28 doron, I tried it with my engine, but it is to old 15:12:30 fabiand: this should help sbonazzo to release 3.4 IIUC. 15:12:39 Anyone who was got a recent engine - at best 3.4. should be able to test it .. 15:12:51 fabiand: unsure we even need an engine 15:12:57 It's a bit far off node's core, so I'd really appreciate if Engine or vdsm people could look into it 15:13:09 if vdsm is up and running it means we're good. 15:13:11 doron, well, it's about vdsm not starting .. 15:13:12 am I wrong? 15:13:18 fabiand: indeed. 15:13:24 I am not sure if this is only the case after the registration .. 15:13:43 fabiand: IIRC the issue is about logging 15:14:00 so if we have log files and vdsm is up we're good. am I wrong? 15:14:02 doron, if it's only about vdsm beeing up, then I can say that it is up and running after a normal installation 15:14:15 danken: here? 15:14:25 fabiand: thanks. 15:14:29 probably - but as we couldn't test the whole functionality because of this issue, it can still be that other issues are hidden 15:15:05 fabiand: we may always have other issues. but this one is resolved if vdsm is running and logging. 15:15:14 doron, the log files, which were previously missing are now there 15:15:25 ok .. 15:15:33 and all log files contain data, except the metadata logfile 15:15:53 fabiand: sounds good to me. 15:15:57 to me too. 15:15:58 sbonazzo: are yo uok with it? 15:16:22 doron: well, release criteria says MUST: ovirt-node full cycle (register, approve and running VM, reboot and verify things still work) 15:16:41 doron: so maybe a bit more testing should be done 15:16:50 sbonazzo: can you prepare a vm with engine 3.4, and use it with fabiand's new node? 15:17:09 doron: I'm downloading the iso while we're speaking 15:17:22 doron: I'll try to test it after the meeting 15:17:27 sbonazzo: all you need is the engine. fabiand already has a node running 15:17:33 sbonazzo: very well. 15:17:42 doron: ok 15:17:53 doron, ah I will not be able to connect my node to sbonazzo's engine btw 15:18:07 bkp: please sync with sbonazzo. If all goes well we should be able to release 3.4 ga tomorrow morning. 15:18:19 fabiand: ? 15:18:19 doron: Acknowledged 15:18:43 fabiand: can you install a 3.4 engine in a vm next to your node? 15:18:55 ... 15:18:55 fabiand: Error: ".." is not a valid command. 15:18:59 sure I can 15:19:04 But I'd really love someone else to do this. 15:19:26 If no one is stepping up then I can do so. 15:19:27 fabiand: if you can provide sbonazzo access he may be able to help. 15:19:43 is this doeable? 15:19:59 http://www.virtualizationmatrix.com/ 15:20:39 fabiand: any other options? 15:20:54 is there a livecd with engine 3.4? 15:21:21 fabian being "up" is not enough 15:21:32 doron: Do we maybe need an update to the announcement email delaying the 3.4 GA date to past Monday? In addition to this mtg minutes even? 15:21:33 danken: why? 15:21:34 danken, thanks - that is what I initially said 15:21:35 dougsland tested that running VMs and hibernating them works 15:21:51 mskrivanek: I'll make a note of it here. 15:21:51 a non-douglas should repeat that before we go live 15:22:01 danken, +1 15:22:29 danken: the original issue was about log files. why does it need vm running? 15:22:34 btw dougsland did great work on nailing the issues down and fixing them. 15:22:40 there have been quite a few patches since the last beta 15:22:56 danken: so it's not about log files.... 15:22:57 doron: it's not only log files. also configuration files not persiste 15:23:03 doron, the log issue were just about the vdsm not being up 15:23:10 during the registration 15:23:21 we had issues with persist files when node get rebooted 15:23:27 dougsland: I know. but apparntly there was more than that. 15:23:54 doron, I know :P 15:24:03 anyway, so what we need now is someone to use fabiand's node t orun vms. 15:24:08 (ti run) 15:24:11 (to run) 15:24:35 I'd like to see that at least one more person can run VMs with vdsm-4.14.6 15:24:55 To me it seems as if we have a lack of testers. 15:24:55 danken: which is in the new node? 15:25:02 fabiand, not only me, all of us. 15:25:05 danken: do you mean in general or on node? 15:25:12 fabian, if you can try out migration it would be even better. since everything breaks migration. 15:25:23 The new node is: http://resources.ovirt.org/releases/3.4.0_pre/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34rc3.el6.iso 15:25:27 danken, ^^ 15:25:50 danken, fabiand doron talked with apahim he wants to help on testing. 15:25:51 sbonazzo: we had practically 0 beta testing of that ovirt-node. 15:26:05 I'd like it to be tested, a bit. 15:26:09 not much. 15:26:10 fabiand: I can't believe we're 208 in this chat room and nobody can test it, I'll give it a run between this evening and tomorrow morning 15:26:12 but a bit. 15:26:17 apahim, say hello to fabiand :) 15:26:21 dougsland: apahim very well. let's sync offline and update using the mailing list. 15:26:28 so 15:26:30 fabiand I hope everything go well and we can somehow release it tomorrow 15:26:30 apahim, heya - /me still remembers that evrsion check ;) 15:26:38 just to conclude 15:26:42 sbonazzo, I am also optimistic 15:26:49 sbonazzo: I'll try to help you 15:27:00 we'll try to conclude testing the new node today. 15:27:06 is all goes well we ga tomorrow. 15:27:11 sbonazzo: ok? 15:27:13 doron, +1 15:27:17 doron: +1 15:27:18 hey fabiand, dougsland o/ 15:27:27 dougsland: apahim sbonazzo thanks 15:27:48 #info pending verification today, 3.4 GA may be released tomorrow. 15:27:53 bkp ^^^^^^ 15:28:01 moving on 15:28:02 doron: Noted 15:28:09 #topic 3.5 planning 15:28:14 ok guys 15:28:26 I want to start reviewing the google doc for 3.5 planning 15:28:42 I'll start with gluster 15:28:59 who's here from gluster? 15:29:05 doron, hi 15:29:07 * fabiand wonders if we can't use Microsoft Office Live ... 15:29:17 hi sahina 15:29:35 you have 6 features listed 15:29:40 none with a devel owner. 15:29:48 doron, do we have any tentative dates for 3.5 feature freeze? 15:29:53 also 5 missing an ovirt bug. 15:30:07 sahina: currently May 1st feature freeze. 15:30:15 doron, will update these..the bug ids as well as devel owner.. 15:30:46 doron, hmm..in that case, we need to reconsider the list :). i'd assumed end may 15:30:57 sahina: very well. we'll do a separate review of each one next week. Please have it updated for next wek. 15:31:10 doron, sure. thanks 15:31:15 sahina: thanks. 15:31:42 #info gluster to update their 6 features for next week's review with owners and bug ID's. 15:31:48 next is infra 15:31:54 ybronhei: here? 15:32:02 doron: yes 15:32:12 ybronhei: 10 features? 15:32:28 doron: :) its not fully arranged yet 15:32:33 4 missing bugs, 6 missing owner 15:32:44 doron: and i need to add also foreman integration 15:32:51 ybronhei: is this your plan for 3.5 currently? 15:32:56 doron: yes yes, barak will arrange it better during next week 15:33:10 ybronhei: very well. 15:33:35 #info infra to update a missing feature, devel owners and bug id's. 15:33:48 doron: what else can i say ? .. the main features are aaa, json rpc, and foreman integration 15:33:48 sbonazzo: infra for 3.5? 15:33:56 sbonazzo: integration for 3.5? 15:34:04 doron: the others are quite small rfe s 15:34:17 ybronhei: we'll review each one next week. 15:34:22 doron: we've updated the planning data sheet 15:34:31 doron: ok 15:34:45 sbonazzo: yep, looks very good. 15:34:51 doron: we're going to work on having dwh, reports and websocket proxy installable on separate hosts 15:35:16 sbonazzo: so please be prepared to explain them for next week. 15:35:23 doron: ok 15:35:43 #info integration has 5 RFEs in place for 3.5. Will be reviewed next week. 15:35:54 who's here for network? 15:36:51 danken: any idea who can represent the network team? 15:37:24 I'll come back to network at the end. 15:37:31 moving to node. 15:37:38 fabiand: node's plans for 3.5? 15:37:52 hey 15:37:55 hey 15:38:08 Well, 15:38:22 we've got the long standing issue of reworking the registration 15:38:28 the Engine registration 15:38:49 The we are looking in adding hosted engine support, jboggs is working on this 15:38:49 fabiand: seems to be missing a devel owner? 15:39:04 not anymore :) 15:39:12 :) 15:39:23 fabiand: very well. so we'll review each one next week. 15:39:35 ack 15:40:00 #info node has 3 features in pace for 3.5. Will be reviewed next week. 15:40:14 moving next to sla 15:41:06 #info SLA to handle missing bugs, and devel owners for next week. Currently 10 RFE's in place for 3.5. 15:41:12 I wonder who handles sla... 15:41:15 moving on 15:41:19 storage 15:41:28 who's here for storage? 15:41:57 sgotliv: here? 15:42:54 I'll get back to storage soon 15:43:18 ecohen: here? 15:43:21 doron, yes. 15:43:37 ecohen: UX plans for 3.5? 15:43:48 doron, ux features for 3.5: (1) move to rest api (2) new look and feel (PatternFly adoption) 15:44:01 doron, they may be more, but much smaller, not sure if worth tracking in the google doc 15:44:18 ecohen: very well. up to you to decide if rfe or a nit. 15:44:25 doron, sure. 15:44:25 we'll review it next week. 15:44:44 #info ux has currently 2 rfe's in place for 3.5. we'lkl review them next week. 15:44:47 ecohen: thanks 15:44:52 doron, np 15:44:53 moving next to virt 15:44:58 I wonder who handles virt... 15:45:03 :) 15:45:08 we have a looong list 15:45:09 mskrivanek: virt plans for 35? 15:45:20 only 30 15:45:27 but most of them nits 15:45:34 3 "maybes" 15:45:59 mskrivanek: so you may want to leave only rfe's in and exclude nits? 15:46:03 ~2-3 we want to only start as they will span 2 releases 15:46:32 well I don't know, in 3.4 we included them all. They are proper RFEs all of them, just not much work 15:46:55 many were already in progress....or...the most natural explanation - we're just that good 15:46:56 mskrivanek: very well. it's your call. 15:46:57 :-D 15:47:08 just remember we track them all. 15:47:14 yes, it's fine 15:47:25 mskrivanek: also please make sure to update missing bz's and devel owners for next week. 15:47:26 missing bugs, working on that... 15:47:41 devel owners are mostly there 15:48:06 #info virt has currently ~30 features for 3.5. The list should be updated for na review next week with devel owners and missing bugs. 15:48:10 mskrivanek: thanks. 15:48:17 pps guys here? 15:48:24 sorry, I meant ppc 15:48:28 lbianc: here? 15:49:07 I got the PPC on line 92...feel free to elaborate in more detail 15:49:27 someone else here from ppc guys? 15:50:05 mskrivanek: can you mail them and ask for their plans in 3.5? 15:50:37 ok 15:50:43 mskrivanek: thanks 15:51:02 #info PPC folks should be contacted offline to get their plans. 15:51:13 anyone here for network or storage? 15:51:37 #info network team missing a representative. 15:51:43 #info storage team missing a representative. 15:52:22 So this is it currently. by next week I we should have everything in place to start work on 3.5 15:52:28 may the force be with us ;) 15:52:31 moving on 15:52:33 #topic conferences and workshops 15:52:40 bkp: updates? 15:52:53 Yes, I will be speaking at LinuxFest NorthWest on April 26-27 Topic: Building a community around mature software. 15:53:04 rkoch is organizing two oVirt workshops in Austria: Grazer Linuxtage in Graz April 4-5 and Linuxwochen Vienna, May 8-10. mskrivanek is finding someone in Brno to go over and help with the booth and workshop. 15:53:17 The weekly Call for Papers email will be reformatted: instead of one big, long list, I will post event-specific reminders on [users] as deadlines come up. 15:53:34 #info bkp ill have a session in LinuxFest NorthWest on April 26-27 Topic: Building a community around mature software. 15:53:39 That's the new news, unless anyone has something to add? 15:54:01 #info Rene Koch is organizing two oVirt workshops in Austria: Grazer Linuxtage in Graz April 4-5 and Linuxwochen Vienna, May 8-10. 15:54:39 #info weekly CFP updated to be reformatted. 15:54:43 bkp: thanks. 15:54:51 moving on 15:54:53 #topic other topics 15:55:04 Got a couple of things. 15:55:07 anyone wants to discuss / raise something? 15:55:11 Mirrors being set up (thanks dcaro!). We have one live with Duke University, and two more are coming soon, with about 6 in progress. 15:55:24 COOL 15:55:25 And Google Summer of Code proposal review now going on. Will coordinate on 4/1 15:55:41 #info oVirt Mirrors being set up (thanks dcaro!). We have one live with Duke University, and two more are coming soon, with about 6 in progress. 15:56:13 #info Google Summer of Code proposal review now going on. A meeting should take place on April 1st. 15:56:17 bkp: thanks 15:56:18 That's it from me. As an aside, already coordinated with sbonazzo on tomorrow's release. 15:56:19 anyone else? 15:56:39 going once? 15:57:10 going twice... 15:57:34 * YamakasY thinks he is going to use his serverroom as fridge 15:57:48 thanks everyone for joining! 15:57:49 #endmeeting