Currently, there is only one connection object with one remote storage and therefore one remote storage in the simulation (besides the very hard coded "dummycluster" work-around. This concept has to be made more flexible, as in reality not all computing resources share the same network connection to a remote storage.
A new approach would be to create remote storage from configurations similarly to how caches are created. Drones, caches and remote storage could that are connected could then be grouped to newly introduced site objects allowing more complex set ups. However, it would have to be ensured in this case that caches and remote storage can be part of multiple sites.
Currently, there is only one connection object with one remote storage and therefore one remote storage in the simulation (besides the very hard coded "dummycluster" work-around. This concept has to be made more flexible, as in reality not all computing resources share the same network connection to a remote storage. A new approach would be to create remote storage from configurations similarly to how caches are created. Drones, caches and remote storage could that are connected could then be grouped to newly introduced
site
objects allowing more complex set ups. However, it would have to be ensured in this case that caches and remote storage can be part of multiple sites.