taskGna! Administration - Tasks: task #744, emergency homepage

 
 
Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

task #744: emergency homepage

Submitted by:  Mathieu Roy <yeupou>
Submitted on:  Sun 12 Sep 2004 08:41:06 AM UTC  
 
Status: DoneApproval Status: None
Should Start On: Sat 11 Sep 2004 10:00:00 PM UTCShould be Finished on: Mon 11 Oct 2004 10:00:00 PM UTC
Category: Services FunctionalitiesPriority: 9 - Immediate
Privacy: PublicAssigned to: Mathieu Roy <yeupou>
Open/Closed: Closed

(Jump to the original submission Jump to the original submission)

Thu 16 Sep 2004 04:49:08 PM UTC, comment #17:

https://gna.org/forum/forum.php?forum_id=394

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 04:31:14 PM UTC, comment #16:

Bon ben merci beaucoup !

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 04:24:33 PM UTC, comment #15:

Ok, un certain problème résolu, ça tourne maintenant à http://emergency.gna.org

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 04:24:33 PM UTC, comment #14:

Ok, un certain problème résolu, ça tourne maintenant à http://emergency.gna.org

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 03:53:54 PM UTC, comment #13:

Bon je ne comprend pas, j'ai crée un compte ftp pour tester et ça fonctionne. Par contre, le compte + mot de passe de l'interface ne fonctionne pas.

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 03:51:58 PM UTC, comment #12:

Sans plus de succès depuis la madeleine

J'ai testé le mode actif, j'ai testé en coupant les parefeu depuis la madeleine comme depuis ici même.

Pour ce qui est de passer par un proxy, j'en sais rien, ça m'étonnerais pas. L'endroit où je suis est réputé pour son réseau ultra-chelou au fonctionnement étrange. Ceci dit, ça colle pas depuis la madeleine qui est sans proxy.

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 03:42:44 PM UTC, comment #11:

cyb@wide:~$ ncftpls ftp://gnaemergency:XXX@ftp.jexiste.fr/
./ ../ www/

Tu passes par un proxy ? T'as un firewall ? T'as essaye le mode actif ? T'as essaye d'un autre endroit (a partir de Madeleine par exemple) ?

Cyril Bouthors <cyb>
Thu 16 Sep 2004 03:34:00 PM UTC, comment #10:

After unpacking 1734kB of additional disk space will be used.
Get:1 http://linuxsoft.cern.ch cern/7.3.4/i386/apt/os lftp 2.4.9-2 [699kB]
Fetched 699kB in 0s (955kB/s)
Committing changes...
Preparing... ########################################### [100%]
1:lftp ########################################### [100%]
Done.
[pcphsft06] /home/mroy # exit
exit
[pcphsft06] /home/mroy > lftp ftp.jexiste.fr -u gnaemergency
Password:
lftp gnaemergency@ftp.jexiste.fr:~> ls
ls: Login failed: 530 Login incorrect.
lftp gnaemergency@ftp.jexiste.fr:~>

chelou !

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 03:29:19 PM UTC, comment #9:

Hum, bizarre, je viens de retester sans succès. J'utilise pourtant bien l'utilisateur et mot de passer crée au début (qui fonctionne pour se logger sur l'interface graphique de jexiste).

le ftp est bien ftp.jexiste.fr ?

Il y'a t-il des accès bloqués en fonctions d'IP (je ne suis pas en France en ce moment) ?

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 03:12:06 PM UTC, comment #8:

Non. Je viens de tester, ca marche.

Cyril Bouthors <cyb>
Thu 16 Sep 2004 02:52:49 PM UTC, comment #7:

Ok.

y'a t-il un cronjob à attendre pour que l'accès ftp fonctionne ?

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Thu 16 Sep 2004 02:10:16 PM UTC, comment #6:

Ok, j'ai valide le compte gnaemergency jusqu'en 2010 et j'ai rattache le nom emergency.gna.org.

Il te suffit de mettre tes fichiers sur le FTP (dans le repertoire www) et de faire pointer le DNS vers web.jexiste.org (CNAME).

Jexiste Mirror <jexiste>
Thu 16 Sep 2004 01:54:11 PM UTC, comment #5:

"Une fois le compte cree, je rattacherai status.gna.org a votre compte, faites moi signe. "

C'est fait. Je préfèrerais emergency.gna.org dans la mesure où je ne pense pas qu'on mettra cette page à jour en tant normal, quand gna tourne -- du coup ça donnera pas forcement des infos de "status".

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Sun 12 Sep 2004 02:25:07 PM UTC, comment #4:

Thanks for fast answer... take time though to be sure the procedures are robust vs implementation

This time, you had no way of warning the users / project admins (apart linuxfr). Having a list of project admin available for warning by mail would be fine...

My proposal of http://www.gna.org / gna.org that could be differentiated in case of emergency is a simple / easy to remember way of access for users... If you want to have a http://emergency.gna.org : that will do (just put it in the FAQ which may not be accessible when it's down... so it has to be easily remembered). You may put there planned downtime (which do not happen that often)

I agree that a wiki is a place for breakage, as a ML for spam... there will always be bad guys out there :-( The important thing is that there remains a way to contact the admin / be informed, and this place must be known.

BTW, tuxfamily.org had a similar problem today : power outage at lost-oasis ;-) maybe they have the same cleaning lady as linuxfr :-))

Benoît Audouard <baud123>
Sun 12 Sep 2004 01:50:04 PM UTC, comment #3:

"From a user point of view, as admin of a project, my requirements are :
- to be informed when it happens, when it's restored
- to get a planned date for restoration of service
- be told whether there's data loss or not (and what I should have done to avoid data loss)"

And that's the kind of information we usually provide, so there's no problem providing these. This remark will be taken into account when writing the template for the emergency website.

"For example, you could have a http://www.gna.org hosted on another"

As currently gna.org eq http://www.gna.org and since it makes sense to do so, I do not think we could do it that way without creating confusion.
An url that always work will be provided and will be the meeting point in case http://www.gna.org/gna.org does not work.

"For hosting, you may ask several LUGs, maybe one can provide you with limited hosting :
- a homepage for information (users have to find something interesting there, or they will forget this URL...)
- maybe a wiki (as was done with tuxfamily.org...)
- perhaps a ML for emergency situations (that project admins are advised to subscribe to)"

Emergency will be an homepage, I think that what fit most to the current need (gna admins having a place where they can put gpg-signed messages) without being to big to maintain (a wiki looks like a thing for endless breakage ; we do not intend to have troubles longer than 24h long frequently, and surely not weeks).

"Last : for backups, they should be externalized if possible - either on user side : for cvs that's easy (but not for support/bugs...)
- or by server side : maybe a regular rsync (but once gna grows it becomes more and more heavy...)"

We already have such backups, even if projects are still advised to maintain their own backups.

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Sun 12 Sep 2004 01:14:34 PM UTC, comment #2:

I was not far for my previous request, as it was support #218 : reread the (full) discussion...

From a user point of view, as admin of a project, my requirements are :
- to be informed when it happens, when it's restored
- to get a planned date for restoration of service
- be told whether there's data loss or not (and what I should have done to avoid data loss)

Possible implementations are :
- full redondancy on several sites (well quite expensive), quite compulsory for DNS (at least for the secundary)
- no redundancy : means of information are indirect (currently linuxfr is quite good), if you still could have sent a mail to subscribers of gna project ML it would have been better
- partial redundancy : alternate hosts are available and can provide minimal service (see below)

For example, you could have a http://www.gna.org hosted on another server :
- if www is unavailable, people go directly to gna.org
- if gna.org (projects) is unavailable, people go to http://www.gna.org and see what happened
=> it's interesting as it does not require any DNS change (which can be long to propagate...)

For hosting, you may ask several LUGs, maybe one can provide you with limited hosting :
- a homepage for information (users have to find something interesting there, or they will forget this URL...)
- maybe a wiki (as was done with tuxfamily.org...)
- perhaps a ML for emergency situations (that project admins are advised to subscribe to)

Last : for backups, they should be externalized if possible - either on user side : for cvs that's easy (but not for support/bugs...)
- or by server side : maybe a regular rsync (but once gna grows it becomes more and more heavy...)

Maybe there's descriptions of procedures / implementations of this already on the web ? other than what I've already done... http://wiki.eagle-usb.org/wakka.php?wiki=BesoinsUtilisateursHebergement in other situations

Benoît Audouard <baud123>
Sun 12 Sep 2004 08:51:28 AM UTC, comment #1:

We should be careful when selecting the host: that's not something that should change every years.

Naturally, using FSF France machines is not an option since they are all along with Gna machines. And finally relying on FSF USA machines is not compatible with their current policy related to machine access.

I could host the emergency page at coleumes.org, however it wont be a virtual domain and it wont be accessible via ssh -- so I'm not sure that's the best solution, but that's an option (if we do not find better in one month, I'd say go for it).

Finally, we could do it on an home connectivity line mine (my IP is static). My local server is not always up but I can let it up during troubles.

Any thought? Any proposal?

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.
Sun 12 Sep 2004 08:41:06 AM UTC, original submission:

We definitely need an emergency homepage, as suggested by Baud123, to be able to inform user easily in case all system go offline. This page must be on another location that gna machines (otherwise it would probably not help much). An account on this machine should be accessible through ssh to gna admins + virtual domain.
We could set emergency.gna.org -- if we use a gna address, it means that the secondary DNS must be a working thing.

Mathieu Roy <yeupou>
Site AdministratorIn charge of this item.

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by cyb (Posted a comment)
  • -unavailable- added by jexiste (Posted a comment)
  • -unavailable- added by yeupou (host)
  • -unavailable- added by baud123 (Posted a comment)
  • -unavailable- added by yeupou (made request)
  • -unavailable- added by yeupou (made request)
  • -unavailable- added by yeupou (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 16 Sep 2004 04:31:14 PM UTCyeupouStatusNone=>Done
      Open/ClosedOpen=>Closed
    Thu 16 Sep 2004 01:54:11 PM UTCyeupouAssigned toNone=>yeupou
    Thu 16 Sep 2004 01:49:20 PM UTCyeupouCarbon-Copy-=>Added jexiste
    Sun 12 Sep 2004 08:41:06 AM UTCyeupouCarbon-Copy-=>Added baud123
      Carbon-Copy-=>Added loic
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup