<div dir="ltr">Hi,<div><br></div><div class="gmail_extra"><div class="gmail_quote">On Wed, Oct 1, 2014 at 1:23 PM, Martin Alfke <span dir="ltr"><<a href="mailto:tuxmea@gmail.com" target="_blank">tuxmea@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
<br>
when changing the network subnet on a onevnet (onevnet update), a newly spawned machine will not make use of the updated network settings.<br>
Using OpenNebula 4.6 on centos with 802.1q networks.<br>
<br>
e.g. onevent xml output prior the change<br>
<br>
<VNET><br>
<ID>137</ID><br>
<UID>0</UID><br>
<GID>0</GID><br>
<UNAME>oneadmin</UNAME><br>
<GNAME>oneadmin</GNAME><br>
<NAME>test</NAME><br>
<PERMISSIONS><br>
<OWNER_U>1</OWNER_U><br>
<OWNER_M>1</OWNER_M><br>
<OWNER_A>0</OWNER_A><br>
<GROUP_U>0</GROUP_U><br>
<GROUP_M>0</GROUP_M><br>
<GROUP_A>0</GROUP_A><br>
<OTHER_U>0</OTHER_U><br>
<OTHER_M>0</OTHER_M><br>
<OTHER_A>0</OTHER_A><br>
</PERMISSIONS><br>
<CLUSTER_ID>-1</CLUSTER_ID><br>
<CLUSTER/><br>
<TYPE>0</TYPE><br>
<BRIDGE>foo</BRIDGE><br>
<VLAN>0</VLAN><br>
<PHYDEV/><br>
<VLAN_ID>1507</VLAN_ID><br>
<GLOBAL_PREFIX/><br>
<SITE_PREFIX/><br>
<RANGE><br>
<IP_START>10.186.0.10</IP_START><br>
<IP_END>10.186.0.255</IP_END><br>
</RANGE><br>
<TOTAL_LEASES>0</TOTAL_LEASES><br>
<TEMPLATE><br>
<NETWORK_ADDRESS><![CDATA[10.186.0.0]]></NETWORK_ADDRESS><br>
<NETWORK_MASK><![CDATA[255.255.254.0]]></NETWORK_MASK><br>
</TEMPLATE><br>
<LEASES/><br>
</VNET><br>
<br>
<br>
onevnet output after doing some changes to the network:<br>
<br>
<VNET><br>
<ID>136</ID><br>
<UID>0</UID><br>
<GID>0</GID><br>
<UNAME>oneadmin</UNAME><br>
<GNAME>oneadmin</GNAME><br>
<NAME>test</NAME><br>
<PERMISSIONS><br>
<OWNER_U>1</OWNER_U><br>
<OWNER_M>1</OWNER_M><br>
<OWNER_A>0</OWNER_A><br>
<GROUP_U>0</GROUP_U><br>
<GROUP_M>0</GROUP_M><br>
<GROUP_A>0</GROUP_A><br>
<OTHER_U>0</OTHER_U><br>
<OTHER_M>0</OTHER_M><br>
<OTHER_A>0</OTHER_A><br>
</PERMISSIONS><br>
<CLUSTER_ID>-1</CLUSTER_ID><br>
<CLUSTER/><br>
<TYPE>0</TYPE><br>
<BRIDGE>foo</BRIDGE><br>
<VLAN>0</VLAN><br>
<PHYDEV/><br>
<VLAN_ID>1507</VLAN_ID><br>
<GLOBAL_PREFIX/><br>
<SITE_PREFIX/><br>
<RANGE><br>
<IP_START>10.186.0.10</IP_START><br>
<IP_END>10.186.0.255</IP_END><br>
</RANGE><br>
<TOTAL_LEASES>0</TOTAL_LEASES><br>
<TEMPLATE><br>
<BRIDGE><![CDATA[foo]]></BRIDGE><br>
<IP_END><![CDATA[10.186.0.255]]></IP_END><br>
<IP_START><![CDATA[10.186.0.100]]></IP_START><br>
<NETWORK_ADDRESS><![CDATA[10.186.0.0]]></NETWORK_ADDRESS><br>
<NETWORK_SIZE><![CDATA[255.255.0.0]]></NETWORK_SIZE><br>
<ONE_0><![CDATA[0]]></ONE_0><br>
<PROTOCOL><![CDATA[ipv6]]></PROTOCOL><br>
<VLAN_ID><![CDATA[1507]]></VLAN_ID><br>
</TEMPLATE><br>
<LEASES/><br>
</VNET><br>
<br>
<br>
All changes are now in the template section.<br>
<br>
Can anybody confirm this behaviour?<br>
<br>
many thanks,<br>
<br>
Martin<br></blockquote><div><br></div><div>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.</div><div><br></div><div>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.</div><div><div dir="ltr"><br></div><div dir="ltr">Regards<br class="">--<br><div>Carlos Martín, MSc<br>Project Engineer</div><div>OpenNebula - Flexible Enterprise Cloud Made Simple<br><div><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="http://www.opennebula.org/" target="_blank">www.OpenNebula.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a> | <a href="http://twitter.com/opennebula" target="_blank">@OpenNebula</a></span><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="mailto:cmartin@opennebula.org" target="_blank" style="color:rgb(42,93,176)"></a></span></div></div></div></div><div> </div></div></div></div>