Jump to content

Orchestration (computing): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
typo
Add a well-know tool for Orchestration page.
Line 1: Line 1:
'''Orchestration''' is the automated [[Configuration management|configuration]], coordination, and management of computer systems and [[software deployment|software]].<ref name="Erl">''Thomas Erl''. Service-Oriented Architecture: Concepts, Technology & Design. ''Prentice Hall'', {{ISBN|0-13-185858-0}}.</ref>
'''Orchestration''' is the automated [[Configuration management|configuration]], coordination, and management of computer systems and [[software deployment|software]].<ref name="Erl">''Thomas Erl''. 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]] and [[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>. For Container Orchestration there is different solutions such as [[Kubernetes]] software or managed services such as AWS EKS, AWS ECS or Amazon Fargate.
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 (Infrastructure as code)|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>. For Container Orchestration there is different solutions such as [[Kubernetes]] software or managed services such as AWS EKS, AWS ECS or Amazon Fargate.


==Usage==
==Usage==

Revision as of 01:30, 12 April 2019

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]. For Container Orchestration there is different solutions such as Kubernetes software or managed services such as AWS EKS, AWS ECS or Amazon Fargate.

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.[4]

The main difference between a workflow "automation" and an "orchestration" (in the context of cloud computing) 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[5] and maximize application performance within budget constraints,[6]

See also

References

  1. ^ a b Thomas Erl. Service-Oriented Architecture: Concepts, Technology & Design. Prentice Hall, ISBN 0-13-185858-0.
  2. ^ Yevgeniy Brikman (2016-09-26). "Why we use Terraform and not Chef, Puppet, Ansible, SaltStack, or CloudFormation".
  3. ^ Giangntc (2019-04-12). "AWS CloudFormation Introduction".
  4. ^ 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
  5. ^ 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. {{cite book}}: |journal= ignored (help)
  6. ^ 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. {{cite book}}: |journal= ignored (help)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Orchestration_(computing)&oldid=892077499"