Revision 6994
Added by ben leinfelder almost 13 years ago
| metacat.properties | ||
|---|---|---|
| 523 | 523 |
dataone.replicationpolicy.default.preferredNodeList= |
| 524 | 524 |
dataone.replicationpolicy.default.blockedNodeList= |
| 525 | 525 |
|
| 526 |
# overall services (TODO: mn vs. cn?) |
|
| 527 |
dataone.mn.services.enabled=true |
|
| 528 |
dataone.mn.registration.submitted=false |
|
| 529 |
|
|
| 526 | 530 |
# state which versions of each MN tier service are availalble |
| 527 | 531 |
dataone.mnCore.serviceAvailable=true |
| 528 | 532 |
dataone.mnCore.serviceVersion=v1 |
Also available in: Unified diff
dataone configuration and registration enhancements:
include flag to disable D1 services, currently only the MN side enforces thisoften this is a client cert issue (at least for my testing)-do not allow multiple registration attempts if we have just submitted and are awaiting Node verification by the CN.
-do not allow configuration "bypass" if D1 settings have been configured previously.
-do not allow update if Node verification is pending
-report errors that occur when calling cn.register or cn.updateNodeCapabilities -