Compatibility Guide 3.4
This guide is aimed at OpenNebula 3.2 users and administrators who want to upgrade to the latest 3.4 version. The following sections summarize the new features and usage changes that should be taken into account, or prone to cause confusion. You can check the upgrade process in the following guide
Visit the Features list and the Release Notes for a comprehensive list of what's new in OpenNebula 3.4.
OpenNebula 3.4 supports multiple datastores. This replaces the previous Image Repository.
:novnc_path
has been replaced by :vnc_proxy_path
in sunstone-server.conf
. It is now a full path to the proxy file.sunstone-server.conf
::vnc_proxy_support_wss
: Specify support for secure websockets connection.:vnc_proxy_cert
: Path to certificate.:vnc_proxy_key
: Path to key.occi-server.conf
::vnc_enable
: Enable websockets based vnc console support.:vnc_proxy_base_port
: Base port to run vnc proxy.:vnc_proxy_path
: Full path to proxy file.:vnc_proxy_support_wss
: Enable wss connections.:vnc_proxy_cert
: Path to certificate.:vnc_proxy_key
: Path to key.sunstone-plugins.yaml
configuration file. Following #1112, Sunstone menus have been reworked and base plugins need to be loaded in a different order (and new ones need to be added to it). Please proceed to update this configuration file with the new one provided in this release.econe.conf
elasticips_vnet_id
VirtualNetwork containing the elastic ips to be used with EC2. If no defined the Elastic IP functionality is disabled.associate_script
Script to associate a public IP with a private IP; arguments: elastic_ip private_ip vnet_template(base64_encoded)disassociate_script
Script to disassociate a public IP; arguments: elastic_ipecone.conf
and occi-server.conf
datastore_id
Datastore in which the Images uploaded through EC2/OCCI will be allocated, by default 1 cluster_id
Cluster associated with the EC2 resources, by default no Cluster is definedopennebula
CloudAuth. Using this method the authentication will be done by the opennebula core using the driver defined for the user. For instance, a user interacting with OpenNebula through Sunstone can be authenticated using the LDAP driver.New CLI commands:
Changed CLI commands:
New EC2 CLI commands:
New OCCI CLI commands:
New verbose option for occi-* list commands
delete
actions in opennebula.js
, ozones.js
, occi.js
have been renamed to del
, to avoid use of the reserved word. For example, a call to OpenNebula.Host.delete()
should now be OpenNebula.Host.del()
.DISK/SOURCE
can't be used anymore, all files need to be registered as an Image and be referenced in the VM template.There have been some modification on the Transfer Manager/Datastore architecture. The basic Transfer Driver protocol has been preserved, although some adaptation is needed in order to make custom drivers to work with the new release:
/etc/tm/tm_<driver>.conf
does not exist. Instead, the driver will automatically look in <remotes_dir>/tm/<driver>/<action>
. where action is: clone
, context
, delete
, ln
, mkimage
, mkswap
, mv
or mvds
.mv
script is now conceptually different: it moves disk images between system datastores across different hosts. The mvds
, which moves disk images back to their original datastore, is more similar to the old mv
script.clone
and ln
are always performed remotely) they're backwards compatible.Removed files:
New files: