With the wide adoption of large-scale internet services and big data, the cloud has become the ideal environment to satisfy the ever-growing storage demand. In this context, data replication has been touted as the ultimate solution to improve data availability and reduce access time. However, replica management systems usually need to migrate and create a large number of data replicas over time between and within data centers, incurring a large overhead in terms of network load and availability. In this paper, we propose CRANE, an effiCient Replica migrAtion scheme for distributed cloud Storage systEms. CRANE complements any replica placement algorithm by efficiently managing replica creation in geo-distributed infrastructures in order to (1) minimize the time needed to copy the data to the new replica location, (2) avoid network congestion, and (3) ensure the minimum desired availability for the data. Through simulation and experimental results, we show that CRANE provides a sub-optimal solution for the replica migration problem with lower computational complexity than its integer linear program formulation. We also show that, compared to OpenStack Swift, CRANE is able to reduce by up to 60 percent the replica creation and migration time and by up to 50 percent the inter-data center network traffic while ensuring the minimum required data availability.
The concept of Network Function Virtualization (NFV) has been introduced as a new paradigm in the recent few years. NFV offers a number of benefits including significantly increased maintainability and reduced deployment overhead. Several works have been done to optimize deployment (also called embedding ) of virtual network functions (VNFs). However, no work to date has looked into optimizing the selection of cloud instances for a given VNF and its specific requirements. In this paper, we evaluate the performance of VNFs when embedded on different Amazon EC2 cloud instances. Specifically, we evaluate three VNFs (firewall, IDS, and NAT) in terms of arrival packet rate, resources utilization, and packet loss. Our results indicate that performance varies across instance types, departing from the intuition of “you get what you pay for” with cloud instances. We also find out that CPU is the critical resource for the tested VNFs, although their peak packet processing capacities differ considerably from each other. Finally, based on the obtained results, we identify key research challenges related to VNF instance selection and service chain provisioning.