This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
software:rnotes:rn-rel4.4beta [2013/11/07 15:36] – [OpenNebula Core: Internals & Administration Interface] tinova | software:rnotes:rn-rel4.4beta [2013/11/18 11:09] – [Migrating from OpenNebula 4.2] jfontan | ||
---|---|---|---|
Line 3: | Line 3: | ||
< | < | ||
- | **Nov 7th, 2013**. The OpenNebula team is pleased to announce a beta release of OpenNebula 4.4 codename Retina. As a project driven by user needs, this release includes important features | + | **Nov 7th, 2013**. The OpenNebula team is pleased to announce a beta release of OpenNebula 4.4 codename Retina. As a project driven by user needs, this release includes important features |
- | OpenNebula Retina includes support for multiple system datastores, which enables a much more efficient usage of the storage resources for running Virtual Machines. This feature ships with different scheduling policies storage load balancing, intended to instruct OpenNebula to spread the running Virtual Machines across different storage mediums to optimize their use. This translates in the ability to define more than one disk (or other backend) to hold running VMs in a particular cluster. Monitorization subsystem in OpenNebula underwent a major redesign as well, effectively switching from a pulling mechanism to a pushing model, with the implications in scalability improvements. | + | OpenNebula Retina includes support for multiple system datastores, which enables a much more efficient usage of the storage resources for running Virtual Machines. This feature ships with different scheduling policies |
An important effort has been made in the hybrid cloud model (cloud bursting). Using the AWS API tools have been deprecated in favor of the new Ruby SDK released, which allows the support of new AWS mechanisms like for instance IAM. Also, now is possible to fully support hybrid VM templates. Moreover, the AWS public cloud interface implemented by OpenNebula has been revisited and extended to support new functionality, | An important effort has been made in the hybrid cloud model (cloud bursting). Using the AWS API tools have been deprecated in favor of the new Ruby SDK released, which allows the support of new AWS mechanisms like for instance IAM. Also, now is possible to fully support hybrid VM templates. Moreover, the AWS public cloud interface implemented by OpenNebula has been revisited and extended to support new functionality, | ||
Line 76: | Line 76: | ||
===== Sunstone ===== | ===== Sunstone ===== | ||
- | * **Improved Apache integration**, | + | * **Improved Apache integration**, |
* **Better memcache integration**, | * **Better memcache integration**, | ||
* **Multiple minor bugfixes**: adding multiple tags of the same name, VM template wizard context fixes and updating, update quotas, attach disks problems, time format inconsistencies, | * **Multiple minor bugfixes**: adding multiple tags of the same name, VM template wizard context fixes and updating, update quotas, attach disks problems, time format inconsistencies, | ||
- | |||
====== Migrating from OpenNebula 4.2 ====== | ====== Migrating from OpenNebula 4.2 ====== | ||
A detailed upgrade process can be found in the documentation. For a complete set of changes to migrate from a 4.4 installation please refer to the [[documentation: | A detailed upgrade process can be found in the documentation. For a complete set of changes to migrate from a 4.4 installation please refer to the [[documentation: | ||
+ | |||
+ | < | ||
+ | :!: After OpenNebula upgrade make use you run [[.:: | ||
+ | < | ||
====== Getting the Software & Documentation ====== | ====== Getting the Software & Documentation ====== |