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

[CONDUIT #RFO-442890]: GFS upgrade

Hi Carissa,

re:
> We believe that this should be working now, and until you point to the new
> IP you shouldn't be seeing any data.

OK.

re:
> So we had to change game plans a
> little bit, we have taken conduit3 out of the College Park/NCWCP pool. I
> added the GFS 0p25 and see it was inserted:
> 
> + echo '161910: [10975]: conduit.sh: end ssh vm-lnx-conduit3 -l ldm
> ncep_bin/gribinsert.sh
> /home/ftp/pub/data/nccf/com/gfs/para/gfs.2014122312/gfs.t12z.pgrb2.0p25.f120
> NMC2'
> 161910: [10975]: conduit.sh: end ssh vm-lnx-conduit3 -l ldm
> ncep_bin/gribinsert.sh
> /home/ftp/pub/data/nccf/com/gfs/para/gfs.2014122312/gfs.t12z.pgrb2.0p25.f120
> NMC2
> + '[' 0 '!=' 0 ']'
> + exit 0
> 
> and in a watch
> 
> Dec 23 16:21:44 pqutil INFO:   506005 20141223162143.935 CONDUIT 232
> data/nccf/com/gfs/para/gfs.2014122312/gfs.t12z.pgrb2.0p25.f129
> !grib2/ncep/GFS/#000/201412231200F129/DWPK/2 m HGHT! 000232
> Dec 23 16:21:44 pqutil INFO:   732338 20141223162143.968 CONDUIT 233
> data/nccf/com/gfs/para/gfs.2014122312/gfs.t12z.pgrb2.0p25.f129
> !grib2/ncep/GFS/#000/201412231200F129/RELH/2 m HGHT! 000233

OK, good.

re:
> The firewall rules should all be in place for all unidata machines. Please
> point to 140.90.101.91.

I just tried a 'notifyme' from the machine on which we will be doing the
testint, and it looks like we are not allowed through a firewall:

% notifyme -vl- -f CONDUIT -h 140.90.101.91
Dec 23 18:32:47 notifyme[9006] NOTE: Starting Up: 140.90.101.91: 
20141223183247.517 TS_ENDT {{CONDUIT,  ".*"}}
Dec 23 18:32:47 notifyme[9006] NOTE: LDM-5 desired product-class: 
20141223183247.517 TS_ENDT {{CONDUIT,  ".*"}}
 (nothing afterwards, so we are not getting through)

The machine we are coming from is:

128.117.149.100 <-> lead.unidata.ucar.edu

re:
> Can you remind me of the plan going forward? 

We want to do some testing before sending out a note to the top level
CONDUIT relay sites and then to the CONDUIT users.  The reasoning is
that we have to verify that we can handle the data and know all of
the changes that users will need to make before worrying them about
a change in CONDUIT content.  Also, we have to verify that the users
actually want us to relay the 0.25 deg GFS fields ** in place of ** the
0.5 deg GFS fields (this may seem like a no brainer, but experience
has demonstrated that we can not take the users' wishes for granted!).

re:
> Have the users been notified
> of the filename change yet?

No, they have not been notified of any change.

Just to make sure that we are on the same page:  the file name change
you are referring to is relevant for the 0.25 deg GFS fields, correct?
If it is relevant for the 0.5 deg fields, then we will need to inform
the users _soon_.

re:
> And we are just waiting to find out what grids
> we are going to send out? Thanks.

Yes, we are waiting on:

1) knowing that we and the CONDUIT top level relay sites can handle
   the increased volume that will be realized by replacing the 0.5 deg
   GFS with 0.25 deg GFS

2) knowing what changes users will need to make in their CONDUIT
   pattern-action file actions

3) knowing that the CONDUIT users actually want to get the 0.25 deg
   GFS fields in stead of the 0.5 deg fields

It is my position that it is not prudent to canvass the users before
knowing that the higher volume data can successfully be relayed
in the IDD.  It is also my position that we need to know all of the
changes that end-users will need to make to their processing before
canvassing the users.  Finally, it is our job to make sure that the
users actually want the change from 0.5 deg GFS to 0.25 deg GFS.
It is, of course, possible that some of the users will request that
the 0.5 deg GFS continue to be relayed AND that 0.25 deg GFS also
be relayed.  This has implications for the volume/number of products
in CONDUIT and the ability of sites that want everything to be able
to handle the volume.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: RFO-442890
Department: Support CONDUIT
Priority: Normal
Status: Closed