Managers And Workers

A Flumotion system consists of a few server processes (daemons) working together. A Worker process creates processes for the Components, and a Manager process tells the Worker what to do. The Flumotion administration user interface connects to the Manager, which in turn controls the Workers, telling it to start and stop components.

The components may be split across multiple machines, so there may be multiple Workers - usually one per machine. The entire system usually has only one Manager, on one of the machines. However, different arrangements, such as multiple workers and managers on one machine, are possible and may be useful in some circumstances in order to clearly separate different parts of your Flumotion system.

This diagram shows the Planet again, with specific components grouped into Workers on separate computers, and a Manager to manage the workers.

Figure 4.2. The Flumotion Architecture, with the Manager and Workers

The Flumotion Architecture, with the Manager and Workers

After the manager process starts, it starts an internal Bouncer component used to authenticate workers and components later on. Then it waits for incoming connections from workers. Then it can tell the workers to start their components. Those new components will also log in to the manager.

Note that the Streamer Worker in this example would typically be outside of a corporate firewall, because client users on the Internet must connect to it directly to receive content. See the Firewall section for more details.