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
software:rnotes:rn-rel4.0beta [2013/07/16 22:45] – rubensoftware:rnotes:rn-rel4.0beta [2014/01/07 11:47] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ~~NOTOC~~  ~~NOTOC~~ 
  
-<html><div><p class="bigheader">OpenNebula 4.2 Beta (4.1.80)</p></div></html>+<html><div><p class="bigheader">OpenNebula 4.0 Beta (3.9.80)</p></div></html>
  
-**July 18th, 2013**, The OpenNebula team is pleased to welcome the summer with a beta release of a new version of OpenNebula. This release includes an important subset of the features originally planned for 4.2, all the missing features has been automatically rescheduled to 4.4. Our goal with this release is not to make you wait to test some exciting new features that are ready! +**March 26th, 2013**. The project has come a long way since the first "technology preview" of OpenNebula five years ago. During these years we've witnessed the rise and hype of the Cloud, the birth and decline of several virtualization technologies, but specially the encouraging and exciting growth of OpenNebula; both as a technology and as an active and engaged community.
  
-OpenNebula 4.2 includes a more polished Sunstone interface, after its redesign in 4.0; with important usability enhancements. Datastore capacity is now monitored and used to limit the amount of storage sized used by images. This is a first step to also control the runtime storage used by the VMs. The VMware backend has been completely redesign with a more comprehensive storage scheme, more functionality and less dependencies. Also we have upgraded the Xen backend to support the new interfaces introduced in Xen 4.0. And last but no least, OneFlow, the multi-tier application (a.k.a. service) manager, it is included and fully integrated in the distribution. It includes also important new features related to service management and elasticity/auto-scaling.+OpenNebula 4.0 is the result of the terrific feedback of the day-to-day operation of virtualized infrastructures by many of you, result of all your contributions, bug reports, patches, and translations, but one and foremost, OpenNebula 4.0 is the realization of a vision of simplicity, openness, code-correctness and a sysadmin-centric approach. This defines our personality as a community, it defines the OpenNebula Way. Now the features that you've been waiting for....
  
-We are now set to basically bug-fixing and feature-freeze. Note that this is a beta release aimed at testers and developers to try the new features, and send a more than welcomed feedback for the final release.+OpenNebula 4.0 includes new features in most of its subsystems. We are showing for the first time a completely redesigned Sunstone, with a fresh and modern look and an updated workflow for most of the dialogs. A whole new set of operations for VMs like system and disk snapshoting, capacity re-sizing, programmable VM actions and IPv6 among others. There are some new drivers also, like Ceph; as well as improvements for VMware, KVM and Xen. The scheduler has received some attention from the OpenNebula team to easily define more placement policies... and much more (see below).
  
-======= What's New in OpenNebula 4.2 Beta =======+There are some last-minute features that will be probably added in the final release, but we are basically in feature-freeze, concentrated in smooth some rough edges here and there. Note that this is a beta release aimed at testers and developers to try the new features, and send a more than welcomed feedback for the final release. Although this is a major release we've done our best to keep compatibility with OpenNebula 3.8 so any application developed for previous versions should work without effort. We have changed the name of some of the operations over the VM (we have now 32 different management actions) so be sure to check the compatibility and upgrade guides.
  
-In the following list you can check the highlights of 4.2 organized by component ([[http://dev.opennebula.org/projects/opennebula/issues?query_id=39 |a detailed list of changes can be found here]]):+======= What's New in OpenNebula 4.0 Beta =======
  
-===== OpenNebula Core =====+In the following list you can check the highlights of 4.0 organized by component ([[http://dev.opennebula.org/projects/opennebula/issues?query_id=32 |a detailed list of changes can be found here]]):
  
-  * **Datastore Monitoring**, the capacity of the datastores is now monitored by the drivers. This will help users and admins to quickly identify the resource usage of the cloud. Admins can also set security threshold in capacity usage. +===== OpenNebula Core: End-user functionality =====
-  * **New Hooks**, you can now program hooks on any transition. Also the information of the previous state can be passed as a hook argument to customized the action depending on the original VM state.+
  
 +OpenNebula 4.0 brings multiple new features to manage virtual machines:
 +  * **VM System Snapshots**, i.e. including the complete VM state (memory+disk). Snapshots can be listed and reverted freely for running VMs. These feature is supported for KVM and VMware  ([[http://opennebula.org/documentation:rel4.0:vm_guide_2#snapshotting|see more info here]]). 
 +  * **Disk Snapshots**, similar to the 3.8 save_as operation but to be performed live, so applications must guarantee FS integrity ([[http://opennebula.org/documentation:rel4.0:vm_guide_2#disk_snapshoting|more here]]).
 +  * **Capacity re sizing**, to change the CPUs and memory allocated to a VM. These operation is only for off-line re-sizing ([[http://opennebula.org/documentation:rel4.0:vm_guide_2#resizing_a_vm|check this out]]).
 +  * **Programmable VM operations**, so you want to suspend your VM Friday afternoon and resume it first thing on Monday. You can do this without intervention by programming the suspend and resume operations, [[http://opennebula.org/documentation:rel4.0:vm_guide_2#scheduling_actions|see a description here]].
 +  * **NIC hotplugging**, need another network card in your VM, [[http://opennebula.org/documentation:rel4.0:vm_guide_2#nic_hotpluging|hot-plug a new one]].
 +  * **IPv6 Support**, extending OpenNebula's contextualization process you can now easily define site and global unicast addresses. For the sake of completeness the link local address is also generated, ([[http://opennebula.org/documentation:rel4.0:vgg#ipv6_networks|more here]]).
 +  * **Plain Files Datastore**, This is an special datastore to store kernels, ramdisks and files to be used in context. The whole set of OpenNebula features applies, e.g. ACLs, ownership... [[http://opennebula.org/documentation:rel4.0:file_ds|more information here]].
 +  * **User defined VM tags** now you can tag VMs with any information (key-value), this is useful to manage your VMs but also to store application specific data (VMs can call-back home), [[ http://opennebula.org/documentation:rel4.0:vm_guide_2#user_defined_data|more in the VM guide]]
 +  * **Powerful CLI**, the shell is also important for us, with OpenNebula 4.0 you can easily control your infrastructure, [[http://blog.opennebula.org/?p=4303|read this]].
 +  * **And much more...**: one-step template update & instantation, rename virtual resources, user umask, capacity checks for deployment operations...
 +
 +===== OpenNebula Core: Internals & Administration Interface =====  
 +
 +There has been also several improvements for administrators and new features to enhance the robustness and scalability of OpenNebula core:
 +  * **Syslog support**, for the oned daemon and the scheduler, [[http://opennebula.org/documentation:rel4.0:log_debug#configure_the_logging_system|read this to configure it]].
 +  * **ACLs for clusters**, now you can define fine-grain access to the resources of a cluster.
 +  * **Default Quotas**, so you can limit resource usage by default, [[http://opennebula.org/documentation:rel4.0:quota_auth#setting_default_quotas|see this]].
 +  * **New persistency model**, VM disk images can now be "inmutable" to implement advanced transfer mechanisms. 
 +  * **Efficient monitoring**, we have greatly reduced the latency and overhead of monitoring, [[http://blog.opennebula.org/?p=4002|read at the end of this post]].
 +  * **VM cancellation and cleanup synchronization**, the previous destroy mechanism was to aggressive and sometimes images were not properly cleaned-up. The cancellation and clean-up procedure are now sync.
 +  * **Better concurrency for network drivers**, to prevent race conditions when instantiating multiple VMs in the same host.
 +
 +===== New Sunstone =====
 +
 +The UI interface has been redesigned with a fresher and modern look. You can see it in action in [[http://www.youtube.com/watch?v=8GnoRYA05c4|this video]], or check this screen-shot:
 +
 +{{ documentation:rel4.0:screenrn40.png |}}
 ===== OpenNebula Drivers ===== ===== OpenNebula Drivers =====
  
-  * **VMware**, the whole set of VMware drivers, storage, networking and virtualization has been greatly improved. The storage system has been simplified and made more efficient, see more here :FIXME:. The networking drivers have been also streamlined. Monitoring of ESXi hosts is now complete and the functionality of the virtualization drivers is now leveled with KVM and Xen. In the process the runtime dependencies of VMware has been reduced by accessing the native VMware VI API.+The back-end of OpenNebula has been also improved in several areas, as described below: 
 +  
 +==== Authentication drivers ==== 
 +  * **CRL support**, [[http://opennebula.org/documentation:rel4.0:x509_auth#configuration|read this to add revocation list]]. 
 +  * **Better DN management**, there is no limitation now to the DN characters, also the authentication process has been fixed, [[http://dev.opennebula.org/issues/1741|read this if you are interested]].
  
-  * **Xen**, support for the Xen4 interfaces through the xl command. Xen3 is totally supported with its own set of drivers+==== Virtualization Drivers ==== 
 +  * **Support for Xen 3 & Xen 4**, better defaults are now for both Xen versions without the need of adapting them. 
 +  * **New attributes**: KVM includes a couple of new attributes, CACHE can be now set in disk attachments and the IO attribute can be defined for DISKS. 
 +  * **More defaults**: a default can be now defined for the raw attribute. Also VM supports a default NIC model. 
 +  * **Custom attributes for VMware VMX files**: VMware users need to define the guestOS attribute, this and any other data can be defined in the VMX files. [[http://opennebula.org/documentation:rel4.0:template?&#raw_section|See an example here]].
  
-===== OpenNebula Gate. NEW COMPONENT! =====+==== Storage Drivers ==== 
 +  * **Improved iSCSI support**, to improve the concurrency of the TGT server. 
 +  * **Ceph Datastore**, a brand new Datastore and Transfer Manager that uses the Ceph FS, [[http://opennebula.org/documentation:rel4.0:ceph_ds|read here if you are a Ceph user]].
  
-OpenNebula Gate (onegate) is the VM gate to OpenNebula. With a security token the VMs can callback home and report guest and/or application status in a simple way, that can be easily queried through OpenNebula interfaces (Suntone, CLI or API).+===== Scheduler ===== 
 +  * **Cluster attributes for VM placement**, you can include cluster and host attributes in your requirements and rank expressions. This is a very easy way to tag all the hosts of a cluster with a given property, [[http://opennebula.org/documentation:rel4.0:template#requirement_expression_syntax|see here examples]] 
 +  * **Affinity policies**, There is a special variable, CURRENT_VMS, that can be used to deploy VMs in a Host where other VMs are (not) running, [[http://opennebula.org/documentation:rel4.0:template#requirement_expression_syntax|see here examples]] 
 +  * **Any host attribute for scheduling expressions**, if you need an even more flexible requirement or rank mechanism you can use Xpath to refer to any host attribute. 
 +  * **Scheduler feedback through VM tags**, the VM is not deployed?, now  the scheduler will send you feedback through the VM properties.
  
-OpenNebula Gate metrics can be also used in conjuntion with OneFlow to develop advanced auto-scaling policies. More information about OpenNebula Gate here :FIXME:+===== OpenNebula API's ===== 
 +Although OpenNebula 4.0 is a major release, we have kept compatibility at the API level. Legacy method names can be used at the XML-RPC and Ruby and JAVA bindings (it'd be a good idea to start using the new ones, though).
  
-===== Sunstone =====+  * **Retrieve OpenNebula configuration**: New methods to retrieve the running configuration of the OpenNebula daemon.
  
-Sunstone has been polished since its redesign in 4.0: +  * **Ruby gems**: The Ruby bindings are now also packed as a gem, [[https://rubygems.org/gems/opennebula/versions/3.9.80.beta|see here]] [[https://rubygems.org/gems/opennebula-cli/versions/3.9.80.beta|and here]].
-  * **Improved VNC**, you can now detach VNC sessions from the Sunstone tab. This let you use the whole window area, prevents synchronization problems with mouse pointers, and... yes make ESC key to work! +
-  * **VM definition update**, the template dialog is also used to update your VM definitions without the need to go to the text based view. +
-  * **Self-service view**, we have a created a "cloudy" provisioning scheme for users, see more on this here :FIXME: +
-  * **Performance improvements**, internal improvements in the information management and resource access.+
  
-===== OpenNebula Flow. NEW COMPONENT! =====+===== OCCI & EC2 Interfaces =====
  
-:FIXME: Include brief description and summary of new features. Now included in the main distribution.+  * **Rackup and memcache**: If you need to scale your public Cloud servers, they now support rack and memcache. [[http://opennebula.org/documentation:rel4.0:sunstone#running_sunstone_in_apache_2_or_nginx|If you are interested read this]]
  
-  * Elasticity policies +====== Migrating from OpenNebula 3.8 ======
-  * Service management, recover of fault situations, increase/decrease of cardinality, role operations.... +
-  * Updated sunstone interface+
  
-====== Migrating from OpenNebula 4.0 ======+There have been minor changes in the OpenNebula DB schema to solve [[http://dev.opennebula.org/issues/1813|bug related with large deployments]], snapshots & generic data. These changes are automatically managed by the migration process, but if you have developed any customization you may need to update it.
  
-:FIXME:+A [[http://opennebula.org/documentation:rel4.0:upgrade|detailed upgrade process can be found in the documentation]].
  
 +For a complete set of changes to migrate from a 3.x installation please refer to the [[http://opennebula.org/documentation:rel4.0:compatibility|Compatibility Guide]]. You should also read this document if you are an OpenNebula 3.x user.
 ====== Getting the Software & Documentation ====== ====== Getting the Software & Documentation ======
  
Line 56: Line 93:
 Please report any bug or send feedback at the [[http://dev.opennebula.org/|development portal]] or at the [[http://www.opennebula.org/community:mailinglists|mailing list]]. Please report any bug or send feedback at the [[http://dev.opennebula.org/|development portal]] or at the [[http://www.opennebula.org/community:mailinglists|mailing list]].
  
-The documentation of OpenNebula 4.2 [[http://opennebula.org/documentation:rel4.2|can be found here]].+The documentation of OpenNebula 4.0 [[http://opennebula.org/documentation:rel4.0|can be found here]].
  
 ====== Acknowledgements ====== ====== Acknowledgements ======
-:FIXME: 
 The OpenNebula project would like to thank the [[http://www.opennebula.org/about:contributors|community members]] and [[http://www.opennebula.org/users:users|users]] who have contributed to this software release by being active with the discussions, answering user questions, or providing patches for bugfixes, features and documentation. The OpenNebula project would like to thank the [[http://www.opennebula.org/about:contributors|community members]] and [[http://www.opennebula.org/users:users|users]] who have contributed to this software release by being active with the discussions, answering user questions, or providing patches for bugfixes, features and documentation.