Deployment Models - Revision history

Carfey: /* Clustered Scheduler with Separate Admin Web Application */

2018-03-19T16:49:04Z

Clustered Scheduler with Separate Admin Web Application

← Older revision		Revision as of 16:49, 19 March 2018
Line 39:		Line 39:
	= Clustered Scheduler with Separate Admin Web Application=		= Clustered Scheduler with Separate Admin Web Application=

	A more complex setup with clustered scheduling comprised of multiple node types is shown below. It demonstrates a cluster of 3 scheduler nodes, one of which also serves the admin webapp. Additionally, two more admin webapp hosts provide access to the web application user interface and REST API.		A more complex setup with clustered scheduling comprised of multiple node types is shown below. It demonstrates a cluster of 3 scheduler nodes, one of which also serves the admin webapp. Additionally, two more admin webapp hosts provide access to the web application user interface and REST API to a different area of the network.

	[[File:DeploymentDiagram.png]]		[[File:DeploymentDiagram.png]]

Carfey: /* Clustered Scheduler with Deparate Admin Web Application */

2018-03-19T16:20:04Z

Clustered Scheduler with Deparate Admin Web Application

← Older revision		Revision as of 16:20, 19 March 2018
Line 37:		Line 37:
	[[File:SimpleDeploymentDiagram.png]]		[[File:SimpleDeploymentDiagram.png]]

	= Clustered Scheduler with ~~Deparate~~ Admin Web Application=		= Clustered Scheduler with Separate Admin Web Application=

	A more complex setup with clustered scheduling comprised of multiple node types is shown below. It demonstrates a cluster of 3 scheduler nodes, one of which also serves the admin webapp. Additionally, two more admin webapp hosts provide access to the web application user interface and REST API.		A more complex setup with clustered scheduling comprised of multiple node types is shown below. It demonstrates a cluster of 3 scheduler nodes, one of which also serves the admin webapp. Additionally, two more admin webapp hosts provide access to the web application user interface and REST API.

	[[File:DeploymentDiagram.png]]		[[File:DeploymentDiagram.png]]

Carfey: /* Purpose of Each Node Type */

2018-03-16T17:36:22Z

Purpose of Each Node Type

← Older revision		Revision as of 17:36, 16 March 2018
Line 3:		Line 3:
	= Purpose of Each Node Type =		= Purpose of Each Node Type =

	~~At its core,~~ Obsidian consists of two ~~distinct services~~:		Obsidian consists of two main processes:
	~~# Scheduling~~
	~~# Administration~~

			* '''Scheduler''' - schedules and executes jobs, sends notifications, etc. Also exposes the [[Embedded API]].
			* '''Admin Web Application''' - provides management and monitoring UI, plus the [[REST API]] and [[Embedded API]].

	These two services may be deployed in different types of deployments. They may be provided by a single application artifact, or they may be split apart, depending on your needs.		These two services may be deployed in different types of deployments. They may be provided by a single application artifact, or they may be split apart, depending on your needs.
Line 29:		Line 29:

	'''Related Terms:'''		'''Related Terms:'''
	* ''Admin/administration webapp'', ''management UI'', ''management web application'', ''etc'' - all refer to the Obsidian interface web application, deployed to a servlet container.		* ''Admin/administration webapp'', ''management UI'', ''management web application'', ''etc'' - all refer to the Obsidian interface web application, deployed to a servlet container.

	= Combined Scheduler and Admin Interface =		= Combined Scheduler and Admin Interface =

Carfey: Carfey moved page Deployment Diagram to Deployment Models

2018-03-15T22:35:18Z

Carfey moved page Deployment Diagram to Deployment Models

← Older revision	Revision as of 22:35, 15 March 2018
(No difference)

Carfey at 22:35, 15 March 2018

2018-03-15T22:35:00Z

@@ 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 [[Recovery_%26_Failover|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 a single node providing both scheduling and the web application, 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.
+= Purpose of Each Node Type =
 [[File:SimpleDeploymentDiagram.png]]
-A more complex setup with clustered scheduling comprised of multiple nodes types is shown below.
+= Clustered Scheduler with Deparate Admin Web Application=
 [[File:DeploymentDiagram.png]]

Carfey at 23:58, 27 August 2014

2014-08-27T23:58:00Z

← Older revision		Revision as of 23:58, 27 August 2014
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.

Carfey at 03:17, 8 November 2013

2013-11-08T03:17:00Z

← Older revision		Revision as of 03:17, 8 November 2013
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.		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]].

	The simplest deployment looks like the following.		The simplest deployment looks like the following.

Carfey at 03:10, 6 January 2013

2013-01-06T03:10:16Z

← Older revision		Revision as of 03:10, 6 January 2013
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 ~~diagram below provides a high-level view of~~ the ~~full set of deployment options and dependencies~~.		The simplest deployment looks like the following.

	~~Obsidian~~ nodes ~~in the cluster may be embedded in your application, or standalone~~. ~~The administration interface~~		[[File:SimpleDeploymentDiagram.png]]

			A more complex setup with clustered scheduling comprised of multiple nodes types is shown below.

	[[File:DeploymentDiagram.png]]		[[File:DeploymentDiagram.png]]

Carfey at 03:07, 6 January 2013

2013-01-06T03:07:57Z

← Older revision		Revision as of 03:07, 6 January 2013
Line 1:		Line 1:
	Obsidian supports multiple ~~node types~~ as described in the [[Getting Started#Deployment\|Getting Started guide]].		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.

			The diagram below provides a high-level view of the full set of deployment options and dependencies.

			Obsidian nodes in the cluster may be embedded in your application, or standalone. The administration interface

	~~The diagram below provides a high-level view of the deployment options and dependencies.~~
	[[File:DeploymentDiagram.png]]		[[File:DeploymentDiagram.png]]

Carfey at 03:04, 6 January 2013

2013-01-06T03:04:12Z

← Older revision		Revision as of 03:04, 6 January 2013
Line 2:		Line 2:

	The diagram below provides a high-level view of the deployment options and dependencies.		The diagram below provides a high-level view of the deployment options and dependencies.
	[[File:DeploymentDiagram.~~jpg~~]]		[[File:DeploymentDiagram.png]]