Orchestration (computing): Difference between revisions
Citation bot (talk | contribs) Add: s2cid. | You can use this bot yourself. Report bugs here. | Suggested by SemperIocundus | via #UCB_webform |
Jackkdanial (talk | contribs) m →Usage Tags: Reverted Visual edit |
||
| Line 5: | Line 5: | ||
==Usage== |
==Usage== |
||
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 | s2cid = 14985590 }}</ref> |
Orchestration<ref>{{Cite web|title=EdgeIQ Orchestration for AWS|url=https://aws.amazon.com/iot/partner-solutions/edgeiq-orchestration/|access-date=2020-09-15|website=Amazon Web Services, Inc.|language=en-US}}</ref> 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 | 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" /> |
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" /> |
||
Revision as of 12:55, 15 September 2020
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]
Usage
Orchestration[4] 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 Thomas Erl. 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".
- ^ "EdgeIQ Orchestration for AWS". Amazon Web Services, Inc. Retrieved 2020-09-15.
- ^ 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)