Containers and Cloud: From LXC to Docker to Kubernetes

Bernstein, David

doi:10.1109/mcc.2014.51

Cited by 896 publications

(409 citation statements)

References 0 publications

Supporting

Mentioning

335

Contrasting

Unclassified

Order By: Relevance

“…From the research perspective, what is more relevant to this work is the possibility of counting on a reliable implementation of the consensus algorithm. Much of the health management functionality described in the paper is inspired from Kubernetes [Bernstein (2014)], although to the best of our knowledge Kubernetes was originally "not intended to span multiple availability zones" 36 . Ubernetes 37 , is a project aiming to overcome this limit by federation.…”

Section: Related Workmentioning

confidence: 99%

Self-managing cloud-native applications: Design, implementation, and experience

Toffetti

Brunner

Blöchlinger

et al. 2017

Future Generation Computer Systems

View full text Add to dashboard Cite

Running applications in the cloud efficiently requires much more than deploying software in virtual machines. Cloud applications have to be continuously managed : 1) to adjust their resources to the incoming load and 2) to face transient failures replicating and restarting components to provide resiliency on unreliable infrastructure. Continuous management monitors application and infrastructural metrics to provide automated and responsive reactions to failures (health management) and changing environmental conditions (auto-scaling) minimizing human intervention.In the current practice, management functionalities are provided as infrastructural or third party services. In both cases they are external to the application deployment. We claim that this approach has intrinsic limits, namely that separating management functionalities from the application prevents them from naturally scaling with the application and requires additional management code and human intervention. Moreover, using infrastructure provider services for management functionalities results in vendor lock-in effectively preventing cloud applications to adapt and run on the most effective cloud for the job.In this paper we discuss the main characteristics of cloud native applications, propose a novel architecture that enables scalable and resilient selfmanaging applications in the cloud, and relate on our experience in porting a legacy application to the cloud applying cloud-native principles.

show abstract

Section: Related Workmentioning

confidence: 99%

Self-managing cloud-native applications: Design, implementation, and experience

Toffetti

Brunner

Blöchlinger

et al. 2017

Future Generation Computer Systems

View full text Add to dashboard Cite

show abstract

“…The Docker efficiency is comparable to the KVM efficiency, and sometimes Docker is even better than KVM in this regard. All these features allow LXC to become an efficient mean of microservices representation [13]. Also, LXC extremely simplifies microservices development [9] and existing instruments of automation like Ansible and SaltStack make docker even more powerful [12].…”

Section: In Monolithic Architecturementioning

confidence: 99%

Microservices Architecture for Tenant-oriented Cloud-based Control Software Services: POC and Proposals

Sorokin¹,

Singla²

2017

dtetr

View full text Add to dashboard Cite

Abstract. Microservices architecture, where application is composed of a set of independently deployable services is a popular modern approach for building enterprise-level applications, meanwhile most of the cloud solutions for control software (including IoT) are designed in so called monolithic way. LXC-based (docker) microservices allow developers to seamlessly migrate current software solutions from VMs to containers. Nowadays, such container-based applications are used primarily for simple semi-automated deployments, when containers are deployed only at the launch time of the whole system and modified when needed. In this paper we analyze application of docker-microservices as functional blocks for control software, propose on-demand tenant-oriented microservices approach (where entire independent topologies of microservices are being deployed on per-tenant basis) for building clouds of control software, review requirements for management system of such cloud and investigate contemporary container-management systems. Constructed test cluster highlighted some disadvantages of Kubernetes regarding multi-tenant container administration. Advanced Container Management System (AMS) is designed as one more level of orchestration on top of Kubernetes. Conducted demo showed practical value and flexibility of the introduced tenant-oriented microservices method. Described design will be helpful for cloud providers of control software who want to organize elastic on-demand service provisioning.

show abstract

“…In 2004, the capability was improved and released with Solaris 10 as zones. By Solaris 11, a full-blown capability based on zones was completed and called containers [1]. By that time, other proprietary Unix vendors offered similar capabilities for example, HP-UX containers and IBM AIX workload partitions.…”

Section: Related Workmentioning

confidence: 99%

Docker Management Using Libvirt Api

2016

IJAERD

View full text Add to dashboard Cite

Containers and Cloud: From LXC to Docker to Kubernetes

Cited by 896 publications

References 0 publications

Self-managing cloud-native applications: Design, implementation, and experience

Self-managing cloud-native applications: Design, implementation, and experience

Microservices Architecture for Tenant-oriented Cloud-based Control Software Services: POC and Proposals

Docker Management Using Libvirt Api

Contact Info

Product

Resources

About