August 2011 - infrastructure - Fedora mailing-lists

new hosts plans and thoughts
by Kevin Fenzi 12 Sep '11

12 Sep '11

As some of you may have noted, I've been building up some new hosts of late. I thought I would give an overview here and plans moving forward and provide a list left to do for those folks in sysadmin-main who wish to help out. :) We have 4 old xen boxes that are going out of service at the end of next month, so we need to get all guests off them before then. Those are: xen03, xen05, xen09, xen15. We have new machines: virthost05-10 and bvirthost04 On the rel-eng side: * I have setup a releng03 to replace releng01 on bvirthost04 * I have setup a releng04 to replace releng02 on bvirthost01 * I have setup a kojipkgs02 to replace kojipkgs02 on bvirthost04 I need to get them finished up and access to the netapp mounts, then we can look at migrating over to them. Once we migrate, bxen03 will be empty and can be re-installed as bvirthost05. We might look then at moving things around a bit to take advantage of bvirthost05. The only outage here would be kojipkgs, and we could make that pretty short/fast. On the staging front: * We need to make a db02.stg thats rhel6. Soon all our db's will be rhel6, and we want staging to match up. I think we should use virthost10 for this. * We need to migrate fas01.stg and pkgs01.stg to virthost10. These are already rhel6. I suppose we could re-install them, but migrating seems reasonable to me. * We may want to migrate some or all the stg on virthost13. virthost13 is now out of warentee. We might not care too much since it's only stg there. Thoughts? On the production front: * I have made a db01 on virthost04. This will replace db02. I'd like to look at doing this wed next week. (2011-09-07). This WILL require an outage, since db02 has fas on it along with many other things. Should we do this outage in the evening? Other thoughts on time? * I have made a bastion03 on virthost04. This will replace bastion02. We will need to swap IP's for it to work with the external IP in phx2. I figure we can do this at the same time as the db outage above. * Machines that still need building/setting up for you sysadmin-main folks who want to help out: - bastion04 to replace bastion01. Should be on a different virthost from bastion03. - proxy08 to replace proxy1 (rhel5). - value03 and value04 (on different virthosts) to replace value01/02. - app02 and app04 are on those xen boxes, so we need to move them. We can't do RHEL6 yet however. So, we could wait a bit more in hopes of being able to rebuild them as RHEL6, or just migrate them, or rebuild them as RHEL5. Once this is all done that leaves us with just xen04 as a xen box in phx2. We can then look at moving stuff off it and repaving it as virthost11. kevin

2 2

Plan for tomorrow's Fedora Infrastructure meeting (2011-09-01)
by Kevin Fenzi 01 Sep '11

01 Sep '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-09-01 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * Upcoming new machine plans. * Upcoming Tasks/Items (nirik) 2011-08-31: send out outage announcement for next week 2011-09-01 infra meeting 2011-09-01 mail fi-apprentice folks. 2011-09-06: Outage to migrate from db02 to db01 and bastion02 -> bastion03 2011-08-31 send infra meeting agenda 2011-09-13 - 27: Beta change freeze 2011-09-09 Remove inactive fi-apprentice people. 2011-09-27: Fedora 16 Beta 2011-10-01 mail fi-apprentice folks. 2011-10-09 Remove inactive fi-apprentice people. 2011-10-18 - 2011-11-01: Final change freeze 2011-11-01: Fedora 16 release. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/report/10 NOTE: I have cleaned out the ones that have been sitting around with this tag. Anytime anyone would like to discuss a ticket, just add the meeting keyword and we will get to it in this section. 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

Missing logs?
by Paul W. Frields 30 Aug '11

30 Aug '11

The proxy logs prior to 2011-08-27 seem to be missing on the log02 host. Is this related to the recent proxy outage? Are these logs retrievable? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com

2 1

Re: infrastructure Digest, Vol 63, Issue 32
by Jesse N. Richardson 29 Aug '11

29 Aug '11

Guys, I know I missed this meeting. But just to let you guys know ahead of time; I'm going to explain why I won't be /that /active in the next few months. The following things will take up most of my time: 1. I'm getting married soon (yay!) 2. I'm going back to college 3. I'm working on the days that I'm not in college. I hope you guys can understand. I'm still going to try my best to help out as much as I can. On 08/26/2011 08:00 AM, infrastructure-request(a)lists.fedoraproject.org wrote: > Send infrastructure mailing list submissions to > infrastructure(a)lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.fedoraproject.org/mailman/listinfo/infrastructure > or, via email, send a message with subject or body 'help' to > infrastructure-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > infrastructure-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of infrastructure digest..." > > > Today's Topics: > > 1. Plan for today's Fedora Infrastructure meeting (2011-08-25 at > 19UTC) (Kevin Fenzi) > 2. Summary/Minutes from today's Fedora Infrastructure meeting > (2011-08-25 at 19UTC) (Kevin Fenzi) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 25 Aug 2011 09:28:19 -0600 > From: Kevin Fenzi<kevin(a)scrye.com> > Subject: Plan for today's Fedora Infrastructure meeting (2011-08-25 at > 19UTC) > To: infrastructure(a)lists.fedoraproject.org > Message-ID:<20110825092819.2b4172f8(a)ohm.scrye.com> > Content-Type: text/plain; charset="us-ascii" > > The infrastructure team will be having it's weekly meeting today: > 2011-08-25 at 1900 UTC in #fedora-meeting on the freenode network. > > Suggested topics (suggested by whom): > > * New folks introductions and Apprentice tasks. > > * Upcoming Tasks/Items (nirik) > > 2011-08-23: Fedora 16 alpha > 2011-09-01 mail fi-apprentice folks. > 2011-09-13 - 27: Beta change freeze > 2011-09-09 Remove inactive fi-apprentice people. > 2011-09-27: Fedora 16 Beta > > * Meeting tagged tickets: > https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… > > 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 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 198 bytes > Desc: not available > Url : http://lists.fedoraproject.org/pipermail/infrastructure/attachments/2011082… > > ------------------------------ > > Message: 2 > Date: Thu, 25 Aug 2011 13:38:29 -0600 > From: Kevin Fenzi<kevin(a)scrye.com> > Subject: Summary/Minutes from today's Fedora Infrastructure meeting > (2011-08-25 at 19UTC) > To: Fedora Infrastructure<infrastructure(a)lists.fedoraproject.org> > Message-ID:<20110825133829.46149824(a)ohm.scrye.com> > Content-Type: text/plain; charset="us-ascii" > > ============================================ > #fedora-meeting: Infrastructure (2011-08-25) > ============================================ > > Meeting started by nirik at 19:00:01 UTC. The full logs are available at > http://meetbot.fedoraproject.org/fedora-meeting/2011-08-25/infrastructure.2… > > Meeting summary > --------------- > * Robot Roll Call (nirik, 19:00:01) > > * New folks introductions and Apprentice tasks. (nirik, 19:01:23) > > * Upcoming Tasks/Items (nirik, 19:03:18) > > * Meeting tagged tickets: (nirik, 19:19:05) > * LINK: > https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… > (nirik, 19:19:05) > > * Open Floor (nirik, 19:20:50) > * ask fedora RFR: I am going to see if I can help mether get an > initial cut added to puppet for staging. It doesn't look too hard to > puppetize (nirik, 19:26:01) > * paste RFR: need to ask herlo status. He was fixing bugs in the epel > package (nirik, 19:26:21) > > Meeting ended at 19:37:29 UTC. > > > > > Action Items > ------------ > > > > > > Action Items, by person > ----------------------- > * **UNASSIGNED** > * (none) > > > > > People Present (lines said) > --------------------------- > * nirik (71) > * skvidal (41) > * abadger1999 (17) > * rfelsburg (12) > * lmacken (8) > * zodbot (4) > * jsmith (1) > * CodeBlock (1) > * tibbs (1) > * smooge (0) > * ricky (0) > * codeblock (0) > -- > 19:00:01<nirik> #startmeeting Infrastructure (2011-08-25) > 19:00:01<zodbot> Meeting started Thu Aug 25 19:00:01 2011 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. > 19:00:01<zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. > 19:00:01<nirik> #meetingname infrastructure > 19:00:01<zodbot> The meeting name has been set to 'infrastructure' > 19:00:01<nirik> #topic Robot Roll Call > 19:00:01<nirik> #chair smooge skvidal codeblock ricky nirik abadger1999 > 19:00:01<zodbot> Current chairs: abadger1999 codeblock nirik ricky skvidal smooge > 19:00:14 * skvidal is here > 19:00:21 * rfelsburg is here > 19:00:23 * CodeBlock here > 19:00:34<abadger1999> boa tardes > 19:00:48<skvidal> what did you just call us? > 19:00:56<skvidal> :) > 19:00:57<rfelsburg> you heard him > 19:01:00<abadger1999> skvidal: Do you really want to know? ;-) > 19:01:06<skvidal> abadger1999: I think I do know > 19:01:09<jsmith> skvidal: He called you a fine fella... > 19:01:09<skvidal> that's the problem! > 19:01:11<abadger1999> hehe > 19:01:17<nirik> ha > 19:01:22 * skvidal storms around in a huff > 19:01:23<nirik> #topic New folks introductions and Apprentice tasks. > 19:01:27<skvidal> *huff* > 19:01:40<abadger1999> skvidal: too much paint is bad for the brain > 19:01:45<nirik> Any new folks want to say hi or ask questions? any apprentice tasks/tickets anyone wants to discuss? > 19:01:54<skvidal> abadger1999: you mean wall candy? > 19:02:42 * rfelsburg says hi. > 19:02:48<nirik> welcome rfelsburg. > 19:02:56<rfelsburg> ty. > 19:03:11<nirik> ok, moving along... > 19:03:18<nirik> #topic Upcoming Tasks/Items > 19:03:27<nirik> so, we are out of freeze. > 19:04:01<nirik> any upcoming plans folks would like to talk about/ > 19:04:04<nirik> I have a few... > 19:04:22<nirik> we finally are getting all out new machines on line in phx2. > 19:04:30 * abadger1999 is finally making tie to deploy raffle > 19:04:41<nirik> abadger1999: cool. > 19:05:01<nirik> once we have new machines installed and added to monitoring, we can: > 19:05:39<nirik> look at whats on xen03/05/09/15 and migrate those things to (hopefully) new rhel6 instances on the new virthosts. > 19:05:52<nirik> those 4 machines are out of warentee at the end of next month. > 19:06:22<nirik> also, will look at migrating more rel-eng stuff to rhel6 > 19:06:49<nirik> we still need community to work to move to rhel6 app servers. > 19:06:49 * skvidal looks at virthost-lists.out and wonders what broke > 19:07:11 * skvidal runs vmdiff > 19:07:13<lmacken> nirik: yeah, i'm working on the whole tg2/moksha/fedoracommunity on RHEL6 thing... > 19:07:39<nirik> lmacken: yeah, thanks for that. ;) > 19:08:04 * lmacken just deployed a new fedoracommunity bugfix release... hopefully no more log spamming too :) > 19:08:10<nirik> hurray > 19:08:13<skvidal> lmacken: cool > 19:08:47<nirik> I have some random projects on my todo list anyone else is welcome to take and run with: > 19:09:11<nirik> * setup arpwatch on dhcp01/noc01, so we can notice if something new plugs into our networks in phx2. > 19:09:26<nirik> * add ipv6 to noc02 and get ipv6 monitoring working. ;) > 19:09:45<nirik> * more bcfg2 work in qa > 19:10:09<nirik> * get clamav filter working with mailman > 19:10:12<skvidal> * setup and config sec on log02 for specific log event alert > 19:10:23<lmacken> arpwatch sounds interesting. would it trigger a nagios alert or something? > 19:10:30<nirik> lmacken: it does email by default. > 19:10:41 * lmacken runs arpon --static on all of his machines to force static arp tables (to mitigate mitm) > 19:10:44 * rfelsburg will brb > 19:10:52 * skvidal does not need a page about a new mac :) > 19:10:56<nirik> mails you the mac address and a thing looking it up to see what vendor, etc. > 19:11:04<nirik> it should be rare. > 19:11:36<tibbs> I use arpwatch here and find it useful. > 19:11:49<skvidal> * plan combining hosted01's mailing lists with collab1's lists > 19:11:51 * nirik uses it at home. > 19:12:01<skvidal> tibbs: it is useful - not sure we need to stow stuff into nagios for it, though > 19:12:09<skvidal> an email or even just a log notice about it sshould be sufficient > 19:12:32<nirik> On the hosted/collab front, I am still waiting to hear back from serverbeach... I wonder if they got confused about our status as donated or something. > 19:12:39 * nirik will followup on that. > 19:13:09<skvidal> nirik: wouldn't shock me :) > 19:13:48<nirik> so the xen move stuff will entail some outage... since db02 is in there... I'll try and come up with a schedule/plan. > 19:14:10<nirik> anyhow, any other upcoming plans? any releases for pkgdb/other apps? > 19:14:30<lmacken> i'll probably do a bodhi bugfix release tomorrow > 19:14:40<abadger1999> We might hotfix some pkgdb stuff before next freeze but we're not going to fit a new release in. > 19:15:06<abadger1999> I'm waiting with elections until we get tg2 stack fixed for rhel6 and rhel6 app servers. > 19:15:09<nirik> ok. > 19:15:30<abadger1999> Since it'll be a tg2 port. > 19:15:31<nirik> lmacken: will that fix the override needs commit on rawhide thing? > 19:15:54<lmacken> nirik: yes, it will > 19:15:59<nirik> excellent. > 19:16:12<lmacken> that patch isn't written yet, but I'll make sure to get it done before the release. should be simple. > 19:16:32<nirik> so it should just need commit on that branch or provenpackager? > 19:16:59 * rfelsburg back > 19:17:11<lmacken> nirik: yep. that logic is already written for the updates portion of bodhi, so I just need to copy/paste/tweak > 19:17:23<nirik> cool. > 19:17:58<skvidal> the virthost-lists output is fixed > 19:18:08<skvidal> and the bug causing it ot be mostly empty is corrected > 19:18:15<skvidal> (sorry for the interruption) > 19:18:16<nirik> oh, I am also going to make the log02 changes I posted to the list a while back... unless folks have objections? basically allow apprentice and make the logs readable to apprentice... > 19:18:24<skvidal> worksforme > 19:19:05<nirik> #topic Meeting tagged tickets: > 19:19:05<nirik> https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… > 19:19:21<nirik> any specific tickets folks want to talk about? > 19:19:45 * nirik is going to look at cleaning out the meeting tagged tickets. > 19:19:56<nirik> just put it on those ones we really do want to talk about at meetings. > 19:20:45 * nirik listens to the crickets. > 19:20:50<nirik> #topic Open Floor > 19:20:57<nirik> Anyone have items for open floor? > 19:22:04<skvidal> anyone want to work on the func2nagios stuff? > 19:22:27<skvidal> it's not hard to get started and it would mean never having to ask for the basic host entry for just seeing if the box is running, etc > 19:22:59<rfelsburg> Since this has been circulating for the last week or so give or take, are we doing anything to mitigate the range header problem in apache? > 19:23:23<skvidal> rfelsburg: I suspect wait for the patch > 19:23:32<nirik> skvidal: might file a ticket on it and we can point people to it? > 19:23:34<rfelsburg> skvidal: is that puppet? the func2nagios stuff > 19:23:43<skvidal> rfelsburg: is it puppet? > 19:23:50<nirik> rfelsburg: yes, waiting for the fix. None of the workarounds are that good. > 19:24:00<rfelsburg> nirik: thanks. > 19:24:11<skvidal> rfelsburg: no - func2nagios - take list of hosts from func - do some magic to them, ask them for listening ports, dump out host entries and some basic service entries for them > 19:24:11<rfelsburg> skvidal: is the func2nagios stuff puppet related? > 19:24:27<rfelsburg> skvidal: gotcha, sorry no experience with that or i would > 19:24:39<skvidal> rfelsburg: it is mainly b/c maintianing simple, common, repeptive host entries in puppet is irritating > 19:25:21<rfelsburg> skvidal: makes sense. > 19:25:25<nirik> oh, also: > 19:26:01<nirik> #info ask fedora RFR: I am going to see if I can help mether get an initial cut added to puppet for staging. It doesn't look too hard to puppetize > 19:26:21<nirik> #info paste RFR: need to ask herlo status. He was fixing bugs in the epel package > 19:27:00<nirik> ok, if nothing else, we can call it a short meeting and get back to infraing. > 19:27:04<abadger1999> There's been some changes to hosted that people should be aware of > 19:27:13<nirik> oh yes, might be good to note those... > 19:27:47<abadger1999> I changed the hosted restricted ssh command script in the past week for a few issues > 19:27:55<abadger1999> Added ability to upload to releases via rsync > 19:28:00<abadger1999> Removed monotone support > 19:28:39<skvidal> yay > 19:28:49<skvidal> can we remove svn, hg and bzr support too? > 19:28:53 * skvidal watches abadger1999 twitch > 19:28:53<nirik> abadger1999: did you see the followup about timestamps with rsync? > 19:28:54<abadger1999> And did my best to lock down bzr and hg -- before they were able to write to the user's ome dir (and thus overwrite authorized_keys and thus get them an ssh shell instead of being locked into only running SCM commands) > 19:29:14<abadger1999> nirik: I did... but I don't know what we'd need to do there. > 19:29:17<skvidal> abadger1999: good job > 19:29:24<abadger1999> nirik: I'm only limiting the directory paths in the script. > 19:29:27<nirik> yeah, I'm not sure if thats possible if you aren't root. > 19:29:37<nirik> but perhaps it should be. Will look. > 19:30:06<abadger1999> nirik: Thanks. I can help with coding.. but I don't know what rsync options (if they exist) we'd need to inject. > 19:31:19<nirik> we don't really have any way to announce things to hosted people do we? > 19:31:56<skvidal> nirik: I guess we can email every account on the machine > 19:31:59<abadger1999> anyhow.. If there's some sort of authenticated, scm-specific issue in the next week, let me know as it might be the updated script. > 19:32:05<nirik> I thought once about: make a fedorahosted-announce list, invite all project owners to it. Would that be viable? > 19:33:06<nirik> it would be nice to have a place to announce stuff, but allow them to opt into that spamming. ;) > 19:33:29<skvidal> nirik: how much just make a list of all of them on-the-fly > 19:33:38<skvidal> and only enable the list when we need it > 19:34:12<nirik> I suppose. I bet we get people telling us they don't care... but that could work. > 19:34:20<nirik> ie, please remove me from your list. > 19:34:53<nirik> we can work out the details out of band... > 19:35:13<nirik> in addition to this rsync addition, I'd like to be able to announce the new hosted machine, migration, etc. > 19:35:38<skvidal> nirik: if they want to be removed from the list then they can stop using hosted > 19:35:40<skvidal> :) > 19:35:50<nirik> indeed. > 19:35:52<skvidal> nirik: but as long as the list defaults to 'off' when not in use > 19:35:57<skvidal> it's not like it will be a spam sync > 19:36:01<nirik> true. > 19:36:02<skvidal> I dunno > 19:36:04<skvidal> that might be silly > 19:36:11 * skvidal doesn't really have a dog in the fight much > 19:36:38<nirik> ok, any other items? or shall we call it a meeting? > 19:37:26<nirik> ok. Thanks for coming everyone! > 19:37:29<nirik> #endmeeting > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 198 bytes > Desc: not available > Url : http://lists.fedoraproject.org/pipermail/infrastructure/attachments/2011082… > > ------------------------------ > > _______________________________________________ > infrastructure mailing list > infrastructure(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/infrastructure > > End of infrastructure Digest, Vol 63, Issue 32 > **********************************************

1 0

logs and emails
by Kevin Fenzi 27 Aug '11

27 Aug '11

Greetings. Two items I'd like some feedback on... 1. Would there be any downsides to switching sysadmin-qa over to requiring just 'cla_done' instead of sysadmin? The QA admins get seperate nagios emails to sysadmin-qa on their machines, and don't use our puppet so they don't care about commit emails. Is there some other reason sysadmin needs to be a requirement for sysadmin-$foo groups? 2. I'd like to allow apprentice folks to look at logs on log02. Currently this is just sysadmin-main and -noc. Can anyone think of anything we log that might be too sensitive for this? We shouldn't be logging any passwords (although I can look). I'd also like to make sure all the logs on log02 are ro to everyone (but main). Currently many of the directories there are writable for sysadmin group, which seems wrong to me. Thoughts? Concerns? Stories? kevin

2 5

Plan for today's Fedora Infrastructure meeting (2011-08-25 at 19UTC)
by Kevin Fenzi 25 Aug '11

25 Aug '11

The infrastructure team will be having it's weekly meeting today: 2011-08-25 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * Upcoming Tasks/Items (nirik) 2011-08-23: Fedora 16 alpha 2011-09-01 mail fi-apprentice folks. 2011-09-13 - 27: Beta change freeze 2011-09-09 Remove inactive fi-apprentice people. 2011-09-27: Fedora 16 Beta * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 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

Hosted plans
by Kevin Fenzi 24 Aug '11

24 Aug '11

Greetings. I thought I would throw out some plans for hosted moving forward and see if we could hash out a plan and some timetable for implementing things. == Current status/setup/problems == Hosted is 2 machines. One primary (hosted01) and one spare (hosted02). There is an hourly rsync of data from 01->02. 02 is completely standby, it takes none of the load or requests, it's simply there in case hosted01 dies. Hosted01 has the following items on it: * apache/httpd gitweb other scm web trac mailman archive http access source downloads (tar.gz, etc) loggerhead reviewboard * rsync * scm checkouts * scm checkins * lists.fedorahosted.org mailman * spamassassin for lists. Issues with current setup: * hosted01 is under heavy load much of the time. Needs to be more responsive. * hosted01 is rhel5 and very old trac. rhel6 has a much newer trac. * If hosted01 dies we could loose up to 1 hour of data with switching to hosted02. * hosted01/02 are at serverbeach. If they are off line, hosted is off line. === Short term plan === * Create a hosted-lists01/02 (or whatever we want to call them) sync all lists and list data to it. make sure dns is happy on it. Move all lists.fedorahosted.org over to these new machines. This will move some of the load off the existing hosted01/02 setup, and should be a pretty easy thing to do. We will just setup them like collab01/02 and hosted01/02 are with a live machine and hot spare (unless we can use some shared fs somehow?) Questions: - Should these be at serverbeach? Or one there and one somewhere else? (There is approx 23GB of mailman archives on hosted01 currently). * Create a hosted03/04 Setup rhel6 versions of hosted01/02 Setup in similar way, except with no lists (see above). Ask hosted project owners to 'opt-in' to moving to the new machines. Get a small pool of things at first, then move more as any issues are fixed. Once everything looks stable, announce a cut over date, and just move all the rest over then. Questions: - Should these be at serverbeach? Or one there and one somewhere else? (There is approx 90GB of data on hosted01 currently). * Look at some caching. Could we add memcached on hosted03/04 easily? What about varnish? Questions: - What of the things we have would use caching well? === Long term plan === We kicked around some plans here in several of our meetings, but did a poor job of recording that anywhere. ;) Some things we talked about: * A caching frontend of some kind. Could cache web requests and take load off the main machines. * Some way to distribute the data, so if serverbeach were off line we could still switch to and use another machine. * Adding more/different services. IRC commit bot redmine (still not in fedora, but people are working on it) your idea here. So, what do folks think? Should we try and come up with more concrete longer term plans before acting on the short term ones? Are there other paths forward that make sense here? kevin

12 28

unfrozen
by Kevin Fenzi 24 Aug '11

24 Aug '11

Just a reminder that we are now unfrozen since Fedora 16 Alpha has gone out. Please do be careful with changes as always. Our next freeze is for F16Beta, starting 2011-09-13. Thanks, kevin

1 0

New user to Join Fedora Team
by Arunk Amu 23 Aug '11

23 Aug '11

Dear Fedora Team, I'm Arun Amu. Working as a Infrastructure Consultant for Linux related development and deployment services. I would like to join Fedora team to, contribute myself and to learn more about Fedora development and technologies. I've been using Linux since my collage days. I'm good at deploying application and debugging servers. I know scripting language such as, bash, python and programming language such as C, Java. I'm also doing security consulting for Linux hosted applications. Have good experience, on penetration testing, conducting security assessment for operating system and tools reverse engineering. I can spend two hours in weekdays and four hours at weekends. :-) Let me know, where to start? ## Amu Arun Quote: Imagination is more important knowledge _AE

2 1

Freeze break: fedoracommunity bugfix release
by Luke Macken 23 Aug '11

23 Aug '11

I would like to do a minor bugfix release for fedoracommunity, as soon as possible. This release contains the following changes: - Fixes to our bodhi/koji/pkgdb connectors to work with koji's new dist tag scheme - A couple more cvs->git link fixes This update will fix a bunch of broken widgets, and it will also stop flooding many of our inboxes with tracebacks. If regressions occur, this RPM can easily be downgraded. Thanks, luke

2 3

Freeze break: add cname for existing tier0 mirror
by Kevin Fenzi 22 Aug '11

22 Aug '11

Turns out this mirror in our rsync acls has 2 names and if dns picks up the other one they get denied. I'd like to add their other name in so they can sync more reliably. odysseus.fi.muni.cz odysseus.linux.cz diff --git a/modules/rsync/files/rsyncd.conf.download-phx b/modules/rsync/files/rsyncd.conf.download-phx index 5ba9e05..c9f3fd5 100644 --- a/modules/rsync/files/rsyncd.conf.download-phx +++ b/modules/rsync/files/rsyncd.conf.download-phx @@ -63,7 +63,7 @@ refuse options = checksum list = no uid = 263 gid = 263 - hosts allow = 152.46.7.122 200.17.202.1/28 zeus1.kernel.org zeus2.kernel.org zeus3.kernel.org zeus4.kernel.org 149.20.20.132 204.152.191.36 199.6.1.170 130.239.17.3 sinclair.wpi.edu bonaparte.hrz.tu-chemnitz.de josephine.hrz.tu-che mirror.speedpartner.de rsyncer.ftp.heanet.ie archive.linux.duke.edu lists.us.dell.com auslistsprd01.us.dell.com auslistsdr01.us.dell.com 65.18.175.19 198.129.224.34 mirror.hiwaay.net sagres.c3sl.ufpr.br mail.fedoraunity.org scrye.com odysseus.fi.muni.cz rhlx01.hs-esslingen.de ftp.nrc.ca zaphod.gtlib.gatech.edu 128.171.104.148 + hosts allow = 152.46.7.122 200.17.202.1/28 zeus1.kernel.org zeus2.kernel.org zeus3.kernel.org zeus4.kernel.org 149.20.20.132 204.152.191.36 199.6.1.170 130.239.17.3 sinclair.wpi.edu bonaparte.hrz.tu-chemnitz.de josephine.hrz.tu-che mirror.speedpartner.de rsyncer.ftp.heanet.ie archive.linux.duke.edu lists.us.dell.com auslistsprd01.us.dell.com auslistsdr01.us.dell.com 65.18.175.19 198.129.224.34 mirror.hiwaay.net sagres.c3sl.ufpr.br mail.fedoraunity.org scrye.com odysseus.fi.muni.cz odysseus.linux.cz rhlx01.hs-esslingen.de ftp.nrc.ca zaphod.gtlib.gatech.edu 128.171.104.148 [fedora-epel0] comment = Fedora EPEL for Tier0|1 Mirrors @@ -71,7 +71,7 @@ refuse options = checksum list = no uid = 263 gid = 263 - hosts allow = 152.46.7.122 200.17.202.1/28 zeus1.kernel.org zeus2.kernel.org zeus3.kernel.org zeus4.kernel.org 149.20.20.132 204.152.191.36 199.6.1.170 130.239.17.3 sinclair.wpi.edu bonaparte.hrz.tu-chemnitz.de josephine.hrz.tu-chemnitz.de mirror.speedpartner.de rsyncer.ftp.heanet.ie archive.linux.duke.edu lists.us.dell.com auslistsprd01.us.dell.com auslistsdr01.us.dell.com 65.18.175.19 198.129.224.34 mirror.hiwaay.net sagres.c3sl.ufpr.br mail.fedoraunity.org scrye.com odysseus.fi.muni.cz rhlx01.hs-esslingen.de ftp.nrc.ca zaphod.gtlib.gatech.edu 128.171.104.148 + hosts allow = 152.46.7.122 200.17.202.1/28 zeus1.kernel.org zeus2.kernel.org zeus3.kernel.org zeus4.kernel.org 149.20.20.132 204.152.191.36 199.6.1.170 130.239.17.3 sinclair.wpi.edu bonaparte.hrz.tu-chemnitz.de josephine.hrz.tu-chemnitz.de mirror.speedpartner.de rsyncer.ftp.heanet.ie archive.linux.duke.edu lists.us.dell.com auslistsprd01.us.dell.com auslistsdr01.us.dell.com 65.18.175.19 198.129.224.34 mirror.hiwaay.net sagres.c3sl.ufpr.br mail.fedoraunity.org scrye.com odysseus.fi.muni.cz odysseus.linux.cz rhlx01.hs-esslingen.de ftp.nrc.ca zaphod.gtlib.gatech.edu 128.171.104.148 # For distributing applications [log] diff --git a/modules/rsync/files/rsyncd.conf.download-rdu b/modules/rsync/files/rsyncd.conf.download-rdu index 027b90e..171b22e 100644 --- a/modules/rsync/files/rsyncd.conf.download-rdu +++ b/modules/rsync/files/rsyncd.conf.download-rdu @@ -63,7 +63,7 @@ refuse options = checksum list = no uid = 263 gid = 263 - hosts allow = 152.46.7.122 200.17.202.1/28 zeus1.kernel.org zeus2.kernel.org zeus3.kernel.org zeus4.kernel.org 149.20.20.132 204.152.191.36 199.6.1.170 130.239.17.3 sinclair.wpi.edu bonaparte.hrz.tu-chemnitz.de josephine.hrz.tu-che mirror.speedpartner.de rsyncer.ftp.heanet.ie archive.linux.duke.edu lists.us.dell.com auslistsprd01.us.dell.com auslistsdr01.us.dell.com 65.18.175.19 198.129.224.34 mirror.hiwaay.net sagres.c3sl.ufpr.br mail.fedoraunity.org scrye.com odysseus.fi.muni.cz rhlx01.hs-esslingen.de ftp.nrc.ca zaphod.gtlib.gatech.edu 128.171.104.148 + hosts allow = 152.46.7.122 200.17.202.1/28 zeus1.kernel.org zeus2.kernel.org zeus3.kernel.org zeus4.kernel.org 149.20.20.132 204.152.191.36 199.6.1.170 130.239.17.3 sinclair.wpi.edu bonaparte.hrz.tu-chemnitz.de josephine.hrz.tu-che mirror.speedpartner.de rsyncer.ftp.heanet.ie archive.linux.duke.edu lists.us.dell.com auslistsprd01.us.dell.com auslistsdr01.us.dell.com 65.18.175.19 198.129.224.34 mirror.hiwaay.net sagres.c3sl.ufpr.br mail.fedoraunity.org scrye.com odysseus.fi.muni.cz odysseus.linux.cz rhlx01.hs-esslingen.de ftp.nrc.ca zaphod.gtlib.gatech.edu 128.171.104.148 [fedora-epel0] comment = Fedora EPEL for Tier0|1 Mirrors @@ -71,7 +71,7 @@ refuse options = checksum list = no uid = 263 gid = 263 - hosts allow = 152.46.7.122 200.17.202.1/28 zeus1.kernel.org zeus2.kernel.org zeus3.kernel.org zeus4.kernel.org 149.20.20.132 204.152.191.36 199.6.1.170 130.239.17.3 sinclair.wpi.edu bonaparte.hrz.tu-chemnitz.de josephine.hrz.tu-chemnitz.de mirror.speedpartner.de rsyncer.ftp.heanet.ie archive.linux.duke.edu lists.us.dell.com auslistsprd01.us.dell.com auslistsdr01.us.dell.com 65.18.175.19 198.129.224.34 mirror.hiwaay.net sagres.c3sl.ufpr.br mail.fedoraunity.org scrye.com odysseus.fi.muni.cz rhlx01.hs-esslingen.de ftp.nrc.ca zaphod.gtlib.gatech.edu 128.171.104.148 + hosts allow = 152.46.7.122 200.17.202.1/28 zeus1.kernel.org zeus2.kernel.org zeus3.kernel.org zeus4.kernel.org 149.20.20.132 204.152.191.36 199.6.1.170 130.239.17.3 sinclair.wpi.edu bonaparte.hrz.tu-chemnitz.de josephine.hrz.tu-chemnitz.de mirror.speedpartner.de rsyncer.ftp.heanet.ie archive.linux.duke.edu lists.us.dell.com auslistsprd01.us.dell.com auslistsdr01.us.dell.com 65.18.175.19 198.129.224.34 mirror.hiwaay.net sagres.c3sl.ufpr.br mail.fedoraunity.org scrye.com odysseus.fi.muni.cz odysseus.linux.cz rhlx01.hs-esslingen.de ftp.nrc.ca zaphod.gtlib.gatech.edu 128.171.104.148 # For distributing applications [log]

3 2

Moving Ask Fedora to Staging
by Rahul Sundaram 22 Aug '11

22 Aug '11

Hi We have been running Ask Fedora in the devel instance for a while now and updated several times as upstream fixed bugs and responded to feature requests http://ask01.dev.fedoraproject.org/questions/ We have a custom CSS file thanks to Suchakra and with the help of PJP (co-sysadmin, cc'ed), we have configured it to run with Apache. I haven't setup Postfix or memcached yet on the devel instance but atleast Postfix has been tested locally. We will have to think about whether we should be running our own instances or hook into the existing infrastructure. A SOP has been written as well https://fedoraproject.org/wiki/Ask_Fedora_SOP We will add more details we go forward. As a side note, while I was looking at memcached, ran into a alternative python binding (pylibmc) for memcached which apparently performs much faster and is being used by reddit. This has been packaged as well as the Django (django-pylibmc) module for that. Details at http://amix.dk/blog/post/19471 Let me know what I need to do to move Ask Fedora to Staging Rahul

4 9

Unplanned Proxy Outage: - 2011-08-19 16:30 UTC
by Toshio Kuratomi 22 Aug '11

22 Aug '11

Summary of Event ================ Tonight there was an unplanned outage of two proxy servers (proxy01 and proxy02). The proxies were unresponsive and needed to be rebooted in order to come back online. Proxy01 being down caused a cascade of other issues that should have had very little end-user impact. As far as we know, the applications on admin.fp.o would have been up but appeared very slow and the wiki would have been up for reading but logging in would have failed. Explanation to follow. Proxy01 is the only proxy server that is used for app servers (web apps, cronjobs, etc) in phx2 that need to talk to our web applications in phx2. This was setup because the router that handles traffic into and out of phx2 does not allow us to "hairpin", send a request for data from phx2 to an external ip address that then resolves back to a server in phx2. As currently implemented, we have an /etc/hosts entry that points admin.fedoraproject.org at the internal ip address of phx2. When proxy01 went down, things in PHX2 that needed to talk to admin.fedoraproject.org were no longer able to get the data they needed. For the wiki, this meant that attempting to login during the outage would be unable to verify the password in fas. For the TurboGears apps on admin.fedoraproject.org the situation was worse. TG1 apps' identity management depends on visit tracking to work. Visit tracking hits fas for every request. This means that no page could be served for the TG1 apps from the phx2 app servers. We have two app servers that reside outside of phx2. Because of network latency between these servers and the database server in phx2, these servers are configured to be backups for the servers in phx2, not handling requests unless phx2 is unable to. The remaining proxy servers detected that the app servers within phx2 were down and properly switched over to app servers outside of phx2 so there was no apparent outage for people trying to use admin.fedoraproject.org, although response time would have been drastically less. Looking at the haproxy status page for proxy03 during the outage we noticed that only one of the two app servers outside of phx2 (app05 at ibiblio) was handling traffic. app06 (at telia) was not. We are not sure why this is. One possibility is that telia's network latency is just too high so haproxy decided that app06 was also down and did not pass traffic to it. Action Items ============ There are some open questions to try to resolve: * Why did proxy01 and proxy02 die? A brief look at the logs has not revealed a cause for this. * Why didn't app06 take up any of the slack when haproxy started passing traffic to the backups? We have identified one means of mitigating this in the future: If we ran internal DNS for phx2 then we could have admin.fedoraproject.org resolve to different proxy servers (using internal ip addresses for the proxies inside of PHX2). This should remove the SPOF on proxy01. We have not yet determined whether we'd need to run more proxy servers inside of PHX2 or if hairpinning would not be an issue if we used proxy servers outside of phx2. -Toshio

2 1

[PATCH] modify all the TG apps (except for bodhi since its logging config is different) to not dump the world to stdout.
by Seth Vidal 19 Aug '11

19 Aug '11

From: Seth Vidal <skvidal(a)fedoraproject.org> --- modules/fas/files/fas-log.cfg | 2 +- modules/fas/templates/fas.cfg.erb | 2 +- .../fedora-packagedb/templates/pkgdb-prod.cfg.erb | 2 +- .../templates/mirrormanager-prod.cfg.erb | 2 +- modules/smolt/templates/prod.cfg.erb | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/modules/fas/files/fas-log.cfg b/modules/fas/files/fas-log.cfg index 3f7843d..a1ed30c 100644 --- a/modules/fas/files/fas-log.cfg +++ b/modules/fas/files/fas-log.cfg @@ -19,7 +19,7 @@ formatter='full_content' [[[access_out]]] class='StreamHandler' -level='INFO' +level='WARN' args='(sys.stdout,)' formatter='message_only' diff --git a/modules/fas/templates/fas.cfg.erb b/modules/fas/templates/fas.cfg.erb index 5908fc4..48ab522 100644 --- a/modules/fas/templates/fas.cfg.erb +++ b/modules/fas/templates/fas.cfg.erb @@ -206,7 +206,7 @@ handlers=['debug_out'] #propagate=0 [[[identity]]] -level='INFO' +level='WARN' qualname='turbogears.identity' handlers=['access_out'] propagate=0 diff --git a/modules/fedora-packagedb/templates/pkgdb-prod.cfg.erb b/modules/fedora-packagedb/templates/pkgdb-prod.cfg.erb index 4f28dce..ce4990a 100644 --- a/modules/fedora-packagedb/templates/pkgdb-prod.cfg.erb +++ b/modules/fedora-packagedb/templates/pkgdb-prod.cfg.erb @@ -133,7 +133,7 @@ formatter='full_content' [[[access_out]]] class='StreamHandler' -level='INFO' +level='WARN' args='(sys.stdout,)' formatter='message_only' diff --git a/modules/mirrormanager/templates/mirrormanager-prod.cfg.erb b/modules/mirrormanager/templates/mirrormanager-prod.cfg.erb index b4d18b9..39345fa 100644 --- a/modules/mirrormanager/templates/mirrormanager-prod.cfg.erb +++ b/modules/mirrormanager/templates/mirrormanager-prod.cfg.erb @@ -121,7 +121,7 @@ level='INFO' handlers=['debug_out'] [[[access]]] -level='INFO' +level='WARN' qualname='turbogears.access' handlers=['access_out'] propagate=0 diff --git a/modules/smolt/templates/prod.cfg.erb b/modules/smolt/templates/prod.cfg.erb index cc22b5a..0e10dbd 100644 --- a/modules/smolt/templates/prod.cfg.erb +++ b/modules/smolt/templates/prod.cfg.erb @@ -78,7 +78,7 @@ level='INFO' handlers=['debug_out'] [[[access]]] -level='INFO' +level='WARN' qualname='turbogears.access' handlers=['access_out'] propagate=0 -- 1.7.2.1

3 2

[PATCH] change access_out to WARN from INFO - testing to quiet down apache error_log
by Seth Vidal 19 Aug '11

19 Aug '11

From: Seth Vidal <skvidal(a)fedoraproject.org> --- modules/elections/templates/elections-prod.cfg.erb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/modules/elections/templates/elections-prod.cfg.erb b/modules/elections/templates/elections-prod.cfg.erb index e0f4ab9..6f92258 100644 --- a/modules/elections/templates/elections-prod.cfg.erb +++ b/modules/elections/templates/elections-prod.cfg.erb @@ -80,7 +80,7 @@ level='INFO' handlers=['debug_out'] [[[access]]] -level='INFO' +level='WARN' qualname='turbogears.access' handlers=['access_out'] propagate=0 -- 1.7.2.1

3 2

Meeting Agenda Item: Introduction Mahrud
by Mahrud S 19 Aug '11

19 Aug '11

Hi I'm Mahrud. irc username: mahrud. *Skills: * I've learned working with these things while working on different projects or digging my linux laptop: LinuxPAM, SELinux, chroot, squid, LDAP, git, Wireless Cryptography & OpenSSL, Linux network/security administration, monitoring and troubleshooting, embedded linux (OpenWRT on a WRT54GL), etc. programming: native c/cpp and adv. bash, familiar with ruby, python, php, javascript, a bit assembly, understand perl, hate Visual Studio and specially VB. Algorithmic programing and data structure (intended school classes). *Projects:* HelliJudge <http://hellicode.allamehelli.ir/git/> (an online judge system; details<http://users.allamehelli.ir/%7Em_sayrafi/blog/2011/08/project-hellijudge/>), OpenSchoolNetwork (a local system for Allamehelli HS (my previous high school), it's goal is to find and train future admin of server<http://allamehelli.ir/>of Allamehelli from students by giving them a jailed ssh account on server. It uses a central authentication system using LDAP for squid on the same server and sshd on another server using the same ldap server) *Hobbies: * Digging Linux! hack (but not crack)! Remote administrating Allamehelli's network and server. *Weaknesses:* If there isn't any problem to solve, then I'll be so lazy and waste my time on google reader! Back in Iran I were working on Allamehelli's server, but now in US due to loss of physical access I'm unable to work with that server (because in case of problem in ssh or auth, I'll have to wait about a day for my friends to take is up again), and that's why I want to join you in administrating the fedora infrastructure. Still in high school (12th grade). Hope you are not bored :) I'm interested in working on this<https://fedorahosted.org/fedora-infrastructure/ticket/230>or this <https://fedorahosted.org/fedora-infrastructure/ticket/833>, but I'll be glad to work on anything related to Linux (even if there is a requirement, I'll learn it through the project, just like all of the above) **-- Best wishes Mahrud <http://users.allamehelli.ir/%7Em_sayrafi/>

2 1

Plan for tomorrow's Fedora Infrastructure meeting (2011-08-18 at 19UTC)
by Kevin Fenzi 18 Aug '11

18 Aug '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-08-18 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * F16 Alpha Freeze reminder and tickets. * Fedora hosted plans * Upcoming Tasks/Items (nirik) 2011-08-02 - 23: Alpha change freeze 2011-08-05 figure replacements for xen 03/05/09/15 (EOL 09-25 ish) 2011-08-17 send infra meeting agenda 2011-08-18 infra meeting 2011-08-23: Fedora 16 alpha 2011-09-01 mail fi-apprentice folks. 2011-09-13 - 27: Beta change freeze 2011-09-09 Remove inactive fi-apprentice people. 2011-09-27: Fedora 16 Beta * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 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

Activity
by Jesse N. Richardson 18 Aug '11

18 Aug '11

I've finally gotten my computer fixed everyone. Can someone please add me back to the team? Sent from my iPod On Aug 14, 2011, at 8:00 AM, infrastructure-request(a)lists.fedoraproject.org wrote: > Send infrastructure mailing list submissions to > infrastructure(a)lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.fedoraproject.org/mailman/listinfo/infrastructure > or, via email, send a message with subject or body 'help' to > infrastructure-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > infrastructure-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of infrastructure digest..." > > > Today's Topics: > > 1. Re: infrastructure Digest, Vol 63, Issue 17 (F?bio Falc?o) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 13 Aug 2011 23:06:33 +0100 > From: F?bio Falc?o <fawcao(a)gmail.com> > Subject: Re: infrastructure Digest, Vol 63, Issue 17 > To: infrastructure(a)lists.fedoraproject.org > Message-ID: > <CAM4+sV0MPs77tWq_fcKsj6Dsjv5d+e9LZszHPhee0=qAHrHR4Q(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, i'm new here too. > > i working with systems development today, but always worked with > infrastructure, specifically in clusters and grids. Currently I master's > degree in computer engineering in Coimbra and my area of ??research is in > the area of ??secure protocols. > > 2011/8/13 <infrastructure-request(a)lists.fedoraproject.org> > >> Send infrastructure mailing list submissions to >> infrastructure(a)lists.fedoraproject.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://admin.fedoraproject.org/mailman/listinfo/infrastructure >> or, via email, send a message with subject or body 'help' to >> infrastructure-request(a)lists.fedoraproject.org >> >> You can reach the person managing the list at >> infrastructure-owner(a)lists.fedoraproject.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of infrastructure digest..." >> >> >> Today's Topics: >> >> 1. joining with the Fedora Infra team - Hello (Buddhika Kurera) >> 2. Re: joining with the Fedora Infra team - Hello >> (Stephen John Smoogen) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sat, 13 Aug 2011 07:28:25 +0530 >> From: Buddhika Kurera <bckurera(a)fedoraproject.org> >> Subject: joining with the Fedora Infra team - Hello >> To: Infrastructure Ffedora Project >> <infrastructure(a)lists.fedoraproject.org> >> Message-ID: >> <CAMkiuStsQxX4790swwTajS6vwGX5jMC9oa3jKg4PNKrsmvwpSQ(a)mail.gmail.com >>> >> Content-Type: text/plain; charset="utf-8" >> >> Hello Infra team, >> >> I am Buddhika Kurera[1] and working with Fedora Ambassadors and Design >> teams >> plus free media teams currently. >> >> I am interested in joining with the infrastructure team too. Therefore I ll >> be keep in touch though the ML. >> Further as I am new to this team please help me to understand the workings >> with the teams. >> >> If any tickets, requests please share, I can give my helping hand. >> >> I am a good at PHP development and web related technologies. That is my >> tech >> background. See you soon. >> >> [1] fedoraproject.org/wiki/User:bckurera >> >> -- >> Regards, >> *Buddhike Chandradeepa Kurera* >> Fedora Ambassador Sri Lanka >> Event Liaison - Design Team >>

4 4

Questions before requesting new mailing list
by James Laska 17 Aug '11

17 Aug '11

Greetings, I'm about to submit a ticket requesting a new mailing list on lists.fedoraproject.org. Before submitting, I'd like to ask a few questions. The new list is really an existing list that will be migrating to lists.fedoraproject.org. Because of this, the list has existing members, and archives. What is the procedure for migrating the existing subscriber list? I gather that's something I'd setup after the list is created, but thought I'd ask here first. Also, is it at all possible to migrate the existing list archives to the new lists.fedoraproject.org location? I suspect this would be fairly painful, but again, can't hurt to ask. :) Thanks, James

3 4

[PATCH 1/2] since we're running all of fasClients from cron now - comment out this run of fasClients from puppet.
by Seth Vidal 15 Aug '11

15 Aug '11

From: Seth Vidal <skvidal(a)fedoraproject.org> I think but am not positive that it is causing this log error: restorecond: set context /var/db/shadow.db->system_u:object_r:shadow_t:s0 failed:'Permission denied' due to fasClient running from cron at the same time as from puppet. --- modules/fas/manifests/init.pp | 9 --------- 1 files changed, 0 insertions(+), 9 deletions(-) diff --git a/modules/fas/manifests/init.pp b/modules/fas/manifests/init.pp index f1eb7ac..64676bb 100644 --- a/modules/fas/manifests/init.pp +++ b/modules/fas/manifests/init.pp @@ -66,15 +66,6 @@ class fas::client { type => "user_home_dir_t", } - exec { "make-accounts": - command => "/usr/bin/fasClient -e; /usr/bin/fasClient -i", - timeout => 90, - creates => "/var/db/shadow.db", - require => [ - File["/etc/fas.conf"], - Package["fas-clients"], - ], - } } # May want to merge this into fas::client in the future if we want yubikey -- 1.7.2.1

3 4

Re: infrastructure Digest, Vol 63, Issue 17
by Fábio Falcão 15 Aug '11

15 Aug '11

Hi, i'm new here too. i working with systems development today, but always worked with infrastructure, specifically in clusters and grids. Currently I master's degree in computer engineering in Coimbra and my area of research is in the area of secure protocols. 2011/8/13 <infrastructure-request(a)lists.fedoraproject.org> > Send infrastructure mailing list submissions to > infrastructure(a)lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.fedoraproject.org/mailman/listinfo/infrastructure > or, via email, send a message with subject or body 'help' to > infrastructure-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > infrastructure-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of infrastructure digest..." > > > Today's Topics: > > 1. joining with the Fedora Infra team - Hello (Buddhika Kurera) > 2. Re: joining with the Fedora Infra team - Hello > (Stephen John Smoogen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 13 Aug 2011 07:28:25 +0530 > From: Buddhika Kurera <bckurera(a)fedoraproject.org> > Subject: joining with the Fedora Infra team - Hello > To: Infrastructure Ffedora Project > <infrastructure(a)lists.fedoraproject.org> > Message-ID: > <CAMkiuStsQxX4790swwTajS6vwGX5jMC9oa3jKg4PNKrsmvwpSQ(a)mail.gmail.com > > > Content-Type: text/plain; charset="utf-8" > > Hello Infra team, > > I am Buddhika Kurera[1] and working with Fedora Ambassadors and Design > teams > plus free media teams currently. > > I am interested in joining with the infrastructure team too. Therefore I ll > be keep in touch though the ML. > Further as I am new to this team please help me to understand the workings > with the teams. > > If any tickets, requests please share, I can give my helping hand. > > I am a good at PHP development and web related technologies. That is my > tech > background. See you soon. > > [1] fedoraproject.org/wiki/User:bckurera > > -- > Regards, > *Buddhike Chandradeepa Kurera* > Fedora Ambassador Sri Lanka > Event Liaison - Design Team > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.fedoraproject.org/pipermail/infrastructure/attachments/2011081… > > ------------------------------ > > Message: 2 > Date: Fri, 12 Aug 2011 20:05:35 -0600 > From: Stephen John Smoogen <smooge(a)gmail.com> > Subject: Re: joining with the Fedora Infra team - Hello > To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org> > Message-ID: > <CANnLRdjoLvWZ=H9gm3GsPqcwQxvMXjcdJrKrwd1jswGGGhPZZA(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > On Fri, Aug 12, 2011 at 19:58, Buddhika Kurera > <bckurera(a)fedoraproject.org> wrote: > > Hello?Infra?team, > > I am Buddhika Kurera[1] and working with Fedora Ambassadors and Design > teams > > plus free media teams currently. > > I am interested in joining with the infrastructure team too. Therefore I > ll > > be keep in touch though the ML. > > Further as I am new to this team please help me to understand the > workings > > with the teams. > > > > If any tickets, requests please share, I can give my helping hand. > > I am a good at PHP development and web related?technologies.?That?is my > tech > > background. See you soon. > > Hi and thank you for your introduction. What are your normal hours on > GMT time? We can try and meet up on IRC sometime soon > > > > > > -- > Stephen J Smoogen. > "The core skill of innovators is error recovery, not failure avoidance." > Randy Nelson, President of Pixar University. > "Let us be kind, one to another, for most of us are fighting a hard > battle." -- Ian MacLaren > > > ------------------------------ > > _______________________________________________ > infrastructure mailing list > infrastructure(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/infrastructure > > End of infrastructure Digest, Vol 63, Issue 17 > ********************************************** > -- Atenciosamente, Fábio Falcão de França Bacharel em Ciências da Computação Especialista em Segurança da Informação Mestrando em Engenharia Informática - Universidade de Coimbra

2 1

[PATCH] since we're running all of fasClients from cron now - comment out this run of fasClients from puppet.
by Seth Vidal 15 Aug '11

15 Aug '11

From: Seth Vidal <skvidal(a)fedoraproject.org> I think but am not positive that it is causing this log error: restorecond: set context /var/db/shadow.db->system_u:object_r:shadow_t:s0 failed:'Permission denied' due to fasClient running from cron at the same time as from puppet. --- modules/fas/manifests/init.pp | 9 --------- 1 files changed, 0 insertions(+), 9 deletions(-) diff --git a/modules/fas/manifests/init.pp b/modules/fas/manifests/init.pp index f1eb7ac..64676bb 100644 --- a/modules/fas/manifests/init.pp +++ b/modules/fas/manifests/init.pp @@ -66,15 +66,6 @@ class fas::client { type => "user_home_dir_t", } - exec { "make-accounts": - command => "/usr/bin/fasClient -e; /usr/bin/fasClient -i", - timeout => 90, - creates => "/var/db/shadow.db", - require => [ - File["/etc/fas.conf"], - Package["fas-clients"], - ], - } } # May want to merge this into fas::client in the future if we want yubikey -- 1.7.2.1

1 1

joining with the Fedora Infra team - Hello
by Buddhike Kurera 13 Aug '11

13 Aug '11

Hello Infra team, I am Buddhika Kurera[1] and working with Fedora Ambassadors and Design teams plus free media teams currently. I am interested in joining with the infrastructure team too. Therefore I ll be keep in touch though the ML. Further as I am new to this team please help me to understand the workings with the teams. If any tickets, requests please share, I can give my helping hand. I am a good at PHP development and web related technologies. That is my tech background. See you soon. [1] fedoraproject.org/wiki/User:bckurera -- Regards, *Buddhike Chandradeepa Kurera* Fedora Ambassador Sri Lanka Event Liaison - Design Team

2 1

Freeze break: add range to dhcp01
by Kevin Fenzi 12 Aug '11

12 Aug '11

I'd like to enable a dhcp range on dhcp01. This would allow me to get to the management interface on a new server we added in that network, which will become bvirthost04. I would like to get this sooner rather than later so we can setup a releng03 on it to compose branched on. This will help us get branched out sooner. dhcp01 does provide dhcp to builders and various things on the build network, so we do need to be careful. kevin -- diff --git a/modules/dhcp/files/dhcpd.conf.dhcp01 b/modules/dhcp/files/dhcpd.conf.dhcp01 index 302260b..6a179fa 100644 --- a/modules/dhcp/files/dhcpd.conf.dhcp01 +++ b/modules/dhcp/files/dhcpd.conf.dhcp01 @@ -269,7 +269,8 @@ group macs { } -# range 10.5.125.170 10.5.125.189; -# next-server 10.5.125.43; -# filename "pxelinux.0"; +range 10.5.125.170 10.5.125.189; +next-server 10.5.125.43; +filename "pxelinux.0"; + }

4 8

Plan for tomorrow's Fedora Infrastructure meeting (2011-08-11 at 19UTC)
by Kevin Fenzi 11 Aug '11

11 Aug '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-08-11 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * F16 Alpha Freeze reminder and tickets. * Upcoming Tasks/Items (nirik) 2011-08-02 - 16: Alpha change freeze 2011-08-16: Fedora 16 alpha 2011-09-06 - 20: Beta change freeze 2011-09-20: Fedora 16 Beta 2011-10-11 - 25: Final change freeze 2011-10-25: Fedora 16 release. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 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

python-fedora package split
by Toshio Kuratomi 10 Aug '11

10 Aug '11

This is a heads up for people packaging or using applications that depend on python-fedora. Currently, python-fedora is one package that contains code useful for both building clients that talk to Fedora Infrastructure Services and servers that run on Fedora Infrastructure (mainly CSRF protection and an auth provider to talk to the Fedora Account System). The package has Require: deps to make the client code run but not everything to make the server run as that would drag packages that are only needed on servers onto the clients. I've been requested to fix this so I'll be splitting the python-fedora package into three subpackages: python-fedora: will continue to provide the client code. It will continue to have the same deps as the current package. python-fedora-turbogears: will provide the helpers for integrating with TurboGears1 and TurboGears2 applications. This package will dep on the TurboGears and TurboGears2 packages in addition to the base package. python-fedora-django: will provide the integration with django servers. It will dep on Django in addition to the python-fedora base package. For packagers, developers, and sysadmins needing python-fedora client code, this should mean you need to make no changes. yum install python-fedora or Requires: python-fedora will continue to get you python-fedora and the minimal deps needed for the client code to function. For packagers, developers, and sysadmins working with server apps that need python-fedora's server helper code, you'll need to update to pulling in the subpackage relevant to your framework (for instance, bodhi should change to use Requires: python-fedora-turbogears ). The lack of complete deps was noted on an F14 box... since this is a somewhat disruptive change (hopefully only for the relatively small number of people working with server code) I was debating how far back to push it. Since it needs to go into EPEL5 and EPEL6 as well as Fedora I've decided that I'll push it out to F15+ as a compromise between keeping things stable and fixing the issue everywhere. Thank you, -Toshio

2 2

ticket#2673 - nitrate deployment
by James Laska 10 Aug '11

10 Aug '11

Greetings, I am in search of sponsorship for hosting space to deploy a test instance of nitrate [1]. Some of you may recall several years back when we deployed an instance of Testopia. That exploration was cut short when we discovered license incompatibilities between testopia and Fedora. At that time, a small group of Red Hat associates began creating a new Django-based test management system to remove the components that had conflicting licenses. That new system became nitrate [1]. The Fedora QA team would like to experiment/explore this newer Django-based test management system. At the very least, I believe we'll need a publicly accessible server where we can host the nitrate instance and a mysql database for it. I filed ticket#2673 (https://fedorahosted.org/fedora-infrastructure/ticket/2673) to track this request. Please don't hesitate with any questions/comments/concerns. Thanks, James [1] https://fedorahosted.org/nitrate/

3 7

Membership
by Jesse N. Richardson 09 Aug '11

09 Aug '11

I haven't been help with the project lately due to my computer being broken. I am still active. Sent from my iPod On Aug 9, 2011, at 8:00 AM, infrastructure-request(a)lists.fedoraproject.org wrote: > Send infrastructure mailing list submissions to > infrastructure(a)lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.fedoraproject.org/mailman/listinfo/infrastructure > or, via email, send a message with subject or body 'help' to > infrastructure-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > infrastructure-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of infrastructure digest..." > > > Today's Topics: > > 1. Re: Request for Freeze Override: wildcard.fedoraproject.org > (Ricky Elrod) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 09 Aug 2011 01:24:12 -0400 > From: Ricky Elrod <codeblock(a)elrod.me> > Subject: Re: Request for Freeze Override: wildcard.fedoraproject.org > To: infrastructure(a)lists.fedoraproject.org > Message-ID: <4E40C47C.1040706@fedoraprojectorg> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > +1, it's got to be done at some point. :) > > On 08/09/2011 12:21 AM, seth vidal wrote: >> On Mon, 2011-08-08 at 19:35 -0600, Stephen John Smoogen wrote: >>> The wildcard certificates are about to run out. I have new ones from >>> the certificate authority and can put them into place pretty quickly. >>> The changes would be: >>> >>> copy old ones for safekeeping. >>> copy new ones over oldones >>> git commit -a >>> git push -a >>> func-command --host="proxy*" "/usr/local/bin/run-puppet nowait" >>> wait for it >>> test >>> >>> if for some reason they do not work, I can revert the git commit and >>> push out the certificates again. >>> >>> >>> >> >> +1 >> -sv >> >> >> _______________________________________________ >> infrastructure mailing list >> infrastructure(a)lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/infrastructure > > > ------------------------------ > > _______________________________________________ > infrastructure mailing list > infrastructure(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/infrastructure > > End of infrastructure Digest, Vol 63, Issue 11 > **********************************************

2 1

Request for Freeze Override: wildcard.fedoraproject.org
by Stephen John Smoogen 09 Aug '11

09 Aug '11

The wildcard certificates are about to run out. I have new ones from the certificate authority and can put them into place pretty quickly. The changes would be: copy old ones for safekeeping. copy new ones over oldones git commit -a git push -a func-command --host="proxy*" "/usr/local/bin/run-puppet nowait" wait for it test if for some reason they do not work, I can revert the git commit and push out the certificates again. -- Stephen J Smoogen. "The core skill of innovators is error recovery, not failure avoidance." Randy Nelson, President of Pixar University. "Let us be kind, one to another, for most of us are fighting a hard battle." -- Ian MacLaren

4 3

Meeting Agenda Item: Introduction Kamal Ejaz
by kamal ejaz 08 Aug '11

08 Aug '11

* My IRC nick is agentvictor * I am a software engineer( php, ruby on rails ). have basic knowledge of python. * I am new to linux development community. I want to be os developer. For my start i would like to help on ticket #2686 gracefully handle FAS outages in our TurboGears apps.sorry for poor english.

3 2

AUTO: Shannon Mcleod is out of the office (returning 08/15/2011)
by Shannon Mcleod 06 Aug '11

06 Aug '11

I am out of the office until 08/15/2011. I will be on vacation starting on Friday and returning on August 15. Thanks, Shannon McLeod Unix System Administrator Dubuque GDF Note: This is an automated response to your message "infrastructure Digest, Vol 63, Issue 6" sent on 8/6/11 6:00:21. This is the only notification you will receive while this person is away.

1 0

Mediawiki on RHEL6 help needed
by Toshio Kuratomi 05 Aug '11

05 Aug '11

Greetings all, Infrastructure is in the process of getting all of our machines switched from RHEL5 to RHEL6. Right now we're looking at one of the more publically visible services that we host -- mediawiki for fedoraproject.org/wiki. Mediawiki installs and runs for us but it is too slow. So slow, in fact, that our proxy server decides that the instance is down and takes it out of rotation. If someone has some mediawiki configuration or mediawiki/php programming experience and would like to take a look, we'd be happy to get you permissions to poke around our RHEL6 app server test instance and try out fixes. You can contact nirik (Kevin Fenzi) or me (abadger1999) on irc.freenode.net #fedora-admin to help get you started. You can also take a look at the ticket for any details I've left out here: https://fedorahosted.org/fedora-infrastructure/ticket/2908 Thanks, -Toshio

3 3

Plan for tomorrow's Fedora Infrastructure meeting (2011-08-04 at 19UTC)
by Kevin Fenzi 04 Aug '11

04 Aug '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-08-04 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * F16 Alpha Freeze reminder and tickets. * Upcoming Tasks/Items (nirik) 2011-08-02 - 16: Alpha change freeze 2011-08-16: Fedora 16 alpha 2011-09-06 - 20: Beta change freeze 2011-09-20: Fedora 16 Beta 2011-10-11 - 25: Final change freeze 2011-10-25: Fedora 16 release. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 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

infra docs
by Seth Vidal 04 Aug '11

04 Aug '11

Following up on the action item for the infra-docs/SOP migration from the wiki to git I was wondering what opinions folks had on these two markup mechanisms: markdown Restructured Text Suggestions include: 1. having each page be plain text and have the following format: Title: blah Summary: blah blah blah Body goes here Then having a commit hook for the git repo generate a simple index of the above for browsing on a web site. 2. Just put the txt files in a dir and let you browse based on filename and be done with it. - since a lot of us are going to just use git grep ANYWAY, just roll with it. I'm inclined toward simple and add complexity as we go. -sv

3 6

Unplanned outage 2011-08-03 in phx2
by Kevin Fenzi 03 Aug '11

03 Aug '11

Just FYI, there was an unplanned outage in phx2 today. There was some cabling work being done and a switch in one of our racks didn't properly failover to it's second power supply when power was moved from it's primary. This resulted in a approx 10min outage to servers in that rack. Additionally, one machine had a network cable that wasn't reseated properly, so it couldn't reach anything after the switch came back. Investigation of how to fix the switch is ongoing. kevin

1 0

Freeze change request: lower rdu I2 download limits
by Kevin Fenzi 02 Aug '11

02 Aug '11

The old I2 mirror machines (2 of them) handled 50 syncs at a time. We have 3 machines, but they are set currently to 25/ea, meaning a total of 75 could be hitting the backend storage. I'd like to lower this down to 15/ea and see if it helps with the slowdown/issues as seen in https://fedorahosted.org/fedora-infrastructure/ticket/2874 kevin -- diff --git a/modules/rsync/files/rsyncd.conf.download-rdu b/modules/rsync/files/rsyncd.conf.download-rdu index de816a0..027b90e 100644 --- a/modules/rsync/files/rsyncd.conf.download-rdu +++ b/modules/rsync/files/rsyncd.conf.download-rdu @@ -1,7 +1,7 @@ #download-rdu pid file = /var/run/rsyncd.pid syslog facility = daemon -max connections = 25 +max connections = 15 timeout = 600 use chroot = yes uid = nobody

5 4

[PATCH] set parent_repos in bodhi mash configs
by Bill Nottingham 02 Aug '11

02 Aug '11

commit 3e946b135a14243b89575b66f43ddea60e5e13bd Author: Bill Nottingham <notting(a)lockbox01.phx2.fedoraproject.org> Date: Tue Aug 2 14:36:54 2011 +0000 Add parent_repos definitions to bodhi mash configs. (#727515, #727138) diff --git a/modules/bodhi/files/f15-updates-testing.mash b/modules/bodhi/files/f15-updates-testing.mash index 27836a6..d464b96 100644 --- a/modules/bodhi/files/f15-updates-testing.mash +++ b/modules/bodhi/files/f15-updates-testing.mash @@ -17,4 +17,4 @@ delta = True # Enable this once F15 releases #delta_dirs = /pub/fedora/linux/releases/15/Everything/%(arch)s/os/,/mnt/koji/mash/updates/f15-updates/%(arch)s/ delta_dirs = /pub/fedora/linux/development/15/%(arch)s/os/ - +parent_repos = http://download.fedoraproject.org/pub/fedora/linux/updates/15/%(arch)s, http://download.fedoraproject.org/pub/fedora/linux/releases/15/Everything/%… diff --git a/modules/bodhi/files/f15-updates.mash b/modules/bodhi/files/f15-updates.mash index 18c88b7..94384ba 100644 --- a/modules/bodhi/files/f15-updates.mash +++ b/modules/bodhi/files/f15-updates.mash @@ -13,3 +13,4 @@ repoviewtitle = "Fedora 15 Updates - %(arch)s" arches = i386 x86_64 delta = True delta_dirs = /pub/fedora/linux/releases/15/Everything/%(arch)s/os/,/mnt/koji/mash/updates/f15-updates/%(arch)s/ +parent_repos = http://download.fedoraproject.org/pub/fedora/linux/releases/15/Everything/%… diff --git a/modules/bodhi/files/f16-updates-testing.mash b/modules/bodhi/files/f16-updates-testing.mash index 2fbcb64..fa530ab 100644 --- a/modules/bodhi/files/f16-updates-testing.mash +++ b/modules/bodhi/files/f16-updates-testing.mash @@ -14,7 +14,9 @@ repoviewurl = http://download.fedoraproject.org/pub/fedora/linux/updates/testing repoviewtitle = "Fedora 16 Updates Testing - %(arch)s" arches = i386 x86_64 delta = True -# Enable this once F15 releases -#delta_dirs = /pub/fedora/linux/releases/15/Everything/%(arch)s/os/,/mnt/koji/mash/updates/f15-updates/%(arch)s/ +# Enable this once F16 releases +#delta_dirs = /pub/fedora/linux/releases/16/Everything/%(arch)s/os/,/mnt/koji/mash/updates/f16-updates/%(arch)s/ delta_dirs = /pub/fedora/linux/development/16/%(arch)s/os/ - +# Enable this once F16 releases +#parent_repos = http://download.fedoraproject.org/pub/fedora/linux/updates/16/%(arch)s, http://download.fedoraproject.org/pub/fedora/linux/releases/16/Everything/%… +parent_repos = http://download.fedoraproject.org/pub/fedora/linux/updates/16/%(arch)s, http://download.fedoraproject.org/pub/fedora/linux/development/16/%(arch)s/… diff --git a/modules/bodhi/files/f16-updates.mash b/modules/bodhi/files/f16-updates.mash index 91d6a9b..bd560b9 100644 --- a/modules/bodhi/files/f16-updates.mash +++ b/modules/bodhi/files/f16-updates.mash @@ -13,3 +13,5 @@ repoviewtitle = "Fedora 16 Updates - %(arch)s" arches = i386 x86_64 delta = True delta_dirs = /pub/fedora/linux/releases/16/Everything/%(arch)s/os/,/mnt/koji/mash/updates/f16-updates/%(arch)s/ +# Fix at GA +#parent_repos = http://download.fedoraproject.org/pub/fedora/linux/releases/16/Everything/%…

3 3

F16 ALPHA FREEZE reminder
by Kevin Fenzi 02 Aug '11

02 Aug '11

Just a reminder that we are now in the f16 alpha freeze. 2011-08-02 - 16: Alpha change freeze 2011-08-16: Fedora 16 alpha http://fedoraproject.org/wiki/Release_Infrastructure_SOP Please send any changes to frozen hosts to the list for acks. Thanks, kevin

1 0

Calendaring. Again.
by Adam Williamson 01 Aug '11

01 Aug '11

Hey, folks. Just wanted to take another shot at one of my oldest windmills :) So, we talked about calendaring for a long time. Then we picked Zarafa. Then we kind of implemented it. Then no-one used it, and we took it out again: http://smoogespace.blogspot.com/2011/02/resetting-expectations-fedora.html That wasn't what you might call a 'success', I know. I think there's maybe a couple of reasons for that. One, I'm still not really sure why we'd pick Zarafa. It's explicitly designed to be a Microsoft Exchange replacement, and I don't think Fedora is a project with a lot of people who really need to use ActiveSync or Outlook, so...huh? It just doesn't seem like it was ever a great fit. By the Zarafa page on the wiki - https://fedoraproject.org/wiki/Zarafa - we couldn't even ship Z-Push because ActiveSync is patented, so apparently our only ever official calendaring system never had a working sync mechanism at all, and I don't think Zarafa's web interface is any great shakes. Two, there was never any particular driver towards using it. So, I think another try with a more appropriate calendaring system - if we can find one - and a 'seed' use of it might be a good idea. I've been using eGroupware, personally, for quite a while, and I think it's a good system. I'm not aware of any major barriers to including it in Fedora. It has internal copies of a few Pear modules, but that's pretty small beer and it should be trivial to use the system-wide copies or get an exception (some of them are extensively modified). It has a nice web UI and decent sync capabilities via CalDAV: I've used it synchronized with Evolution on two systems and never had major problems. It seems at least a better fit than Zarafa. Citadel would be another one to look at. As for a 'seed' use, I think an ideal fit here would be the release schedules. Currently, these are dumb HTML tables with ICS files living in the current release manager's personal fedoraproject space: http://rbergero.fedorapeople.org/schedules/f-16/ which sucks for any number of reasons, not least of which you need to know who the hell the release manager is at the moment in order to find the schedule. =) Using a proper calendaring system would seem to be a far better way to handle the release calendars, and would be a great kickstarter for a project calendaring system. Since the calendars are maintained by one person, we only need to get one person (hi, Robyn!) to buy in, in order to kick off this seed use. To restrict the liability issues mentioned in Smooge's blog post, we could not enable the email function of the system we choose (this is possible with both EGW and Citadel). We could also not have individual accounts for all Fedora project members, at least at first: we could have just a few individual accounts with commit access, mainly for the release manager to maintain the calendars, and then have a single read-only guest account which people could use to view the calendars and sync them read-only to their phones and desktop clients. It may even be possible to set things up so people can view and read-only sync without any authentication required. What do people think of this idea? If it seems like an approach that's simpler to maintain and more likely to produce actual useful results, that'd be great. I'm willing to work on packaging eGroupware and resolving the private-copies-of-pear-modules issue - I already maintain eGW for Mandriva, so it wouldn't be too much work to convert the spec to Fedora standards. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

5 10

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2011