-
-
Notifications
You must be signed in to change notification settings - Fork 234
feat(playout): high availablility playout #3149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
05382ab
use fanout exchange for playout HA with server named temporary queues…
dakriy 32931aa
don't need to clear liquid soap queues on startup notify, because que…
dakriy e6df104
document setting up playout HA
dakriy 3993c53
remove extra spaces
dakriy dad511e
2 space indent in markdown I guess?
dakriy 072a648
blah
dakriy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
54 changes: 54 additions & 0 deletions
54
docs/admin-manual/tutorials/setup-high-availability-playout.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
--- | ||
title: How to setup high availability playout | ||
--- | ||
|
||
This tutorial walks you through the steps required to setup playout for high availability. | ||
|
||
:::info | ||
|
||
We assume you have a way to consume multiple audio inputs (for example icecast). For terrestrial HA you might consider | ||
having an audio processor with switching and silence detection capabilities. | ||
|
||
::: | ||
|
||
## 1. Initial LibreTime setup | ||
|
||
When initially setting up LibreTime, first setup the components in | ||
the [Create the schedule block](../../contributor-manual/design/architecture.md#create-the-schedule) along with | ||
the message queue. | ||
|
||
If you are going provide multiple icecast or shoutcast streams, please make sure to set all streams you want visible | ||
from the LibreTime widget to enabled in this blocks config file. | ||
|
||
## 2. Setup your playout blocks | ||
|
||
Create your [Play the schedule blocks](../../contributor-manual/design/architecture.md#play-the-schedule). | ||
|
||
You will need one for each replication you want, and any additional playout blocks you may want. For example, if you | ||
are running a terrestrial radio station, you may have two playout blocks for your radio processor, and an additional | ||
one for a non-HA icecast instance. | ||
|
||
The playout blocks should each contain the LibreTime playout service as well as a liquidsoap service. They should be | ||
able to talk to the message queue and the LibreTime API. | ||
|
||
## 3. Configure each playout block | ||
|
||
Create a config file for each playout block. Only enable the output you want from this block. For example, you may | ||
configure two blocks for system output to an audio card, and another block for streaming to icecast. | ||
|
||
The sections that need configured are | ||
|
||
- [General](../configuration.md#general) | ||
- Only `public_url` and `api_key` are needed. `cache_ahead_hours` currently has | ||
no effect as playout is hardcoded to cache ahead 1 day. | ||
- [RabbitMQ](../configuration.md#rabbitmq) | ||
- [Playout](../configuration.md#playout) | ||
- Make sure to configure the associated liquidsoap host for this block. | ||
- [Liquidsoap](../configuration.md#liquidsoap) | ||
- [Stream](../configuration.md#stream) | ||
- Configure the stream outputs you want this playout block to provide and disable the rest. | ||
|
||
## 4. Testing | ||
|
||
Start all the playout blocks and confirm they get the schedule from the LibreTime web server. Additionally and verify | ||
their outputs are correct. |
10000
View file
Open in desktop
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am gonna be picky, but this is unrelated to the change to fanout no? Could you do another PR please :) ?