This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
software:rnotes:rn-rel3.2s1 [2011/11/18 21:19] – created ruben | software:rnotes:rn-rel3.2s1 [2011/12/12 17:56] – [What's New in OpenNebula 3.2] ruben | ||
---|---|---|---|
Line 6: | Line 6: | ||
November 18th, 2011. The OpenNebula project announces the general availability of the first pre-release of OpenNebula 3.2. With this release we make our debut with a new development cycle that aims at rapidly delivering new features to the community and faster react to their needs and feedback. | November 18th, 2011. The OpenNebula project announces the general availability of the first pre-release of OpenNebula 3.2. With this release we make our debut with a new development cycle that aims at rapidly delivering new features to the community and faster react to their needs and feedback. | ||
- | The pre-releases | + | The pre-release |
With this release we also wanted to celebrate our 4th birthday. Happy testing everybody! | With this release we also wanted to celebrate our 4th birthday. Happy testing everybody! | ||
- | ======= What's New in OpenNebula 3.2 ======= | + | ======= What's New in OpenNebula 3.1.0 ======= |
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 18: | Line 18: | ||
Most of the changes in the new release have been done in the OpenNebula core (oned) and libraries to support the following new features: | Most of the changes in the new release have been done in the OpenNebula core (oned) and libraries to support the following new features: | ||
- | * **Security and User management**, | + | * **Security and User management**, |
* Users now have a pre-defined driver (set by the admin). One of the issues found is that there are potential security holes if the user is able to choose its own driver through its ONE_AUTH file. | * Users now have a pre-defined driver (set by the admin). One of the issues found is that there are potential security holes if the user is able to choose its own driver through its ONE_AUTH file. | ||
- | * Cloud services now uses an special authentication mechanism, using special server users. A server user account is granted to authenticate on-behalf of other users. Two mechanism are provided cipher that uses symmetric cryptography and x509 certificates. | + | * Cloud services now uses an special authentication mechanism, using special server users.A server user account is granted to authenticate on-behalf of other users. Two mechanism are provided |
* Notion of public users, that are restricted to public cloud APIs (e.g. EC2 or OCCI) | * Notion of public users, that are restricted to public cloud APIs (e.g. EC2 or OCCI) | ||
- | * Restricted attributes in Templates DISK/ | + | * Restricted attributes in VM Templates: DISK/ |
* Authentication Token caching. As some of the drivers may take some time to authenticate a request (e.g. LDAP), session token can no be cached by OpenNebula. | * Authentication Token caching. As some of the drivers may take some time to authenticate a request (e.g. LDAP), session token can no be cached by OpenNebula. | ||
- | * **Images and Virtual Networks by name**, by popular request we've brought back these feature. When two images | + | * **Images and Virtual Networks by name**, by popular request we've brought back these feature. When two resources |
* **Metadata for Users, Images and Virtual Networks**, you can update, and tag these resources with arbitrary metadata, that can be later used by other components. | * **Metadata for Users, Images and Virtual Networks**, you can update, and tag these resources with arbitrary metadata, that can be later used by other components. | ||
Line 48: | Line 48: | ||
====== Migrating from OpenNebula 3.0 ====== | ====== Migrating from OpenNebula 3.0 ====== | ||
- | OpenNebula 3.2 is API compatible with OpenNebula 3.0, so you should expect that applications, | + | OpenNebula 3.2 is API compatible with OpenNebula 3.0, so you should expect that applications, |
- | For a complete set of changes to migrate from a 3.0 installation please refer to the new [[documentation: | + | For a complete set of changes to migrate from a 3.0 installation please refer to the [[documentation: |
====== Known Issues and Pending Features ====== | ====== Known Issues and Pending Features ====== |