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.
Hei,we are currently using thredds in two project, each in a machine on it's own. We expect to have a several more thredds-projects in the near future. The projects have partly shared, partly separated data, and the access-permissions to data is generally different for each project.
I would like to hear some experience about administration of thredds in such an environment. I can currently think of three possible solutions:
a) all data shared on a nfs-server, one thredds-server per project, configured to use the data on the server. Thredds installation should be integrated in the machine-setup, i.e. debian-packages in our case.
b) one thredds server for all projects, with group-policies for each projectc) one (internal) thredds server per data-pool, one thredds-server per project, configured to access the data from other each internal thredds server.
We will also need to use a thredds version which enables 'rotated latitude-longitude' data (thredds 4). Will there soon be a stable version? Or do we need to run a alpha version of thredds?
Best regards, Heiko -- Dr. Heiko Klein Tel. + 47 22 96 32 58 Development Section / IT Department Fax. + 47 22 69 63 55 Norwegian Meteorological Institute http://www.met.no P.O. Box 43 Blindern 0313 Oslo NORWAY
thredds archives: