VM Creation #7855: Provide node to install GeoFence application - D4Science Infrastructure - D4science

Actions

Copy link

VM Creation #7855

closed

Provide node to install GeoFence application

Added by Fabio Sinibaldi over 8 years ago. Updated over 8 years ago.

Status:

Closed

Priority:

High

Assignee:

_InfraScience Systems Engineer

Target version:

SDI-Security

Start date:

Mar 27, 2017

Due date:

% Done:

100%

Infrastructure:

Development

RAM:

CPU:

DiskSpace:

Smartgears:

Yes

Smartgears Version:

latest

Application Instructions:

Smartgears scopes:

/gcube
/gcube/devsec
/gcube/devsec/devVRE
/gcube/devNext
/gcube/devNext/NextNext

Applications list and version:

Applications context path:

/geofence

External storage data disk:

Smartgears auth connector:

data transfer enabled:

PostgreSQL database:

Number of VMs:

Actions

Copy link

Updated by Andrea Dell'Amico over 8 years ago

Which kind of node? a smartgears one?

Resources? cpu, ram, disk space?
scopes list?

Actions

Copy link

Updated by Fabio Sinibaldi over 8 years ago

The node needs to be a SmartGears with small hw requirements.

Scopes should be :
/gcube
/gcube/devsec/
/gcube/devsec/devVRE
/gcube/devNext
/gcube/devNext/NextNext

Suggested name : geofence-d-d4s.d4science.org

Actions

Copy link

Updated by Andrea Dell'Amico over 8 years ago

IP is going to be 146.48.123.90

Actions

Copy link

Updated by Andrea Dell'Amico over 8 years ago

Tracker changed from Task to VM Creation
RAM set to 3
CPU set to 2
DiskSpace set to 12
Smartgears set to Yes
Smartgears Version set to latest
Smartgears scopes updated (diff)
Applications context path updated (diff)

Actions

Copy link

Updated by Andrea Dell'Amico over 8 years ago

Status changed from New to In Progress

Actions

Copy link

Updated by Andrea Dell'Amico over 8 years ago

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

The VM is ready.
The reverse proxy has been configured to redirect the http requests to https, while the smartgears is still publishing itself on port 80.

Actions

Copy link

Updated by Fabio Sinibaldi over 8 years ago

There seems to be a mismatch between container tokens and declared tcp port.
In ghn.log I can see messages like

WARN ContainerManager: the token d555ade1-1a1c-4b08-bb59-74f5837f6807-98187548 cannot be used, the client id geofence-d-d4s.d4science.org:443 resolved with the token is not the same of the one specified in this container

for every token in container.xml.
Resolving token d555ade1-1a1c-4b08-bb59-74f5837f6807-98187548 we have
AuthorizationEntry [clientInfo=ContainerInfo [host=geofence-d-d4s.d4science.org, port=443], context=/gcube, map=null, qualifier=TOKEN, policies=[]]

while in container.xml the declared port is 80.

Actions

Copy link

Updated by Andrea Dell'Amico over 8 years ago

I think I've understood the problem. I'll let you know asap.

Actions

Copy link

Updated by Andrea Dell'Amico over 8 years ago

smartgears deploys correctly now. The logs say that the geofence app fails.

Actions

Copy link

#10

Updated by Fabio Sinibaldi over 8 years ago

Smartgears scopes updated (diff)

GeoFence application has been now integrated with SmartGears. Requested action will be reported on wiki for further automation of the process.

There is just a misconfiguration in container.xml file.
As I wrongly asked in this ticket, a token has been generated for scope "/gcube/devsec/". The last '/' character prevents the service to retrieve the related scope map. I'm updating this ticket with the right scope names. Please evaluate if any further action/check needs to be implemented/performed.

Actions

Copy link

#11