[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20030203:changing idd relay machine

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20030203:changing idd relay machine
  • Date: Mon, 3 Feb 2003 13:01:01 -0700 (MST)
Hi David, 

Congrats on the new machine!

What we often suggest is bringing up the new machine "gusher", and have it
run in parallel for a time with redwood. Once you are confident that
gusher is stable and getting all feeds desired, notify all those that feed
from you (from your ldmd.conf) to change to gusher from redwood. This will
allow some flexibility for the transition as both redwood and gusher can
offer the feed. Then notify the downstream folks of the "drop dead"
date/time for redwood and all should be feeding from gusher by that time.

Thats how we do it.

I am assuming this does not affect "striker"...;)

Cheers,

-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
COMET Case Study Library                      FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Mon, 3 Feb 2003, Unidata Support wrote:

> 
> Reply-to:David Knight <address@hidden>
> --------
> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >cc: address@hidden
> >From: David Knight <address@hidden>
> >Subject: chaning idd relay machine
> >Organization: UCAR/Unidata
> >Keywords: 200302031501.h13F18627520
> 
> Hi,
>     The time has come to change the machine we use for our IDD relay.
> To insure continuity of both our local data, and our downstream sites,
> we will probably want to run both idd machines in parallel for some time.
> 
> Is there a "best practices" writeup somewhere on the recommended procedure
> for transitioning from one IDD machine to another? I searched but
> could not find anything - maybe I didn't search hard enough...
> 
> Here is what I was thinking. Lets say we have the following setup
> snow - our primary upstream IDD data source
> redwood - our old IDD relay
> gusher - our new IDD relay
> 
> Can I set up redwood so that it makes requests to both snow and gusher?
> Similarly, can I set up gusher to make requests to both snow and redwood?
> Then ask snow to change their allow statements and be assured of
> continuous data feeds into both redwood and gusher? It seems like this
> should work, but, I want to make sure we are not missing anything.
> 
> Thanks
> David
> 
> David Knight
> Department of Earth and Atmospheric Sciences   Tel: (518)-442-4204
> University at Albany   ES-228                  Fax: (518)-442-4494
> Albany, NY  12222                              Email: address@hidden
> 
> 
> ------- End of Forwarded Message
> 
>