[db-wg] Whois Update Server Migration

thanks Ed


      From: Edward Shryane <eshryane at ripe.net>
 To: denis walker <ripedenis at yahoo.co.uk> 
Cc: Database WG <db-wg at ripe.net>
 Sent: Tuesday, 20 March 2018, 21:23
 Subject: Re: [db-wg] Whois Update Server Migration
   
Hi Denis,
we plan to switch from the current Whois update server, to a different server, sometime tomorrow evening. We expect a few minutes downtime for updates.
On the update server, a read-only flag will prevent writes to the database. We will confirm all updates are replicated to the new server before switching. 
On each Whois server, maintenance mode will be turned on, which will cause incoming Syncupdates and REST API updates to be rejected (503 Service Unavailable).
Incoming mailupdates will be queued up, and will be processed once maintenance mode is turned off.
We will announce to the working group again when the downtime has ended, and updates will be accepted again.
RegardsEd ShryaneRIPE NCC



On 20 Mar 2018, at 02:34, denis walker <ripedenis at yahoo.co.uk> wrote:
Hi Ed
Thanks for the notice. Can you explain in a little more detail what will happen if anyone submits an update during this downtime, or for any automated scripts that send in updates?
cheersdenisco-chair DB WG

      From: Edward Shryane via db-wg <db-wg at ripe.net>
 To: Database WG <db-wg at ripe.net> 
 Sent: Monday, 19 March 2018, 17:20
 Subject: [db-wg] Whois Update Server Migration
  
Dear Working Group,

on Wednesday 21st March, we plan to migrate the Whois Update Server to a new configuration. This will cause a short downtime for Whois updates. Queries will not be affected.

We will also create a Service Announcement on the RIPE NCC website.

Regards,
Ed Shryane
RIPE NCC




   



   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20180320/ecb72b99/attachment.html>