VLMa/Projects/DVBlast integration - Revision history

DoesItReallyMatter: Add wikilinks

2019-03-09T20:01:50Z

Add wikilinks

← Older revision		Revision as of 20:01, 9 March 2019
Line 3:		Line 3:
	VLMa has been architectured assuming that VLC would be the only streaming facility it would use and the telnet interface is the way it communicates with VLC.		VLMa has been architectured assuming that VLC would be the only streaming facility it would use and the telnet interface is the way it communicates with VLC.

	With DVBlast coming as a better solution than VLC for broadcasting DVB channels, this assumption is not right anymore, and DVBlast has no telnet interface (and the README clearly states the DVBlast will keep as simple as possible which means it will probably never implement		With [[DVBlast]] coming as a better solution than VLC for broadcasting [[DVB]] channels, this assumption is not right anymore, and DVBlast has no telnet interface (and the README clearly states the DVBlast will keep as simple as possible which means it will probably never implement

	The idea behind this project is to provide a facade for communicating from the master (VLMa) to the slaves (the streamers: VLC, DVBlast, etc.).		The idea behind this project is to provide a facade for communicating from the master (VLMa) to the slaves (the streamers: VLC, DVBlast, etc.).

Corbax at 14:14, 30 September 2013

2013-09-30T14:14:21Z

← Older revision		Revision as of 14:14, 30 September 2013
Line 39:		Line 39:
	* GET '''/streamers/<id>/logs''' logs of streamer <id>		* GET '''/streamers/<id>/logs''' logs of streamer <id>
	* GET '''/streamers/<id>/restart''' restart the streamer whose id is <id>		* GET '''/streamers/<id>/restart''' restart the streamer whose id is <id>

			[[Category:VLMa]]

Jpountz: creation

2009-11-17T21:46:49Z

creation

New page

== Issue ==

VLMa has been architectured assuming that VLC would be the only streaming facility it would use and the telnet interface is the way it communicates with VLC.

With DVBlast coming as a better solution than VLC for broadcasting DVB channels, this assumption is not right anymore, and DVBlast has no telnet interface (and the README clearly states the DVBlast will keep as simple as possible which means it will probably never implement

The idea behind this project is to provide a facade for communicating from the master (VLMa) to the slaves (the streamers: VLC, DVBlast, etc.).

== Solution ==

There already is a little piece of code in charge of doing process management in the Git repository which can probably be reused.

=== Required features ===

* Monitoring of the server (CPU load, Incoming/Outgoing traffic, etc.)
* Monitoring of the streamer (restarting of the process when needed, CPU & memory used, etc.)
* Extensibility, it should be very easy to add the support of another streaming tool,
* Information retrieval (logs, uptime, version of the software installed)

=== Implementation ===

Python programming language (to reuse some code which has already been written).

REST/XML API:
* Applications only need XML and HTTP bindings (which are prensent in almost every serious programming language) to use the API,
* XML is human-readable (on the contrary to protobuf, etch or thrift).

=== Paths ===

I'm not very good at finding resources' names, feel free to modify them.

* GET '''/server/monitoring''' monitoring metrics of the whole server (CPU load, etc.)
* GET '''/streamers''' list of the streaming programs running (VLC, DVBlast)
* GET '''/streamers/<id>''' description of the streamer whose id is <id>
* GET '''/streamers/<id>/channels''' channels currently handled by streamer <id>
* PUT '''/streamers/<id>/channels/<channel>''' add/modify the channel whose id is <channel>
* DELETE '''/streamers/<id>/channels/<channel>''' remove the channel whose id is <channel>
* GET '''/streamers/<id>/monitoring''' monitoring metrics specific to streamer <id>
* GET '''/streamers/<id>/logs''' logs of streamer <id>
* GET '''/streamers/<id>/restart''' restart the streamer whose id is <id>