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 participating in load-sharing and providing failover via a [[Clustering|cluster]]. | 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 [[Recovery_%26_Failover|failover]] via a [[Clustering|cluster]]. | ||
The simplest deployment looks like the following. | The simplest deployment looks like the following. | ||
Revision as of 23:58, 27 August 2014
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 via a cluster.
The simplest deployment looks like the following.
A more complex setup with clustered scheduling comprised of multiple nodes types is shown below.
