D4Science Infrastructure

Questions. Do we need to run it behind the load balancer as we to for the tunaatlas services to have URLs like sdi-lab.d4science.org/{geoserver,geonetwork}?

The tunaatlas geoserver uses a jndi pool to connect to the database. Do we need to use a pool or a 'standard' connection, configured by the geoserver admin?

I can assume we need to replicate what provided for Tuna Atlas VRE, but we're better double check.
@emmanuel.blondel@fao.org , @julien.barde@ird.fr can you answer to Andrea's questions, please?

The question involves and affects also provisioning of GeoNetwork for SDI_Lab VRE (ticket #11035).

I would say one instance of Geoserver, no clusters/no load balance.
For JNDI, if you could set it up it could be useful for us. Let me know if it is possible

JNDI is ok. The provisioning is in progress.

Instance registered into IS, SDI-Service is correctly reporting configuration.

For this Geoserver, https is not yet available apparently... can we get it?

In addition, we would also need a SFTP access to geoserver data directory (for myself + @julien.barde@ird.fr in case he provided to you an ssh key).
Thanks in advance for that

Emmanuel Blondel wrote:

For this Geoserver, https is not yet available apparently... can we get it?

A certificate request is submitted every day, but because of the letsencrypt.org limits will need to wait for 2 or 3 days at least. That's not under our control.

Emmanuel Blondel wrote:

In addition, we would also need a SFTP access to geoserver data directory...

@emmanuel.blondel@fao.org just to double check : REST interface of data-transfer service is available on the instance and configured to operate on geoserver's data directory, so you can use that to retrieve and store files in it. Is SFTP access still needed?

For completeness :
here a GET request for the subfolder gwc (absolute path would be "/srv/geoserver_data/gwc" here is "geoserver/gwc" being "geoserver" a configurable placeholder) with optional flag "descriptor" for JSON representation - NB needs your token - :

http://geoserver-sdi-lab.d4science.org/data-transfer-service/gcube/service/REST/geoserver/gwc?gcube-token=****&descriptor=true

Yes, it's still needed; They are 2 different things. SFTP is required for the same arguments as for the VREs, we need to be able to arrange geoserver data dirs subsystems and o cleaning operation that we can't do through REST API. This is particularly needed in this context as about 30 newcomers will learn how to use the REST API, so I need behind the capacity to interven on the file system of geoserver.

@emmanuel.blondel@fao.org you can now access as user emmanuel.blondel. The geoserver data directory is /srv/geoserver_data

Hi @andrea.dellamico@isti.cnr.it apparently the SSL certificate was requested 13 days ago, do you know if we can get one quickly, the workshop started already, ideally we should get it this afternoon. Tomorrow 30 people will have to work with geoserver, and we would like to have it through the VRE as unique endpoint for users. Thanks in advance

@emmanuel.blondel@fao.org I'm really sorry but there's nothing I can do right now. The letsencrypt.org rules are becoming a limit, we are taking measures to change the situation but that will take some weeks.

Hello @andrea.dellamico@isti.cnr.it @fabio.sinibaldi@isti.cnr.it , yesterday i've been struggling with this geoserver while testing the REST API. First I've realized the version is not the same as the other geoserver requested (2.10.5 and not 2.10.0). Is it possible for you to quickly deploy 2.10.0 instead on this component? and check the configuration of the data directory, in comparison with the Aquaculture atlas (http://geoserver-aquacultureatlas.d4science.org/geoserver/).

At that time, it is impossible to use the API for pushing shapefiles in data directory, but for this I need 2.10.0 for the sake of the training, as later versions might have changed things, and I know 2.10.0 is ok since we are push well shapefiles in aquaculture atlas

Please let me know ASAP, as the training is today :-), thanks a lot for your help there

I usually install the latest minor because I assume there are bug fixes only. I'm going to install the 2.10.0 version now.

2.10.0 is running now.