infrastructure July 2009

infrastructure@lists.fedoraproject.org

42 participants
66 discussions

hi, i newly joined fedora infrastructure group
by p sena 17 Sep '10

17 Sep '10

Hi, I am new to the fedora infrastructure group. I am going throug few of the links in the site to get a feel of the work. I have submitted my .ssh_rsa_key.pub from the site. I think I will get some intimation on this. Please someone can let me know further proceedings from here onwards. Cheers. Regards & Thanks Prabir Senapati mailto: senapati2001(a)yahoo.com

3 5

Ok. Looks like this one _may_ fulfill our calendering needs. Testing required.
by susmit shannigrahi 29 Jan '10

29 Jan '10

Hi, I am quite "frightened" to take up this topic again and again lest you all be bored. But interestingly, this one http://publictest15.fedoraproject.org/calender/ can fulfill all our requisites. But, I don't use a calender on my phone, so I never used remote export/import etc. And no surprise that I shall not be able to test it fully. So, if someone who is familiar with these help me out, it will be nice. Thanks. [1] https://fedorahosted.org/fedora-infrastructure/ticket/1197 -- Regards, Susmit. ============================================= ssh 0x86DD170A http://www.fedoraproject.org/wiki/user:susmit =============================================

11 40

hosts for rawhide build chroots - different rpm versions?
by Axel Thimm 05 Oct '09

05 Oct '09

Hi, AFAIK the build hosts are RHEL5 (or maybe F10 by now?). At any rate the rpm used in rawhide is quite different than the ones from the hosts, how has this been solved in the build hosts? Has the hosting OS upgraded its rpm to be compatible to all hosted chroots? Or is the rpm within the chroot used? I'm asking in a double context: First I'd like to understand if smart can properly handle chroots of rawhide/F11 on F10/RHEL5 hosts. Anders Björklund (in the Cc, please keep him there on replies) has put a great deal of effort to have smart working on F10 and F11, and a smart version for managing F11 and later chroots on F10 or earlier would be great. And second I'd like to know how to setup a build environment for F11 for getting some ATrpms packages out. Thanks! -- Axel.Thimm at ATrpms.net

3 5

Hello, My intro
by Chris Johnson 18 Sep '09

18 Sep '09

Hi all, I've been lurking on the mailing list for a while and I finally registered for my fedora account today (username: chrisj) I'm interested in helping out as time permits. I got on irc once (lurking again) and haven't really logged in since. I'll try to make a few meetings after the holidays I'm planning to get my personal test systems setup soon. I just moved and still getting things straight at home. Bought a 750GB drive last night and will be installing F10 over the weekend. I had been running the U... distro and it's time to get back to the fedora/RH rpm way of doing things :-) I've used RedHat since before Fedora existed (I think 6 was the first one). Started as a hobbyist, 2 years. Then got a job as an admin and have been doing Linux admin and Cisco networks for the last 5 years. My current employer is a Win shop so I just get to run the DNS, email, and network, but the network is 50 remote offices and 3 different data centers in the midwest. I don't mind the Windows too much and can find my way around them, it's also kinda fun to get the Linux and MS products to play nice together. I've worked with a lot of different linux and OSS software products including: postfix, openldap, apache, bind, samba, mailman, pam, built some custom rpm's, etc. I use RHEL mostly at work and some fedora and Cent for testing (some suse, deb, and slackware in the past). I used to do lots of security firewall apliances with various linux distros (I was a big fan of LRP when it would fit on a floppy), most of this is now done with Cisco in my world. I can shell script pretty well and I've written several perl scripts in the last few years (dabbled in php but not enough to know it well). I've always been interested in python but don't have much if any exp with it. I also don't have much experience with SQL/DB or source control. I was looking at the FIGs and would be interested in the base sysadmin and sysadmin-noc for now while I figure out where everything is and what it does. I'm also interested in more info on the sysadmin-tools and sysadmin-web FIG. So, next just apply for the FIGs, keep lurking, ask some questions, show up for IRC meetings? Thanks all, -- Chris Johnson ++++++++++ j.chris.johnson(a)gmail.com ++++++++++++++++++++

2 2

memcached opinions
by Mike McGrath 10 Sep '09

10 Sep '09

I'm not sure if we have any memcached experience on the list but I thought I'd ask. Can anyone explain this: http://pastebin.ca/1481219 Notice how memcached1 has a much higher hit rate and memcached2 has a much lower hit rate? -Mike

4 7

Bugzilla bot account / Fedora mail alias
by Till Maas 07 Aug '09

07 Aug '09

Hiyas, I will eventually want to use a bugzilla account for a certain service[0]. To make it easier for someone else to reclaim this account in case i vanish, I would like to use a Fedora mail alias for this. Is there some type of bot account type in FAS that I can use to create the additional mail alias or some other procedure for this? Regards Till [0] https://fedoraproject.org/wiki/Using_FEver_to_track_upstream_changes

7 19

Meeting Log - 2009-07-30
by Ricky Zhou 30 Jul '09

30 Jul '09

19:59 < smooge> #startmeeting Fedora Infrastructure 19:59 < zodbot> Meeting started Thu Jul 30 19:59:49 2009 UTC. The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:59 < zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:59 -!- zodbot changed the topic of #fedora-meeting to: (Meeting topic: Fedora Infrastructure) 20:00 < smooge> #topic Who is here? 20:00 -!- zodbot changed the topic of #fedora-meeting to: Who is here? (Meeting topic: Fedora Infrastructure) 20:00 * lmacken 20:00 * onekopaka 20:00 * ricky 20:00 < smooge> Fedora Infrastructure Meeting. I don't know how to 'Yell' in a channel my announcements will be a bit muted :) 20:00 < smooge> smooge is here 20:01 -!- fontana-afk is now known as fontana 20:01 * f13 20:01 -!- jpwdsm [n=jason(a)desm-47-239.dsl.netins.net] has joined #fedora-meeting 20:01 * SmootherFrOgZ is around 20:01 * mdomsch is here for a short time 20:01 * abadger1999 stands up to be counted 20:01 * jpwdsm is here 20:01 < smooge> okie dokie 20:01 < smooge> Thank you all for showing up. 20:01 < smooge> mmcgrath is in class this week. and I will try to run this quickly and clearly 20:02 < smooge> We will start with Tickets 20:02 * fontana is here 20:02 < smooge> #topic tickets (https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi…) 20:02 -!- zodbot changed the topic of #fedora-meeting to: tickets (https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi…) (Meeting topic: Fedora Infrastructure) 20:02 * J5 is here 20:02 < onekopaka> smooge: ick. make that into a tinyurl. 20:02 < onekopaka> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 20:02 < zodbot> onekopaka: http://tinyurl.com/2hyyz6 20:02 < onekopaka> #link https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 20:03 < smooge> thank you onekopaka 20:03 * onekopaka hopes the #link worked 20:03 < smooge> I forgot it was .tiny and not /tiny 20:03 < smooge> #link https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 20:03 < smooge> #topic tickets -- 1503 Licensing. 20:03 -!- zodbot changed the topic of #fedora-meeting to: tickets -- 1503 Licensing. (Meeting topic: Fedora Infrastructure) 20:04 < smooge> abadger1999, you and spot have updates 20:04 < abadger1999> So we got back a lot of good information from legal. 20:04 * abadger1999 thinks fontana might be here if we have furhter questions. 20:04 < fontana> abadger1999: yes :) 20:04 * lmacken waves at fontana 20:05 < ricky> Nice :-) 20:05 < smooge> ok at this point we are looking at how we can best comply with the AGPL 20:05 < lmacken> fontana: oh, I left you a gift from the SFLC on your door frame btw :) 20:05 < abadger1999> If we link to the srpms and the trac query for all hotfixes applied to fedora infrastructure apps, we should be covered. 20:05 * fontana waves back at lmacken 20:05 < smooge> and its going to be about methodology to make sure that the source code is available to users 20:05 < lmacken> fontana: from ian sullivan 20:05 -!- herlo [n=clints@fedora/herlo] has joined #fedora-meeting 20:05 < fontana> lmacken: got that, thanks (was wondering who put it there) 20:05 < abadger1999> I think that's reasonable for production. 20:05 < smooge> abadger1999, I thought the trac entries were NOT acceptable. 20:05 < abadger1999> config files are not copyrightable so that should be fine. 20:05 * abadger1999 looks at hte email again 20:06 -!- sijis [n=sijis(a)adsl-70-131-122-61.dsl.emhril.sbcglobal.net] has joined #fedora-meeting 20:06 * sijis is here. 20:06 < abadger1999> + links to base srpm and tickets in trac that have patches attached 20:06 < abadger1999> * Red Hat Legal says that this is OK. 20:06 < lmacken> sounds like we need a HotfixSOP 20:06 < abadger1999> So the mirrormanager example from last week that said what we changed but didn't provide a patch would not be okay. 20:06 < ricky> For reference, hereis what the link woud look like: 20:06 < ricky> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 20:07 < zodbot> ricky: http://tinyurl.com/numfgb 20:07 < abadger1999> But if we have a patch we are okay. 20:07 < smooge> lmacken, we will need a HotfixSOP and a testing/integration SOP 20:07 < abadger1999> So if everyone else agrees that that's fine, it just leaves the question of staging and publictest. 20:08 < onekopaka> yay more SOPs! 20:08 * herlo likes SOps 20:08 < smooge> abadger1999, thanks. I misread and thought it was the next one down. 20:08 < abadger1999> fontana: Did spot send you the followup questions? Whether we can avoid the AGPL requirment if we use Apache Basic Auth to limit who can access the staging and publictest instances? 20:09 < fontana> abadger1999: I don't think spot sent me that, but I saw it in the mailing list archives anyway 20:09 < smooge> basically we would like to limit who the "users" are that we intend to give the "code" to. 20:09 < fontana> abadger1999: you're limiting it to members of the FI team? 20:09 < spot> darn, i knew i was forgetting something. :/ 20:09 * smooge pulls out greasy noodle to whip spot 20:10 < onekopaka> spot: why hello. 20:10 < lmacken> I'd be fine with apache auth, or requiring vpn/ssh tunnels to get to publictest* 20:10 -!- thomasj_ is now known as thomasj 20:10 < smooge> fontana, it would be limited to Fedora Infrastructure and "Service Owners". 20:10 < lmacken> or staging.. even though it would be a little annoying 20:10 < abadger1999> fontana: Yes. My proposal was the same group that has access to the servers -- sysadmin-test for publictest instances, for instance. 20:10 < fontana> smooge: what's a Service Owner? 20:10 < smooge> "Service Owners" being the sub-group that is asking for the application 20:10 < fontana> ok 20:10 < abadger1999> fontana: But the more inclusive we can be and still satisfy the requirements the better. 20:11 < smooge> so if Fedora Marketing is wanting the AGPL blog, we would limit it to people with that group. 20:11 < abadger1999> fontana: As that lets more people within Fedora test edge cases. 20:11 < fontana> abadger1999: I think this is ok 20:12 < smooge> In this way, the people who are requesting a service are able to see/use that code, and they would know how to get the source code 20:12 < fontana> bkuhn from sflc is not here to tell me I am wrong 20:12 < abadger1999> fontana: Cool. Would all of sysadmin also be okay? 20:12 < abadger1999> :-) 20:12 < onekopaka> fontana: =) 20:12 < fontana> smooge: right 20:13 * abadger1999 sees smooge's proposal already had that. 20:13 < smooge> i proposed something? I forgot ... turning 40 is like the new 80. 20:13 < abadger1999> err.. limited to Fedora Infrastructure and "Service Owners". 20:13 < smooge> ah yes. 20:14 < onekopaka> smooge: nah, it's not. 20:14 < abadger1999> Slightly different than what I thought up on the lsit. 20:14 -!- lcafiero [n=larry(a)dsl-63-249-115-153.dhcp.cruzio.com] has quit "is heading out. Talk to you later" 20:14 < smooge> abadger1999, it comes from all my ITIL brainwashing 20:14 < smooge> ok do we have any other questions on particulars of the license? 20:15 < smooge> if not we can move onto either the next topic or spend 5 minutes on what SOP's would be needed, who is writing them, and when we can have some drafts? 20:15 < ricky> One note is that FAS auth in stating/testing will be a pain 20:15 < abadger1999> ricky: In what way? 20:16 * smooge repeats abadger1999 20:16 < ricky> We don't like to mix testing, prod, and staging, so using mod_auth_postgres to handle restricting access to staging/testing instances is not allowed 20:16 < ricky> It'd suck to make exceptions for this (especially with testing) 20:16 < abadger1999> smooge: How about 5 minutes of implementation talk and then I'll write up the changes we'll need to make for next meeting. 20:17 < ricky> So that's how it'll be a pain. 20:17 < smooge> abadger1999, noted 20:17 < abadger1999> ricky: Ah... fasClient currently hits the production fas anyway, right? 20:17 < ricky> In testing, yes, in staging, no 20:17 < ricky> But staging has hosts entries to point to the staging db 20:17 < ricky> And publictest servers have no access to the db by design 20:19 * ianweller rolls in 20:19 < ricky> PAM auth is an option, but I just wanted to make it clear that mod_auth_postgres is probably not 20:19 < onekopaka> ianweller: did you lose your jetpack? 20:20 < ricky> At least not for publictest machines - if you ignore the outdated auth info, it's usable in staging 20:20 < abadger1999> <nod> 20:20 < ricky> which we already do ignore that problem for the most part :-( 20:20 < abadger1999> ricky: Could we stick the publictest servers behind a proxy? 20:21 < abadger1999> Then the proxy does the bsaic Auth and tlaking to mod_auth_postgres. 20:21 < ricky> We could. It'd be highly annoying, but doable 20:21 < abadger1999> k 20:22 < ricky> In a sense, it'd be something that needs to be done when something gets deployed to production anyway 20:22 < abadger1999> So that's a sticky point. 20:22 < ricky> But it'd cause AGPL compliance to burden people testing non-AGPL apps, which I really want to avoid 20:22 < abadger1999> Any other problems people can identify? 20:22 < smooge> oh one second. Thank you fontana, and spot is there anything you wanted to add? 20:23 < spot> nope. :) 20:23 -!- Pikachu_2014 [n=Pikachu_(a)85-169-125-118.rev.numericable.fr] has quit Read error: 60 (Operation timed out) 20:24 < abadger1999> ricky: also note, we'll have to figure out something whether we switch infrastructure over to AGPL or not. 20:24 < smooge> ricky, abadger1999 it looks like we will need to work out a testing/staging SOP/network design 20:24 < abadger1999> Since we have one AGPL app that people need to test and collaborate on. 20:24 < ricky> abadger1999: Well, doing painful configuration one time for fcomm/moksha is fine with me, as long as it won't affect other stuff 20:24 -!- mchua is now known as mchua_tooling 20:25 < smooge> ricky I think we should not lookinat at as one-time .. long term there will be other apps etc that will need it even if they aren't AGPL. 20:26 < smooge> ok I am at 10 minutes for technical discussion. 20:26 < smooge> sorry 20:26 < abadger1999> Cool. move on to the next one. 20:26 < smooge> next topic 20:26 -!- Sonar_Guy [n=Who@fedora/sonarguy] has quit "Leaving" 20:26 < smooge> #topic tickets #1573 20:26 -!- zodbot changed the topic of #fedora-meeting to: tickets #1573 (Meeting topic: Fedora Infrastructure) 20:26 < smooge> back to you abadger1999 20:27 < onekopaka> .ticket 1573 20:27 < zodbot> onekopaka: #1573 (Remove "All rights reserved" from fedoraproject footers and code) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1573 20:27 < abadger1999> This one's somewhat of a FYI. 20:27 < abadger1999> We have "All rights reserved" i nthe footer of pretty much every Fedora page. 20:27 -!- Pikachu_2014 [n=Pikachu_(a)85-169-125-118.rev.numericable.fr] has joined #fedora-meeting 20:27 < smooge> And there is a problem with that? Oh wait.. I don't work for a University any more. 20:28 < onekopaka> are our right becoming first-come-first-serve? 20:28 < onekopaka> rights* 20:28 < abadger1999> That's misleading since we're actually licensing everything in one way or another (the trademark license for the logo is the most restrictive one we have) 20:28 < onekopaka> ;) 20:28 < fontana> abadger1999: "All rights reserved" is evil and should be eliminated 20:28 < abadger1999> So we should remove it. 20:28 * hiemanshu is here now 20:28 < smooge> what is the proper rights we should have? CC All rights reserved ? 20:29 < abadger1999> spot, fontana: Couple questions: Do we need to talk to other groups when we make changes 20:29 < abadger1999> (like docs) 20:29 < ianweller> all the fedora docs are currently OPL, and will be moving to CC BY-SA 20:29 < smooge> abadger1999, as you said this is FYI. Who will be working on it? 20:29 -!- mdomsch [n=mdomsch(a)24.174.1.212] has quit "Leaving" 20:29 < abadger1999> 2) Should we list the actual license in use? (GPLv2/AGPLv3+ for web apps, OPL to be replaced by CC-BY-SA for docs and wiki) ? 20:30 < ricky> How urgently should we treat this? 20:30 < ricky> Like is it worth live-patching FAS for? 20:30 < spot> abadger1999: you probably should let them know you're doing it, but you don't have to get their approval 20:30 < abadger1999> smooge: Depends on the answer to #1. I'm hoping I can submit patches for all the web apps after thismeeting. 20:30 < abadger1999> AndI'm hoping ricky hasaccess to all the others :-) 20:30 < smooge> ricky no I don't believe its that urgent. regular relaease cycle 20:31 < spot> abadger1999: and you don't have to list the license in use, but it would not be incorrect to do so 20:31 < ricky> FAS is unlikely to have a release in quite some time 20:31 < onekopaka> ricky: yeah, it doesn't need changing. 20:31 < smooge> ricky, ok.. regular rollout of code versus hot-patch 20:31 < smooge> :) 20:32 -!- GeroldKa [n=GeroldKa@fedora/geroldka] has joined #fedora-meeting 20:32 < hiemanshu> Regular rollout i suggest 20:32 < smooge> to me hot-patch means your typing in another window during this meeting... regular rollout is it goes through testing 20:32 -!- cassmodiah [n=cass@fedora/cassmodiah] has quit Remote closed the connection 20:32 < abadger1999> Excellent -- so the FYI portion is "don't use "All rights reserved" in the future and if you see more of that footer in the future, let me know so I can make sure it gets fixed. 20:33 < ianweller> should we just report those to that ticket? 20:33 < ricky> All I'm saying is that regular rollout could potentially be months away for all I know vs. a trivial string change. 20:33 < abadger1999> ianweller: Yep. that would be best. 20:33 < ricky> Anyway, if it's not urgent, I'll leave it alone 20:34 < abadger1999> I think as long as we get it into version control soon it's fine. Deployment can wait. 20:34 -!- RadicalRo [n=radical(a)193.254.32.144] has quit "Leaving." 20:34 < smooge> ricky, months away sounds passable. 20:34 < smooge> ok anything else? 20:34 < abadger1999> Cool. So that's all I have for that one. 20:35 < smooge> #topic Other tickets 20:35 -!- zodbot changed the topic of #fedora-meeting to: Other tickets (Meeting topic: Fedora Infrastructure) 20:35 < ricky> Er, one more thing 20:35 < smooge> waits... 20:35 < ricky> While the legal people are around - should that copyright line not be translated? 20:35 < ricky> (As in should it remain in English on all translated versions of the page) 20:36 < ricky> Right now, it's marked as text that can be translated 20:36 < smooge> spot, fontana question for you. 20:37 < ricky> The text I'm talking about is "Copyright (c) 2009 Red Hat, Inc. and others. All Rights Reserved. For comments or queries, please contact us" 20:37 -!- shepherd [n=shepherd@unaffiliated/shepherd] has joined #fedora-meeting 20:37 * ricky imagines the contact stuff can remain translated 20:37 < fontana> ricky: You mean translate "Copyright © 2009 Red Hat, Inc. and others. All Rights Reserved. For comments or queries, please contact us. "? 20:37 < ricky> Yup 20:37 < spot> well, without the "All Rights Reserved."... 20:38 < ricky> So that line with "All Rights Reserved" is fine to be translated, then? 20:38 * spot defers to fontana 20:38 < fontana> ricky: I wouldn't translate the 'Copyright' part. 20:38 < onekopaka> ricky: as long as it doesn't have "All Rights Reserved" ;) 20:38 < ricky> OK, I'll leave that out, thanks for clarifying 20:38 < fontana> ricky: I guess you could translate the contact part, if you want. 20:38 < ricky> So from "For comments or queries..." will be the only part translatable 20:39 < hiemanshu> AFAIK Copyright part is never translated any where 20:39 -!- shepherd [n=shepherd@unaffiliated/shepherd] has quit Client Quit 20:39 < fontana> ricky: You could make the copyright part non-language-specific by just using the copyright symbol without "Copyright", I suppose 20:39 < onekopaka> © 20:39 < fontana> right 20:39 < ricky> hiemanshu: It is at http://fedoraproject.org/zh_TW/ for example 20:40 < hiemanshu> ricky: it should not be translated 20:40 < onekopaka> © 20:40 < ricky> OK, so (c) 2009 Red Hat, Inc. and others can be translated, or does it stay in English? 20:40 < hiemanshu> ricky: it depends on which country the company or project is located, USA in our case so it should be English 20:41 * ricky would be happy to ask all of this after the meeting if you'll still be around. 20:41 < hiemanshu> ricky: it should stay in English 20:41 < fontana> ricky: legally the "and others" probably doesn't mean anything so I don't think it matters 20:42 < smooge> ricky, lets put this into email. I believe that they are saying the For comments ... should be translated but licensing should not 20:42 < ricky> Cool, thanks 20:42 < sijis> we could take this offline and post the 'results' to the list. 20:42 < smooge> okie dokie 20:42 < ricky> It'll show up in list via the meeting logs, so I'm happy as is 20:42 < smooge> Any other tickets we are looking at? 20:42 < smooge> ricky and dgilmore updated BIND on the servers last night. 20:43 < onekopaka> yep 20:43 < smooge> I am working on getting a trip to Az to upgrade backup hardware. 20:43 < onekopaka> I heard of that story. 20:44 < onekopaka> not the trip story 20:44 < onekopaka> the BIND updatign 20:44 < onekopaka> updating* 20:44 < smooge> there was a story involved? Beyond where the f* is smoogen and why isn't he doing it? 20:44 < onekopaka> smooge: of course. 20:45 < smooge> Alright I think that means we are on open floor 20:45 < smooge> #topic openfloor 20:45 -!- zodbot changed the topic of #fedora-meeting to: openfloor (Meeting topic: Fedora Infrastructure) 20:45 < dgilmore> sorry im late 20:45 < onekopaka> blogs.fedoraproject.org 20:45 < ricky> f13: How is the signing server going? 20:46 < f13> jwb is using it right now 20:46 < f13> so far so good 20:46 < ricky> Cool :-) 20:46 < f13> We've discovered a number of issues with the first setup, that we'll need to resolve and do a clean re-deployment 20:46 -!- opuk [n=kupo(a)pipe.intertubez.net] has left #fedora-meeting [] 20:46 < f13> and then write up some good SOPs in case I get eaten by a raptor 20:46 < smooge> ok cool. let me know when you need that 20:46 < f13> and then we'll be able to go "live" with it 20:46 < smooge> I need to rebuild the RAID 20:47 < tmz> I've been (slowly) working on learning the hosted setup enough to expand the SOPs and create an improved hosted-setup script to do the dirty work for us. 20:47 < tmz> today I'm wondering if we have any working examples of svn commit notifications. 20:48 < ricky> tmz: I think aplaws might be a project with an example of that - not sure if it got broken with noexec or not though 20:48 < smooge> tmz, what does that mean? rebuild of fedora hosted 20:48 < ricky> THanks for working on that by the way 20:49 < tmz> ricky: yeah, I know aplaws is one of them, but it uses a post-commit in /srv/svn, so I'm thinking it's likely to be broken. but I don't honestly know yet. 20:49 < ricky> Ah, I think I tried to debug that at some point with no luck - maybe noexec was the culprit 20:49 < tmz> smooge: nah, no rebuilds needed. just a smarter and more comprehensive hosted-setup script for creating new projects. 20:49 < smooge> ah ok 20:49 < smooge> thanks 20:50 < ricky> Update on mirrors: 20:50 < ricky> The i2 mirror is up, but we're getting slower speeds on than we'd expect from i2 20:50 < ricky> So we opened a ticket with the networking people today 20:50 < ricky> Otherwise, things seem to have cooled down significantly since last meeting 20:51 < smooge> thanks ricky 20:53 < onekopaka> blogs.fedoraproject.org? 20:53 < smooge> ok what about blogs :)? 20:53 < onekopaka> so. 20:53 < onekopaka> It's on production servers 20:53 < onekopaka> but we're trying to work on SSL login. 20:54 < ricky> One thing I'd like you guys to do is make it clear on the front page that it's not 100% in production yet - otherwise there might be some confusion 20:54 < onekopaka> thing is, HAProxy isn't going over SSL 20:54 < onekopaka> ricky: will do 20:54 < ricky> Then you can make an announcement post and everything when it's 100% ready 20:54 < onekopaka> and so value1 & value2 aren't seeing that the request is SSL 20:54 < onekopaka> and that's confusing WPMU. 20:55 < smooge> oh so there needs to be an SSL proxy? 20:55 -!- JSchmitt [n=s4504kr@fedora/JSchmitt] has quit Read error: 104 (Connection reset by peer) 20:55 < sijis> i would think so. 20:55 < onekopaka> smooge: yes, but I haven't figured out how to do such a thing, and ricky doesn't want us to use SSL on value1 & value2. 20:56 < ricky> It's the app servers that wordpress-mu needs to think is SSL, but we'd rather avoid that, even if it takes patches sent upstream to fix it 20:56 < ricky> One resource to try is asking people who run wordpress.com how they do it 20:56 < ricky> Assuming that they have separate proxy/app servers 20:56 < smooge> probably hardware :) 20:56 < onekopaka> ricky: their infrastructure is largely based on nginx 20:57 < onekopaka> ricky: which is kinda like haproxy, but it can also serve static HTML, and run FCGI apps. 20:57 < ricky> OK, so on the backend, is it http or https? 20:57 < onekopaka> ricky: not sure. 20:58 < smooge> ok 2 minutes til hardstop 20:58 < ricky> It might be good to find out and see if they can maybe help with the setup. 20:58 < onekopaka> ricky: the front end you can request with SSL, and in your Profile, choose to use SSL on your dashboard 20:59 < onekopaka> yeah, not sure who does the infrastructure at Automattic. 20:59 < onekopaka> (Automattic is the company that oversees wp.com, and WP/WPMU development, FYI) 20:59 < onekopaka> oh I see. 20:59 < onekopaka> http://automattic.com/about/ 21:00 -!- rdieter [n=rdieter@fedora/rdieter] has quit Remote closed the connection 21:00 < smooge> ok lets wrap this up 21:00 < onekopaka> Barry Abrahamson would most likely be the guy to talk to. 21:00 < onekopaka> smooge: I'm not done. 21:00 < smooge> are we going to run over into someone elses meeting? 21:01 < abadger1999> smooge: I don't believe so. 21:01 < onekopaka> I don't think so. 21:01 < smooge> ok sorry I misread 21:01 < smooge> continue on please and apologies for interrupting 21:01 < onekopaka> I'll see if I can get in touch with Barry. 21:02 < onekopaka> #action onekopaka to attempt to contact Barry Abrahamson, Systems Wrangler at Automattic. 21:02 -!- fbijlsma [n=fbijlsma(a)p54B2DEEA.dip.t-dialin.net] has quit "Leaving" 21:02 -!- gholms [n=gholms(a)minnock.spa.umn.edu] has quit "Leaving." 21:03 < onekopaka> He might also be able to help us with them MySQL queries ;) 21:03 -!- mep [n=palazzot(a)host126-9-dynamic.0-79-r.retail.telecomitalia.it] has quit "Leaving." 21:03 < onekopaka> wp.com is a big site, and they most likely have a way to back it up. 21:03 < onekopaka> so I think we're done.. 21:04 < smooge> #action onekopaka to attempt to contact Barry Abrahamson, Systems Wrangler at Automattic. 21:04 < onekopaka> they also apparently have a big "deploy" button to deploy the latest WPMU code to wp.com 21:04 * onekopaka needs to go get lunch 21:05 < smooge> ok sorry for taking a while to get to you 21:05 < onekopaka> smooge: it's okay. 21:05 < onekopaka> woah, new admin bar on wp.com. it has my gravatar even.. 21:06 < smooge> do we have a time line? 21:06 < onekopaka> smooge: for blogs.fp.o? 21:07 * onekopaka is hitting up the contact page on Barry's WP.com blog 21:07 < smooge> yes? just as in where you think you might be in a couple of weeks 21:07 < onekopaka> well 21:07 < onekopaka> another note is that we would like to upgrade our WPMU 21:08 < onekopaka> so that we can enable plugins sitewide (specificially "Bad Behavior" the anti-spam plugin we chose) 21:09 < smooge> ok this is in the 'testing' stage correct? 21:09 < smooge> so it would not impact users? 21:09 < onekopaka> it's on prod. servers, but not quite there. 21:09 < onekopaka> and the packages aren't in any repo 21:09 * onekopaka digs up his el5 package he made via Koji 21:09 < onekopaka> http://oks.verymad.net/~onekopaka/wordpress-mu-2.8.2-1.fc11.src.rpm 21:10 < onekopaka> hmm 21:10 < onekopaka> that's the f11 one. 21:10 < onekopaka> http://oks.verymad.net/~onekopaka/yumrepo/wordpress-mu-2.8.2-1.el5.noarch.r… is the final one 21:11 < onekopaka> I should rebuild them, I didn't put a changelog 21:11 < smooge> ok so we need to have that built/signed/etc for the infrastructure correct? 21:11 < ricky> Only if we actually do decide that it's worth upgrading to something not in EPEL/Fedora 21:11 < onekopaka> ideally, we'd want them in epel & fedora 21:11 < onekopaka> but. 21:11 < onekopaka> but. 21:11 < onekopaka> BUT! 21:12 < onekopaka> bretm, the owner of the package says after wordpress-mu 2.7, there's a "missing feature" 21:12 -!- sharkcz [n=dan(a)plz1-v-4-17.static.adsl.vol.cz] has quit "Ukončuji" 21:13 < onekopaka> but I have yet to hear what feature that is 21:13 < onekopaka> which is annoying. 21:13 -!- Pikachu_2015 [n=Pikachu_(a)85-169-125-118.rev.numericable.fr] has joined #fedora-meeting 21:13 < smooge> ah ok. we need to get that pinned down I think. 21:13 < onekopaka> yep 21:14 < onekopaka> hiemanshu was going to bug bretm about it, but I haven't any thing from him 21:14 -!- Pikachu_2014 [n=Pikachu_(a)85-169-125-118.rev.numericable.fr] has quit Nick collision from services. 21:14 -!- Pikachu_2015 is now known as Pikachu_2014 21:14 -!- jnettlet [n=jnettlet(a)x1-6-00-16-b6-ad-03-88.k462.webspeed.dk] has quit Read error: 60 (Operation timed out) 21:14 -!- shepherd [n=shepherd@unaffiliated/shepherd] has joined #fedora-meeting 21:14 < onekopaka> so I'm pretty much done here... 21:14 < onekopaka> and so I think we can #endmeeting. 21:15 < onekopaka> unless anyone else has something to say. 21:15 < onekopaka> I'm going to count from 5 21:15 < onekopaka> 5 21:15 < onekopaka> 4 21:15 < onekopaka> 3 21:15 < onekopaka> 2 21:15 < onekopaka> 1 21:15 < onekopaka> 0 21:15 < smooge> ok 21:15 < onekopaka> mmkay, time's up. 21:15 < smooge> #endmeeting 21:15 -!- zodbot changed the topic of #fedora-meeting to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Meeting_channel for meeting schedule 21:15 < zodbot> Meeting ended Thu Jul 30 21:15:59 2009 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . 21:15 < zodbot> Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2009-07-30/fedora-meeting.2… 21:16 < zodbot> Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2009-07-30/fedora-meeting.2… 21:16 < zodbot> Log: http://meetbot.fedoraproject.org/fedora-meeting/2009-07-30/fedora-meeting.2…

1 0

transif user in packager group
by Toshio Kuratomi 29 Jul '09

29 Jul '09

Today we added the transif user to the packager group because transifex lost the ability to add translations for comps. At the moment, this doesn't affect much -- packager group only gives you the ability to commit to comps and what packages you are given explicit rights to. However, it may become bigger in the future since we may allow people to specify that anyone in packager can commit to their packages. transif's last commit to the comps files was around the 17th of July. If anyone can recall some action or config change that they might have performed that would have changed whether transif could commit to comps between 17th of July and today or can think of a better way to give transif access to the comps cvs repo please speak up! it would be better long-term if transif was not in the packager group. The only solution we've come up with that doesn't use the packager group so far requires that we do two things: 1) add cvs acls for transif to commit to comps. 2) set filesystem acls so transif can commit to comps. Doing #2 isn't that great an idea as it's a one-off doing something not readily apparent (we don't use fs acls anywhere else in cvs). But if it could be puppet managed it might not be too bad. -Toshio

2 2

AGPL compliancewith moksha
by Toshio Kuratomi 29 Jul '09

29 Jul '09

Okay, We've got to do some work for AGPL compliance with moksha. First, a few restrictions that we'll have to live with until we can figure out a legal way to do them better: * We cannot do development work directly fedoracommunity/moksha on staging for now. All fedoracommunity/moksha changes must be deployed to staging in the form of an rpm. * lmacken has confirmed that staging is currently deployed from rpm. * **The same for the publictest instances** * If legal approves of using Apache Basic Auth to fix this, we can use that to allow use of the publictest boxes again. Note, though, that that approval will still restrict us (for instance, ianweller is using pt7 to demo his fedora community stats branch. He won't be able to demo it to people outside of sysadmin-test with the Apache Basic Auth solution in place). Some things we need to code into Fedora Community: * We need to be able to customize the footer or front page of fedoracommunity to point to infrastructure.fedoraproject.org for the sources and to trac for hotfixes. * Note that for certain uses of publictest/staging, this can work as well. For instance, ianweller could run his demo strictly from a git checkout and the configuration can point people to that *specific* revision. * Upstream moksha/fedoracommunity might want to change their default footer/frontpage to point to the upstream tarballs as legal says the project page isn't good enough for people running it to be compliant. -Toshio

1 0

Brainstorming Session for Fedora Community 2.0 - Monday August 3, 2009 - 1500 UTC
by Tom Callaway 28 Jul '09

28 Jul '09

For those of you who haven't no idea what "Fedora Community" is, its our newest Fedora web application, providing a window into the Fedora distribution, and leveraging the power of Fedora's Account System, Bodhi, Bugzilla, Koji, and PackageDB into a single user-friendly website. It is built entirely with Free Software, such as Moksha and Turbogears 2. Fedora Community is designed to simplify Fedora workflows and bring transparency to Fedora processes: https://admin.fedoraproject.org/community What you see on that URL is our 1.0 milestone, but we already have lots of ideas on improvements and new functionality that we'd like to develop for our 2.0 release. So, we're going to have a public brainstorming session on Monday, August 3rd, 2009: * The session will be held at 1500 UTC (11 AM Eastern) (In addition, if there are enough interested international folks who cannot attend the session due to their timezone, please let me know, and we will try to schedule a future session that works for you) We're going to use a variety of ways to be involved: * IRC: #moksha on irc.freenode.net (we'll be watching and taking questions from the channel) * Gobby: We're going to keep our notes in Gobby, an open source collaboration tool. The name of our document is "Fedora Community Brainstorm", see http://fedoraproject.org/wiki/Communicate/GobbyHowTo for information on how to connect * Telephone: This is where we'll be doing the talking. US Toll-Free: 800-451-8679 Conference Code: 22717 79826 (If you need an international dial-in number, please email me with your country, and I may be able to provide it.) Please be kind and mute your line if you're not asking a question. If the noise on the call becomes unbearable, I will mute everyone. :) Questions about the meeting? Email me. Questions about Fedora Community 2.0? Come to the brainstorming session! Can't make it to the session and want to suggest something? Login to Gobby and add it to our notes before the session. Thanks, Tom "spot" Callaway, Fedora Community Cat Herder

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure July 2009