This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
software:rnotes:rn-rel3.2 [2012/01/16 07:05] – nacho | software:rnotes:rn-rel3.2 [2014/01/07 11:47] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 21: | Line 21: | ||
======= What's New in OpenNebula 3.2 ======= | ======= What's New in OpenNebula 3.2 ======= | ||
- | 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:// |
===== OpenNebula Core ===== | ===== OpenNebula Core ===== | ||
Line 29: | Line 29: | ||
* **[[documentation: | * **[[documentation: | ||
* 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 for this: cipher that uses symmetric cryptography, | + | * Cloud services now use 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 for this: cipher that uses symmetric cryptography, |
* 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 VM 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 now be cached by OpenNebula. |
* **[[documentation: | * **[[documentation: | ||
- | * **Images and Virtual Networks by Name**, by popular request we've brought back these feature. When two resources share the same name, the UID or name of the owner of the resource can be used (defaults to " | + | * **Images and Virtual Networks by Name**, by popular request we've brought back this feature. When two resources share the same name, the UID or name of the owner of the resource can be used (defaults to " |
* **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 90: | Line 90: | ||
====== 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 [[documentation: | For a complete set of changes to migrate from a 3.0 installation please refer to the [[documentation: |