I were testing the new RPC calls and it seems that some of them have changed so we have found some backwards incompatibilities between the 4.x and 5.x versions. In our case the most important change is related with the host management.
it seems that
one.host.allocate has changed since the last version:
Using the 4.x rpc call we get this error:
[ERROR] _rpc failed to make request faultCode -501 faultString Parameter that is supposed to be integer is not method one.host.allocate args [string, hyp101.altaria.os], [string, kvm], [string, kvm], [string, ovswitch], [int, -1]
The reason is that
vn_mad is not used by the new onehost command, and also the VNET template should be changed. This is done on purpose? It’s not commented in the compatibility guide and it breaks the compatibility with some RPC clients.
This change also raises another question, how is possible now to setup an heteregenous hyp cluster with OVS and linux bridges hyps? In OpenNebula 4.x we were able to setup the vn_mad for each host, so we were able to include linux and OVS bridges in different hypervisors, thanks to
OVS_BRIDGE variable, as example we had for an specific
NAME = "vscnetwork"
and we had hosts with
dummy and also hyps with
ovsswitch network drivers, so OVS_BRIDGE was used for OVS hyps, how is possible to keep this heterogeneous configuration now? It’s still supported?
Thanks in advance!
About the XML-RPC API, you are totally right, we missed the compatibility
notes about that. Sorry for the inconveniences
About the OVS_BRIDGE parameters, now the VN_MAD drivers are attached to the
network. This way a host can implement multiple network types, (as opposed
to the OVS_BRIDGE parameter to implement the same network with different
drivers, but only to some extent).
So you can have openvswitch networks and linux bridges networks, and each
host can implement any of them. If you only have support for a given
network type on a host, you can create a cluster to be sure that only VMs
of a given type are allocated to that host (in 5.0 you can add a VM to
Thanks a lot for your feedback! We will update our vnet templates to include the new parameter.
About the RPC changes that means that the opennebula clients must be updated to support ONE 5.0 right?
About the RPC changes that means that the opennebula clients must be
updated to support ONE 5.0 right?
or reply to this email to respond.
You are receiving these emails cause you have enabled mailing list mode.
To unsubscribe from these emails, click here
Alternatively you may click here
<email@example.com?subject=unsubscribe> to unsubscribe via email.
Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | firstname.lastname@example.org | @OpenNebula