Jan Schoonderbeek: direct links to BTs

2014-04-11T14:55:20Z

direct links to BTs

← Older revision		Revision as of 14:55, 11 April 2014
Line 2:		Line 2:
	{{Pageheaderbox4PatternType		{{Pageheaderbox4PatternType
	\|PATname=Facilities Deployment		\|PATname=Facilities Deployment
	\|summary=Provides a set of facilities to automate the deployment and administration of platforms, applications and/or configurations		\|summary=Provides a set of facilities to automate the deployment and administration of platforms, applications and/or configurations
	\|version=0.3		\|version=0.3
	\|owner=S.A.D. Jumelet		\|owner=S.A.D. Jumelet
Line 13:		Line 13:
	\|size=450px		\|size=450px
	\|title=Facilities Deployment pattern		\|title=Facilities Deployment pattern
			\|kind=Type
	}}		}}
	{{Pattern Type Composition}}		{{Pattern Type Composition}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SS~~.Deployment		\|facility=BT.Deployment
	\|choice=must		\|choice=must
	\|reason=This type of facility is used to roll out software and or configurations to (remote) facilities that are set up and/or configured centrally		\|reason=This type of facility is used to roll out software and or configurations to (remote) facilities that are set up and/or configured centrally
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SS~~.Configuration Register		\|facility=BT.Configuration Register
	\|choice=must		\|choice=must
	\|reason=This Building Block Type is used to store configuration data, either centrally or distributed. Stored configuration data can be used by the process 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 Building Block Type is used to store configuration data, either centrally or distributed. Stored configuration data can be used by the process 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.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SS~~.Configuration Retrieval		\|facility=BT.Configuration Retrieval
	\|choice=may		\|choice=may
	\|reason=This type of facility is used to collect configuration data from remote facilities. This configuration data can be stored within a configuration register facility and/or used by the process engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data is also useful to operators.		\|reason=This type of facility is used to collect configuration data from remote facilities. This configuration data can be stored within a configuration register facility and/or used by the process engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data is also useful to operators.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SE~~.Process Engine		\|facility=BT.Process Engine
	\|choice=must		\|choice=must
	\|reason=The Process Engine facility 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 facility 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.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SS~~.Reporting		\|facility=BT.Reporting
	\|choice=may		\|choice=may
	\|reason=This facility carries out reporting regarding deployment activities, to provide feed-back of the deployment solutions towards operators.		\|reason=This facility carries out reporting regarding deployment activities, to provide feed-back of the deployment solutions towards operators.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SE~~.Control Interface		\|facility=BT.Control Interface
	\|choice=may		\|choice=may
	\|reason=The Control Interface Facility 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 end-users, who can trigger the installation of (user workspace) applications.		\|reason=The Control Interface Facility 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 end-users, who can trigger the installation of (user workspace) applications.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT.~~MW.Scheduler~~		\|facility=BT.Scheduling
	\|choice=must		\|choice=must
	\|reason=This type of facility is used to schedule deployment activities.		\|reason=This type of facility is used to schedule deployment activities.

Jan Schoonderbeek: start

2012-11-11T23:22:21Z

start

New page

{{Maturity|3}}
{{Pageheaderbox4PatternType
|PATname=Facilities Deployment
|summary=Provides a set of facilities to automate the deployment and administration of platforms, applications and/or configurations
|version=0.3
|owner=S.A.D. Jumelet
|sector=Infrastructure Sector Operations
}}
This Pattern Type serves as a template for all facilities that are used by Operations to deploy IT systems, and/or configurations thereof.
{{PAgraphic
|graphic=PAT.Facilities Deployment.png
|source=Pattern Facilities Deployment.vsd
|size=450px
|title=Facilities Deployment pattern
}}
{{Pattern Type Composition}}
{{Pattern Type Composition Row
|facility=BT.SS.Deployment
|choice=must
|reason=This type of facility is used to roll out software and or configurations to (remote) facilities that are set up and/or configured centrally
}}
{{Pattern Type Composition Row
|facility=BT.SS.Configuration Register
|choice=must
|reason=This Building Block Type is used to store configuration data, either centrally or distributed. Stored configuration data can be used by the process 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.
}}
{{Pattern Type Composition Row
|facility=BT.SS.Configuration Retrieval
|choice=may
|reason=This type of facility is used to collect configuration data from remote facilities. This configuration data can be stored within a configuration register facility and/or used by the process engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data is also useful to operators.
}}
{{Pattern Type Composition Row
|facility=BT.SE.Process Engine
|choice=must
|reason=The Process Engine facility 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.
}}
{{Pattern Type Composition Row
|facility=BT.SS.Reporting
|choice=may
|reason=This facility carries out reporting regarding deployment activities, to provide feed-back of the deployment solutions towards operators.
}}
{{Pattern Type Composition Row
|facility=BT.SE.Control Interface
|choice=may
|reason=The Control Interface Facility 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 end-users, who can trigger the installation of (user workspace) applications.
}}
{{Pattern Type Composition Row
|facility=BT.MW.Scheduler
|choice=must
|reason=This type of facility is used to schedule deployment activities.
}}
{{Table Ending}}
{{Pattern Type Neighbors}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Storage
|choice=must
|reason=To enable software deployment, storage capacity is needed to accommodate software deployment packages.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Authentication+Authorization
|choice=must
|reason=Unauthorized usage of this type of facility is undesirable. Therefore, a facility to validate permissions is required. Permissions are usually linked with identities (of operators and/or users), so in many cases, an identity valication facility is needed as well. This pattern type defines such facilities and their supporting functions.
}}
{{Table Ending}}
{{PATfooter}}

PAT.Facilities Deployment - Revision history

Jan Schoonderbeek: direct links to BTs

Jan Schoonderbeek: start