Compatibility Guide 4.4
This guide is aimed at OpenNebula 4.2 users and administrators who want to upgrade to the latest 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 4.4.
fixed
. This policy will rank hosts and datastores according looking for a PRIORITY
attribute that can be set manually by the administrator.DEV_PREFIX
, is now 'hd' for cdrom type disks, regardless of the value set in oned.conf.# 4.2 arguments hypervisor=$1 host_id=$2 host_name=$3 # 4.4 arguments hypervisor=$1 datastore_location=$2 collectd_port=$3 monitor_push_cycle=$4 host_id=$5 host_name=$6
ec2.conf
file was renamed to ec2_driver.default. In this file you can define the default values for ec2 instances.ec2rc
file has been removed. A new configuration file is available: ec2_driver.conf
. ec2_driver.conf
. More infoCLOUD
attribute has been deprecated, now you have to use HOST
to define more than one EC2 sections in the template. More infoAUTHORIZED_PORTS
: we removed it because the right approach is to use SECURITY_GROUPS. What OpenNebula was doing was to modify the default security group, but we now think that a much better approach is to achieve the same using different SECURITY GROUPS and assigning VMs to them.USERDATAFILE
: OpenNebula 4.4 is dropping support due to a security risk, it allowed practically everyone to retrieve files from the OpenNebula front-end and stage them into an Amazon EC2 VM. The alternative is to read the file and set its contents into the USERDATA
attribute, which is still supported.AWS_DNS_NAME AWS_PRIVATE_DNS_NAME AWS_KEY_NAME AWS_AVAILABILITY_ZONE AWS_PLATFORM AWS_VPC_ID AWS_PRIVATE_IP_ADDRESS AWS_IP_ADDRESS AWS_SUBNET_ID AWS_SECURITY_GROUPS AWS_INSTANCE_TYPE
IPADDRESS
monitoring attribute has been renamed to AWS_PRIVATE_IP_ADDRESS
.PUBLIC_CLOUD
. This allows users to create templates that can be run locally, or in different public cloud providers. Public cloud vmm drivers must make use of this:DISK = [ IMAGE_ID = 7 ] PUBLIC_CLOUD = [ TYPE = "jclouds", JCLOUDS_DATA = "..." ] PUBLIC_CLOUD = [ TYPE = "ec2", AMI = "...", KEYPAIR = "..." ]
:use_file_templates:
parameter in econe.conf. But using the new system is recommended, since file based templates will be removed soon.