[one-users] IP reservations in virtual networks

[Carlos Martín Sánchez]

Hi,

VNet hold/release is not meant for your use case, it was implemented to
hold IPs that may be temporarily used by a physical host, or some machines
not managed by OpenNebula.

Maybe you could put your VM in the hold state [1], that will take the vnet
lease, and you can later release the VM to be deployed.

Regards

[1]
http://opennebula.org/documentation:rel3.8:vm_guide_2#life-cycle_operations
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>


On Wed, Jan 16, 2013 at 2:47 PM, Rolandas Naujikas <
rolandas.naujikas at mif.vu.lt> wrote:

> Hi,
>
> When trying to configure virtual router VM I got into a problem.
>
> I want to configure its private IP fixed to some low IP (e.g. 10.1.1.1).
>
> I'm creating virtual (isolated) network X, where I defines
> IP_START=10.1.1.3, IP_END=10.1.1.254, but opennebula doesn't allow
> instantiate a VM with NIC=[IP=10.1.1.1,NETWORK=X], because 10.1.1.1 is not
> in range IP_START to IP_END.
>
> If I put IP_START=10.1.1.1 to X, then some other user VM could take this
> IP. If I put 10.1.1.1 on hold (onevnet hold), then I cannot start VM with
> this IP until I release it (onevnet release), but there is always some time
> window when someone from users could take it. It looks like onevnet
> hold/release is almost useless.
>
> Regards, Rolandas
> ______________________________**_________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**org<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130116/bcb6cab4/attachment-0002.htm>