infrastructure February 2007

infrastructure@lists.fedoraproject.org

34 participants
32 discussions

people,developers.fedoraproject.org
by Mike McGrath 03 Mar '07

03 Mar '07

So now that fpserv no longer hosts the wiki... We may be able to re-evaluate the people.fedoraproject.org and developers.fedoraproject.org setup. This machine is at Duke and Seth is on board (he suggested it). I'd still like to send a copy of the CVS off site to this box for safe keeping but it would allow us for plenty of leg room. This is probably going to be a long discussion (as it should be) but I'll get started. people.fedoraproject.org: For Fedora contributors[1] only, no exceptions. 50M quota, strictly enforced. Static content only sftp access http access Fedora related content only. (We will passively police) No expectation of privacy Won't take much to get banned from p.fp.o username.people.fedoraproject.org (should be trivial to setup) developers.fedoraproject.org For the more high-level people, will require full approval of the infrastructure team. For those that don't make it I'll send them a note telling them no and explaining why if there is a reason. (This if for the jkatz, thl's, abadger1999 and dgilmore's of our group) 200M quota, manually enforced (email notifications) Static content and basic scripting, TurboGears, python, php, perl, etc. cronjobs (this may be a bad idea) sftp http/https shell / ssh no expectations of privacy Local apps (like running their own mysql db's and such, as long as it's within the quota) username.dev.fedoraproject.org (should be trivial to setup) We will help meet these peoples needs but won't go too far out of the way (like installing multiple versions of python) ** Not for critical apps ** The idea here is that this should be a very hands off process for our team. We'll help the developers with things but if we don't meet their needs, they'll have to go somewhere else, this is a convenience thing. The people.fp.o site will be completely hands off, we have to find a scriptable way to determine who belongs in people. Anyway, what do you think? -Mike [1] Contributor. Here are a few possible definitions of contributor: CLA: Users who have signed the CLA (I consider this to be the general public) Sponsored: Users who have been sponsored by someone for their team. Committers: People who actually have commit access to the CVS (Doc's team, Extras, etc) I vote for "sponsored"

7 11

planet sub domains
by Dennis Gilmore 28 Feb '07

28 Feb '07

So it came up that it could be useful if there were sub planets. say art.planet.fedoraproject.org for people posting art work. or docs or some other fedora sub topics. What does every one think of the possibilities? Dennis

8 7

Infrastructure IRC Meeting Logs Updated
by Jeffrey Tadlock 26 Feb '07

26 Feb '07

Just a heads up that I added IRC meeting logs to the Wiki from 1/11/2007 to 2/22/2007. They are located here: http://fedoraproject.org/wiki/Infrastructure/Meetings --Jeffrey

3 2

FAS2 Views
by Mike McGrath 26 Feb '07

26 Feb '07

I've created a page with a list of views, that is things I know the user needs to be able to see / do. The admin interface for FAS2 will be very minimal since LDAP level stuff can be done in LDAP. Please add / change stuff that on this page so we get a full list of things what needs to be done. Also, I haven't organized views into actual pages, some views would make sense on the same page. There's also lots of fun stuff on the mockup that I haven't added but should (like invite new members, etc) http://fedoraproject.org/wiki/Infrastructure/LookAndFeel/FedoraAccountSyste… -Mike

1 0

Re: reStructured Text now supported on the wiki
by John Baer 26 Feb '07

26 Feb '07

Mike wrote: > {{{ > #!rst > Place *text* here. > }}} Mike, I am new to the infrastructure list. Most of my time of late has been spent in the art-team area. Mairin Duffy invited me to the list to assist with some of the projects she is working on. The Fedora wiki IMO is the best implementation of MoinMoin to be experienced. Great work! :) I am also running a version locally but I feel I am light years behind what you have accomplished. For example, I don't have this plug-in as well as many others. Is there a way I can catch up? Cheers, John

2 1

Moin moin security patch
by Toshio Kuratomi 24 Feb '07

24 Feb '07

Hey guys, So we (Mostly Mike :-) gave the wiki the ability to parse restructured text yesterday which gives the Docs people another tool for working with wiki content. However, the restructured text parser was originally designed for command line tools to statically convert rst into other formats (html, docbook, etc.) Using it in a dynamic environment like a wiki has some security issues that have to be addressed. The docutils authors have listed the issues they're aware of with configuration options to disable the features. We've placed a config file on the app servers that do this. Unfortunately, Moin has reimplemented one of the features (include) in a safer manner. But their implementation doesn't process ACLs so any user can look at pages they lack the ACL for by using an include. Attached is a small patch that disables include entirely. I've submitted a bug with upstream moin to add ACL support to this function as a longer term fix. -Toshio

1 0

reStructured Text now supported on the wiki
by Mike McGrath 24 Feb '07

24 Feb '07

http://docutils.sourceforge.net/docs/user/rst/quickref.html in case you want to use it. {{{ #!rst Place *text* here. }}} -Mike

1 0

OTRS Spam filtering
by Mike McGrath 24 Feb '07

24 Feb '07

I'm going to enable some long overdue spam filtering to the OTRS app, this is different from the SMTP server but will ultimately work with it. -Mike

1 0

[Fwd: [Fedora Project Wiki] Update of "Docs" by 10.8.32.56]
by Rahul Sundaram 23 Feb '07

23 Feb '07

Hi Never seen a wiki change that showed a IP address instead of the user name before. Rahul

4 4

Wiki Upgrade
by Mike McGrath 23 Feb '07

23 Feb '07

So for those wondering what I've done with the wiki upgrade, I've made a simple diagram. As we get more hardware and resources you can see where we're headed as far as HA goes in our environment. I'm still trying to acquire a NAS or SAN for us, this will make what we need to do much easier. Also at the application layer once we get in a Xen environment we can add and remove app servers easily without having to expand the number of proxy servers we have until they get overloaded. I'm still experimenting with various things but right now app2 is our biggest SPOF[1] as it houses the wiki and shares it with app1. The proxy servers are using mod-rewrite [P] to proxy services. Basically the load balancer balances between proxy[1-2] and each proxy in turn proxies to app[1-2]. Instead of proxy1 -> app1, proxy2 -> app2. The proxy servers will also mount or contain copies of static content (like /extras, or favicon.ico) There are many tweaks to be made to make this useful and hands-off HA, but this is a good first step for us. As always I'm interested in discussion so send it my way. -Mike [1] Our load balancer may also be a SPOF, not sure.

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure February 2007