x/terracotta
Code Issues Proposed changes

Modify the readme.md

Browse Source 
Change-Id: I0f8bd7d036a8dfb01b187b3b9323c645c4f02714
This commit is contained in:
LingxianKong 2015-05-30 09:19:39 +08:00
parent a090881fbf
commit 8ed471cd59
1 changed files with 10 additions and 93 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

103
README.md
View File

@ -1,9 +1,7 @@
# OpenStack Neat: A Framework for Dynamic Consolidation of Virtual Machines in Openstack Clouds
[![Build Status](https://travis-ci.org/beloglazov/openstack-neat.svg?branch=master)](https://travis-ci.org/beloglazov/openstack-neat)
# Terracotta: A Framework for Dynamic Consolidation of Virtual Machines in Openstack Clouds
OpenStack Neat is an extension to OpenStack implementing dynamic consolidation
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
@ -15,7 +13,7 @@ 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 OpenStack Neat.
managed by Terracotta.
In general, the problem of dynamic VM consolidation can be split into 4
sub-problems:
@ -29,101 +27,20 @@ sub-problems:
VMs currently served by the host.
- Placing VMs selected for migration to other active or re-activated hosts.
The aim of the OpenStack Neat project is to provide an extensible framework for
The aim of the Terracotta project is to provide an extensible framework for
dynamic consolidation of VMs 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. The implementation of the framework includes the
algorithms proposed in our publications [1], [2].
decision-making algorithms.
## More details
For more information please refer to the
The Terracotta project idea originally comes from the
[paper](http://beloglazov.info/papers/2014-ccpe-openstack-neat.pdf) describing
the architecture and implementation of OpenStack Neat and Chapter 6 of Anton
Beloglazov's PhD thesis: http://beloglazov.info/thesis.pdf
## Installation
Unfortunately, there is no clear installation and usage guide yet. However, the
basic installation steps are the following:
1. Clone the repository on every compute and controller node.
2. Adjust the configuration by modifying neat.conf file in the repo directory on
every node.
3. Install the package by running the following command from the repo directory
on every node: `sudo python setup.py install`
4. Start the services by running the following command on the controller: `sudo
./all-start.sh`
You can monitor the current VM placement using the `./vm-placement.py` script.
Some information about running experiments on the system can be found in the
following thread:
https://groups.google.com/forum/#!topic/openstack-neat/PKz2vpKPMcA
## Who we are
This work is conducted within the Cloud Computing and Distributed Systems
(CLOUDS) Laboratory at the University of Melbourne: http://www.cloudbus.org/
The problem of dynamic VM consolidation considering Quality of Service (QoS)
constraints has been studied from the theoretical perspective and algorithms
addressing the sub-problems listed above have been proposed [1], [2]. The
algorithms have been evaluated using CloudSim and real-world workload traces
collected from more than a thousand PlanetLab VMs hosted on servers located in
more than 500 places around the world.
## Discussion group / mailing list
Please feel free to post any questions or suggestions in the project's
discussion group: http://groups.google.com/group/openstack-neat
## Issues / bugs
Please submit any bugs you encounter or suggestions for improvements to our
issue tracker: http://github.com/beloglazov/openstack-neat/issues
## Publications
[1] Anton Beloglazov and Rajkumar Buyya, "OpenStack Neat: A Framework for
Dynamic and Energy-Efficient Consolidation of Virtual Machines in OpenStack
Clouds", Concurrency and Computation: Practice and Experience (CCPE), John Wiley
& Sons, Ltd, USA, 2014 (in press, accepted on 19/05/2014).
Download: http://beloglazov.info/papers/2014-ccpe-openstack-neat.pdf
[2] Anton Beloglazov, "Energy-Efficient Management of Virtual Machines in
Data Centers for Cloud Computing", PhD Thesis, The University of Melbourne,
2013.
Download: http://beloglazov.info/thesis.pdf
[3] Anton Beloglazov and Rajkumar Buyya, "Managing Overloaded Hosts for
Dynamic Consolidation of Virtual Machines in Cloud Data Centers Under Quality of
Service Constraints", IEEE Transactions on Parallel and Distributed Systems
(TPDS), Volume 24, Issue 7, Pages 1366-1379, IEEE CS Press, USA, 2013.
Download: http://beloglazov.info/papers/2013-tpds-managing-overloaded-hosts.pdf
[4] Anton Beloglazov and Rajkumar Buyya, "Optimal Online Deterministic
Algorithms and Adaptive Heuristics for Energy and Performance Efficient Dynamic
Consolidation of Virtual Machines in Cloud Data Centers", Concurrency and
Computation: Practice and Experience (CCPE), Volume 24, Issue 13, Pages:
1397-1420, John Wiley & Sons, Ltd, New York, USA, 2012.
Download: http://beloglazov.info/papers/2012-ccpe-vm-consolidation-algorithms.pdf
## License
The source code is distributed under the Apache 2.0 license.
Copyright (C) 2012-2014 Anton Beloglazov.
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.