18:00:07 #startmeeting Infrastructure (2016-01-07) 18:00:07 Meeting started Thu Jan 7 18:00:07 2016 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:07 The meeting name has been set to 'infrastructure_(2016-01-07)' 18:00:08 #meetingname infrastructure 18:00:08 The meeting name has been set to 'infrastructure' 18:00:08 #topic aloha 18:00:08 #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson 18:00:08 Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pbrobinson pingou puiterwijk relrod smooge threebean 18:00:08 #topic New folks introductions / Apprentice feedback 18:01:14 welcome everyone. Any new folks like to give a short one line introduction? Or any apprentices with questions or comments? 18:02:23 I guess it will be a quick meeting if it's only me. ;) 18:02:28 he 18:02:30 .hello smdeep 18:02:33 smdeep: smdeep 'Sudeep Mukherjee' 18:02:35 I am in another meeting at the moment 18:02:40 hi everyone :) 18:02:41 ehlo 18:02:46 so splitting time 18:02:53 .hello sayanchowdhury 18:02:54 sayan: sayanchowdhury 'Sayan Chowdhury' 18:03:13 hi 18:03:20 nirik, I am an appretince and i need a sometime to start contributing 18:05:05 great. ;) feel free to ask questions here or in #fedora-admin/#fedora-apps/#fedora-noc... 18:05:05 time is something we are all short of. ;( 18:05:25 ok, if no new folks or questions, lets move on to status / info... hang on to your irc clients.... :) 18:05:36 #topic announcements and information 18:05:37 #info Smooge and Nirik in phx2 datacenter all next week - smooge / nirik 18:05:37 #info Bunch of tech debt has been fought - see https://fedoraproject.org/wiki/Infrastructure/Debt - everyone 18:05:37 #info New OpenID login theme in staging, please test (prod on 15th) - puiterwijk 18:05:37 #info January apprentice nag email out, please reply if you are an apprentice - kevin 18:06:07 anything else folks would like to note or discuss more of the above? 18:06:35 we will have short outages next week but probably nothing longer than 15-20 minutes 18:06:41 yay for the technical debt fighters! 18:06:56 smooge: Well, I think cloud may be longer since I'm planning to do an update there as well 18:07:04 smooge: yeah, I was going to send an email on that... we probibly need to schedule some of the outages we know about 18:07:21 smooge / puiterwijk: when do you want to do the cloud stuff? 18:07:29 wednesday? 18:07:33 Sure, fine with me 18:07:36 or tuesday? 18:07:48 * kushal is also here 18:07:48 .hello subho 18:07:50 subho: subho 'None' 18:08:06 Though I'll probably try to do the updates before., so we don't have to wait for that when you're onsite 18:08:15 how about wed morning? 10am datacenter time? 18:08:25 Sure, sounds fine with me. 18:08:40 I'll do the updates at the usual time 18:08:47 puiterwijk: can you write up an outage notice and send it? 18:08:55 nirik: yup, will do 18:08:57 we will need to pull 01-08 out and add memory to each... 18:09:38 Sounds perfect. I'll handle the bringing up of openstack etc 18:09:58 are you planning just a apply updates cycle? or is there an OS update in there too? 18:10:19 There's a bunch of openstack updates 18:10:25 #info Rewritten darkserver is now getting tested on a cloud instance. 18:10:38 kushal: great news. ;) 18:10:41 And I'm also going to try to get rid of the EPEL packages on those boxes 18:11:06 (there's still some left, but I got a set of packages that we can go back to that are in RHOSP 18:11:07 ) 18:11:32 puiterwijk: so, you want to start doing those updates at 10am? or you will have them done before and we can take down machines at 10am? 18:11:51 nirik, so that we can finally move to el7 :) 18:11:58 nirik: I'm planning to start the updates at the nomrla time (2AM UTC), so that I'll be done before you guys get there 18:12:10 ok. 18:12:19 sounds good. 18:12:25 I don't want to make you guys wait on openstack update + fixing. That can take quite some time as I found out 18:12:44 we may plan some more outages too, but I can discuss that in #fedora-noc out of meeting... 18:12:51 Yeah, sounds good 18:13:17 Oh, I see you had an option for tuesday open as well. Do you have a preference? Tuesday or Wednesday? 18:13:34 doesn't matter to me, as long as we schedule it. 18:13:39 Okay. 18:14:07 so pick one and we will go with that. ;) 18:14:27 I have 2 other items to mention here: 18:14:57 1. smooge and I will as you have seen be in the datacenter all next week. So, I won't be able to run the meeting. Would someone else be willing to do so? 18:15:04 Wednesday is what python says 18:15:13 nirik: I can do that 18:15:34 2. Are there things folks would like to learn about or teach about? I'd love to line up people in advance a few weeks for meetings so we have things ready to go. 18:15:39 puiterwijk: thanks. 18:15:48 #action puiterwijk to run meeting next week 18:15:58 * mirek-hm is late here 18:16:15 hey mirek-hm. :) 18:16:21 Hello all, I am Subhendu Ghosh, currently working as Python Developer in a startup in India. I am new here , I have been contributing to fedora-infra projects regularly and I want to be an apprentice. 18:16:46 welcome subho. Please do see me after the meeting in #fedora-admin and we can get you setup... :) 18:17:13 nirik, awesome! thanks :) 18:17:37 ok, if no other discussion items I will move on to the learn about section. 18:18:00 #topic Learn about: CSI - kevin 18:18:20 So, I just wanted to talk briefly about CSI... community services infrastructure. 18:18:37 It's a process/docuement for community based infrastructures (like ours!) 18:19:03 https://docs.fedoraproject.org/en-US/Community_Services_Infrastructure/1/html-single/Security_Policy/index.html 18:19:20 currently we only have the security policy written, and it's likely somewhat out of date at this point... 18:19:30 and I thought that it stand for Crime Scene Investigation :( 18:19:53 But there's still some very good processes and settings in there, so I would encourage everyone to read it 18:20:05 mirek-hm: :) yeah, happy accident I guess, or perhaps it's not an accident. :) 18:20:25 basically two things that really are worth thinking about for us: 18:20:40 1. Making sure the client machines we all use are secure. 18:21:03 Most of this is just common sense, but it's nice to look and make sure you aren't making any mistakes. 18:21:28 applying updates regularly, strong passwords, lock screens, etc 18:22:24 also, and much more up to date than CSI, linux foundation recently posted their policies: 18:22:26 https://github.com/lfit/itpol 18:22:58 The second part of CSI setup is how to handle security events... who to notify, what to do, etc. 18:23:16 Those are good for everyone to know so they know how to act if there's a security event. 18:23:30 Luckily we don't have them very often at all, but having a process ready is very important. 18:23:55 So, I would encourage everyone to read up and make sure you are following good practices on your workstations/client machines 18:24:06 and know what to do when there's some kind of security event. ;) 18:24:42 any questions or comments? 18:25:18 great. :) 18:25:22 #topic Open Floor 18:25:32 well, on that topic, I am giving a talk for centos dojo in bruxelles 18:25:40 on sysadmin workstation security 18:25:51 misc: awesome. ;) Do you know if it will be recorded? 18:25:56 nirik: it should 18:26:13 it might just be me reading the Linux Fundation check list and adding jokes and french accents 18:26:34 cool. If you could post the link to the talk on the infra list, or pass it on to me to post that would be great. 18:26:44 sure, once it is done :) 18:27:06 (if people also want me, I can do the same talk for all kind of events, from install party to weddings) 18:27:40 ha. Nice. 18:28:11 ok, if nothing else will close out the meeting in a few... 18:28:55 ok, thanks for coming everyone! 18:28:57 #endmeeting