Container-Based Orchestration in Cloud: State of the Art and Challenges

Tosatto, Andrea; Ruiu, Pietro; Attanasio, Aldo

doi:10.1109/cisis.2015.35

Cited by 56 publications

(21 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Another issue concerning the wide adoption of containers as a portability standard is the fragmented landscape of orchestration frameworks, as observed in [74]. Cloudify and Kubernetes are the main TOSCA compliant implementations that allow the orchestration of Docker containers.…”

Section: Deployment and Migration Of Servicesmentioning

confidence: 99%

Research challenges in legal-rule and QoS-aware cloud service brokerage

Casalicchio

Cardellini

Interino

et al. 2018

Future Generation Computer Systems

View full text Add to dashboard Cite

The ICT industry and specifically critical sectors, such as healthcare, transportation, energy and government, require as mandatory the compliance of ICT systems and services with legislation and regulation, as well as with standards. In the era of cloud computing, this compliance management issue is exacerbated by the distributed nature of the system and by the limited control that customers have on the services. Today, the cloud industry is aware of this problem (as evidenced by the compliance program of many cloud service providers), and the research community is addressing the many facets of the legal-rule compliance checking and quality assurance problem.\ud \ud Cloud service brokerage plays an important role in legislation compliance and QoS management of cloud services. In this paper we discuss our experience in designing a legal-rule and QoS-aware cloud service broker, and we explore relate research issues. Specifically we provide three main contributions to the literature: first, we describe the detailed design architecture of the legal-rule and QoS-aware broker. Second, we discuss our design choices which rely on the state of the art solutions available in literature. We cover four main research areas: cloud broker service deployment, seamless cloud service migration, cloud service monitoring, and legal rule compliance checking. Finally, from the literature review in these research areas, we identify and discuss research challenges

show abstract

Section: Deployment and Migration Of Servicesmentioning

confidence: 99%

Research challenges in legal-rule and QoS-aware cloud service brokerage

Casalicchio

Cardellini

Interino

et al. 2018

Future Generation Computer Systems

View full text Add to dashboard Cite

show abstract

“…For instance, Kubernetes, using kube-proxy, defines networking in Google Cloud via a set of dynamic routes associations between service addresses and bridges' addresses in PODs (servers) hosting containers; ideally, a service is maintained independently of the associated containers host location. Container-based orchestration is a production reality, but many challenges remain open [148], a number of them related to the seamless integration with network services inside the data centers and across data centers.…”

Section: Cloud Data Centersmentioning

confidence: 99%

Network Service Orchestration: A survey

Sousa

Perez

Rosa

et al. 2019

Computer Communications

103

View full text Add to dashboard Cite

Business models of network service providers are undergoing an evolving transformation fueled by vertical customer demands and technological advances such as 5G, Software Defined Networking (SDN), and Network Function Virtualization (NFV). Emerging scenarios call for agile network services consuming network, storage, and compute resources across heterogeneous infrastructures and administrative domains. Coordinating resource control and service creation across interconnected domains and diverse technologies becomes a grand challenge. Research and development efforts are being devoted to enabling orchestration processes to automate, coordinate, and manage the deployment and operation of network services. In this survey, we delve into the topic of Network Service Orchestration (NSO) by reviewing the historical background, relevant research projects, enabling technologies, and standardization activities. We define key concepts and propose a taxonomy of NSO approaches and solutions to pave the way to a common understanding of the various ongoing efforts towards the realization of diverse NSO application scenarios. Based on the analysis of the state of affairs, we present a series of open challenges and research opportunities, altogether contributing to a timely and comprehensive survey on the vibrant and strategic topic of network service orchestration.

show abstract

“…There are a number of papers that mainly focus on describing (and evaluating) the common features of the Linux container technology, i.e., system virtualization, and/or specific features of Docker [32][33][34][35][36][37]. However, these works provide little to no overview of the common functions of state-of-the-art container orchestration frameworks.…”

Section: Related Workmentioning

confidence: 99%

A Comprehensive Feature Comparison Study of Open-Source Container Orchestration Frameworks

et al. 2019

View full text Add to dashboard Cite

(1) Background: Container orchestration frameworks provide support for management ofcomplex distributed applications. Different frameworks have emerged only recently, and they havebeen in constant evolution as new features are being introduced. This reality makes it difficult forpractitioners and researchers to maintain a clear view of the technology space. (2) Methods: wepresent a descriptive feature comparison study of the three most prominent orchestrationframeworks: Docker Swarm, Kubernetes, and Mesos, which can be combined with Marathon,Aurora or DC/OS. This study aims at (i) identifying the common and unique features of allframeworks, (ii) comparing these frameworks qualitatively ánd quantitatively with respect togenericity in terms of supported features, and (iii) investigating the maturity and stability of theframeworks as well as the pioneering nature of each framework by studying the historical evolutionof the frameworks on GitHub. (3) Results: (i) we have identified 124 common features and 54 uniquefeatures that we divided into a taxonomy of 9 functional aspects and 27 functional sub-aspects. (ii)Kubernetes supports the highest number of accumulated common and unique features for all 9functional aspects; however, no evidence has been found for significant differences in genericitywith Docker Swarm and DC/OS. (iii) Very little feature deprecations have been found and 15 out of27 sub-aspects have been identified as mature and stable. These are pioneered in descending orderby Kubernetes, Mesos, and Marathon. (4) Conclusion: there is a broad and mature foundation thatunderpins all container orchestration frameworks. Likely areas for further evolution and innovationinclude system support for improved cluster security and container security, performance isolationof GPU, disk and network resources, and network plugin architectures.

show abstract

Container-Based Orchestration in Cloud: State of the Art and Challenges

Cited by 56 publications

References 8 publications

Research challenges in legal-rule and QoS-aware cloud service brokerage

Research challenges in legal-rule and QoS-aware cloud service brokerage

Network Service Orchestration: A survey

A Comprehensive Feature Comparison Study of Open-Source Container Orchestration Frameworks

Contact Info

Product

Resources

About