[EXTERNAL] [BULK] RE: [Ops] non-responsive services in the Registry

Fri Jul 14 23:49:38 CEST 2023

Thanks for all the responses.  It sounds like we just need to write this down, perhaps somewhere on the Registry wiki?

- - - -
Dr. Tess Jaffe (she/her)
NASA Goddard Space Flight Center, Greenbelt, MD, USA

________________________________
From: registry <registry-bounces at ivoa.net> on behalf of Christophe Arviset <Christophe.Arviset at esa.int>
Sent: Thursday, July 13, 2023 4:28 AM
To: registry at ivoa.net <registry at ivoa.net>
Cc: Sara Nieto <sara.nieto at ext.esa.int>; Philip Matsson <philip at winterway.eu>
Subject: [EXTERNAL] [BULK] RE: [Ops] non-responsive services in the Registry

CAUTION: This email originated from outside of NASA.  Please take care when clicking links or opening attachments.  Use the "Report Message" button to report suspicious messages to the NASA SOC.

Dear all

Indeed, at the Euro-VO Registry, we’ve recently applied the same rules as Pierre and in all cases, we did not have to go up to point 4 (ask IVOA Exec for final decision), as earlier steps and through step 3 (ask national representative at the IVOA Exec to take decision) was enough to have the confirmation.

--

Thanks in advance

Cheers

Christophe

PS: This e-mail might reach you during non-working hours. This is a matter of my personal work-life balance and travel schedule only.

I do not expect to receive a reply outside of your usual working hours.

-------------------------------------------------------------------

Christophe ARVISET                       Christophe.Arviset at esa.int<mailto:Christophe.Arviset at esa.int>

Head of the Data Science and Archives Division

Science and Operations Department, Directorate of Science

European Space Astronomy Centre (ESAC)

European Space Agency (ESA)

Camino Bajo del Castillo s/n

Urb. Villafranca del Castillo

28692 Villanueva de la Canada - Madrid        Tel: +34 91 813 12 78

SPAIN                                         Mob: +34 655 05 43 03

-------------------------------------------------------------------

From: registry <registry-bounces at ivoa.net> On Behalf Of Pierre Le Sidaner
Sent: Tuesday, July 11, 2023 12:18 PM
To: registry at ivoa.net
Subject: Re: [Ops] non-responsive services in the Registry

On 10/07/2023 09:38, Markus Demleitner wrote:

Hi Tess,

Thanks for tackling this.

On Fri, Jul 07, 2023 at 01:18:46PM +0000, Jaffe, Tess (GSFC-6601) wrote:

So I'm looking for information about how to remove services from

the registry that are not responding and whose responsible contacts

aren't either.  Renaud pointed me at a mention on the Ops page

(https://wiki.ivoa.net/twiki/bin/view/IVOA/IvoaOps#Procedure%20for%20Removing%20Non-Respo)

which refers to "A revised procedure was adoped by the IVOA in

October 2016."  But we don't find it.  Anybody know where I can

hear about what other registries are doing and what we should do?

Well... this, I seem to remember, refers to item 7 in these Exec

minutes:

<https://wiki.ivoa.net/internal/IVOA/IvoaRepMin/ivoa-fm66-20161020.pdf><https://wiki.ivoa.net/internal/IVOA/IvoaRepMin/ivoa-fm66-20161020.pdf>.

I think Pierre had a nicely worked-out paper back then that I may

even be able to dig out if necessary.  Pierre, if you have it at

hand, can you perhaps put it on the twiki in some suitable position?

But then in practice here's what I've been doing when I encounter

dead services by chance, typically because dead services have bad

resource records, too:

(1) use the contact address to ask the service's operators

(2) if they are unresponsive, try the originating publishing

registry's operators

(2a) if they are responsive, work with them to either get the service

fixed or have it removed from their publishing registries

(2b) if they are unresponsive, see whether any living services are

published through that registry (in case *it* is still alive).  If

that is the case (never has been), improvise.  Otherwise, ask the

Exec to tell the RofR to remove the dead publishing registry.

Perhaps that's something we should note down on the Twiki, perhaps on

a page linked to by Ops and Registry?

               -- Markus

I will talk about experience in removing ghost service from the registry, our (group of cleaners) where having a step that are more empirical

1) As Markus said, first try to contact the owner of the service, in those case usually nobody answer, because we had already did that many time.

2) try to see in the same institute if you know somebody close to ...
Sometime it worked, mean we have an answer like "it's dead you can remove it"

In that case you go with this answer to the owner of the registry where the service is registered and ask to make it in status='inactive'

3) still no answer, try to find (usually on exec) the national representative in iVOA

sometime it solve the problem, because he know who is now in charge of the service and it can allow to change the resource content or pass it to inactive

4) nothing work, ask exec to take a decision on the status of the resource to remove it from registry

I hope it helped

Regards

Pierre

--

-------------------------------------------------------------------------

                          Pierre Le Sidaner

                     Observatoire de Paris - PSL

Directeur de la Direction Informatique de l'Observatoire

Directeur technique de Paris Astronomical Data Centre

tel : 01 40 51 20 82

77 Av Denfert Rochereau 75014 Paris

mailto:pierre.lesidaner at observatoiredeparis.psl.eu

http://dio.obspm.fr<http://dio.obspm.fr/>  http://padc.obspm.fr<http://padc.obspm.fr/>

--------------------------------------------------------------------------

This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo at esa.int).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/registry/attachments/20230714/cba02178/attachment-0001.htm>