15:01:05 <quaid> #startmeeting
15:01:05 <ovirtbot> Meeting started Mon Oct 15 15:01:05 2012 UTC.  The chair is quaid. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:05 <ovirtbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:01:09 * mburns here
15:01:23 <quaid> #meetingname oVirt Infra weekly sync
15:01:23 <ovirtbot> The meeting name has been set to 'ovirt_infra_weekly_sync'
15:01:26 * ewoud here
15:01:36 <quaid> #topic rollcall & agenda check
15:01:40 * quaid is here too
15:01:52 <quaid> anyone with anything to add to the agenda?
15:02:01 <quaid> #chair mburns ewoud
15:02:01 <ovirtbot> Current chairs: ewoud mburns quaid
15:02:12 * SirDerigo leaves so he wont disturb the meeting
15:02:34 * quaid on his way to full console to get agenda URL
15:02:57 * eedri here
15:03:08 <ewoud> ping RobertM
15:03:22 <mburns> #link http://wiki.ovirt.org/wiki/Infrastructure_team_meetings#2012-10-15
15:03:26 <RobertM> ewoud, Yes
15:03:27 <mburns> quaid: ^
15:03:36 <ewoud> mburns: I just opened it as well :)
15:03:50 <ewoud> #chair eedri RobertM
15:03:50 <ovirtbot> Current chairs: RobertM eedri ewoud mburns quaid
15:03:58 <SirDerigo> mburns, can you check my log ? http://pastebin.com/bxJmDtmR
15:04:31 <mburns> SirDerigo: is that engine.log?
15:04:38 <SirDerigo> mburns, yes
15:04:51 <SirDerigo> i created the nfs domain with the installer
15:05:06 <mburns> SirDerigo: can you get the vdsm.log from the host you using to import/create the iso domain?
15:05:14 <mburns> SirDerigo: ahh...
15:05:34 <SirDerigo> mburns, what?
15:05:51 <mburns> SirDerigo: nvm, didn't realize you were creating from the installer
15:05:58 <ewoud> quaid: ping?
15:05:58 * mburns will look after the meeting
15:06:13 * quaid is back
15:06:28 <quaid> http://wiki.ovirt.org/wiki/Infrastructure_team_meetings#2012-10-15
15:06:43 <quaid> sorry, I was moving between travel & home
15:06:57 <quaid> ''Agenda''
15:06:57 <quaid> * MediaWiki & www
15:06:57 <quaid> * Hosting
15:06:57 <quaid> * Trac review
15:06:57 <quaid> * Puppet
15:06:59 <quaid> * Jenkins
15:07:02 <quaid> * Gerrit
15:07:05 <quaid> * Infra presentation at oVirt Workshop -- Barcelona
15:07:07 * quaid likes to have the actual agenda in the log :)
15:07:09 <quaid> ok, moving along
15:07:17 <quaid> #topic MediaWiki & www
15:07:50 <quaid> #info MW *still* not upgraded; quaid has failed to find the right window & stick to it
15:08:03 <ovirtbot> 14[[07CLI14]]4 !10 02http://wiki.ovirt.org/w/index.php?diff=4728&oldid=4551&rcid=4843 5* 03Michael Pasternak 5* (-4) 10
15:08:11 <quaid> I'm willing to try again today, depending on how the visit to the DMV goes (timing)
15:08:38 <quaid> or we have the wiki offline for a few hours for developers workday
15:08:56 <ovirtbot> 14[[07CLI14]]4 !10 02http://wiki.ovirt.org/w/index.php?diff=4729&oldid=4728&rcid=4844 5* 03Michael Pasternak 5* (-5) 10
15:09:10 <quaid> #info wiki may be offline for a few hours during Tel Aviv workday due to challenge of finding compatible time
15:09:25 <quaid> #action quaid to announce a new downtime window with as much lead time as he can get
15:09:33 <mburns> quaid: EOD US would seem to make the most sense
15:09:44 <quaid> mburns: ah, but whose EOD :)
15:09:52 <quaid> but yes, that's the target
15:10:01 <mburns> quaid: or even better -- friday morning
15:10:09 <quaid> I've just found that same window for me is rife with "life interrrupts"
15:10:10 <mburns> or friday during TLV day
15:10:29 <quaid> yeah, that's the one I was going to try last Friday, but it didn't happen
15:11:09 <quaid> certainly Friday morning Pacific time is one possibility - East US doesn't seem to do as much past Noon :)
15:11:29 <eedri> jenkins server also needs upgrading to latest version, but i guess it's windows is more flexiable
15:11:32 <quaid> ok, and otherwise
15:12:38 <quaid> #info quaid has control of *-ovirt.rhcloud.com namespace with extra enough slots to put our services, once the upgrade is done the mirror with new theme can be created at wiki-ovirt.rhcloud.com
15:12:58 <quaid> I'm loathe to bug garrett_ for updates since he's waiting on me
15:13:10 <quaid> #chair eedri
15:13:10 <ovirtbot> Current chairs: RobertM eedri ewoud mburns quaid
15:13:29 <quaid> anything more here?
15:13:31 <ewoud> quaid: already did that
15:13:36 <quaid> sorry, didn't notice :)
15:13:51 <ewoud> ok, any more about mediawiki?
15:13:52 <mburns> quaid: my preference would be to do it after wednesday
15:14:12 <mburns> there is a request out to create feature pages before the wednesday project meeting
15:14:20 <mburns> so i'd like to avoid downtime before then
15:14:29 <mburns> so i think scheduling for this friday makes the most sense
15:14:43 <ewoud> friday is israel free as well, right?
15:15:07 <mburns> yes
15:15:11 <quaid> mburns: ok, I think we can do that, if you all don't mind the wiki being down Friday after Noon
15:15:12 <mburns> (mostly)
15:15:21 <mburns> no issues here
15:15:36 <quaid> mburns: I can do an offline upgrade of a snapshot of the data to test the process, and use that as a test mirror, so I can pre-check my process before Friday
15:16:14 <quaid> #action quaid to do upgrade on Friday after Wed feature meeting-topic (so wiki is available for making feature pages)
15:16:33 <quaid> #action quaid to test upgrade process with snapshot & new mirror test on OpenShift
15:17:21 <quaid> ok, ready to move on?
15:17:53 <quaid> silence = consent
15:18:01 <quaid> #topic Hosting
15:18:11 <quaid> dneary: are you available for hosting update?>
15:18:24 <quaid> #info quaid is still working with RHT IT on additional hosting requirements
15:19:18 <ewoud> that feels like a no
15:20:07 <quaid> #info quaid & itamar discussed risk of moving Gerrit & downtime potentials (before, during, after); both  are recommending that we stagger the move of Gerrit until after Infra has stabilized its relationship and proceeses with hosting sponsor Alter Way
15:21:08 <quaid> that's all for now then
15:21:18 <ewoud> so what would be first? I think jenkins would be the least critical?
15:21:19 <mburns> quaid: i agree with holding on gerrit until after jenkins is stable
15:21:30 <mburns> if jenkins goes down, we can survive
15:21:38 <mburns> but if we lose gerrit, we come to a complete stop
15:21:40 <quaid> ewoud: moving Jenkins is the main goal, I think - getting the better server, etc.
15:21:44 <eedri> agree
15:21:45 <quaid> mburns: exactly
15:22:05 <ewoud> mailing lists are almost as critical as gerrit?
15:22:23 <quaid> #agreed Infra team agrees on holding on Gerrit move unitl after Jenkins is stable, etc.
15:22:35 <ovirtbot> 14[[07SLA-mom14]]4 !N10 02http://wiki.ovirt.org/w/index.php?oldid=4730&rcid=4845 5* 03Doron 5* (+2341) 10Created page with "<!-- {{autolang|base=yes}} -->  == SLA: MoM integration <!-- The name of your feature --> ==  === Summary === <!-- A sentence or two summarizing what this feature is and what it ..."
15:22:41 <quaid> ewoud: yes, critical, but much less finicky
15:23:05 <ewoud> ok, next topic?
15:23:09 <quaid> ayup
15:23:17 <quaid> #topic Trac ticket review
15:23:38 * quaid is looking :)
15:23:53 <quaid> https://fedorahosted.org/ovirt/report/1
15:24:26 <quaid> https://fedorahosted.org/ovirt/ticket/3 is in progress and reported on - MediaWiki upgrade
15:24:38 <quaid> https://fedorahosted.org/ovirt/ticket/4 is dependent on #3
15:24:47 <quaid> here's a question:
15:25:03 <quaid> does anyone here know Trac well enough to write a basic how-to file a ticket?
15:25:20 <quaid> we need to instruct other contributors (especially) on how we want to interact with them via Trac
15:25:39 <ewoud> been a while since I've mainted a trac instance, but I could look into it again
15:25:47 <dneary> quaid, My apologies
15:25:50 <quaid> https://fedorahosted.org/ovirt/ticket/5 is currently unowned
15:25:58 <dneary> quaid, I was here, but missed your call
15:26:19 <quaid> dneary: do you have anything we need to switch topics back for? happy to, in just a moment
15:26:31 <quaid> (re:hosting or other topic)
15:26:36 <mburns> quaid: can we get alerts of new tickets sent to infra@
15:26:36 <mburns> ?
15:26:52 <quaid> mburns: I presume we need to add a rule to Mailman, yes I like the idea
15:27:03 <quaid> infra@ is the default for all new tix currently
15:27:07 * quaid looks
15:27:21 <mburns> quaid: that way we all know when a new ticket is filed
15:27:31 <mburns> rather than waiting a week for this meeting
15:27:32 <quaid> +1
15:27:51 <quaid> yep, that's why I set that as default, but hadn't looked at Mailman side
15:28:00 <mburns> would probably also be good to have someone who is in charge of triaging tickets and making sure that they get picked up
15:28:12 <mburns> though we can probably do that on the weekly...
15:29:00 <quaid> we can see how it develops, we'll naturally have a workflow of someone grabbing the ticket on list or it being obvious no one has grabbed it
15:29:36 <quaid> ewoud: is your FAS username 'ewoud'
15:29:42 <dneary> quaid, no - nothiong hugely new since last week
15:29:45 <ewoud> quaid: ekohl
15:30:15 <quaid> #action ewoud taking over #5 to give it a first draft
15:30:24 <dneary> quaid, The board approved hosting move to AlterWay, I did an interview in French with the director of R&D from AlterWay at the Open World Forum, and we still need to nail down the details
15:30:46 <quaid> hmm, that's worth putting in the record, so let's do that in a second
15:30:59 <quaid> ok, anything more on Trac tickets?
15:31:05 <ewoud> quaid: I also created #6 and assigned it to myself
15:31:15 <dneary> quaid, I was wondering when the name change for the mailing list might get done - is that something we can add to this week's things to get done? Or are you waiting until we move Mailman?
15:31:29 <quaid> ewoud: sweet, thanks
15:31:53 <dneary> quaid, re Gerrit move, I would suggest doing it in two stages!
15:31:57 <dneary> s/!/:
15:32:09 <quaid> dneary: topic, plz
15:32:23 <dneary> Sorry. Still catching up with backlog
15:32:28 <quaid> ah, I see
15:32:29 <ovirtbot> 14[[07OVirt 3.2 release-management14]]4 !10 02http://wiki.ovirt.org/w/index.php?diff=4731&oldid=4722&rcid=4846 5* 03Doron 5* (-16) 10
15:32:39 <quaid> eedri: can you create a ticket for the Jenkins upgrade?
15:32:50 <eedri> quaid, sure
15:32:52 <quaid> ok, moving on with a quick U-turn
15:32:58 <quaid> #topic Hosting take deux
15:33:10 <quaid> #info Board has approced Alter Way hosting
15:33:42 <quaid> #info dneary interviewed Alter Way Dir of R&D about their oVirt plans at OWF
15:33:59 <quaid> #info Hosting details need to be defined
15:34:13 <quaid> #idea do Gerrit moving in two stages
15:34:36 <quaid> dneary: can you explain what you mean by two stages (feel free to use #info and #idea liberally)
15:35:47 * quaid waits a moment for dneary to catch up on backlog
15:35:53 <ewoud> quaid: approced = approved?
15:36:07 <dneary> quaid, My #idea was to basically do it like a live migration: set up a separate gerrit instance, mirror the live one, then switch when you're sure it's all OK
15:36:09 <quaid> ewoud: oops, yes
15:36:23 <quaid> dneary: I think you need to lead the line with the command #idea, sorry
15:36:32 <quaid> #info s/approced/approved/g
15:37:18 * eedri created trac #7 to update jenkins
15:37:26 <quaid> #idea look in to Gerrit replication services - is there any concept of a cluster or mirror?
15:37:27 <dneary> #idea Step 1 for gerrit migration. Clone git repos  (if we need to), set up new gerrit instance, clone data from live Gerrit
15:38:10 <dneary> #idea Step 2: Set "old" gerrit read-only, sync any comments/changes that need it, set "new" gerrit live
15:38:33 <ewoud> if we could host read only git repos off-site it would be a big advantage IMHO, even after we migrate
15:38:59 <dneary> That's all - the upside is that you only lose a few minutes while you're syncing changes made since you cloned the old gerrit instance's DBs, and while you test that the new gerrit is behaving reasonably
15:39:09 <ewoud> maybe we can get a permanent github clone going?
15:39:45 <ewoud> #idea mirror git repos to github
15:40:11 <dneary> quaid, Have I missed something obvious?
15:40:14 <quaid> +1
15:40:31 <quaid> dneary: I think that's it
15:40:43 <mburns> ewoud: some projects have that already
15:40:48 * mburns has ovirt-node on github
15:40:52 <mburns> though only master branch
15:40:53 <quaid> dneary: the question then is one of when we do that, which is "after we've moved Jenkins and Mailman and have them stable"
15:40:55 <mburns> and it syncs weekly
15:41:06 <mburns> (or rather i try to remember to sync it weekly)
15:41:07 <quaid> mburns: how hard is it to do that sync?
15:41:08 <ewoud> mburns: maybe that's something we can expand
15:41:11 <quaid> ah, manual!
15:41:20 <ewoud> mburns: and please get a higher resolution image for the profile :)
15:41:29 <mburns> quaid: git push github gerrit/master:master
15:41:46 <quaid> mburns: so we could script that to run as a cronjob on git.ovirt.org?
15:42:07 <dneary> mburns, I believe that there's a recipe to do post-commit pushes to a github clone somewhere...
15:42:09 <quaid> #idea script github push to happen as a daily cronjob on git.ovirt.org
15:42:10 <mburns> quaid: potentially, just need to setup the remotes correctly
15:42:17 <mburns> dneary: probably
15:42:43 <mburns> it's not overly onerous to push up a single repo
15:42:49 <mburns> so i never bothered automating
15:43:00 <dneary> mburns, As long as you're the only one pushing :)
15:43:12 <mburns> if we end up expanding, then we need something more
15:43:14 <mburns> dneary: i am
15:43:33 <mburns> well, jboggs and apevec can push too, i think
15:43:34 <quaid> well, we just want to cover the "hit by a raptor" factor
15:43:38 <mburns> but no one does
15:44:13 <quaid> I'll make a ticket, we'll get it done by someone
15:44:39 <ovirtbot> 14[[07Features/Quota-3.214]]4 !N10 02http://wiki.ovirt.org/w/index.php?oldid=4732&rcid=4847 5* 03Doron 5* (+1777) 10Created page with "<!-- {{autolang|base=yes}} -->  == SLA: Quota in 3.2 <!-- The name of your feature --> ==  === Summary === <!-- A sentence or two summarizing what this feature is and what it wil..."
15:44:48 <ewoud> I wonder who maintains https://github.com/gerrit-ovirt-org
15:46:06 <quaid> ewoud: I think that's the Engine team
15:46:59 <quaid> ok, ready to move on ...
15:47:10 <ovirtbot> 14[[07OVirt 3.2 release-management14]]4 !10 02http://wiki.ovirt.org/w/index.php?diff=4733&oldid=4731&rcid=4848 5* 03Doron 5* (+52) 10
15:47:12 <quaid> #topic Puppet & Foreman
15:47:16 <mburns> we can certainly add repos to the oVirt account
15:47:32 <mburns> oops...out of context...
15:47:52 <quaid> mburns: I'll have the ticket in a moment, we can add comments on how-to there :)
15:47:58 <quaid> https://fedorahosted.org/ovirt/ticket/6
15:48:13 <quaid> ewoud: anything about Puppet for the meeting?
15:48:14 <ewoud> I'd like to start fresh when we start on Alter Ways
15:48:30 <ewoud> so we only install servers using puppet
15:49:03 <quaid> +1
15:49:12 * eedri thinks we should try to manage jenkins from puppet as well
15:49:25 <quaid> mburns: https://fedorahosted.org/ovirt/ticket/8 for Git
15:49:27 <eedri> thinks like plugin versions, slaves,etc...
15:49:48 <ewoud> so if we make a timeline we'd start with a VM for foreman, provision that using the foreman-installer modules
15:49:59 <ewoud> next step would be to start building a jenkins server
15:50:29 <ewoud> https://github.com/rtyler/puppet-jenkins could be the basis for that
15:51:22 <quaid> #agreed Use Puppet for deploying all new services on Alter Way
15:51:59 <ewoud> not sure how we're going to manage the git flow
15:52:03 <quaid> #idea we can manage Jenkins from Puppet
15:52:26 <eedri> ewoud, exactly
15:52:42 <ewoud> but I'd prefer to start building the basis without gerrit and then import the git repo in gerrit once it's running
15:53:13 <eedri> btw, if we manage our own dhcp/dns. foreman can manage them and create vms automaticly
15:54:24 <ewoud> yes, I'd like our own VLAN and IP space there
15:54:38 <ewoud> have we discussed anything there?
15:54:56 * mburns will brb
15:55:51 <ewoud> #idea manage our own IP and DNS from foreman
15:55:57 <ewoud> dneary: ^
15:56:04 <quaid> #idea puppet can manage versions, slaves, etc.
15:56:23 <quaid> #info next step is to build a jenkins server
15:56:38 <quaid> #info how to manage the git flow?
15:57:26 <quaid> #idea build the basis without gerrit and then import the git repo in gerrit once it's running
15:57:45 <ewoud> also, what's the time frame we can expect to start building servers there?
15:57:46 <quaid> #info if we manage our own dhcp/dns, Foreman can manage them and and create VMs automatically
15:58:00 <mburns> +1 from me on building first, then import to gerrit when it's working
15:58:03 <quaid> #idea it would be good to ahve our own VLAN and IP space at Alter Way
15:58:30 <mburns> easier than having to post/ack/review/push until it's up and running
15:58:35 <mburns> once stable we want that process
15:59:20 <ewoud> yes, and we need to look at how we manage the private data
15:59:39 <ewoud> because ssl private keys shouldn't be public on gerrit
16:00:27 <ewoud> anything else?
16:00:29 * ewoud looks at the time
16:01:04 <quaid> yeah, sorry, distracted myself
16:01:16 <quaid> #topic Jenkins
16:01:19 <quaid> Anything here?
16:01:31 * ewoud looks at eedri and RobertM
16:01:39 <quaid> yeek, I should just let you all go
16:01:47 <eedri> yea
16:01:50 <eedri> RobertM, here?
16:02:06 <eedri> i was asked about status for jenkins.ovirt.info, any update on reviving it?
16:02:42 <quaid> we'll wait a moment
16:02:50 <RobertM> Sorry Guys I am out of town and not really around
16:02:57 <eedri> ok
16:03:12 <eedri> then i suggest to wait till we migrate jenkins to the new server
16:03:21 <ewoud> .info is a hack until we .org more power, right?
16:03:21 <ovirtbot> ewoud: Error: "info" is not a valid command.
16:03:27 <eedri> and then adding the gerrit patches jobs again
16:03:29 <ewoud> ovirtbot: botsnack
16:03:29 <ovirtbot> ewoud: Error: "botsnack" is not a valid command.
16:03:34 <eedri> current jenkins server can't handle the load
16:03:35 <ewoud> bad bot
16:03:50 <eedri> ewoud, correct
16:03:56 <eedri> ewoud, there should be only one master server
16:03:58 <dneary> ewoud, quaid: Anything is possible with Alter Way. Hervé asked whether we would need our own network firewalled away from the rest of the world - I thought we did not.
16:04:28 <quaid> dneary: a private network? I could see us wanting to pass e.g. database traffic on a VPN
16:04:30 <ewoud> dneary: I like a private VLAN with some public IP space
16:04:31 <dneary> quaid, Just let them know what you'd like to have, and as long as it does not put huge demands on their network engineers, I'm sure they'll consider it
16:04:43 <quaid> +1 to ewoud said
16:04:43 <ewoud> and by private I mean non-shared
16:05:00 <dneary> quaid, ewoud: Let's ask them what's possible
16:05:26 <ewoud> dneary: also ask for IPv6 while you're at it :)
16:06:13 * ewoud has a habit of using IPv6 where possible
16:06:40 <quaid> ok, we'll capture these details when they come around again
16:06:45 <ewoud> #idea invite AlterWays for an infra meeting
16:06:59 <quaid> yeah
16:07:18 <quaid> ok, going to capture anything about the last topic
16:07:30 <quaid> #topic Gerrit
16:07:51 <quaid> other than what was discussed ...
16:08:17 <eedri> i have a gerrit issue
16:08:30 <quaid> go ahead
16:08:34 <eedri> a few developers asked me if we can give permissions for drafts
16:08:48 <eedri> seems there isn't a view permissions to see drafts on gerrit
16:08:57 <eedri> http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.3.html#_drafts
16:09:02 <quaid> #info A few developers haved asked for permission to few drafts in gerrit
16:09:40 <eedri> on ovirt-engine
16:10:43 <ewoud> is that by design not an option or gerrit never thought about it?
16:10:44 <quaid> is that a feature we can use?
16:10:49 <quaid> oh
16:11:05 <dneary> ewoud, quaid: I would prefer not to be a gateway to AlterWay. How about we take these requests to the infra@ list? I can let Stéphane & Hervé know that we'll discuss practicalities there, and we'll only go off-list for the annoying private stuff (hosting agreement terms, getting things signed, etc)
16:11:29 <ewoud> dneary: +1 on less gateways
16:11:34 <quaid> dneary: +1
16:11:51 <ewoud> infra is low traffic anyway
16:12:03 <dneary> ewoud, I believe they're on there already, as well
16:12:12 <dneary> Isn't that where Stéphane made his initial offer?
16:12:32 <eedri> quaid, as i saw, drafts are a feature from 2.3 version
16:12:59 <quaid> eedri: worth upgrading our Gerrit when that happens, I guess
16:13:13 <eedri> quaid, we're running 2.4.2 already :)
16:13:19 <eedri> quaid, it got in at 2.3
16:13:40 <eedri> quaid, i'm guess it's just a minor permissions settings per project
16:13:50 <eedri> quaid, something like "refs/drafts/*"
16:14:17 <quaid> ah, I see!
16:14:26 <quaid> ok, so we need our gerrit admin(s) to fix this
16:14:34 <quaid> #action Gerrit admins need to enable viewing of drafts
16:14:52 <quaid> I'm looking for the Gerrit admins (Itamar and ?) to do some knowledge sharing
16:15:00 <quaid> anything more?
16:15:00 <eedri> itamar, ?
16:15:44 <mburns> i admin a gerrit instance, but i don't see any permissions related to drafts...
16:15:51 <mburns> 2.4.2
16:16:28 <eedri> mburns, from little i read i think its related to adding a 'refs/drafts/...' permission
16:16:45 <eedri> mburns, similar to 'refs/tags or refs/for..'
16:17:27 * quaid has to walk away for a minute
16:17:58 <mburns> eedri: ok, i see create reference permission
16:18:09 <mburns> in my instance /refs/* is allowed for all
16:18:34 <ewoud> mburns: I think it was about reading it
16:19:07 <eedri> mburns, i'm planning to install a test gerrit locally here to try it
16:19:15 <mburns> ewoud: yes, meant read permission under that reference
16:19:16 <eedri> mburns, needed also in our gerrit instance
16:19:40 <eedri> mburns, but giving read for /refs/* should solve it i think
16:20:18 <mburns> eedri: but now that i look closer, pushing a new refs/drafts isn't allowed...
16:20:51 * mburns does see --draft option in git-review though
16:22:57 <ewoud> maybe we should finish this with an #action
16:23:15 <mburns> eedri: do you want to followup with itamar ?
16:23:29 <eedri> mburns, yea i will ask him
16:23:32 <mburns> #action eedri to follow up with itamar about enabling this option on gerrit
16:23:39 <mburns> ok, ready for the last topic?
16:24:01 <mburns> #topic Infra presentation at Workshop in Barcelona
16:24:16 * mburns happy enough to discuss this on list rather than here
16:24:31 <mburns> i'm just looking for feedback on what i should cover
16:24:57 * mburns also curious who is going to be in attendance in Barcelona
16:25:34 * ewoud wishes he could
16:26:07 <ovirtbot> 14[[07Meetings14]]4 !10 02http://wiki.ovirt.org/w/index.php?diff=4734&oldid=4688&rcid=4849 5* 03DNeary 5* (+434) 10/* Meeting Time and Place */ 
16:26:26 * mburns thinks we're all suffering from meeting fatigue
16:26:34 <ewoud> +1
16:26:36 * dneary too
16:26:38 <eedri> +1
16:26:47 <mburns> #action mburns to come up with a draft presentation for review by next week's meeting
16:26:54 <dneary> mburns, I made a Google Calendar for oVirt meetings
16:27:01 <dneary> Thought it might be useful
16:27:03 <ewoud> though I've reviewed some patches for a colleague, so a very productive time :P
16:27:07 <mburns> dneary: awesome!
16:27:29 <mburns> #info no other comments on the presentation
16:27:32 <dneary> https://www.google.com/calendar/ical/tj13m8saobjame27tiphp47vf8%40group.calendar.google.com/public/basic.ics
16:27:36 <mburns> #topic other topics
16:27:41 <dneary> mburns, Can I add you as an admin?
16:27:49 <mburns> #info dneary created a google calendar with ovirt meetings
16:27:54 <mburns> #link https://www.google.com/calendar/ical/tj13m8saobjame27tiphp47vf8%40group.calendar.google.com/public/basic.ics
16:27:58 <mburns> dneary: sure
16:28:10 <dneary> mburns, gmail ID?
16:28:24 <mburns> anyone have other topics?
16:29:18 <mburns> closing in 10
16:29:30 <mburns> 5
16:29:39 <mburns> 1
16:29:42 <mburns> #endmeeting