15:02:38 #startmeeting oVirt Weekly Sync 15:02:38 Meeting started Wed Dec 18 15:02:38 2013 UTC. The chair is doron. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:38 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:02:41 here 15:02:56 here 15:02:56 #topic Agenda and roll Call 15:02:58 #info conferences and workshops 15:02:59 #info 3.3 update releases 15:03:01 #info 3.4 progress 15:03:02 #info conferences and workshops 15:03:04 * lvernia here 15:03:04 #info infra update 15:03:05 #info other topics 15:03:22 ybronhei: here? 15:03:24 sgotliv here 15:03:42 sgotliv: hi 15:03:51 doron, hi 15:04:13 bkp: here? 15:04:26 Just walked in 15:04:32 bkp: gr8, hi 15:04:33 dneary is here too 15:04:40 is dave also around? 15:04:46 Yup 15:04:46 gr8 15:04:49 so let's start 15:04:53 * ofrenkel here 15:04:58 #topic conferences and workshops 15:04:59 Hi all 15:05:01 * dneary here 15:05:05 dneary: hi 15:05:09 updates? 15:05:15 * jb_netapp here 15:05:15 doron, Yes 15:05:41 doron, oVirt had a stand accepted for FOSDEM! We will have a table for demos, giveaways, and more 15:05:53 yey! 15:06:09 #info ovirt got a stand in FOSDEM. 15:06:09 Also, bkp and myself would like to have an oVirt meet-up on Saturday evening in Brussels 15:07:00 #info there's a plan for an ovirt meet-up on Saturday evening in Brussels 15:07:08 We also got the talk confirmations back from the virt & IaaS devroom - there are 6 oVirt presentations 15:07:26 #info 6 oVirt presentations were accepted for Virt & IaaS DevRoom 15:07:34 thanks ;) 15:07:56 anything you need /. want for the meetup? 15:08:03 #info The presentations cover oVirt & OpenStack integration, extending oVirt with plug-ins, APIs & hooks 15:08:08 doron, People! 15:08:10 Beer 15:08:13 Maybe food 15:08:28 * orc_orc here 15:08:32 So any action items here? 15:08:32 We'll firm it up in early January, I just want to get it on people's radar 15:08:59 very well. 15:09:24 post fosdem events? 15:09:49 #info Also, PPC porting, Neutron integration, and self-hosted engine 15:09:56 Hold on - still catching up 15:10:45 #info We will also participate in a cloud day in Ghent on Wednesday after FOSDEM (right after cfgmgmtcamp, in the same venue) 15:11:18 #info We will be looking for content on oVirt, OpenStack, Gluster, and other projects 15:11:58 We are still unsure whether we're organising an event the day before Monkigras in London, the Wednesday before FOSDEM 15:12:19 But if we do, we will look for someone to represent oVirt locally 15:12:32 bkp, Did I forget anything? 15:12:40 dneary: eta for that pre-fosdem? 15:12:53 doron, ASAP :-{ 15:13:07 We have an oVirt Board Meeting scheduled for Jan. 7, right after the holidays. 15:13:08 very well. 15:13:23 #info Virt Board Meeting scheduled for Jan. 7, 15:13:32 #info oVirt Board Meeting scheduled for Jan. 7, 15:13:51 anything else? 15:14:08 It will be a public meeting, details will be available on the users and board mailing lists. 15:14:40 #info oVirt Board Meeting details to be published in the users and board mailing lists. 15:14:41 I think that's everything! I'd like to thank everyone for their hospitality this week. 15:15:04 dneary: bkp thank you for your hard work. 15:15:04 And me as well. TLV has been awesome. 15:15:29 ok, next topic 15:15:41 #topic 3.3 update releases 15:15:49 sbonazzo: congrat's on the RC release 15:15:56 doron: thanks 15:16:10 #info 3.3.2 RC release earlier this week (Monday) 15:16:23 sbonazzo: updates? 15:16:32 doron: no new bugs for 3.3.2 for now 15:17:08 sbonazzo: very well. what's the plan for 3.3.2? can we release it this week? 15:17:34 I vote +1. 15:17:35 plan was to release it today, but maybe it's better to wait until friday at least 15:18:13 I'm for it, too. Had no issues with upgrade coming from 3.3.1 15:18:26 the fact that we have 3.3.3 candidate piling in should not matter. 15:18:29 Can we cleanup the repos prior to the release? 15:18:42 outi: what do you mean? 15:18:44 there are still old gluster rpms 15:19:00 all 3.4.0 and newer one is required 15:19:16 this could probably confuse people and only consuse precious diskspace 15:19:22 sbonazzo: can we make sure repos are cleaned? 15:19:44 sbonazzo: and who can do it? 15:19:59 doron: dcaro and knesenko can do it 15:20:10 imho, we don't need to carry these obsoleted packages, but there may be reasons to keep them though :) 15:20:24 doron: but I'm not sure on what has to be removed 15:20:48 outi: main reason for keeping old packages is allowing rollback if needed 15:20:57 sbonazzo: well, we can get just the latest rpms and archive everything else. 15:21:14 doron: that would break rollback 15:21:19 sbonazzo: so for at least one minor version we keep the archive 15:21:47 sbonazzo: but how many versions does the rollback need? 15:22:08 and maybe we can change it to refer to archive? 15:22:17 old rpms could be kept in the stable repo and only use uptodate ones in the version-named repos? 15:22:19 outi: it may be that people following older how-to's need such -- perhaps creatig a new archive with each release, and then pointing in to a master repository with links .. then when it is retired and removed, and a link no longer resolves, it disappears 15:22:36 and the repodate rebuild updates old stuff out 15:23:22 ok guys, I suggest we take this offline and discuss it in the list. 15:23:24 probaly out of scope to come to a final conclusion without some discussion on the mailing list 15:23:32 aye 15:23:35 ... what he said ^^ 15:23:35 orc_orc: Error: ".." is not a valid command. 15:23:39 ... what he said ^^ 15:24:06 well you potentially may upgrade from any 3.3.z to 3.3.2 15:24:07 outi: doron: we can release a new ovirt-release rpm, adding another repo(3.3.2) to stable 15:24:07 outi: doron: but this means that users may update ovirt-release before ovirt-engine-setup 15:24:08 outi: doron: and this change a bit the ususal upgrade path 15:24:28 outi: can you start a thread in the arch list for it? 15:25:00 doron: ok 15:25:25 #action outi to start a thread on proper repo handling in arch list. 15:25:28 thanks 15:25:39 sbonazzo: let's go back to 3.3.2 release 15:25:44 doron: since we're talking about repo 15:25:51 would you prefer releasing it on Friday or Thursday? 15:26:17 doron: I'm ok releasing also tomorrow if anybody vote against it 15:26:46 doron: and no blockers are opened tonight 15:27:17 #idea or mainly a concern- On Friday and later many folks will be in vacation. So I'd prefer to try and find issues before people are going away 15:27:21 orc_orc, I didn't know . started a bot command :) 15:27:30 dneary: nor I 15:27:33 it is a pest 15:27:56 well, I know from running into it, but it is only the bot here ;) 15:28:07 so any objections to releasing 3.3.2 tomorrow? 15:28:40 doron: +1 for tomorrow 15:29:12 danken: / others: any issues with releasing tomorrow? 15:29:27 I already voted +1... 15:29:44 very well then. 15:30:01 #agreed oVirt 3.3.2 to be release tomorrow. 15:30:05 yey! 15:30:13 (pending on sbonazzo getting all the rpms right.) 15:30:13 sbonazzo: anything else? 15:30:26 doron: about the repo cleaning, should we bump ovirt-release as said a few lines above? 15:31:09 sbonazzo: bump to what? 15:31:19 doron: options are 2 15:31:23 release-3.3.2? 15:31:39 doron: 1) just move rpms from updates-testing to stable and keep everything 15:32:16 doron: 2) keep stable as is, and add a line in ovirt.repo pointing to 3.3.2 release and prepare a new ovirt-release rpm for delivering it 15:32:40 sbonazzo: how will (2) effect rollback? 15:33:04 keeping stable and 3.3.2 both enabled by default in ovirt.repo will not affect rollback at all 15:33:35 is like haveing stable and updates-testing 15:33:59 Very well then. Please make sure to include it in your mail. 15:34:09 doron: ok 15:34:47 #ACTION release a new ovirt-release rpm enabling 3.3.2 new repository and stable as default 15:34:54 thanks 15:34:59 moving on 15:35:10 #topic 3.4 progress 15:35:25 sahina: hi 15:35:37 doron, hi 15:35:51 sahina: updates on gluster progress for 3.4? 15:36:23 doron, we have 1 done, 1 in progress (hope to make it) 15:36:52 doron, the monitoring feature - seems like most of the work is in writing nagios plugins 15:37:16 sahina: will you make it to the feature frees in Dec 31st? 15:37:28 (freeze) 15:37:58 doron, does feature freeze mean no new development or requirements freeze? 15:38:24 sahina: basically yes. we move to stabilization and bug fixing. 15:38:59 doron, in which case, we will drop the gluster volume monitoring feature from 3.4 15:40:07 sahina: no chance of having it in? 15:40:46 doron, we will try our best. it's a stretch goal considering next week lot of folks are on holiday 15:41:00 sahina: very well. 15:41:26 #info gluster team completed one task. 2 other in progress. Monitoring as risk. 15:41:29 thanks sahina 15:41:37 ybronhei: here for infra? 15:41:42 I am 15:41:52 minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-12-16-15.08.html 15:41:55 orc_orc: it's engine infra ;) 15:41:58 nm 15:42:08 heh -- I bit at that last week as well ;( 15:42:25 I'll reorder next time. 15:42:34 bazulay: here? 15:43:27 anyone from engine infra here? 15:43:59 #info infra team missing a representative. Please update offline. 15:44:10 sbonazzo: integration updates? 15:44:22 ie0 3.4 progress. 15:44:34 we're late on 3.4, I don't think we'll make it in time 15:44:59 sbonazzo: you do have one task completed. 15:45:11 we've near to refactoring ovirt-engine-setup for ease the migration to otopi of other packages 15:45:32 no others that will make it? 15:45:34 yes, we hopefully have ovirt-hosted-engine in 3.4 :-) 15:45:43 yey! 15:46:08 sbonazzo: other tasks that will be in 3.4? 15:46:15 incl. block-storage or nfs only? 15:46:29 outi: nfs only 15:46:29 outi: nfs only for now 15:46:33 k 15:46:47 doron: nightly test on Fedora 20 has already started by dougsland 15:47:12 very well. 15:47:15 doron: hopefully we'll be able to have 3.4 running on it 15:48:12 doron: also alonbl started refactoring dwh and reports 15:48:28 doron: so they'll be in a better shape at least 15:48:36 #info integration team has 1 task completed for 3.4. working on the others. Hosted engine is expected to be included in 3.4. 15:48:47 thanks sbonazzo 15:48:56 lvernia: here? 15:49:05 doron: Indeed. 15:49:18 lvernia: how are the network team doing? 15:49:51 doron: Network features moving along well. Half of them have patches being reviewed. 15:50:12 iproute2 patches reviewed, only some minor changes needed 15:50:14 doron: Labels won't make it in before feature freeze, but if allowed to continue will make it prior to GA. 15:50:35 doron: Same concerning at least some functionality of Network QoS. 15:50:41 lvernia: we'll revisit it early january 15:50:48 doron: Alright. 15:51:04 lvernia: anything else? 15:51:22 apuimedo: iproute2 has to be done before xmas, so it's an effort. 15:51:27 doron: No, just adding that an attempt is made to fix some problems of NIC ordering. 15:51:29 but we'll make it. 15:51:58 #info network team doing well. most tasks either done or being reviewed. Labels and host QoS are at risk. 15:51:58 danken: it is 15:51:59 doron: Maybe danken can shed some light if it could be considered an implementation of the requested feature or not. 15:52:05 but it will be done 15:52:19 lvernia: oved's nic ordering patches? 15:52:25 danken: Yes. 15:52:38 there is a guide on how to create users or implement ldap? 15:52:42 lvernia: I have not reviewed them (yet), but my understainf is that they are. 15:52:57 danken: Alright. 15:53:03 lvernia: some case would not be covered, and we know it (hot plug, for one's) 15:53:16 lvernia: sounds promising 15:53:17 but main things (template, clone, import) are covered. 15:53:26 doron: So that's it for us. 15:53:32 lvernia: thanks. 15:53:40 moving to ovirt node 15:53:44 fabiand: here? 15:53:52 yep 15:54:00 hi fabiandhow are you doing on 3.4? 15:54:09 doron, we are moving slowly. 15:54:22 as you might have noted we already limited outrselfs for now to Fedora 19 based images 15:54:40 A new update - in our stable branch - is planned for 3.4 to fix bugs which are mainly discussed on the ml 15:55:30 fabiand: what about the generic registration? 15:55:44 doron, I'm vividly speaking with dougsland about that 15:55:59 fabiand: sounds like it's at risk? 15:56:01 doron, It looks quite good, dougsland has got code for it and a POC 15:56:18 doron, no - it is part of the vdsm plugin and should make it into 3.4 (as part of the plugin) 15:56:28 fabiand: very good. 15:56:32 doron, IMO our main part is to get a stable iso in place 15:56:46 fabiand: I agree. I'm getting complaints on that. 15:56:56 Yeah ... I'm very unhappy about that .. 15:57:07 And we try to come up with fixes 15:57:13 fabiand: so can we expect a stable 3.4 node? 15:57:31 fabiand, doron actually, it will be in vdsm, we will call vdsm-tool (the tool will support ovirt node and normal distro) 15:57:49 anyway, vdsm plugin must be adapted. 15:57:52 doron, yes - we plan to get something into place until begin of Jan 15:58:06 thanks 15:58:13 doron, I target to also do a release as soon as we get a stable build (currently we've got integration problems) 15:58:18 dougsland, thanks 15:58:32 dougsland, do you think that those changes will make it for 3.4? 16:00:02 I'll take that as a yes based on what he mentioned. 16:00:04 fabiand, I don't recall the deadline for inclusion of new tool. 16:00:14 doron, ^ 16:00:28 dougsland: Dec 31 feature freeze, Jan 31 GA 16:00:51 dougsland: so will it be in the node in time? 16:01:21 doron, yes. 16:01:22 dougsland, from a Node perspective it should be usable by mid jan. Then we've got two weeks to test it .. 16:01:30 dougsland, we just need to ensure that it lands in vdsm 16:01:53 fabiand, I think we need to talk about automatic installation (as soon as it land into vdsm) 16:01:53 I'll take that as a yes... 16:02:07 (after the meeting) ;-) 16:02:09 dougsland, automatic installation of? 16:02:14 dougsland, ack 16:02:20 #info node generic registration looks good. Also stable node is expected for 3.4. 16:02:26 thanks dougsland fabiand 16:02:37 anyonehere for ppc? 16:02:42 yes 16:02:42 vitorlima: here? 16:02:45 doron, please also note that el6 support is not dropped, it's just that we need to focus on one image right now .. 16:02:47 hi lbianc 16:02:50 i'm here 16:02:53 doron: hi! 16:03:03 hi guys. 16:03:12 fabiand: I guess we'll need to discuss it later. 16:03:17 ack 16:03:23 lbianc: vitorlima ppc updates for 3.4? 16:03:41 and I saw you found a nice PCI BZ guys. Good job! 16:03:47 we updated the spreadsheet with the status of our main features 16:04:00 we are going good, many patches merged. We have 8 features done and 7 under review 16:04:14 anything at risk? 16:04:19 yeah, we are still looking for bugs related to PCI checks, we will send more patches soon 16:04:47 yes, we have some pretty new patches, that maybe will not get done till 31th 16:05:06 * gtemple PCI checks fixes coming soon 16:05:28 ok. out of your task list for 3.4, what do you have at risk? 16:05:54 it's about blocking migration, snapshots on PPC and support for sPAPR VLAn sPAPR VSCSI 16:06:19 all at risk for 3.4? 16:06:53 i think just blocking migration and snapshots will take some more time than expected, they are already coded, but they need to be reviewed 16:07:02 very well. 16:07:37 #info PPC doing very well; some already done, other in progress. Currently at risk blocking migration and snapshots. 16:07:47 vitorlima: lbianc thanks! 16:07:58 doron: welcome 16:08:01 moving on to sla... 16:08:05 doron: thanks! 16:09:21 #info SLA team has patches for new power savings policy, and sustaining HA flag. other features being designed. 16:09:32 sgotliv: here for storage? 16:10:51 abaron: here? 16:10:54 doron, yes 16:11:05 sgotliv: storage updates? 16:11:23 doron, everything just great 16:11:43 sgotliv: status of 3.4 tasks? 16:12:09 doron, except of the multipath I am not aware of any delays 16:12:35 sgotliv: including functional tests? 16:13:14 doron, ? 16:13:39 sgotliv: take a look at https://docs.google.com/spreadsheet/ccc?key=0AuAtmJW_VMCRdHJ6N1M3d1F1UTJTS1dSMnZwMF9XWVE&usp=drive_web#gid=0 16:13:46 you have the storage tasks there for 3.4. 16:14:08 we're tracking progress here 16:14:18 doron, give me a sec 16:14:21 checkign for risks, based on freeze date. 16:14:33 doron: Vered started working on functional tests changes. No estimate yet. 16:14:59 abaron: so I take it as in risk for 3.4? 16:15:17 yellow at the moment 16:15:27 abaron: any other risks? 16:15:45 beyond multipath? not atm. single disk snapshot 16:15:59 single disk snapshot is on track and patches should be up for review next week 16:16:39 ovf on any domain scope is clear, 2 options for solution there, converging on one 16:16:47 is this generic multipath or equallogic iscsi? 16:17:10 outi: iscsi multipathing. which would solve the equallogic issue, but also for other iscsi backends 16:17:51 ok 16:18:07 #info storage team making progress. functional tests and multipath are currently at risk for 3.4. 16:18:25 abaron: sgotliv thanks for the update and details. 16:18:34 ux next. ecohen? 16:18:39 doron, yes, hi. 16:18:40 doron, "case insensitive search", "centralizing refresh logic" - done. 16:18:40 doron, "broken layout in low resolutions", "ovirt new l&f" - were stretch goals but won't make it, postponed. 16:19:10 ecohen: thanks. so basically you;re done for 3.4? 16:19:15 doron, yep 16:19:44 #info UX team done for 3.4. 2 tasks pushed forward. 16:19:52 thanks ecohen! 16:19:55 doron, np 16:20:02 back to infra, ybronhei here? 16:20:54 ok 16:21:10 mskrivanek: here? 16:21:20 doron: hi, yes 16:21:27 doron: yes, im here 16:21:29 mskrivanek: hi, virt updates for 3.4? 16:22:10 search by description is in, spice proxy at cluster level will make it as well 16:22:21 default VNC console mode is in 16:22:36 hotplug CPU should make it (so far looks good) 16:22:53 disable SSO per VM will make it 16:22:53 nice! 16:23:11 this one as well "Show name of the template in General tab for a vm if the vm is deployed from template via clone allocation" 16:23:41 ..and we have a new event for remote console connection. Small things, but quite a few of them... 16:23:41 mskrivanek: Error: ".and" is not a valid command. 16:23:52 what's currently at risk for 3.4 freeze? 16:24:40 vminit (did'nt mention yet). It's a persistence for cloud-init options and sysprep enhancements in one 16:24:54 at risk? 16:25:06 there's a good chance it will make it at least partially, so I should add it to the spradsheet... 16:25:20 indeed so... 16:25:42 mskrivanek: anything else at risk? 16:27:56 #info virt team making good progress. vminit currently at risk. 16:28:04 thanks mskrivanek 16:28:06 moving on 16:28:14 #topic infra update 16:28:20 orc_orc: that;s your queue ;) 16:28:22 general infra minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-12-16-15.08.html 16:28:25 heh 16:28:29 a quick shout out: centos slaves bumped to to 6.5 -- thanks ewoud 16:28:39 yey! 16:28:43 but on a less bright note, rackspace03 is still blocked -- now it is routing issues 16:28:47 https://feorahosted.org/ovirt/ticket/80 16:28:51 eedri was to escalate w R/S 16:28:56 and that is about it 16:29:01 eedri: any news? 16:29:16 orc_orc, we're evaluating moving to another vendor 16:29:32 orc_orc, i will send specs soon to the list 16:29:32 eedri: get me a requirements document and I'll quote it ;) 16:29:43 orc_orc, yea, i'd love your input on that 16:29:47 * nod * 16:29:53 #info centos slaves bumped to to 6.5 16:29:58 orc_orc, i'm going to send an email to infra soon on what we want and what people recommends 16:30:07 I was talking a a new DC that wanted my business last week 16:30:13 #info infra considering an alternate vendor 16:30:27 eedri: check your mail about OS1 16:30:37 end of year is contract re-negotiation time 16:30:57 doron, ok 16:31:06 anything else on infra? 16:31:30 thanks orc_orc eedri 16:31:33 moving on 16:31:37 you are welcome 16:31:41 #topic other topics 16:31:55 anyone wishes to raise something? 16:32:42 Going once?.... 16:32:42 doron: maybe you're missing ybronhei 16:33:00 ybronhei: i think so 16:33:12 sbonazzo: I was waiting, twice.. 16:33:18 ybronhei: infra updates? 16:33:50 ybronhei: we still have an 3.3 issue that i aware of - https://bugzilla.redhat.com/show_bug.cgi?id=1040063 16:33:59 doron: ^ 16:34:51 doron: and about 3.4 feature, we're done with all of them except the snmp part which supposes to be also in its last steps 16:35:27 ybronhei: is the 3.3 a blocker for ovirt? 16:35:43 I meant 3.3 bz 16:35:52 doron: no 16:36:01 ybronhei: very well. 16:36:07 anything at risk for 3.4? 16:37:14 #info infra team looking into 1040063 . 3.4 progress doing well. 16:37:20 anything else? 16:37:31 Going once?.... 16:38:00 Going twice?.... 16:38:29 #info happy holidays everyone! 16:38:32 #endmeeting