This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
software:rnotes:rn-rel3.2beta [2011/12/12 17:32] – ruben | software:rnotes:rn-rel3.2beta [2011/12/16 17:08] – nacho | ||
---|---|---|---|
Line 3: | Line 3: | ||
< | < | ||
- | December | + | December |
+ | |||
+ | < | ||
With this Beta release the master branch of the OpenNebula repository enters a feature-freeze mode and the OpenNebula developers concentrate on fixing bugs an smooth rough edges in the software. | With this Beta release the master branch of the OpenNebula repository enters a feature-freeze mode and the OpenNebula developers concentrate on fixing bugs an smooth rough edges in the software. | ||
Line 10: | Line 12: | ||
- | ======= What's New in OpenNebula 3.2 ======= | + | ======= What's New in OpenNebula 3.1.80 ======= |
In the following list you can check the highlights of 3.2 by component, [[http:// | In the following list you can check the highlights of 3.2 by component, [[http:// | ||
Line 31: | Line 33: | ||
This release includes some improvements in the web ui of the Zones component, as well as minor bug fixes. | This release includes some improvements in the web ui of the Zones component, as well as minor bug fixes. | ||
+ | |||
+ | ===== OpenNebula OCCI ===== | ||
+ | |||
+ | The OCCI API has been extended to include: | ||
+ | * **VM types**, can now be defined in the server configuration file and tagged with arbitrary information, | ||
+ | * **Network templates**, | ||
| | ||
====== Migrating from OpenNebula 3.0 ====== | ====== Migrating from OpenNebula 3.0 ====== | ||
Line 40: | Line 48: | ||
====== Known Issues and Pending Features ====== | ====== Known Issues and Pending Features ====== | ||
- | There are a couple of known issues and limitations in 3.0, you can check the [[http:// | + | |
+ | * This release includes a set of VMware drivers that are not fully integrated yet. | ||
+ | |||
+ | * CPU Quotas are bypassed if CPU attribute is not define in the VM template. | ||
+ | |||
+ | * There are a couple of known issues and limitations in 3.0, you can check the [[http:// | ||
====== Getting the Software ====== | ====== Getting the Software ====== |