Task #9205: Create alias for sdi service - 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

Task #9205

closed

Create alias for sdi service

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

Status:

Closed

Priority:

High

Assignee:

_InfraScience Systems Engineer

Category:

Other

Target version:

SDI-nodes management

Start date:

Jul 06, 2017

Due date:

% Done:

100%

Estimated time:

Infrastructure:

Production

Description

Please, create an alias "sdi.d4science.org" for the VM sdi-d4s.d4science.org.
Certificate should be valid for this alias as well.

History
Notes
Property changes

Actions

Copy link

Updated by Leonardo Candela almost 8 years ago

Assignee changed from _InfraScience Systems Engineer to Pasquale Pagano

@pasquale.pagano@isti.cnr.it I'm wondering we should go for the proposed names or we should use a different approach.

According to my understanding we created:

data.d4science.org to be the access point for all the data / datasets managed by D4Science
services.d4science.org to be access point for all the services managed by D4Science

From these two basic names the rest (specialization for data and services) should come either

by using prefixes, e.g. sdi.services.d4science.org
by using "/" e.g. services.d4science.org/SDI

I would like to have an agreed and uniform strategy. Please, bear with my if this "agreement" is already there. I personally prefer the "/" based approach.

Actions

Copy link

Updated by Pasquale Pagano almost 8 years ago

Well, i think that we never adopted the services.d4science.org base url. The trend since a couple of months is to use names for the service as first citizen, thus sdi.d4science.org will point to an HA proxy that will then use one of the available sdi instances.

The glue is done via 'd4science.org'. Is it a problem?

Actions

Copy link

Updated by Leonardo Candela almost 8 years ago

There is no technical issue yet I would like having some homogeneity in naming. Moreover, I'm realising that I might be confusing two concepts: server naming with service base URLs. I'll make a try with another service we have, i.e. the catalogue:

catalogue service URL is https://services.d4science.org/catalogue
catalogue server name is ckan-d4s.d4science.org

We already faced some issues with such naming and now are relying on a resolver http://data.d4science.org/ctlg ...

Dunno what is the plan with sdi, actually if sdi stands for Spatial Data Infrastructure I'm even more confused because (AFAIK) this concept is actually a set of services ...

Actions

Copy link

Updated by Fabio Sinibaldi almost 8 years ago

Hi Leo, the SDI Service is a gCube Service that offers REST API for the management of the SDI itself and for most common use cases involving SDI resources exploitation. It is described here https://gcube.wiki.gcube-system.org/gcube/SDI-Service.

Actions

Copy link