Deployment information
This article outlines the hardware requirements, architecture and deployment of arivis Hub.
Introduction
VisionHub is based on a service architecture that allows flexible packaging and rollout scenarios for on-premises or cloud installations (see architecture deployment examples). A VisionHub installation can start with a single server or consist of an extendible, high-performance cluster of servers for different purposes. We propose customers to add at least one additional server when the goal for the VisionHub is scalable computation or 3D server-side rendering (SSR). This ensures that analysis workers or rendering load will not interfere with interactive user experience of the VisionHub frontend.
As not all VisionHub components can be completely restricted regarding memory and CPU/GPU usage, we propose to use dedicated servers for the VisionHub installation and not run other services/applications on these machines. Deployment on dedicated servers ensures prevention of competition for resources (processing, or otherwise) with other non-arivis solutions.
You can use VMs to setup dedicated servers for a VisionHub installation. They allow easy adoption of performance parameters and flexible scaling even after installation.
High-Speed Image Storage
The VisionHub system requires high-speed access to a file system folder. This folder will be the root for all VisionHub related data including all managed images, pipelines, and workflow results. All VisionHub components will directly use this directory when image data is read (during exploration in the viewer or via analysis) or added (results from analysis, uploads via web frontend).
VisionHub supports UNC paths (with user/pass) to mount a file system. As stated above, multiple dedicated servers can be used for specific tasks such as management server, analysis workers or 3D rendering. If multiple VisionHub servers are deployed, one could share the central folder to these other servers, or all servers can use a central network file system.
VisionHub will NEVER alter image data that is stored and expects that no external processes are allowed to alter data within this folder. However, images might have a read lock when VisionHub components are working on a specific file.
VisionHub can automatically watch and reflect changes in the image storage file system. For large volume acquisitions and to avoid copying of large image data, devices or users should directly write to this directory. The file system permission handling and the acquisition workflow ensures that no data is modified or deleted.
Client Requirements
- Web Browser (Firefox, Chrome, Edge, Safari etc.)