Task #9344: Remove the haproxy frontend listening on the 8080 port - D4Science Infrastructure - D4science

Actions

Copy link

Task #9344

closed

Remove the haproxy frontend listening on the 8080 port

Added by Andrea Dell'Amico almost 8 years ago. Updated over 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

_InfraScience Systems Engineer

Category:

System Application

Target version:

Production Jackrabbit Migration from Derby to PostgreSQL

Start date:

Sep 01, 2017

Due date:

% Done:

100%

Estimated time:

Infrastructure:

Production

Description

It was created to facilitate the migration to the new workspace configuration.

Actions

Copy link

Updated by Andrea Dell'Amico almost 8 years ago

Start date changed from Jul 21, 2017 to Sep 01, 2017

Actions

Copy link

Updated by Andrea Dell'Amico almost 8 years ago

Can we proceed? All the traffic should be on the standard http and https ports right now.

Actions

Copy link

Updated by Massimiliano Assante almost 8 years ago

Status changed from New to In Progress

I would say yes but i would like to hear the opinion of @gianpaolo.coro@isti.cnr.it and or @lucio.lelii@isti.cnr.it and @roberto.cirillo@isti.cnr.it on this first. If all the data miner nodes have been restarted since July then they already using the new URL. Is there any other service which is using the HomeLibrary REST API and was not restarted that you know of?

Actions

Copy link

Updated by Andrea Dell'Amico over 7 years ago

Massimiliano Assante wrote:

I would say yes but i would like to hear the opinion of @gianpaolo.coro@isti.cnr.it and or @lucio.lelii@isti.cnr.it and @roberto.cirillo@isti.cnr.it on this first. If all the data miner nodes have been restarted since July then they already using the new URL. Is there any other service which is using the HomeLibrary REST API and was not restarted that you know of?

Any news on this one?

Actions

Copy link

Updated by Roberto Cirillo over 7 years ago

Andrea Dell'Amico wrote:

Massimiliano Assante wrote:

I would say yes but i would like to hear the opinion of @gianpaolo.coro@isti.cnr.it and or @lucio.lelii@isti.cnr.it and @roberto.cirillo@isti.cnr.it on this first. If all the data miner nodes have been restarted since July then they already using the new URL. Is there any other service which is using the HomeLibrary REST API and was not restarted that you know of?

Any news on this one?

I think the Rstudio instances are using the HomeLibrary REST API (please @gianpaolo.coro@isti.cnr.it could you confirm?) and some rstudio instances were not restarted since June. I've checked rstudio1 (restarted 07 September) and ip-90-147-167-29.ct1.garrservices.it (restarted 05 June)

Actions

Copy link

Updated by Andrea Dell'Amico over 7 years ago

Roberto Cirillo wrote:

Andrea Dell'Amico wrote:

Massimiliano Assante wrote:

I would say yes but i would like to hear the opinion of @gianpaolo.coro@isti.cnr.it and or @lucio.lelii@isti.cnr.it and @roberto.cirillo@isti.cnr.it on this first. If all the data miner nodes have been restarted since July then they already using the new URL. Is there any other service which is using the HomeLibrary REST API and was not restarted that you know of?

Any news on this one?

I think the Rstudio instances are using the HomeLibrary REST API (please @gianpaolo.coro@isti.cnr.it could you confirm?) and some rstudio instances were not restarted since June. I've checked rstudio1 (restarted 07 September) and ip-90-147-167-29.ct1.garrservices.it (restarted 05 June)

The rstudio sessions load the home library functions from the users' .RProfile. The file was fixed the same day the new workspace went into production, but it's only loaded when a new session is been opened.
There's no way to know if any users did not closed their session since late July.

Actions

Copy link