Eli Mallon

We shouldn't have the word "Studio" everywhere.

We need to decouple catalyst-ui from the Studio corporate site.

New proposed organization with Catalyst rebrand: ### Lite Build * Includes Catalyst but not some of the surrounding, heavier apps for the full stack like RabbitMQ. * Main tag: `livepeer/catalyst-lite`...

Remaining TODO: * Auto-generate the `mocks` folder (via `go generate`) and then `gitignore` them rather than hardcoding there

Gracefully take out of production.

Treat broken Serf connection as a fatal condition

1

[I'm unsure why this happens, but catalyst-node can get into a state where it keeps getting timeouts from 127.0.0.1:7373 when it's trying to connect to Serf](https://eu-metrics-monitoring.livepeer.live/grafana/explore?left=%5B%221667223421698%22,%221667223937697%22,%22Loki%22,%7B%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22P8E80F9AEF21F6940%22%7D,%22expr%22:%22%7Bnamespace%3D%5C%22prod%5C%22,%20pod%3D%5C%22prod-catalyst-0%5C%22,%20region%3D%5C%22nyc%5C%22%7D%20%7C~%20%5C%22livepeer-catalyst-node%5C%22%22,%22refId%22:%22A%22%7D%5D&orgId=1). While it might be...

Studio-specific features can be ignored but we should be randomizing things like test duration, RTMP/SRT, etc.

With catalyst multi-node, disconnecting an RTMP stream takes a long time afterward. This happens because incoming connections check against the load balancer, notice that the stream already exists, and exit....