x/terracotta
Code Issues Proposed changes
Dynamic resource scheduling service for OpenStack cloud.
798 Commits 1 Branch 0 Tags 6.8 MiB
Python 93.6%
Shell 6.4%
df8a3efc71
Go to file
wanghao df8a3efc71 Update README.md for Terracotta 
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
2016-01-06 17:43:07 +08:00
doc/blueprint/src Refactor 2015-05-05 13:12:07 +08:00
etc Make local manager work 2015-05-12 21:29:43 +08:00
terracotta Merge "Add launch script for each service" 2016-01-06 08:53:29 +00:00
tools Refactor global manager 2015-05-01 23:58:06 +08:00
.gitignore Refactor global manager 2015-05-01 23:58:06 +08:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:41:13 +00:00
.pylintrc Refactor global manager 2015-05-01 23:58:06 +08:00
.testr.conf Remove contract package dependency 2015-05-05 12:10:48 +08:00
LICENSE Added the Apache 2.0 license, header, and notice file 2012-08-02 15:55:15 +10:00
nosetests.sh Made the test runner accept a package argument to run tests from 2012-10-23 16:34:14 +11:00
openstack-common.conf Refactor api service 2015-05-04 16:40:32 +08:00
README.md Update README.md for Terracotta 2016-01-06 17:43:07 +08:00
requirements.txt refactor-at-the-very-early-age 2015-05-08 16:53:30 +08:00
run_tests.sh Refactor global manager 2015-05-01 23:58:06 +08:00
setup.cfg Add launch script for each service 2016-01-06 16:40:15 +08:00
setup.py Refactor global manager 2015-05-01 23:58:06 +08:00
test-requirements.txt Update package requirement 2015-05-04 17:37:20 +08:00
tox.ini Refactor global manager 2015-05-01 23:58:06 +08:00

README.md

Terracotta: A Framework for Dynamic Consolidation of Resources in Openstack Clouds

Terracotta is an extension to OpenStack implementing dynamic consolidation 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 provided by just one of the hosts. Then, one of the VMs can be migrated to the host serving the other VM, and the idle host can be switched to a low power mode to save energy. When the resource demand of either of the VMs increases, they get deconsolidated to avoid performance degradation. This process is dynamically managed by Terracotta.

In general, the problem of dynamic VM consolidation can be split into 4 sub-problems:

  • Deciding when a host is considered to be underloaded, so that all the VMs should be migrated from it, and the host should be switched to a low power mode, such as the sleep mode.
  • Deciding when a host is considered to be overloaded, so that some VMs should be migrated from the host to other hosts to avoid performance degradation.
  • Selecting VMs to migrate from an overloaded host out of the full set of the VMs currently served by the host.
  • 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 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 decision-making algorithms.

More details

The Terracotta project idea originally comes from the paper describing the architecture and implementation of OpenStack Neat and Chapter 6 of Anton Beloglazov's PhD thesis: http://beloglazov.info/thesis.pdf. After discussion with the author, we are authorized to use Neat as the Terracotta code base at the very early stage. However, a lot of work need to be done according to OpenStack project's requirement.