Supercloud

Jia, Qin; Shen, Zhiming; Song, Weijia; Renesse, Robbert van; Weatherspoon, Hakim

doi:10.1145/2723872.2723892

Cited by 23 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…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.…”

Section: User-centric Inter-cloud Migrationmentioning

confidence: 99%

“…Considering the benefits of lightweight virtualization and evaluating the complexities/performance overhead of the existing inter-cloud migration techniques like nested virtualisation [12], the proposed MyMinder prototype adopts the widely accepted Docker Swarm container technology [8] in order to perform the multi-cloud deployment of user applications. However, Docker Swarm does not provide the facility for resource provisioning policies that are required by MyMinder.…”

Section: User-centric Inter-cloud Migrationmentioning

confidence: 99%

See 1 more Smart Citation

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

Barlaskar

Kilpatrick

Spence

et al. 2018

Cloud Computing and Service Science

View full text Add to dashboard Cite

Section: User-centric Inter-cloud Migrationmentioning

confidence: 99%

Section: User-centric Inter-cloud Migrationmentioning

confidence: 99%

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

Barlaskar

Kilpatrick

Spence

et al. 2018

Cloud Computing and Service Science

View full text Add to dashboard Cite

A survey on the service interoperability in cloud computing: Client‐centric and provider‐centric perspectives

2020

View full text Add to dashboard Cite

The vendor lock-in is a prominent issue in cloud computing. It is caused by cloud providers who offer proprietary services, which hinders the cloud interoperability. Client-centric interoperability enables the migration of the data and applications across clouds; it gives the clients control over their workloads and a wider range of service choices. Whereas, provider-centric interoperability allows the providers to collaborate. Thus, providers, who have spare resources, can lend them to other providers who lack computational or storage capabilities to overcome the limitations of their local resources. In this article, we conduct a survey to differentiate between client-and provider-centric interoperability solutions. We aim to provide an up-to-date analysis of the current tendencies and the neglected areas of the cloud interoperability field. Thus, we study the cloud service interoperability evolution through the years. Furthermore, we propose definitions for the intra-cloud and inter-cloud interoperability. Moreover, we propose a taxonomy to classify the cloud interoperability approaches into client-centric and provider-centric categories. Then, for each category, we classify the approaches based on their interoperability environment into single cloud or interconnected clouds. Finally, we analyze and compare the approaches based on multiple criteria. The study reveals the focus on the client-centric solutions and the interoperability in interconnected clouds. We notice more interest in the data and application levels interoperability, mainly, in infrastructure as a service model. We also find that client-centric solutions are, mostly, semantic technologies and brokers. However, provider-centric solutions are middleware, protocols, and standards. We conclude that a generic cloud service interoperability model is needed.

show abstract

Fast privacy-preserving network function outsourcing

et al. 2019

View full text Add to dashboard Cite

In this paper, we present the design and implementation of SplitBox, a system for privacy-preserving processing of network functions outsourced to cloud middleboxes-i.e., without revealing the policies governing these functions. Split-Box is built to provide privacy for a generic network function that abstracts the functionality of a variety of network functions and associated policies, including firewalls, virtual LANs, network address translators (NATs), deep packet inspection, and load balancers. We present a scalable design aiming to provide high throughput and low latency, by distributing functionalities to a few virtual machines (VMs), while providing provably secure guarantees. We implement SplitBox inside FastClick, an extension of the Click modular router, using Intel's DPDK to handle packet I/O. We evaluate our prototype experimentally to find its bottlenecks and stress-test its different components, vis-à-vis two widely used network functions, i.e., firewall and VLAN tagging. Our evaluation shows that, on commodity hardware, SplitBox can process packets close to line rate (i.e., 8.9Gbps) with up to 50 traversed policies.

show abstract

Supercloud

Cited by 23 publications

References 6 publications

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

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

A survey on the service interoperability in cloud computing: Client‐centric and provider‐centric perspectives

Fast privacy-preserving network function outsourcing

Contact Info

Product

Resources

About