NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Dear Community, Using the TDS User's Guide and Tutorial<https://docs.unidata.ucar.edu/tds/current/userguide/>, and the documentation in the unidata/thredds-docker:5.4 Docker image, I've been able to get very close to getting this to work here at the CloudSat DPC. But I am hung up on the TDS trying to change ownership of the files and directories in our Ceph data store. For our own security purposes, we have made all the files and directories on our data store read-only for any standard user and we don't need the TDS to be writing files to it. Again, we only need the OpenDAP service. Does anyone here know how to configure TDS to stop trying to chown all of our data files to the tomcat user, and to stop it from trying to change permissions on all of our files and directories? Any help would be greatly appreciated! Thanks, Jim On 1/11/24 14:46, Fluke,James wrote: ** Caution: EXTERNAL Sender ** Hello, Here at the CloudSat Data Processing Center, we would like to set up a THREDDS server to serve the publicly available CloudSat data files. Our main website is here<https://www.cloudsat.cira.colostate.edu/>. So far, we have successfully used the unidata/thredds-docker:5.4 Docker image to serve a small subset of our data files by mounting a test directory tree to /usr/local/tomcat/content/thredds/public/data in the container according to the instructions, but we doubt the default configuration in the image specifies the resource usage needed for our entire data set. We would like to continue using the Docker image for setting up the production server, but we could definitely use some help with the configuration. We have a idea of which configuration files to look at from the documentation, but some examples of other groups production configuration would be very helpful. And of course, we could also use help with authentication, which we would like to keep to username/password for simplicity. For production, we would be serving 1400358 files in 88147 directories - these are the low level directories that contain the files. Most of the files are HDF-EOS format which THREDDS can clearly read. At least the OPenDAP server can, and that is probably all we need to get started. Any help would be appreciated! Thanks, -- Jim Fluke Research Associate III Cooperative Institute for Research in the Atmosphere (CIRA) Colorado State University James.Fluke@xxxxxxxxxxxxx<mailto:James.Fluke@xxxxxxxxxxxxx> (970) 491-8990 _______________________________________________ NOTE: All exchanges posted to Unidata maintained email lists are recorded in the Unidata inquiry tracking system and made publicly available through the web. Users who post to any of the lists we maintain are reminded to remove any personal information that they do not want to be made public. thredds mailing list thredds@xxxxxxxxxxxxxxxx<mailto:thredds@xxxxxxxxxxxxxxxx> For list information or to unsubscribe, visit: https://www.unidata.ucar.edu/mailing_lists/
thredds archives: