Jump to content

Orchestration (computing): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
rm spam magnet
rm spam magnet
 
(31 intermediate revisions by 25 users not shown)
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>
{{Short description|Automated configuration, coordination, and management of computer systems and software}}
In [[system administration]], '''orchestration''' is the [[automation | automated]] [[Configuration management|configuration]], coordination,<ref>{{cite book |chapter-url=https://doi.org/10.1007/978-3-030-00262-6_10 |url=https://doi.org/10.1007/978-3-030-00262-6 |isbn=978-3-030-00262-6 |last=Sarma |first=Anita |chapter=Coordination Technologies |title=Handbook of Software Engineering |editor1=Sungdeok Cha |editor2=Richard N. Taylor |editor3=Kyochul Kang |publisher=Springer Cham |date=11 Feb 2019 |access-date=15 July 2024}}</ref> [[system deployment | deployment]], [[software development | development]], and [[management]] of [[computer systems]] and [[software]].<ref name="Erl">{{Cite book |last=Erl |first=Thomas |date=2005 |title=Service-Oriented Architecture: Concepts, Technology & Design |publisher=Prentice Hall |isbn=0-13-185858-0}}</ref>


[[:Category:Orchestration software|Many tools exist]] to automate server configuration and management.
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>


==Usage==
==Usage==
⚫
Orchestration is often discussed in the context of [[service-oriented architecture]], [[platform virtualization|virtualization]], [[provisioning (technology)|provisioning]], [[converged Infrastructure|converged infrastructure]] and dynamic [[datacenter|data center]] topics. Orchestration in this sense is about aligning the business request with the applications, data, and infrastructure.<ref>{{Cite book |last1=Menychtas |first1=Andreas |last2=Gatzioura |first2=Anna |last3=Varvarigou |first3=Theodora |chapter=A Business Resolution Engine for Cloud Marketplaces |series=IEEE Third International Conference on Cloud Computing Technology and Science (CloudCom) |date=2011 |pages=462–469 |publisher=[[IEEE]] |doi=10.1109/CloudCom.2011.68 |title=2011 IEEE Third International Conference on Cloud Computing Technology and Science |isbn=978-1-4673-0090-2 |s2cid=14985590}}</ref>


⚫
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.<ref name="Erl" />
⚫
Orchestration is often discussed in the context of [[service-oriented architecture]], [[Platform virtualization|virtualization]], [[provisioning]], [[Converged Infrastructure|converged infrastructure]] and dynamic datacenter topics. Orchestration in this sense is about aligning the business request with the applications, data, and infrastructure.<ref>{{Citation | chapter = A Business Resolution Engine for Cloud Marketplaces | series = IEEE Third International Conference on Cloud Computing Technology and Science (CloudCom) | year = 2011 | pages = 462–469 | publisher = [[IEEE]] | doi = 10.1109/CloudCom.2011.68| title = 2011 IEEE Third International Conference on Cloud Computing Technology and Science | last1 = Menychtas | first1 = Andreas | last2 = Gatzioura | first2 = Anna | last3 = Varvarigou | first3 = Theodora | isbn = 978-1-4673-0090-2 }}</ref>


⚫
In this context, and with the overall aim to achieve specific goals and objectives (described through the [[quality of service]] parameters), for example, meet application performance goals using minimized cost<ref name="sc2011workflow">{{cite book|last=Mao|first=Ming|author2=M. Humphrey|title=Proceedings of 2011 International Conference for High Performance Computing, Networking, Storage and Analysis |chapter=Auto-scaling to minimize cost and meet application deadlines in cloud workflows |date=2011 |pages=1–12 |doi=10.1145/2063384.2063449|isbn=978-1-4503-0771-0|s2cid=11960822}}</ref> and maximize application performance within budget constraints,<ref name="ipdps2013scaling">{{cite book|last=Mao|first=Ming|author2=M. Humphrey|title=2013 IEEE 27th International Symposium on Parallel and Distributed Processing |chapter=Scaling and Scheduling to Maximize Application Performance within Budget Constraints in Cloud Workflows |date=2013|url=http://dl.acm.org/citation.cfm?id=2511429|doi=10.1109/IPDPS.2013.61|isbn=978-0-7695-4971-2|pages=67–78|s2cid=5226147}}</ref> cloud management solutions also encompass frameworks for workflow mapping and management.
⚫
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.<ref name="Erl" />

⚫
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<ref name="sc2011workflow">{{cite book|last=Mao|first=Ming|author2=M. Humphrey|title=Auto-scaling to minimize cost and meet application deadlines in cloud workflows|journal=Proceedings of 2011 International Conference for High Performance Computing, Networking, Storage and Analysis (SC2011)|year=2011|doi=10.1145/2063384.2063449|isbn=978-1-4503-0771-0}}</ref> and maximize application performance within budget constraints,<ref name="ipdps2013scaling">{{cite book|last=Mao|first=Ming|author2=M. Humphrey|title=Scaling and Scheduling to Maximize Application Performance within Budget Constraints in Cloud Workflows|journal=Proceedings of the 2013 IEEE 27th International Symposium on Parallel and Distributed Processing(IPDPS2013)|year=2013|url=http://dl.acm.org/citation.cfm?id=2511429|doi=10.1109/IPDPS.2013.61|isbn=978-0-7695-4971-2|pages=67–78}}</ref>


==See also==
==See also==
* [[Job Control Language]]
* [[Web Service Choreography|Choreography]]
* [[System management]]
* [[Web service choreography]]
* [[Configuration management]]
* [[Configuration management]]
* [[Infrastructure as code]]
* [[Infrastructure as code]]
* [[Server provisioning]]
* [[Server provisioning]]
* [[Service-oriented architecture]]
* [[Service-oriented architecture]]
* [[Kubernetes]]
* [[Job scheduler]]


== References ==
== References ==
Line 22: Line 26:


[[Category:Enterprise application integration]]
[[Category:Enterprise application integration]]
[[Category:Business terms]]
[[Category:Business intelligence terms]]
[[Category:Computing terminology]]
[[Category:Computing terminology]]
[[Category:Orchestration software]]
[[Category:Orchestration software]]

Latest revision as of 03:08, 25 September 2024

In system administration, orchestration is the automated configuration, coordination,[1] deployment, development, and management of computer systems and software.[2]

Many tools exist to automate server configuration and management.

Usage

[edit]

Orchestration is often discussed in the context of service-oriented architecture, virtualization, provisioning, converged infrastructure and dynamic data center topics. Orchestration in this sense is about aligning the business request with the applications, data, and infrastructure.[3]

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

In this context, and with the overall aim to achieve specific goals and objectives (described through the quality of service parameters), for example, meet application performance goals using minimized cost[4] and maximize application performance within budget constraints,[5] cloud management solutions also encompass frameworks for workflow mapping and management.

See also

[edit]

References

[edit]
  1. ^ Sarma, Anita (11 Feb 2019). "Coordination Technologies". In Sungdeok Cha; Richard N. Taylor; Kyochul Kang (eds.). Handbook of Software Engineering. Springer Cham. ISBN 978-3-030-00262-6. Retrieved 15 July 2024.
  2. ^ a b Erl, Thomas (2005). Service-Oriented Architecture: Concepts, Technology & Design. Prentice Hall. ISBN 0-13-185858-0.
  3. ^ 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.
  4. ^ Mao, Ming; M. Humphrey (2011). "Auto-scaling to minimize cost and meet application deadlines in cloud workflows". Proceedings of 2011 International Conference for High Performance Computing, Networking, Storage and Analysis. pp. 1–12. doi:10.1145/2063384.2063449. ISBN 978-1-4503-0771-0. S2CID 11960822.
  5. ^ Mao, Ming; M. Humphrey (2013). "Scaling and Scheduling to Maximize Application Performance within Budget Constraints in Cloud Workflows". 2013 IEEE 27th International Symposium on Parallel and Distributed Processing. pp. 67–78. doi:10.1109/IPDPS.2013.61. ISBN 978-0-7695-4971-2. S2CID 5226147.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Orchestration_(computing)&oldid=1247618088"