** Notice: all internal pipelines have been restricted to 30 minute timeouts, if your CI/CD runs take longer, either use your own runners or read below **
We would remind everyone that the CI/CD services provided by the university Gitlab servers are intended for CI/CD use only (ie. delivering new versions of your software to your production servers, etc).They are not intended for data analysis or -production use, or creating, building and running servers to do heavy data calculation or visualization.
As a general guideline; if your jobs take more than 15 minutes, you might be running something that is better suited for a dedicated system or a virtual server - in this case, please contact the helpdesk for a solution to your needs.
In order to allow external access to our immersive video streams it is necessary to provide a web proxy to them that can manage discovery and security issues as well as allowing access through firewalls. The internal C++ applications that are doing the reconstruction work use a network protocol that can also operate over Web-Sockets to connect with, for example, Node.js. The protocol is based around MsgPack and uses an RPC style approach with messages.
The web-service would provide a way of listing what streams are available as well as allowing the creation of new virtual cameras, or the sharing of existing virtual cameras, that can be controlled by the user. Eventually it is expected that scenes from multiple locations can be merged together, producing a combined virtual view from multiple source views. Such mixing would likely require specific computing resources, all of which would need to be managed by this web-service or at least can be controlled via the web-service.
The service would need to provide at least the following:
* Login and security
* Snapshot thumbnails of available streams
* Video or jpeg feeds of streams
* Control of camera positions by clients
* Configuration of new virtual cameras in specific scenes
* Listing and search of cameras and scenes
* Groups of cameras, public and private
* Statistical information about scenes + cameras
* Access to overlay or additional data associated with feeds
* Automatic camera control options
* Sharing of cameras and scene configurations by users with other groups of users
