• Support for Ceph datastore
• There is a new Datastore type that lets you store plain files to be used as VM kernels, ramdisks or context files.
• There are new image types: KERNEL, RAMDISK and CONTEXT
• The system datastore used by each cluster is now set adding it to the cluster, instead of updating the cluster's template attribute SYSTEM_DS.

• The monitoring process has been greatly improved, to reduce network connections.
• WILD and ZOMBIE VMs are reported in the host information

• You may resize the capacity assigned to a Virtual Machine in terms of the virtual CPUs, memory and CPU allocated
• Users can create and restore VM snapshots. These snapshots include the whole system: memory and disks.
• You can take a snapshot of a VM disk to preserve or backup its state at a given point of time, using the command 'onevm disk-snapshot --live'.
• In a similar way to the disk hotplug functionality, you can now attach or detach network interfaces while the VM is running.
• The onevm saveas (now renamed to disk-snapshot) now requires the VM to be in the RUNNING state.
• Some VM actions can be scheduled to be executed at a later date & time using the new onevm –schedule option (#1483)
• VMware VMs can now use the RAW section of the VM Template to add metadata straight to the .vmx file (DATA_VMX). This comes in handy to specify for example a specific guestOS type.
• KVM VMs can use the IO attribute in the disks.
• You can now merge another template to the one being instantiated. The new attributes will be added, or will replace the ones fom the source template. This can be more convinient that cloning an existing template and updating it

<xterm> $ onetemplate instantiate 6 –cpu 2 –memory 1024 </xterm>

• Each history record included a generic reason. In OpenNebula 4.0 it also includes the specific action that closed the record, which can be seen in the output of 'onevm show' and 'oneacct':

<xterm> VIRTUAL MACHINE HISTORY SEQ HOST ACTION REAS START TIME PROLOG

0 host02          live-migrate     user  04/05 15:21:10   0d 00h00m   0h00m03s
1 host01          suspend          user  04/05 15:21:24   0d 00h00m   0h00m00s

VID HOSTNAME ACTION REAS START_TIME END_TIME MEMORY CPU NET_RX NET_TX

 0 host02          live-migrate     user 04/05 15:21:10 04/05 15:21:27   128M   1   0.6K   0.2K
 0 host01          suspend          user 04/05 15:21:24 04/05 15:21:32   128M   1   0.6K   0.2K

</xterm>

• The default permissions given to newly created resources can be set in globally in oned.conf, or individually for each user with 'oneuser umask'.
• Administrators can set default quota limits that apply to all users or groups.
• ACL rules can now apply to Hosts, Datastores or VNets inside a Cluster. For example, the following rule allows users in group 106 to deploy VMs in Hosts assigned to the cluster 100

@106 HOST/%100 MANAGE

• Rename operation for templates, images, VMs and VNets

Some onevm commands have been renamed. This is the complete list of onevm sub-commands:

New CLI commands:

• onevm snapshot-create snapshot-revert and snapshot-delete
• onevm nic-attach and nic-detach
• onevm resize
• onevm undeploy
• oneuser umask

Changed CLI commands:

• New option –hold for 'onevm create' and 'onetemplate instantiate'. Using this flag, the new VMs are created on hold state instead of pending. VMs in this state are ignored by the scheduler, giving users the chance release them later or to deploy them manually.
• New option –enforce for 'onevm deploy' and 'onevm migrate'. Using this flag, the core will enforce that the target host's capacity is not overcommitted.
• 'onetemplate instantiate' will accept a template file to merge with the Template being instantiated.
• New option ''--live'' for 'onevm disk-snapshot' (previously named 'onevm saveas').

Options:

• New options –user and –password are available for all commands. They replace the current credentials, making it easier for administrators to quicky execute commands as another user.

Some of these changes are better explained, with examples, in this blog post.

• The VM REQUIREMENTS and RANK attributes must be now named SCHED_REQUIREMENTS and SCHED_RANK (#1483)
• SCHED_REQUIREMENTS and SCHED_RANK can be edited in the VM template (#1483)
• A new keyword, CURRENT_VMS, can be used in the SCHED_REQUIMENTS expression to deploy VMs in the same hosts where other VMs are (not) running (#1675)
• SCHED_RANK expression can use first level attributes, e.g. RANK=“ID” to sort the hosts by their /HOST/ID element (#1553)
• SCHED_REQUIREMENTS and SCHED_RANK expressions can use xpath to identify elements, e.g. REQUIREMENTS=“\”/HOST/HOST_SHARE/MAX_MEM\“ > 0” (#1747)
• If the scheduler cannot find a suitable host for a VM, or any other problem is found, a message is stored inside the VM template attribute SCHED_MESSAGE (#846)
• SCHED_REQUIREMENTS and SCHED_RANK expressions can use attributes from the Host's Cluster template (#1554)

• Sunstone views. This is a new feature that allows you to customize the UI for different users or user groups, so the interface implements the provisioning model for each role. Sunstone views replaces the 3.x self-service portal. Sunstone views does not require any additional service (apart from the sunstone server). Sunstone ships with two predefined views admin and user, we may add a couple of more pre-defined views for the final release.

• sunstone-plugins are now configured using the new Sunstone views. This is a new feature that allows you to customize the UI for different users or user groups, so the interface implements the provisioning model for each role.

• Support for IPv6 addresses.
• OpenVswitch drivers with and without bridge compatibility layer.

• Currently, OpenNebula Apps are not supported with this new version. After the final 4.0 release there will be a new version of OpenNebula Apps, fully integrated with the new Sunstone.

• New states and transitions. These transitions are only relevant to developers, users will perceive the same functionality.
  • UNDEPLOYED
  • CLEANUP_DELETE
  • HOTPLUG_SNAPSHOT
  • HOTPLUG_NIC
  • HOTPLUG_SAVEAS
  • HOTPLUG_SAVEAS_POWEROFF
  • HOTPLUG_SAVEAS_SUSPENDED
  • SHUTDOWN_UNDEPLOY
  • EPILOG_UNDEPLOY
  • PROLOG_UNDEPLOY
  • BOOT_UNDEPLOY
• The REASON element inside each history record has changed.

3.8 values:

NONE        = 0  Normal termination
ERROR       = 1  The VM ended in error
STOP_RESUME = 2  Stop/resume request
USER        = 3  Migration request
CANCEL      = 4  Cancel request

4.0 values:

NONE  = 0 History record is not closed yet
ERROR = 1 History record was closed because of an error
USER  = 2 History record was closed because of a user action

• Each history record includes an ACTION element, see the xsd file reference.

New xml-rpc methods:

• New rename methods
• New one.system.config
• New user/group quota.info and quota.update
• one.vm.snapshot methods
• one.vm.resize
• one.vm.attachnic .detachnic

Changed xml-rpc methods:

• one.vm.savedisk has a new param to save the disk immediately or when the VM shuts down
• one.vm.deploy and .migrate have a new param, enforce
• one.vm.allocate and one.template.instantiate have a new param to create VMs on hold instead of pending
• one.template.instantiate extra param to merge attributes
• one.template.action has new action names

• Library file is now called 'opennebula', require it using:

require 'opennebula'

• Now OCA is packaged as a ruby gem, if you are developing on machine that does not have OpenNebula package installed you can install it with this command:

<xterm> $ gem install opennebula-oca –pre </xterm>

X509:

• CRL Checking can be enabled in /etc/one/auth/x509_auth.conf.
• Escaped DN's

• VMware VMs can now use the RAW section of the VM Template to add metadata straight to the .vmx file (DATA_VMX). This comes in handy to specify for example a specific guestOS type.

• Support for ssh based storage for VMware infrastructures has been dropped. There are two possible scenarios now: nfs or vmfs based storage.

• You can set the default configuration for the cache type on newly attached disks.
• New default attribute RAW in /etc/one/vmm_exec/vmm_exec_kvm.conf. For example:

RAW  = "<devices><serial type=\"pty\"><source path=\"/dev/pts/5\"/><target port=\"0\"/></serial><console type=\"pty\" tty=\"/dev/pts/5\"><source path=\"/dev/pts/5\"/><target port=\"0\"/></console></devices>"

• The Monitoring process has been improved to reduced connections to the hosts. If you have developed a custom information driver you may want to extended to leverage this new feature

• Sunstone can now be served by Apache or nginx web servers using Phusion Passenger moduler. This kind of deployment adds better concurrency and lets us add an https endpoint.

Changes in /ect/one/oned.conf

• DEFAULT_UMASK The permissions for newly created objects can be set globally in oned.conf, or individually for each User.
• OpenNebula driver names changed and now they are not prefixed by the driver type. For example, im_kvm changed to kvm, vmm_xen to xen and so on. To add a kvm host the command will be:

<xterm> $ onehost create host_name –im kvm –vm kvm –net dummy </xterm>

Changes in /etc/one/sunstone-server.conf

Changes in /etc/one/auth/x509_auth.conf

• x509 driver is now able to check certificate revocation list just drop the CRL file in the CA directory. To force its checking uncomment this line:

:check_crl: true

Changes in /var/lib/one/remotes/vmm/kvm/kvmrc

• DEFAULT_ATTACH_CACHE default cache type for new attached disks.

Changes in /etc/one/occi-server.conf

Changes in EC2 Server configuration files: