June 2014 - infrastructure - Fedora mailing-lists

Ask Fedora being badgered by spam
by Ankur Sinha 12 Aug '14

12 Aug '14

Hi, Of late, Ask Fedora is being badgered by spam. They seem to open multiple accounts and post as many as 50 spam questions at a time. Is there something we can do to tackle this? For the time being, we're manually blocking the user and deleting each question one by one. It's a lot of work and one needs to keep an eye out on the forum all the time. I've asked upstream a question here: http://askbot.org/en/question/12506/how-do-i-mass-delete-all-questions-from… This is a work around to clean up the mess. Can we do something to avoid it altogether? I've asked upstream another question: http://askbot.org/en/question/12507/alternatives-to-akismet/ -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG

8 37

mirroring for alternative content
by Colin Walters 18 Jul '14

18 Jul '14

Hi, We have several forms of non-Koji internal builds: 1) COPR (the most visible) 2) http://alt.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/ (this could be a COPR) 3) rpm-ostree: http://rpm-ostree.cloud.fedoraproject.org/#/ Now, I recently was allocated a new atomic01.qa.fedoraproject.org server dedicated to rpm-ostree composes, and I'm happy to announce I now have it composing trees: fedora-atomic/rawhide/x86_64/server/docker-host => 175510ab77ef39ec6000db2745c70444d55957e38c5ff28f890237e1f012ea5e fedora-atomic/rawhide/x86_64/workstation/gnome/core => b6f3f3b53ef957c71e8d8bdc36c35519888d4177bf6a582ba37e33416ff84216 But it's on the QA network, and so I can't just serve the content directly from it. Nor would I want to have the compose server doing double duty as a static webserver anyways. I could just rsync this content to the current rpm-ostree.cloud.fedoraproject.org, but there are a few issues with that: 1) It's a one off instance in the fedora cloud with no backup/monitoring 2) No redundancy 3) No tuning for static webserving 4) Most critically, no TLS COPR only relatively recently gained TLS, which is fundamentally necessary for retrieving arbitrary executable code that runs as root. But COPR also (from what I understand from <puiterwijk>) is just one machine. What do you think about investing in having e.g. altcdn.fedoraproject.org be a load-balanced static webserver farm protected by TLS that could be written to by a trusted subset of non-Koji build/compose tooling? "altcdn" is the first thing that came to mind offhand for a name, feel free to pick others =) We'd need to determine the writing process; could be rsync-over-ssh access to specific subdirectories gated by ssh key? Something else?

2 5

Meeting Agenda Item: Introduction John Dulaney
by John Dulaney 30 Jun '14

30 Jun '14

Hello! My name is John Dulaney, and I am a long time contributor. I have been kicking the idea of joining the infrastructure team for quite some time now. I can bring the following to the table: Red Hat Certified Engineer Many years of contributing to Fedora Experience supporting Red Hat Enterprise Linux for Red Hat Python I look forward to helping out! John. IRC: handsome_pirate

1 0

non idempotent tasks
by Kevin Fenzi 30 Jun '14

30 Jun '14

Greetings. We have a few tasks that show up all the time in check/diff output. Would be nice to fix these up. Fixes welcome. pkgdb 07.09.52 pkgdb01.phx2.fedoraproject.org Jun 30 2014 07:13:00 4 CHECK_DIFF:CHANGED copy sundry pkgdb configuration task_userid:root 07.09.52 pkgdb01.stg.phx2.fedoraproject.org Jun 30 2014 07:13:00 4 CHECK_DIFF:CHANGED copy sundry pkgdb configuration task_userid:root 07.09.52 pkgdb02.phx2.fedoraproject.org Jun 30 2014 07:13:01 4 CHECK_DIFF:CHANGED copy sundry pkgdb configuration task_userid:root buildhw 06.28.48 bkernel01.phx2.fedoraproject.org Jun 30 2014 06:34:26 68 CHECK_DIFF:CHANGED enable pcscd task_userid:root 06.28.48 bkernel01.phx2.fedoraproject.org Jun 30 2014 06:34:29 70 CHECK_DIFF:CHANGED enable pesign task_userid:root 06.28.48 bkernel01.phx2.fedoraproject.org Jun 30 2014 06:34:35 75 CHECK_DIFF:CHANGED set pesign facls to allow mockbuild user to use the socket directory task_userid:root 06.28.48 bkernel01.phx2.fedoraproject.org Jun 30 2014 06:34:36 76 CHECK_DIFF:CHANGED set pesign facls to allow mockbuild user to use the socket. task_userid:root 06.28.48 bkernel02.phx2.fedoraproject.org Jun 30 2014 06:34:26 68 CHECK_DIFF:CHANGED enable pcscd task_userid:root 06.28.48 bkernel02.phx2.fedoraproject.org Jun 30 2014 06:34:29 70 CHECK_DIFF:CHANGED enable pesign task_userid:root 06.28.48 bkernel02.phx2.fedoraproject.org Jun 30 2014 06:34:35 75 CHECK_DIFF:CHANGED set pesign facls to allow mockbuild user to use the socket directory task_userid:root 06.28.48 bkernel02.phx2.fedoraproject.org Jun 30 2014 06:34:36 76 CHECK_DIFF:CHANGED set pesign facls to allow mockbuild user to use the socket. task_userid:root mailman 04.05.07 mailman01.phx2.fedoraproject.org Jun 30 2014 04:08:45 13 CHECK_DIFF:CHANGED install needed packages task_userid:root 04.05.07 mailman01.phx2.fedoraproject.org Jun 30 2014 04:08:49 14 CHECK_DIFF:CHANGED add mailman to the apache group task_userid:root 04.05.07 mailman01.phx2.fedoraproject.org Jun 30 2014 04:08:49 15 CHECK_DIFF:CHANGED add apache to the mailman group task_userid:root 04.05.07 mailman01.phx2.fedoraproject.org Jun 30 2014 04:08:51 16 CHECK_DIFF:CHANGED set the mailman conffile task_userid:root 04.05.07 mailman01.phx2.fedoraproject.org Jun 30 2014 04:08:52 17 CHECK_DIFF:CHANGED hyperkitty logging -- directory task_userid:root 04.05.07 mailman01.phx2.fedoraproject.org Jun 30 2014 04:08:54 18 CHECK_DIFF:CHANGED hyperkitty logging -- file creation task_userid:root 04.05.07 mailman01.phx2.fedoraproject.org Jun 30 2014 04:08:55 19 CHECK_DIFF:FAILED hyperkitty logging -- file permissions task_userid:root 04.05.07 mailman01.stg.phx2.fedoraproject.org Jun 30 2014 04:06:11 17 CHECK_DIFF:CHANGED /etc/postfix/main.cf task_userid:root 04.05.07 mailman01.stg.phx2.fedoraproject.org Jun 30 2014 04:08:19 81 CHECK_DIFF:CHANGED restart postfix task_userid:root 04.05.07 mailman01.stg.phx2.fedoraproject.org Jun 30 2014 04:09:01 22 CHECK_DIFF:CHANGED install the hyperkitty settings file task_userid:root 04.05.07 mailman01.stg.phx2.fedoraproject.org Jun 30 2014 04:09:12 29 CHECK_DIFF:CHANGED create the kittystore plain text index dir task_userid:root 04.05.07 mailman01.stg.phx2.fedoraproject.org Jun 30 2014 04:10:00 58 CHECK_DIFF:CHANGED restart mailman3 task_userid:root 04.05.07 mailman01.stg.phx2.fedoraproject.org Jun 30 2014 04:10:00 59 CHECK_DIFF:CHANGED reload apache task_userid:root 04.05.07 mailman02.phx2.fedoraproject.org Jun 30 2014 04:08:46 13 CHECK_DIFF:CHANGED install needed packages task_userid:root 04.05.07 mailman02.phx2.fedoraproject.org Jun 30 2014 04:08:49 14 CHECK_DIFF:CHANGED add mailman to the apache group task_userid:root 04.05.07 mailman02.phx2.fedoraproject.org Jun 30 2014 04:08:49 15 CHECK_DIFF:CHANGED add apache to the mailman group task_userid:root 04.05.07 mailman02.phx2.fedoraproject.org Jun 30 2014 04:08:51 16 CHECK_DIFF:CHANGED set the mailman conffile task_userid:root 04.05.07 mailman02.phx2.fedoraproject.org Jun 30 2014 04:08:52 17 CHECK_DIFF:CHANGED hyperkitty logging -- directory task_userid:root 04.05.07 mailman02.phx2.fedoraproject.org Jun 30 2014 04:08:54 18 CHECK_DIFF:CHANGED hyperkitty logging -- file creation task_userid:root 04.05.07 mailman02.phx2.fedoraproject.org Jun 30 2014 04:08:55 19 CHECK_DIFF:FAILED hyperkitty logging -- file permissions task_userid:root nuancier 06.35.07 nuancier01.phx2.fedoraproject.org Jun 30 2014 06:37:38 4 CHECK_DIFF:CHANGED copy sundry nuancier configuration task_userid:root 06.35.07 nuancier01.stg.phx2.fedoraproject.org Jun 30 2014 06:37:38 4 CHECK_DIFF:CHANGED copy sundry nuancier configuration task_userid:root 06.35.07 nuancier02.phx2.fedoraproject.org Jun 30 2014 06:37:38 4 CHECK_DIFF:CHANGED copy sundry nuancier configuration task_userid:root 06.35.07 nuancier02.stg.phx2.fedoraproject.org Jun 30 2014 06:37:38 4 CHECK_DIFF:CHANGED copy sundry nuancier configuration task_userid:root badges-web 06.37.46 badges-web01.phx2.fedoraproject.org Jun 30 2014 06:42:08 57 CHECK_DIFF:CHANGED copy over all our badge images task_userid:root 06.37.46 badges-web01.stg.phx2.fedoraproject.org Jun 30 2014 06:41:51 57 CHECK_DIFF:CHANGED copy over all our badge images task_userid:root 06.37.46 badges-web02.phx2.fedoraproject.org Jun 30 2014 06:43:14 57 CHECK_DIFF:CHANGED copy over all our badge images task_userid:root

2 2

Review for new rbac_playbook
by Tim Flink 27 Jun '14

27 Jun '14

I've been working to rewrite and extend the script that we've been using to control playbook execution for folks who are not in sysadmin-main. https://bitbucket.org/tflink/rbac-ansible I've been testing the script but before we actually start using it on lockbox01, I'd appreciate a review of the code to make sure I didn't miss any security holes. Injection attacks shouldn't be an issue due to usage of os.execv - all injection attempts are grouped as a single argument and will not be broken up. Tim

5 19

Plan for tomorrow's Fedora Infrastructure meeting (2014-06-25)
by Kevin Fenzi 26 Jun '14

26 Jun '14

The infrastructure team will be having it's weekly meeting tomorrow, 2014-06-25 at 18:00 UTC in #fedora-meeting on the freenode network. Suggested topics: #topic New folks introductions and Apprentice tasks. If any new folks want to give a quick one line bio or any apprentices would like to ask general questions, they can do so in this part of the meeting. Don't be shy! #topic Applications status / discussion Check in on status of our applications: pkgdb, fas, bodhi, koji, community, voting, tagger, packager, dpsearch, etc. If there's new releases, bugs we need to work around or things to note. #topic Sysadmin status / discussion Here we talk about sysadmin related happenings from the previous week, or things that are upcoming. #topic nagios/alerts recap Here we go over the last weeks alerts and see if we can find ways to make it so they don't happen again. #topic Upcoming Tasks/Items https://apps.fedoraproject.org/calendar/list/infrastructure/ #topic Open Floor Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

June status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 26 Jun '14

26 Jun '14

Greetings. You are getting this email because you are in the 'fi-apprentice' group in the fedora account system (or are reading this on the infrastructure list). Feel free to reply just directly to me, or cc the infrastructure list for everyone to see and comment on. https://fedoraproject.org/wiki/Infrastructure_Apprentice At the first of every month(or so), I am going to be sending out an email like this one. I would like feedback on how things are going for you. I'd like to ask for everyone to send me a quick reply with the following data or anything related you can think of that might help us make the apprentice program more useful. 0. Whats your fedora account system login? 1. Have you logged in and used your fi-apprentice membership to look at our machines/setup in the last month? Do you plan to? 2. Has it helped you decide any area you wish to focus on or contribute to more? 3. Have you looked at or been able to work on any of the fi-apprentice 'easyfix' tickets? https://fedorahosted.org/fedora-infrastructure/report/14 4. Do you still wish to be a member of the group? If not (for whatever reason) could you provide any hints to help others down the road? 5. Is there any help or communication or ideas you have that would help you do any of the above? 6. What do you find to be the hardest part of getting involved? Finding things to work on? Getting attention from others to help you? Finding tickets in your interest area? 7. Have you been able to make any weekly irc meetings? Do you find them helpful or interesting? 8. Whats your most used command in your bash history? (run: cut -d\ -f 1 ~/.bash_history | sort | uniq -c | sort -rn | head -n 1 | sed 's/.*/ &/g' to see) (if using zsh: history 1| awk '{print $2}' | sort | uniq -c | sort -rn | head -n1 ) Any other general feedback is also quite welcome, including improvements to this email, the wiki page, etc. Any folks I do not hear from in the next week will be removed from the group. (Note that it's easy to be readded when you have time or whatever and it's nothing at all personal, we just want to keep the group up to date with active folks). Thanks, and looking forward to your feedback! kevin

12 11

introduction
by Gonçalo Gomes 26 Jun '14

26 Jun '14

Hello Fedora Infrastructure! I'm a Linux engineer with a keen interest in Linux, OSS and Fedora in general. I want to contribute to Fedora as an outlet to get involved in the open source. I have attempted in the past to contribute to Fedora as a bugzapper, but due to other commitments taking place around the same time, this never really materialised. I am happy to contribute to fedora's infrastructure. The subjects that seem to get my attention the most are: Distributed Systems, Automation, Virtualization. I normally write most code in Python, Shell and C.. Name: Goncalo Gomes Time Zone / Country: UTC / IRELAND IRC: goncalo Interests: Distributed systems & Automation, C, Kernel and Program Analysis. Python. Contribution hours per week: upwards of 5hours, hard to estimate how much time I will be able to spend on Fedora at this stage. Skills: System Engineer/DevOps, Software Development in Python and C Having said that, I am looking for a sponsor/mentor within the group. Thank you. Goncalo N.B: I templated this email using Selva's recent introduction email. I hope it's not a big issue! And, Welcome Selva! :-)

1 0

Meeting Agenda Item: Introduction Selvakumar (Selva)
by Selvakumar M 24 Jun '14

24 Jun '14

Hello Everyone, I am looking to join Fedora project infrastructure community. I had been working on linux some years ago & tried to build email service using qmail system for one of my friend organization, which was successful at the pilot phase. It was a wonderful experience with limited Linux skill. Over the period, i groom myself in Linux specifically on system administration and scripting (automation). Now i would like to contribute for fedora project. Please find below my details. Name: Selvakumar M (Selva) Time Zone / Country: UTC +05:30 / INDIA IRC Handle: selvakumarm Interest: Design & Administer Linux Infrastructure, Automation using Perl, Linux Satellite & OpenSource Deployment (E-mail, Web, Nagios & ERP Services) Contribution hours per week: Ranging from 6 - 10 hrs Skills: System Administrator & Automation (PERL) Having said, I am looking for a sponsor/mentor within the group. Thank You !! Regards, Selva

1 0

Reliability of Fedora infrastructure to download cloud images
by Kashyap Chamarthy 23 Jun '14

23 Jun '14

[I'm not subscribed to this list, please keep me in CC.] Heya, A little while ago, we (Matthew Miller, myself, Attila Fazekas (upstream OpenStack developer) had an IRC discussion (on #openstack-qa, Freenode) with OpenStack upstream CI infrastructure folks about their concerns for continuing to have Fedora as a default to run as CI voting guest (Nova instance). They (mostly Sean Dague - a major upstream OpenStack contributor who voiced these) outlined a few issues: 1. It's not possible to download from the fedora infrastructure reliably - 10% failure rate from their cloud providers (HP and RAX). - About this point, when mattdm inquired - "is the failure in hitting the fedora mirrors or fedora core infrastructure?", their response - "I don't fully know, I think going through the url we are using we get bounced to mirrors". 2. There are possibly issues with the normal upstream fedora image that could be fixed with custom respin. - NOTE: I'm doubtful of this idea, as existing Fedora cloud images itself are not really extensively tested. I'd think focusing on _official_ cloud images and having a solid set of tests so that it can be consumed by cloud projects (OpenStack, etc). - Having a custom respin means that we're off the main path for testing of the image -- which again needs _some_ level of assurance that it can be used in a higher-level cloud project's CI infr- which again needs _some_ level of assurance that it can be used in a higher-level cloud project's CI infra. 3. Another important point OpenStack infra folks emphasized is - these images will get 4000 test runs a week on them Any suggestions to allay these are welcome. -- /kashyap

4 7

Introduction - Ethan Hussong
by Ethan Hussong 22 Jun '14

22 Jun '14

Hello all. I've been lurking in IRC and digging through some of the publicly available Fedora pages for the last couple weeks in attempt to familiarize myself with the group and the environment and thought that it was the right time to introduce myself. My name is Ethan Hussong and my IRC nick is "Xirrin". I'm in the Chicago suburbs which puts me in the Central timezone in the US. I have recently made a transition over the last few years into IT and have found myself often excited about Linux and Open Source even though I am not a programmer. I would say that my Linux skills are probably around an RHCSA-level (I've been lightly pondering taking the test for the last couple of weeks). Most of my IT experience has come in the form of beginner level network and system administration on top of the help desk jobs that I have worked that have included system performance monitoring and basic remediation. I've attached a resume as well for the sake of helping folks understand my background. As I mentioned I have some simple network and systems administration experience. I have experience building PCs as well as enterprise servers and have a small test lab of my own at home. I would like to join the Fedora Infrastructure group primarily because of my excitement for the project. I have great respect for Red Hat as far as what it provides to the world and the IT community as a whole (standards, leadership in Linux, a face for Open Source, a great platform to share with both individuals as well as companies, the list goes on...). Fedora plays a significant part in the RHEL ecosystem and because of that, despite my meager credentials, I would very much like to contribute to the cause. My hope is that going forward I will be able to start small and grow within the community. As my current job is working in a NOC it seems most appropriate to start with system monitoring and trouble remediation tasks. Additionally it seems as though there may be some opportunities to clean up some of the Nagios configuration with tweaking some alert triggers as well as making sure all of the infrastructure is actually monitored (based on what I've seen from conversation the #fedora-noc channel). I would eventually like to help with the Ansible work that is being done and hope that I can eventually help with server deployment, configuration, and decommissioning as my skills expand. Currently I have an interesting work schedule that gives me a couple of hours of free time on one week and a large amount of free time the next. My availability on a specific week is irregular, but ranges between 5 and 25 hours depending on my schedule. All that being said I am looking for a sponsor/mentor here within the FIG and hope that someone may be willing to step up and guide me to my first steps within the group. Thank you! Ethan Hussong <http://protocol.by/ehussong>

1 0

Hello World
by Hans-Peter Romfeld 20 Jun '14

20 Jun '14

Hey, EXP: Monitoring: nagios. cacti, smokeping, logstash, graphite, shinken (want to go deeper into snmp and graphical monitoring, mostly doing event_handling if some service doesnt work right now) Configuration management: puppet (interest to learn also chef) Backup: mainly script to s3 with gpg encryption, a little bit amanda, Veeam Versioning: git, svn (want to lern webDAV) Usermgmt: windowsAD, openldap (want to lern Radius, kerberus and more) Firewalls: CISCO ASA virtualization: VMware, VirtualBox (highly interested into XEN lerning) Mail: Zimbra, iRedMail Clustering: Pacemaker (interested in everythin here othen then windows) Cloud: AWS (want to lern urgently openstack) Datastore: MySql, Couchbase, Mongo, NDBCLUSTER (i am huge fan of non-sql since i touched it) CI: jenkins/pylint/nose/.. python a little bit (huge interest to learn this more) ManagementSoftware: openERP, redmine, requesttracker, bugzilla web: nginx, apache, some loadbalancing(AWS more then some) scripting: bash, python python frameworks: django, cherrypy, falcon, ...(had to do some basic webdev for app api's....) other: DNS config(want also lern howto setup my own DNS server), Vlan/SECURITY MANAGEMENT, much about windows(dont want to touch windows much again: linux: wget http://www.domain.com/myCA.pem mac: curl -LH http://www.domain.com/myCA.pem windows: (new-object System.Net.WebClient).DownloadFile('http://www.domain.com/myCA.pem','C:\tmp\rootCA.pem').... maybe something more i didnt think about yet.. I learn fast and i am very interested, i work not even 2 years in IT and have no education background ;) Cheers, Peter

1 0

Meeting Agenda Item: Introduction Libert Schmidt (resend)
by Libert R Schmidt 20 Jun '14

20 Jun '14

(sorry about the other email) IRC: lrsz Skills: Proactive Curious Work Pressure troubleshooting I would like to learn how the Fedora community works to make possible the Fedora project up to running and I also want to expand my programming and my Linux System administrator Skills.

1 0

Meeting Agenda Item: Introduction Libert Schmidt
by Libert R Schmidt 20 Jun '14

20 Jun '14

- IRC: lrsz - Skills: - Proactive - What you would like to work on and quite possibly which outstanding issues <https://fedorahosted.org/fedora-infrastructure/report/1> you would like to help resolve - After you send your "Hello World!" to the Fedora Infrastructure Group a greeter should respond to you on the mailing list offering to help you get started. But don't feel like you have to wait for this message, you can also join the #fedora-admin channel on IRC and ask for a greeter to help you out!

1 0

Meeting Agenda Item: Introduction Phillip T. George
by Phillip T. George 20 Jun '14

20 Jun '14

Hey everybody. I'm looking to join the Fedora project to give something back to the community. I've been a Linux user for quite awhile, and Linux has been a big part of a career. Previous to my current role I was a Linux sysadmin/engineer for a couple of years. My client's environment is made up RHEL (75%), Solaris (<5%), and Windows (~20%). The total server count is around 5-6K -- that does include some virtuals, but it is primarily physicals. I definitely work for a large corporation, but I'm not here to represent them in any way at this point in time. I have been using Linux distros for nearly 20 years (probably since around 1997). My current role involves automation of existing processes and tools. Its a lot of trying to introduce people to common scripting practices as well as making systems communicate that previously did not (often through an orchestration engine). I have a lot of skills/knowledge/experiences, some significant, some not so much. Programming/scripting: PHP (w/ MySQL), JS, HTML, CSS, jQuery (mostly for UI), bash, C/C++, Java, Objective C, Perl OSes: Fedora, RHEL, Mac OS X, Ubuntu, Debian, Red Hat (pre-enterprise), Windows (server 2008, server 2003, 8, 7, XP, and older OSes) Projects: 1. Fedora customized build for Linux sysadmins/engineers at work (now its a retrofit script) 2. PHP-based front-end for a change management tool -- uses an orchestration engine to do the work, though all of the orchestration steps had to be created (SOAP based in this case, though there were some pre-fabricated operations that helped with this a bit) 3. PHP-based server build/configuration tool -- just for Linux but planning on using it for other OSes eventually. Has multiple levels/objects you can configure: Server, Profile (multiple), OS (w/ hierarchy), and Site/Location 4. PHP-based report/data customized viewer -- a perl script imports a massive CSV to allow updating of the data without having to push around CSV/spreadsheet files 5. iPhone note sharing app 6. Lots of miscellaneous partially finished projects -- mostly game development projects Unfortunately these projects are not open source, so I cannot share them with you. Though the iPhone note sharing app is not open source, I have full rights to it, though I doubt anyone here is interested in that :) Obviously I have many interests. The best summary of my interests would be: computer-based technology. A more focused summary would be: Linux and programming. Today, I am interesting in doing some sysadmin/engineer and possibly web development work. Tomorrow (figuratively speaking), it may be more than that. I'm willing to provide up to 5 hours a week of my time. As far as what I would specifically like to work on -- I have no idea. Right now, I'm hear to listen, learn, and absorb. Eventually I'll find something. I will be browsing the open items to see if there is indeed something I can try to solution, though not yet knowing much details of the infrastructure makes that somewhat difficult. A quick look at the Trac tickets reveals that some cleanup of the tickets might be needed. There are some items open since 2007, which implies they may no longer be valid (unless there is a review process going on to ensure they are indeed valid). IRC: lanica -Phillip

1 0

Plan for tomorrow's Fedora Infrastructure meeting (2014-06-19)
by Kevin Fenzi 19 Jun '14

19 Jun '14

The infrastructure team will be having it's weekly meeting tomorrow, 2014-06-19 at 18:00 UTC in #fedora-meeting on the freenode network. Suggested topics: #topic New folks introductions and Apprentice tasks. If any new folks want to give a quick one line bio or any apprentices would like to ask general questions, they can do so in this part of the meeting. Don't be shy! #topic Applications status / discussion Check in on status of our applications: pkgdb, fas, bodhi, koji, community, voting, tagger, packager, dpsearch, etc. If there's new releases, bugs we need to work around or things to note. #topic Sysadmin status / discussion Here we talk about sysadmin related happenings from the previous week, or things that are upcoming. #topic nagios/alerts recap Here we go over the last weeks alerts and see if we can find ways to make it so they don't happen again. #topic Upcoming Tasks/Items https://apps.fedoraproject.org/calendar/list/infrastructure/ #topic Open Floor Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

Re-enable Greek Language on ask.fedoraproject.org
by NikTh 17 Jun '14

17 Jun '14

May I ask you to enable (re-enable) the Greek Language support on askfedoraproject.org ? It was disabled because of poor participation, but we would like to be enabled (again) and thus any local users be able to post any questions/answers on relevant section(Greek) in their own language. Relevant link of recent post in Greek Language[1]. Also read the comments. [1] https://ask.fedoraproject.org/en/question/48968/to-fedora-20-upostirizetai-… Best Regards NikTh

2 2

Plan for tomorrow's Fedora Infrastructure meeting (2014-06-12)
by Kevin Fenzi 12 Jun '14

12 Jun '14

The infrastructure team will be having it's weekly meeting tomorrow, 2014-06-12 at 18:00 UTC in #fedora-meeting on the freenode network. Suggested topics: #topic New folks introductions and Apprentice tasks. If any new folks want to give a quick one line bio or any apprentices would like to ask general questions, they can do so in this part of the meeting. Don't be shy! #topic Applications status / discussion Check in on status of our applications: pkgdb, fas, bodhi, koji, community, voting, tagger, packager, dpsearch, etc. If there's new releases, bugs we need to work around or things to note. #topic Sysadmin status / discussion Here we talk about sysadmin related happenings from the previous week, or things that are upcoming. #topic nagios/alerts recap Here we go over the last weeks alerts and see if we can find ways to make it so they don't happen again. #topic Upcoming Tasks/Items https://apps.fedoraproject.org/calendar/list/infrastructure/ #topic Open Floor Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

pkgdb2 post-mortem and strategy for future deployments
by Toshio Kuratomi 06 Jun '14

06 Jun '14

This came up in a different venue and pingou and I have continued to talk about it. Seemed that this was the right place to bring the discussion though. Some observations: * Pkgdb2 and a call for testing in staging was announced well in advance of the deployment to production (good) but not everyone understood that we were going to be breaking API (bad). * There were people inside of fedora infrastructure and outside of infrastructure who were surprised by the API break. There were also some community members and infrastructure members who heeded the call for testing and both gave feedback and ported before the deployment. * There was a FAS2 update that pkgdb2 depended upon. That was also pending in stg for a long time and also had some minor API changes (IIRC, all unintentional. I hotfixed one of them that was simply a bug last week). These also caused issues for some scripts. * Unexpected problems: we had things that we didn't know used the pkgdb API, things that weren't tested in stg because stg couldn't replicate that part of production, and things that were ported but mistakes caused the ported scripts to not be deployed or to point at stg instead of production. I saw that we had the right people on IRC throughout the day working on analyzing and patching all of the broken things so. However, this was somewhat by accident and some of those people were surprised that they spent their day doing this. Some ideas for doing major deployments in the future: 1: We have to make people aware when a new deployment means API breaks. * Be clear that the new deployment means API breaks in every call for testing. Send announcements to infrastructure list and depending on the service to devel list. * Have a separate announcement besides the standard outage notification that says that an API breaking update is planned for $date * When we set a date for the new deployment, discuss it at least once in a weekly infrastructure meeting. * See also the solution in #3 below 2: It would be really nice for people to do more testing in stg. * Increase rube coverage. rube does end-to-end testing so it's better at catching cross-app issues where API changes better than unittests which try to be small and self-contained - A flock session where everyone/dev in infra gets to write one rube test so we get to know the framework * Run rube daily - Could we run rube in an Xvfb on an infrastructure host? * Continue to work towards a complete replica of production in the stg environment. 3: "Mean time to repair is more important than mean time between failure." It seems like anytime there's a major update there's unexpected things that break. Let's anticipate the unexpected happening. * Explicitly plan for everyone to spend their day firefighting when we make a major new deployment. If you've already found all the places your code is affected and pre-ported it and the deployment goes smoothly then hey, you've got 6 extra working hours to shift back to doing other things. If it's not smooth, then we've planned to have the attention of the right people for the unexpected difficulties that arise. * As part of this, we need to identify people outside of infrastructure that should also be ready for breakage. Reach out to rel-eng, docs, qa, cvsadmins, etc if there's a chance that they will be affected. 4: Related to the FAS release: Buggy code happens. How can we make it happen less? * More unittests would be good however we know from experience with bodhi that unittests don't catch a lot of things that are changes in behaviour rather than true "bugs". Unexpected API changes that cause people porting pain can be as simple as returning None instead of an empty list which causes a no-op iteration in running code to fail while the unittests survive because they're checking that "no results were returned". * Pingou has championed making API calls and WebUI calls into separate URL endpoints. I think that coding style makes it easier to control bugs related to updating the webui while trying to preserve the API so we probably want to move to that model as we move onto the next major version of our apps. * Not returning json-ified versions of internal data structures (like database tables) but instead parsing the results and returning a specific structure would also help divorce internal changes from external API. What should we apply this to? * Probably can skip if: - Things that we don't think have API breaks - Things that are minor releases (hopefully these would correlate with not having API breaks :-) - Leaf services that are not essential to releasing Fedora. + ask, nuancier, elections, easyfix, badges, paste, nuancier + There's a lot of boderline cases too -- is fedocal essential enough to warrant being under this policy? Since the wiki is used via its API should that fall under this as well? Comments, thoughts, other ideas? Do we need to "ratify" something like this at a meeting? What's the next app deploy where we'll want to enact this? Maybe bodhi2 ;-)? -Toshio

4 4

Code review on kerneltest-harness
by Pierre-Yves Chibon 06 Jun '14

06 Jun '14

Hi all, Justin and I have been working on a small application gathering logs of kernel tests and giving the kernel maintainers some stats about these results The idea is that there is a script running tests on a kernel. That script is ran for every kernel built by the kernel team but also anyone can run the tests and also submit their results (with a final idea to provide badges to the users that do). There are three possibilities to submit one's results - Via the UI of the application, just login, select the `upload` tab at the top and upload your result file - Via curl or any other tool that can make POST request - either with an API key that is kept secret This API key is used by the automatic testing tool used by the kernel team, it ensures these results are trusted - either via a public endpoint. This endpoint support both anonymous and logged-in (via openid) uploads The challenge is of course about allowing anonymous upload while not giving too much space for people to abuse it. So we are restricting the uploads by their mime type and size (10Kb by default). The mime type is however something that is easy to circumvent but at least that means they'll check the sources. (I was just thinking, maybe we could enforce a dedicated mime type for the CL upload) Also, any file that do no contain the expected pattern will be discarded. I am fairly confident about the application but I would not mind more eyes looking at the code and checking if we missed obvious solutions to limit the potential angles of attack. For those interested: The code is at: https://github.com/jmflinuxtx/kerneltest-harness (see the frontend folder) A sample input file is at: http://paste.fedoraproject.org/107782/02061911 Thanks in advance for your help :) Pierre

1 0

Help with implementation of file uploads and thumbnail generation
by Hammad Haleem 06 Jun '14

06 Jun '14

Hello All, I was developing a Web API for Uploading and managing content. For the Feodra College Project. The API would allow basic stuff like Uploading Deleting and Uploading revisions of Content. Content can be either of following types namely Documents( PDF / DOC etc ), Images, Videos and Audio recordings. The problem I am facing here is with generating thumbnail images for these content types. Mainly for the Video and Document types. Can someone guide me on how this can be done? Or any previous efforts by anyone. -- Regards Hammad Haleem

2 1

Fedora Hosted Project Documentation -- We're back!
by Bill Wood 05 Jun '14

05 Jun '14

Hey guys, sorry for the month of silence on this; school started and I've been a bit busy. On top of that, Tropico 5 and Star Citizen's dog-fighting module have been released, so that took a lot of my time as well. :) In our meeting today I reported that I would be working on this issue again, and I've been going though the old email thread and making changes left and right. I still need you guys to chime in and make sure that this is headed in the right direction. I'm probably going to need a few people to help me gather statistics to gauge the effects of implementing this, and people to actually help me implement it. I haven't been around for too long and I don't know how everything works around here yet. Let me know what you guys think! It'd be great to get some final feedback on this. I'll be editing it as stuff comes in. Feel free to add your thoughts! Once we get this finalized I'll work on maybe getting it into the wiki (or whatever it needs to be posted to). http://paste.fedoraproject.org/107594/ ----------------------- Bill Wood FAS billwood09 IRC bwood09, #fedora-admin, #fedora-noc bwood(a)simbox.io Office: (850) 898-4198

1 0

Plan for tomorrow's Fedora Infrastructure meeting (2014-06-05)
by Kevin Fenzi 05 Jun '14

05 Jun '14

The infrastructure team will be having it's weekly meeting tomorrow, 2014-06-05 at 18:00 UTC in #fedora-meeting on the freenode network. Suggested topics: #topic New folks introductions and Apprentice tasks. If any new folks want to give a quick one line bio or any apprentices would like to ask general questions, they can do so in this part of the meeting. Don't be shy! #topic Applications status / discussion Check in on status of our applications: pkgdb, fas, bodhi, koji, community, voting, tagger, packager, dpsearch, etc. If there's new releases, bugs we need to work around or things to note. #topic Sysadmin status / discussion Here we talk about sysadmin related happenings from the previous week, or things that are upcoming. #topic nagios/alerts recap Here we go over the last weeks alerts and see if we can find ways to make it so they don't happen again. #topic Upcoming Tasks/Items https://apps.fedoraproject.org/calendar/list/infrastructure/ #topic Open Floor Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

Linux Administration experience
by Tony Ponce 02 Jun '14

02 Jun '14

Hello, My name is Tony. I am a student at FHTC technical college in Emporia, KS. I stumbled upon your project through the internet and I was interested in the fact that I could gain experience by volunteering. I have just completed two courses here at the tech college, Linux Administration 1 and Linux Administration 2. Both of these courses are part of the Network Technology program at FHTC. I am interested in pursuing my career in this field, however I have read many posts about the fact the employers will not hire without experience and this I think is where Fedora comes in. Can you please guide me in the right direction in pursuing my career in Linux Administration? Thank you for your time, Tony

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure June 2014