Difference between revisions of "Architecture Intro"

From LinuxMCE
Jump to: navigation, search
m (→‎LinuxMCE and DHCP)
 
(40 intermediate revisions by 7 users not shown)
Line 1: Line 1:
−
LinuxMCE is divided in two parts: the '''core''' (aka the backend) and the '''media station''' (aka the frontend).
+
LinuxMCE is divided in two parts: the '''Core''' (aka the backend) and the '''Media Director''' (aka the frontend).
  
−
==The core==
+
==The Core==
−
The '''core''' has no user interface.  It provides services throughout the home, like the phone system, the central database cataloging all your media, message routing and net boot images for all the media stations. You can only have one core in the house because it is the central point through which all the devices connect. Your core should generally be left on all the time because if it's ever turned off, all the LinuxMCE functionality everywhere in the home stops working.
+
The '''[[Core]]''' has no user interface other than an [[LinuxMCE Admin Website|administration page]] (unless it is a [[hybrid]]).  It provides processing services throughout the home, however. It acts as the central database that catalogues your media. It routes home automation messages and commands, and provides net boot images for the [[Media Directors]]. It can even act as your phone system. You only have one Core in the house because it is the central point through which all devices connect. Your Core is generally left on all the time. If it is turned off, LinuxMCE functionality everywhere else in the home stops working.
  
−
==Media stations==
+
==Media Directors==
−
Wherever you have a TV you have a '''media station''', which is just a PC running LinuxMCE.  Generally you do not need to install any software on the media stations because one of the services the core provides is what's called ''net boot''.  This is a seldom used feature that almost all PC's have.  You need to go into the BIOS setup on any PC you want to use as a media station, turn on the net boot and make it higher in the boot priority.  This means when you turn the PC on, before it boots up off the hard drive like it normally would, it asks on the network for a boot image, and will boot up off the core's hard drive, not its own.  This makes it extremely convenient.  You can leave Windows, Fedora, or any other operating system you want on your PC's hard drive, and when you want to use it as a LinuxMCE media station, all you do is enable net boot, and without installing any software, you have a media station.  A great benefit is that the LinuxMCE software will never interfere with the software or operating system on the hard drive, so it's like having 2 systems in one.  It also means you only have to install LinuxMCE software one time and one PC, the core, and you can have LinuxMCE media stations throughout the house.  The whole process is fully automated and completely plug and play, so it doesn't matter if you don't understand what net boot is all about.  The only technical thing you need to do is turn on net boot in the BIOS of any PC you want to use as a media station, and your PC manufacturer can explain how to do that.
+
A '''[[Media Directors | Media Director]]''' (aka a Media Station) is connected to your TV. It is a PC running LinuxMCE, but you do not need to install any software on a Media Director, as long as you enable the Media Director to ''[[netboot]]'' LinuxMCE from the Core server.
  
−
The most common way to install LinuxMCE is to install the media station software on the same PC you install the core on.  This means you can use the core as a media station, and you can thus have a single PC stand-alone solution. You can still add other media stations using the net boot described above, and the UI (user interface) on those media stations will look exactly the same as the UI on the core.  They will have the same media catalog, the same UI, and so on, and you actually can't tell the difference between the media station on the core and a net boot media station.  But remember, don't turn off the core, or all the other media stations will stop working.
+
Network booting is a capability that almost all PCs have.  Through the BIOS setup on any PC, netboot can be enabled as the first bootup device.  When this setting is chosen and the PC is rebooted, the PC will search the network for a boot image and boots that image as its OS (rather than the OS on the hard drive).  In a LinuxMCE network, the Core provides the boot image over the network.
 +
 
 +
The local PC that functions as a Media Director is essentially a thin client to the Core.  You can leave Windows, Fedora, or any other operating system you want on your PC's hard drive.  When you want to use that PC as a LinuxMCE Media Director, enable netboot in the BIOS.  When you want to use the OS that is stored on that PC's hard drive, reset the BIOS so that the hard drive is again the first boot device.  (You can't do both at the same time.)
 +
 
 +
When LinuxMCE netboots, the software will not interfere with the software or operating system on the hard drive; it's like having 2 systems in one.  You only have to install LinuxMCE software on one PC -- the Core -- and you can then have thin client Media Stations on PCs throughout the house.  The whole process is fully automated and plug and play (whether or not you understand the concept of a netboot).  The only technical thing you need to do is turn on netboot in the BIOS of a PC you want to use as a Media Director. Your PC manufacturer instructions should tell you how to change the BIOS settings.
 +
 
 +
It is possible for the PC that functions as the LinuxMCE Core to also function as a Media Director.  This is known as a [[hybrid]], and it can be used as a standalone Home Theater solution. Later, you can add other Media Directors (using the netboot method described above).  A hybrid, like a standalone Core, will provide netboot images across a network. The UI (user interface) on all Media Directors looks exactly the same as the UI on the hybrid Core/Media Director.  The hybrid should not be shut down, either, since it is acting as a Core.  If you do, all the other Media Directors will stop working.
 +
 
 +
==Orbiters==
 +
'''[[Orbiters]]''' are the control interfaces, or remote controls, for the system. Each Media Director has an on-screen Orbiter user interface. In addition, multiple devices, such as a Nokia Internet Tablet N810, web-enabled equipment, or mobile phones can be used as Orbiters. The Orbiter User Interface (stored on and accessed from the Core) can also be accessed from any web browser.
  
 
==LinuxMCE and DHCP==
 
==LinuxMCE and DHCP==
−
Another important thing to know about LinuxMCE is that it's fairly important that LinuxMCE be your DHCP server, which is what allocates IP addresses to all the devices in your home network.  Generally you can only have 1 DHCP server on your network, and in most cases you will already have a DHCP server running in your cable or DSL modem.  The easiest way around this is to have 2 network cards in the core. One connects to the cable or DSL modem and gets an IP address from its DHCP server, and the other connects to your home switch and all your other PC's connect to it and use the core's DHCP server. LinuxMCE's default installer recognizes this configuration automatically, and will automatically set everything up for you, so this is what's recommended if you don't know about networking concepts. If you only have 1 network card in your core and your Internet service provider gives you a static IP, and not a DHCP server, then this will also be fine.  Otherwise if you already have a DCHP server in your home, you will need to know how to configure it to disable DHCP and give your core a static IP address. Or, if you don't know how to do this, then just answer 'no' when the LinuxMCE installer asks if you want to run a DHCP server. However by doing this, LinuxMCE won't be able to provide net boot images to additional media stations, and most of the plug-and-play adding of IP devices will not work.
+
It is fairly important that within your LinuxMCE home automation/multimedia network, the Core must be the DHCP server. The DHCP server allocates IP addresses to all the devices within your LinuxMCE automation/multimedia network.  Generally you can only have 1 DHCP server per network. In most cases you will already have a DHCP server on your "external" home LAN, usually as part of your router. (If you don't have a router and you have a dynamic (changing) IP address from your cable or DSL service provider, the DHCP server is at your cable or DSL provider's central office.)
 +
 
 +
Your LinuxMCE automation/multimedia network can be '''nested''' ''within'' an existing home LAN, leaving some devices "external" to the LinuxMCE automation/multimedia network. Or you can make your entire home LAN and the LinuxMCE automation/multimedia LAN one and the same, making every device in your home LAN part of the LinuxMCE automation/multimedia network as well.
 +
 
 +
When every PC and ethernet-connected device in your home LAN is also part of your LinuxMCE automation/multimedia LAN, then the Core must act as the router/DHCP server for the entire LAN. The DHCP on your existing router (if any) must be disabled and the Core then handles the DHCP functions for the entire LAN.
 +
 
 +
If you choose the nested "network within a network" configuration, the LinuxMCE Core will act as the DHCP router for the "internal" automation/multimedia network only. Your existing router would still handle DHCP functions for the "external" home LAN.
 +
 
 +
The easiest way to do this is to have 2 network cards (NICs) in the PC that will be the LinuxMCE Core. One NIC would connect to the external network (the home router, or perhaps directly to a cable or DSL modem) and gets an IP address from the DHCP of your home router or ISP provider. The other NIC would connect to your "internal" LinuxMCE automation/multimedia LAN (through a switch or a router with the DHCP disabled). All your other PCs and devices ''within'' your LinuxMCE automation/multimedia LAN connect to the switch (or the DHCP-disabled router) and therefore use the Core as the DHCP server.
 +
 
 +
This is the default configuration that the LinuxMCE installer expects by default. This is the configuration recommended if you aren't experienced with networking.
 +
 
 +
In some situations it is possible for the Core to get by with a single network card (NIC), but it is not recommended. For example, if your home has a static, unchanging IP address assigned by your cable or DSL provider, and every device in your home LAN will also be part of your home automation/multimedia LAN, then you will only need one network card. The Core will be the DHCP server for your entire LAN.
 +
 
 +
In the rare instance when you will have a single PC acting as a hybrid Core/Media Director and do not plan to have any additional devices (i.e. you don't have a home LAN at all), then the Core does not need to be configured to provide DHCP. In this scenario, one PC would act as a standalone Home Theater PC. None of the network capabilites of LinuxMCE would be available.  
  
−
The [[Usage_Intro]] explains the concepts about how to use LinuxMCE.
+
The [[Usage Intro]] explains the concepts about how to use LinuxMCE.
  
−
[[Category:Hardware]]
+
[[Category:Documentation| ]]

Latest revision as of 16:58, 8 February 2010

LinuxMCE is divided in two parts: the Core (aka the backend) and the Media Director (aka the frontend).

The Core

The Core has no user interface other than an administration page (unless it is a hybrid). It provides processing services throughout the home, however. It acts as the central database that catalogues your media. It routes home automation messages and commands, and provides net boot images for the Media Directors. It can even act as your phone system. You only have one Core in the house because it is the central point through which all devices connect. Your Core is generally left on all the time. If it is turned off, LinuxMCE functionality everywhere else in the home stops working.

Media Directors

A Media Director (aka a Media Station) is connected to your TV. It is a PC running LinuxMCE, but you do not need to install any software on a Media Director, as long as you enable the Media Director to netboot LinuxMCE from the Core server.

Network booting is a capability that almost all PCs have. Through the BIOS setup on any PC, netboot can be enabled as the first bootup device. When this setting is chosen and the PC is rebooted, the PC will search the network for a boot image and boots that image as its OS (rather than the OS on the hard drive). In a LinuxMCE network, the Core provides the boot image over the network.

The local PC that functions as a Media Director is essentially a thin client to the Core. You can leave Windows, Fedora, or any other operating system you want on your PC's hard drive. When you want to use that PC as a LinuxMCE Media Director, enable netboot in the BIOS. When you want to use the OS that is stored on that PC's hard drive, reset the BIOS so that the hard drive is again the first boot device. (You can't do both at the same time.)

When LinuxMCE netboots, the software will not interfere with the software or operating system on the hard drive; it's like having 2 systems in one. You only have to install LinuxMCE software on one PC -- the Core -- and you can then have thin client Media Stations on PCs throughout the house. The whole process is fully automated and plug and play (whether or not you understand the concept of a netboot). The only technical thing you need to do is turn on netboot in the BIOS of a PC you want to use as a Media Director. Your PC manufacturer instructions should tell you how to change the BIOS settings.

It is possible for the PC that functions as the LinuxMCE Core to also function as a Media Director. This is known as a hybrid, and it can be used as a standalone Home Theater solution. Later, you can add other Media Directors (using the netboot method described above). A hybrid, like a standalone Core, will provide netboot images across a network. The UI (user interface) on all Media Directors looks exactly the same as the UI on the hybrid Core/Media Director. The hybrid should not be shut down, either, since it is acting as a Core. If you do, all the other Media Directors will stop working.

Orbiters

Orbiters are the control interfaces, or remote controls, for the system. Each Media Director has an on-screen Orbiter user interface. In addition, multiple devices, such as a Nokia Internet Tablet N810, web-enabled equipment, or mobile phones can be used as Orbiters. The Orbiter User Interface (stored on and accessed from the Core) can also be accessed from any web browser.

LinuxMCE and DHCP

It is fairly important that within your LinuxMCE home automation/multimedia network, the Core must be the DHCP server. The DHCP server allocates IP addresses to all the devices within your LinuxMCE automation/multimedia network. Generally you can only have 1 DHCP server per network. In most cases you will already have a DHCP server on your "external" home LAN, usually as part of your router. (If you don't have a router and you have a dynamic (changing) IP address from your cable or DSL service provider, the DHCP server is at your cable or DSL provider's central office.)

Your LinuxMCE automation/multimedia network can be nested within an existing home LAN, leaving some devices "external" to the LinuxMCE automation/multimedia network. Or you can make your entire home LAN and the LinuxMCE automation/multimedia LAN one and the same, making every device in your home LAN part of the LinuxMCE automation/multimedia network as well.

When every PC and ethernet-connected device in your home LAN is also part of your LinuxMCE automation/multimedia LAN, then the Core must act as the router/DHCP server for the entire LAN. The DHCP on your existing router (if any) must be disabled and the Core then handles the DHCP functions for the entire LAN.

If you choose the nested "network within a network" configuration, the LinuxMCE Core will act as the DHCP router for the "internal" automation/multimedia network only. Your existing router would still handle DHCP functions for the "external" home LAN.

The easiest way to do this is to have 2 network cards (NICs) in the PC that will be the LinuxMCE Core. One NIC would connect to the external network (the home router, or perhaps directly to a cable or DSL modem) and gets an IP address from the DHCP of your home router or ISP provider. The other NIC would connect to your "internal" LinuxMCE automation/multimedia LAN (through a switch or a router with the DHCP disabled). All your other PCs and devices within your LinuxMCE automation/multimedia LAN connect to the switch (or the DHCP-disabled router) and therefore use the Core as the DHCP server.

This is the default configuration that the LinuxMCE installer expects by default. This is the configuration recommended if you aren't experienced with networking.

In some situations it is possible for the Core to get by with a single network card (NIC), but it is not recommended. For example, if your home has a static, unchanging IP address assigned by your cable or DSL provider, and every device in your home LAN will also be part of your home automation/multimedia LAN, then you will only need one network card. The Core will be the DHCP server for your entire LAN.

In the rare instance when you will have a single PC acting as a hybrid Core/Media Director and do not plan to have any additional devices (i.e. you don't have a home LAN at all), then the Core does not need to be configured to provide DHCP. In this scenario, one PC would act as a standalone Home Theater PC. None of the network capabilites of LinuxMCE would be available.

The Usage Intro explains the concepts about how to use LinuxMCE.

Retrieved from "http://wiki.linuxmce.org/index.php?title=Architecture_Intro&oldid=22333"