Modify README to reflect our wiki and launchpad pages

Also change .gitignore to ignore .settings

Change-Id: I99a7dba732224e12344b41053afce7c50c3def6f
This commit is contained in:
Changbin Liu 2013-08-28 13:46:15 -04:00
parent 641c97e2a4
commit 76f759dc87
2 changed files with 7 additions and 28 deletions

1
.gitignore vendored
View File

@ -33,3 +33,4 @@ nosetests.xml
.mr.developer.cfg .mr.developer.cfg
.project .project
.pydevproject .pydevproject
.settings

View File

@ -1,33 +1,11 @@
Inception: Towards a Nested Cloud Architecture Inception
========= =========
Inception Clouds are built entirely on top of the virtual resources A tool to launch OpenStack-in-OpenStack clouds, to accelerate testing
acquired from todays clouds, and provide nested VMs to end users. and many more.
Inception Clouds enable: - More information at https://wiki.openstack.org/wiki/Inception
- Acceleration of continuous integration for open-source cloud Join us
management software such as OpenStack
- Hypervisor flexibility: VM live migration, VM replication for high - https://launchpad.net/inception
availability, instant VM spawning under high load demand, intrusion
detection by customizing Dom0 firewall...
- App-specific resource allocation: customize subscription ratio, VM
consolidation
- Low operation overhead: no physical metals, therefore no worry on
issues like cooling, power, cabling, rack design, malfunctioned
hardware replacement, data center real estate
- Spanning across multiple providers: both private and public clouds
over geographically wide area
Essentially, Inception Clouds enable entire control of your cloud,
with even less operation overhead.
For more information, please refer to our HotCloud'13 paper
http://www2.research.att.com/~changbl/pubs/Inception_Towards_a_Nested_Cloud_Architecture.pdf
The code is rapidly evolving. Stay tuned!