[conduit] 20140519: upcoming change to NOAA/NCEP top level relay for CONDUIT products

Unidata CONDUIT Users:

On Wednesday, May 28 the new NOAA/NCEP top level IDD relay cluster
conduit.ncep.noaa.gov will replace ncepldm4.woc.noaa.gov as the primary
injection site/top level distributor of CONDUIT data in the IDD.

Sites receiving CONDUIT data from Unidata community relay sites (e.g.,
idd.meteo.psu.edu, idd.tamu.edu, idd.aos.wisc.edu, flood.atmos.uiuc.edu,
and idd.unidata.ucar.edu) do NOT have to make any changes to their
~ldm/etc/ldmd.conf REQUEST line(s) for CONDUIT.

Impacts of the switchover:

Negative:

- the only potentially negative impact of the switchover is a change
  in the Product IDs for NDFD products

  NDFD Product IDs for products originating from the current IDD
  top level, ncepldm4.woc.noaa.gov, contain the clause 'data/ndfd'.
  After the change, this clause will change to 'data2/ndfd'.

  NOTE: there are NDFD products with both flavors of Product IDs
  currently flowing in CONDUIT.  Sites that are using 'data/ndfd' in
  their ~ldm/etc/ldmd.conf REQUEST line(s) and/or LDM pattern-action
  file action(s) are advised to update those entries well in advance of
  the switchover on May 28.  Please keep in mind that changes made in
  ~ldm/etc/ldmd.conf require an LDM restart before they become active.

Positive:

- the real server nodes in the new top level relay cluster
  conduit.ncep.noaa.gov are 64-bit machines that have significantly
  more system memory than the 32-bit real server nodes in the current
  top level relay cluster ncepldm4.woc.noaa.gov

  The increase in system memory on the new top level relay backends
  will allow more data to be added to CONDUIT in the future.  This
  will eliminate the restriction of not being able to add significantly
  more data to CONDUIT due to the limited size of the LDM queues
  on the current relay cluster backends.

We believe that the switch to the new top level relay will be a great
boon to recipients of CONDUIT data!

Please send any questions/comments to support-conduit@xxxxxxxxxxxxxxxxx

Cheers,

Unidata User Support
--
********************************************************************** <
Unidata User Support                              UCAR Unidata Program <
(303)497-8643                                            P.O. Box 3000 <
support@xxxxxxxxxxxxxxxx                             Boulder, CO 80307 <
---------------------------------------------------------------------- <
Unidata Web Support               http://www.unidata.ucar.edu/support  <
********************************************************************** <