Moksha/Fedora Community Planning Meetings
by Tom Callaway
The Fedora Community (and Moksha) efforts have a regular public meeting
at 1400 UTC every Monday. We invite interested parties to participate in
our meeting.
You can join our meeting via Fedora Talk, extension 2001. For more
information about Fedora Talk, see:
http://talk.fedoraproject.org/
Our next meeting will be on Monday, August 24, 2009.
Thanks,
~spot
14 years, 10 months
Freeze break request for sigul fine tuning
by Jesse Keating
Sigul changes are very low risk, as we're mostly done with the signing
and puppet is currently disabled on these hosts. However vault may be
rebuilt tomorrow and if so I want the puppet modules to be correct for
the rebuild.
--
Jes
14 years, 10 months
Last call for talking points - what makes you excited about F12?
by Mel Chua
If you've got a moment for some last-minute help...
We (Marketing) will be freezing the F12 talking points list today, and
are still somewhat light in the "what makes Fedora awesome for admins
and developers?" categories.
Right now we have "libguestfs and kvm improvements" for admins and
"maybe moblin" for developers, but there must be more - and more reasons
why they're awesome (why *is* libguestfs something that makes admins
happy?). We figured you would know.
The features list is at
https://fedoraproject.org/wiki/Releases/12/FeatureList. If you've got a
moment, please take a look at that, then edit
https://fedoraproject.org/wiki/F12_talking_points with the things that
are making you (as admins and devels) happy about F12 coming out.
Help us promote the heck out of your work. ;)
Thanks!
--Mel
PS: I know this is last-minute notice - sorry about that. We're still
learning how to do things on a schedule, and next time around we'll put
the call out here much earlier.
14 years, 10 months
Wan't to join and why
by Steven M. Parrish
Hi guys and gals,
I am looking to join both the sysadmin-test and sysadmin-cvs groups. Why you
might ask? Well I'll tell you. I wan't to get more involved in Fedora.
Here is my current Fedora resume...
- BugZapper for both KDE and Packagekit.
- Maintain 20+ packages and am a Sponsor in the packaging group.
- Work closely with the OLPC and Sugar folks at getting and maintaining the
packages in Fedora
- Responsible for creating builds of F11 with Sugar specifically for the OLPC
XO-1 (Hope to get an XO-1.5 soon) see http://wiki.laptop.org/go/F11_for_XO-1
for info on this.
What I am looking to do now is create a very simplified bugzilla interface that
can be used by OLPC users, mostly children, to report issues with Sugar
Activities in Fedora. Will develop in PHP and would like to develop and test
it on one of the publictest servers.
Also would like to help maintain the cvs servers and projects contained there.
Any questions just ask.
=====================================================
Steven M. Parrish
-------------------------------------------------------------------------------------------------
gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0
http://tuxbrewr.fedorapeople.org/
irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar
14 years, 10 months
Thoughts on NOPASSWD and disabling agent forwarding on publictest machines?
by Ricky Zhou
Hey, I've been thinking about sudo passwords (particularly on publictest
machines, where security holes in apps being developed cant turn up from
time to time).
Could enabling NOPASSWD for sudo and disabling agent forwarding on
publictest machines be a good option for lowering the possible impact if
anything were to happen on the publictest machines?
The specific situation that I'm thinking about right now is:
* Command execution hole in some app in testing (this has happened)
* Kernel bugs like the two that have shown up in the past month
* People like me regularly entering their FAS password on publictest
machines and having SSH agent forwarding enabled
Maybe this is being too paranoid or not the best ultimate solution (Mike
mentioned that he was looking into alternatives to entering sudo
passwords, for example), but it does seem like a real risk given the
freedom we allow for testing stuff out on the publictest machines.
Thanks,
Ricky
14 years, 10 months
publictest10 rebuild
by Ricky Zhou
Hey, is anybody currently using publictest10? I haven't seen any logins
from anybody other than mmcgrath, myself, smooge, and nb (for doing a
yum update) since May, and this machine is due for a rebuild, as
mentioned in the earlier thread.
If anybody still needs anything from pt10, now's a good time to copy
it off - otherwise, it'll be rebuilt sometime in the next few days.
Thanks,
Ricky
14 years, 10 months
Self-introduction: Mel Chua
by Mel Chua
Hiya. Infrastructure newbie here. I'm Mel; some of you have seen me
around (particularly in Marketing).
https://fedoraproject.org/wiki/User:Mchua has more introduction-esque stuff.
Ricky sponsored me for sysadmin-test so I can get up a test instance of
zikula for FI (https://fedoraproject.org/wiki/Fedora_Insight) - copious
documentation being written at
http://blog.melchua.com/2009/08/16/how-the-zikula-based-test-instance-of-...
(to be turned into wiki notes when everything is up and working). [1]
This is the first time I've done sysadmin-type stuff on a box that
wasn't my own personal computer, and it's been fascinating so far to
learn how things work when multiple users get involved. You'll see
questions from me on IRC (mchua) once in a while - thanks to everyone
who's been extending such a warm welcome! This is much less scary than I
thought it would be. ;)
--Mel
[1] If anyone's interested in playing with a Real Zikula Project early,
we could definitely use help; we're serving as a guinea pig for future
bigger projects like The Great Docs Migration, so there's a ton of stuff
I don't think anybody really knows yet. If someone's looking for a
project for the remainder of F12 and wants to learn about zikula and run
with the tech/infrastructure stuff for FI for a few months, we should talk.
14 years, 10 months
Re: IPv6 for Fedora services?
by Matt Domsch
Do we know if native IPv6 connectivity is available in any of our colo sites, or if we would need to use some form of tunnel?
------Original Message------
From: Mike McGrath
Sender: fedora-infrastructure-list-bounces(a)redhat.com
To: Fedora Infrastructure
ReplyTo: Fedora Infrastructure
Subject: Re: IPv6 for Fedora services?
Sent: Aug 17, 2009 10:01 AM
On Mon, 17 Aug 2009, Jeff Garzik wrote:
>
> Is there any IPv6 plan for *.fedoraproject.org ?
>
There is currently no plan.
-Mike
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
--
Matt Domsch
Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
14 years, 10 months
[Change Request] Enable rw /mnt/fedora on puppet1
by Toshio Kuratomi
Currently we're mounting /mnt/fedora ro on puppet1. I think that this
was a change committed in puppet that affected the /etc/fstab file.
That didn't come into play until we rebooted puppet1 last night -- the
reboot caused the new fstab to be used and mount /mnt/fedora ro.
Here's the changeset that caused that:
Date: Fri Jun 26 22:53:26 2009 +0000
e mount instead of nfs.
diff --git a/modules/puppet/manifests/init.pp
b/modules/puppet/manifests/init.pp
index 21b8d62..0af2273 100644
--- a/modules/puppet/manifests/init.pp
+++ b/modules/puppet/manifests/init.pp
@@ -75,9 +75,12 @@ class puppet::master::mounts {
ensure => directory,
}
- nfs { "/mnt/fedora":
+ mount { "/mnt/fedora":
device => "ntap-fedora1.fedora.phx.redhat.com:/vol/fedora/",
- require => File["/mnt/fedora/"],
+ fstype => "nfs",
+ ensure => "mounted",
+ options => "defaults,ro,soft,intr",
+ require => File["/mnt/fedora"],
}
}
I'd like to make the following change to this:
- options => "defaults,ro,soft,intr",
+ options => "defaults,rw,soft,intr",
Can I get two +1's for my change?
-Toshio
14 years, 10 months
Re: [Change Request] Enable rw /mnt/fedora on puppet1
by Dennis Gilmore
+1 from me
Dennis
Toshio Kuratomi <a.badger(a)gmail.com> wrote:
>Currently we're mounting /mnt/fedora ro on puppet1. I think that this
>was a change committed in puppet that affected the /etc/fstab file.
>That didn't come into play until we rebooted puppet1 last night -- the
>reboot caused the new fstab to be used and mount /mnt/fedora ro.
>
>Here's the changeset that caused that:
>
>Date: Fri Jun 26 22:53:26 2009 +0000
>
> e mount instead of nfs.
>
>diff --git a/modules/puppet/manifests/init.pp
>b/modules/puppet/manifests/init.pp
>index 21b8d62..0af2273 100644
>--- a/modules/puppet/manifests/init.pp
>+++ b/modules/puppet/manifests/init.pp
>@@ -75,9 +75,12 @@ class puppet::master::mounts {
> ensure => directory,
> }
>
>- nfs { "/mnt/fedora":
>+ mount { "/mnt/fedora":
> device => "ntap-fedora1.fedora.phx.redhat.com:/vol/fedora/",
>- require => File["/mnt/fedora/"],
>+ fstype => "nfs",
>+ ensure => "mounted",
>+ options => "defaults,ro,soft,intr",
>+ require => File["/mnt/fedora"],
> }
> }
>
>
>I'd like to make the following change to this:
>
>- options => "defaults,ro,soft,intr",
>+ options => "defaults,rw,soft,intr",
>
>Can I get two +1's for my change?
>
>-Toshio
>
>_______________________________________________
>Fedora-infrastructure-list mailing list
>Fedora-infrastructure-list(a)redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
--
Sent from my Android phone with K-9. Please excuse my brevity.
14 years, 10 months
