Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
software:rnotes:rn-rel2.2.1 [2011/06/09 10:17] – tinovasoftware:rnotes:rn-rel2.2.1 [2011/06/09 15:46] – tinova
Line 4: Line 4:
  
 9th June, 2011. This maintenance release is intended to fix a [[http://dev.opennebula.org/issues/670|security issue]] (see the Security Notice below) found in the cloud servers (OCCI and econe). It aims to provide an even more robust, reliable and scalable version of OpenNebula for efficient management of virtual infrastructures, to be used in production environments. 9th June, 2011. This maintenance release is intended to fix a [[http://dev.opennebula.org/issues/670|security issue]] (see the Security Notice below) found in the cloud servers (OCCI and econe). It aims to provide an even more robust, reliable and scalable version of OpenNebula for efficient management of virtual infrastructures, to be used in production environments.
 +
 +OpenNebula 2.2.1 is completely backward compatible with v2.2.0 in terms of the database schema, interfaces and API's, so v2.2.0 can be updated maintaining the same DB and integrated components.
  
 This Release Notes are incremental with respect to [[http://opennebula.org/software:rnotes:rn-rel2.2.0|version 2.2.0]]. This Release Notes are incremental with respect to [[http://opennebula.org/software:rnotes:rn-rel2.2.0|version 2.2.0]].
Line 29: Line 31:
 In most setups (private cloud) SECURE_CONTEXT can be safely set to 0, however setting it to 1 is highly recommended when using the OCCI interface (note that EC2 Query is not affected by this issue). In most setups (private cloud) SECURE_CONTEXT can be safely set to 0, however setting it to 1 is highly recommended when using the OCCI interface (note that EC2 Query is not affected by this issue).
  
-We will like to thank Vivien Bernet-Rollande <vivien.bernet-rollande@nexen.alterway.fr> for noticing the bug and for providing a patch to fix it. We are working on a more robust and flexible fix, we will maintain you informed on the developments.+We would like to thank Vivien Bernet-Rollande <vivien.bernet-rollande@nexen.alterway.fr> for noticing the bug and for providing a patch to fix it. We are working on a more robust and flexible fix, we will maintain you informed on the developments.