Warning

Nightly releases are generated automatically from the latest source code and are intended for experimental purposes only. These builds may contain incomplete or untested features, bugs, or security vulnerabilities, and as such, are not for production use. Users should be aware that nightly releases may cause unexpected behavior, data loss, or system instability. Use of these releases is at the user's own risk, and it is advised to have adequate backups before testing. The software is provided as is with no guarantees or support.

How to transfer 3D Spaces between hubs

Set Up Datapools

instant3Dhub 3.10 introduces Datapools to streamline and unify how instant3Dhub retrieves and authorizes data. Datapools are configured via values.yaml. The configuration includes setting up the relevant URNs to other instant3Dhub instances / Datapools as well as authorization preferences.

More details and explanations can be found in the comments of the values.yaml or in our docs under URN Mapper Configuration.

Add Resources to 3D Space

Add resources to a 3D Space with the usual functions. As soon as resources are added to the 3D Space, the system uses the Datapool configuration to proxy data from responsible instances automatically.

Trigger 3D Space Transfer:

To make resources available on the local Hub, trigger the 3D Space Transfer via one of the two options:

  1. Via transferSession(): Use the transferSession() function to initiate the transfer. Refer to the documentation for detailed usage instructions: SessionStorageAPI

  2. Via Resource API: The Request part of the Resource is extended to support a clusterID parameter as part of each element. If no clusterID is given, the ID of the local instance is used. This implies caches will be transferred over if configuration points to another instant3Dhub instance being responsible for the data.

The system now starts to download the caches from the central Hub to the local Hub making the resources locally available.