15:02:34 <doron> #startmeeting oVirt Weekly Sync
15:02:35 <ovirtbot> Meeting started Wed Jan 22 15:02:34 2014 UTC.  The chair is doron. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:35 <ovirtbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:02:35 * ybronhei1 Infra here
15:02:40 * sbonazzo here
15:02:44 <sgotliv> storage here
15:02:45 * ecohen here
15:02:46 <doron> #topic Agenda and roll Call
15:02:47 <doron> #info 3.3 update releases
15:02:49 <doron> #info 3.4 progress
15:02:50 <doron> #info conferences and workshops
15:02:52 <doron> #info infra update
15:02:53 <doron> #info other topics
15:03:05 * lvernia is here.
15:03:11 * itamar here
15:03:48 * sherold is here
15:03:55 * mskrivanek here
15:03:57 * apuimedo here
15:04:15 <doron> Let's s tart with 3.3.x
15:04:18 <doron> #topic 3.3 update releases
15:04:28 <doron> sbonazzo: updates?
15:04:32 <sbonazzo> doron: 3.3.3 RC has been released and announced
15:04:46 <doron> #info 3.3.3 RC has been released and announced
15:04:47 * orc_orc is here
15:04:47 <itamar> sbonazzo: when is GA planned?
15:05:27 <sbonazzo> doron: still missing an update on release notes page about vdsm bugs and new features. GA next week, jan 28th
15:06:00 <doron> sbonazzo: who should be handling this update?
15:06:13 <sbonazzo> doron 3.3.2 is currently broken on Fedora due to a recent change in python-cpopen
15:06:23 <doron> grrr
15:06:30 <ybronhei1> :(
15:06:40 <doron> #info 3.3.2 is currently broken on Fedora due to a recent change in python-cpopen
15:06:48 <sbonazzo> doron: I hope vdsm team can update vdsm fixed bug list
15:07:05 <ybronhei1> sbonazzo: what is it exactly ?
15:07:13 <doron> ybronhei1: danken who can help updating it?
15:07:34 <sbonazzo> ybronhei1: opened a bug about it, it has obsoletes and missing provides, so broke dependency resolution
15:08:01 <ybronhei> sbonazzo: what exactly the implications ?
15:08:23 <ybronhei> sbonazzo: why broken ? if you remove the old and install the new , is it work properly ?
15:08:25 <sbonazzo> ybronhei: yum install vdsm doesn't work if you don't have python-cpopen already installed
15:08:44 <ybronhei> sbonazzo: right, its build requierment
15:08:49 <sbonazzo> ybronhei: 3.3.2 still requires vdsm-python-cpopen
15:09:11 <sbonazzo> so if you don't have python-cpopen installed it try to install it and fail
15:09:27 <freax1> Some problem with Centos 6.5
15:10:04 <ybronhei> sbonazzo: 3.3.2 brings vdsm-python-cpopen
15:10:04 <freax1> sorry, same
15:10:21 <sbonazzo> ybronhei: which is obsoleted by python-cpopen-1.3
15:10:42 <sbonazzo> ybronhei: but doesn't provide vdsm-python-cpoen itself
15:10:48 <sbonazzo> ybronhei: so yum fails
15:10:59 * gtemple ppc_team here
15:11:02 <ybronhei> sbonazzo: and this is not good? I thought thats the required behavior
15:11:09 <orc_orc> sbonazzo: why not add a phantom: Provides: vdsm-python-cpoen in the .spec file to solve that
15:11:21 <sbonazzo> ybronhei: usually you obsolete <1.3 and provides >=1.3
15:11:59 <sbonazzo> ybronhei: you're missing the provides part
15:11:59 <ybronhei> sbonazzo: odd.. im not sure what's the problem here, i need to see it
15:12:19 <sbonazzo> just install a f19, wun yum install vdsm with stable repo enabled
15:12:24 <sbonazzo> run
15:12:34 <doron> ybronhei: please take this offline with sbonazzo and update the list. is it ok?
15:12:40 <ybronhei> ye
15:12:45 <sbonazzo> doron: ok
15:12:57 <doron> sbonazzo: thanks. any other updates?
15:13:05 <sbonazzo> not for 3.3.z
15:13:38 <doron> very well. any chance the python issue will effect tomorrow's test day?
15:14:10 <sbonazzo> doron: I don't think so, 3.4.0 seems to work fine with that
15:14:43 <doron> very well.
15:14:48 <doron> so we can move on ;)
15:14:56 <doron> #topic 3.4 progress
15:15:08 <sbonazzo> doron: 3.4.0 beta has been released and announced
15:15:25 <doron> #info 3.4.0 beta has been released and announced
15:15:28 <doron> thanks sbonazzo
15:15:29 <sbonazzo> it has been delayed by one day due to recent changes rising build requirements
15:15:38 <doron> any known blockers ?
15:15:41 <sbonazzo> causing jenkins to fail building it
15:16:08 <sbonazzo> doron we have some, but I think major is AIO not working
15:16:23 <doron> sbonazzo: who's handling it?
15:16:28 <mskrivanek> blockers for what?
15:16:36 <doron> mskrivanek: 3.4
15:16:38 <mskrivanek> GA?
15:16:40 <sbonazzo> doron: juan for sdk and didi and me for setup
15:16:45 <sbonazzo> mskrivanek: GA
15:16:56 <sbonazzo> mskrivanek: 3.4.0 GA
15:16:58 <mskrivanek> well, features?
15:16:59 <dneary> Hi apuimedo
15:17:05 <doron> sbonazzo: so we should alert folks not to use it for now?
15:17:05 <mskrivanek> not all is green on the spreadsheet yet
15:17:05 <dneary> apuimedo, Looking into it
15:17:14 <apuimedo> dneary: hi
15:17:16 <doron> sbonazzo: ie- testday
15:17:20 <sbonazzo> doron: yes, I'm adding a note to release page
15:17:25 <sbonazzo> doron: in known issues
15:17:29 <doron> sbonazzo: thanks.
15:17:51 <doron> #info all-in-one broken in 3.4. Please do not use for now.
15:18:09 <doron> before discussing test day
15:18:15 <apuimedo> sbonazzo: the build requirements is the vdsm buildrequires libnl issue?
15:18:17 <doron> let's do a quick update round
15:18:45 <doron> who's here for gluster?
15:18:53 <sbonazzo> apuimedo: no the build requirements are in ovirt-engine: it needs now 20Gb of ram on a 4 core hyperthreaded cpu
15:19:02 <apuimedo> :O
15:19:10 * kanagaraj here for gluster
15:19:16 <apuimedo> I'll never be able to build it then xD
15:19:24 <kanagaraj> doron, hi
15:19:24 <doron> kanagaraj: hi, can you please update on your 3.4 status?
15:19:36 <sbonazzo> apuimedo: there are tricks for doing that with 4 gb only but it takes a life to build
15:19:36 <orc_orc> that set of requirements is ... breathtaking
15:19:47 <apuimedo> :-)
15:19:51 <apuimedo> indeed
15:19:52 <kanagaraj> Async tasks is in, Volume capacity did not make in
15:20:28 <doron> kanagaraj: and what about your next gluster version? IIRC we had dependencies for it.
15:21:15 <kanagaraj> gluster 3.5 should be released start of next month
15:21:41 <kanagaraj> all the related patches are already in 3.5, so no issues
15:22:03 <doron> kanagaraj: this means that 3.4 has to be released after 3.5 is in GA?
15:22:17 <doron> (ovirt 3.4 and gluster 3.5)
15:22:56 <kanagaraj> gluster 3.5 is in beta now
15:23:24 <doron> kanagaraj: right, but we need to make sure ovirt 3.4 will not break due to lack of gluster 3.5.
15:24:23 <doron> sbonazzo: kanagaraj let's sync offline- we need to verify this will not be an issue. ok?
15:24:27 <kanagaraj> there wont be any breaking,  async tasks needs gluster 3.5
15:24:34 <kanagaraj> doron, ok
15:24:42 <sbonazzo> doron: ok
15:25:00 <doron> #info gluster 3.4 status: Async tasks is in, Volume capacity did not make in. Need to sync on gluster 3.5 and ovirt 3.4 status.
15:25:04 <doron> thanks kanagaraj
15:25:14 <doron> ybronhei: here for infra?
15:25:19 <ybronhei> doron: yes
15:25:30 <doron> ybronhei: awwesome. What's the 3.4 status?
15:25:35 <ybronhei> doron: snmp & snmp trap monitoring (will do only snmp trap as notification) - still not ready. but we intend to get it in asap
15:25:35 <ybronhei> doron: allow to provide a password change url on login failure when password expires - in develop progress, yair was not here to response about the exact status, but hopefully it will get in very so
15:25:35 <ybronhei> on
15:26:22 <doron> ybronhei: I'm counting on snmp for infra.next conference. do not let us down...
15:26:35 <ybronhei> doron: hope so ..
15:26:44 * danken is late, partially here
15:27:11 <doron> #info infra 3.4 status: SNMP in progress, password change url on login failure when password expires - in develop progress.
15:27:16 <doron> thanks ybronhei
15:27:23 <doron> sbonazzo: 3.4 status?
15:27:31 <doron> (for integration)
15:27:47 <sbonazzo> dwh and hosted engine are in today beta on both centos and fedora 19
15:28:00 <doron> cool,.
15:28:01 <sbonazzo> jasper server has been ported to centos
15:28:11 <sbonazzo> reports is still a work in progress
15:28:41 <sbonazzo> same for the virtual appliance
15:28:59 <itamar> sbonazzo: I think these one is "ready when its ready". folks are waiting for them, and they don't impact the other components
15:29:09 <sbonazzo> itamar: +1
15:29:17 <doron> #info integration 3.4 status: dwh and hosted engine are in today beta on both centos and fedora 19. jasper server has been ported to centos. reports and virtual appliance are being worked on.
15:29:22 <doron> sbonazzo: thanks
15:29:31 <doron> lvernia: here for network?
15:29:36 <lvernia> doron: Yep.
15:29:42 <doron> lvernia: how are you doing?
15:29:55 <lvernia> doron: Good, thank you. Labels made it in shortly after last week's meeting.
15:30:13 <doron> cool
15:30:15 <lvernia> doron: The migration issue with the Neutron security groups will stay with us as a bug.
15:30:45 <lvernia> doron: And I think some issues with iproute2 will have to be fixed as bugs as well.
15:30:52 <lvernia> doron: apuimedo probably knows best.
15:30:58 <doron> apuimedo: ?
15:31:18 <doron> apuimedo: what should we expect in 3.4?
15:31:24 <apuimedo> lvernia: yes, there will be some reporting fixed as a bug
15:31:33 <apuimedo> for the engine-vdsm communication
15:31:41 <doron> apuimedo: is this a bocker for GA?
15:31:45 <doron> (blocker)
15:31:52 <lvernia> doron: I would say no.
15:31:59 <doron> very well.
15:32:02 <lvernia> apuimedo: Right?
15:32:21 <apuimedo> doron: no, it isn't, as one can just use ifcfg configurator on the meantime
15:32:36 <lvernia> doron: Good, so I think we're good to move on.
15:32:51 <doron> #info network 3.4 status: Labels are ready. migration issue with the Neutron security groups and iproute2 issues became non-blocker bugs.
15:32:59 <doron> thanks lvernia apuimedo.
15:33:12 <doron> ppc guys, who's here?
15:33:13 <apuimedo> you're welcome
15:33:21 <lbianc> here
15:33:21 <gtemple> sbonazzo: vitorlima and lbianc here
15:33:30 <lbianc> doron: here
15:33:45 <doron> vitorlima: lbianc hi. PPC status for 3.4?
15:33:47 <gtemple> doron: vitorlima and lbianc here
15:34:07 <doron> gtemple: thanks.
15:34:25 <lbianc> doro: Hi! we are in the same status from last week, missing to be merged the patches for blocking migration and snapshot
15:34:52 <doron> lbianc: is it missing reviews or something else?
15:34:58 <mskrivanek> that shouldn't be a blocker though
15:35:07 <doron> mskrivanek: ack.
15:35:20 <lbianc> yes
15:35:30 <doron> lbianc: what can we do to help?
15:35:58 <lbianc> We need review on these patches
15:35:59 <mskrivanek> I suppose review:) it's ongoing, but it's a lot of code...
15:36:22 <doron> I see. ok. mskrivanek I assume you're on top of it?
15:36:26 <mskrivanek> i'd consider it "nice to have" and have it polished over time, regardless it's 3.4 or 3.5
15:36:52 <doron> very well. we may want to put it in 3.5 spreadsheet if we miss it.
15:37:03 <mskrivanek> rephrase - something between "nice to have" and "blocker"
15:37:23 <doron> #info pps 3.4 status: no changes since last week. A few patches being reviewed, non-blocking.
15:37:32 <lbianc> Ok, it is possible to consider it be merged on bug fix time? I think it's not too much code
15:37:37 <doron> mskrivanek: what is blocking?
15:37:45 <vitorlima> doron, can it be included in some 3.4.x release later?
15:38:09 <mskrivanek> lbianc: yes, agree, definitely
15:38:10 <doron> vitorlima: yes if not a feature and not a blocker.
15:38:44 <doron> ie- if we consider it as a bug it cangot into 3.4.z
15:38:59 <doron> vitorlima: ok?
15:39:19 <vitorlima> doron, it may be considered as such, since trying to migrate or do a memory snapshot will result in an error
15:39:24 <orc_orc> ... does oVirt run a formal Z channel -- thot that was elsewhere
15:39:24 <ovirtbot> orc_orc: Error: ".." is not a valid command.
15:39:27 <orc_orc> ... does oVirt run a formal Z channel -- thot that was elsewhere
15:39:51 <doron> vitorlima: very well, but let's try to have it asap.
15:40:04 <doron> vitorlima: lbianc thanks for the updates.
15:40:10 <doron> sla updates
15:40:21 <gtemple> doron: thanks a lot !
15:40:24 <lbianc> doron: thanks!
15:40:45 <doron> #info sla 3.4 status: hosted engine maintenance still not in- awaiting vdsm maintainers.
15:40:59 <doron> ybronhei: danken appreciate is you can review
15:41:11 <doron> gpadgett 's pathes.
15:41:35 <doron> moving on to storage.
15:41:42 <doron> who's here for storage?
15:41:51 <sgotliv> sgotliv
15:41:56 <sgotliv> Get rid of storage pool metadata on master storage domain :
15:41:56 <sgotliv> VDSM code is merged, we are waiting for another cycle of review for 4 Engine patches, we don't feel confident at this stage to merge it.
15:41:56 <sgotliv> QA will help us to perform pre-integration tests then we'll know better
15:41:56 <sgotliv> Store OVF on any domains - code review
15:41:56 <sgotliv> Multiple storage domains under same storage pool -
15:41:58 <sgotliv> Merged upstream, Tal working to backport it to the stable branch.
15:42:21 <sgotliv> multipath is merged
15:42:25 <doron> sgotliv: anything else?
15:42:31 <sgotliv> no
15:42:35 <doron> sgotliv: thanks
15:43:40 <doron> #info storage 3.4 status: multipath in. Multiple storage domains merged to master and should be ported. getting rid of storage pool metadata on master storage domain in progress.
15:43:49 <doron> ecohen: ux updates?
15:43:51 <ecohen> doron, "easily collapsible left-panel" (that I requested last week as an exception) eventually made it in time for ovirt-engine-3.4.
15:43:52 <ecohen> doron, all-in-all - 4 UX features are in ovirt-engine-3.4.
15:44:12 <doron> ecohen: very nice!
15:44:37 <doron> #info: ux 3.4 status: 4 features made it in.
15:44:49 <doron> mskrivanek: how's virt doing?
15:44:58 <mskrivanek> awesome, of course!:)
15:45:05 <mskrivanek> 3 features still missing
15:45:07 <mskrivanek> hotplug merged to master, 3.4 backports posted, expecting to get in today
15:45:09 <mskrivanek> vminit (cloud-init/sysprep persistence) - in progress, expecting to get it in by EOD
15:45:11 <mskrivanek> template versions - merge in progress right now, expecting to get it in by EOD
15:45:54 <itamar> lbianc: please note you'd have to backport them to ovirt-engine-3.4 branch for inclusion in 3.4 (for engine)
15:46:06 <doron> #info virt 3.4 status: hotplug merged to master, 3.4 porting in progress. vminit  and  template versions in progress.
15:46:17 <doron> thanks mskrivanek
15:46:33 <doron> #topic 3.4 test day
15:46:43 <doron> sbonazzo: test day updates for tomorrow?
15:47:26 <sbonazzo> doron: mail sent to mailing list reminding about it
15:47:41 <sbonazzo> doron: wiki page is under update
15:47:47 <doron> #info mailing list notified about test day details
15:47:58 <lbianc> itamar: Hi! Ok, thanks for remembering.
15:48:00 <doron> #info wiki page being updated.
15:48:06 <doron> sbonazzo: thanks. anything else?
15:48:45 <sbonazzo> doron: no
15:49:06 <doron> #info everyone are invited to join us tomorrow. For details please check the mail. Thanks!
15:49:08 <doron> thanks sbonazzo
15:49:18 <doron> anything else for 3.4?
15:49:33 <doron> very well than. Moving on.
15:49:36 <doron> #topic conferences and workshops
15:49:43 <doron> dneary: bkp updates?
15:50:22 <bkp> None here. Flier for FOSDEM is set, talks are set. Looking good for the next couple of weeks.
15:50:42 <bkp> I will be attending SCALE and delivering an oVirt talk there.
15:51:36 <doron> #info fosdem arrangments done. You're all welcome tojoin us in the stand and sessions and social event.
15:52:00 <doron> #info bkp to give an Ovirt session in SCALE.
15:52:10 <doron> thanks bkp. anything else?
15:52:29 <bkp> I'm set for this topic.
15:52:47 <doron> very well.
15:52:55 <doron> #topic infra update
15:53:02 <doron> orc_orc: how are you?
15:53:09 <orc_orc> doron: hi -- fine thank you
15:53:19 <doron> orc_orc: updates?
15:53:20 <orc_orc> better, (over a cold) than the last couple weeks ;)
15:53:21 <orc_orc> my full remarks for infra are posted at, just now:
15:53:22 <orc_orc> http://lists.ovirt.org/pipermail/infra/2014-January/005064.html
15:53:28 <orc_orc> I was absent Monday for an appt, and do not see an email with minutes.
15:53:28 <orc_orc> Prior week was skipped because of member availability issues as well.
15:53:30 <orc_orc> So this is a summary from the list traffic for the last few days
15:53:37 <orc_orc> In no particular order:
15:53:49 <orc_orc> #info In no particular order:Kimchi asks for jenkins coverage #105
15:54:08 <orc_orc> #info ditto standing up an Ubuntu test instance was requested
15:54:17 <orc_orc> Disk space issues on lists were hit on a transient basis Sunday
15:54:28 <orc_orc> no action n4eeded there save keep an eye on it
15:54:37 <orc_orc> also I have observed wink outages on gerrit, and lists of less than an hour's duratio
15:55:03 <orc_orc> importantly for email delivery, linnode PTR and it turns out A and AAAA record have not proceded, as the request was being 'sat on'
15:55:13 <orc_orc> This is really needed to solve an email filtering issue at Comcast and one assumes other ISPs,  They also examine this data, along with _SPF  TXT records
15:55:32 <orc_orc> one person silently and unilaterally deciding not to push a change through after reequest is a problem
15:55:48 <orc_orc> so an issue we at infra need to solve is: DNS management is weak as responsibility and capability to solve are not unified here
15:56:16 <orc_orc> as to 'production' he gerrit is sluggish for unknown reasons doing version control CO's (several reports),  One possible cause is BW limitations on some link paths?
15:56:18 <doron> orc_orc: and I assume this will be handled in the next mt?
15:56:23 <doron> (mtg)
15:56:40 <orc_orc> doron: perhaps but there is a dicision of responsibility and control that looks hard to solve from teh infra side\
15:56:49 <orc_orc> division*\
15:57:04 <orc_orc> I will escalate out of band, and then in, as needed
15:57:14 <orc_orc> jenkins got a 'just in case' reboot last week, but no root cause analysis was performed
15:57:30 <eedri> orc_orc, i'm just replying to your email now
15:57:49 <eedri> orc_orc, there has been major issues with jenkins last week and most of the infra team were on it
15:57:51 <orc_orc> infra needs to get more habitual as to documenting on the ML, and running down root causes of outages, but that is an ongoing process
15:58:02 <orc_orc> eedri: * nod *
15:58:04 <eedri> orc_orc, we're mostly out of resources
15:58:18 <eedri> orc_orc, and seems like very limited people are handking real live issues on the jenkins itself
15:58:32 <eedri> orc_orc, which is a major scale issue to support ovirt going forward
15:58:37 <orc_orc> eedri: as I am US side of Atlantic, do handoffs to me at the end of your day if more continual attention is needed
15:59:09 <orc_orc> I don't really see the needs in IRC, and the ML is ... partial and retrospective
15:59:12 <doron> orc_orc: eedri I suggest you discuss it offline and update us next week?
15:59:17 <orc_orc> doron: * nod *
15:59:25 <eedri> doron, i'm answering the email on the infra list now with updates
15:59:26 <eedri> doron, sure
15:59:36 <orc_orc> and then, on a personal note: Personally I am building a 'knock-off' iscsi and NFS unit based on the QNAP doco and git content, for oVirt testing locally ... particularly performance timing trials
15:59:53 <doron> orc_orc: cool :)
16:00:02 <doron> and thanks for the updates!
16:00:03 <orc_orc> doron: in the future, I have a standing voice conf call at 1100 US ET ... could infra come earlier in the list, possibly
16:00:08 <orc_orc> doron:  a pleasure
16:00:27 <doron> orc_orc: please mail me / ping me earlier and I'll adjust.
16:00:39 <orc_orc> doron: wilco
16:00:46 <doron> very well,
16:00:53 <doron> let's move on-
16:00:54 <doron> #topic other topics
16:01:11 <doron> Do we have anyone here workin on the NUMA features?
16:01:36 <doron> Anyone from Vinod's team around?
16:01:46 <BruceShi> here
16:02:09 <BruceShi> doron:hi
16:02:09 <doron> BruceShi: hi. Do you want to give a very short intro to what you're doing?
16:03:40 <doron> We'll wait with this intro for next time.
16:03:45 <doron> BruceShi: 谢谢
16:03:57 <doron> anyone else wants to discuss something?
16:04:16 <bkp> I have something on documentation
16:04:20 <doron> bkp: shoot
16:04:38 <bkp> We are still trying to figure out how to notify users on the oVirt site about new releases. We have stable (3.3.2), pre (3.3.3 RC), and development (3.4.0 beta)...
16:04:52 <bkp> ...Should we keep a permanent link to the stable release on the home page, and then link to the most current pre and devel on either the Download or Development page?
16:04:52 <ovirtbot> bkp: Error: "..Should" is not a valid command.
16:05:52 <bkp> We want to get these new releases out, but not accidentally give newer users a path to an unstable release.
16:06:48 <doron> bkp: other projects make it very clear
16:06:56 <doron> Here's an example: http://www.mozilla.org/en-US/firefox/beta/
16:07:37 <bkp> And we can do something along those lines.
16:08:17 <doron> So I'm all for a simplified direction such as firefox are doing.
16:08:26 <doron> so the default is always stable.
16:08:44 <bkp> Exactly
16:08:51 <doron> +1 from me.
16:08:57 <doron> anyone else?
16:09:49 <doron> bkp: I suggest you draft it in a mail and send to the arch list.
16:10:00 <doron> you can take it from here. ok?
16:10:23 <alonbl> ovedo: I pushed new changes, I hope you like the first one.
16:10:41 <doron> bkp: ?
16:10:59 <bkp> Yes, acknowledge
16:11:08 <ovedo> alonbl, acked the new patch. is there another change in the previous patches?
16:11:31 <doron> thanks
16:11:37 <doron> anything else?
16:11:47 <doron> Going once?....
16:12:18 <doron> Going twice....
16:12:39 <doron> #endmeeting