x/terracotta
Code Issues Proposed changes

Update README.md for Terracotta

Browse Source 
Update the README.md to make the objective of
this project more clear.

Implements: blueprint
refactoring-terracotta-as-per-requires-of-openstack-project

Change-Id: If1a52b9ce86780462224214cb3b2f4a504d84f54
This commit is contained in:
wanghao 2016-01-06 17:43:07 +08:00
parent 887a7d155e
commit df8a3efc71
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -1,11 +1,13 @@
# Terracotta: A Framework for Dynamic Consolidation of Virtual Machines in Openstack Clouds
# Terracotta: A Framework for Dynamic Consolidation of Resources in Openstack Clouds
Terracotta is an extension to OpenStack implementing dynamic consolidation
of Virtual Machines (VMs) using live migration. The major objective of dynamic
VM consolidation is to improve the utilization of physical resources and reduce
energy consumption by re-allocating VMs using live migration according to their
real-time resource demand and switching idle hosts to the sleep mode.
of resources, e.g. Virtual Machines (VMs) using live migration.
Currently, the major objective is dynamic VM consolidation to improve the utilization
of physical resources and reduce energy consumption by re-allocating resources using
live migration according to their real-time resource demand and switching idle hosts to
the sleep mode.
For example, assume that two VMs are placed on two different hosts, but the
combined resource capacity required by the VMs to serve the current load can be
@ -28,7 +30,7 @@ sub-problems:
- Placing VMs selected for migration to other active or re-activated hosts.
The aim of the Terracotta project is to provide an extensible framework for
dynamic consolidation of VMs based on the OpenStack platform. The framework
dynamic consolidation of resources based on the OpenStack platform. The framework
provides an infrastructure enabling the interaction of components implementing
the 4 decision-making algorithms listed above. The framework allows
configuration-driven switching of different implementations of the