Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CLARITY GeoServer URIs #66

Closed
p-a-s-c-a-l opened this issue Mar 25, 2020 · 6 comments
Closed

Update CLARITY GeoServer URIs #66

p-a-s-c-a-l opened this issue Mar 25, 2020 · 6 comments
Assignees
Labels
enhancement New feature or request question Further information is requested SHOWSTOPPER Feature or bug, that, if not addressed, renders the CSIS essentially useless STALLED Further Action is requested

Comments

@p-a-s-c-a-l
Copy link
Member

p-a-s-c-a-l commented Mar 25, 2020

Once the Export of Geoserver layers from MTG to ATOS has been completed. We have to update all GeoServer URIs of respective resources. AFAIK @therter knows how to do it directly on the level of the database.

Furthermore, I've noticed that there a two ATOS GeoServer instances:

http://services.clarity-h2020.eu:8080/ still seems to cause problems with include in report functionality, since TLS is not enabled for services.clarity-h2020.eu.

Question: Will we move everything to geoserver.myclimateservice.eu? If not, https has to be supported for services.clarity-h2020.eu.

@p-a-s-c-a-l p-a-s-c-a-l added enhancement New feature or request question Further information is requested labels Mar 25, 2020
@p-a-s-c-a-l p-a-s-c-a-l added this to Backlog: Low Priority in T1.3 Climate Services Co-creation via automation Mar 25, 2020
@p-a-s-c-a-l p-a-s-c-a-l changed the title Update CLARTIY GeoServer URI Update CLARITY GeoServer URIs Mar 25, 2020
@negroscuro
Copy link
Contributor

negroscuro commented Mar 25, 2020

We plan to move to the new instance so probably it does not worth the effort to secure the old one.

@p-a-s-c-a-l
Copy link
Member Author

p-a-s-c-a-l commented Apr 21, 2020

What is now the correct instance for all layers (hazard + hazard-le input layers)? https://geoserver.myclimateservice.eu/ ?

We have to make the changes in the data packages before we set up the synchronisation between DEV and PROD instance of CSIS and also in EMIKAT which currently calls http://services.clarity-h2020.eu:8080

@p-a-s-c-a-l p-a-s-c-a-l added the SHOWSTOPPER Feature or bug, that, if not addressed, renders the CSIS essentially useless label Apr 21, 2020
@p-a-s-c-a-l p-a-s-c-a-l moved this from Backlog: Low Priority to In Progress in T1.3 Climate Services Co-creation Apr 21, 2020
@p-a-s-c-a-l p-a-s-c-a-l added the STALLED Further Action is requested label May 4, 2020
@p-a-s-c-a-l
Copy link
Member Author

Question to @DanielRodera & @maesbri

What is now the correct instance for all layers (hazard + hazard-le input layers)? https://geoserver.myclimateservice.eu/ ?

@therter can prepare the update statements

@therter
Copy link

therter commented May 13, 2020

@therter can prepare the update statements

The following update statements will adjust the geoserver urls, if only the url base must be changed.

update node__field_reference_path set field_reference_path_value = replace(field_reference_path_value, 'https://clarity.meteogrid.com/', 'https://geoserver.myclimateservice.eu/') where position('https://clarity.meteogrid.com/' in field_reference_path_value) = 1;
update node__field_reference_path set field_reference_path_value = replace(field_reference_path_value, 'http://services.clarity-h2020.eu:8080/', 'https://geoserver.myclimateservice.eu/') where position('http://services.clarity-h2020.eu:8080/' in field_reference_path_value) = 1;

@p-a-s-c-a-l
Copy link
Member Author

@therter this is done, right?
Did you also check for other services.clarity-2020.eu appearances?

@therter
Copy link

therter commented Jun 30, 2020

@therter this is done, right?

Yes, this is done and on the maintenance site, the url was also corrected.

T1.3 Climate Services Co-creation automation moved this from In Progress to Done Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested SHOWSTOPPER Feature or bug, that, if not addressed, renders the CSIS essentially useless STALLED Further Action is requested
Projects
No open projects
Development

No branches or pull requests

5 participants