MS Windows/Virtual Appliance - Revision history

Henriquejf at 13:24, 18 May 2009

2009-05-18T13:24:26Z

← Older revision		Revision as of 09:24, 18 May 2009
Line 3:		Line 3:
	Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [[Main_Documentation#Components\|components]] are coded in Perl, guided towards a Linux-like traditional structure;		Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [[Main_Documentation#Components\|components]] are coded in Perl, guided towards a Linux-like traditional structure;

	The new virtualization softwares available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows~~; but then a first and strong limitation would be the capture device´s sharing~~;		The new virtualization softwares available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows;

	~~Observing that most users deploy ZoneMinder systems using PCI~~ (~~cheap or professional~~) capture ~~devices, sharing the~~ device among the host and the guest system would be the first challenge to face; One solution that shows up for that case would be the use of PCI PASS-TROUGH methods;		== Using ZM with IP cameras ==

			It is possible to get ZM running into a virtualized space hosted on Windows, and then configure the system to use IP cameras;

			One possible scenario is to use the ZM virtual appliance; details may be found under the vmware.com website, specifically at http://www.vmware.com/appliances/directory/86653;

			== Using ZM with capture devices (not accomplished so far)==

			Sharing the capture device among the host and the guest system would be the first challenge to face; One solution that shows up for that case would be the use of PCI PASS-TROUGH methods;

	PCI pass-trough is a recent implementation for some virtualization softwares that promises to share the capture device resources, or even assign it´s resources exclusively to the guest system; unfortunately, accomplishing that may not be an easy task; you may find below some web links that may introduce those subjects, but it would be worthy to rethink on how useful or how stable a Windows implementation would get in the end;		PCI pass-trough is a recent implementation for some virtualization softwares that promises to share the capture device resources, or even assign it´s resources exclusively to the guest system; unfortunately, accomplishing that may not be an easy task; you may find below some web links that may introduce those subjects, but it would be worthy to rethink on how useful or how stable a Windows implementation would get in the end;
Line 30:		Line 38:

	== External references ==		== External references ==
			* ZM Virtual Appliance for vcware: http://www.vmware.com/appliances/directory/86653
	* Virtualization: http://en.wikipedia.org/wiki/Platform_virtualization		* Virtualization: http://en.wikipedia.org/wiki/Platform_virtualization
	* Pci Pass-trough: http://bitbud.com/2008/11/12/a-virtualization-first-from-kvm/		* Pci Pass-trough: http://bitbud.com/2008/11/12/a-virtualization-first-from-kvm/
	* Pci Pass-trough: http://ubuntuforums.org/showthread.php?t=974060		* Pci Pass-trough: http://ubuntuforums.org/showthread.php?t=974060

Henriquejf: MS Windows implementation development moved to MS Windows/Virtual Appliance: the previous title was not useful

2009-05-18T13:08:13Z

MS Windows implementation development moved to MS Windows/Virtual Appliance: the previous title was not useful

← Older revision	Revision as of 09:08, 18 May 2009
(No difference)

Henriquejf: /* External references */

2009-03-31T23:28:46Z

External references

← Older revision		Revision as of 19:28, 31 March 2009
Line 31:		Line 31:
	== External references ==		== External references ==

	* Virtualization: http://en.wikipedia.org/wiki/~~Virtualization~~		* Virtualization: http://en.wikipedia.org/wiki/Platform_virtualization
	* Pci Pass-trough: http://bitbud.com/2008/11/12/a-virtualization-first-from-kvm/		* Pci Pass-trough: http://bitbud.com/2008/11/12/a-virtualization-first-from-kvm/
	* Pci Pass-trough: http://ubuntuforums.org/showthread.php?t=974060		* Pci Pass-trough: http://ubuntuforums.org/showthread.php?t=974060

Henriquejf: /* Pros */

2009-03-31T23:27:44Z

Pros

← Older revision		Revision as of 19:27, 31 March 2009
Line 17:		Line 17:
	=== Pros ===		=== Pros ===

	* ~~Windows users may use their~~ ZoneMinder Server ~~side-by-side~~ with a Windows OS; ~~traditionally~~, dual boot implementations are used to have ZoneMinder in one partition (or entire disk) and Windows on another, so ~~you can´t use~~ both at the same time;		* The interested audience could benefit from having the ZoneMinder Server running simultaneously with their Windows operating system;

			* Eventually, dual boot implementations are used to have ZoneMinder in one partition (or entire disk) and Windows on another, so it is not possible to run both at the same time in those cases, having a single pc;

	=== Cons ===		=== Cons ===

Henriquejf: /* Limitations for deploying on MS Windows */

2009-03-31T23:17:49Z

Limitations for deploying on MS Windows

← Older revision		Revision as of 19:17, 31 March 2009
Line 5:		Line 5:
	The new virtualization softwares available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device´s sharing;		The new virtualization softwares available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device´s sharing;

	Observing that most users deploy ZoneMinder systems using PCI (cheap or professional) capture devices, sharing the device among the host and the guest system would be the first challenge to face; One ~~possibility~~ that shows up for that is the use of PCI PASS-TROUGH methods;		Observing that most users deploy ZoneMinder systems using PCI (cheap or professional) capture devices, sharing the device among the host and the guest system would be the first challenge to face; One solution that shows up for that case would be the use of PCI PASS-TROUGH methods;

	PCI pass-trough is a recent implementation for some virtualization softwares that ~~may~~ share the capture device resources, or even assign it´s resources exclusively to the guest system; unfortunately, accomplishing that may not be an easy task; you may find below some web links that may introduce those subjects, but it would be worthy to rethink on how useful or how stable a Windows implementation would get in the end;		PCI pass-trough is a recent implementation for some virtualization softwares that promises to share the capture device resources, or even assign it´s resources exclusively to the guest system; unfortunately, accomplishing that may not be an easy task; you may find below some web links that may introduce those subjects, but it would be worthy to rethink on how useful or how stable a Windows implementation would get in the end;

	A Much better, simpler, safer and more reliable solution would be to forget the Windows implementation entirely and use the available live cd ZoneMinder Distributions; they´re actively updated, and you may even experiment a full working ZoneMinder system without even changing ~~one~~ bit in your hard-disk;		A Much better, simpler, safer and more reliable solution would be to forget the Windows implementation entirely and to use the available live cd ZoneMinder Distributions; they´re actively updated, and you may even experiment a full working ZoneMinder system without even changing a single bit of your hard-disk;

	~~For more information on~~ ZoneMinder Live ~~Cd distros~~, roll down the ZoneMinder [http://www.zoneminder.com/downloads.html downloads page]; Please also get to check the [http://www.zoneminder.com/forums/viewforum.php?f=1 announcements] as newer implementations seem to appear first there and only ~~aftterwards~~ on the downloads page;		To get the ZoneMinder Live Cds, roll down the ZoneMinder [http://www.zoneminder.com/downloads.html downloads page]; Please also get to check the [http://www.zoneminder.com/forums/viewforum.php?f=1 announcements] as newer implementations seem to appear first there and only afterwards on the downloads page;

	== Pros and cons on the Windows Implementation ==		== Pros and cons on the Windows Implementation ==

Henriquejf: /* Limitations for deploying on MS Windows */

2009-03-31T23:11:08Z

Limitations for deploying on MS Windows

← Older revision		Revision as of 19:11, 31 March 2009
Line 1:		Line 1:
	== Limitations for deploying on MS Windows ==		== Limitations for deploying on MS Windows ==

	Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [[Main_Documentation#Components\|components]] are coded in Perl, ~~and it´s structure is built considering~~ a Linux traditional structure;		Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [[Main_Documentation#Components\|components]] are coded in Perl, guided towards a Linux-like traditional structure;

	The new virtualization ~~technologies~~ available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture ~~device~~ sharing;		The new virtualization softwares available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device´s sharing;

	Observing that most users deploy ZoneMinder systems using PCI (cheap or professional) capture devices, sharing the device among the host and the guest would be the first challenge to face; One ~~first~~ possibility that shows up ~~then~~ is the use of PCI PASS-TROUGH methods;		Observing that most users deploy ZoneMinder systems using PCI (cheap or professional) capture devices, sharing the device among the host and the guest system would be the first challenge to face; One possibility that shows up for that is the use of PCI PASS-TROUGH methods;

	PCI ~~PASS~~-~~TROUGH~~ is a recent implementation for virtualization softwares that may share the capture device resources, or even assign it´s resources exclusively to the guest system; unfortunately, accomplishing that may not be an easy task; you may find below some web links that may ~~help on better understanding the virtualization and pass-trough technics~~, but ~~that~~ would be ~~interesting~~ to ~~think first about~~ how ~~usefull~~ or how stable a Windows implementation would be;		PCI pass-trough is a recent implementation for some virtualization softwares that may share the capture device resources, or even assign it´s resources exclusively to the guest system; unfortunately, accomplishing that may not be an easy task; you may find below some web links that may introduce those subjects, but it would be worthy to rethink on how useful or how stable a Windows implementation would get in the end;

	A Much better, simpler, safer and more reliable solution~~, tough,~~ would be forget the Windows implementation and use the available live cd ZoneMinder Distributions; they´re actively updated, and you may even experiment a full working ZoneMinder system without even changing one bit in your hard-disk;		A Much better, simpler, safer and more reliable solution would be to forget the Windows implementation entirely and use the available live cd ZoneMinder Distributions; they´re actively updated, and you may even experiment a full working ZoneMinder system without even changing one bit in your hard-disk;

	For more information on ZoneMinder Live Cd distros, roll down the ZoneMinder [http://www.zoneminder.com/downloads.html downloads page]; Please also get to check the [http://www.zoneminder.com/forums/viewforum.php?f=1 announcements] as newer implementations seem to appear first there and only aftterwards on the downloads page;		For more information on ZoneMinder Live Cd distros, roll down the ZoneMinder [http://www.zoneminder.com/downloads.html downloads page]; Please also get to check the [http://www.zoneminder.com/forums/viewforum.php?f=1 announcements] as newer implementations seem to appear first there and only aftterwards on the downloads page;

Henriquejf: /* Cons */

2009-03-31T21:06:12Z

Cons

← Older revision		Revision as of 17:06, 31 March 2009
Line 24:		Line 24:

	* Permormance: sharing your operational system with another virtualized systems, besides it´s implementation efforts, will result in degraded overall performance; Using a dedicated surveillance system is far better and safer;		* Permormance: sharing your operational system with another virtualized systems, besides it´s implementation efforts, will result in degraded overall performance; Using a dedicated surveillance system is far better and safer;

			* Getting support, mainly free support, under a virtualized implementation of ZoneMinder, under Windows, is a challenge itself; maybe you will find yourself in a very uncomfortable situation on which you´ll be on your own;

	== External references ==		== External references ==

Henriquejf: /* Limitations for deploying on MS Windows */

2009-03-31T21:01:27Z

Limitations for deploying on MS Windows

← Older revision		Revision as of 17:01, 31 March 2009
Line 1:		Line 1:
	== Limitations for deploying on MS Windows ==		== Limitations for deploying on MS Windows ==

	Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [[Main_Documentation#Components components]] are coded in Perl, and it´s structure is built considering a Linux traditional structure;		Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [[Main_Documentation#Components\|components]] are coded in Perl, and it´s structure is built considering a Linux traditional structure;

	The new virtualization technologies available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device sharing;		The new virtualization technologies available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device sharing;

Henriquejf: /* Limitations for deploying on MS Windows */

2009-03-31T21:01:03Z

Limitations for deploying on MS Windows

← Older revision		Revision as of 17:01, 31 March 2009
Line 1:		Line 1:
	== Limitations for deploying on MS Windows ==		== Limitations for deploying on MS Windows ==

	Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [Main_Documentation#Components components] are coded in Perl, and it´s structure is built considering a Linux traditional structure;		Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [[Main_Documentation#Components components]] are coded in Perl, and it´s structure is built considering a Linux traditional structure;

	The new virtualization technologies available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device sharing;		The new virtualization technologies available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device sharing;

Henriquejf: /* Limitations for deploying on MS Windows */

2009-03-31T21:00:41Z

Limitations for deploying on MS Windows

← Older revision		Revision as of 17:00, 31 March 2009
Line 1:		Line 1:
	== Limitations for deploying on MS Windows ==		== Limitations for deploying on MS Windows ==

	Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core ~~components (http://www.zoneminder.com/wiki/index.php/~~Main_Documentation#Components) are coded in Perl, and it´s structure is built considering a Linux traditional structure;		Altough Zoneminder´s interface is based on PHP and the system database uses MySQL, (both of which that may easily be deployed under Windows nowadays), the system core [Main_Documentation#Components components] are coded in Perl, and it´s structure is built considering a Linux traditional structure;

	The new virtualization technologies available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device sharing;		The new virtualization technologies available, on the other hand, may ecourage experiences of deploying the ZoneMinder system into a virtualized space under Windows; but then a first and strong limitation would be the capture device sharing;