[CONDUIT #HGF-659268]: setting up new CONDUIT feed

Hi Carissa,

re:
> I made your suggested changes and there are no other ALLOW's in the
> table besides what I listed below.

OK, thanks.

re:
> So to make sure I am clear, are you
> suggesting a change to the PSU entry? Or is what you provided below what
> you had meant?

Yes, I am suggesting a change to the PSU entry (the list I provided included
this change).

The list of ALLOW entries I sent was based on the ones you had sent being
the _only_ ALLOW entries in the file.  The list you just included:

> ALLOW   ANY     ^((localhost|loopback)|(127\.0\.0\.1\.?$))
> #
> # Give permission to the Unidata Program Center
> ALLOW   ANY     ^[a-z].*\.unidata\.ucar\.edu\.?$
> #
> # CONDUIT hosts
> allow   ANY     ^conduit(|[0-9])\.unidata\.ucar\.edu\.?$        .* 
> ^data2/TIGGE_resend
> allow   ANY     ^atm\.cise-nsf\.gov\.?$ .*      ^data2/TIGGE_resend
> allow   ANY     ^idd\.aos\.wisc\.edu\.?$        .*      ^data2/TIGGE_resend
> allow   ANY     ^flood\.atmos\.uiuc\.edu\.?$    .*      ^data2/TIGGE_resend
> allow   ANY     ^(idd-ingest|iddrs3)\.meteo\.psu\.edu\.?$       .* 
> ^data2/TIGGE_resend
> #
> # TIGGE hosts
> #
> # NCAR
> ALLOW   ANY     ^dataportal\.ucar\.edu\.?$      .*
> ALLOW   ANY     ^datagrid\.ucar\.edu\.?$        .*
> # ECMWF
> ALLOW   ANY     ^193\.61\.196\.74\.?$   .*
> # Test from vm-lnx-ldmex
> ALLOW   ANY     ^140\.90\.100\.93\.?$   .*

is different from what you sent previously.  In particular, the catch-all
ALLOW for all machines in the unidata.ucar.edu domain negates the need for
a separate entry for machines named conduit* (e.g., conduit, conduit0, ...,
conduit9).

We would like you to keep the catch-all ALLOW for machines from the
unidata.ucar.edu domain (!); make the change to the PSU machine, and tighten-up
the name regular expression for the other machines. The full list of ALLOWs
would then be:

#
ALLOW ANY ^((localhost|loopback)|(127\.0\.0\.1\.?$))

#
# Give permission to the Unidata Program Center
ALLOW ANY ^[a-z].*\.unidata\.ucar\.edu\.?$

#
# non-unidata.ucar.edu CONDUIT hosts
allow ANY ^atm\.cise-nsf\.gov\.?$ .* ^data2/TIGGE_resend
allow ANY ^idd\.aos\.wisc\.edu\.?$ .* ^data2/TIGGE_resend
allow ANY ^flood\.atmos\.uiuc\.edu\.?$ .* ^data2/TIGGE_resend
allow ANY ^(idd-ingest|iddrs3)\.meteo\.psu\.edu\.?$ .* ^data2/TIGGE_resend

#
# TIGGE hosts
#

# NCAR
ALLOW ANY ^dataportal\.ucar\.edu\.?$ .*
ALLOW ANY ^datagrid\.ucar\.edu\.?$ .*

# ECMWF
ALLOW ANY ^193\.61\.196\.74\.?$ .*

# Test from vm-lnx-ldmex
ALLOW ANY ^140\.90\.100\.93\.?$ .*

re:
> As for memory, we have about 46G free, without LDM started yet. Do you
> still feel comfortable with 20G?

Yes.  We are running our idd.unidata.ucar.edu cluster real servers with
20 GB queues, and they work nicely.  I must add, however, that we are
running current Fedora versions of Linux, not RedHat Enterprise.  Because
of this difference, especially if you are running version 5 of RHEL,
testing will be needed to make sure that the large queues work OK.
The only reason I bring this up is that at least one Unidata university
site tried running Scientific Linux with a 20 GB queue, and he had
problems.  The problem went away, however, when he switched to the
CentOS distribution of Linux (which _is_ RedHat Enterprise), but I
believe he is running version 6, not 5.

re:
> ldm@za-ldm0:~$ free -m
> total       used       free     shared    buffers     cached
> Mem:         48390        792      47598          0        242        230
> -/+ buffers/cache:        319      48071
> Swap:        15258          0      15258

OK.

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: HGF-659268
Department: Support CONDUIT
Priority: Normal
Status: Closed