September 2008 - infrastructure - Fedora mailing-lists

Strange build error for classpathx-mail
by Orion Poplawski 24 Oct '08

24 Oct '08

Starting looking into updating classpathx-mail to version 1.1.2 (anyone know of a reason not to?). Got a really weird internal compiler error on the ppc64 build: [javac] 1. ERROR in /builddir/build/BUILD/mail-1.1.2/inetlib-1.1.1/source/org/jpackage/mail/inet/imap/IMAPConnection.java (at line 0) [javac] /* [javac] ^ [javac] Internal compiler error [javac] java.lang.NullPointerException [javac] at org.eclipse.jdt.internal.compiler.looku [javac] p.BinaryTypeBinding.cachePartsFrom(BinaryTypeBinding.java:262) [javac] at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:719) [javac] at org.eclipse.jdt.i [javac] nternal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:699) [javac] at org.eclipse.jdt.internal.compiler.Compiler.accept(Compiler.java:294) [javac] at org.eclipse.jdt.internal.com [javac] piler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:128) [javac] at org.eclipse.jdt.internal.compiler.lookup.PackageBinding.getTypeOrPackage(PackageBinding.java:179) [javac] at org.eclipse.jdt.inte [javac] rnal.compiler.lookup.CompilationUnitScope.findImport(CompilationUnitScope.java:456) [javac] at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.findSingleImport(CompilationUnitScope.java:510) [javac] at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.faultInImports(CompilationUnitScope.java:359) [javac] at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.faultInTypes(Compi [javac] lationUnitScope.java:435) [javac] at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:736) [javac] at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:137) [javac] at java.lang.Thread.run(libgcj.so.9) Other arches seemed okay but got cancelled. See: http://koji.fedoraproject.org/koji/taskinfo?taskID=809142 This was on ppc7. Resubmitted and it built okay (or at least got past this point). This time on ppc2 http://koji.fedoraproject.org/koji/taskinfo?taskID=809169 Fully successful build (if anyone wants to take a look at the package): http://koji.fedoraproject.org/koji/taskinfo?taskID=809200 -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion(a)cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com

2 3

Puppet training
by Mike McGrath 03 Oct '08

03 Oct '08

Hey guys, i think I'd like to hold puppet training next week on Wed sometime. Which would work best for you guys: 1:00 pm Chicago time 4:00 pm Chicago time. The live training will be identical to this training: http://mmcgrath.fedorapeople.org/puppet/ But will allow for Q and A. The training at that links includes an ogg and takes about a half hour to complete at full speed though if you're new to puppet its worth it to stop in the middle and review some of the topics. If you have any questions or comments about it please let me know. The slideshow is made with openoffice and I made the ogg with audacity. My throat hurts now so I'm going to get some tea :) -Mike

12 20

F10 Beta release
by Paul W. Frields 30 Sep '08

30 Sep '08

Great job with the release this morning, guys. I know there were some gremlins in a torrent or two, but overall very painless and you guys made it look easy (as always). Hurrah, another milestone on the path to Cambridge! If anyone has any issues, we could plant them on a page for the next release day planning group call. -- 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/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

4 3

Beta freeze lift
by Jesse Keating 30 Sep '08

30 Sep '08

Since beta went out this morning, I'm +1 to lift the change freeze. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating

1 0

[MAILER-DAEMON@redhat.com: Returned mail: see transcript for details]
by Roland McGrath 30 Sep '08

30 Sep '08

I had this bounce to my (new) fedorahosted.org mailing list. A few minutes later, I sent a test message and it got through fine. Then I sent this same message again, and it got through fine. I hope there isn't regularly some little window in which lists.fedorahosted.org's mailing lists are unknown to its MTA. Thanks, Roland

1 0

Re: a Beta announcement to use
by Paul W. Frields 30 Sep '08

30 Sep '08

On Mon, Sep 29, 2008 at 03:41:42PM -0700, Jesse Keating wrote: > On Mon, 2008-09-29 at 15:16 -0700, Karsten 'quaid' Wade wrote: > > In light of trying to pump up the marketing and the bug reporting, here > > is a Beta release announcement: > > This looks good to me. Are the links within validated with > Infrastructure to handle the load, and valid content? In answering that question, I believe there is an Infrastructure SOP for release that has the links automatically load balanced and expected by our intrepid sysadmins. -- 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/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

1 0

Re: fas/auth.py fas/json_request.py
by Yaakov Nemoy 29 Sep '08

29 Sep '08

I actually like this code. Just issue a revert patch to my code, or, i'll do it myself. I suggest we name the function something more generic though. I like 'group_list' like we have 'email_list', but anything goes. -Yaakov On Sun, Sep 28, 2008 at 10:32 PM, Ricky Zhou (周家杰) <ricky(a)fedoraproject.org> wrote: > fas/auth.py | 2 +- > fas/json_request.py | 14 ++++++++++++++ > 2 files changed, 15 insertions(+), 1 deletion(-) > > New commits: > commit cc20015bb73b0e18b91632dc452af0d8f614ab5a > Author: Ricky Zhou <ricky(a)fedoraproject.org> > Date: Sun Sep 28 22:32:37 2008 -0400 > > Initial fas_client method. > > diff --git a/fas/auth.py b/fas/auth.py > index 070259a..087ef2a 100644 > --- a/fas/auth.py > +++ b/fas/auth.py > @@ -89,7 +89,7 @@ def CLADone(person): > ''' > Returns True if the user has completed the CLA > ''' > - cla_done_group =config.get('cla_done_group') > + cla_done_group = config.get('cla_done_group') > try: > if person.group_roles[cla_done_group].role_status == 'approved': > return True > diff --git a/fas/json_request.py b/fas/json_request.py > index d762ed4..e56bfc3 100644 > --- a/fas/json_request.py > +++ b/fas/json_request.py > @@ -27,6 +27,7 @@ import sqlalchemy > > from fas.model import People > from fas.model import Groups > +from fas.model import PersonRoles > > class JsonRequest(controllers.Controller): > def __init__(self): > @@ -57,6 +58,19 @@ class JsonRequest(controllers.Controller): > > @identity.require(turbogears.identity.not_anonymous()) > @expose("json", allow_json=True) > + def fas_client(self): > + output = []; > + try: > + roles = PersonRoles.query.all() > + for role in roles: > + role.member.filter_private() > + output.append((role.member, role.role_type, role.group.name)) > + return dict(success=True, output=output) > + except InvalidRequestError: > + return dict(success=False) > + > + @identity.require(turbogears.identity.not_anonymous()) > + @expose("json", allow_json=True) > def person_by_username(self, username): > try: > person = People.by_username(username) > > >

1 0

func logrotate fix
by Mike McGrath 29 Sep '08

29 Sep '08

I'd like to implement the following global fix (its generating cron spam) in /etc/logrotate.d/func_rotate I'd like to change line 8 from /etc/init.d/funcd condrestart to /etc/init.d/funcd condrestart > /dev/null Can I get 2 +1's? -Mike

7 8

Just made a global change
by Mike McGrath 26 Sep '08

26 Sep '08

Hey guys, I accidental broke the freeze just now and didn't realize it till after I'd done it. I made a change to the puppetd.conf file thinking it'd only go to the puppet master but its gone out everywhere. I'll be more careful about that in the future. Let me know if it has any adverse affects (it shouldn't) -Mike

1 0

change request: [[MediaWiki:Common.css]]
by Ian Weller 26 Sep '08

26 Sep '08

(cc docs) Request to change https://fedoraproject.org/wiki/MediaWiki:Common.css to the following: ===== .messagebox.wikicleanup { background-image: url("/w/uploads/7/72/Wiki-cleanup-background.png"); background-repeat: repeat; } ===== Reason: to allow for [[Template:Wiki cleanup]] (a new admonition to replace using {{admon/note}} in {{move}}, {{delete}}, etc) to stand out from other admonitions as not being alerting to the user, but rather to wiki gardeners. The reason this can't be done right in the template is because MediaWiki is very, very careful about external images (even though this one is technically "internal"). Effect on remainder of wiki/website/world: Little to none. An error should have no effect on the rest of the style of the wiki, except for user styles. I do not believe there to be an error in the above. Why I'm asking: I have to wield my sysop powers on the wiki to do this, and I just wanted to make sure it was cool (especially since we're in a change freeze). Why I'm asking now: I'll forget later. -- Ian Weller <ianweller(a)gmail.com> http://ianweller.org GnuPG fingerprint: E51E 0517 7A92 70A2 4226 B050 87ED 7C97 EFA8 4A36 "Technology is a word that describes something that doesn't work yet." ~ Douglas Adams

3 3

Meeting Log - 2008-09-25
by Ricky Zhou 25 Sep '08

25 Sep '08

20:00 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Who's here? 20:00 * ricky 20:01 -!- cassmodiah [n=cass@fedora/cassmodiah] has quit "שָׁלוֹם" 20:01 * mmcgrath wonders if anyone else is 20:01 < fchiulli> fchiulli is lurking 20:02 < mmcgrath> abadger1999 dgilmore f13 fchiulli G jcollie lmacken marek ping? 20:02 < brothers> hi 20:02 < mmcgrath> brothers: yo 20:02 < dgilmore> gday mates 20:02 * lmacken 20:02 < fchiulli> mmcgrath: pong 20:02 < abadger1999> hola 20:02 < mmcgrath> yo 20:02 < mmcgrath> ok, lets get started 20:02 -!- skvidal [n=nnnnnnsk@fedora/skvidal] has joined #fedora-meeting 20:03 * jcollie will lurk a bit... got some $DAYJOB stuff to do in the background 20:03 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Tickets 20:03 < mmcgrath> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 20:03 < zodbot> mmcgrath: http://tinyurl.com/2hyyz6 20:03 < mmcgrath> .ticket 753 20:03 < zodbot> mmcgrath: #753 (Mini-freeze for Fedora 10 beta) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/753 20:03 < mmcgrath> So the freeze is still on until... 20:03 -!- balor [n=balor(a)gimili.plus.com] has quit Remote closed the connection 20:03 < mmcgrath> 2008-09-30 20:04 < mmcgrath> nothing extrodinary there. 20:04 < mmcgrath> Does anyone have work thats blocking on that release? 20:04 < mmcgrath> I know domsch might have some MM stuff, not totally sure though 20:04 < mmcgrath> k, I'll move on then 20:04 < mmcgrath> .ticket 395 20:04 < zodbot> mmcgrath: #395 (Audio Streaming of Fedora Board Conference Calls) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/395 20:04 < abadger1999> bunch of little stuff. I'm working on other stuff until then 20:05 < mmcgrath> <nod> 20:05 < mmcgrath> jcollie: anything new on this front? 20:05 < jcollie> nope 20:05 < mmcgrath> k 20:05 < mmcgrath> .ticket 446 20:05 < zodbot> mmcgrath: #446 (Possibility to add external links on spins page) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/446 20:05 < mmcgrath> dgilmore: ^^^ 20:05 < dgilmore> nope i think it should be closed 20:06 < mmcgrath> k, if you're ready to close it have at it. 20:06 * nokia3510 says hello 20:06 < mmcgrath> .ticket 740 20:06 < zodbot> mmcgrath: #740 (Loaning out system time to OLPC participants) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/740 20:06 * mmcgrath looks at ticket to see if anything new is there. 20:06 < dgilmore> here i really dont know if we can provide what they want 20:07 < mmcgrath> so my last question there never really got answered. 20:07 < mmcgrath> gregdek: ping 20:07 < gregdek> mmcgrath: pong 20:07 < mmcgrath> dgilmore: do you know if their end goal is education or if their end goal is packages 20:07 < gregdek> Oh, trac ticket. 20:07 -!- mdomsch [n=Matt_Dom(a)cpe-70-124-62-55.austin.res.rr.com] has joined #fedora-meeting 20:07 < mmcgrath> gregdek: we're talkinga bout https://fedorahosted.org/fedora-infrastructure/ticket/740 20:07 < dgilmore> mmcgrath: not really sure. i think both 20:07 < mmcgrath> k 20:08 < mmcgrath> dgilmore: do you think we could point them to SuSE's open buildsystem? 20:08 < mmcgrath> I have a reasonably good relationship with those guys, not sure if they'd be interested or not. 20:08 < gregdek> aiui, the biggest problem is they've got participants who are being asked to build packages for OLPC, but they don't have Fedora systems, only Debian systems. And they end up doing weird stuff to get packages built. 20:09 < mmcgrath> and OLPC builds packages now, do we just need the koji client in debian? 20:09 < dgilmore> mmcgrath: not really. 20:09 < dgilmore> mmcgrath: honestly i think having koji in debian/ubuntu would go a long way to helping 20:09 < dgilmore> since mock is tehre and works 20:10 < mmcgrath> I guess I'm still confused by what is there, what they want and what they would suggest Fedora's role in that should be. 20:10 < mmcgrath> gregdek says they have people who are being asked to build packages, is this like OLPC extras or something? 20:10 < mmcgrath> OLPC.us? 20:10 < mmcgrath> :) 20:10 < ricky> Hehe 20:11 < gregdek> You know, I'm unsure. 20:11 < dgilmore> mmcgrath: most of it is dealling with fedora packages. 20:11 < dgilmore> mmcgrath: a tiny amount is packages not in fedora 20:11 < mmcgrath> so getting fedora packages into OLPC? 20:11 < dgilmore> but thats really tiny 20:11 < dgilmore> yeah 20:11 < mmcgrath> so they're worried about the tiny portion not in Fedora? 20:11 < mmcgrath> or the portion that is in Fedora? 20:11 < mmcgrath> if so, are we just talking about another distribution of Fedora similar to what EPEL is now? 20:12 < dgilmore> dealling with testing builds in mock. i.e. for new packages. dealing with submitting builds to koji 20:12 < mmcgrath> and the requirements are that this work on debian? 20:12 < dgilmore> thats the main hurdle 20:12 -!- jmtaylor [n=jason@fedora/jmtaylor] has joined #fedora-meeting 20:13 < mmcgrath> so there's potentially two parts to this 20:13 < mmcgrath> 1) is getting the koji client into debian, mock already is. 20:13 < mmcgrath> dgilmore: does mock build olpc packages just fine? what does it build against? 20:13 -!- fbijlsma [n=fbijlsma(a)p4FDC4F8C.dip.t-dialin.net] has joined #fedora-meeting 20:13 < dgilmore> mmcgrath: most people use the fedora release that there targeting against 20:13 < mmcgrath> k 20:14 < dgilmore> mmcgrath: though i have a mock config that uses olpc specfic packages also 20:14 < mmcgrath> and thast something that could be done on debian today? 20:14 < dgilmore> yes 20:14 < dgilmore> really whats missing is koji 20:14 < dgilmore> and maybe fedora-packager 20:15 < mmcgrath> so the thing the OLPC debian guys can't do is actually submit builds to koji so I'd think really we need to get one of those debian guys to get koji into debian. 20:15 < mmcgrath> or one of our guys to do it, I have no idea what the process is there. 20:15 < dgilmore> yeah i think one of them would be best 20:16 < mmcgrath> dgilmore: gregdek: do either of you know who we could assign this ticket to in debian world? 20:16 -!- JSchmitt [n=s4504kr@fedora/JSchmitt] has quit "Konversation terminated!" 20:16 < dgilmore> mmcgrath: ill ask them to provide someone 20:16 < mmcgrath> k 20:16 < dgilmore> lets move on 20:16 < mmcgrath> k 20:16 < mmcgrath> Thats the last of the tickets 20:16 -!- kulll [i=d318e24a(a)gateway/web/ajax/mibbit.com/x-d4dfe58a02d08d2a] has joined #fedora-meeting 20:17 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- puppet training 20:17 < mmcgrath> I dropped the ball on that puppet training. It'll happen next week I swear! 20:17 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- oVirt 20:18 < mmcgrath> I've been working to get xen6 rebuilt with oVirt. It is now dedicated to just the staging environment. there's a couple of potential uses there and possibly some upcomming projects as well. 20:18 -!- c_scott [n=cscott(a)schoolserver.laptop.org] has joined #fedora-meeting 20:18 -!- m_stone [n=mstone(a)dhcp-47-72.media.mit.edu] has joined #fedora-meeting 20:18 < m_stone> dgilmore: howdy. what can I do for you? 20:18 < mmcgrath> But I (and hopefully the rest of us) will be able to get our hands dirty with ovirt and help the developers harden it and get it ready. 20:18 < mmcgrath> dgilmore: I'll switch the topic back 20:18 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Tickets 20:18 < mmcgrath> .ticket 740 20:18 < zodbot> mmcgrath: #740 (Loaning out system time to OLPC participants) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/740 20:19 < mmcgrath> m_stone: we were looking at that ticket and from what we understand, we just need to get the koji client into debian but we don't know how to do that. 20:19 < m_stone> mmcgrath: that would certainly be a good first step. 20:19 < mmcgrath> m_stone: do you know any debian guys who can package it and get it in? 20:19 < m_stone> I can probably scare some up. 20:20 < m_stone> (though not this week!) :) 20:20 -!- DemonJester [n=DemonJes@fedora/DemonJester] has quit "leaving" 20:20 < smooge> quick question... mediawiki .. do we need to update to something furhter on upstream? I am looking at the source now 20:20 < mmcgrath> dgilmore tells me mock is already in debian so it should have everything we need to 1) test mock builds on debian workstations and 2) ultimately submit those builds to koji to be built. 20:20 < dgilmore> m_stone: what kind of educational assistance do you think fedora could offer? 20:20 < m_stone> mmcgrath: the difficulty is that, as of the last time I tested it, mock's usage of yum on debian was failing. 20:20 < dgilmore> m_stone: what are the ultimate end goals your hopping we can provide? 20:20 -!- marcopg_ [n=marco(a)host162-118-dynamic.9-87-r.retail.telecomitalia.it] has joined #fedora-meeting 20:20 < m_stone> so it was unable to initialize chroots. 20:20 < c_scott> m_stone: no, mock WorksForMe 20:20 < m_stone> c_scott: glad to hear it! 20:21 < c_scott> a koji port would be very nice, though 20:21 < m_stone> I'll retry it myself then. 20:21 < c_scott> i'd like to see the olpc repo configurations make it into mock upstream, though 20:21 < dgilmore> m_stone: i know mock worked for me when testing 20:21 < m_stone> (or else teach mock to be able to pull form urls) 20:21 < abadger1999> That would be nice from my perspective as well. 20:21 < m_stone> i.e. to pull configurations from, say, http urls 20:21 < dgilmore> m_stone: was it just ubuntu that was having issues? i used plain debian 20:22 * abadger1999 needs olpc repo's for the package database. 20:22 < nirik> smooge: it still needs to be built for epel... ianweller or you or whoever should do that if it's ready to be used. ;) 20:22 < m_stone> dgilmore: it was plain debian too. 20:22 < c_scott> dgilmore: yes, i use plain debian, too. 20:22 < m_stone> dgilmore: I last tested this March 7 though. 20:22 < m_stone> so it has been a while. 20:22 < m_stone> dgilmore: anyway, returning to your questions about educational assistance and goals... 20:22 < dgilmore> c_scott: there a few extra configs that need to get into mock 20:23 < m_stone> http://wiki.laptop.org/go/Developer/Fedora should give you some idea of the audience we're targetting. 20:23 < m_stone> however, if you glance at the 'outside reading' section... 20:24 < m_stone> you'll see that the tutorials/guidelines for actually writing specfiles which are listed are all severely out of date.. 20:24 < mdomsch> c_scott, if the olpc configs exist, adding them to mock should be trivial 20:24 < c_scott> mdomsch: dgilmore's got 'em 20:24 < m_stone> either the Maximum-RPM snapshot or the draft 'creating rpms' chapter. 20:25 < m_stone> dgilmore: consequently, I'm interested in three basic things. 20:26 < m_stone> dgilmore: 1) ability to use A Single Program for basic specfile maintenance tasks. this could be the common Makefile if it were easily adapted by newbies to new packages, it could be my Makefiles, etc. 20:26 -!- Gaaruto [n=Gaaruto@fedora/Gaaruto] has joined #fedora-meeting 20:26 < m_stone> having to immediately learn the individual command lines for git, cvs, rpmbuild, rpmlint, mock, and koji simultaneously doesn't work real well, in my experience. 20:27 < mmcgrath> m_stone: it doesn't work well even one at a time :) 20:27 < dgilmore> m_stone: you mean for getting packages ready for review? 20:27 < m_stone> 2) some authoritative written documentation on how to deal with specfiles. 20:27 < m_stone> dgilmore: for that, and also for bumpspec, changelog update from VCS logs, simplified error detection for %files problems, ... 20:27 < m_stone> that sort of thing. 20:27 < abadger1999> m_stone: Are we mostly talking new packages or maintaining old packages? 20:28 < m_stone> abadger1999: a mix of both. the documentation I wrote was geared at tweaking existing packages. 20:29 < m_stone> abadger1999: on the other hand, requests for new packages come up frequently. since FUDCON Boston, though, it's been a lot easier to get help from folks like mether on the new-requests packaging. 20:29 < c_scott> also, i'd rather like some tools to help manage forked packages -- starting with basic notifications when there's a new (say) f9 release of a package with an olpc3 fork 20:29 < m_stone> dgilmore: similarly, a source-code browser for the patched contents of SRPMs. -- I've started on this myself and may eventually finish it, but this ought to be useful for Fedora too. 20:29 < c_scott> and, if I get ambitious, a way of automatically applying patches to (say) f9 packages to get a corresponding olpc3 package 20:30 < m_stone> dgilmore: anyway, moving into the rest of the education problem. 20:30 < abadger1999> m_stone: #fedora-devel is the best resource for tweaking existing packages as it's likely to be one-off questions. 20:30 < m_stone> dgilmore: I benefitted greatly from hands-on tutoring on making rpms from bernie, from dcbw, and from you. 20:31 < m_stone> dgilmore: however, in order to be able to benefit from that tutoring, I needed both a fedora machine and access to the tutor. 20:31 < abadger1999> New packages would benefit from having someone mentor. 20:31 < m_stone> dgilmore: lots of people who I've tutored since then simply do not have easy access to a fedora development machine. 20:31 < m_stone> conceivably they could use a livecd, but in practice, it's still a real pain. 20:31 < abadger1999> The mingw people have started building a script that can help with forked packages... although we'dwant to reduce forking in olpc's case if possible. 20:31 < m_stone> and they still have to figure out where to find a mentor and how to give the mentor access to the build environment, etc... 20:32 < dgilmore> m_stone: so with the approriate tools on whatever distro they use they should be able to do thinks ok. 20:32 < dgilmore> m_stone: and they would have an XO to actually test things on 20:32 < c_scott> abadger1999: the goal is actually to help distinguishing (a) what packages are currently forked, (b) what the patch is that requires them to be forked 20:32 < c_scott> abadger1999: both help long term in ensuring changes are merged upstream to mitigate future need for the fork 20:33 -!- stickster_afk is now known as stickster 20:33 < abadger1999> c_scott: I think the mingw script does the opposite. 20:33 < c_scott> abadger1999: ? 20:33 < abadger1999> But maybe you could run it with the branches switched. 20:33 < m_stone> dgilmore: it's possible that you're right; it just makes more sense to me think of it as a Fedora-based 'newbie's sandbox' in koji. 20:34 < f13> sorry, I was busy 20:34 < m_stone> dgilmore: for example, you can imagine wanting to build up a browsable library of spec-file corrections made by experienced folks to newbie specfiles. 20:34 < abadger1999> Basically, it was designed so the mingw people could have a cross-compiled version of a Fedora package. then they can run the script to tell them what has changed in the Fedora-native package. 20:34 < m_stone> dgilmore: so that new folks have a wide variety of materials to browse to try to bootstrap themselves into knowledge. 20:34 < c_scott> abadger1999: ok, i see 20:35 < c_scott> abadger1999: but that tends to perpetuate the fork ;-) 20:35 < c_scott> i want to base all our packages on an f9 package, and just apply a patch to them automatically 20:35 < abadger1999> c_scott: yeah. In their case, the fork is permanent (the crosscompiled package is always going to be separate even if the source is all the same). 20:36 < abadger1999> <nod> 20:36 < dgilmore> m_stone: we have cvs history :). i can think of a few improvements for fedora-packager from this. 20:36 < m_stone> dgilmore: how is cvs history browsable? 20:37 < dgilmore> m_stone: cvsweb 20:37 < abadger1999> You want to say I have one olpc-specific patch and two that I submitted upstream (Fedora). New Fedora version is out, what patches can I drop, what patch do I need to rebase to the new version. 20:37 < m_stone> dgilmore: and how can diff between the upstream sources? 20:37 -!- ldimaggi_ [n=ldimaggi@nat/redhat/x-ce1910205342fe50] has quit "Leaving" 20:37 < m_stone> dgilmore: remember that a lot of folks are both the upstream and the packager for us. 20:37 < m_stone> and it's particularly confusing for them since the fedora docs mainly assume that packagers are not upstream. 20:37 < dgilmore> http://cvs.fedoraproject.org/viewvc/rpms/ however not easily searchable 20:38 < abadger1999> m_stone: Not that they aren't... just that they separate their roles. 20:39 < dgilmore> m_stone: it would be great if you could add some comments to that ticket. 20:39 < m_stone> dgilmore: okay, I can do that. 20:39 < m_stone> poke me again when it's not release week. :) 20:39 < dgilmore> :) will do 20:39 < m_stone> also, thanks for being so open to these suggestions. 20:40 < mmcgrath> we like openess :) 20:40 < m_stone> as I said before, I'm happy to take a crack at some of this myself; I just wanted to make sure you were aware of what I was aiming for. 20:40 < mmcgrath> dgilmore: m_stone: anything else for now or can we move on to the next meeting item? 20:40 < mmcgrath> m_stone: FYI, you can almost always find us in #fedora-admin should you have questions or ideas concerning this (or anything else for that matter) 20:40 < m_stone> mmcgrath: I'll follow up w/ dgilmore again in future weeks, then we can see where we stand. 20:40 < m_stone> good? 20:40 < mmcgrath> sounds good, m_stone please do make notes in the ticket so we don't forget - https://fedorahosted.org/fedora-infrastructure/ticket/740 20:40 < m_stone> mmcgrath: will do. 20:41 < mmcgrath> You'll need a fedora account for that, but not a CLA - https://admin.fedoraproject.org/accounts/ 20:41 < mmcgrath> Ok, if there's nothing else I'll move on to the next item. 20:41 -!- bryan_kearney [n=bkearney@nat/redhat/x-ff8ab0eafb7c82fd] has left #fedora-meeting ["Jar Jar Binks is my co-pilot"] 20:41 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- oVirt 20:41 < mmcgrath> K, so the oVirt team (ovirt.org) is working on some stuff and I think it'd be good for our team to adopt it. 20:42 < ricky> I looked at the website a tiny bit. Is it an appliance "take-over-the-machine" type thing, or just a package that you install? 20:42 < mmcgrath> We can't blanket move our infrastructure to it because we're almost entirely paravirt right now and not all of our hardware suports hardware virt. 20:42 < mmcgrath> ricky: both. 20:42 < SmootherFrOgZ> ricky: it's an appliance 20:42 < mmcgrath> But right now they just have an image for you to use and install. 20:42 < ricky> Aw :-( 20:43 < mmcgrath> ricky: my understanding is this is still very early. 20:43 < mmcgrath> the good thing about us getting involved now is we can make sure and make suggestions to help suit our needs and what we think others needs will be. 20:43 < ricky> OK. Hopefully, that will be one of the things 20:44 < SmootherFrOgZ> mmcgrath: what is the goal ? use the image appliance or make all service up and running for fedora-infra ? 20:44 < mmcgrath> well, in our case there's a couple of goals. 20:44 < mmcgrath> the primary goal is to look at whether or not we think ovirt will be the future of virtualization in the RH stack of virtualization. 20:45 < mmcgrath> I don't think we really have a say in it, but as fedora goes, it typically follows that RHEL goes. 20:45 < dgilmore> mmcgrath: having a base appserver appliance proxyserver applaince etc? 20:45 < mmcgrath> And managment tools in the open source space are horrible right now. 20:45 < mmcgrath> dgilmore: well, the ovirt stack's primary win is its management piece, and really thats the appliance. 20:45 < mmcgrath> so, in theory, we can 'convert' our current images to use to ovirt stack. 20:45 < mmcgrath> which, AFAIK, will just work. 20:45 < dgilmore> mmcgrath: ok 20:45 < SmootherFrOgZ> mmcgrath: correct 20:46 < mmcgrath> SmootherFrOgZ: did you do any conversions or was all your stuff fresh? 20:46 < lmacken> mmcgrath: how come we can't just start using it on everything? It uses libvirt, which supports xen and kvm, no ? 20:46 < SmootherFrOgZ> some conversions from xen host, yeah 20:46 * lmacken knows nothing about oVirt though, other than it is a rails app 20:46 < mmcgrath> lmacken: well, it uses libvirt's api, and libvirts api supports xen and kvm, but ovirt doesn't yet. 20:46 < mmcgrath> I get the feeling that we are VERY early adopters of ovirt. 20:46 < lmacken> odd, ok. 20:47 < mmcgrath> SmootherFrOgZ: were your xen host images actual disk images or were they partition images? 20:47 -!- Sonar_Guy [n=Who_Know@fedora/sonarguy] has joined #fedora-meeting 20:47 < lmacken> Sounds good to me though, I'm all for it. Do we have any kvm guests yet ? 20:47 < mmcgrath> not a single one yet. 20:47 * ricky didn't know about the rails part :-) 20:47 < mmcgrath> though hopefully some of our staging environment will be. 20:48 < dgilmore> mmcgrath: we were very early adopters of xen also 20:48 * SmootherFrOgZ only use partition images, but i did some tries with disk image 20:48 < lmacken> dgilmore: and TurboGears ;) 20:48 -!- mdomsch [n=Matt_Dom(a)cpe-70-124-62-55.austin.res.rr.com] has quit Remote closed the connection 20:48 < mmcgrath> dgilmore: yep, and I miss all that pain :) 20:48 < mmcgrath> SmootherFrOgZ: k 20:49 < mmcgrath> So yeah, I'm hoping FI can get a good working relationship with the oVirt guys so if you see them poking around at what we're doing, spend some time talking to them, ask questions and answer theirs. 20:49 < SmootherFrOgZ> i think we should add closer look on all services that ovirt requires also 20:49 -!- nman64 [n=n-man@fedora/nman64] has quit Remote closed the connection 20:49 < ricky> #ovirt and #ovirt-devel, I assume? 20:50 < mmcgrath> <takes_off_RH_hat>Considering that RH bought Qumranet it seems likely to me that they'll be pushing harder for KVM, especially since its already in the kernel and some how xen has still managed to fail at that </rh_hat_off> 20:50 < mmcgrath> <nod> 20:50 < ricky> Er, not #ovirt-devel, #ovirt on OFTC, apparently 20:50 < mmcgrath> I don't really have a view into that virtualization stack stuff yet but maybe this will be a better way to see what RH's roadmap is for all of that. 20:50 < dgilmore> ricky: the virt guys seem to like oftc 20:51 < ricky> Heh. 20:51 < mmcgrath> I have to figure there will be a seemless way to convert from xen to kvm by RHEL6 but I guess we'll have to see. 20:51 < dgilmore> #virt there is for libvirt 20:51 < mmcgrath> :) 20:51 < mmcgrath> So anywho, anyone have any questions on that? 20:51 * dgilmore has none 20:51 < ricky> Is this something that'd be hard to setup at home? 20:51 < mmcgrath> ricky: you'd need hardware virt support. 20:51 < SmootherFrOgZ> ricky: not 20:51 < mmcgrath> I actually don't have a single box here at home that has that. 20:52 < ricky> But it won't take over the machine with appliance-y stuff, right? 20:52 < mmcgrath> other then that though, I don't think it'd be difficult. 20:52 < mmcgrath> ricky: the appliance is an actual image that you'd run in KVM. 20:52 < SmootherFrOgZ> ricky: but you will also need to have a lot of memory for the image appliance 20:52 < mmcgrath> so its like a 500M download or something then you run it. 20:52 < ricky> OK 20:53 < SmootherFrOgZ> ricky: fedora packages seem to work well just like ovirt repo btw 20:53 < mmcgrath> Ok, anyone have anything else on that? If not I'll open the floor. (we're running out of time) 20:53 < dgilmore> nothing more from me 20:53 -!- fbijlsma [n=fbijlsma(a)p4FDC4F8C.dip.t-dialin.net] has quit Read error: 113 (No route to host) 20:53 < mmcgrath> k 20:53 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Open Floor 20:53 < mmcgrath> Anyone have anything they want to talk about? 20:53 * mmcgrath wants to mention he'll be missing for a chunk of tomorrow afternoon. 20:53 < SmootherFrOgZ> just a quick question 20:54 < mmcgrath> SmootherFrOgZ: sure thing. 20:54 < SmootherFrOgZ> there is a cron tack on buildsys (for koji) which actually does nothing 20:54 < SmootherFrOgZ> s/tack/task 20:54 < mmcgrath> which one? 20:54 < dgilmore> SmootherFrOgZ: what one 20:54 < mmcgrath> its on buildsys.fedoraproject.org or koji.fedoraproject.org ? 20:55 < SmootherFrOgZ> this cron deamon on koji.fp.o 20:56 < SmootherFrOgZ> Cron <apache@koji1> $SCRIPT --action=prune 20:56 < dgilmore> abadger1999: thats for koji-gc 20:56 < dgilmore> SmootherFrOgZ: ^ 20:56 < SmootherFrOgZ> there a couple of 20:56 < SmootherFrOgZ> delete, purge, etc 20:56 < mmcgrath> dgilmore: are we gc'ing again? 20:56 < dgilmore> SmootherFrOgZ: it needs to be fixed i was waiting for infra freeze to be over to fix it 20:56 < dgilmore> mmcgrath: no 20:57 < dgilmore> mmcgrath: auth is not right 20:57 < dgilmore> I can fix it now 20:57 -!- rdieter is now known as rdieter_away 20:57 < SmootherFrOgZ> here is the lil' log 20:57 < dgilmore> but was going to wait for freeze to be done 20:57 < dgilmore> SmootherFrOgZ: i know exactly what it is 20:57 < SmootherFrOgZ> Error: unable to log in, no authentication methods available 20:57 < dgilmore> SmootherFrOgZ: for now ignore it 20:57 < SmootherFrOgZ> dgilmore: ok ;) 20:58 < mmcgrath> dgilmore: yeah, lets fix it after the freeze. 20:58 < mmcgrath> Ok, anyone have anything else to discuss? If not I'll close the meeting in 30 20:58 < ricky> If we're have any thoughts about which CA we're planning to use, I'd be willing to test it out at home 20:58 < dgilmore> ricky: dogtag 20:59 < ricky> Cool, I'll start playing around with it and seeing how FAS can talk to it, etc. 20:59 < dgilmore> ricky: i have some feedback from the devs on what we will need to do to migrate from what we have now 20:59 < mmcgrath> 15 20:59 < mmcgrath> :) 20:59 < ricky> Worst case, I'll start a fresh setup with it just to test FAS against it 20:59 < ricky> That's all I had :-) 20:59 < mmcgrath> K 20:59 < mmcgrath> with that 21:00 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Meeting Closed

1 0

oVirt and xen6
by Mike McGrath 24 Sep '08

24 Sep '08

Hey guys, I'm going to convert xen6 to F9 soon to do some ovirt/kvm testing. xen6 is almost dedicated to staging now, it will be before I start (need to move fas2 somewhere else). -Mike

3 6

Stale Fedora Hosted Projects (revisited)
by Mike McGrath 24 Sep '08

24 Sep '08

Getting back to this. What should we do with code to which no one claims ownership or the owner cannot be found? -Mike

7 17

A new member...
by Kevin Cadieux 24 Sep '08

24 Sep '08

Hello everyone, My name is Kevin, and I just recently created my account to be a member of the Fedora Project. I was interested in getting involved, so I looked at the different sub-projects on the wiki. I found that the Infrastructure sub-project was the one that suited best my experience and interests. So here I am now, writing to you all to introduce myself :) I am a Computer Engineering student at the University of Sherbrooke in Quebec, Canada. I am very organized with my school work so I can easily manage to get 10 to 20 hours of "Fedora" time per week. I am still in the process of reading the different documents on the wiki in order to get up to speed with Fedora and the Infrastructure group. So, if you have any advice as to what would be the best thing to start with, feel free to let me know. It would be greatly appreciated. In the meantime, I'll continue my reading and let you all know when I feel ready to roll. Thanks a lot, Kevin

2 2

My first mail
by liang yu 24 Sep '08

24 Sep '08

Hi all: I am a new member of the Fedora Infrastructure team.My name is Yuliang from China.I have plenty of spare time to contribute and wish to involve the team. I like programming Any suggestion or mentorship from the team is important to me.I want to work with you qucikly. Best Regards Yuliang

1 0

Some doubts for creation of new projects in fedorahosted
by Huzaifa Sidhpurwala 23 Sep '08

23 Sep '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I was doing a ticket on creating new projects on fedorahosted today and found certain anomalies in the documentation [1]. Since this is my first ticket on creating new projects on fedorahosted, I am not sure if my methods are correct, hence this email. The ticket in question is [2] 1. When a create a new git repo and do a git clone, exactly following the instructions on the wiki, i get a "headers does not exist message" I resolved it by doing cd /git/libaio.git; sudo git init This worked dont know if it is correct though 2. When running the script to create a new project, It seems that the trac enviroment was correctly created however adding a user to TRAC_ADMIN group gave the following error: "Command failed: columns username, action are not unique" However the user does get added to TRAC_ADMIN Group. Also the script already has step 6 [1] incorporated so i dont think that is needed. I would really appreciate if someone with a more experience can help me out a bit. Thanks a lot in advance. :) [1] https://fedoraproject.org/wiki/Infrastructure/ProjectHosting/RepositorySetup http://fedoraproject.org/wiki/Infrastructure/ProjectHosting/CreateNewProject [2] https://fedorahosted.org/fedora-infrastructure/ticket/837 - -- Regards, Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas) GnuPG Fingerprint: 3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFI2JAQzHDc8tpb2uURAnKZAJ9bLQDyOAl9o10snMUDDQx9gnmB7QCfUkR5 wt2/QjUOVGvsS0JvMkOB8hw= =Rj3g -----END PGP SIGNATURE-----

2 1

Big thank you to the Fedora infrastructure team
by Rahul Sundaram 23 Sep '08

23 Sep '08

Hi, Just passing on the message, http://forums.fedoraforum.org/forum/showthread.php?t=199590 Rahul

1 0

[Fwd: How to become a public mirror]
by Ignacio Vazquez-Abrams 22 Sep '08

22 Sep '08

For your consideration. -------- Forwarded Message -------- From: Truong Anh. Tuan <tatuan(a)gmail.com> To: webmaster(a)fedoraproject.org Subject: [SPAM] How to become a public mirror Date: Tue, 23 Sep 2008 00:40:05 +0700 (ICT) Dear sir/madam, We are the HanoiLUG, the largest Linux User Group and FOSS community in Vietnam. Currently, we have got a server contributed by Intel and Internet connection contributed by NetNam for mirroring Linux distibutions as well as FOSS in Vietnam (we call it Virror project). Honestly, I can not find how to become a Fedora public mirror, even, after read this Wiki article: http://fedoraproject.org/wiki/Infrastructure/Mirroring Could you please tell us more about this. Thanks, Tuan TRUONG A HanoiLUG member

1 0

Change Request - Elections
by Nigel Jones 22 Sep '08

22 Sep '08

Technically not directly covered in the Beta Freeze, but it's only running on app4 at the moment and the settings it's on now is okay for the infrequent use of casual browsing, but the Art team want to use it for the next 36 or so hours. Can I get a +1 to bump to the resources used during the FESCo/Board votes? Thanks - Nigel -- Nigel Jones <dev(a)nigelj.com>

5 5

Change request: bugfix for packagedb-bzsync
by Toshio Kuratomi 22 Sep '08

22 Sep '08

We've got a pair of problems with the packagedb-bugzilla sync script that is keeping bugzilla from being updated with new information that I'd like to deploy. Both are extremely simple (so easy to back out) and both are causing bugzilla to not update. 1) config change. The debug flag was left on when we deployed a new version of the script a few weeks ago. Unfortunately, for this script, debug implies dry_run. So no updates occur while debug is on. 2) one line bugfix. The script was attempting to change a variable containing a fas username into a bugzilla email address twice. This failed on the second attempt since the email address couldn't be found in the username field. This change affects app5 (where the scripts run) and bugzilla. Since the script was hitting pkgdb before (just not updating bugzilla), it shouldn't affect the pkgdb. Can I get two +1's ? -Toshio

3 2

haproxy SOP
by Mike McGrath 22 Sep '08

22 Sep '08

https://fedoraproject.org/wiki/Infrastructure/SOP/haproxy As most of you know we're slowly migrating from mod_proxy_balancer to haproxy. Just doing an app at a time. here's the haproxy SOP. -Mike

1 0

Re: Planning a future L10N infrastructure (including Fedora)
by Asgeir Frimannsson 22 Sep '08

22 Sep '08

Hi Dimitris, Thanks for your comments. ----- "Dimitris Glezos" <dimitris(a)glezos.com> wrote: > 2008/9/17 Asgeir Frimannsson <asgeirf(a)redhat.com>: > > On Tuesday 16 September 2008 23:29:32 Mike McGrath wrote: > >> > > > >> > > Please correct me if I'm reading this wrong but I see > "transifex is > >> > > great or close to it" and "here's how we're going to build our > own > >> > > solution anyway" ? > >> > > >> > Yes, "Transifex is great and will continue to serve us". > >> > > >> > BUT: > >> > > >> > If you look at the state of the art in L10N outside the typical > Linux > >> > projects where PO and Gettext rule, you'll notice we are very > short on > >> > areas like: - Translation Reuse > >> > - Terminology Management > >> > - Translation Workflow and Project Management > >> > - Integration with CMSs. > >> > - Richer Translation Tools > >> > > >> > This is an effort in narrowing that gap, and I can't see that > effort work > >> > by evolving an existing tool from this 'cultural background'. > Yes, we can > >> > get some of the way by developing custom solutions for e.g. > linking wikis > >> > to Transifex for CMS integration, or using e.g. Pootle for > web-based > >> > translation. But we would still be limited to the core > architecture of > >> > the intent of the original developers, which is something that > would > >> > radically slow the project down. > > For the record, I believe these are some fine ideas, which I would > like to see added to Transifex as features (eg. through plugins). I > have been discussing most of them with people around conferences for > the past year. An example: Tx already downloaded all the translation > files from upstream projects, so if someone requests a translation > file, why not be able to pre-populate it using existing translations > from all the other projects (translation reuse)? > > Also, I should mention that Transifex isn't (and will never be) > specific to a particular translation file format (eg. PO) or any > translation repository. I'd like to support translation of both PO > and > XLIFF files. And also support not only VCSs, but CMSs, wiki pages and > even arbitrary chunks of text. Transifex's goal is to be a platform > to > help you manage your translations. For the record (since XLIFF is mentioned and since I'm part of the Oasis XLIFF Technical Committee), I am not aiming to design anything around XLIFF in this project, other than perhaps support XLIFF is an import/export format for resources in the same way as we support PO (we do have the odd XLIFF file coming through for translation). I don't think XLIFF (1.2) is mature enough yet as a L10N resource format. I know there are some big ideas in transifex. In fact, when transifex is mentioned, often people refer to the *goal/idea* of transifex, rather the actual current implementation. Take for example plugins, transifex doesn't currently have a plugin system, neither does it have workflow, project management, or any concept of translation resources internally. Transifex today is a simple 'file submission system' with a growing community aiming to build it into something more. With this in mind, 'building on top of transifex' really means redefining what transifex really is. For example, 'file submission' should really be a plugin, not a core feature. That means all of transifex today (excluding maybe the login UI), should really be plugins to a core model of projects, people, etc, that currently doesn't exist. Defining this 'model' of a repository doesn't really depend much on the implementation, and in fact many implementations might help push this faster and ensure a better solution (if it was on the tx roadmap in the first place). And it's not like it is impossible for e.g. a java based repository to communicate with Transifex for file submissions, isn't that exactly what the remote-interface of TX (on the roadmap) is supposed to provide? What I'm hearing is "Don't build something new, continue building on the python/tg/transifex architecture", which is fully understandable. However, considering the cost of developing this on top of tx (re-architecture, convincing all that it is the right path to go, immaturity/stability of libraries for e.g. ajax, limited workflow support), I honestly think it's better with two projects that 'compliment' each other. There are more than enough tasks for everyone in the existing Tx roadmap, and the idea is bigger than what a combined development team could accomplish. Diversifying and pulling in good people from e.g. the java-side of things might even help speed things up. > >> Correct me if I'm wrong though, instead of forking or adapting or > working > >> with upstream, you are talking about doing your own thing right? > > > > We have a goal of where we want to see L10N infrastructure go, to > enable us in > > the future to provide internal (translators paid by Red Hat) and > community > > translators with tools to increase their productivity as well as > better tools > > to manage the overall L10N process. If there is an 'upstream' that > provides > > this, or a platform on to which we could develop this, then yes, we > would > > consider 'working with upstream' or (in a worst-case-scenario) > forking > > upstream. > > The Translate Toolkit folks are a very friendly bunch, actively > maintaining and extending the rich library, and always open to > suggestions. Maybe some (if not all) of the features could be done in > TT, and the rest that might not fit there, as Python libraries to > maximize interoperability and community involvement. Yes, I know TT very well, and have discussed the library with Dwayne Bailey (the main visionary behind the project) in the past, even before tx was born. In fact, a django-migration of Pootle (built on top of the TT) has been on the agenda for a while, and combining forces with TT is one of the other options I have been strongly considering for a repository (TT e.g. has a file submission library, and there is a lot of duplication between tt and tx). Looking at the svn activity of TT (in my rss reader), it is definetly a project with a 'dangerous' future. > I also think that Transifex could serve as the "UI" for a lot of > translation-specific tasks. If there's a library that does X, that > would help people manage their translations or leverage Transifex's > strong points of "I read a lot of repositories" and "I write to some > repositories", then we could provide a web wrapper around it. (eg. > search for string "X" in all translation files of language "Y", or > "mark <this> file as a downstream of <that> and send me an msgmerged > file whenever <that> changes". > > > So to answer your question bluntly, YES - after 4 years involvement > in > > industry and community L10N processes - I believe we can do better. > But > > holding that thought, remember that this is in many ways > 'middleware', and > > making use of e.g. the vast amount of knowledge invested in > Translate Toolkit > > (file format conversions, build tools, QA) makes sense, and I'm not > saying > > 'forget about all that we have invested in tools so far'. > > It might be my poor English or the fact that I usually read long > mails > at night, but despite the lengthy descriptions I still don't have a > clear picture of exactly what problem you'd like to solve, and the > reasoning behind the decisions being made. I do understand there is a 'semantic gap' here, and that we do need to provide a better description and demonstration of why a new project is necessary. I do believe everything is theoretically possible to build on top of python/tg and through reuse of concepts in e.g. tx and TT, but I honestly believe if we are going to manage and drive the development effort in this, it is more worthwhile to expand beyond the fedora/python community, and use tools that the core developers would be more comfortable and productive with. This is not a 'we think you guys should develop this' request, we are taking ownership of the project, as well as inviting anyone that is interested in the community to participate and take ownership. > Don't take me wrong -- I think there are some good ideas. But I feel > it would be too bad if you guys didn't invest on top of existing > tools > (TT for file formats, Transifex for file operations and UI, OmegaT > for > translation memory) or just isolate specific solutionsthat don't fit > into other projects in well-defined libraries (do one thing, to it > right). Sure, it takes a lot more effort to work *with* other people, > but it is usually worth it. :-) This is *not* about an effort to avoid working with people. It is an effort to get more people working on this. I know more people in the Java community that is or might be interested in a open source solution for these problems than in the Python/Fedora/TG community. And of course adding to this a portion of my natural bias towards Java, and the fact that the people that would be working on this would initially be much more productive in Java than in Python (TG2 or django). With the fact that we throw this idea out to the fedora/tx community early, please take that as a sign that we are trying to work with the community, rather than simply developing something on our own. And I for one will continue being involved with Tx to some degree, and help out where I can. L10N is an area with a lot of space for improvement, and an area that has sadly been to some extent 'neglected' except for Dimitris' recent work. We still have a long way to go before we have what I would call a L10N infrastructure that serves translators well. cheers, asgeir

1 0

Planning a future L10N infrastructure (including Fedora)
by Asgeir Frimannsson 21 Sep '08

21 Sep '08

Hi infrastructure wranglers, (cc transifex-devel) Over the last few months, a few of us involved in Red Hat L10N engineering have discussed how to best ensure we have Localisation Infrastructure and Tools that can serve the needs of Red Hat, JBoss, Fedora and 'upstream' communities in years to come. Let me first describe some of the background and requirements behind this project: Up until now, we have managed translations through version control systems such as CVS, Svn and Git. This has ensured that all contributions are pushed upstream, as we always store translations within the upstream repositories and projects. 'Damned Lies' further gave us a tool to view language-specific translation statistics for modules, branches and releases, as well as convenient information about people, teams and projects. This has been a great help for translators in their work. Dimitris' (and others) work on Transifex has in addition given the translation community a way to submit translations upstream without ever touching a developer-centric version control system, which has been of great help to translators. Some of the immediate needs that could be addressed within the existing framework (some of which are on the Transifex roadmap) are: - Consolidation of Damned Lies and Transifex, allowing retrieving and submitting translations through the same interface - Allowing retrieving and submitting multiple-files at once (e.g. for translating a publican document with many PO files) - Simple workflow on top of Transifex (porting features from Vertimus) - Better usability and easier user registration process (Fedora specific) Transifex is gaining some traction upstream (e.g. within Gnome), and we hope development will continue strong, serving Fedora and potentially other upstream communities. Looking at the bigger picture, some of the core requirements we have identified for Red Hat and community L10N going forward are: - Customizable Translation Workflows and integration with e.g. Content Authoring Workflows - Infrastructure easily adaptable to support new File formats and project types (e.g. OpenOffice formats, CMS formats, DTP formats, Wiki, Dita, Java formats), rather than relying on 'upstream' projects to fit a certain L10N infrastructure. - Managing the life-cycle of a translation project across releases and iterations - Translation Reuse and Terminology Management across projects and iterations - Job management, scoping, tracking and resourcing - Managing and/or Tracking upstream translation projects, pushing changes back upstream. These requirements require a system where the translation lifecycle would be managed within 'Translation Repositories' (similar to e.g. Pootle or Launchpad Translations), rather than directly through e.g. upstream version control systems. With a repository-based approach, we would be able to track and manage changes to a project on a translation unit level, and manage e.g. translation reuse and terminology within and across projects. We could still retain a link with upstream repositories (like with Transifex/Damned Lies). However, this would not be the 'core datamodel', but on a different layer through plug-ins. This link to external repositories could also go beyond traditional version control systems, communicating with external sources like wikis and CMSs. We have evaluated a number of existing open source L10N frameworks and systems, but haven't found any (yet) that stands out or satisfies our needs or requirements as a development platform. Technology-wise, we are aiming to develop a Java-based(!) system, using technology such as JBoss Seam, Hibernate, jBPM and RichFaces. A java based platform will enable us to make best use of internal expertise in these technologies, as well as making use of technology we are developing (as open source) through collaboration with partners in the L10N industry. We hope some of these requirements and ideas will excite some of you, and ultimately lead to something that can be of use to open source communities. While we have certain requirements and goals for this internally within the company, there is no need for this to be an 'internal' Red Hat project, and most of the requirements and needs overlap with those of community projects like Fedora. In other words, by developing this in collaboration with the community from a very early stage, we are more likely to develop something that may be of use to the greater community. Thoughts and comments, all sorts of comments, are very welcome. cheers, asgeir frimannsson (Senior Software Engineer, I18N Engineering, Red Hat APAC)

4 9

app2 disk space
by Mike McGrath 21 Sep '08

21 Sep '08

Some of you have seen the disk alerts on app2, Looking more closely it seems the host was not built with enough disk space (like was app1). So after the freeze is over I'll rebuild it. It does raise a point about storage for transifex though. Basically each host running transifex (or damned lies, I can't quite remember which) keeps a local copy of every scm as part of its usage. For performance reasons I don't think that will change but its something we'll want to figure out long term. I haven't done the research but in my brain it seems like running something like git/hg/svn/bzr over nfs will cause problems. On the other hand, these aren't upstream repos but local cache so I'm also curious what the harm would be, if they get borked one could just delete the cache and it would repopulate. Thoughts? -Mike

5 5

Re: Fedora 10 Beta Release Planning Meeting
by Rahul Sundaram 19 Sep '08

19 Sep '08

Josh Boyer wrote: > On Sat, Sep 20, 2008 at 12:15:46AM +0530, Rahul Sundaram wrote: >> I have. My point still stands. If a new Fedora meeting is being held, it >> should not planned and organized as a secret. It should be announced > > So those Red Hat budget meetings that control the financial fate of Fedora... > those should be planned in public too right? No but the meeting minutes are not published publicly for such meetings either. The Fedora specific budget details are however published at https://fedoraproject.org/wiki/Accounting https://fedoraproject.org/wiki/CommunityArchitecture/Expenses This I consider to be a very good thing. Or the meetings that were held > to discuss the outage crisis? Here there might have been reasons for secrecy and it would better to let people know that such a meeting is being held even then. I don't see any such requirement for release planning. Should Paul publish his work calendar, given > that he's the Fedora project lead and has Fedora meetings all the time? Since all the other public Fedora meetings are well known, I don't need his work calender. > Seriously, everything is not black and white. You're making entirely too > big of a deal about this because you didn't get invited and someone pissed > in your lemondade Whether I get invited or not is irrelevant and I don't drink lemondate much ;-) I never said I should be invited even once. There is no need to be so petty. You might want to read about what I said completely. My issue is with the way in this meeting is organized and planned in secret and just that. Rahul

1 0

Re: Fedora 10 Beta Release Planning Meeting
by Rahul Sundaram 19 Sep '08

19 Sep '08

Josh Boyer wrote: > On Fri, Sep 19, 2008 at 10:13:32PM +0530, Rahul Sundaram wrote: >> Josh Boyer wrote: >>> On Fri, Sep 19, 2008 at 09:07:16PM +0530, Rahul Sundaram wrote: >>>>>> Wouldn't it be useful to invite more than person as part of the >>>>>> different groups? Currently it seems a number of people have not >>>>>> attended which leaves that group voice unheard. >>>>> I'm pretty sure the meeting was public. >>>> Was the invitation public? >>> I don't know. It doesn't really matter though. See the part of my email >>> that you cut off in your reply. >> I think it does matter. If new meetings for Fedora is being organized, >> invitations MUST be send publicly. I would want to know who is >> organizing it, where it was held, which date and time, whether others >> are attending etc. If it is a IRC meeting, where are the logs? You said >> you are sure the meeting was public. Why do you think that? > > I was wrong in thinking it was public. It was a phone call, not an IRC > meeting. Still does not matter, and you still apparently haven't read the > second part of my original reply. I have. My point still stands. If a new Fedora meeting is being held, it should not planned and organized as a secret. It should be announced ahead of time in public so interested people can participate. Even if you don't want others to participate, you can still organize it publicly. The fact that the people someone decided to pick on their own in private, can pull in others doesn't change this. Rahul

1 0

Re: Fedora 10 Beta Release Planning Meeting
by Jesse Keating 19 Sep '08

19 Sep '08

On Fri, 2008-09-19 at 12:53 -0400, Josh Boyer wrote: > I was wrong in thinking it was public. It was a phone call, not an IRC > meeting. Just for more fun and confusion, a meeting doesn't have to be on IRC for it to be "public". While this meeting wasn't announced on one of the major lists (for good reason), it was somewhat assumed that if a leader for a group couldn't make it that they would have somebody else go in their steed. Perhaps we'll call that out a bit more clearly next time. These people were sent mail multiple times leading up to the meeting so there was plenty of chance to find an alternative. The release readiness meetings are designed to be very high bandwith information exchanges between the various groups involved with doing releases. Obviously the later releases (preview, final) are more important and have more people involved than the earlier (alpha, beta) ones. It's an exchange of information that each group should already have through through and discussed in lower bandwith higher visibility meetings within each group. The readiness meeting is just like a mini mission control meeting to ensure things go off without a hitch and that those leading the groups and responsible for the functions are aware of whats going on. If nobody from your group showed up, I'm sorry, but we gave them ample time to find a replacement. You can be prepared as these meetings will come up for each major milestone during our development cycle. If you want, we can probably embed this information into the schedule pages that John creates, it's not like those aren't busy enough as they are (: -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating

1 0

Re: Fedora 10 Beta Release Planning Meeting
by Rahul Sundaram 19 Sep '08

19 Sep '08

Josh Boyer wrote: > On Fri, Sep 19, 2008 at 09:07:16PM +0530, Rahul Sundaram wrote: >>>> Wouldn't it be useful to invite more than person as part of the >>>> different groups? Currently it seems a number of people have not >>>> attended which leaves that group voice unheard. >>> I'm pretty sure the meeting was public. >> Was the invitation public? > > I don't know. It doesn't really matter though. See the part of my email > that you cut off in your reply. I think it does matter. If new meetings for Fedora is being organized, invitations MUST be send publicly. I would want to know who is organizing it, where it was held, which date and time, whether others are attending etc. If it is a IRC meeting, where are the logs? You said you are sure the meeting was public. Why do you think that? Rahul

1 0

Change request, log compression
by Mike McGrath 19 Sep '08

19 Sep '08

I'd like to add the 'compress' term to logrotate for http logs on the app servers. App2 is low on disk space right now and it would free up some space. -Mike

4 5

Fedora 10 Beta Release Planning Meeting
by John Poelstra 19 Sep '08

19 Sep '08

Fedora 10 Beta Release Planning Meeting 2008-09-17 == Invitees == Jonathan Roberts -- Marketing Karsten Wade -- Docs Jesse Keating -- Rel Eng (present) Paul Frields -- FPL (present) Spot Callaway -- FEM (present) John Poelstra -- Organizer (present) Mike McGrath -- Infrastructure (present) Dimitris Glezos -- Translation (present) Máirín Duffy -- Art (present) Will Woods -- QA James Laska -- QA (present) Ricky Zhou -- Websites (present) Bill Nottingham -- Development == Meeting Goals == o not intended to be a lengthy meeting o opportunity to quickly go around the "virtual room" to make sure we are all ready for Beta release day o make it easier for us to communicate in real-time across teams on the telephone o John Poelstra also trying to flush out the taskjuggler schedules to reflect the reality of what needs to get done so that future schedules are tighter o Invited a representative from each Fedora group with a role in getting the release out the door == Meeting Notes == === Release Engineering === o Release Engineering is expecting the following on release day 1) announcement with link to page with information about the beta 2) landing zone to drive all the users to --Mike M notes that this page http://get.fedoraproject.org should be used going forward for all releases o All tasks and content for the beta release (for all teams) should be ready the day before release--Monday, September 22, 2008 --need to do a dry run or validate that things (links, content, etc.) are in working order before announcing --meet 1 hour before release and try things out o Future release cycles could be smoother with a buffer between feature freeze and beta freeze --considering during Fedora 11 planning o Consider proposing a set of earlier dates for core packages in the distro to solidify the release earlier. For example: anaconda, yum, rpm, etc. o Consider moving feature freeze to one week before beta freeze so that features don't crash land on the beta freeze date === Documentation === o docs team responsible for content of releases notes o single page release notes --do not get translated o will assist release engineering to help with release announcement o Docs team will need more community participation and help to get the installation guide ready --past contributors will not be able to be as involved this release cycle --waiting for git repo to get online; Mike will help coordinate as needed o https://fedoraproject.org/wiki/Releases/10/Beta/ReleaseNotes === Art Team === o Art team to create banner to point to beta o Art team is still deciding on a final theme and content will not be ready in time to package for the beta --in the future we will target getting new artwork ready and packaged by feature freeze o Art team will work on a count-down timer to be ready at the release of the Preview Release ==== Web Sites Team === o websites team responsible for presentation of get.fedoraproject.org === Marketing & PR === o Paul is working with RHT PR to create press release blog o Also need to do coordination with Jonathan Roberts and the Fedora marketing team === Translation === o Translation deadline pulled in by one week to provide one week between the translation deadline and the final development freeze o Translation of the release notes starts with the preview release o Dimitris is trying to get Red Hat to commit internal resources to help translate release notes for languages that RHT supports --15 languages now supported by Fedora could increase to 30 or 35 o Considered how we could make sure that translations are repacked before before final devel freeze? --use tracker bugs? --Spot is willing to help patrol and look for things that are missing == Next Meeting == o Prepare for Preview Release o Wednesday, October 22, 2008 o 17:00 UTC

4 5

Re: Fedora 10 Beta Release Planning Meeting
by Rahul Sundaram 19 Sep '08

19 Sep '08

Josh Boyer wrote: > On Thu, Sep 18, 2008 at 06:20:06PM +0530, Rahul Sundaram wrote: >> John Poelstra wrote: >>> Fedora 10 Beta Release Planning Meeting >>> 2008-09-17 >>> >>> == Invitees == >>> Jonathan Roberts -- Marketing >>> Karsten Wade -- Docs >>> Jesse Keating -- Rel Eng (present) >>> Paul Frields -- FPL (present) >>> Spot Callaway -- FEM (present) >>> John Poelstra -- Organizer (present) >>> Mike McGrath -- Infrastructure (present) >>> Dimitris Glezos -- Translation (present) >>> Máirín Duffy -- Art (present) >>> Will Woods -- QA >>> James Laska -- QA (present) >>> Ricky Zhou -- Websites (present) >>> Bill Nottingham -- Development >> Wouldn't it be useful to invite more than person as part of the >> different groups? Currently it seems a number of people have not >> attended which leaves that group voice unheard. > > I'm pretty sure the meeting was public. Was the invitation public? Rahul

1 0

Infrastructure update notice
by Paul W. Frields 19 Sep '08

19 Sep '08

http://www.redhat.com/archives/fedora-announce-list/2008-September/msg00009… This notice was slightly delayed for a number of reasons, so I apologize. The return of all our services was more contemporaneous when I drafted it. I wanted to make sure there was a canonical record that we are back to all systems go for infrastructure, websites, and so forth. -- Paul W. Frields gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://paul.frields.org/ - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

1 0

[Fwd: bugzilla.redhat.com, hardware.redhat.com Planned Outage | 09-17-2008 - 1700 EDT (-0400)]
by John Poelstra 17 Sep '08

17 Sep '08

-------- Original Message -------- Subject: bugzilla.redhat.com, hardware.redhat.com Planned Outage | 09-17-2008 - 1700 EDT (-0400) Date: Wed, 17 Sep 2008 15:00:29 -0400 From: Matthew Schick O U T A G E R E Q U E S T F O R M ===================================== Severity: Severity One (Urgent) Scheduled Date: 09-17-2008 Scheduled Time: 1700 EDT (-0400) Estimated Time Required: 30 minutes Performed By: Engineering Operations People/Groups Impacted: Bugzilla users Site/Services Affected: bugzilla.redhat.com, hardware.redhat.com Impact: Bugzilla and Hardware will be offline briefly. Description: New perl package will be installed to address performance concerns. Mysql servers will be upgraded for bugfixes.

1 0

Change Request: Fix /wikiold/ (r/o moin)
by Ricky Zhou 16 Sep '08

16 Sep '08

Hi, Rahul reported that /wikiold/ is currently broken, so it looks like we missed some stuff during the rebuild. I wasn't sure if this is considered under the change freeze, so here's the puppet patch I'd like to apply (also, can somebody confirm that the mount for /srv/web/wiki is correct?): Thanks, Ricky From 7a4f9b64fe100dd4eb7de9ad57c98338bf0dd7f7 Mon Sep 17 00:00:00 2001 From: Ricky Zhou <ricky(a)fedoraproject.org> Date: Tue, 16 Sep 2008 03:56:43 +0000 Subject: [PATCH] Fix up old moin setup. --- configs/web/applications/moin.wsgi | 11 +++++++++-- manifests/services/fedoraproject.org.pp | 23 ++++++++++++++--------- 2 files changed, 23 insertions(+), 11 deletions(-) diff --git a/configs/web/applications/moin.wsgi b/configs/web/applications/moin.wsgi index 5bd3772..bfd0d86 100644 --- a/configs/web/applications/moin.wsgi +++ b/configs/web/applications/moin.wsgi @@ -1,7 +1,14 @@ -#!/usr/bin/python import sys sys.path.insert(0, '/srv/web/wiki') -from MoinMoin.server.wsgi import moinmoinApp +import logging + +from MoinMoin.server.server_wsgi import WsgiConfig, moinmoinApp + +class Config(WsgiConfig): + logPath = 'moin.log' + +config = Config() application = moinmoinApp + diff --git a/manifests/services/fedoraproject.org.pp b/manifests/services/fedoraproject.org.pp index 5981bf8..80bf50e 100644 --- a/manifests/services/fedoraproject.org.pp +++ b/manifests/services/fedoraproject.org.pp @@ -1,14 +1,5 @@ # Config files for http://fedoraproject.org/ -class fedoraproject-moin-slave { - symlink { '/srv/web/wiki/': - ensure => "/fedora/wiki/" - } - package { 'PyXML': - ensure => present, - } -} - class fedoraproject-moin inherits httpd { include mod_wsgi-package @@ -28,6 +19,20 @@ class fedoraproject-moin inherits httpd { package { 'PyXML': ensure => present, } + + folder { '/srv/web/wiki/': + source => 'blank/', + require => Folder['/srv/web/'], + } + + mount { "/srv/web/wiki": + device => "ntap-fedora1.fedora.phx.redhat.com:/vol/fedora/app/wiki", + fstype => "nfs", + ensure => "mounted", + options => "defaults", + atboot => true + } + } class fedoraproject-proxy inherits httpd { -- 1.5.5.1

3 2

About the recent invasion
by Henrique Junior 16 Sep '08

16 Sep '08

Hello, guys I'm sorry if this list is not the right place to post this question but I can't figure a better place. As a Fedora ambassador (in Brazil) I've been asked by a lot of people about the recent invasion in our servers. The question I've been asked yesterday was “how it happened?” I'd like to explain here exactly what happened to make our users more comfortable and confident. Please excuse my bad english. Thanks Henrique "LonelySpooky" Junior ________________________________ "In a world without walls and fences, who needs windows and gates?!" Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com. http://br.new.mail.yahoo.com/addresses

4 5

sb2/3 reboot again and weird newkey.newkey directories
by Ricky Zhou 16 Sep '08

16 Sep '08

sb2/3 randomly rebooted again tonight (the nagios alert about ns1). Sorry, but I never got around to sending a ticket about it. I'll try to get a list of dates/times where this happened together soon. Also, just so this doesn't get lost in the backlog: 09:03:57 < yaneti> http://download.fedora.redhat.com/pub/fedora/linux/updates/8/ 09:04:04 < yaneti> newkey.newkey ? Weird stuff. Thanks, Ricky

3 2

modules/plague/templates/sync-committers.sh.erb Change
by Ricky Zhou 13 Sep '08

13 Sep '08

Sorry, I completely forgot we were in a change freeze now. I just pushed a change (diff below) to make the sync-committers script not fail. Should I revert this, or does it look all right? diff --git a/modules/plague/templates/sync-committers.sh.erb b/modules/plague/templates/sync-committers.sh.erb index d3c8e63..4e51d44 100644 --- a/modules/plague/templates/sync-committers.sh.erb +++ b/modules/plague/templates/sync-committers.sh.erb @@ -12,7 +12,7 @@ fi for user in `cat ${users}|cut -d, -f2` do - plague-user-manager.py ${userdb} add $user own_jobs > $cruft 2>&1 + /usr/bin/plague-user-manager ${userdb} add $user own_jobs > $cruft 2>&1 if [ $? != 0 ]; then if ! grep -qi 'already exists' $cruft; then echo "Error adding user $user was:" Thanks, Ricky

2 1

Outage Notification - 2008-09-13 01:00 UTC
by Dennis Gilmore 13 Sep '08

13 Sep '08

There will be an outage starting at Y2008-09-13 01:00 UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2008-09-13 01:00 UTC' Affected Services: Buildsystem Unaffected Services: Websites Database CVS / Source Control DNS Mail Torrent Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/830 Reason for Outage: update koji to 1.2.6. it will enable us to turn garbage collection back on. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage.

1 2

Emergency update to kojiweb.conf
by Dennis Gilmore 13 Sep '08

13 Sep '08

I just made a minor change to kojiweb.conf RewriteRule ^/koji/login$ https://koji.fedoraproject.org/koji/login koji-1.2.6 only allows you to use ssl when logged in. by rewriting the login you end up using https without the change a user would need to go to https before trying to login or they would get a traceback trying to login. Dennis

1 0

[Fwd: download.fedoraproject.org mirrors problem]
by Ignacio Vazquez-Abrams 13 Sep '08

13 Sep '08

For your consideration. -------- Forwarded Message -------- From: George Billios <gbillios(a)gmail.com> To: webmaster(a)fedoraproject.org Subject: download.fedoraproject.org mirrors problem Date: Sat, 13 Sep 2008 09:12:29 +0300 Hello, During the last week I noticed that when trying to access directly download.fedoraproject.org I get automatically redirected to ftp.ntua.gr mirror of fedoraproject, probably accordingly to my ip. The problem is that this mirror is not updated, for example the repo for fedora 9 with the new key was only updated yesterday and as you can see here: http://ftp.ntua.gr/pub/linux/fedora/linux/updates/testing/ there is nothing under testing. Therefore it would be best to disable this redirecting until the repo is up to date. Thank you

1 0

Res: About the recent invasion
by Henrique Junior 12 Sep '08

12 Sep '08

Thank you, paul. I'll spread the announcement. Henrique "LonelySpooky" Junior ________________________________ "In a world without walls and fences, who needs windows and gates?!" ----- Mensagem original ---- > De: Paul W. Frields <stickster(a)gmail.com> > Para: Fedora Infrastructure <fedora-infrastructure-list(a)redhat.com> > Enviadas: Sexta-feira, 12 de Setembro de 2008 13:59:43 > Assunto: Re: About the recent invasion > > On Fri, 2008-09-12 at 09:40 -0700, Henrique Junior wrote: > > Hello, guys > > I'm sorry if this list > > is not the right place to post this question but I can't figure a > > better place. > > As a Fedora ambassador > > (in Brazil) I've been asked by a lot of people about the recent > > invasion in our servers. The question I've been asked yesterday was > > “how it happened?” > > I'd like to explain > > here exactly what happened to make our users more comfortable and confident. > > Please excuse my bad english. > > Hello Henrique. You can refer to the following announcement for the > most recent update: > http://www.redhat.com/archives/fedora-announce-list/2008-August/msg00012.ht… > > This is an ongoing investigation, and we'll provide another update as > soon as more information is available. > > -- > Paul W.. Frields > gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 > http://paul.frields.org/ - - http://pfrields.fedorapeople.org/ > irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug Novos endereços, o Yahoo! que você conhece.. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com. http://br.new.mail.yahoo.com/addresses

1 0

Beta Freeze
by Mike McGrath 12 Sep '08

12 Sep '08

Hey guys the beta freeze is going into affect tomorrow. It will end on 2008-09-24. This is the first pre-release freeze type we've had here's a link: http://fedoraproject.org/wiki/Infrastructure/SOP/Release#Change_Freeze Just a reminder... DON'T go making changes to machines that are on that list after tomorrow. -Mike

1 0

Meeting Log - 2008-09-11
by Ricky Zhou 11 Sep '08

11 Sep '08

20:00 -!- dgilmore changed the topic of #fedora-meeting to: infra meeting prep 20:00 * abadger1999 stretches 20:00 < dgilmore> hey all meetingtime 20:00 * ValHolla walks in 20:00 < SmootherFrOgZ> hello guys 20:00 < abadger1999> Hey ValHolla! 20:01 < abadger1999> Hello SmootherFrOgZ 20:01 < brothers> EHLO 20:01 < ValHolla> Hello 20:01 * wakko666 lurks. 20:01 < dgilmore> we will start with https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 20:01 < dgilmore> the tickets :) 20:01 * fchiulli is observing 20:01 * mmcgrath notes G said he won't be around and sends his best. 20:01 < dgilmore> .ticket 753 20:01 < zodbot> dgilmore: #753 (Mini-freeze for Fedora 10 beta) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/753 20:01 * ricky 20:01 * nokia3510 says hello 20:02 < dgilmore> we need to plan infra freeze for F-10 release 20:02 < dgilmore> and a mini one for beta 20:02 < dgilmore> f13: when is beta. what would you like frozen? 20:04 < dgilmore> mmcgrath: thanks :) 20:04 < f13> mmcgrath write up a chart that showed what would be frozen and what wouldn't. THe beta freeze is supposed to be today 20:04 -!- skvidal [n=nnnnnnsk@fedora/skvidal] has joined #fedora-meeting 20:04 < mmcgrath> f13: ah, k. I wasn't sure about the dates. given the fas issues that are going on, mind if we start the freeze tomorrow? 20:05 < dgilmore> f13: i have a koji outage scheduled for tomorrow 20:05 < dgilmore> i guess we should have talked about this last week 20:05 -!- kital [n=Joerg_Si@fedora/kital] has quit Remote closed the connection 20:06 < mmcgrath> yeah, its the first time we've really done a beta freeze, I wasn't sure when it was going to start either. 20:06 < mmcgrath> f13: so next time we'll be more careful, mind if we start the freeze on the 13th? 20:06 < f13> this beta is looking like a rolling wreck anyway, so sure, why not 20:06 < mmcgrath> hahahah 20:06 < dgilmore> f13: :) 20:06 < abadger1999> As long as it's rolling :-) 20:06 < mmcgrath> on the f13th 20:06 < f13> so it goes. 20:07 < dgilmore> so that means all changes need to be sent to infra list first and acked by one other? 20:07 < mmcgrath> yeah. I'll send a note out after the meeting similar to the last one. I should update the release SOP as well. 20:08 < dgilmore> do we roll from mini freeze to full freeze? or do we unfrezze once beta is out and frezze again for test and final? 20:09 < dgilmore> lets talk this over on the list 20:09 < dgilmore> .ticket 395 20:09 < zodbot> dgilmore: #395 (Audio Streaming of Fedora Board Conference Calls) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/395 20:09 < dgilmore> jcollie: ping 20:09 < jcollie> dgilmore: ping 20:09 < dgilmore> any update 20:09 < f13> I'm fine with unfreeze/refreeze later 20:09 < SmootherFrOgZ> dgilmore: mail says on Saturnday 13 for the outage 20:09 < dgilmore> SmootherFrOgZ: 1:00am UTC which is 8pm friday my time 20:10 < jcollie> dgilmore: nope, been busy with other stuff :( 20:10 < dgilmore> jcollie: :) it happens 20:10 -!- cassmodiah [n=cass(a)p54AB3DC0.dip.t-dialin.net] has quit Remote closed the connection 20:10 < SmootherFrOgZ> dgilmore: k 20:10 < dgilmore> .ticket 446 20:10 < zodbot> dgilmore: #446 (Possibility to add external links on spins page) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/446 20:10 < dgilmore> this is me 20:10 < dgilmore> i fail 20:10 < dgilmore> .ticket 740 20:11 < zodbot> dgilmore: #740 (Loaning out system time to OLPC participants) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/740 20:11 < dgilmore> so I got from OLPC what it is they wanted 20:11 < dgilmore> as i suspected its a machine where people can log in. have cvs, koji, mock, etc access 20:12 < dgilmore> so they can do test builds. package management etc 20:12 -!- kital [n=Joerg_Si@fedora/kital] has joined #fedora-meeting 20:13 < dgilmore> there is quite a few people at OLPC who don't use fedora and are not familiar with fedora and how it works 20:13 < dgilmore> so part of what they want is also help to train people on how to work with fedora. how to maintain packages. 20:14 < dgilmore> mock is packaged and works on debian 20:14 < dgilmore> koji is not packaged 20:15 < dgilmore> so does anyone have ideas on what we can do to help 20:15 < nokia3510> I don't get it why they need a machine in this case. 20:15 < f13> I really don't understand why they can't supply this themselves 20:15 < f13> it's not very hard to put up a RHEL or Fedora host and install those packages 20:16 < f13> or is the thing they really want help with account management, in the form of FAS logins? 20:16 < dgilmore> nokia3510: so that people who dont use fedora can get access to it 20:16 < dgilmore> f13: some of it is fas 20:16 < dgilmore> and account management 20:17 < dgilmore> When i was there i was pushing to get fas in place. and i think it will happen over time 20:17 < f13> so tell them if they host a quadg5 system, we'll let them use fas to log in on it (: 20:18 < ValHolla> The reply from OLPC sounds to me like they are looking for a "tutor" ... someone to teach the non Fedora folks 20:18 < dgilmore> some of it is trying to get it closer to fedora. so that fedora developers could help train olpc's developers in fedora 20:18 < dgilmore> f13: :) 20:18 < f13> er, why does it matter where the box lives for that? 20:18 * f13 is seriously confused by the folks over there. 20:19 < dgilmore> it really doesnt 20:19 < dgilmore> they currently have a box they give out accounts on 20:19 < f13> and really, all they have to do is *ask* 20:19 < f13> but we've seen evidence of where that just doesn't happen 20:19 < dgilmore> but there are concerns its not as secure as it could be 20:19 * ValHolla wonders if it wouldn't be a good Idea to create #fedora-OLPC and try to have some of us in there for the OLPC to ask questions to 20:20 < dgilmore> ValHolla: it exists already 20:20 < dgilmore> well #fedora-olpc 20:21 < dgilmore> they are doing a better job of asking for help, than has been the case in the past 20:21 < ValHolla> dgilmore: ok, well a specific channel the OLPC folks know they can go to for a quick answer/tutorial on what they are doing? 20:21 < ValHolla> if they get stuck using mock, koji etc... 20:21 < wakko666> ValHolla: like #fedora, or #koji, or #fedora-admin? 20:21 < dgilmore> ValHolla: they usually come to me and I point them in the right direction. 20:22 < dgilmore> #fedora-devel 20:22 < dgilmore> there are quite a few olpc folks in #fedora-devel 20:22 < ValHolla> yes like those.... but there are so many different places to go. 20:22 < dgilmore> perhaps what we can do is help them with kickstart files, FAS help, etc 20:23 < dgilmore> help get an environment setup where they could rebuild the box that is used by people to test builds and play with things on a regular basis 20:24 -!- stickster_afk is now known as stickster 20:24 < dgilmore> help them to understand fas 20:24 < ValHolla> roughly how large an image do they use? will it all fit on a single dvd? 20:24 < dgilmore> and help get it implemented 20:24 < ValHolla> make them a "Live CD on steroids" 20:24 < dgilmore> ValHolla: image for what? 20:25 < ValHolla> kickstart image 20:25 * ValHolla is throwing solaris terms around ... sorry 20:25 < dgilmore> ValHolla: well it would need to be a developer spin of sorts 20:26 < nokia3510> I'd ask where Fedora-related stuff ends and strict OLPC particularities appear 20:26 < dgilmore> having fedora-packager gcc rpm-build etc installed 20:26 < nokia3510> because it seems to be a big overlap 20:26 -!- warren [n=warren@redhat/wombat/warren] has quit "Leaving" 20:26 < dgilmore> nokia3510: there are a few things in OLPC that can not be in fedora 20:26 < dgilmore> but most of it really should be built in fedora 20:27 -!- TopoMorto [n=TopoMort(a)151.61.153.118] has quit "Sto andando via" 20:27 < dgilmore> anyways. lets move on 20:27 < nokia3510> ok 20:28 < dgilmore> feel free to make comments in the ticket with ideas 20:28 -!- dgilmore changed the topic of #fedora-meeting to: Fedora Infrastructure - Open Floor 20:28 < dgilmore> anyone have anything they would like to bring up? 20:29 < SmootherFrOgZ> what about hosting request ? 20:29 < dgilmore> SmootherFrOgZ: which hosting request? 20:29 -!- LetoTo1 [n=paul(a)76-10-173-74.dsl.teksavvy.com] has joined #fedora-meeting 20:29 < dgilmore> SmootherFrOgZ: OLPC's? 20:29 < SmootherFrOgZ> nope 20:30 < SmootherFrOgZ> seth ask few weeks ago, that fp.o was looking for more hosting place 20:30 < dgilmore> skvidal: ^^^ 20:30 < skvidal> we're always looking for more hosting locations 20:31 < skvidal> we found some new space w/ibiblio 20:31 < skvidal> very kindly of them 20:31 < ricky> So torrent server there? 20:31 -!- dwmw2_gone is now known as dwmw2_HIO 20:31 < skvidal> ricky: xen host there 20:31 < skvidal> torrent will be on it 20:31 < SmootherFrOgZ> :), skvidal can you draft me details about what fp.o is looking for 20:31 < ricky> Niice 20:31 < skvidal> SmootherFrOgZ: mmcgrath has a better background in what's needed 20:31 < skvidal> ricky: iirc the box has been ordered 20:32 < SmootherFrOgZ> actually, our hosting sevice need more details to reply on that 20:32 < SmootherFrOgZ> service* 20:32 < ricky> Coolnsess 20:32 < skvidal> SmootherFrOgZ: but the gist is 1-2U +power +network 20:32 < ricky> **Coolness 20:32 < skvidal> SmootherFrOgZ: ideally, a serial console and the ability to power off/on the machine 20:32 < skvidal> SmootherFrOgZ: though we're willing to work with various amount of other things 20:32 < dgilmore> SmootherFrOgZ: or an easy way to get it handled 20:32 < ricky> Non-blocked ports are usually good 20:33 < SmootherFrOgZ> k 20:33 < skvidal> ricky: +1 :) 20:33 < dgilmore> disk is good to 20:33 < skvidal> dgilmore: well, normally we can provide the box 20:33 < skvidal> if we can get the space 20:33 < dgilmore> skvidal: true. 20:34 < dgilmore> we have some hosting that is rack space+power+network. we provide servers. we also have some where servers are provided 20:34 < dgilmore> depends on whats on offere 20:34 < dgilmore> offer 20:35 < skvidal> nod 20:35 < skvidal> SmootherFrOgZ: does that help? 20:36 -!- JSchmitt [n=s4504kr@fedora/JSchmitt] has quit "Konversation terminated!" 20:36 < SmootherFrOgZ> yep, thanks 20:37 < dgilmore> moving on 20:37 < abadger1999> I'm going to be at a memorial service tomorrow. Out all day. I'll probably be *very* spotty on the weekend as well with all the relatives in town. 20:37 -!- stickster is now known as stickster_afk 20:37 -!- stickster_afk is now known as stickster 20:37 < dgilmore> abadger1999: :) ok 20:37 * dgilmore will be updating koji to 1.2.6 20:38 -!- bzbot is now known as buggbot 20:38 < ricky> Any thoughts about upgrading postgres on db2? 20:38 < dgilmore> so we will need to look and see if we start hitting bugs. 20:38 < dgilmore> abadger1999: ^ 20:38 < dgilmore> ricky: im for it. 20:38 < abadger1999> I'd like to do it ASAP. 20:38 < SmootherFrOgZ> :) 20:38 < skvidal> abadger1999: :( 20:38 < abadger1999> mmcgrath: Thoughts on when we can do that? 20:38 < dgilmore> from my use of 8.3 its much better than 8.1 20:38 < ricky> No rush or anything, just wondering when it can go down (did we ever end up scheduling an outage for it?) 20:39 < ricky> dgilmore: That's really good to hear :-) 20:39 < mmcgrath> abadger1999: just need someone to do it. I can try to do it next week sometime 20:39 < SmootherFrOgZ> mmcgrath: i can give you a hand on that 20:39 < abadger1999> mmcgrath: k. I can help with the data manipulation. It's just dumping the data on one box and loading on another. 20:40 -!- mbacovsk_ [n=mbacovsk@nat/redhat/x-574ae97d3509588a] has joined #fedora-meeting 20:40 < mmcgrath> SmootherFrOgZ: thanks. I'm hoping it will be pretty straight forward but I'll make sure you can be around the night of. 20:40 < mmcgrath> we have a staging box now too so hopefully that will make things nice and clean :) 20:40 < ricky> abadger1999: Does it necessarily need to be on different boxes? 20:40 < abadger1999> ricky: Could be the same box even. 20:40 < nokia3510> can I help too ? 20:40 < ricky> Actually, I guess it could be good to test the postgres 8.3 manifest as well 20:40 < abadger1999> It's easier for reverting if they're separate boxes. 20:40 < ricky> And there's waay less data to transfer each time, I forgot 20:41 < SmootherFrOgZ> mmcgrath: no pb 20:41 < ricky> mmcgrath: So how will staging play into this? 20:42 < mmcgrath> ricky: we'll run it there first, if it works fine we'll run it in production 20:42 < ricky> Cool. 20:43 < ricky> Also, any update on the mod_wsgi mirrorlist? 20:43 < ricky> Is it close to ready? 20:43 < abadger1999> I think mdomsch just wanted people to test his new code. 20:43 -!- greenlion [n=greenlio(a)93-80-108-19.broadband.corbina.ru] has quit Remote closed the connection 20:44 < abadger1999> lmacken: If you're still around, did you get a chance to do that? 20:44 < ricky> Ah, so it's fully running on staging right now? 20:44 < ricky> Anybody have a URL handy? 20:44 < ricky> Ah, I guess http://mirrors.stg.fedoraproject.org/mirrorlist 20:45 < lmacken> abadger1999: nope, I haven't had time to do anything other than a basic sanity check on it 20:45 -!- mbacovsk__ [n=mbacovsk(a)okr2fw.topnet.cz] has quit Read error: 104 (Connection reset by peer) 20:46 < abadger1999> ricky: In the same vein, I heard you switched trac over to mod_wsgi? 20:46 < ricky> I haven't yet, actually 20:46 < abadger1999> Okay. 20:46 < ricky> I only did moin, but I want to look into trac soon 20:46 < abadger1999> Cool. 20:46 < dgilmore> mmcgrath: want to give an update on staging? 20:46 < ricky> I'll hopefully have a bit to look at it tonight or tomorrow night 20:46 < abadger1999> I want to convert the bzr web viewer to loggerhead... the new version is a wsgi app so when trac switches I try to deploy that. 20:47 < mmcgrath> dgilmore: sure, I can give a quick one. 20:47 < ricky> Nice 20:47 < abadger1999> (And then the code will actually be maintained upstream :-) 20:47 < mmcgrath> right now we have an app1.stg, app2.stg, proxy1.stg and db1.stg. The staging environment can't contact any production hardware except for /accounts/ and the infrastructure repo. 20:47 < mmcgrath> Matt is giving it a try for some actual work, I'm going to continue documenting it and will hold training at some point in the future (separate from the puppet training) 20:48 < dgilmore> :) 20:48 < lmacken> excellent 20:48 -!- mbacovsk__ [n=mbacovsk(a)okr2fw.topnet.cz] has joined #fedora-meeting 20:48 < dgilmore> when is puppet training again? 20:48 < mmcgrath> haven't schedule it yet. 20:48 < mmcgrath> its coming though 20:48 < dgilmore> ok 20:49 < dgilmore> If somoene wants to help with some things. I wantto design a way to load balance koji 20:49 < SmootherFrOgZ> dgilmore: go on 20:50 < ricky> As in kojihub? 20:50 * ricky wonders what kind of locking would need to happen 20:50 < dgilmore> ricky: locking is all in the db 20:50 < ricky> Oh, cool. 20:51 < dgilmore> SmootherFrOgZ: either setting up haproxy, pound, or something like that to do load balancing 20:51 -!- warren [n=warren@redhat/wombat/warren] has joined #fedora-meeting 20:51 < ricky> Oh, so it's 100% doing the balancing (as in, the code doesn't really need to change?) 20:51 < dgilmore> so we can do pretty much all maintainence without koji going down. coping with spikes. taking a box off to test something etc 20:52 < ricky> So would we build a separate proxy box just for koji and put it in front of koji1 and koji2 then? 20:52 < dgilmore> ricky: yeah. 20:52 < SmootherFrOgZ> dgilmore: interesting, haproxy is pretty good 20:52 < dgilmore> ricky: or pound would need two boxes 20:53 < ricky> So both pound and haproxy would handle SSL stuff easily, right? 20:53 < dgilmore> ricky: it should. we would need to test it first. 20:53 < ricky> Yeah. 20:54 < SmootherFrOgZ> yeah haproxy handle that well 20:54 < ricky> I wonder if we'd want koji + a builder in staging 20:54 < dgilmore> ricky: we should. 20:54 < ricky> But that sounds really complicated to setup 20:54 < dgilmore> i do my testing of koji on sparc.koji.fedoraproject.org 20:55 < dgilmore> mostly i want to remove the spof in the buildsys 20:55 < dgilmore> so i dont know how well haproxy would help 20:55 < ricky> Hm. 20:55 < dgilmore> since it would replace the spof 20:56 < dgilmore> pound having two boxes. one active, one passive would do it 20:56 < dgilmore> but it needs thought and testing 20:56 -!- wfp [n=wfp5p(a)viridian.itc.Virginia.EDU] has quit "Leaving" 20:56 < dgilmore> also something that I need help with is dogtag 20:57 < dgilmore> getting it to build in mock. so we can look at migrating the CA to it 20:57 < dgilmore> thats going to need alot of testing. 20:57 < ricky> Yeah, I'll try to ping you about that when I have some more itme 20:57 < ricky> **time 20:57 < mmcgrath> dgilmore: if we're going to load balance it we should probably just put them behind the hardware firewall we have at RH, if not maybe just do heartbeat. 20:57 < dgilmore> when we switch we have to do some funkyness to migrate from the existing CA 20:58 < dgilmore> mmcgrath: id be ok with either 20:58 < mmcgrath> I'm not sure we want to put koji behind our proxy farm thats shared with the other webservers, and doing a dedicated frontend would take our koji server from 1 to 4 (2 koji, 2 proxy) which we could do but I think its probably easier just to use the balancer thats there. 20:58 < dgilmore> mmcgrath: though id kinda prefer load balancing 20:58 * ValHolla wonders if you use pound the setup could be used for more then just koji 20:59 -!- mccann [n=jmccann(a)66.187.234.199] has quit "See ya" 20:59 < dgilmore> ValHolla: we try and keep buildsys seperate from everything else 20:59 < ricky> I guess we don't have very much control over the load balancer between fedoraproject.org and proxy1/2? 20:59 < mmcgrath> dgilmore: yeah, use the front end load balancer then. we'll have two backend servers and the balancer on front. 20:59 < mmcgrath> ricky: yeah its all by request 20:59 < dgilmore> mmcgrath: works for me 21:00 < mmcgrath> really though its been pretty solid so I haven't complained about it. 21:00 < ValHolla> digilmore: yeah I guess that is a good idea:/ 21:00 -!- ldimaggi___ [n=ldimaggi@nat/redhat/x-6a2313ae23860d09] has quit "Leaving" 21:00 < dgilmore> so thats some things for thought 21:00 < dgilmore> Anyone have anything else to talk about? 21:00 -!- mbacovsk_ [n=mbacovsk@nat/redhat/x-574ae97d3509588a] has quit Connection timed out 21:00 < dgilmore> if not ill wrap up in 30 21:01 < dgilmore> 20 21:01 < dgilmore> 10 21:01 -!- brothers [n=brothers(a)66-234-43-147.nyc.cable.nyct.net] has left #fedora-meeting [] 21:01 < dgilmore> --meeting wrap-- thanks all

1 0

Intrusion Detection System
by Luke Macken 11 Sep '08

11 Sep '08

Hey all, A couple of weeks ago I did an initial deployment of an Intrusion Detection System in our infrastructure. It utilizes the prelude stack, and is currently powered by auditd and prelude-lml events. Audit gives us a ridiculous amount of power with regarding to monitoring everything that happens on a system. Prelude-lml, out of the box using it's pcre plugin, is able to watch a large variety of service logs, including many things we are running (asterisk, mod_security, nagios, cacti, PAM, postfix, sendmail, selinux, shadowutils, sshd, sudo). Prewikka is the web-based frontend (https://admin.fedoraproject.org/prewikka) I created a new 'prelude' puppet module that contains the configuration for audit, auditsp-plugins, libprelude, prelude-manager, prewikka, prelude-correlator, and prelude-lml. Turning a node/servergroup into a sensor entails adding the following to your class definition: 'include prelude::sensor::audisp' My initial deployment entailed setting up the prelude-manager and correlator on a single box, and hooking up a single sensor (bastion). So, we're now at the point where we can fine tune our audit rules before we further deploy this infrastructure. Some things we want to consider: - Creating specific security policies for each servergroup - Define what files/directories/activities we want to monitor on which machines. - What events to we want to escalate ? I opened an infrastructure ticket to track this deployment here: https://fedorahosted.org/fedora-infrastructure/ticket/833 Suggestions, comments, and ideas are welcome. Cheers, luke

3 4

SELinux status update
by Luke Macken 11 Sep '08

11 Sep '08

Over the past few months, I've been working closley with Dan Walsh and Mike McGrath to solidify our SELinux deployment. We're not yet to the point where we can flip every system into enforcing mode, but we're getting close. We're at the point now where we can pretty much do everything we need to do via our puppet configuration, and we've created a handful of constructs that can be used to configure various aspects of SELinux, for example: == Setting custom context semanage_fcontext { '/var/tmp/l10n-data(/.*)?': type => 'httpd_sys_content_t' } == Toggling booleans selinux_bool { 'httpd_can_network_connect_db': bool => 'on' } == Allowing ports semanage_port { '8081-8089': type => 'http_port_t', proto => 'tcp' } == Deploying custom policy semodule { 'fedora': } I created a custom 'fedora' selinux module that is loaded on all systems (that are configured with 'include selinux'). This module exists to fix various issues custom to our environment, and to cover up minor annoyances such as leaky file descriptors. So, now it's just a matter of hunting down the existing issues, and fixing them in puppet or in the SELinux policy. I've been keeping our infrastructure ahead of the RHEL5 selinux-policy, as Dan has fixed a lot of our issues in his rpms. I threw together a basic SOP for our SELinux configuration here: https://fedoraproject.org/wiki/Infrastructure/SOP/SELinux You can keep up to date on our SELinux deployment status here: https://fedorahosted.org/fedora-infrastructure/ticket/230 Cheers, luke

2 1

Orientation page
by Mike McGrath 10 Sep '08

10 Sep '08

Hey guys I threw together a standard orientation page for new members. Take a look and let me know what pieces you think are missing and fix whatever problems you find. http://fedoraproject.org/wiki/Infrastructure/SOP/Orientation -Mike

3 2

Removal of old projects from fedorahosted.
by susmit shannigrahi 10 Sep '08

10 Sep '08

Hi, This is w.r.t to ticket #714[1]. As explained by mmcgrath, Fedora has a policy to remove _any_ hosted projects that are not altered or updated for last six months. Here is the list of projects, which falls into this category and they will soon be removed. -------------------------------------------------------------------------------------------------------------------- These directories have not been altered for 6 months /srv/svn/hardlink group: svnhardlink /srv/svn/package-jitsu group: svnpackage-jitsu /srv/svn/repoview group: svnrepoview /srv/svn/ols group: svnols /srv/svn/setarch group: svnsetarch /srv/svn/authd group: svnauthd /srv/svn/system-config-keyboard.old group: svnsystem-config-keyboard /srv/hg/camelus group: hgcamelus /srv/hg/passwd group: hgpasswd /srv/hg/bodhi.old group: gitbodhi /srv/hg/guest-account group: hgguest-account /srv/hg/timeconfig group: hgtimeconfig /srv/hg/LHCP group: hgLHCP /srv/hg/virt-manager group: hgvirt-manager /srv/hg/pam-redhat group: hgpam-redhat /srv/hg/tmpwatch group: hgtmpwatch /srv/git/splatbind.git group: gitsplatbind /srv/git/system-config-securitylevel.git group: gitsystem-config-securitylevel If you have any update with respect to this, and don't want any/some project(s) be removed, please let us know. Thanks. [1]https://fedorahosted.org/fedora-infrastructure/ticket/714 -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit =============================================

12 33

Environments Doc
by Mike McGrath 09 Sep '08

09 Sep '08

So I'm slowly getting more architecture docs put together. This is now in our repo: http://mmcgrath.fedorapeople.org/Environments.pdf When we're in a freeze or a pre-freeze here's the rules. If the host is listen in the $FREEZE_TYPE list. Then its frozen. You'll notice that, for example, app[1-5] are listed in both the normal full freeze as well as the pre-release freeze. That's because we have applications that exist in each environment. Until we move those services somewhere else. Those servers are frozen during prefreezes. The actual environment names are: * Buildsystem * Distribution * Support * Virtualization * Staging * Testing * Value Added -Mike

2 3

More puppet training!
by Mike McGrath 08 Sep '08

08 Sep '08

So I'm going to hold a couple more training seminars for Puppet in Fedora's Infrastructure. I was hoping you guys could also throw some questions together so i make sure I don't miss anything. -Mike

7 9

Last week
by Mike McGrath 08 Sep '08

08 Sep '08

Strange week last week, many of you noticed a bunch of nagios outages so I thought I'd send a roundup of what happened. 1) The big one was what seems to be a corrupt database table. For some reason running a vacuum on a table (which was only 66M large) was taking a long time and even after it would finish the disks would thrash for sometimes 10 minutes after. This caused outages of lots of our systems like the account system, to which other systems depend. The job was hourly so thats why it kept happening. We were able to reproduce this on another host and never quite figured out what was going on but a dump, drop, restore fixed the issue and so far we haven't had time to revisit what was going on, just that it hasn't happened since. 2) Strange network issues towards the end of the week. Seems our round time to server beach went up causing nagios to flag some hosts as dead. I've also not yet had time to look into this. The network seems and I don't think we're seeing any functional issues from it but it was different. 3) pkgdb's home page started taking longer to load causing our balancer to start flagging it dead causing it to throw 503's. We only recently moved it to haproxy so this could be a normal behavior that we just didn't see. I've moved response time of the front page up to 5 seconds from 2. -Mike

2 2

Introduction
by TJ Davis 08 Sep '08

08 Sep '08

Hi All, I have been watching this email list for awhile and decided to finally introduce myself. I am TJ Davis from West Texas but I currently live in Belize. I am an independent software consultant for several universities. I mostly do database consulting on MSSQL but have about 10 years of experience with LAMP and Linux administration. I have not managed enterprise level systems but have managed 6 Linux servers doing various tasks for a university for 10 years. I also have a good amount of experience with OpenVPN as well as SpamAssassin/Amavis/Maia/Clamv. I will start reading over tickets soon and try to pick some once I have been accepted. But, in the mean time, if anyone knows where I might fit in best give me a shout. I will be on #fedora-admin as tjdavisbz as much as possible. Tj

2 2

archives on secondary1
by Matt Domsch 06 Sep '08

06 Sep '08

quick sanity check. archives.fp.o is on secondary1.fp.o, right? There are 2 separate rsyncd.conf files in puppet, one for archives, one for secondary. Given they land at the same place on the same machine, only the one for secondary is actually in effect. If they're going to be on the same machine, we need to merge them. yes? Thanks, Matt -- Matt Domsch Linux Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux

2 2

Test fedora-release packages for F8 and F9
by Warren Togami 06 Sep '08

06 Sep '08

http://togami.com/~warren/fedora/fedora-release-8-5.transitiontest1.noarch.… http://togami.com/~warren/fedora/fedora-release-9-3.transitiontest1.noarch.… Test fedora-release packages pointing at the newkey update repos. Attached are sha1sums GPG clearsigned by my personal GPG keyid 54A2ACF1. Some cursory tests have indicated that no typos are in these new .repo files. Please test these and report if you see any errors. The F9 version seems to work fine with yum, but unfortunately it exposes one or more nasty bugs in PackageKit so we likely need more work before updates can go live. http://lists.fedoraproject.org/pipermail/rel-eng/2008-September/001702.html http://lists.fedoraproject.org/pipermail/rel-eng/2008-September/001704.html Discussion ensues about our options for the F9 PackageKit problem... http://lists.fedoraproject.org/pipermail/rel-eng/2008-August/001627.html These packages are drafts the first fedora-release of the newrepo process. After this has settled in we will push another fedora-release in the newrepo signed by the newkey in order to complete the transition and eliminate the old repos from the user's system. Warren Togami wtogami(a)redhat.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 b2938496b2f57b0b8340c436aac4064802d5b9c6 fedora-release-8-5.transitiontest1.noarch.rpm bf9338d4f04dcdf733946ded9d375f7631383187 fedora-release-8-5.transitiontest1.src.rpm d9d26a1061079bf4580a892d668ae569cafe8081 fedora-release-9-3.transitiontest1.noarch.rpm f01c1749470a7e296408ab6338857e326fe6457e fedora-release-9-3.transitiontest1.src.rpm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjCMVcACgkQa93+jlSirPFLrQCfbAgUaumBGWy5YfDOc8Sbn6l3 W6MAnj501zCkRN3Jb+JM0+YdAQsHjfFr =ftuj -----END PGP SIGNATURE-----

1 0

need approval
by sujan sunil pilli 06 Sep '08

06 Sep '08

1 0

staging environment discussion
by Mike McGrath 06 Sep '08

06 Sep '08

So as many of you have seen in the commits lists, the staging environment is coming along and getting built. I've hit a policy issue and so I thought instead of just doing this in a black hole. I'd discuss it. The way I see it there are two ways to do staging environments. For those of you unfamiliar with staging the general idea is to have an environment as close to production as feasible. 1) use identical configs with only minor changes and use /etc/hosts to fake things to point where you need them. Not always possible but generally good where you can do it. 2) use different configs in production and staging. The differences being able to redirect things, using different usernames, passwords, hostnames, etc. Each has pros and cons. Right now I'd like to do 1) but I don't think its possible. 2) is going to require a lot of focus. For example... we won't be able to just git merge from staging to production as we could with 1). Security's only an issue in that we don't want people making changes to production data from staging and vise versa. The same people will have the same access to both of these environments without exception. I'm going to continue to think about this. I've had staging environments in the past. Both went with option 2). But still. I'd like to hold this discussion so discuss. -Mike

3 3

Interested in doing some fedora cvs work
by Huzaifa Sidhpurwala 05 Sep '08

05 Sep '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, Now that i am in the sysadmin group. I have taken a thorough look at all the other FIGS which are listed. I have also taken a look at the kind of work the people in the FIGS do and i would like to get involved with the cvs group. I have a good amount of technical experience with cvs and svn, so that should not be a barrier. Can Mike, Bill or Dennis, sponsor me to this group please? Thanks a lot. - -- Regards, Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas) GnuPG Fingerprint: 3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFIwNnkzHDc8tpb2uURApOKAJ95P7ND8Wt68Xm+1FuPd45gIYLT3ACePwEe UotTlcg06khaN2pjWpK/isI= =eHs6 -----END PGP SIGNATURE-----

1 0

(no subject)
by sujan sunil pilli 05 Sep '08

05 Sep '08

1 0

need approval
by Amitakhya Phukan 05 Sep '08

05 Sep '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am interested in joining the Fedora Infrastructure team. I am interested in general sysadmin, sysadmin-test and sysadmin-hosted groups. Can anyone sponsor me ? Regards, Amit. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAki/ejgACgkQisV6fTFpwA2q6gCfSKBiIHW7DdQIxykaLuXGjc7c Q/AAnjgT8MhfNGL2BPUuPYWQUQkxhwen =oDSZ -----END PGP SIGNATURE-----

3 8

a quick self-introduction
by Bret McMillan 03 Sep '08

03 Sep '08

Hey folks, I've been lurking in the infrastructure area for awhile, but just recently joined the list. jonrob & mmcgrath have been kind enough to work w/ me on blog stuff for news.fp.org, etc. I've been an RH employee for a number of years, mostly in RHN engineering, but now recently in IT working on collaborative applications. I'd classify myself as a marginal SA, but always willing to learn and help out :) Current interests: * blogs (wordpress-mu) * wikis * mobile devices * CDN's * opening RH's IT tooling & methods to be more open and in alignment w/ what the community is doing cheers, --Bret

2 2

Paul VanGundy - Introduction
by Paul VanGundy 03 Sep '08

03 Sep '08

Hello List! :) My name is Paul VanGundy and this is my introduction to the list. No worries as I will make this short and sweet and if there are questions or people want to know more about me they can email me or the list. I have eight years experience in Linux systems administration in many different parallels (government, education, enterprise) with which I am currently serving in enterprise. Nutshelling, I have worked with many different flavors of Linux but mainly Red Hat, CentOS and Fedora in the enterprise market. I have done everything from managing large email farms running on Red Hat (my stints at WebEx and Cisco), running CentOS (both physical and virtual) in development environments (WebEx, Cisco, Bradford Networks) to helping school districts reach there educational potentional by using open source projects such as LTSP (of which I have written a pdf doc that is used world over but a little outdated... see wiki.ltsp.org) I have many other skills, abilities and experience that I will not list as I want to keep this short and sweet. I do welcome questions and am very eager to help the Fedora Project and utilize my skills to give back to those that have given to me. I look forward to working with all of you! Cheers!! /paul

2 1

New Key Repo Locations v2
by Warren Togami 02 Sep '08

02 Sep '08

2 1

Can someone approve me?
by Huzaifa Sidhpurwala 02 Sep '08

02 Sep '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I have been hanging around the infrastructure team for a year now, I am also your friendly neighborhood beat writer for FWN, can some one please approve me in the sysadmin group? Thanks. - -- Regards, Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas) GnuPG Fingerprint: 3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFIvR0IzHDc8tpb2uURAv+mAJ9Ayl0xFDlQBjpM0JkqxgTNPhjO/wCeKU3n /YuFbWAUloyCsc7crWiLzn4= =czHm -----END PGP SIGNATURE-----

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure September 2008