DataSpace enables you to configure Global Access between clusters that are connected to DataSpace. The advantage of configuring global access using DataSpace is that you can do it with a single short configuration flow. DataSpace creates and runs all of the tasks required on all of the clusters, without your needing to configure each replication peer, protected path and destination on each cluster in a separate configuration flow.
In the VAST Web UI, open the DataSpace page (select DataSpace from the left navigation menu.)
Make sure that the cluster that hosts the path that you want to make accessible is connected to DataSpace and that all destination clusters are also connected. To connect clusters, see Connecting Clusters to DataSpace.
From the Add New menu at the top right of the page, select Create new Global Access.
In the Source pane on the left, click Define a Source.
Provide the following details for the source path:
Cluster
Select the source cluster from the dropdown.
Tenant
From the dropdown, select the tenant on the source cluster where the source path resides.
Path
Specify the source path, relative to the tenant. For example,
/source. This path must already exist.Click Add Source.
In the Destination pane on the right, click Define destinations.
Provide the following details for a destination path:
Cluster
Select a connected cluster from the dropdown, to be a destination cluster.
Tenant
From the dropdown, select the tenant on the selected cluster under which you want to create the destination path.
Path
Specify a destination path, relative to the tenant. For example,
/destination. This must not be an existing path.Click Add Destination.
If you wish to add another destination, click Add Another and repeat steps 8 and 9.
If you want to change the lease expiration time, click the edit icon (
) in the Global Access box and change it to the preferred expiration time. To set the time, enter a number in the field provided and select the time units from the dropdown. Click Save.The lease expiration time is the duration for which data that was already requested at any of the destination paths can be read locally from cache without the destination peer requesting it from the source peer. When the lease expires, the cache is invalidated and the next read request for the data is requested again from the source peer.
Click Create.
The creation task is initiated. You can monitor it from the Tasks tab.