DLNA Media Server Virtual Appliance - Revision history

Emma.ciobanu at 07:08, 11 October 2012

2012-10-11T07:08:53Z

← Older revision		Revision as of 07:08, 11 October 2012
Line 64:		Line 64:

	== Network configurations ==		== Network configurations ==
	The DLNA server will only appear in the local LAN. Because of this, testing the dlna image using the qemu tool requires the VM to be in the same network as the host (bridged network configuration). The standard runqemu script creates a NAT configuration. To create the necessary configuration you first have to run the qemu-bridge script with the start parameter (The script needs the bridge-utils and the uml-utilities packages ~~that have~~ to be installed on the host system). After this you simply run the qemu command with the following parameters:		The DLNA server will only appear in the local LAN. Because of this, testing the dlna image using the qemu tool requires the VM to be in the same network as the host (bridged network configuration). The standard runqemu script creates a NAT configuration. To create the necessary configuration you first have to run the qemu-bridge script with the start parameter (The script needs the bridge-utils and the uml-utilities packages to be installed on the host system). After this you simply run the qemu command with the following parameters:

	sudo ~~${path_to_build_folder}~~/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel ${path_to_build_folder}/poky/tmp/deploy/images/bzImage-qemux86.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -hda ${path_to_build_folder}/tmp/deploy/images/core-image-mediaserver-qemux86.ext3 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -m 128 --append "vga=0 root=/dev/hda rw mem=128M opr[Bofile.timer=1 "		sudo /home/ema/ssd/work/poky/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel \
			${path_to_build_folder}/poky/tmp/deploy/images/bzImage-qemux86.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -hda \
			${path_to_build_folder}/tmp/deploy/images/core-image-mediaserver-qemux86.ext3 -show-cursor -usb -usbdevice wacom-tablet \
			-vga vmware -no-reboot -m 128 --append "vga=0 root=/dev/hda rw mem=128M opr[Bofile.timer=1 "

	The command supposes that you build the image for a x86 architecture.		The command supposes that you build the image for a x86 architecture.
	<br/>The qemu-bridge script can be found here - [[File:Qemu-bridge-configuration.txt\|qemu-bridge.sh]]. After downloading the qemu-bridge script, make sure you have changed its extension to .sh and added execution rights (chmod a+x qemu-bridge.sh).		<br/>The qemu-bridge script can be found here - [[File:Qemu-bridge-configuration.txt\|qemu-bridge.sh]]. After downloading the qemu-bridge script, make sure you have changed its extension to .sh and added execution rights (chmod a+x qemu-bridge.sh).
	~~<br/>~~After you finished all the testing you can run ./qemu-bridge.sh stop to revert the configuration to your initial one.
			After you finished all the testing you can run ./qemu-bridge.sh stop to revert the configuration to your initial one.

Emma.ciobanu at 06:57, 11 October 2012

2012-10-11T06:57:01Z

← Older revision		Revision as of 06:57, 11 October 2012
Line 49:		Line 49:
	* source the oe-init-env script		* source the oe-init-env script
	* build the image using the guacamayo-image-mediaserver target		* build the image using the guacamayo-image-mediaserver target
	bitbake <tt>guacamayo-image-mediaserver</tt> ~~[TODO]~~		bitbake <tt>guacamayo-image-mediaserver</tt>
	For testing purposes, demo content can be added by inserting the following line into <tt>build/conf/local.conf</tt>:		For testing purposes, demo content can be added by inserting the following line into <tt>build/conf/local.conf</tt>:

Line 64:		Line 64:

	== Network configurations ==		== Network configurations ==
	The DLNA server will only appear in the local LAN. Because of this, testing the dlna image using the qemu tool requires the VM to be in the same network as the host (bridged network configuration). The standard runqemu script creates a NAT configuration. To create the necessary configuration you first have to run the qemu-bridge~~.sh~~ script with the start parameter (The script needs the bridge-utils and the uml-utilities packages that have to be installed on the host system). After this you simply run the qemu command with the following parameters:		The DLNA server will only appear in the local LAN. Because of this, testing the dlna image using the qemu tool requires the VM to be in the same network as the host (bridged network configuration). The standard runqemu script creates a NAT configuration. To create the necessary configuration you first have to run the qemu-bridge script with the start parameter (The script needs the bridge-utils and the uml-utilities packages that have to be installed on the host system). After this you simply run the qemu command with the following parameters:

	sudo ${path_to_build_folder}/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel ${path_to_build_folder}/poky/tmp/deploy/images/bzImage-qemux86.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -hda ${path_to_build_folder}/tmp/deploy/images/core-image-mediaserver-qemux86.ext3 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -m 128 --append "vga=0 root=/dev/hda rw mem=128M opr[Bofile.timer=1 "		sudo ${path_to_build_folder}/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel ${path_to_build_folder}/poky/tmp/deploy/images/bzImage-qemux86.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -hda ${path_to_build_folder}/tmp/deploy/images/core-image-mediaserver-qemux86.ext3 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -m 128 --append "vga=0 root=/dev/hda rw mem=128M opr[Bofile.timer=1 "

	The command supposes that you build the image for a x86 architecture.		The command supposes that you build the image for a x86 architecture.
			<br/>The qemu-bridge script can be found here - [[File:Qemu-bridge-configuration.txt\|qemu-bridge.sh]]. After downloading the qemu-bridge script, make sure you have changed its extension to .sh and added execution rights (chmod a+x qemu-bridge.sh).
	After you finished all the testing you can run ./qemu-bridge.sh stop to revert the configuration to your initial one.		<br/>After you finished all the testing you can run ./qemu-bridge.sh stop to revert the configuration to your initial one.

Emma.ciobanu at 06:41, 11 October 2012

2012-10-11T06:41:34Z

← Older revision		Revision as of 06:41, 11 October 2012
Line 62:		Line 62:
	In order to run Media Server under a VM manager with full virtualization acceleration technologies follow this [https://wiki.yoctoproject.org/wiki/Running_an_x86_Yocto_Linux_image_under_QEMU_KVM guide].		In order to run Media Server under a VM manager with full virtualization acceleration technologies follow this [https://wiki.yoctoproject.org/wiki/Running_an_x86_Yocto_Linux_image_under_QEMU_KVM guide].
	<br/>Please note that Media Server is already configured for KVM, paravirtualization and virtio, so Yocto Linux guest OS will not need further configuration (Guest OS preparation section is already integrated).		<br/>Please note that Media Server is already configured for KVM, paravirtualization and virtio, so Yocto Linux guest OS will not need further configuration (Guest OS preparation section is already integrated).

			== Network configurations ==
			The DLNA server will only appear in the local LAN. Because of this, testing the dlna image using the qemu tool requires the VM to be in the same network as the host (bridged network configuration). The standard runqemu script creates a NAT configuration. To create the necessary configuration you first have to run the qemu-bridge.sh script with the start parameter (The script needs the bridge-utils and the uml-utilities packages that have to be installed on the host system). After this you simply run the qemu command with the following parameters:

			sudo ${path_to_build_folder}/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel ${path_to_build_folder}/poky/tmp/deploy/images/bzImage-qemux86.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -hda ${path_to_build_folder}/tmp/deploy/images/core-image-mediaserver-qemux86.ext3 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -m 128 --append "vga=0 root=/dev/hda rw mem=128M opr[Bofile.timer=1 "

			The command supposes that you build the image for a x86 architecture.

			After you finished all the testing you can run ./qemu-bridge.sh stop to revert the configuration to your initial one.

Emma.ciobanu at 09:40, 7 September 2012

2012-09-07T09:40:02Z

← Older revision		Revision as of 09:40, 7 September 2012
Line 9:		Line 9:
	Poky is a platform-independant layer that provides useful features and functionalities for embedded solutions. [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html A Quick Start Guide] and further information can be found on the main page of the [http://www.yoctoproject.org/projects/poky Poky Project].		Poky is a platform-independant layer that provides useful features and functionalities for embedded solutions. [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html A Quick Start Guide] and further information can be found on the main page of the [http://www.yoctoproject.org/projects/poky Poky Project].
	The functionality of the Media Server was implemented as a new layer, the meta-dlna layer, which can easily be integrated over any poky distribution. Stability and reliability was achieved by using the denzil branch of the yocto project.		The functionality of the Media Server was implemented as a new layer, the meta-dlna layer, which can easily be integrated over any poky distribution. Stability and reliability was achieved by using the denzil branch of the yocto project.
	<br/>		<br/>Media Server is built as a virtual appliance, destined to be run under a [http://en.wikipedia.org/wiki/QEMU QEMU] KVM Virtual Machine Manager.
	[~~TODO]~~ - KVM		<br/> The linux core of Media Server makes use of the following virtualization acceleration technologies built in the host and guest kernel:
			* [http://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine KVM]
			* [http://en.wikipedia.org/wiki/Paravirtualization Paravirtualization]
			* [http://wiki.libvirt.org/page/Virtio Virtio drivers virtualization]

	== Arhitecture design ==		== Arhitecture design ==
Line 26:		Line 29:
	===== MediaExport plugin for Rygel =====		===== MediaExport plugin for Rygel =====
	The [https://live.gnome.org/Rygel/ MediaExport] plugin exports files and folders over the network. This solution was preferred to Tracker because it represents a more lightweight alternative and meets to all project requirements.		The [https://live.gnome.org/Rygel/ MediaExport] plugin exports files and folders over the network. This solution was preferred to Tracker because it represents a more lightweight alternative and meets to all project requirements.
	~~<br/>[TODO] - KVM~~

	== How to integrate DLNA to a poky distribution ==		== How to integrate DLNA and KVM into a poky distribution ==
	The tutorial assumes that a poky distribution already exists on the local machine. If this is not the case, follow the steps described in the [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#dev-manual-start poky manual].		The tutorial assumes that a poky distribution already exists on the local machine. If this is not the case, follow the steps described in the [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#dev-manual-start poky manual].
	<br/>		<br/>
Line 36:		Line 38:
	[...]		[...]
	BBLAYERS="		BBLAYERS="
	$POKY_HOME/meta-dlna/meta-guacamayo		$POKY_HOME/meta-dlna/meta-guacamayo \
			$POKY_HOME/meta-kvm \
	[...]		[...]

Line 55:		Line 58:
	The demo media will be automatically added into the <tt>/usr/share/demos</tt>. You can now start a media player on a renderer device and be able to navigate trough the demo content from the Media Server.		The demo media will be automatically added into the <tt>/usr/share/demos</tt>. You can now start a media player on a renderer device and be able to navigate trough the demo content from the Media Server.
	<br/>At boot the system configures <tt>/home/rygel/</tt> as the default home for rygel. Any additional media files that is added in this folder will automatically be shared throughout the local network. If demo content is added, the <tt>/usr/share/demos</tt> will also be appended in the rygel configuration file as one of the media sources.		<br/>At boot the system configures <tt>/home/rygel/</tt> as the default home for rygel. Any additional media files that is added in this folder will automatically be shared throughout the local network. If demo content is added, the <tt>/usr/share/demos</tt> will also be appended in the rygel configuration file as one of the media sources.

			== How to run MediaServer using QEMU KVM ==
			In order to run Media Server under a VM manager with full virtualization acceleration technologies follow this [https://wiki.yoctoproject.org/wiki/Running_an_x86_Yocto_Linux_image_under_QEMU_KVM guide].
			<br/>Please note that Media Server is already configured for KVM, paravirtualization and virtio, so Yocto Linux guest OS will not need further configuration (Guest OS preparation section is already integrated).

Emma.ciobanu at 15:45, 6 September 2012

2012-09-06T15:45:44Z

← Older revision		Revision as of 15:45, 6 September 2012
Line 14:		Line 14:
	== Arhitecture design ==		== Arhitecture design ==
	[[File:MediaServer Terminal.png\|thumb\|left\|upright=1.1\|Media Server with Rygel]]		[[File:MediaServer Terminal.png\|thumb\|left\|upright=1.1\|Media Server with Rygel]]
			<br/>
	A basic requirement for the application is giving a minimal solution that meets all the tehnical specifications. That is why the Media Server application was designed to be a headless image. This means that after the system boots a console will automatically pop up.		A basic requirement for the application is giving a minimal solution that meets all the tehnical specifications. That is why the Media Server application was designed to be a headless image. This means that after the system boots a console will automatically pop up.
	<br/>The operating system image has no WiFi configuration. However, if possible, wired network connections are automatically set up by the init script of the os.		<br/>The operating system image has no WiFi configuration. However, if possible, wired network connections are automatically set up by the init script of the os.
			<br/>

	== Package dependencies ==		== Package dependencies ==

RossBurton: /* How to integrate DLNA to a poky distribution */

2012-09-06T14:27:05Z

How to integrate DLNA to a poky distribution

← Older revision		Revision as of 14:27, 6 September 2012
Line 53:		Line 53:

	The demo media will be automatically added into the <tt>/usr/share/demos</tt>. You can now start a media player on a renderer device and be able to navigate trough the demo content from the Media Server.		The demo media will be automatically added into the <tt>/usr/share/demos</tt>. You can now start a media player on a renderer device and be able to navigate trough the demo content from the Media Server.
	<br/>At boot the system configures <tt>/home/rygel/</tt> as the default home for rygel. Any additional media files that is added in this folder will automatically be shared throughout the local network. If demo content is added, the <tt>/usr/~~home~~/~~share~~</tt> will also be appended in the rygel configuration file as one of the media sources.		<br/>At boot the system configures <tt>/home/rygel/</tt> as the default home for rygel. Any additional media files that is added in this folder will automatically be shared throughout the local network. If demo content is added, the <tt>/usr/share/demos</tt> will also be appended in the rygel configuration file as one of the media sources.

Emma.ciobanu at 14:01, 6 September 2012

2012-09-06T14:01:00Z

← Older revision		Revision as of 14:01, 6 September 2012
Line 28:		Line 28:

	== How to integrate DLNA to a poky distribution ==		== How to integrate DLNA to a poky distribution ==
			The tutorial assumes that a poky distribution already exists on the local machine. If this is not the case, follow the steps described in the [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#dev-manual-start poky manual].
			<br/>
	The meta-dlna layer was created using the [https://wiki.yoctoproject.org/wiki/Combo-layer combo-layer tool]. To enable it, follow the next steps:		The meta-dlna layer was created using the [https://wiki.yoctoproject.org/wiki/Combo-layer combo-layer tool]. To enable it, follow the next steps:
	* Copy the <tt>meta-dlna</tt> folder into the root directory of a <tt>poky</tt> distribution. <tt>Cd</tt> into the poky folder.		* Copy the <tt>meta-dlna</tt> folder into the root directory of a <tt>poky</tt> distribution. <tt>Cd</tt> into the poky folder.

Emma.ciobanu at 13:49, 6 September 2012

2012-09-06T13:49:40Z

← Older revision		Revision as of 13:49, 6 September 2012
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
	[[File:Rygel_Example.png\|thumb\|upright=1.5\|A practical example of how the Media Server using Rygel package is seen by a renderer Media Player.]]		[[File:Rygel_Example.png\|thumb\|upright=1.5\|A practical example of how the Media Server using Rygel package is seen by a renderer Media Player.]]
	A [http://en.wikipedia.org/wiki/Digital_Living_Network_Alliance DLNA] Media Server is a device that stores media content that can be accessed by media players and rederers found in the same local network. The goal of the project was creating a minimal solution to meet theese requirements. This was achieved using the tools provided by the [http://www.yoctoproject.org/ yocto] project through the creation of the meta-dlna layer.		A [http://en.wikipedia.org/wiki/Digital_Living_Network_Alliance DLNA] Media Server is a device that stores media content that can be accessed by media players and rederers found in the same local network. It is developed using the [http://en.wikipedia.org/wiki/Universal_Plug_and_Play Universal Plug and Play] protocol which permits devices to see each other in a local network and enables different data sharing services between them.
			<br/> The goal of the project was creating a minimal solution to meet theese requirements. This was achieved using the tools provided by the [http://www.yoctoproject.org/ yocto] project through the creation of the meta-dlna layer.


Line 14:		Line 15:
	[[File:MediaServer Terminal.png\|thumb\|left\|upright=1.1\|Media Server with Rygel]]		[[File:MediaServer Terminal.png\|thumb\|left\|upright=1.1\|Media Server with Rygel]]
	A basic requirement for the application is giving a minimal solution that meets all the tehnical specifications. That is why the Media Server application was designed to be a headless image. This means that after the system boots a console will automatically pop up.		A basic requirement for the application is giving a minimal solution that meets all the tehnical specifications. That is why the Media Server application was designed to be a headless image. This means that after the system boots a console will automatically pop up.
	<br/>The image has no WiFi configuration. However, if possible, wired network connections are automatically set up by the init script of the ~~operating system~~.		<br/>The operating system image has no WiFi configuration. However, if possible, wired network connections are automatically set up by the init script of the os.


	== Package dependencies ==		== Package dependencies ==
	===== Rygel =====		===== Rygel =====
	The solution was build around [https://live.gnome.org/Rygel/ rygel], an application used for media content sharing on a home network. Rygel ~~implements its functionality through~~ a ~~plugin mechanism~~.		The solution was build around [https://live.gnome.org/Rygel/ rygel], an application used for media content sharing on a home network. Rygel can act both as a Media Renderer, e.g. an application that plays media content received from the local network and as an Universal Plug and Play Media Server, e.g. and application that makes the media available throughout the network. The project implemented the second solution, that of a UPnP Media Server.
	===== Tracker plugin =====		===== Tracker plugin for Rygel =====
	[http://projects.gnome.org/tracker/ Tracker] reprezents a data storage for devices that keeps semantic metadata about files and folders and enables data sharing throughout a local network.		[http://projects.gnome.org/tracker/ Tracker] reprezents a data storage for devices that keeps semantic metadata about files and folders and enables data sharing throughout a local network.
	===== MediaExport plugin =====		===== MediaExport plugin for Rygel =====
	The [https://live.gnome.org/Rygel/ MediaExport] plugin exports files and folders over the network. This solution was preferred to Tracker because it represents a more lightweight alternative and meets to all project requirements.		The [https://live.gnome.org/Rygel/ MediaExport] plugin exports files and folders over the network. This solution was preferred to Tracker because it represents a more lightweight alternative and meets to all project requirements.
	<br/>[TODO] - KVM		<br/>[TODO] - KVM

Emma.ciobanu at 12:58, 6 September 2012

2012-09-06T12:58:59Z

← Older revision		Revision as of 12:58, 6 September 2012
Line 50:		Line 50:

	The demo media will be automatically added into the <tt>/usr/share/demos</tt>. You can now start a media player on a renderer device and be able to navigate trough the demo content from the Media Server.		The demo media will be automatically added into the <tt>/usr/share/demos</tt>. You can now start a media player on a renderer device and be able to navigate trough the demo content from the Media Server.
	<br/>At boot the system configures <tt>/home/rygel/</tt> as the default home for rygel. If demo content is ~~add~~ the <tt>/usr/home/share</tt> will also be ~~added~~ in the rygel configuration file as one of the media sources.		<br/>At boot the system configures <tt>/home/rygel/</tt> as the default home for rygel. Any additional media files that is added in this folder will automatically be shared throughout the local network. If demo content is added, the <tt>/usr/home/share</tt> will also be appended in the rygel configuration file as one of the media sources.

Emma.ciobanu at 12:49, 6 September 2012

2012-09-06T12:49:03Z

← Older revision		Revision as of 12:49, 6 September 2012
Line 48:		Line 48:
	IMAGE_FEATURES_append = " guacamayo-demos"		IMAGE_FEATURES_append = " guacamayo-demos"
	[...]		[...]

			The demo media will be automatically added into the <tt>/usr/share/demos</tt>. You can now start a media player on a renderer device and be able to navigate trough the demo content from the Media Server.
			<br/>At boot the system configures <tt>/home/rygel/</tt> as the default home for rygel. If demo content is add the <tt>/usr/home/share</tt> will also be added in the rygel configuration file as one of the media sources.