18:01:54 <puiterwijk> #startmeeting Infrastructure (2018-01-18) 18:01:54 <zodbot> Meeting started Thu Jan 18 18:01:54 2018 UTC. The chair is puiterwijk. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:54 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:54 <zodbot> The meeting name has been set to 'infrastructure_(2018-01-18)' 18:01:56 <puiterwijk> #meetingname infrastructure 18:01:56 <zodbot> The meeting name has been set to 'infrastructure' 18:01:58 <puiterwijk> #topic aloha 18:02:00 <puiterwijk> #chair smooge relrod nirik dgilmore threebean pingou puiterwijk pbrobinson maxamillion 18:02:00 <zodbot> Current chairs: dgilmore maxamillion nirik pbrobinson pingou puiterwijk relrod smooge threebean 18:02:02 <puiterwijk> #topic New folks introductions 18:02:06 <puiterwijk> Any new folks wanting to introduce themselves? 18:02:32 <cverna> hi o/ 18:03:15 * relrod here 18:03:24 <tflink> .hello tflink 18:03:26 <zodbot> tflink: tflink 'Tim Flink' <tflink@redhat.com> 18:03:28 <puiterwijk> I do note that I'm in the middle of a deployment 18:03:54 <puiterwijk> Okay, given that I'm not seeing any new people yet, I'm going to assume there's not any, if there are, just chime in 18:04:07 <puiterwijk> #topic announcements and information 18:04:09 <puiterwijk> #info Many old f25 instances moved to f27, a few more to go - kevin 18:04:11 <puiterwijk> #info Many folks traveling to devconf/fosdem/configmgmt-camp next week 18:04:13 <puiterwijk> #info Bodhi upgrade in production to 3.2.0 - Randy 18:04:15 <puiterwijk> Any other updates from anyone? 18:05:31 <puiterwijk> If not, let's move on 18:05:36 <puiterwijk> There's no ticket cleanup this week 18:05:38 <puiterwijk> #topic Apprentice Open office hours 18:05:38 <relrod> puiterwijk: Do you want me to take over this since you're in a deployment? 18:05:43 <puiterwijk> Any apprentices with questions? 18:06:00 <cverna> it will be a quick meeting :) 18:07:18 <puiterwijk> If nothing, let's move on to... 18:07:20 <puiterwijk> #topic Open Floor 18:07:25 <puiterwijk> Anyone has any questions or remarks at all? 18:07:46 <tflink> wow, this is going to be a short meeting :) 18:07:52 <tflink> not that I'm complaining, mind you 18:07:54 <puiterwijk> tflink: don't jinx it now! 18:07:58 <tflink> too late 18:08:12 * puiterwijk does not that it's totally fine if anyone wants to ask/remark anything... Now'd be the time 18:08:51 <bowlofeggs> .hello2 18:08:52 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <randy@electronsweatshop.com> 18:09:08 <relrod> puiterwijk: okay I'll bite, but it should be pretty quick: 18:09:10 <willo> gidday, I'm up. Morning all. Just reading back 18:09:11 <puiterwijk> Come on people, don't be shy. You have one more minute 18:09:20 <puiterwijk> relrod: sure, what's up? 18:09:29 * puiterwijk cancels timer 18:09:36 <ajayvembu> @<puiterwijk> I have query regarding apprentice 18:09:38 <tflink> when's the new openstack going to be ready? 18:09:43 <tflink> you did ask for questions 18:09:54 <ajayvembu> after logging in what are next steps? 18:10:00 <relrod> Several times lately I've seen cases where nagios has gotten disabled, and forgotten about, and users end up reporting an outage to us. puiterwijk I know you talked about a nagios alert alert in the past, to remind us if nagios is disabled for too long. Have you looked into what that would take to accomplish? 18:10:11 <puiterwijk> ajayvembu: did you look at the easyfix to get some tasks to get started with? 18:10:50 <ajayvembu> how to do that? 18:10:52 <puiterwijk> relrod: I have not. Though it's not that tricky, just needs a timer in $somewhere (supybot-fedora?) that checks it 18:10:54 <puiterwijk> ajayvembu: https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix 18:10:56 <ajayvembu> I just have this link https://docs.pagure.org/infra-docs/sysadmin-guide/sops/sshaccess.html 18:11:03 <ajayvembu> okay will check 18:11:11 <ajayvembu> thanks 18:12:01 <relrod> puiterwijk: There's got to be some way to query for the state of notifs on noc01, right? So can we just have a cron run there and send something to the zodbot socket depending on state? 18:12:02 <puiterwijk> tflink: I did indeed. And I plan to work on that this week. Now if only things had followed schedule I'd be further. Right now, I am not sure yet on deployment time, as I've not gotten the first control plane setup 18:12:24 <relrod> (of course if zodbot notifs are off too, this doesn't help, but...) 18:12:30 <puiterwijk> relrod: yeah, that should be simple enough. 18:12:30 <relrod> it's a first step I guess 18:12:48 <tflink> puiterwijk: no worries, I was just tossing out a question to satiate you :) 18:12:50 <puiterwijk> running it on noc01 itself might also be a lot easier indeed, since there's no auth to deal with 18:12:56 * relrod nods 18:12:56 <puiterwijk> tflink: thanks for that :) 18:13:16 <willo> ajayvembu: Have you checked out https://fedoraproject.org/wiki/Infrastructure_Apprentice 18:13:19 <puiterwijk> relrod: so, you want to take a whack at that? It's somewhere on my todo list, but way down :( 18:13:23 <relrod> puiterwijk: okay. I'm going to add this to my list then 18:13:24 <relrod> yeah 18:13:28 <puiterwijk> relrod++ thanks! 18:13:58 <ajayvembu> @willo no will check it out thankd 18:14:09 <relrod> puiterwijk: that's all I have 18:14:19 <puiterwijk> Okay. 18:14:32 <puiterwijk> If nothing else, I'll close out in about one minute. 18:14:48 <puiterwijk> If there are other questions, go right ahead 18:15:54 <puiterwijk> Thanks all for coming to a really short infra meeting. Please do continue your questions in #fedora-admin and #fedora-apps and respective other channels! 18:16:01 <puiterwijk> #endmeeting