# Enabling Role-Based Orchestration for Cloud Applications
## 4 Experimental Evaluation
### TOSCA Model Conversion Cost
This work itself builds up a container orchestration on top of Mesos, while a native container orchestration layer such as Kubernetes and Docker Swarm could be exploited as much as possible to deliver a full-fledged orchestration systems as reported in [23]. ## 6 Conclusions

This study proposes and explores a methodology for orchestrating cloud applications built on DevOps platforms by combining two prominent orchestration standards of TOSCA and OAM. Our orchestration system design does not only support cloud application modeling, but it also provides a viable solution for deploying and managing the applications on the target runtime platform. By defining a set of capabilities as modeling constructs, our scheme allows TOSCA-based application topology itself and its orchestration needs to be specified in a way to provide a more targeted support for different needs of involved individuals, e.g., application developers and operators. With support for advanced orchestration features such as application topology model, platform capability abstraction, and role-awareness for cloud application orchestration, our approach significantly reduces the complexity of application orchestration tasks on diverse cloud platforms. We have demonstrated the feasibility and effectiveness of the proposed approach by using a Kubernetes-based prototype implementation. More importantly, our evaluation study shows the promising results that an ever-increasing complexity of cloud application orchestration can be effectively tamed by our scheme. Conceptualization, C.L. and E.K. ; Funding acquisition, C.L. and S.C.; Investigation, Y.W. and S.R. ; Methodology, Y.W. and C.L. ; Project administration, C.L. ; Software, Y.W. and S.R. ; Supervision, E.K. and S.C.; Validation, Y.W., S.R., and S.C.; Visualization, Y.W. and S.R. ; Writing--original draft, Y.W. ; Writing--review and editing, C.L., E.K., and S.C. All authors have read and agreed to the published version of the manuscript. This research was funded by the National Research Foundation of Korea (NRF) funded by the Korea government (MSIT) (No. 2020R1A2B5B01001758) and by the Korea Meteorological Administration Research and Development Program under Grant KMI 2021-01310. Not applicable. The authors declare no conflict of interest. ## References

* [PERSON] and [PERSON] (2017) [PERSON]; [PERSON] Understanding Cloud-native Applications after 10 Years of Cloud Computing--A systematic Mapping Study. _J. Syst. Softw._**2017**, _126_, 1-16. [CrossRef]
* [PERSON] (2015) [PERSON] Containerization and the PaaS Cloud. _IEEE Cloud Comput._**2015**, \(2\), 24-31. [CrossRef]
* [PERSON] et al. (2016) [PERSON]; [PERSON]; [PERSON]; [PERSON] DevOps. _IEEE Softw._**2016**, _33_, 93-100. [CrossRef]
* [PERSON] and [PERSON] (2016) [PERSON]; [PERSON] [PERSON] DevOps: Making It Easy to Do the Right Thing. _IEEE Softw._**2016**, _33_, 53-59. [CrossRef]
* [PERSON] et al. (2015) [PERSON]; [PERSON]; [PERSON] [PERSON] Dimensions of devops. In Proceedings of the International Conference on Agile Software Development, Helsinki, Finland, 25-29 May 2015; pp. 212-217. * [PERSON] et al. (2015) [PERSON]; [PERSON]; [PERSON]; [PERSON] [PERSON]; [PERSON]; [PERSON] [PERSON] Cloud Orchestration Features: Are Tools Fit for Purpose? In Proceedings of the 8 th IEEE/ACM International Conference on Utility and Cloud Computing, Limassol, Cyprus, 7-10 December 2015; pp. 95-101. * OASIS Standard (2013) OASIS Standard. Topology and Orchestration Specification for Cloud Applications Version 1.0. 2013. Available online: [[http://docs.oasis-open.org/tosca/TOSCA/v1.0/os/TOSCA-v1.0-os.html](http://docs.oasis-open.org/tosca/TOSCA/v1.0/os/TOSCA-v1.0-os.html)]([http://docs.oasis-open.org/tosca/TOSCA/v1.0/os/TOSCA-v1.0-os.html](http://docs.oasis-open.org/tosca/TOSCA/v1.0/os/TOSCA-v1.0-os.html)) (accessed on 14 March 2021). * [PERSON] et al. (2012) [PERSON]; [PERSON]; [PERSON] [PERSON]; [PERSON] Portable Cloud Services Using TOSCA. _IEEE Internet Comput._**2012**, _16_, 80-85. [CrossRef]
* [PERSON] et al.