#fedora-meeting: Infrastructure (2014-11-06)
Meeting started by nirik at 18:00:22 UTC. The full logs are available at
* aloha (nirik, 18:00:23)
* New folks introductions and Apprentice tasks. (nirik, 18:02:22)
* Unfreeze reminder (nirik, 18:07:19)
* Applications status / discussion (nirik, 18:07:47)
* LINK: https://github.com/fedora-infra/bodhi/pull/109
* bodhi2 pr's pending: https://github.com/fedora-infra/bodhi/pull/109
(great way to get started) (nirik, 18:13:56)
* hyperkitty testing sqlalchemy changes (nirik, 18:14:16)
* anytia announce sometime after next week possibly. (nirik,
* askbot upstream update. Help wanted to update el6 package in epel.
* fedimg seems to be working, next step to automate it starting in
stg. (nirik, 18:16:42)
? (pingou, 18:18:36)
* nirik to work on migrating blockerbugs. (nirik, 18:20:08)
* Sysadmin status / discussion (nirik, 18:25:05)
* smooge going to USENIX LISA next week to work a booth and answer
questions on EPEL (smooge, 18:25:49)
* mass reboot went pretty well aside puppetmaster restart issues and
ns03 issues (still ongoing). (nirik, 18:26:42)
* nagios alerts (nirik, 18:29:33)
* Upcoming Tasks/Items (nirik, 18:34:20)
* LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/
* Open Floor (nirik, 18:36:01)
Meeting ended at 18:38:03 UTC.
Action Items, by person
People Present (lines said)
* nirik (82)
* tflink (22)
* pingou (15)
* sebito91 (8)
* zodbot (7)
* threebean (6)
* oddshocks (4)
* abompard (3)
* adimania (3)
* mpduty (3)
* puiterwijk (2)
* kushal (1)
* smooge (1)
* sritanu (1)
* pjones (1)
* danielbruno (1)
* relrod (1)
* abadger1999 (0)
* lmacken (0)
* mdomsch (0)
* dgilmore (0)
18:00:22 <nirik> #startmeeting Infrastructure (2014-11-06)
18:00:23 <zodbot> Meeting started Thu Nov 6 18:00:22 2014 UTC. The chair is nirik.
Information about MeetBot at http://wiki.debian.org/MeetBot
18:00:23 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:23 <nirik> #meetingname infrastructure
18:00:23 <zodbot> The meeting name has been set to 'infrastructure'
18:00:23 <nirik> #topic aloha
18:00:23 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch
threebean pingou puiterwijk
18:00:23 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou
puiterwijk relrod smooge threebean
18:00:42 * oddshocks is here
18:00:47 * danielbruno is here
18:00:48 * sebito91 is here
18:00:50 * relrod here
18:00:50 * puiterwijk is here
18:01:20 * mpduty is here
18:01:48 * pingou here
18:01:52 * threebean here
18:01:55 * adimania here
18:02:04 <kushal> kushal is here
18:02:22 <nirik> #topic New folks introductions and Apprentice tasks.
18:02:23 <pjones> hello.
18:02:31 <nirik> Any new folks like to introduce themselves?
18:02:39 * sebito91 waves hello
18:02:43 <sritanu> sritanu is here
18:02:44 <nirik> or apprentices with questions, comments, suggestions, ideas, ?
18:02:55 <sebito91> hi team, i missed last week's meeting and therefore
couldn't introduce myself
18:03:15 <sebito91> very excited to help out where i can...quick hits: very
interested in metrics collection/analysis
18:03:45 <sebito91> currently working as an SA in NYC
18:04:15 <oddshocks> sebito91: welcome!
18:04:24 <sebito91> oddshocks: thank you!
18:04:32 <nirik> welcome sebito91!
18:04:46 <nirik> we could definitely use some ideas around metrics and the like...
18:04:58 <mpduty> if I feel some application can be packaged how do I know whether
it meets Fedora standards or requirements
18:05:01 <sebito91> I'm going to post a suggestion to the distro, but thinking
of possibly adding a graphite or grafana based view to current collectors
18:05:20 <sebito91> nirik: thanks
18:05:41 <nirik> mpduty: it's mostly a matter of looking at it and the
guidelines... you can often also ask #fedora-devel or the devel mailing list for others to
18:06:36 <mpduty> nirik, okay
18:07:04 <nirik> cool.
18:07:19 <nirik> #topic Unfreeze reminder
18:07:29 <nirik> just a reminder that we are currently NOT in freeze. ;)
18:07:40 <nirik> we go back on the 18th... so not too much time really.
18:07:45 <adimania> \o/
18:07:47 <nirik> #topic Applications status / discussion
18:07:58 <nirik> any applications news or status to talk about?
18:08:45 <pingou> I have some pull-requests pending review
18:08:56 <pingou> on fedocal, pkgdb2 and anitya
18:09:08 <nirik> during this non freeze it would be good to move stuff to
ansible/rhel7 where possible/easy. ;)
18:09:14 <pingou> mostly bug fixes :)
18:09:28 <threebean> bodhi2 taskotron integration is done in dev. I'm hoping we
can triage what tickets need to be closed before staging in the next week or so.
18:09:31 <threebean> https://github.com/fedora-infra/bodhi/pull/109
18:10:26 <threebean> on those pull-requests, anybody can review them. Just read
through the code change and see if it looks sane. Ask questions about anything you
don't understand or looks funny.
18:10:41 <threebean> an easy way for apprentices to get involved on the
apps/dev/maintenance side of the house.
18:10:43 <nirik> yeah, it would be nice to get bodhi2 in stg where we can look at it
18:11:16 <nirik> cool.
18:11:41 <nirik> abompard: any news on hyperkitty? I read that upstream was very
happy with the sqlalchemy stuff. ;)
18:12:17 <abompard> nirik: yeah, that branch has finally been merged. I've
adapted hyperkitty to work with it
18:12:19 <abompard> testing it now
18:12:23 <nirik> pingou: do we have a timeline for announcing aytia more widely?
18:12:38 <nirik> abompard: cool. So next step is likely moving some automated lists
18:12:43 <nirik> (after that testing)
18:12:47 <abompard> nirik: yes
18:13:03 <pingou> nirik: as I won't be there next week, I didn't want to do
it this week, but when I get back +1 for me
18:13:36 <nirik> Oh, another thing to note: there's a new askbot version... if
someone would like to rebase our patches and get it building we can look at upgrading.
18:13:56 <nirik> #info bodhi2 pr's pending:
(great way to get started)
18:14:16 <nirik> #info hyperkitty testing sqlalchemy changes
18:14:30 <nirik> #info anytia announce sometime after next week possibly.
18:14:43 <nirik> #info askbot upstream update. Help wanted to update el6 package in
18:14:55 <tflink> not much on the qa front - going to be looking into beaker again
soon, expecting the blocking bug there to be fixed in the next month or so. still waiting
on a warranty quote for some of the old qa0* boxes that we want to use for beaker clients
18:14:57 <pingou> threebean: how is the-new-hotness doing?
18:15:07 <threebean> it is just waiting to be deployed.
18:15:11 <pingou> cool :)
18:15:34 <pingou> so if we move anitya on, we can push a new pkgdb2 and deploy
18:15:42 <nirik> tflink: if we could possibly move blockerbugs to rhel7 when we
ansible it that would be great. If you like I can test and see what might be missing...
18:15:46 <tflink> going to be decomissioning some of the autoqa clients soon because
the queues on taskotron keep getting longer than I'd like
18:15:55 <tflink> nirik: what timeline are you thinking of?
18:16:09 <oddshocks> Fedimg successfully uploaded good F21 beta AMIs for base and
atomic cloud images, so I think it's about time to actually add in the ansible files I
wrote and let it start doing automatic uploads this week, at least in stg
18:16:13 <nirik> tflink: well, I could look in the next few days, but perhaps next
week for migrating/
18:16:14 <nirik> ?
18:16:26 <nirik> oddshocks: excellent.
18:16:42 <nirik> #info fedimg seems to be working, next step to automate it starting
18:16:57 * tflink isn't against migration, just concerned about balancing that with
the other tasks he's supposed to be working on
18:17:05 <oddshocks> Those AMIs are on the fp.o page proper now, so they are public
and the official ones we're offering for beta.
18:17:20 <tflink> I suppose that it should be a pretty simple migration, though
18:17:47 <pingou> tflink: hopefully, 1 change in ansible and re-run the playbook :)
18:17:59 <tflink> pingou: blockerbugs isn't in ansible, though
18:18:17 <tflink> its still puppet
18:18:26 <pingou> isn't there a patch for that on trac?
18:18:35 <nirik> yes...
18:18:41 <adimania> pingou, yes
18:18:43 <nirik> so, hopefully it will not be too bad...
18:18:46 <nirik> but you never know. ;)
18:19:00 <pingou> true enough :)
18:19:00 <tflink> oh, I didn't see that ticket
18:19:08 <nirik> tflink: I'm happy to do the bulk of the work on it... as long
as you are around to ping if it blows up?
18:19:32 <tflink> nirik: yeah, that's fine. we have a bug to fix in there,
18:19:40 <tflink> the app, I mean
18:19:57 <nirik> ok.
18:20:08 <nirik> #info nirik to work on migrating blockerbugs.
18:21:14 <nirik> tflink: oh, another thing I wanted to run by you... but I guess
it's more sysadminy... I want to re-install virthost-comm01.qa... I think it has no
prod stuff on it, but would need an hour downtime for the re-install sometime.
18:21:40 <tflink> the only thing that could affect me is bastion-comm01
18:21:46 <tflink> but an hour isn't a problem
18:22:01 <nirik> cool. will schedule that out of meeting...
18:22:11 <nirik> any other application type news/
18:22:11 <nirik> ?
18:22:27 <tflink> I have some questions about what exactly you have in mind but that
sounds like an out-of-meeting topic
18:22:33 <tflink> er, exact process
18:22:51 <tflink> some of the stuff on virthost-comm01 isn't backed up and
isn't easily reinstallable
18:23:54 <nirik> backup libvirt info for guests, reinstall with rhel7 over the
existing install (leaving lvm alone), bring up, redefine guests, bring them up. ;)
18:24:06 <nirik> so, only the host should be affected.
18:24:14 <nirik> the guests lv's stay the exact same
18:24:50 * nirik has done this with a number of other virthosts just fine.
18:25:05 <nirik> #topic Sysadmin status / discussion
18:25:14 <tflink> ok, wasn't sure if the reinstall involved rebuilding the
18:25:23 <nirik> so yeah, I have been migrating things to rhel7/ansible where
possible... I will keep doing that until freeze.
18:25:32 <nirik> tflink: nope, it could, but it doesn't have to.
18:25:45 <nirik> no need to tie them together
18:25:49 <smooge> #info smooge going to USENIX LISA next week to work a booth and
answer questions on EPEL
18:26:01 <nirik> we had a mass reboot last night, went pretty well with a few
18:26:16 <nirik> smooge: do have fun! :)
18:26:42 <nirik> #info mass reboot went pretty well aside puppetmaster restart
issues and ns03 issues (still ongoing).
18:27:01 <nirik> I'm also going to run the master playbook today... catch things
up with ansible.
18:27:10 <tflink> I mentioned this to smooge yesterday but we have 3 more hosts
coming to phx2 soon (order approved, submitted to vendor). I'd guess an eta of 2-3
18:27:22 <nirik> tflink: cool. :)
18:27:40 <tflink> which is the rest of the stuff we ordered for FY15
18:28:01 <nirik> nice. These are all qa0* taskotron virthosts? or were we going to
make another virthost-comm?
18:28:26 <nirik> I guess we can decide when we need to. ;)
18:28:49 <tflink> nirik: not sure yet, to be honest
18:29:03 <nirik> yeah. no need to decide really, we can adjust...
18:29:33 <tflink> if they're compatible, it might make sense to add them as
compute nodes to the cloud
18:29:33 <nirik> #topic nagios alerts
18:29:57 <nirik> tflink: we could possibly do that, although that might require some
re-wiring as the cloud network is isolated.
18:30:06 <nirik> tflink: we are also getting some more cloud nodes in Q4
18:30:12 <tflink> yeah, that would be a different conversation, I think
18:30:20 <nirik> .tiny
18:30:21 <tflink> that -> what we may end up doing with openstack
18:30:25 <zodbot> nirik: http://tinyurl.com/pzzwx2r
18:30:32 <nirik> tflink: yeah, we really need to get our new one on-line. ;)
18:30:42 <puiterwijk> .tiny
18:30:42 <zodbot> puiterwijk: http://tinyurl.com/qevmn8u
18:31:00 <nirik> threebean: you looked at the tagger thing right? what was that?
18:31:57 <nirik> I have no idea what was going on with bodhi... lmacken has been
traveling this week, but hopefully we can figure it out.
18:32:02 <nirik> (or the reboots helped it)
18:33:23 <nirik> the report looks more real when you only do hard states.
18:33:33 <nirik> .tiny
18:33:34 <zodbot> nirik: http://tinyurl.com/oz9c4ym
18:34:06 <nirik> anyhow...
18:34:20 <nirik> #topic Upcoming Tasks/Items
18:34:21 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/
18:34:32 <nirik> we have our FAD coming up in the beginning of december...
18:34:39 <nirik> freeze on the 18th of this month.
18:34:51 <nirik> anything else anyone would like to note or schedule?
18:35:10 <pingou> I'll be away next week
18:35:26 <pingou> no idea about my access to internet :)
18:35:32 <nirik> alrighty. :) well, have fun...
18:35:53 <pingou> will do :)
18:36:01 <nirik> #topic Open Floor
18:36:10 <nirik> anyone have any items for open floor?
18:37:00 <nirik> alrighty then, will close out in a minute if nothing more.
18:38:00 <nirik> Alright. Thanks for coming everyone! Do continue in #fedora-admin,
#fedora-noc, and #fedora-apps
18:38:03 <nirik> #endmeeting