Kangaroo: A Tenant-Centric Software-Defined Cloud Infrastructure

Abstract

Abstract-Applications on cloud infrastructures acquire virtual machines (VMs) from providers when necessary. The current interface for acquiring VMs from most providers, however, is too limiting for the tenants, in terms of granularity in which VMs can be acquired (e.g., small, medium, large, etc.), while giving very limited control over their placement. The former leads to VM underutilization, and the latter has performance implications, both translating into higher costs for the tenants. In this work, we leverage nested virtualization and a networking overlay to tackle these problems. We present Kangaroo, an OpenStack-based virtual infrastructure provider, and IPOPsm, a virtual networking switch for communication between nested VMs over different infrastructure VMs. In addition, we design and implement Skippy, the realization of our proposed virtual infrastructure API for programming Kangaroo. Our benchmarks show that through careful mapping of nested VMs to infrastructure VMs, Kangaroo achieves up to an order of magnitude better performance, with only half the cost on Amazon EC2. Further, Kangaroo's unified OpenStack API allows us to migrate an entire application between Amazon EC2 and our local OpenNebula deployment within a few minutes, without any downtime or modification to the application code.

Uma taxonomia para corretagem de nuvens IaaS baseada na migração de infraestruturas virtuais

“…Inicialmente, a Tabela 2 apresenta uma classificação de alguns mecanismos/corretores de acordo com a unidade de migração. OpenVZ [56], Docker [49], Kangoroo [63], Xen-Blanket [73] A Tabela 4 apresenta uma classificação de acordo com os mecanismos de migração de MVs implementados pelas soluções e/ou corretores. Novamente, tem-se o mecanismo VMWare em mais de uma categoria, implementando as técnicas de migração por Pré-cópia e Live Migration.…”

Using Docker Swarm with a User-Centric Decision-Making Framework for Cloud Application Migration

“…These dependencies are often subject to CPs specific (non-standardized) service APIs. For users to avail of the benefits of application migration independent of the CP's permission, recent studies proposed different intercloud migration techniques which use a second layer of hardware virtualisation called nested virtualisation [34], [12], [23]. Nested VMs are usually migrated by using an NFS-based solution or an iSCSI-based solution.…”

Exploring Live Cloud Migration on Amazon EC2

“…Nested virtualization is configuring one hypervisor (in the upper layer) within a virtual machine hosted by another hypervisor [25]. Most of legacy hypervisors, such as KVM, Xen, and VMware can run nested virtualization [3][4] [7]. However, public cloud hypervisors do not allow running nested virtualization [1].…”

“…Live migration of VMs disks has been considered in many studies [3] [16]. However, it is considered to be unreliable and needs synchronization between CPU processing speed and network bandwidth [18].…”

“…Virtualization allows cloud users to exploit multi-tenant resources (compute, network and storage) from a secure Cloud IaaS [3]. Public cloud IaaS is often described as a heterogeneous environment due to the fact that each cloud provider has their own hypervisor.…”