15:00:54 <tflink> #startmeeting fedoraqa-devel
15:00:54 <zodbot> Meeting started Mon Dec 15 15:00:54 2014 UTC.  The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:54 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:02 <tflink> #meetingname fedoraqa-devel
15:01:02 <zodbot> The meeting name has been set to 'fedoraqa-devel'
15:01:07 <tflink> #topic Roll Call
15:01:11 * kparal is here
15:01:14 <lbrabec> he should, at least he told me so
15:01:18 * lbrabec is here
15:01:28 * kparal pokes mkrizek
15:01:45 * mkrizek is here
15:01:50 <kparal> jskladan wrote me an email today saying he can't come today, and asked for moving the meeting for tomorrow
15:02:14 * tflink is fine doing that
15:02:21 <mkrizek> me too
15:02:28 <kparal> lbrabec: if we moved it, can you two come as well?
15:02:33 <lbrabec> yep
15:02:37 <tflink> we could also change the agenda up a bit to talk about stuff that is less likely to be of as much interest to josef
15:03:05 <tflink> beaker and vacation
15:03:46 <kparal> I'm fine either way. we can discuss some topics today and some topics tomorrow, I don't mind
15:04:04 <kparal> is here anyone else who wanted to attend/listen to this meeting?
15:04:44 <kparal> it seems garretraziel forgot about today's meeting anyway
15:05:36 <kparal> tflink: if you think we can discuss something that's not interesting for jskladan and garretraziel, we can do it right away
15:06:02 <kparal> people can forget about tomorrow's meeting as well, so better discuss at least something today :)
15:06:26 <tflink> yeah
15:06:40 <kparal> lbrabec: a quick question, what are your plans (even including Jan'
15:06:50 * tflink proposes discussing beaker a bit and figuring out when folks will be around
15:06:50 <kparal> Jan's if you know) for the rest of the year?
15:07:11 <tflink> a decent segue into ...
15:07:20 <tflink> #topic Vacation Plans
15:07:49 * tflink will be around until at least the 24th
15:08:04 * kparal will be available tomorrow and then from Jan 2
15:08:39 <kparal> so far, I've spent my holiday upgrading to Fedora 21 and reporting bugs, hmm....
15:08:43 <mkrizek> I am around this week and then from 5th (or 2nd, not sure yet)
15:09:22 <tflink> kparal: sounds like an ... interesting choice for a holiday :)
15:09:29 <lbrabec> this tue and wed in office, and christmas then x)  we have exams in january, so not much from us, once a week i guess
15:10:32 <tflink> lbrabec: when are exams over?
15:10:34 <kparal> lbrabec: ok, so better not count with you too much in Jan
15:10:55 <lbrabec> kparal: yep
15:11:57 <lbrabec> tflink: i should be done around 16th, but last week in january i'll go skiing
15:12:28 <tflink> lbrabec: ok, so you'll be mostly AFK until ~ Feb?
15:12:36 <lbrabec> yes
15:12:58 * kparal inspects F22 schedule
15:13:24 <kparal> no earlier than 2015-02-10 	Branch Fedora 22 from Rawhide
15:13:26 <kparal> ufff
15:13:34 <kparal> so early
15:15:30 * tflink wonders when the f22 schedule will be finalized
15:15:52 <tflink> ok, I think we've gotten all that we can out of this topic for now
15:16:02 <tflink> #topic Beaker Update and Possible Plans
15:16:13 <tflink> so, I got back to futzing with beaker again last week
15:16:54 <tflink> I had F21 provisions working and a rawhide tree that would work well enough (hit a bug during install that prevented provision but beaker worked as expected)
15:17:10 <tflink> we've managed to break it again, though
15:17:26 <kparal> what about that dual hostname issue?
15:17:27 * tflink is working with atodorov to get nightly trees imported into beaker
15:18:00 <tflink> kparal: that's still waiting on an RFE but it doesn't prevent beaker from working well enough to test
15:18:12 <tflink> it mostly breaks the log URLs
15:18:16 <kparal> ok
15:19:09 <tflink> I tried adding a bare-metal box to beaker but found out that firewall or networking changes are needed before that'll work
15:19:36 <tflink> https://phab.qadevel.cloud.fedoraproject.org/T379
15:20:40 <tflink> at some point, we need to decide how important it is to have a production(-ish?) beaker deployment
15:21:15 <tflink> assuming that the RFE is completed and released in January, there's still a lot of work that needs to be done before that can happen
15:22:36 <tflink> hopefully we'll be able to get the trees working soon so atodorov can continue his work on getting the install tests to run
15:23:01 <tflink> if we have those, that's a compelling use case to justify a beaker deployment
15:23:05 <tflink> in my mind, at least
15:23:26 * kparal considers whether it is worth the effort to try and find some other team to take care and maintainer beaker in fedora instead of us
15:23:35 <kparal> *maintain
15:23:41 <tflink> who?
15:24:00 <kparal> somebody internal from RH, I guess
15:24:06 <tflink> I'm hoping that maintenance work will be minimal once it's up an running
15:24:27 <tflink> unfortunately, I think that initial deployment is going to fall mostly in my lap due to permissions in infra
15:24:47 <tflink> s/mostly/at least partially
15:25:27 <kparal> ok
15:25:30 <tflink> I think it's going to be difficult getting others on board until we have something running
15:25:45 <tflink> but I'm certainly not going to turn down help
15:25:49 <kparal> I guess you're right
15:26:16 <kparal> what about help from ncolghan?
15:26:28 <kparal> I guess I misspelled his name
15:27:08 <tflink> dcallagh has been helping with some stuff, the devs have said that they're willing to help maintain the system since having a public instance benefits them in more than one way
15:27:51 <kparal> ok, at least that
15:28:32 <tflink> but this still has the potential to become a large maintenance task going forward
15:29:31 <tflink> I don't know how to quantify the value of that investment until we get something working and see what kinds on tests we can get to run in it
15:30:00 <tflink> there is a bit of a time limit to this, as well. we only have the bare-metal boxes until the end of October
15:30:22 * tflink really doesn't want to approach extending the warranties on them again
15:30:52 <tflink> it doesn't sound like there's too much excitement over getting beaker to work :)
15:30:58 <tflink> at least, not in this crowd
15:31:20 <tflink> there'd also be some taskotron integration work, eventually, if we chose to keep a production system
15:31:44 <kparal> having bare metals is not necessary, right? can it work with virt finally?
15:31:47 <tflink> and some other beaker RFEs at some point that will be a pain eventually but aren't required for an initial system
15:32:06 <tflink> kparal: yeah, it has been able to work with virt for a while - the existing dev system only has working virt clients
15:32:14 <kparal> great
15:32:48 <tflink> well, "working"
15:33:34 <tflink> hopefully, we'll get this tree issue figured out today
15:33:51 <tflink> anything else on beaker?
15:34:12 <kparal> not here
15:34:20 <tflink> ok, moving on to ...
15:34:28 <tflink> #topic qadevel update
15:34:49 <tflink> one issue is trying to get rid of the old username/password auth mechanism
15:35:12 <tflink> we still have 11 users who haven't linked their accounts to FAS
15:35:22 <tflink> 11/12 people ignored my email last week
15:35:30 <tflink> at least one of whom is in this meeting
15:36:19 * kparal still haven't read the mailbox
15:36:32 <tflink> kparal: you're fine. I show your account as linked to FAS
15:36:54 * kparal is relieved
15:37:08 * tflink was hoping to turn off the username/password system this week but it looks like that isn't going to happen
15:37:20 <tflink> I'll just have to step up my pestering level
15:37:28 <kparal> send direct emails
15:37:39 <tflink> kparal: that's what I started with
15:37:43 <kparal> ah
15:37:55 <tflink> maybe public listing of the folks who have been ignoring me at some point?
15:38:20 * tflink has started PM-ing people
15:38:50 <tflink> the other bit is about migrating off of our current cloud instance
15:39:14 <tflink> not a huge problem yet, but I'd like to get on to the infra systems that we've set up for qadevel and get more CI working
15:39:45 <tflink> the biggest hurdle there is packaging phabricator for epel
15:39:49 <tflink> and/or fedora
15:40:48 <kparal> lbrabec: you said you would be interested to help out in packaging phabricator?
15:41:04 <tflink> relrod also said he'd be interested in helping
15:41:33 <tflink> as much as I'd like to see it done - it's the same old dilemma. how much time is it worth right now?
15:42:08 * tflink has some notes and the current specfiles up at https://bitbucket.org/tflink/phabricator-dist
15:43:18 <tflink> anyhow, I just wanted to mention the status of that as an update
15:43:31 <tflink> but I think we're up to:
15:43:35 <tflink> #topic Open Floor
15:43:38 <lbrabec> kparal: yep, sounds interesting
15:43:50 <tflink> the other topics would probably be better served waiting for josef
15:44:07 <tflink> #info lbrabec interested in helping to package/maintain phabricator
15:44:37 <kparal> I created a new qa-devel meeting in fedocal for tomorrow
15:44:41 <kparal> same time
15:44:52 <tflink> kparal: thanks, that was going to be my next question
15:44:59 * tflink will send out the announce shortly
15:45:01 <kparal> is everybody OK with it?
15:45:05 <mkrizek> yep
15:45:06 <tflink> WFM
15:45:47 <lbrabec> yep
15:45:56 <kparal> done, then
15:46:39 <kparal> if there are no further topics, let's close this and see you tomorrow
15:46:44 <tflink> anything else that folks want to bring up?
15:47:15 * tflink assumes not
15:47:33 <tflink> ok, thanks for coming everyone. see you tomorrow and/or at the qa meeting in ~ 10 minutes
15:47:41 * tflink will send out minutes shortly
15:47:44 <tflink> #endmeeting