Wiki Outage Notification - 2008-08-14 03:00 UTC & 2008-08-15 03:00 UTC
by Nigel Jones
There will be an outage starting at 2008-08-14 03:00 UTC, which will
last approximately 1 hour. A second outage is scheduled to start at
2008-08-15 03:00 UTC lasting approximately 30 minutes.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2008-08-14 03:00 UTC'
date -d '2008-08-15 03:00 UTC'
Affected Services:
Fedora Project Wiki
Unaffected Services:
All Other Websites
CVS / Source Control
Buildsystem
Database
DNS
Mail
Torrent
Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/754
Reason for Outage:
We will be performing database changes to the wiki database to enable
searching by default for specific categories and to switch to the
internal authentication methods. We hope to be able to leave the wiki
Read Only during both outages.
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email
to track the status of this outage.
Thanks,
Nigel Jones
15 years, 8 months
[Fwd: Re: Tasks and followup]
by Paul W. Frields
-------- Forwarded Message --------
> On Tue, 12 Aug 2008, Mike McGrath wrote:
> > On Tue, 12 Aug 2008, Paul W. Frields wrote:
> > > On Tue, 2008-08-12 at 15:52 -0500, Mike McGrath wrote:
> > > > On Tue, 12 Aug 2008, Paul W. Frields wrote:
> > > >
> > > > > Apologies for this being an idea with no code attached. I'm hoping that
> > > > > some of the able folks are on this list and will see something
> > > > > achievable.
> > > > >
> > > > > Something the Community Architecture folks and I have discovered is that
> > > > > when we sign up new folks for an account, there's not any way to mark
> > > > > them for follow up or to indicate a note for where they did it. A
> > > > > couple methods for doing this come to mind:
> > > > >
> > > > > 1. Simple but effective -- a way to tag account holders arbitrarily.
> > > > > This might help with a number of things, like skill sets, karma, and so
> > > > > forth. In this case, the tag would allow Ambassadors to follow up on
> > > > > particular shows by listing everyone with "FooCon 2008" in their tag
> > > > > list.
> > > > >
> > > > > 2. More complicated but possibly more predictable -- A plugin for FAS
> > > > > that would allow ambassadors to request or create a special signup
> > > > > portal, and use it at a show to help visitors sign up (e.g.
> > > > > join.fp.o/foocon2008 or foocon2008.join.fp.o).
> > > > >
> > > >
> > > > I'd say 2 is pretty easy in a plugin.
> > > >
> > > > https://admin.fedoraproject.org/accounts/promo/sign-up/MyPromo
> > > >
> > > > where MyPromo could just be arbitrary. It'd get flagged somewhere that we
> > > > could get it later.
> > > >
> > > > The point of this is so users can sign up with some sort of flag on how
> > > > they found out about Fedora, and then run stats on it later?
> > >
> > > Not just stats, but also to get people "assigned" geographically to
> > > Ambassadors or some other mentor group, in a way that makes sense and
> > > maximizes stickiness.
> > >
> >
> > So something more exact then timezone, locale and country or could this
> > metric bet completely independent of those values?
> >
>
> Another note on that, if we split up the ambassadors into regions (I
> suspect they already are) would it be better to just create a group for
> each region managed by the ambassadors?
We could create FAS groups for regions, sure. But there's also
particular ambassadors to consider -- for example, an Ambassador who
works on Websites might target a new signup for helping with Websites,
even though that new person lives in a different country.
Maybe groups plus the portal plugin would do the trick. I'll ask around
with the Ambassadors.
--
Paul W. Frields
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://paul.frields.org/ - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
15 years, 8 months
Tasks and followup
by Paul W. Frields
Apologies for this being an idea with no code attached. I'm hoping that
some of the able folks are on this list and will see something
achievable.
Something the Community Architecture folks and I have discovered is that
when we sign up new folks for an account, there's not any way to mark
them for follow up or to indicate a note for where they did it. A
couple methods for doing this come to mind:
1. Simple but effective -- a way to tag account holders arbitrarily.
This might help with a number of things, like skill sets, karma, and so
forth. In this case, the tag would allow Ambassadors to follow up on
particular shows by listing everyone with "FooCon 2008" in their tag
list.
2. More complicated but possibly more predictable -- A plugin for FAS
that would allow ambassadors to request or create a special signup
portal, and use it at a show to help visitors sign up (e.g.
join.fp.o/foocon2008 or foocon2008.join.fp.o).
--
Paul W. Frields
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://paul.frields.org/ - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
15 years, 8 months
publictest10
by Mike McGrath
publictest10 is our most heavily used test server and it has OOMed a few
times. We have a couple of options.
1) move pt10 somewhere where it will have more ram (preferably outside of
PHX)
2) create new pt servers
3) move some apps off of pt10 and on to other test servers
I generally lean towards 1. Anyone have any preferences? Has anyone done
an audit of the box in a while to see what the big memory hogs are?
-Mike
15 years, 8 months
*.fedoraproject.org
by Mike McGrath
We now have a *.fedoraproject.org wildcard cert. This will make creating
websites significantly easier. We already have some plans for the
translated wiki and such. I'm going to be implementing this cert soon for
much of our infrastructure. My tests worked fine but just the same,
conversion to production might produce some cert oddness. Please do keep
your eyes open.
I've never worked with a wildcard cert before and right now plain old
"fedoraproject.org" doesn't work. This makes sense but I'm wondering if
anyone knows a way around it. Is it not possible to create a cert for
your entire domain as you'll always have at least a *.example.com and a
root "example.com" cert? correct me if I'm wrong on that.
-Mike
15 years, 8 months
DNS serial number
by Mike McGrath
Should the first serial number for a day be 00 or 01? EX:
2008081001 or 2008081000
-Mike
15 years, 8 months
RFC: script to run sqlalchemy migrations on the db
by Toshio Kuratomi
FAS started using the python-migrate package to update its db. This is
a good thing for third-parties that want to install their own FAS server
as it lets us ship the database changes in a way that is easy for those
users to apply to their own production databases.
However, it doesn't work very well in our particular environment because
we're a bit more strict about our permissions than the migrate authors
envision. In order to perform migrations, you need to have a user that
can modify the schema for the db. This is either hte owner of the db or
the superuser. In our setup, we create the db with the superuser and
then run our web apps with another user. This prevents the normal web
app from modifying the db schema.
To work around this I propose writing a script that does this:
# 1) Create a db user.
# 2) grant access to all the values in the specified db
# 3) run the migrate commands to create the manage.py script and run it
with the new username and password
# 4) Reassign any new tables to the postgres user
# 5) Remove the temporary db user
The command line to invoke it would then look like this:
sudo -u postgres migrate-runner -h DBHOST -d DBNAME MIGRATE_REPO
Does this look:
1) Doable -- loupgaroublond I'm looking at you to tell me what the
migrate commands will be and if there's any caveats to this
2) Secure -- the point of this would be to keep protecting the db
superuser with a sudo account on db2 and not being able to use it
without a shell on db2. If the security of this solution is less than
what giving a password to a superuser account would be then we might as
well do that instead.
If this looks good, I'll work on coding something up.
-Toshio
15 years, 8 months
Introduction
by Grady Laksmono
Hello,
My name is Grady Laksmono, and I've been becoming Fedora Ambassador for a
while now, and since I've a technical background, I'd love to contribute to
Fedora infrastructure and/or anything related with source code.. :)
Nice to meet all of you
Cheers,
Grady
15 years, 8 months
