14:00:01 #startmeeting oVirt Weekly Meeting 14:00:01 Meeting started Wed Sep 11 14:00:01 2013 UTC. The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:05 #chair oschreib dneary 14:00:05 Current chairs: dneary mburns oschreib 14:00:12 #topic Agenda and Roll Call 14:00:18 #info 3.3 Release Status 14:00:31 #info tentative planning for 3.3.1 14:00:38 #info 3.4.0 planning 14:00:41 #info conferences and workshops 14:00:47 #info infra update 14:00:50 #info other topics 14:01:13 also, just as an fyi -- i'm somewhat split-focused during this meeting... 14:01:33 * oschreib here 14:01:49 * sahina here 14:01:58 * yzaslavs here 14:03:53 #topic 3.3 release status 14:04:13 #info final RC builds posted between yesterday and today for engine, vdsm, node 14:04:35 I suspect the all-in-one issues are not over. 14:05:03 oschreib: blocking issues? 14:05:05 I'd like to get two +1 on the .el6 build and the all-in-one before release 14:05:12 mburns: under invastigations 14:05:19 oschreib: ok 14:05:19 sgotliv here 14:05:30 * mburns will try to pick up el6 build today 14:05:51 #info ovirt-node-iso rpms will be uploaded shortly 14:06:04 #info node iso images are available in releases/3.3/iso 14:06:27 I wouldn't release in a short cycle without few positive installations 14:06:34 oschreib: agreed 14:06:34 we normally want at least a week 14:07:18 oschreib: yes, i normally agree, but let's see if we can get successful tests and get it out quicker 14:07:28 dneary: plan is to get marketing stuff out on Monday, right? 14:07:36 mburns, Yes 14:08:05 oschreib: so we can wait until monday if we have to 14:08:54 I'm fine with Monday, but again, I need as many installation as we can 14:09:01 agreed 14:09:17 #action mburns to get things set for release today 14:09:29 #action mburns to coordinate release for Monday 14:09:31 oschreib, mburns: My understanding was that we would have release ready packages today 14:09:39 An oVirt Live for 6.4 would be appreciated too 14:10:01 dneary: Ohad is working on ovirt-live 14:10:06 dneary: no ETA yet 14:10:15 dneary: -live is hard to do when we don't have stable engine... 14:10:29 i think that's ok to lag a bit behind the ga release... 14:10:29 or stable all-in-one 14:10:49 Yes, it's OK 14:11:01 But it would be nice to have it ASAP 14:11:26 dneary: agreed 14:12:06 dneary: I thought we will have packages today to, and they we're built, BUT, they failed my tests (and I don't know if it's a local issue or not), I'd love some help from people over here with aio installations, so we could verify and release in short cycle 14:12:58 oschreib, Can you please send regular emails to arch@ when there are problems with builds, please? It seems like we're losing a day every time a package needs to be rebuilt 14:13:31 dneary: what sort of emails? 14:13:40 oschreib, Status of builds 14:13:50 If a package needs rebuilding, it should happen ASAP 14:14:08 dneary: I'm the one building ovirt-engine 14:14:27 and since I don't have any other resource, it's me or someone from the team testing it. 14:14:36 oschreib, Which tests did they fail? 14:14:43 all in one install 14:15:11 on f19 14:16:56 ok, so plan is to get as many successful tests as possible in the next 2 days 14:17:04 and get problems reported ASAP 14:17:21 mburns: after the meeting, can you send an status update, and request for feedback on the rpms? 14:18:02 oschreib: i can send a current status as i know it and ask for feedback, yes 14:18:14 #action mburns to solicit feedback on beta rpms 14:18:16 superb 14:19:11 #info no open blockers at the moment, release just pending successful testing of current packages 14:19:33 anything else we have to discuss on 3.3.0? 14:19:39 nope 14:19:54 #topic 3.3.1 planning 14:20:13 oschreib: i think the main drive is when we can get engine ready to go 14:20:25 \exit 14:20:33 target mid-october (so just before ovirt dev meetings in Edinburgh)? 14:21:28 oschreib: ? 14:21:29 well, it depends on the 3.3.1 branch (if we're going to rebase the engine or not) 14:21:53 oschreib: from itamar, it seems it's primarily bug fixing in master branch 14:22:02 it's true 14:22:03 with a couple small features, but things that would be valuable 14:22:16 mburns: I won't call them small 14:22:17 and 3.3.1 should also include the hosted engine 14:22:26 oschreib: what are the features? 14:23:03 I'm not tracking all the features that got into the engine, I heard that network profiles is in, and it's pretty heavy 14:23:09 again, I'm not against a rebase 14:23:22 but if we do so, I'd like to have some sort of test day 14:23:29 and a short beta cycle 14:23:47 so we should rebase->beta->tests->beta2->release 14:23:52 or something like that 14:24:02 oschreib: ok, how long do you need to get things into a good state for a test day? 14:24:22 #info engine exploring pulling all master changes (primarily bug fixes) into 3.3.1 14:24:46 mburns: I don't think it should be problematic at all 14:25:06 mburns: if the rebase will be smooth, it can just take a day 14:25:13 #info target should be before developer meetings in October 14:25:35 but.... It's a really ugly thing to do in a small release 14:26:38 oschreib: ok, how about planning to get packages together for 3.3.1 for 25 Oct? 14:26:49 and plan test day for following week 14:27:20 mburns: so how should we decide about the rebase issue? 14:27:39 oschreib: let's get to a decision on the email thread 14:27:57 i haven't seen any objections to a rebase yet, but if you have concerns, let's get them there 14:28:25 #action oschreib to get a decision on 3.3.1 rebase 14:28:58 oschreib: final build for issues in 3.3.1 test day on 14-Oct and release that week? 14:29:28 will vdsm be rebased with master as well for 3.3.1 ? 14:29:43 mburns: I'd not decide on dates before the release of 3.3.0 14:29:46 but sounds ok 14:30:04 (I'll be OOO between 06.10 and 12.10, jut FYI) 14:30:15 #info tentative plan: build new 3.3.1 packages by 25-Sep, test-day on 1-Oct, rebuild between 9-Oct and 14-Oct for test day issues, release prior to 20-Oct 14:30:33 oschreib: ok, it's a tentative plan... 14:30:44 sahina: that's a choice of the vdsm team 14:30:58 but in general, i'm against a rebase unless it's only bug fixes 14:31:17 mburns, cos some of the engine patches have corresponding vdsm changes as well 14:31:36 sahina: those would need to be backported if we don't rebase 14:31:49 mburns, k. got it 14:32:16 but rebase choice has to be the maintainer's choice 14:33:05 #topic 3.4.0 planning 14:33:20 mburns: don't even start the thread about engine maintainership 14:33:46 i don't have much to say here other than to point to the feature request list is on the arch@ mailing list 14:33:49 oschreib: ;-) 14:33:59 yes, i ran into that when you were out... 14:34:01 same here 14:34:13 itamar started an email thread about it as well 14:34:26 #info please comment/request/commit to new features on arch@ and users@ mailing lists 14:35:06 mburns, do we have a timeline for 3.4 release or will we decide that as per features? 14:35:14 #info we'll start talking dates and release planning in the next few weeks 14:35:25 mburns: even what we think is the obvious? bazulay and others from his group for example have plans to continue improving the async task mgmt at engine... 14:36:09 yzaslavs|mtg: features like that should get feature pages and attached to the new 3.4 release management page that i'm hoping oschreib will be creating shortly... 14:36:30 mburns: i thought so, wanted to be sure, thanks 14:37:50 yzaslavs|mtg: might make comment on the thread if there are net new features rather than just improvements 14:38:30 something like "we're working on improving async task management, see the feature page here: " 14:38:52 but i'll leave that to your best judgement 14:39:19 i'm looking to get info on big features that we will want to track for the release 14:39:28 and highlight in release marketing 14:39:57 #topic workshops and conferences 14:40:03 dneary: any news here? 14:40:22 #info oVirt Developers Meeting during KVM Forum in Edinburgh, UK 21-23 October 14:40:59 #info to attend, please register for KVM Forum 14:41:06 #info first 200 people to register get free admission 14:41:15 mburns - on vdsm - need to review more carefully. I think worth doing the extra testing for a rebase (even if we need to change the version). we can stabilize that version in a short cycle, revert problematic issues, etc. 14:41:35 mburns, but we'll confer with danken on what's best for vdsm 14:41:57 itamar1: agreed, we can discuss on the existing email thread 14:42:39 dneary: any other details we should be sharing here? 14:42:48 mburns, Is the plan for 3.3.1 (apologies, was AFK) to rebase straight after the 3.3 release? 14:43:06 mburns, If so, I'd like to get packages off the rebased branch straight after that 14:43:18 I have details on the talks 14:43:20 dneary: depends on the final decision made, but i'd like to see them ASAP 14:43:24 Let me fetch them up... 14:43:51 we can rebase anytime, iiuc 14:44:22 * LinuxCon Europe - CloudOpen 14:44:22 * 6 oVirt related talks: 14:44:22 RAM Snapshots in oVirt - Arik Hadas 14:44:22 oVirt and Cloud-Init integration - Omer Frenkel 14:44:22 Empowering Data Center Virtualization Using KVM - Livnat Peer 14:44:24 Converged Infrastrucure with Open Source - Theron Conrey 14:44:25 GlusterFS Architecture & Roadmap - Vijay Bellur 14:44:27 Cloud Computing with KVM - Tony Gargya 14:44:29 * 2 hours training session 14:44:31 Scripting And Integration with the oVirt Engine - Oved Ourfali 14:44:33 * LinuxCon Europe - KVM Forum 14:44:35 * 5 oVirt talks in KVM Forum: 14:44:37 Empowering Data Center Virtualization using KVM (Livnat Peer) 14:44:39 Kimchi: Simplified KVM Management (Adam Litke) 14:44:43 Providing quality of service for VMs in oVirt (Martin Sivak) 14:44:45 Linux storage stack for the cloud (Yeela Kaplan) 14:44:47 Trusted Compute Pools Feature in oVirt (Gang Wei) 14:44:49 * 3 oVirt talks in oVirt developer meeting: 14:44:51 The State of oVirt (Itamar Heim) 14:44:53 oVirt hosted engine: the egg that hosts its parent chicken (Doron 14:44:55 Fediuck) 14:44:57 oVirt for PowerPC (Otavio Luiz Ferrant) 14:44:59 Oops - that's quite a flood 14:45:01 We also need to define a rough agenda for the developers summit still - needs to get done over the next week or so 14:45:21 It's been fortunate that 3.3 has been delayed so much in one way - we'll be much closer to the start of the release cycle for 3.4 now 14:46:18 dneary: is that posted on the wiki anywhere? 14:46:30 * mburns doesn't want to info all of that 14:47:14 #info 6 talks in CloudOpen track of LinuxCon (requires separate registration to LinuxCon) 14:47:14 mburns, Not yet 14:47:33 #info 5 talks at KVM Forum on oVirt 14:47:48 By the way, the el6 release RPM http://resources.ovirt.org/releases/ovirt-release-el6-7-1.noarch.rpm gives a 404 (link from the 3.3 test day page) 14:48:01 #info 3 talks currently planned for developer meetings 14:48:12 dneary: oh, we revved it 14:48:32 http://resources.ovirt.org/releases/ovirt-release-el6.noarch.rpm 14:48:37 dneary: i'll fix the page shortly 14:48:43 $info 14:49:03 #info schedule still being worked for oVirt Dev Meetings 14:50:02 #info see full meeting transcript for details of what the presentations are 14:50:12 dneary: anything else? 14:50:38 mburns, We also have 2 oVirt related presentations in LinuxCon NA 14:50:56 #info 2 presentations at LinuxCon NA 14:50:59 I still do not have dates for a Raleigh workshop, but making some progress 14:51:11 dneary: oh, didn't realize we had anyone going to LCNA 14:51:18 * mburns tried, but his talk was not accepted 14:51:29 Private Cloud SLA - Greg Padgett 14:51:41 #info progress has been made on RTP workshop, but details not defined yet 14:51:43 And Theron Conrey had a talk accepted too (don't know if he plans to attend) 14:51:58 ah, cool 14:52:45 dneary: anything else? 14:53:14 We have a nice new user case study up on the site! 14:53:29 #info Case study added to the wiki 14:53:36 http://www.ovirt.org/Alter_Way_case_study 14:53:46 awesome 14:54:13 I am eager to have other volunteers - I'd love to showcase people using oVirt in small businesses, universities and research centers, hosting companies, or services companies deploying it for clients 14:54:30 Will pitch it on the users list after the release 14:54:32 dneary: karim might be someone to talk to 14:55:04 We're also working on the 3.3 promotion push. You can see our key talking points here: http://www.ovirt.org/OVirt_3.3_talking_points 14:55:25 #info 3.3 promotional push being worked on 14:56:27 mburns, karim? As a user, or a source of potential users? 14:56:41 dneary: as a user success story 14:57:25 * mburns moves on 14:57:27 #topic infra update 14:57:34 eedri: ewoud: updates? 14:57:40 #chair ewoud eedri 14:57:40 Current chairs: dneary eedri ewoud mburns oschreib 14:58:23 mburns, we have now enabled unit tests per patch for ovirt-engine patches 14:58:48 #info unit tests running per-patch for engine patches 14:59:02 mburns, new disks were installed on rackspace to allow new gluster storage (planned for backups & new jenkins slaves) 14:59:55 #info new storage added to rackspace servers 15:00:07 #info planned for backups and jenkins slaves 15:00:25 maybe ewoud can elaborate on puppet efforts done as well 15:00:49 not sure, there's much to report right now, but let's see 15:01:28 mburns, there are also plans to add new ovirt tools jobs soon 15:01:40 we have a puppet server with foreman and all hosts report. we've started to set up most of our base install now I think 15:01:47 #info plans for new ovirt tools jobs soon (image/iso uploader) 15:02:03 currently we're working on the deployment procedure to get changes in through gerrit to production 15:02:31 #info puppet/foreman running with all hosts reporting, base install mostly up and done 15:02:39 future steps would be to add more hosts (resources, lists, gerrit) and their configuration as well as monitoring 15:03:10 #info working on deployment procedure to get changes through gerrit to production 15:03:30 #info next steps: move more hosts to foreman (resources/lists/gerrit) 15:03:44 and documentation … 15:03:53 #info and documentation of the setup 15:04:08 eedri: ewoud: excellent 15:04:11 anything else? 15:04:30 mburns: not that I can think of now 15:04:39 ok, thanks for the update 15:04:43 #topic Other Topics 15:04:49 anyone have anything else to bring up? 15:05:22 going once... 15:06:23 twice.. 15:06:25 Hi: are you guys done meeting? 15:06:40 gone. 15:06:43 #info no other topics 15:06:47 #endmeeting