On Thu, 2005-10-06 at 19:57 +0200, Christian Rose wrote: > ons 2005-10-05 klockan 10:44 +0200 skrev Carlos Perelló Marín: > > > > If you'd prefer not to host it on your own server, and if there is > > > > willing to maintain it, I expect some space could possibly be arranged > > > > on one of the real gnome.org servers. It's just easier for the GNOME > > > > sysadmins to set up a DNS entry than it is to set up new user accounts > > > > and a secure/capable hosting area etc. It would probably get rolling > > > > quicker if hosted externally, at least to begin with ;) > > > > > > I agree with Ross; an external solution is probably the best in the > > > short run, but in the long run, GNOME translation status pages and the > > > translation status page scripts make sense to have hosted on the > > > gnome.org servers. That will make sure that: > > > > > > * There are always several people distributed around the world who can > > > access the machine and fix it if needed (gnome.org sysadmins) > > > * The pipe is already a *very* Fat (tm) one > > > * The status pages will not be inaccessible again when some single > > > individual moves/goes on vacation/loses his job/gets hit by a bus and is > > > unable to maintain them > > > * The translation status pages will have access to the repository which > > > sits right next to it at the very same location > > > > > > The only thing needed for the translation status pages to be hosted at > > > the real, live gnome.org servers is for someone to figure out what kind > > > of CPU/memory/disk resources it needs, and is prepared to help set it > > > up, or at least give sufficient instructions for having it set up. > > > > > > So what's the required configuration? > > > > root gandalf:/srv/l10n # du -hs . > > 6.9G . > > > > and the process takes near 4 hours with an AMD Sempron(tm) 2800+ and > > 768MB of RAM > > > > With more RAM and faster CPU the process should be also faster. The main > > problem here is the hard disk I/O that's why we had to move it outside > > widget the first time, the server load was really high. > > widget has since then been replaced by window. window.gnome.org is a > dual Xeon 2.8 GHz server with 2 GB memory and RAID1 SCSI disks. > > This should be doable, right? Sure, the server works, the problem are the other process on that machine not the generation of the status pages... I'm not able to tell you if that machine will work or not, sorry. > > > > As I said in other email, I don't mind to give shell access to you > > (Christian), danilo or any GNOME admin to have a "backup" > > Still, I think the Translation Status pages are too important to be > hosted off-site. The work of the GTP effectively stops completely when > the status pages are not working. Just to make it crystal clear, I don't have anything against that, I'm the maintainer, not the owner. > > If you are on vacation and the current server hosting the pages goes > down, we aren't helped much by shell accounts. Sure, we can probably > call someone, but whom? And how fast can it be fixed? My current hosting allows to control it over the web and reboot a recovery Linux system just in case is there any problem with the server so if finally we don't move it outside my server and offline problems became a problem (the stability of the server changed a lot since 6 months ago...) I could share that web access too with any GNOME sysadmin (it's better if I know him) > > With the gnome.org servers, emergency plans for all of that are already > in place, and have been proven to be working. But having the translation > status pages hosted somewhere completely else where I and others don't > have any information of that sort doesn't make me sleep well at night. If the migration to GNOME server is doable, perfect, if it's not, I don't mind to get a plan in place so you can sleep well... Cheers. > > > Christian > -- Carlos Perelló Marín Ubuntu Hoary (PowerPC) => http://www.ubuntulinux.org Linux Registered User #121232 mailto:carlos pemas net || mailto:carlos gnome org http://carlos.pemas.net Valencia - Spain
Attachment:
signature.asc
Description: This is a digitally signed message part