Story #2008
Consistent mechanism for a client to discover a CN for an environment
100%
Description
There is a need for a consistent way to define the root of each environment. Given the Root URL of a DataONE environment, a client can discover all it needs to know to interact with services available there. e.g. For the sandbox environment, a client may connect to "cn-sandbox.dataone.org" which should point to one of the sandbox CN implementations. From that, the client could pull the node registry and discover nodes and services available in that environment.
suggest:
Production: cn.dataone.org (RR DNS pointing to one of cn-ucsb-1, cn-unm-1, or cn-orc-1)
Staging: cn-staging.dataone.org
Sandbox: cn-sandbox.dataone.org
Development: cn-dev.dataone.org
Client instances should take a CN address as a parameter, this would be something that resolves to a CN baseURL, which could be a direct link to a CN, or an indirect link via the RR DNS mechanism.
History
#1 Updated by Dave Vieglais almost 11 years ago
- Status changed from New to Closed
- Start date deleted (
2011-11-08) - translation missing: en.field_remaining_hours set to 0.0
This has been the process for while now.