GP.Facilities Deployment - Revision history

Jan Schoonderbeek: two missing functions added

2018-08-06T06:23:00Z

two missing functions added

@@ Line 45: / Line 45: @@
 |choice=Must
 |reason=The Controlling Function provides the management interface to deployment solutions. Depending on the implementation, this may be a programming interface to operators, or a self-service interface to (authenticated and authorized) end-users, who can trigger the installation of (user workspace) applications or configurations.
 }}
 {{Table Ending}}

Jan Schoonderbeek: corrected sector

2014-12-30T06:40:58Z

corrected sector

← Older revision		Revision as of 06:40, 30 December 2014
Line 2:		Line 2:
	{{Pageheaderbox4GP		{{Pageheaderbox4GP
	\|name=Facilities Deployment		\|name=Facilities Deployment
	\|sector=~~Core~~		\|sector=Operations
	\|version=0.4		\|version=0.4
	\|owner=J.A.H. Schoonderbeek		\|owner=J.A.H. Schoonderbeek

Jan Schoonderbeek: typo

2014-12-30T06:40:02Z

typo

← Older revision		Revision as of 06:40, 30 December 2014
Line 1:		Line 1:
	{{Maturity\|3}}		{{Maturity\|3}}
	{{Pageheaderbox4GP		{{Pageheaderbox4GP
	\|name=Facilities ~~Deplyment~~		\|name=Facilities Deployment
	\|sector=Core		\|sector=Core
	\|version=0.4		\|version=0.4
Line 15:		Line 15:
	{{Pattern Graphic		{{Pattern Graphic
	\|graphic=GP.Facilities Deployment.png		\|graphic=GP.Facilities Deployment.png
			\|source=GP.
	\|size=600px		\|size=600px
	\|title=Facilities Deployment		\|title=Facilities Deployment
Line 33:		Line 34:
	\|function=GF.Configuration Register		\|function=GF.Configuration Register
	\|choice=Must		\|choice=Must
	\|reason=This Function is used to consult the deployment configuration data. Stored configuration data can be used by the Rules Engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data in a structured way is also useful to operators.		\|reason=This Function is used to consult the deployment configuration data. Stored configuration data can be used by the Rules Engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data in a structured way is also useful to operators.
	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
	\|function=GF.Configuration Retrieval		\|function=GF.Configuration Retrieval
	\|choice=May		\|choice=May
	\|reason=This Function is used to collect configuration data from the facilities to which deployment must/may take place. This configuration data can be stored using the configuration register function and/or directly used by the Rules Engine to guide the deployment of software and/or configurations. Of course, the availability of current configuration data is also useful to operators.		\|reason=This Function is used to collect configuration data from the facilities to which deployment must/may take place. This configuration data can be stored using the configuration register function and/or directly used by the Rules Engine to guide the deployment of software and/or configurations. Of course, the availability of current configuration data is also useful to operators.
	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row

Jan Schoonderbeek: finish up

2014-12-30T06:39:21Z

finish up

← Older revision		Revision as of 06:39, 30 December 2014
Line 14:		Line 14:
	}}		}}
	{{Pattern Graphic		{{Pattern Graphic
	\|graphic=~~No graphic yet~~.png		\|graphic=GP.Facilities Deployment.png
	\|size=600px		\|size=600px
	\|title=Facilities Deployment		\|title=Facilities Deployment
Line 28:		Line 28:
	\|function=GF.Rules Engine		\|function=GF.Rules Engine
	\|choice=Must		\|choice=Must
	\|reason=The Process Engine function is the heart of automated deployment solutions. It is programmed by operators to carry out deployment jobs. Depending on it's implementation, deployment activities are carried out based on rules, pre-defined jobs, configuration data, et cetera.		\|reason=The Process Engine function is the heart of automated deployment solutions. It is programmed by operators to carry out deployment jobs. Depending on it's implementation, deployment activities are carried out based on rules, pre-defined jobs, configuration data, et cetera.
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Configuration Register
			\|choice=Must
			\|reason=This Function is used to consult the deployment configuration data. Stored configuration data can be used by the Rules Engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data in a structured way is also useful to operators.
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Configuration Retrieval
			\|choice=May
			\|reason=This Function is used to collect configuration data from the facilities to which deployment must/may take place. This configuration data can be stored using the configuration register function and/or directly used by the Rules Engine to guide the deployment of software and/or configurations. Of course, the availability of current configuration data is also useful to operators.
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Controlling
			\|choice=Must
			\|reason=The Controlling Function provides the management interface to deployment solutions. Depending on the implementation, this may be a programming interface to operators, or a self-service interface to (authenticated and authorized) end-users, who can trigger the installation of (user workspace) applications or configurations.
	}}		}}
	{{Table Ending}}		{{Table Ending}}

Jan Schoonderbeek: Jan Schoonderbeek moved page GP.Facilities Deplyment to GP.Facilities Deployment without leaving a redirect: typo

2014-12-30T06:31:35Z

Jan Schoonderbeek moved page GP.Facilities Deplyment to GP.Facilities Deployment without leaving a redirect: typo

← Older revision

Revision as of 06:31, 30 December 2014

Jan Schoonderbeek: intermediate save

2014-12-30T06:31:15Z

intermediate save

New page

{{Maturity|3}}
{{Pageheaderbox4GP
|name=Facilities Deplyment
|sector=Core
|version=0.4
|owner=J.A.H. Schoonderbeek
|summary=This Function can deploy the software part of an IT (sub)system, and/or configurations thereof.
}}
This Function can deploy the software part of an IT (sub)system, and/or configurations thereof. This entails the digital transformation from a packaged form to an operational working state, either of the IT (sub)system in its entirity, or of specific datasets for that system.
To this end, this Function makes use of a Deploying function, that is controlled by a Rules Engine. The Rules Engine (optionally supported by Scheduling) controls the actual deployment, a.o. by checking a Configuration Register for the configuration to be deployed. Optionally, Configuration Retrieval can be used to compare the actual configuration with the required configuration.
Optionally a Reporting function is used to report to the operators of the Facilities Deployment Function on the state of various deployments.
{{Pattern Realizes
|service=GS.Facilities Deployment
}}
{{Pattern Graphic
|graphic=No graphic yet.png
|size=600px
|title=Facilities Deployment
|kind=Generic
}}
{{Generic Pattern Composition}}
{{Generic Pattern Composition Row
|function=GF.Deploying
|choice=Must
|reason=This function carries out the act of rolling out software and/or configurations to (remote) facilities that are set up and/or configured centrally.
}}
{{Generic Pattern Composition Row
|function=GF.Rules Engine
|choice=Must
|reason=The Process Engine function is the heart of automated deployment solutions. It is programmed by operators to carry out deployment jobs. Depending on it's implementation, deployment activities are carried out based on rules, pre-defined jobs, configuration data, et cetera.
}}
{{Table Ending}}
{{Pattern Adjacent Services}}
{{Generic Pattern Adjacent Service Row
|service=GS.Authentication+Authorization
|choice=May
|reason=Authentication & Authorization services may be used
* to control who operates the Facilities Deployment solution, and/or
* to ensure that a deployment takes place only on a properly authenticated target system.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Data Management
|choice=May
|reason=This service may be used to store deployment rules, reports, configurations, and/or the actual deployable information
}}
{{Table Ending}}
{{Text Footer GP}}