Orchestration (computing): Difference between revisions
m Added year to citation |
Added Kubernetes ref as it is the most popular orchestration system on earth Tag: Reverted |
||
| Line 2: | Line 2: | ||
In [[system administration]], '''orchestration''' is the automated [[Configuration management|configuration]], coordination, and management of computer systems and [[software deployment|software]].<ref name="Erl">Erl, Thomas (2005) Service-Oriented Architecture: Concepts, Technology & Design. ''Prentice Hall'', {{ISBN|0-13-185858-0}}.</ref> |
In [[system administration]], '''orchestration''' is the automated [[Configuration management|configuration]], coordination, and management of computer systems and [[software deployment|software]].<ref name="Erl">Erl, Thomas (2005) Service-Oriented Architecture: Concepts, Technology & Design. ''Prentice Hall'', {{ISBN|0-13-185858-0}}.</ref> |
||
A [[:Category:Orchestration software|number of tools exist]] for automation of server configuration and management, including [[Ansible (software)|Ansible]], [[Puppet (software)|Puppet]], [[Salt (software)|Salt]], [[Terraform (software)|Terraform]],<ref>{{cite web|url=https://blog.gruntwork.io/why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c|title=Why we use Terraform and not Chef, Puppet, Ansible, SaltStack, or CloudFormation|author=Yevgeniy Brikman|date=2016-09-26}}</ref> and [[AWS CloudFormation]].<ref>{{cite web|url=https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html|title=AWS CloudFormation Introduction|author=Giangntc|date=2019-04-12}}</ref> |
A [[:Category:Orchestration software|number of tools exist]] for automation of server configuration and management, including [[Ansible (software)|Ansible]], [[Puppet (software)|Puppet]], [[Salt (software)|Salt]], [[Terraform (software)|Terraform]],<ref>{{cite web|url=https://blog.gruntwork.io/why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c|title=Why we use Terraform and not Chef, Puppet, Ansible, SaltStack, or CloudFormation|author=Yevgeniy Brikman|date=2016-09-26}}</ref> and [[AWS CloudFormation]].<ref>{{cite web|url=https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html|title=AWS CloudFormation Introduction|author=Giangntc|date=2019-04-12}}</ref> In the context of software containers, systems like Kubernetes are commonly used to dynamically deploy and manage service based distributed applications. <ref>{{cite web|url=https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/|title=What is Kubernetes|author=Kubernetes|date=2021-07-25}}</ref> |
||
==Usage== |
==Usage== |
||
Revision as of 15:57, 13 August 2021
In system administration, orchestration is the automated configuration, coordination, and management of computer systems and software.[1]
A number of tools exist for automation of server configuration and management, including Ansible, Puppet, Salt, Terraform,[2] and AWS CloudFormation.[3] In the context of software containers, systems like Kubernetes are commonly used to dynamically deploy and manage service based distributed applications. [4]
Usage
Orchestration is often discussed in the context of service-oriented architecture, virtualization, provisioning, converged infrastructure and dynamic datacenter topics. Orchestration in this sense is about aligning the business request with the applications, data, and infrastructure.[5]
In the context of cloud computing, the main difference between workflow automation and orchestration is that workflows are processed and completed as processes within a single domain for automation purposes, whereas orchestration includes a workflow and provides a directed action towards larger goals and objectives.[1]
In this context, and with the overall aim to achieve specific goals and objectives (described through quality of service parameters), for example, meet application performance goals using minimized cost[6] and maximize application performance within budget constraints.[7]
See also
References
- ^ a b Erl, Thomas (2005) Service-Oriented Architecture: Concepts, Technology & Design. Prentice Hall, ISBN 0-13-185858-0.
- ^ Yevgeniy Brikman (2016-09-26). "Why we use Terraform and not Chef, Puppet, Ansible, SaltStack, or CloudFormation".
- ^ Giangntc (2019-04-12). "AWS CloudFormation Introduction".
- ^ Kubernetes (2021-07-25). "What is Kubernetes".
- ^ Menychtas, Andreas; Gatzioura, Anna; Varvarigou, Theodora (2011), "A Business Resolution Engine for Cloud Marketplaces", 2011 IEEE Third International Conference on Cloud Computing Technology and Science, IEEE Third International Conference on Cloud Computing Technology and Science (CloudCom), IEEE, pp. 462–469, doi:10.1109/CloudCom.2011.68, ISBN 978-1-4673-0090-2, S2CID 14985590
- ^ Mao, Ming; M. Humphrey (2011). Auto-scaling to minimize cost and meet application deadlines in cloud workflows. doi:10.1145/2063384.2063449. ISBN 978-1-4503-0771-0. S2CID 11960822.
{{cite book}}:|journal=ignored (help) - ^ Mao, Ming; M. Humphrey (2013). Scaling and Scheduling to Maximize Application Performance within Budget Constraints in Cloud Workflows. pp. 67–78. doi:10.1109/IPDPS.2013.61. ISBN 978-0-7695-4971-2. S2CID 5226147.
{{cite book}}:|journal=ignored (help)