VM Creation #11126: Access to a VM with Geoserver v2.10 istance - D4Science Infrastructure - D4science

Custom queries

03. VRE Plan
04. All Projects Deliverables
04. All Projects Milestones
06. D4Science Projects Activities
All open Issues
D4Science Infrastructure Upgrade
My InProgress Tasks
My Paused Tasks
My Watched Tasks
Not Closed Assigned To Me
Not Closed Assigned To Me (No Releases, No Project Tasks)
Not Closed Opened by Me
Open Issues
Upgrade Plan
Upgrade Plan Clear

Actions

Copy link

VM Creation #11126

closed

Access to a VM with Geoserver v2.10 istance

Added by Vincenzo Terrano over 7 years ago. Updated over 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

_InfraScience Systems Engineer

Target version:

WP07

Start date:

Feb 07, 2018

Due date:

% Done:

100%

Infrastructure:

Development

RAM:

CPU:

DiskSpace:

Smartgears:

Yes

Smartgears Version:

latest

Application Instructions:

Smartgears scopes:

/gcube/devNext/NextNext

Applications list and version:

geoserver 2.10

Applications context path:

geoserver

External storage data disk:

Smartgears auth connector:

data transfer enabled:

Yes

PostgreSQL database:

Yes

Number of VMs:

Description

In order to test GeoServer migration, a VM with GeoServer v2.10 istance is required.

Related issues

Related to D4Science Infrastructure - Task #10956: Clone geoserver.d4science.org

Closed

_InfraScience Systems Engineer

Jan 17, 2018

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Andrea Dell'Amico over 7 years ago

Related to Task #10956: Clone geoserver.d4science.org added

Actions

Copy link

Updated by Andrea Dell'Amico over 7 years ago

Tracker changed from Support to VM Creation
RAM set to 4
CPU set to 2
DiskSpace set to 20
Smartgears set to Yes
Applications list and version updated (diff)
Applications context path updated (diff)
data transfer enabled set to Yes
PostgreSQL database set to Yes
Number of VMs set to 1

Do you also need all the old data?

Actions

Copy link

Updated by Andrea Dell'Amico over 7 years ago

What smartgears scopes?

Actions

Copy link

Updated by Ciro Formisano over 7 years ago

Dear Andrea,
Vincenzo and I do not know exactly if there will be any problem by choosing a certain scope. I would suggest to use nextnext of eng environment, but I would also ask @fabio.sinibaldi@isti.cnr.it if this could be a good solution.

Actions

Copy link

Updated by Fabio Sinibaldi over 7 years ago

For the sake of migration tests there are no constraints in scopes, thus I support the suggestion of /gcube/devNext/NextNext

Actions

Copy link

Updated by Andrea Dell'Amico over 7 years ago

Status changed from New to In Progress
Smartgears Version set to latest
Smartgears scopes updated (diff)

hostname and IP are going to be: geoserver2-d.dev.d4science.org 146.48.122.252

Actions

Copy link

Updated by Andrea Dell'Amico over 7 years ago

Status changed from In Progress to Feedback
% Done changed from 0 to 100

The VM is up, with a geoserver 2.10.5 installed and configured. All the databases descripted in #10956 are accessible as user reader

Actions

Copy link

Updated by Vincenzo Terrano over 7 years ago

The "GEOSERVER_DATA_DIR" environment variable has to point to /home/gcube/tomcat/webapps/geoserver/data folder.
I can't add data to the default path /srv/geoserver_data or change the path inside /etc/default/tomcat-instance-9000.local

Actions

Copy link

Updated by Andrea Dell'Amico over 7 years ago

Vincenzo Terrano wrote:

The "GEOSERVER_DATA_DIR" environment variable has to point to /home/gcube/tomcat/webapps/geoserver/data folder.
I can't add data to the default path /srv/geoserver_data

Why not? that directory is owned by the gcube user, nothing prevents you to write there. The new geoservers are going to have the data directory outside the application directory, anyway.

Actions

Copy link

#10