15:00:17 <mburns> #startmeeting oVirt Weekly Meeting
15:00:17 <ovirtbot> Meeting started Wed Feb 13 15:00:17 2013 UTC.  The chair is mburns. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:17 <ovirtbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:00:24 <mburns> #topic agenda and roll call
15:00:28 * lh here
15:00:32 <mburns> #chair dneary oschreib quaid
15:00:32 <ovirtbot> Current chairs: dneary mburns oschreib quaid
15:00:39 <mburns> Agenda:
15:00:48 <mburns> #info Release Status
15:00:54 <mburns> #info Workshops and Conferences
15:01:00 <mburns> #info Sub Project Reports
15:01:08 <mburns> #info Introducing theron
15:01:36 * mburns pauses for people to identify themselves
15:01:47 * Rydekull is here, listening
15:01:53 * oschreib here
15:02:51 * doron mostly here
15:03:02 * dustins here
15:04:13 <mburns> i'm going to mix up the agenda a bit
15:04:22 <mburns> to make sure we get to everything
15:04:26 <mburns> so we'll start with:
15:04:33 <mburns> #topic Workshops and Conferences
15:04:39 <mburns> lh: dneary:  any news here?
15:05:09 <lh> mburns, oVirt Shanghai workshop still on for 8-9 May 2013 at Intel Campus
15:05:24 <mburns> #info Shanghai Workshop still on for 8-9 May 2013
15:05:29 <lh> mburns, planning proceeds apace. I have a message into Susie Li on some logistical details needed before registration can be opened
15:05:42 <dneary> mburns, I asked Leslie to take over the co-ordination of the Intel hosted workshop in Shanghai in May - I have not been doing it justice
15:05:48 <lh> mbetak, and the CFP is in process (theron will have more on that when/after he is introduced)
15:06:05 <dneary> mburns, It's now in her (and Theron's) capable hands
15:06:21 <mburns> #info CFP in process, some logistical details still needed before registration can be opened
15:06:23 * dneary sees I was too slow
15:06:30 <mburns> dneary: ack
15:06:58 <mburns> hmm...maybe i should have done the introduction first...
15:07:09 <mburns> theron: want to give an update on the CFP?
15:07:22 <mburns> then we can have you introduce yourself in the next #topic
15:07:43 <theron> in progress is the best update at this point....
15:07:50 * mgoldboi here
15:07:56 <mburns> theron: ok
15:08:02 <vfeenstr> me too
15:08:06 * vfeenstr too
15:08:07 <vfeenstr> -_-
15:08:07 <mburns> lh: anything else to report?
15:08:15 <lh> mbetak, that's all i have
15:08:20 <lh> er
15:08:22 <lh> mbetak, sorry
15:08:25 <lh> mburns, that's all i have
15:08:39 <mburns> lh: thanks
15:08:49 <mburns> #topic Introducing theron
15:09:06 <mburns> lh: theron:  who is doing the honors?
15:09:12 <theron> I'll jump in.
15:09:21 <theron> My name is Theron Conrey, I'm new to the Carl Trieloff's team at Redhat, the open source and standards team, working primarily on oVirt support. Currently I'm working on the CFP with lh for Shangai, and Dave will busy mentoring me to get me up to speed on all things oVirt.  I'm coming from Nexenta where I was a solutions architect designing and implementing large scale cloud solutions.  I'm excited to join the community and help where I can.
15:10:02 <theron> feel free to pepper me with questions.
15:10:08 <doron> welcome theron
15:10:12 <theron> thanks!
15:10:13 <vfeenstr> Welcome :)
15:10:18 <lh> Folks who attended the oVirt workshop at NetApp HQ may have already had the opportunity to meet Theron at that time, as he was gracious enough to attend to get up to speed before he'd started officially at Red Hat.
15:10:19 <mburns> welcome!
15:10:19 <oschreib> welcome
15:10:36 <mburns> #info My name is Theron Conrey, I'm new to the Carl Trieloff's team at Redhat, the open source and standards team, working primarily on oVirt support. Currently I'm working on the CFP with lh for Shangai, and Dave will busy mentoring me to get me up to speed on all things oVirt.  I'm coming from Nexenta where I was a solutions architect designing and implementing large scale cloud solutions.  I'm excited to join the community and help where I can.
15:11:01 <mgoldboi> bienvenidos theron
15:11:17 <mburns> #chair mgoldboi ewoud
15:11:17 <ovirtbot> Current chairs: dneary ewoud mburns mgoldboi oschreib quaid
15:11:27 <mburns> ok, moving on
15:11:40 <mburns> theron: feel free to jump in with any thoughts you have
15:11:50 <mburns> #topic Infra Team Report
15:11:56 <mburns> ewoud: quaid:  any news?
15:12:25 <ewoud> #info we've fixed logins, now in the last planning phase before actually installing
15:13:05 <ewoud> trying to decide on how what software we're going to use (ovirt 3.1 or 3.2) now
15:13:05 <mburns> #info for the AlterWay servers ^^
15:13:23 <ewoud> #info set a deadline for next monday to decide on software
15:13:39 <ewoud> I think that's the most important news now
15:13:49 <dneary> mburns, I have a few updates here
15:14:16 <mburns> #info discussion on what software is happening on list
15:14:18 <mburns> dneary: go ahead
15:14:31 <dneary> I talked to Stéphane Vincent yesterday and asked about the possibility of having a console to access our VMs running on our second server
15:14:48 <dneary> He will check internally and get back to me before the weekend.
15:15:26 <dneary> The main issue is that they do not expose the user console to their cloud customers, so this would require them to do some set-up to provide us with a separate network and spin up & manage VMs for us
15:15:38 <mburns> #info dneary working on getting a console to access vms running on the second server
15:15:52 <mburns> dneary: if we use ovirt, then don't we get the console?
15:16:01 <mburns> since we have access to the first server?
15:16:09 <dneary> He will let me know what he is prepared to do - but it sounds like running it as an all-in-one and managing our own VMs through ovirt-engine might be our easiest option
15:16:34 <dneary> mburns, We have access to both servers
15:17:07 <ewoud> currently we have 2 dedicated servers, but if they already host oVirt it may be easier to just create VMs there in a quota
15:17:12 <mgoldboi> dneary, how many servers do we have there?
15:17:23 <mgoldboi> got it
15:17:24 <mgoldboi> 2
15:17:25 <dneary> mgoldboi, Two
15:17:35 <dneary> One other update: dcaro noticed that the servers were CentOS 5.8
15:17:38 <ewoud> but we could always migrate our VMs when that's possible and go for an all-in-one solution now
15:18:02 <mgoldboi> dneary, so all-in-one will restrict on the clustering/vm migration we can do there
15:18:04 <ewoud> dneary: Kevin is planning to reinstall tomorrow, pending our decission on CentOS 6 or Fedora
15:18:09 <dneary> I checked with kmazière whether there was a reason for it, and he assured me hat there wasn't - he can re-install the servers with CentOS 6.3
15:18:22 <dneary> ewoud, Ah, great! I missed that thread
15:18:41 <mburns> #info infra team working out deployment details
15:18:46 <ewoud> dneary: http://lists.ovirt.org/pipermail/infra/2013-February/002047.html
15:18:48 <dneary> mgoldboi, We could also install the engine on alterway01, and have VMs on alterway02
15:19:02 <mburns> #info hosts currently are centos 5.8, will be centos 6.3 or f18 when infra team decides what to use
15:19:39 <ewoud> discussion is on the infra mailing list if anyone is interested
15:20:45 <mburns> great, anything else from the infra team?
15:21:26 <dneary> ewoud, I see no reason to revisit the previous discussion about the OS to use - we should use CentOS 6.3
15:21:46 <dneary> That's what we agreed in December
15:22:08 <mgoldboi> dneary, not such a clear cut- we should aim there, but right now we aren't packaging 3.2 for it
15:22:09 <ewoud> dneary: mburns said earlier that CentOS may not be that well tested, but I'd prefer CentOS on a server over Fedora
15:22:46 <mburns> i think we should make every effort to run on centos if possible
15:22:58 <dneary> ewoud, I think most of our users would prefer RHEL or CentOS too
15:23:09 <ewoud> mburns: could you (get someone to) package ovirt 3.2 (beta) for EL6?
15:23:13 <ewoud> http://resources.ovirt.org/releases/beta/rpm/ doesn't list it
15:23:23 <mgoldboi> mburns, +1 effort is being done, oschreib is on the making of it
15:23:33 <mburns> ewoud: that's more mgoldboi and oschreib
15:23:48 <mburns> and not sure who is doing the vdsm side of it
15:24:05 * Rydekull really suggest stop discussing OS and just go with CentOS.
15:24:07 <mburns> fsimonce`: do you know if anyone is working on el6 rpms for vdsm for 3.2?
15:24:27 <ewoud> Rydekull: yes, then we need packages :)
15:24:30 <fsimonce`> mburns, what rpm exactly?
15:24:44 <mburns> fsimonce`: all vdsm rpms
15:24:48 <oschreib> Well, there's ovirt-engine at http://www.dreyou.org/ovirt/
15:24:55 <oschreib> (not official by us, though)
15:25:06 <mburns> oschreib: we should try to use our packages if at all possible
15:25:22 <mburns> the dreyou packages are good, but they're a hybrid mix of some 3.1 and some 3.2 stuff
15:25:30 <mburns> won't be upgradable
15:25:30 <fsimonce`> mburns, no, we *cannot* do that... we cannot provide vdsm in el6 they would override rh* downstream packages
15:26:06 <fsimonce`> mburns, as long as I know there are only hooks there
15:26:16 <oschreib> mburns: I don't see how "our own" .el6 build will be much different
15:26:16 <dneary> fsimonce`, I believe the plan is to do just that
15:26:24 <fsimonce`> mburns, anyway as far as I know there should be a jenkins job
15:26:35 <oschreib> mburns: I didn't see any 3.1/3.2 hybrid code in the engine.
15:26:36 <mburns> fsimonce`: i'm not talking about epel -- these are for people using centos
15:26:55 <ewoud> there's nightly vdsm RPMs
15:27:08 <ewoud> they just have to be available in our beta repo as well
15:27:28 <fsimonce`> mburns, the ovirt repo should be as far as I know fully automated by jenkins build
15:27:31 <mburns> ewoud: ok, then we just need to use that to create versions of our beta packages
15:27:40 <mburns> fsimonce`: not beta and ga
15:27:51 <mburns> those are manually built (or built in koji for Fedora rpms)
15:28:01 <mgoldboi> oschreib, it will be different by the fact we are officially releasing it, and we need to build nighties with it
15:28:24 <mburns> ok, let's take this out of the meeting -- i'll follow up with it today
15:28:55 <mburns> #action mburns to follow up on getting el6 rpms available in 3.2 repository
15:29:17 <mburns> that's going to bring us to the release status
15:29:17 <fsimonce`> mburns, the fedora 18 build is "stable" as far as I'm concerned... nobody pinged me about any blocker
15:29:35 <mburns> fsimonce`: right, and we have that build in our repositories now
15:30:03 <mburns> fsimonce`: we're just looking for an el6 version of that build...
15:30:07 <fsimonce`> mburns, that's the same that should have been built for el6 (I suppose by an ovirt jenkins job)
15:30:13 <eedri> asaf, ping
15:30:21 <mburns> fsimonce`: i'll check after this meeting
15:30:27 <fsimonce`> mburns, we cannot build that on koji as it would end up in epel
15:30:35 <mburns> and see if I can build it using the jenkins job
15:30:44 <fsimonce`> mburns, that's why it has to be an ovirt.org local build
15:30:50 <mburns> fsimonce`: right
15:31:02 <mburns> we're just not using jenkins as our official build system quite yet
15:31:30 <mburns> #topic release status
15:31:47 <oschreib> let the fun begin
15:31:50 <mburns> ok, so a quick review of where we are right now
15:32:00 <mburns> ovirt-node is available and posted as of last night
15:32:10 <mburns> i've confirmed that it works with the current engine build
15:32:13 <mgoldboi> mburns, congrats
15:32:17 <vfeenstr> The oVirt Guest Agent has now been officially accepted as package. Please find the package Database Entry: https://admin.fedoraproject.org/pkgdb/acls/name/ovirt-guest-agent
15:32:20 <vfeenstr> Current status can be reviewed here:
15:32:22 <vfeenstr> For Fedora 17: https://admin.fedoraproject.org/updates/ovirt-guest-agent-1.0.6-4.fc17
15:32:25 <vfeenstr> For Feodra 18: https://admin.fedoraproject.org/updates/ovirt-guest-agent-1.0.6-4.fc18
15:32:30 <vfeenstr> as package in Fedora ;)
15:32:35 <mburns> and have nfs guests running
15:32:42 <mburns> vfeenstr: excellent
15:32:43 <mgoldboi> oschreib, did you get dwh/reports packages for 3.2 release?
15:33:08 <mburns> engine packages for f18 are available in the beta repo now and can go to GA as well
15:33:18 <oschreib> mgoldboi: I got them today
15:33:22 <mburns> unless something came up in the last 24 hours...
15:33:25 <oschreib> I'm uploading them atm
15:33:35 <oschreib> wait guys
15:34:07 <oschreib> there are 3 new patches in engine_3.2 (committed after last Friday, in which I uploaded the new version)
15:34:20 <mburns> oschreib: so we need a new build?
15:34:52 <mgoldboi> oschreib, let's go over the bugs
15:35:19 <oschreib> mburns: I suspect so
15:35:28 <oschreib> mgoldboi: and the gluster thingy isn't in yet
15:35:43 <mgoldboi> mburns, http://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+branch:engine_3.2,n,z
15:36:37 <mburns> ok, so these are obviously important since they got into 3.2
15:36:50 <mburns> what's the gluster thing that isn't in yet?
15:37:00 <mgoldboi> mburns, verification
15:37:07 <mgoldboi> mburns, i'll push it
15:37:18 <mburns> mgoldboi: is there risk in the change?
15:37:30 <mburns> we're supposed to be shipping today
15:37:36 <mburns> (or tomorrow at the latest)
15:37:56 <mgoldboi> mburns, risk is always there, but it's already merged in master
15:38:01 <mburns> and we have 3 patches and this gluster issue that are not merged yet
15:38:11 <mburns> which means no build yet, which means no release
15:38:24 <mburns> unless we say that they can go in an async update
15:38:28 <oschreib> if we're uploading new build, we can't release in 1 fday
15:38:42 <oschreib> we should give it few days to see if anything comes up
15:39:04 <mburns> and then another few days when something does come up
15:39:09 <mgoldboi> let's release and go async with what we are left with
15:39:12 <mburns> how critical are these patches?
15:40:04 <oschreib> Fix for file.tlv.redhat.com:/home/tlv/ydary/ovirt-3.2-rpms
15:40:07 <oschreib> ops
15:40:16 <oschreib> fix for https://bugzilla.redhat.com/show_bug.cgi?id=908392
15:40:25 <oschreib> fix for https://bugzilla.redhat.com/show_bug.cgi?id=902242
15:40:41 <oschreib> fix for https://bugzilla.redhat.com/906291
15:40:47 <oschreib> (that's what the commit says)
15:41:29 <mburns> 906291 is the only one that sounds like a blocker to me...
15:41:45 <mburns> but i think even that could go async
15:41:47 <mgoldboi> mburns, +1
15:41:54 <oschreib> +1
15:42:33 <mburns> ok, so no more blocker issues with any of the major components
15:42:49 <mburns> so we just need to get the reports/dwh stuff uploaded and flip some links around
15:43:02 <mburns> maybe do some cleanup of the releases area as well
15:43:08 <oschreib> since uploading dwh/reports takes some time
15:43:24 <oschreib> I suggest that we will prepare everything
15:43:27 <mburns> if guest-agent is now in fedora, can we drop it from the ovirt repos?
15:43:43 <oschreib> mburns: yes, if this build is in Fedora18
15:43:52 <mburns> bah, it's in testing still
15:43:56 <oschreib> mburns: and release it tomorrow
15:44:04 <mgoldboi> mburns, not sure actually
15:44:06 <mburns> if people give karma, then we can drop guest-agent
15:44:26 <mburns> oschreib: +1 on releasing tomorrow
15:44:47 <mburns> oschreib: i'll create a new directory on resources and get the right content there
15:44:49 <mgoldboi> mburns, ovirt suppose to be upstream while fedora is additional distro
15:45:11 <mburns> and we can simply drop in reports/dwh when it's uploaded
15:45:11 <mgoldboi> mburns, srpms should be in ovirt anyhow
15:45:20 <mburns> mgoldboi: src tarballs, yes
15:45:40 <mgoldboi> mburns, correct
15:45:47 <mburns> mgoldboi: i'm fine with continuing to carry the guest agent rpms as well
15:46:41 <mgoldboi> mburns, can you summarize all action items for the release
15:47:19 <mburns> #action mburns to create release repo in resources.ovirt.org
15:47:31 <mburns> #action mburns to get latest packages moved over from current beta repo
15:47:44 <mburns> #action mburns to get guest-agent rpms and source from koji and upload
15:47:55 <mburns> #action oschreib to get dwh/reports rpms uploaded
15:48:02 <mburns> #action mburns to write announcement
15:48:23 <mburns> #action mburns to look into vdsm on el6
15:48:35 <mburns> mgoldboi: oschreib:  who is doing el6 for engine?
15:49:01 <oschreib> mburns: I'm taking care of it, although it might take some time
15:49:20 <mburns> #action oschreib to work on el6 engine rpms
15:49:24 <karim> sgordon_, thank you!
15:49:33 <mburns> oschreib: ok, something we can update as we go...
15:49:34 <sgordon_> karim, ?
15:49:55 <mburns> mgoldboi: oschreib:  anything i'm forgetting?
15:49:56 <karim> sgordon_, the bugzilla regarding attach of cdrom when vm s online!
15:50:02 <mgoldboi> mburns, regarding the missing patches
15:50:27 <mburns> #action mgoldboi and oschreib to work on remaining 3.2 engine patches and post new build async
15:50:35 <fabiand> rbarry, nice to see your first patch :)
15:50:47 <mburns> hmm...we need to update some wiki pages too
15:51:09 <mgoldboi> mburns, do we have a list of them?
15:51:16 <mburns> i don't
15:51:27 <mburns> the 3.2 release page is one
15:51:35 <mburns> the getting ovirt page is another
15:51:45 <mburns> we should probably have an announcement on the front page as well
15:52:23 <mburns> #action mburns to review wiki/website updates that are needed
15:52:33 <mgoldboi> mburns, who has permissions on home page?
15:52:49 <mburns> mgoldboi: i don't know, but i'll harass dneary until i do
15:52:55 <Rydekull> haha
15:53:05 <dneary> mburns, The oVirt home page?
15:53:11 <mburns> dneary: yes
15:53:12 <dneary> Anyone in the admin group for the wiki
15:53:25 <rbarry> fabiand: It is, isn't it?  Even if it's quite terse.
15:53:43 <mburns> dneary: what do i need to do to get into the admin group?
15:53:56 <fabiand> rbarry, In my opinion those are the best ones :)
15:55:06 <dneary> http://www.ovirt.org/index.php?title=Special%3AListUsers&username=&group=sysop&limit=50
15:55:42 <mburns> dneary: yes, that's the list of people currently in the group
15:55:47 <mburns> how do i join the group?
15:56:11 * mburns writes a cron job to spam dneary and quaid every 5 min until he gets access...
15:56:19 <mburns> ;-)
15:56:24 <dneary> mburns, reload that page
15:56:42 <mburns> dneary: woot!
15:56:43 <mburns> thanks
15:56:47 * mburns cancels cron job
15:57:02 <mburns> ok, so anything else to discuss?
15:57:09 <mburns> either release specific or in general?
15:57:12 * dneary thanks mburns turning off the spam cron job
15:57:45 <mburns> if nothing else, /me will #endmeeting
15:57:48 <mburns> going once...
15:57:59 <mgoldboi> mburns,
15:58:10 <mgoldboi> so just to be clear we are targeting release tomorrow
15:58:11 * mburns stops countdown
15:58:16 <mburns> mgoldboi: yes
15:58:24 <mburns> #info release targeted to be announced tomorrow
15:58:33 <mburns> though, i hope to have most of it ready to go today
15:58:35 <mgoldboi> mburns, all action items should be resolved by EOD tomorrow
15:58:51 <mburns> ack
15:58:58 <mgoldboi> ack from my side as well
15:59:09 <sgordon_> karim, oh right - i actually did that yesterday but bugzilla mail is having a bit of a go slow
15:59:22 <oschreib> mburns: sgordon_: any PR around 3.2?
15:59:49 <sgordon_> heh, cheryn and team did release notes i believe - i dont have anything else afaik
16:00:08 <mgoldboi> sgordon_, while you are temporary here - docs rpm?
16:00:16 <sgordon_> what docs rpm?
16:00:22 <sgordon_> :P
16:00:29 <sgordon_> (seriously)
16:01:21 <mgoldboi> sgordon_, http://gerrit.ovirt.org/gitweb?p=ovirt-docs.git;a=shortlog;h=refs%2Fheads%2Fmaster
16:01:49 <sgordon_> mgoldboi, the only thing in that repo is the 3.0 install guide
16:02:25 <sgordon_> mgoldboi, i was dissuaded from pursuing that and we elected to use the quick start in wiki that jbrooks created
16:02:48 <mgoldboi> sgordon_, ok
16:03:09 <mburns> ok, so we need a review of the quick start in the wiki, as well
16:03:10 <sgordon_> (fwiw we never delivered that as an rpm anyway, just a pdf)
16:03:20 <mburns> mgoldboi: can you review the quickstart?
16:03:22 <oschreib> mburns: mgoldboi: reports/dwh uploaded and in 3.2 dir
16:03:31 <mburns> oschreib: excellent, thanks
16:03:33 <mgoldboi> mburns, sure
16:03:49 <mburns> #action mgoldboi to review/update the quick start guide for 3.2
16:03:54 <sgordon_> # link http://www.ovirt.org/Quick_Start_Guide
16:04:09 <mburns> #link http://www.ovirt.org/Quick_Start_Guide
16:04:22 <mburns> anything else?
16:05:05 <oschreib> mburns: once again, PR?
16:05:26 <mburns> what have we done in the past?
16:05:35 <mburns> blog posts? twitter? etc?
16:05:41 * mburns wasn't involved in any of that
16:06:01 <oschreib> mburns: sgordon_ and someone which I don't remember took care of it.
16:06:15 <mburns> probably jbrooks
16:06:19 <oschreib> indeed
16:06:32 <jbrooks> I'll be blogging, and tweeting
16:06:44 <mburns> excellent
16:06:46 <mburns> thanks jbrooks
16:07:00 <mburns> anything else we need aside from the wiki stuff and email announcement that i'll be sending?
16:07:19 <mburns> #action mburns to update irc channel topic as well
16:08:01 <jbrooks> I don't think we'll need other materials, but the more community members who can take part in the blogging/word spreading, the better
16:08:27 <mburns> ok, great
16:08:45 <mburns> #action All Community Members to tweet/blog/spread the word
16:08:51 <oschreib> :)
16:09:05 <mburns> (but only if they have good things to say!)
16:09:20 <mburns> ok, last call for topics
16:09:22 <mburns> going once...
16:10:56 <theron> thanks mburns and all for the warm welcome!
16:11:08 <mburns> twice..
16:11:11 <mburns> theron: ;-)
16:11:51 <mburns> gone.
16:11:53 <mburns> thanks all
16:11:56 <mburns> #endmeeting