This mail is an automated notification from the task tracker
 of the project: Gna! Administration.

/**************************************************************************/
[task #744] Latest Modifications:

Changes by: 
                Cyril Bouthors <[EMAIL PROTECTED]>
'Date: 
                Thu 09/16/04 at 17:42 (Europe/Paris)

------------------ Additional Follow-up Comments ----------------------------
[EMAIL PROTECTED]:~$ ncftpls ftp://gnaemergency:[EMAIL PROTECTED]/

./      ../     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) ?






/**************************************************************************/
[task #744] Full Item Snapshot:

URL: <http://gna.org/task/?func=detailitem&item_id=744>
Project: Gna! Administration
Submitted by: Mathieu Roy
On: Sun 09/12/04 at 10:41

Should Start On:  Sun 09/12/04 at 00:00
Should be Finished on:  Tue 10/12/04 at 00:00
Category:  Services Functionalities
Priority:  9 - Immediate
Resolution:  None
Privacy:  Public
Assigned to:  yeupou
Percent Complete:  0%
Status:  Open
Effort:  0.00


Summary:  emergency homepage

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.


Follow-up Comments
------------------


-------------------------------------------------------
Date: Thu 09/16/04 at 17:42         By: Cyril Bouthors <cyb>
[EMAIL PROTECTED]:~$ ncftpls ftp://gnaemergency:[EMAIL PROTECTED]/

./      ../     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) ?

-------------------------------------------------------
Date: Thu 09/16/04 at 17:34         By: Mathieu Roy <yeupou>
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 [EMAIL PROTECTED]:~> ls             
ls: Login failed: 530 Login incorrect.
lftp [EMAIL PROTECTED]:~> 


chelou !

-------------------------------------------------------
Date: Thu 09/16/04 at 17:29         By: Mathieu Roy <yeupou>
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) ?

-------------------------------------------------------
Date: Thu 09/16/04 at 17:12         By: Cyril Bouthors <cyb>
Non. Je viens de tester, ca marche.

-------------------------------------------------------
Date: Thu 09/16/04 at 16:52         By: Mathieu Roy <yeupou>
Ok.

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

-------------------------------------------------------
Date: Thu 09/16/04 at 16:10         By: Jexiste Mirror <jexiste>
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).

-------------------------------------------------------
Date: Thu 09/16/04 at 15:54         By: Mathieu Roy <yeupou>
"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".

-------------------------------------------------------
Date: Sun 09/12/04 at 16:25         By: Benoît Audouard <baud123>
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 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 :-))

-------------------------------------------------------
Date: Sun 09/12/04 at 15:50         By: Mathieu Roy <yeupou>
"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 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 
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.

 






-------------------------------------------------------
Date: Sun 09/12/04 at 15:14         By: Benoît Audouard <baud123>
I was not far for my previous request, as it was support #218 : reread the 
(full) discussion...


Reply via email to