Replication management
Replication mappings
Introduction
DCT 9.0.0 introduces the feature to differentiate between the replicated objects and original objects in case of a parent and replicated engines, both are registered with DCT.
Prerequisites
One parent and one replicated engine is required with few replicated dSources and VDBs.
User interface
Convenient separation between the replicated objects(VDB/dSource/environments) and original objects.
Users can filter the replicated object using the advanced filter.
All the actions on the replicated objects are disabled.
The status of the replicated objects are N/A.
On the VDB provisioning wizard, replicated objects(VDB/dSources) are marked as replicated.
API
Below are the list and search APIs, updated to return three additional fields (is_replica, namespace_id, namespace_name):
Sources
GET:/sources
GET:/sources/{sourceId}
POST:/sources/searchVDBs
GET:/vdbs
GET:/vdbs/{vdbId}
POST:/vdbs/searchdSources
GET:/dsources
GET:/dsources/{dsourceId}
POST:/dsources/searchCDBs
GET:/cdbs
GET:/cdbs/{cdbId}
POST:/cdbs/searchVCDBs
GET:/vcdbs
GET:/vcdbs/{vcdbId}
POST:/vcdbs/searchEnvironments
GET:/environments
GET:/environments/{environmentId}
POST:/environments/searchDataset-groups
GET:/groups
GET:/groups/{groupId}
POST:/groups/searchTimeflows
GET:/timeflows
GET:/timeflows/{timeflowId}
POST:/timeflows/searchPolicies
GET:/virtualization-policies
GET:/virtualization-policies/{policyId}
POST:/virtualization-policies/searchSnapshots
GET:/snapshots
GET:/snapshots/{snapshotId}
POST:/snapshots/search
Below are the three fields added in response of these APIs:
is_replica: Boolean telling that this object id replicated or not.namespace_id: This field will only come for replicated objects and is essentially thenamespace idof the replicated object.namespace_name: This field will only come for replicated objects and is essentially thenamespace nameof the replicated object.