Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#424 Use better name in orchestrator location

closed-fixed
HiLA (18)
5
2011-02-02
2011-02-02
Bjoern Hagemeier
No

Currently, all orchestrators are named the same. Although there may not be many orchestrators in an infrastructure, they become indistinguishable once there is more than one. Using the first part of the path of the EPR would be a good option.

E.g. the service orchestrator at https://zam025s01.zam.kfa-juelich.de:7701/ORCHESTRATOR/ServiceOrchestrator
would be names ORCHESTRATOR.

Discussion

    • status: open --> closed-fixed
     
  • There may still be issues if orchestrator "site" names are the same behind different gateways. However, this should then be solved by giving the orchestrator a "name" property or using a name from the EPR, which is currently not in there.