How tickets are resolved
Hi, I have suggestion. Can we please put into tickets how they have been resolved? I mean something else then Fixed. Something like: Fixed - puppet.git commit abc123 or Fixed - I run command rm foo.bar This way people (and apprentice group especially) can learn how infra set up works. And if ticket need to be reopened (or audited) later, you can easily what was really done. I can understand exceptions in complicated tickets, but usually it is just few commits and one or few more commands. Isn't it? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: How tickets are resolved
On Thu, Dec 19, 2013 at 04:16:33PM +0100, Miroslav Suchý wrote: I have suggestion. Can we please put into tickets how they have been resolved? I mean something else then Fixed. Something like: Fixed - puppet.git commit abc123 or Fixed - I run command rm foo.bar This way people (and apprentice group especially) can learn how infra set up works. And if ticket need to be reopened (or audited) later, you can easily what was really done. I can understand exceptions in complicated tickets, but usually it is just few commits and one or few more commands. Isn't it? IMHO it is always good to at least shortly explain what happened. Not only in tickets but also in IRC. Regards Till ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: How tickets are resolved
On Thu, 19 Dec 2013 19:05:57 +0100 Till Maas opensou...@till.name wrote: On Thu, Dec 19, 2013 at 04:16:33PM +0100, Miroslav Suchý wrote: I have suggestion. Can we please put into tickets how they have been resolved? I mean something else then Fixed. Something like: Fixed - puppet.git commit abc123 or Fixed - I run command rm foo.bar This way people (and apprentice group especially) can learn how infra set up works. And if ticket need to be reopened (or audited) later, you can easily what was really done. I can understand exceptions in complicated tickets, but usually it is just few commits and one or few more commands. Isn't it? IMHO it is always good to at least shortly explain what happened. Not only in tickets but also in IRC. Yeah. I'm happy to try and start being more verbose where possible and ask others to do the same. In some cases it may well not be however. kevin signature.asc Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: https://apps.fedoraproject.org/packages broken again?
On Wed, Dec 18, 2013 at 11:46:14PM +0800, Christopher Meng wrote: zmap It should be back now - https://apps.fedoraproject.org/packages/zmap A puppet upgrade caused a gluster issue that caused the indexer to lose control of its lock files. That's been resolved and it should be indexing nightly again. pgpnVVxdhnh6j.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: https://apps.fedoraproject.org/packages broken again?
On Wed, Dec 18, 2013 at 07:40:12PM +0330, james Abtahi wrote: On 12/18/2013 04:46 AM, Christopher Meng wrote: Hi, I can't find any information of packages recently added to pkgdb, I think the data hasn't been synchronized, can someone have a look at it? I'm experiencing the same issue too. Even though my package (yarock) has been pushed to fedora stable repos since two days ago I can't find it in apps.fedoraproject.org/packages. I thought perhaps it'd take some time to get synchronized but so far searching it would return nothing :( Best, James James, It finally got indexed: https://apps.fedoraproject.org/packages/yarock pgpC4ijXwt460.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: https://apps.fedoraproject.org/packages broken again?
On Thu, Dec 19, 2013 at 12:09 PM, Ralph Bean rb...@redhat.com wrote: It should be back now While you're messing around with it...is the sources tab supposed to work? The request it does has always returned a 500 for me. :-( GET https://apps.fedoraproject.org/packages/_w/package.sources?package_name=v8subpackage_of= 500 (Internal Server Error) jquery.js:8102 send jquery.js:8102 jQuery.extend.ajax jquery.js:7580 moksha.ajax_load moksha.js:634 moksha.html_load moksha.js:563 moksha.dynamic_goto moksha.js:418 tab_selected (index):267 sources_tab_selected (index):225 onclick (index):228 -T.C. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: https://apps.fedoraproject.org/packages broken again?
On Thu, Dec 19, 2013 at 12:17:16PM -0700, T.C. Hollingsworth wrote: On Thu, Dec 19, 2013 at 12:09 PM, Ralph Bean rb...@redhat.com wrote: It should be back now While you're messing around with it...is the sources tab supposed to work? Yeah, there's a thousand of these little things :( This particular one is on my list for after the holidays. I added a new nagios check as of a week or so ago that checks for this functionality specifically. The request it does has always returned a 500 for me. :-( Its working for me right now, but it goes out intermittently/frequently: https://apps.fedoraproject.org/packages/v8/sources/spec/ The issue is that an rpmdb gets corrupted somehow. I *think* its due to a race condition between the webapp, a cron job, and a cache warming daemon. We likely just need to introduce some locking in those places to get it to stop. Right now, if the cron job detects that the rpmdb is corrupt, it rebuilds it and that sets it to working again until the next time it melts down. pgp6gHt17kOki.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Summary/Minutes from today's Fedora Infrastructure meeting (2013-12-19)
#fedora-meeting: Infrastructure (2013-12-19) Meeting started by nirik at 19:00:03 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-12-19/infrastructure.2013-12-19-19.00.log.html . Meeting summary --- * welcome y'all (nirik, 19:00:04) * New folks introductions and Apprentice tasks (nirik, 19:01:40) * Applications status / discussion (nirik, 19:08:46) * ACTION: nirik to coordinate with pingou about cnucnuweb and legal concerns, will talk to fedora-legal (nirik, 19:16:27) * new python-fedora out later today for testing (nirik, 19:20:49) * badges server can now authorize specific users to hand out specific badges. (nirik, 19:23:07) * Sysadmin status / discussion (nirik, 19:24:25) * upgraded to puppet 2.7 without too much pain (nirik, 19:24:44) * updates will be applied later today and non outage causing reboots done. (nirik, 19:31:10) * Upcoming Tasks/Items (nirik, 19:33:41) * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/ (nirik, 19:33:41) * Open Floor (nirik, 19:40:45) * LINK: http://en.wikipedia.org/wiki/CRIME_%28security_exploit%29 (tyll_, 19:43:57) * LINK: http://www.data.gouv.fr/ (threebean, 19:46:44) * no meetings next two weeks. (nirik, 19:49:44) Meeting ended at 19:50:01 UTC. Action Items * nirik to coordinate with pingou about cnucnuweb and legal concerns, will talk to fedora-legal Action Items, by person --- * nirik * nirik to coordinate with pingou about cnucnuweb and legal concerns, will talk to fedora-legal * pingou * nirik to coordinate with pingou about cnucnuweb and legal concerns, will talk to fedora-legal * **UNASSIGNED** * (none) People Present (lines said) --- * nirik (107) * abadger1999 (30) * threebean (29) * tyll_ (10) * relrod (8) * zodbot (6) * smooge (4) * janeznemanic (4) * lmacken (3) * ianweller (1) * fchiulli (1) * docent (1) * tflink (1) * puiterwijk (0) * mdomsch (0) * pingou (0) * dgilmore (0) -- 19:00:03 nirik #startmeeting Infrastructure (2013-12-19) 19:00:03 zodbot Meeting started Thu Dec 19 19:00:03 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:03 zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:04 nirik #meetingname infrastructure 19:00:04 nirik #topic welcome y'all 19:00:04 nirik #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 19:00:04 zodbot The meeting name has been set to 'infrastructure' 19:00:04 zodbot Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 19:00:34 * ianweller is hereish 19:00:38 * tflink is lurking 19:00:44 * threebean is here 19:01:23 * relrod here 19:01:25 * abadger1999 is here 19:01:34 nirik morning everyone. 19:01:40 nirik #topic New folks introductions and Apprentice tasks 19:01:55 nirik any new folks like to introduce themselves? or apprentices with questions or comments? 19:02:11 janeznemanic me 19:02:25 nirik hey janeznemanic 19:02:32 janeznemanic guys do i ask to many questions 19:02:35 * lmacken here 19:02:49 nirik janeznemanic: not at all. ;) questions are good... 19:02:50 threebean janeznemanic: no 19:02:54 threebean :) 19:03:16 janeznemanic okey then 19:03:50 nirik we may not get to them as fast as you like, but we will get there. ;) 19:04:15 janeznemanic the important thing is that you get there 19:04:33 tyll_ I would like to become an apprentice 19:05:02 nirik hey tyll_ 19:05:15 nirik love to have you help out and look around... I can add you after the meeting. 19:06:04 * docent is late :) 19:06:17 nirik hey docent 19:06:50 tyll_ thanks, not sure what to write to introduce myself - I wold like to get a fedmsg service running for rel-eng 19:07:15 * fchiulli is also late 19:07:23 nirik thats a good quantifyable goal. ;) 19:07:38 nirik morning fchiulli 19:07:42 threebean tyll_: cool :) I'm glad to try and help wherever I can 19:08:27 nirik ok, shall we move on to applications? 19:08:46 nirik #topic Applications status / discussion 19:08:49 tyll_ threebean: thank you, I assume I will need it 19:08:56 nirik any application news this week or upcoming? 19:09:53 * nirik listens to the crickets. :) 19:09:57 threebean nothing much here. ;) 19:09:59 tyll_ Is cnucnuweb already an officially planned Fedora App? I was wondering whether it will be ok to use it for RPMFusion as well 19:10:23 threebean tyll_: well, pingou has been spearheading it and he's not here today. 19:10:36 threebean but I'm pretty sure resources have already been allocated for it. 19:10:37 nirik yeah. it is in the planning stages tho 19:10:46 * threebean nods 19:11:09 nirik tyll_: you were thinking of using the same fedora one for rpmfusion? or a seperate install somewhere? 19:11:23 nirik
Holiday Freezing
Man, it's cold in here... :) At the meeting today we decided for over the holiday (thats starting the late afternoon of 2013-12-20 and until 2014-01-06) we would do a relaxed freeze. This means: * Fixing existing things that are broken or outage is fine. * If you are adding something new or making config changes, please send them to the list and get at least one +1 from anyone. * Remember that many people are away enjoying their holidays so avoid doing things that cause alerts or outages. * This is a great time to update docs or make plans for changes to be done in the new year if you are inclined. I'd like to wish everyone a happy holiday season and I hope it's restful and enjoyable. kevin signature.asc Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
2014 dreaming
Greetings. I meant to send this out sooner, but with the Fedora 20 release things have been crazy. :) Now that we are nearing the end of 2013, I think it might be a nice time to think ahead to next year. What would you love to see happen? What would you like to work on making happen? (even if it's not practical resource wise or logistically) Here's a list of some of mine: * 0 downtime upgrades. By this I mean we can update and reboot all our servers (probibly in some specific order with specific actions between) and not have to schedule any downtime or notify users anything is going on. This means at least that we have db replication/failover working and 2 of everything. * Migration to ansible fully done, with all hosts moved over and rebuilt and working. * Migration to RHEL7. :) * Ticket queue down to a very small set. When I first started it was gigantic, then I closed/fixed/redirected a lot of the ticket and we started going down in number, but over the last year or so we have hovered between 140-150. * Migration to hyperkitty/mailman3 complete with all lists moved. * All hosts selinux enforcing. :) * No app servers left. All applications split out to their own (at least pair) of instances. * Logging from every app/server goes to a known place and we process them all looking for problems. I'll probibly think of some more, will send them to this thread when I do. So how about you? Any big dreams for 2014? Hopefully we can make at least some of them real. kevin signature.asc Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: 2014 dreaming
Is it possible to use gitlab to replace cgit? Thanks. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: 2014 dreaming
On Fri, Dec 20, 2013 at 07:43:50AM +0800, Christopher Meng wrote: Is it possible to use gitlab to replace cgit? I would say no. gitlab would really be more of a trac replacement. cgit is a lightweight web frontend for git repositories. Two different purposes. -Toshio pgpcc4VcI4kBY.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
