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.
Regards & Thanks Prabir Senapati mailto: senapati2001(a)yahoo.com
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?
Background: Shortly after we started scaling out to remote sites we
noticed some parts of some of our applications had issues over the vpn
link. Initial ticket creation was a bit off as to what we were looking at
To try to keep this short: after lots of tests we discovered that
applications that run lots of queries are the core of our issue. We have
ok bandwidth to all of our sites, but latency is high enough that it's
become too expensive to actively run applications at these sites. Every
query that gets run at a remote site seems to take a minimum of .3 to .5
seconds for the complete round-trip. As we mature and as features get in
lots of our apps need more queries. We can and should go through and make
these more efficient but that's going to happen over a long time. We just
don't have the number of people we need to do trends on each page of each
application and convert all the sql to its most efficient.
Instead we're going to convert all of our remote application servers to
passive/backup servers. Up until now we've generally been using our
remote sites to scale load. Now though we can't really do that. They're
an important role for being fairly HA (our SPOF is still our data layer).
Having a multi-master data layer of postgres and mysql just won't be a win
for us at our size at this time.
So what does this mean for the future? Our scaling issues at our app
layer will just have to be in a centralized location. This won't scale
forever but I think for the near and middle term in Fedora's future it's
what we're going to have to bank on. We can continue to focus on better
caching at our proxy layer which will continue to be active at each remote
All of what I've written here is probably very obvious to most of you, and
it is. The difference now is we have some much better data concerning the
interaction between our app servers and the data layer and better metrics
for how long those interactions take. So darnit, I'm not going to spend
all the time I did with testing and metrics and not write some long
summary about it! :)
rsyncing from secondary I get following error:
rsync: send_files failed to open "/releases/test/9-Beta/Fedora/source/SRPMS/.kernel-126.96.36.199-78.2.9.fc9.src.rpm.U3tJXy" (in fedora-secondary): Permission denied (13)
My name is Nadim. I'm a psychology sophmore and computer science minor at
the Lebanese American University in Beirut, Lebanon.
I became acquainted with Fedora after deciding to try it after three years
of Gentoo Linux usage on various servers and desktops I've built and
I found Fedora to be an awesome distribution, and having had much experience
with Gentoo server building and administration (I've set up many servers for
my university and am the founder of Anapnea, the Open Gentoo Linux shell
server (http://anapnea.net)), I felt that maybe I could contribute with my
time and skill to help out with the Fedora project as much as I can, in
whatever area I am capable to help in.
I'll be attending today's IRC fedora-meeting, and I look forward to being
able to contribute!!
Hello newcomers to Fedora Infrastructure!
There have been quite a few of you popping up lately, but there hasn't
been a lot for you to do yet. Well here's your chance. I'd like to
investigate adding Review Board
<http://code.google.com/p/reviewboard/> as a service for Fedora Hosted
projects. Review Board is a web based tool for managing code reviews.
If this is something that you'd like to work on, here's an outline of
what needs to happen.
1. Package Review Board for Fedora (and EPEL too, as Fedora
Infrastructure typically deploys services on RHEL 5). This will be
useful even if we decide not to deploy Review Board for Fedora Hosted.
2. Install & configure Review Board on a test system and figure out
how to Puppetize the configs.
3. Get feedback from the community and decide if we want to deploy as
4. Assist in the deployment to production and help with day-to-day management.
If you're interested, here's the ticket I'm using to track progress:
---------- Forwarded message ----------
From: Fedora Infrastructure <trac(a)fedorahosted.org>
Date: Thu, Feb 19, 2009 at 9:10 AM
Subject: [Fedora Infrastructure] #1196: Deploy Review Board for use by
#1196: Deploy Review Board for use by hosted projects
Reporter: jcollie | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Hosted Projects | Version:
Severity: Normal | Keywords:
Review Board is a tool for managing code reviews. Digium has been
successfully using it to review code submissions for Asterisk for several
months now. It would be very useful to offer this to hosted projects for
Review Board itself would need to be packaged, but it appears that all of
the dependencies are already in Fedora:
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/1196>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to
our source code.
"You know, I used to think it was awful that life was so unfair. Then
I thought, wouldn't it be much worse if life were fair, and all the
terrible things that happen to us come because we actually deserve
them? So, now I take great comfort in the general hostility and
unfairness of the universe."
-- Marcus to Franklin in Babylon 5: "A Late Delivery from Avalon"
Hey all, I've added an additional "Self Access" policy to our security
"Admins and users must not give themselves access to resources unless it
is an emergency or a setup issue. Follow normal steps to get in a group
and sponsored by someone."
Also note that anyone in our sysadmin group with shell access to our
servers must be fully compliant with the security standard by the end of
Xavier Lamien wrote:
> 2009/2/14 Dennis Gilmore <dennis(a)ausil.us>:
>> There will be an outage starting at 2009-02-21 15:00 UTC, which will last
>> approximately 48 hours.
>> To convert UTC to your local time, take a look at
>> or run:
>> date -d '2009-02-21 15:00 UTC'
>> Affected Services:
>> Buildsystem (koji and plague)
>> Unaffected Services:
>> CVS / Source Control
>> Fedora Hosted
>> Fedora People
>> Fedora Talk
>> Mirror System
>> Translation Services
>> Ticket Link:
>> Reason for Outage:
>> Maintenance of /mnt/koji filesystem,
>> koji DB Maintainence
>> Upgrade koji to support EPEL, noarch subpackages, srpm's built in a chroot.
>> along with lots of bug fixes.
>> Contact Information:
>> Please join #fedora-admin in irc.freenode.net or respond to this email to
>> track the status of this outage.
>> Fedora-infrastructure-list mailing list
> Just a heads-up
> The outage is still going
This is still ongoing. A final Done email will be sent when you can
submit builds again.
Thanks for your paitence.