Deployment Models: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Obsidian supports multiple deployment setups as described in the [[Getting Started#Deployment|Getting Started guide]]. This can be as simple as single scheduling/web application node or as complicated as many scheduling nodes of different types. | Obsidian supports multiple deployment setups as described in the [[Getting Started#Deployment|Getting Started guide]]. This can be as simple as single scheduling/web application node or as complicated as many scheduling nodes of different types participating in load-sharing and providing failover. | ||
The | The simplest deployment looks like the following. | ||
[[File:SimpleDeploymentDiagram.png]] | |||
A more complex setup with clustered scheduling comprised of multiple nodes types is shown below. | |||
[[File:DeploymentDiagram.png]] | [[File:DeploymentDiagram.png]] | ||
Revision as of 03:10, 6 January 2013
Obsidian supports multiple deployment setups as described in the Getting Started guide. This can be as simple as single scheduling/web application node or as complicated as many scheduling nodes of different types participating in load-sharing and providing failover.
The simplest deployment looks like the following.
A more complex setup with clustered scheduling comprised of multiple nodes types is shown below.
