[one-users] Changes to onevnet will not be available to new VM?

[Carlos Martín Sánchez]

Hi,

On Wed, Oct 1, 2014 at 1:23 PM, Martin Alfke <tuxmea at gmail.com> wrote:

> Hi,
>
> when changing the network subnet on a onevnet (onevnet update), a newly
> spawned machine will not make use of the updated network settings.
> Using OpenNebula 4.6 on centos with 802.1q networks.
>
> e.g. onevent xml output prior the change
>
> <VNET>
>   <ID>137</ID>
>   <UID>0</UID>
>   <GID>0</GID>
>   <UNAME>oneadmin</UNAME>
>   <GNAME>oneadmin</GNAME>
>   <NAME>test</NAME>
>   <PERMISSIONS>
>     <OWNER_U>1</OWNER_U>
>     <OWNER_M>1</OWNER_M>
>     <OWNER_A>0</OWNER_A>
>     <GROUP_U>0</GROUP_U>
>     <GROUP_M>0</GROUP_M>
>     <GROUP_A>0</GROUP_A>
>     <OTHER_U>0</OTHER_U>
>     <OTHER_M>0</OTHER_M>
>     <OTHER_A>0</OTHER_A>
>   </PERMISSIONS>
>   <CLUSTER_ID>-1</CLUSTER_ID>
>   <CLUSTER/>
>   <TYPE>0</TYPE>
>   <BRIDGE>foo</BRIDGE>
>   <VLAN>0</VLAN>
>   <PHYDEV/>
>   <VLAN_ID>1507</VLAN_ID>
>   <GLOBAL_PREFIX/>
>   <SITE_PREFIX/>
>   <RANGE>
>     <IP_START>10.186.0.10</IP_START>
>     <IP_END>10.186.0.255</IP_END>
>   </RANGE>
>   <TOTAL_LEASES>0</TOTAL_LEASES>
>   <TEMPLATE>
>     <NETWORK_ADDRESS><![CDATA[10.186.0.0]]></NETWORK_ADDRESS>
>     <NETWORK_MASK><![CDATA[255.255.254.0]]></NETWORK_MASK>
>   </TEMPLATE>
>   <LEASES/>
> </VNET>
>
>
> onevnet output after doing some changes to the network:
>
> <VNET>
>   <ID>136</ID>
>   <UID>0</UID>
>   <GID>0</GID>
>   <UNAME>oneadmin</UNAME>
>   <GNAME>oneadmin</GNAME>
>   <NAME>test</NAME>
>   <PERMISSIONS>
>     <OWNER_U>1</OWNER_U>
>     <OWNER_M>1</OWNER_M>
>     <OWNER_A>0</OWNER_A>
>     <GROUP_U>0</GROUP_U>
>     <GROUP_M>0</GROUP_M>
>     <GROUP_A>0</GROUP_A>
>     <OTHER_U>0</OTHER_U>
>     <OTHER_M>0</OTHER_M>
>     <OTHER_A>0</OTHER_A>
>   </PERMISSIONS>
>   <CLUSTER_ID>-1</CLUSTER_ID>
>   <CLUSTER/>
>   <TYPE>0</TYPE>
>   <BRIDGE>foo</BRIDGE>
>   <VLAN>0</VLAN>
>   <PHYDEV/>
>   <VLAN_ID>1507</VLAN_ID>
>   <GLOBAL_PREFIX/>
>   <SITE_PREFIX/>
>   <RANGE>
>     <IP_START>10.186.0.10</IP_START>
>     <IP_END>10.186.0.255</IP_END>
>   </RANGE>
>   <TOTAL_LEASES>0</TOTAL_LEASES>
>   <TEMPLATE>
>     <BRIDGE><![CDATA[foo]]></BRIDGE>
>     <IP_END><![CDATA[10.186.0.255]]></IP_END>
>     <IP_START><![CDATA[10.186.0.100]]></IP_START>
>     <NETWORK_ADDRESS><![CDATA[10.186.0.0]]></NETWORK_ADDRESS>
>     <NETWORK_SIZE><![CDATA[255.255.0.0]]></NETWORK_SIZE>
>     <ONE_0><![CDATA[0]]></ONE_0>
>     <PROTOCOL><![CDATA[ipv6]]></PROTOCOL>
>     <VLAN_ID><![CDATA[1507]]></VLAN_ID>
>   </TEMPLATE>
>   <LEASES/>
> </VNET>
>
>
> All changes are now in the template section.
>
> Can anybody confirm this behaviour?
>
> many thanks,
>
> Martin
>

In ONE 4.6, not all network definition attributes can be changed with
onevnet update. Only bridge, phydev, vlan and vlan_id will be updated.

I guess you wanted to change IP_START. The range of a 4.6 vnet cannot be
updated. What you can do is put the IPs from 10 to 100 on hold.

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org <http://www.opennebula.org/> | cmartin at opennebula.org |
@OpenNebula <http://twitter.com/opennebula> <cmartin at opennebula.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20141002/d22c72bf/attachment-0001.htm>