Task #7009

Do not publish ServiceEndpoint on parent scope

Added by Luca Frosini about 3 years ago. Updated about 3 years ago.

Status:RejectedStart date:Feb 08, 2017
Priority:HighDue date:
Assignee:Lucio Lelii% Done:

0%

Category:common
Sprint:zz - Smartgears Improvements & Fixes
Milestones:
Duration:

Description

The code used to publish the resource is:

ServiceEndpoint serviceEndpoint = new ServiceEndpoint();
// service enpoint fill


RegistryPublisher registryPublisher = RegistryPublisherFactory.create();
registryPublisher.create(serviceEndpoint);

History

#1 Updated by Luca Frosini about 3 years ago

  • Tracker changed from Bug to Task

#2 Updated by Lucio Lelii about 3 years ago

  • Status changed from New to Rejected

this is the expected behaviour on ServiceEndpoint.

#3 Updated by Luca Frosini about 3 years ago

  • Status changed from Rejected to In Progress
  • Subject changed from ServiceEndpoint are published also on parent scope to Do not publish ServiceEndpoint on parent scope

This behaviour was ought to discover the ServiceEndpoint on parent scope if not available in the current one (with authentication this is not possible any more).
I think should be changed to reflect the new paradigm of the other resources (i.e. HostingNode and RunningInstances).

for example the SmartExecutor create a Service endpoint for each scope and on root scope you can find each one.

#4 Updated by Pasquale Pagano about 3 years ago

Not sure to understand.

a) service endpoint and generic resources are not automatically propagated at registration time to VO and Root if registered at VRE level
b) service endpoint and generic resources are visible only if registered in the current scope at query time

a1) gcore endpoint and ghn resources are automatically propagated at registration time to VO and Root if registered at VRE level
b1) gcore endpoints are visible in the VRE scope at query time even if they are only registered at VO

#5 Updated by Lucio Lelii about 3 years ago

a) no, if you try to create a service endpoint from the resource monitor you can see that it is automatically propagated to the parent scopes.
b) yes

a1) it is not true with the new Smartgears services, only the gcore services maintain this behaviour
b1) yes

#6 Updated by Pasquale Pagano about 3 years ago

Summarising, we have these rules in place (reported again for documentation)

a) generic resources are NOT automatically propagated at registration time to VO and Root if registered at VRE level
b) generic resources are visible ONLY if registered in the current scope at query time

a1) service endpoints are automatically propagated at registration time to VO and Root if registered at VRE level
b1) service endpoints are visible ONLY if registered in the current scope at query time

a2) gCore service endpoints are automatically propagated at registration time to VO and Root if registered at VRE level
b2) gCore service endpoints are visible in the VRE scope at query time EVEN if they are only registered at VO

a3) SmartGears service endpoints are NOT automatically propagated at registration time to VO and Root if registered at VRE level
b3) SmartGears service endpoints are visible in the VRE scope at query time EVEN if they are only registered at VO

#7 Updated by Lucio Lelii about 3 years ago

  • Status changed from In Progress to Rejected

Also available in: Atom PDF