I was wondering if anyone had interest in setting up a Wordpress MU install for Fedora's infrastructure?
Gerold Kassube on the marketing team had this cool idea to set up a blog per Fedora foundation (freedom, friends, features, first) and the multiuser capabilities of wordpress seem ideal to drive the project.
Let me know if you have any interest in this. It would be really, really useful for Fedora's marketing.
I'd like to do a low-risk bodhi upgrade this weekend. Changes include:
* A new argument to the 'list' API method that will be utilized by
Fedora Community. This does not break the existing API.
* Added FormEncode validators to the 'list' API method, which fixes a
couple of issues, and ensures we get the data that we expect.
* Made some parts of the updates push process a bit more robust, so if
there is a problem with 1 update, it won't effect the others. This
will help us mitigate some recent explosions that we saw due to
* Fixed some Koji session issues, which we have been hitting
every now and then during pushes.
my name is Tomek Walkuski. I want to introduce myself and write
something about my skills, responsibilities at day job and so on.
I am administering a few CentOS servers, two of these are under VERY
high load running some Java and MySQL powered applications. One of these
is running quite small Oracle instance. I am also using CentOS in my
Master's degree thesis.
What I want to achieve? Always learn something new (to be more
proficient in Red Hat / CentOS / Fedora and to pass someday RHCE
certificate), give my skills, experience (well...) and knowledge back.
I think sticking to Fedora Infrastructure Team someday would be great
opportunity to get involved in FOSS development. Now I will try to
wander around a little :)
During my free time, I am riding my bike, playing with Ada and Eiffel
languages, "doing things".
tel. +48 505 766 148
My name is Will Morris. I thought that I would say hi, and mention some
of my skills as that is what it says to do. I have an ever growing
knowledge of HTML and CSS. I am starting to learn how to do shell
scripting, as well as creating MySQL. I am looking to learn how to
administer a larger network better than I currently do. I am currently
running a medium sized home network, and hope to increase the size of.
If you have any questions please feel free to email me or ask a question
of me on the mailing list.
20:00 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Who's here
20:00 < mmcgrath> Ok all, time to get started, who's here for the infrastructure meeting?
20:00 * ricky
20:00 * jds2001
20:01 * ke4qqq
20:01 * abadger1999 here
20:01 -!- che [n=che@redhat/che] has joined #fedora-meeting
20:01 -!- meyering [n=jim@unaffiliated/meyering] has joined #fedora-meeting
20:02 < meyering> mmcgrath: I'm here ;-)
20:02 < mmcgrath> k, lets get started
20:02 < ranjith> here
20:02 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Tickets
20:02 < mmcgrath> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=as...
20:02 < zodbot> mmcgrath: http://tinyurl.com/47e37y
20:02 < mmcgrath> meyering: yo
20:02 < mmcgrath> kanarip: you around?
20:02 < mmcgrath> .ticket 1203
20:02 < zodbot> mmcgrath: #1203 (RFR: x86_64 host for composing spins) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1203
20:02 < kanarip> yes
20:02 -!- J5 [n=quintice(a)c-66-31-41-146.hsd1.ma.comcast.net] has joined #fedora-meeting
20:02 < mmcgrath> kanarip: so what's the scoop on this?
20:03 < mmcgrath> what is the planned use for this server and what gets spun on it?
20:03 -!- MrTom [n=MrTom@fedora/MrTom] has left #fedora-meeting ["Konversation terminated!"]
20:03 < kanarip> we require resources for spin maintainers to see whether their spins fail or succeed composing, and additional details
20:03 -!- MostafaDaneshvar [n=MostafaD@unaffiliated/mostafadaneshvar] has joined #fedora-meeting
20:03 < mmcgrath> so it won't really have any sustained local storage? Just a sort of cache?
20:03 < mmcgrath> IE: we won't have to run backups on it?
20:03 < kanarip> basically, our plan is to create the spins, and get the logfiles somewhere public
20:04 -!- MostafaDaneshvar [n=MostafaD@unaffiliated/mostafadaneshvar] has left #fedora-meeting 
20:04 < kanarip> mmcgrath, yes, no backup required
20:04 < kanarip> we grab livecd-tools, we grab spin-kickstarts, give it a spin and copy the log files somewhere, then destroy everything
20:04 < kanarip> "everything"; not the machine itself of course ;-)
20:04 < mmcgrath> kanarip: so you guys will just log in via ssh, someone will $run_script, and the results will get placed somewhere that is easily readable to the spin owner?
20:05 < kanarip> yes
20:05 < mmcgrath> I really don't see any blockers from my end other then the one listed in the ticket.
20:05 < jds2001> an installable rawhide would be nice :)
20:05 -!- ggruener [n=Gregor(a)pD9575D6A.dip.t-dialin.net] has joined #fedora-meeting
20:05 < mmcgrath> I'm not sure wtf is up with our physical hosts but after moving to 5.3, none of them can virt-install fedora anymore.
20:05 * kanarip goes to check the ticket
20:06 < mmcgrath> But that's all on our end, just going to delay getting this box up and running unfortunately.
20:06 < kanarip> ok
20:06 < kanarip> thanks!
20:06 < mmcgrath> kanarip: is there a pre-existing group that we can use in FAS or should I create a sysadmin-spins group or something?
20:07 -!- josemmanimala [n=chatzill(a)126.96.36.199] has joined #fedora-meeting
20:07 < kanarip> i think gitspin-kickstarts is a little to broad, so a new group seems most appropriate
20:07 < mmcgrath> I guess these guys aren't really sysadmins, they're just consumers of this box.
20:07 < mmcgrath> kanarip: k, we'll just create a new "spinners" group or something.
20:07 < kanarip> perfect
20:07 < mmcgrath> kanarip: I take it you're the admin of that group?
20:08 < kanarip> yes
20:08 < mmcgrath> is there a "must have" by date?
20:08 -!- notting [n=notting@redhat/notting] has joined #fedora-meeting
20:09 -!- dwmw2 is now known as dwmw2_gone
20:09 < kanarip> mmcgrath, not really, but we'd love to have it before the F12 development cycle starts
20:09 < kanarip> ;-)
20:09 < mmcgrath> k. I need to hunker down and figure out why the virt-installs are failing anyway.
20:09 < mmcgrath> So that's really all the tickets we have listed right now.
20:10 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Beta Launch
20:10 < mmcgrath> https://fedorahosted.org/fedora-infrastructure/report/9
20:10 < mmcgrath> I'll go through these ticket by ticket
20:10 < mmcgrath> .ticket 1250
20:10 < zodbot> mmcgrath: #1250 (Website) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1250
20:10 < mmcgrath> ricky: you all set for website stuff?
20:10 < ricky> Yup
20:10 -!- Gaaruto [n=Gaaruto@fedora/Gaaruto] has quit "Bye!"
20:10 < mmcgrath> Are you going to do the website launch or will you be disposed on release morning?
20:10 < ricky> f13 warned me about checksum filename changes, so that's the biggest change other than the get-prerelease page
20:11 < mmcgrath> and we have the banner ready?
20:11 < ricky> Hm, if it's a Tuesday, I probably won't be around in the morning
20:11 < ricky> Yup, the art team has sent us a banner
20:11 < mmcgrath> k
20:11 * SmootherFrOgZ here
20:12 < mmcgrath> ricky: go ahead and accept that ticket so we know who's got it.
20:12 < mmcgrath> .ticket 1251
20:12 < mmcgrath> this one's all but done.
20:12 < zodbot> mmcgrath: #1251 (We need to verify Mirror Space for the F11 release) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1251
20:12 < mmcgrath> I need to verify the updates/testing 7/8 content is deleted and good to go.
20:12 < mmcgrath> I'll probably close that right after the meeting
20:12 < mmcgrath> .ticket 1252
20:12 -!- Gaaruto [n=Gaaruto@fedora/Gaaruto] has joined #fedora-meeting
20:12 < zodbot> mmcgrath: #1252 (Release Day Ticket - F11 beta) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1252
20:12 -!- ldimaggi_ [n=ldimaggi(a)c-76-19-171-76.hsd1.ma.comcast.net] has quit "Leaving"
20:12 < mmcgrath> That's just the release day ticket, I'll close it when we're all done.
20:12 < mmcgrath> .ticket 1253
20:12 < zodbot> mmcgrath: #1253 (Mirror Manager Redirects) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1253
20:13 < mmcgrath> domsch did this earlier in the week, it's closed already.
20:13 < mmcgrath> .ticket 1254
20:13 < zodbot> mmcgrath: #1254 (Infrastructure Change Freeze) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1254
20:13 < mmcgrath> The change freeze has been in place.
20:13 < mmcgrath> Aside from transifex it's been very quiet and good.
20:13 < mmcgrath> and even with transifex things have been well, I think that team is happy with the work and have started using it.
20:13 < mmcgrath> .ticket 1255
20:13 < zodbot> mmcgrath: #1255 (Add new release to Mirror Manager) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1255
20:14 < mmcgrath> This should be automatic. I seem to remember it not being in the past though, we'll have to watch it on release day
20:14 -!- ldimaggi_ [n=ldimaggi(a)c-76-19-171-76.hsd1.ma.comcast.net] has joined #fedora-meeting
20:14 < mmcgrath> So really that's it for the release.
20:14 < mmcgrath> I'm going to try to do the mirror-rediness test again like I did for the alpha
20:14 < ricky> Hm, how much of the fullfilelist work has been done so that we can have less of a mirror sync delay?
20:14 * mmcgrath gets those notes
20:14 < mmcgrath> ricky: I know some of it has been done, i'm not sure how much.
20:15 < mmcgrath> I don't believe it's ready for the beta though
20:15 < mmcgrath> .any mdomsch
20:15 < zodbot> mmcgrath: mdomsch was last seen in #fedora-meeting 20 hours, 11 minutes, and 16 seconds ago: *** mdomsch has quit IRC ("Leaving")
20:15 < ricky> Ah, OK
20:15 < mmcgrath> http://mmcgrath.fedorapeople.org/alphaMirrorRediness.html
20:15 < mmcgrath> here's how it went last time.
20:15 -!- rogersinel1 [n=rogers(a)188.8.131.52] has quit Read error: 104 (Connection reset by peer)
20:15 < mmcgrath> with hour 1 being the hour prior to release.
20:16 < mmcgrath> f13: have you talked to mdomsch in a while about the file lists change to make the mirrors sync faster?
20:16 < f13> no
20:16 < mmcgrath> k, i'm going to check the tickets and open one if it doesn't exist so we don't forget about it.
20:17 < mmcgrath> f13: what are our odds for a release on the 24th?
20:17 < mmcgrath> 90%? :)
20:18 < f13> 10%
20:18 < mmcgrath> ouch.
20:18 < mmcgrath> if we do slip, will it target one week later?
20:18 < mmcgrath> is it the anaconda storage stuff?
20:19 < f13> we're discussing it right now on the side, I odn't have full details/plans yet
20:19 < f13> but 99% certain there will be a slip, either a 2 day or 7 day slip
20:19 < mmcgrath> k.
20:19 < mmcgrath> <nod>
20:19 -!- Sonar_Guy [n=Who@fedora/sonarguy] has joined #fedora-meeting
20:20 < mmcgrath> So anyone have any questions about the beta release?
20:20 < ggruener> we get a new wiki site to test like the alpha-release?
20:21 < mmcgrath> ggruener: I believe the QA team will have that page up yes.
20:21 < ggruener> ah ok
20:21 < mmcgrath> ggruener: I'll make sure to send it to the fil when it's up.
20:22 < mmcgrath> K
20:22 < mmcgrath> so next item
20:22 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Wiki
20:22 < mmcgrath> So EPEL went up to 1.14.x for mediawiki.
20:22 < mmcgrath> we're going to have to upgrade soon.
20:22 < mmcgrath> Jose did some tests yesterday and it looks like it'll be painless.
20:22 < mmcgrath> I'm going to wait until after the beta to put it in though.
20:22 < mmcgrath> any questions / concerns on that?
20:23 < mmcgrath> k
20:23 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Cloud
20:23 < mmcgrath> So our cloud stuff is coming along, it seems all of our network stuff is configured.
20:23 < mmcgrath> the problem? Our cyclades stopped responding at some point between when it was installed and now.
20:23 < mmcgrath> I've got a ticket open and my understanding is they're working to get remote hands in place to figure out what's goin gon.
20:24 < mmcgrath> If we can't get it working by monday, it'll likely be another week before our tech gets back on site
20:24 < mmcgrath> he'll be traveling to Raleigh
20:24 -!- fugolini1 [n=francesc(a)host104-201-dynamic.21-87-r.retail.telecomitalia.it] has joined #fedora-meeting
20:24 < mmcgrath> So that's really all I have on that
20:24 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Open Floor
20:24 < mmcgrath> anyone have anything else they'd like to discuss?
20:25 < jds2001> .ticket 1279
20:25 < zodbot> jds2001: #1279 (FAS integration with Freemedia TRAC.) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1279
20:25 < jds2001> so we need some policy about when we'll do this.
20:25 < jds2001> I'm going to experiment with doing it with mod_auth_postgres, but that's not really scalable.
20:25 < mmcgrath> jds2001: I'm fine with doing it whenever, AFAIK their shipping for the month is currently closed.
20:26 < mmcgrath> jds2001: define scalable.
20:26 < jds2001> no, I mean for what other projects :)
20:26 < mmcgrath> oh
20:26 < mmcgrath> well, as far as I'm concerned, freemedia got grandfathered in.
20:26 < ricky> We should be making things private very very rarely, I'd hope
20:26 < jds2001> i.e. project X sees we did this and asks tomorrow.
20:26 < mmcgrath> jds2001: I'm fine taking the heat on that and just saying "no, we won't"
20:26 < mmcgrath> We can take it on a case by case basis.
20:27 < jds2001> sounds reasonable.
20:27 -!- JSchmitt [n=s4504kr(a)p4FDD1FB6.dip0.t-ipconnect.de] has quit Remote closed the connection
20:27 -!- josemmanimala [n=chatzill(a)184.108.40.206] has quit "ChatZilla 0.9.84 [Firefox 3.0.7/2009021910]"
20:27 < jds2001> famna and famsco do, but they're using the private tickets plugin
20:27 < mmcgrath> jds2001: do they maintain all of that via trac directly?
20:28 -!- GeroldKa [n=GeroldKa@fedora/geroldka] has quit "Verlassend"
20:28 < jds2001> I packaged up the private tickets plugin for them and edited trac.ini
20:28 < jds2001> but other than that, they maintain it via trac.
20:28 < mmcgrath> k
20:29 < jds2001> but freemedia is a tad...larger :)
20:29 < mmcgrath> yeah
20:29 < mmcgrath> jds2001: thanks for taking a look at that ticket. Let me know if you want any help testing it.
20:29 < jds2001> cool, I'll probably work on hosted2 to start.
20:30 < mmcgrath> excellent
20:30 < mmcgrath> anyone have anything else? If not we'll close the meeting early today
20:31 < mmcgrath> ok, sounds good then we'll close in 30
20:32 < mmcgrath> 10
20:32 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Meeting Closed
We want to update Transifex on app1 with the latest code tagged as 0.5
This shouldn't affect any other service on app1.
Can I have +1s?
Diego Búrigo Zacarão
Linux User #402589
USE SOFTWARE LIVRE
syncing against archive I get:
rsync: opendir "/fedora/linux/releases/8/Everything/i386.newkey" (in fedora-archive) failed: Permission denied (13)
rsync: opendir "/fedora/linux/releases/8/Everything/x86_64.newkey" (in fedora-archive) failed: Permission denied (13)
rsync: opendir "/fedora/linux/releases/8/Everything/source.newkey" (in fedora-archive) failed: Permission denied (13)
rsync: opendir "/fedora/linux/releases/8/Everything/ppc.newkey" (in fedora-archive) failed: Permission denied (13)
rsync: opendir "/fedora/linux/releases/8/Everything/ppc64.newkey" (in fedora-archive) failed: Permission denied (13)
The newkey directories can be probably deleted. As far as I know, there
was never anything in them. On the master server I was able to sync
these directories, although the directories were not accessible to the
user of my mirror server (just like a release before the bitflip).
rsync: send_files failed to open "/fedora/linux/updates/7/SRPMS/.gdm-2.18.4-2.fc7.src.rpm.twC87k" (in fedora-archive): Permission denied (13)
To move pub/fedora/linux/releases/ to
/pub/archive/fedora/linux/releases/, and to retain the MM yum redirects,
we're going to have to do some changes.
* mount archive on bapp1 (add to mirrormanager-server in puppet)
* create directory /pub/archive in MM db
* create category "Fedora Archive" in MM db
* edit /etc/mirrormanager/prod.cfg to add Fedora Archive
* edit repomap.py to add Fedora Archive
* ensure Repository pointers get moved to new location, which means
deleting previous repository pointers.
- the new Repository pointers will collide with the existing ones,
and by virtue of the uniqueness, the new ones won't get created.
So, we'll have to delete the original ones from the DB before
adding the new ones. Will need to kill the u-m-d-l cronjob to
accomplish this, then can restart it.
* mirror admins will have to manually move the content, as we don't
expose /pub/fedora/ and /pub/archive under the same rsync module
anywhere such that we can use hardlinks for a few days. Otherwise
they'll delete it and have to re-download it.
What else am I missing?
This won't require downtime from a user's perspective, but will
require pausing some jobs on bapp1, and editing some files in place in
/usr/share/mirrormanager until I can get a new release rolled out
(which I've been preparing but we're in change freeze so haven't
Also, I'm mostly offline this week as it's Spring Break. How fast do
we need this? Presumably by Thursday or so...
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux