[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20040322: CONDUIT Feed Requests
- Subject: Re: 20040322: CONDUIT Feed Requests
- Date: Fri, 02 Apr 2004 16:24:44 +0000
Tom,
FSL's new conduit server arrangement is operational.
Please feel free to remove the old allow line for eldm2
at your convenience.
Thanks,
-Bob L.
>
> Thanks, Tom. We'll be sure to only request from
> one host or the other. We intend to discontinue the
> original eldm2 client when we go live with the new
> systems. We won't make the switch until next week.
>
> Bob Lipschutz
> NOAA Forecast Systems Lab
> 303-497-6636
>
>
> > >From: "Patrick D Hildreth" <address@hidden>
> > >Organization: NOAA/FSL
> > >Keywords: 200403222159.i2MLxIrV007646 IDD CONDUIT
> >
> > Patrick,
> >
> > >We have set up two new machines we would like to request CONDUIT data for.
> > >They are :
> > >
> > >conduita.fsl.noaa.gov - 137.75.133.40
> > >conduitb.fsl.noaa.gov - 137.75.133.41
> >
> > OK. I checked forward and reverse name lookup for both of these machines
> > and everything looks good.
> >
> > >These are a high availability pair that will become our primary CONDUIT
> > >machines in the long term, but we'd like to keep the existing eldm2 allow
in
> > >place until we can complete the transition to these new machines.
> >
> > OK. Hopefully, the transition will be a fast one.
> >
> > >Additionally we were wondering if it would be acceptable to have both
> > >machines ingesting concurrently.
> >
> > We would rather feed a single machine at a site and then have the site
> > (you) configure that machine to relay data to other machines at the site.
> >
> > >If not we can just perform ingest on
> > >the primary member of the pair and switch ot the other as needed for
> > >failovers.
> >
> > I would setup conduita to feed CONDUIT from thelma, and conduitb to
> > feed from conduita. At the same time, I would put a commented out
> > request line in the ~ldm/etc/ldmd.conf file on conduitb that,
> > when uncommented, will request directly from thelma. In this way,
> > the queue on conduitb would be as full of current data as possible
> > when conduita is taken out of service.
> >
> > You may begin requesting the CONDUIT data from conduita whenever
> > you are ready.
> >
> > >Thanks!
> >
> > No worries.
> >
> > >Patrick Hildreth <address@hidden>
> > >NOAA/FSL/DSG
> >
> > Tom Yoksas
> > --
> > ***************************************************************************
*
> <
> > Unidata User Support UCAR Unidata Progra
m
> <
> > (303)497-8643 P.O. Box 300
0
> <
> > address@hidden Boulder, CO 8030
7
> <
> > ---------------------------------------------------------------------------
-
> <
> > Unidata WWW Service http://my.unidata.ucar.edu/content/support
> <
> > ---------------------------------------------------------------------------
-
> <
> > NOTE: All email exchanges with Unidata User Support are recorded in the
> > Unidata inquiry tracking system and then made publically available
> > through the web. If you do not want to have your interactions made
> > available in this way, you must let us know in each email you send to us.
>