** 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.
* indexing and searching of all available data streams
* generating and providing stream statistics
* authorizing stream access and creation
* reconfiguration of virtual streams
What it does not do is:
* handle raw stream data
* allow streams to be created or deleted
Largely it responds to Redis events that informs it of new streams coming into existence or being destroyed, along with various data update events. From these events it can index the streams to allow search operations by users.
