infrastructure August 2011

infrastructure@lists.fedoraproject.org

28 participants
39 discussions

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

13 Sep '11

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

2 2

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

02 Sep '11

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

1 1

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

30 Aug '11

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

2 1

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

29 Aug '11

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

1 0

logs and emails
by Kevin Fenzi 27 Aug '11

27 Aug '11

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

2 5

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

26 Aug '11

The infrastructure team will be having it's weekly meeting today: 2011-08-25 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * Upcoming Tasks/Items (nirik) 2011-08-23: Fedora 16 alpha 2011-09-01 mail fi-apprentice folks. 2011-09-13 - 27: Beta change freeze 2011-09-09 Remove inactive fi-apprentice people. 2011-09-27: Fedora 16 Beta * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

Hosted plans
by Kevin Fenzi 25 Aug '11

25 Aug '11

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

12 28

unfrozen
by Kevin Fenzi 24 Aug '11

24 Aug '11

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

1 0

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

24 Aug '11

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

2 1

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

23 Aug '11

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

2 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2011