[one-users] VMs IP Clash after failure

Valentin Bud valentin.bud at gmail.com
Tue Nov 13 04:14:32 PST 2012


Hi Carlos,

On Tue, Nov 13, 2012 at 11:17:29AM +0100, Carlos Martín Sánchez wrote:
> Hi Valentin,
> 
> That's exactly how it works now. When you set
> 
> NIC = [
>   NETWORK_ID = <vnet_id>,
>   IP = <ip>
> ]
> 
> You are not hardcoding the IP, you are requesting that IP from the leases
> of the network. It will be assigned only if it is free, and will be marked
> as used, just like any other IP assigned automatically.

You are right. I have done some test now and it works as you say it
does. 

I meant something else though. I will take it step be step so I can make
myself understood. 

I have one template with ID 17.
```
$ onetemplate show 17 | grep IP
IP="172.16.18.54"
```

I clone the template and try to instantiate it and an error pops up
telling me that the IP address is taken, which is the right thing to do.

Now, as an user when I create a new template, either by `create` or
`clone` I have to *remember* to modify the IP address in case it is in
use. I have to find out which is the next usable IP addresses by looking
at all templates. I can see the active leases using `onevnet show` by I
don't have a way to know if the IP I choose to use in the new template
is in use by other templates or VMs.

That's not a problem, more of a user friendly thing. 

Cheer and Goodwill,
v

> Regards
> --
> 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 Tue, Nov 13, 2012 at 10:39 AM, Valentin Bud <valentin.bud at gmail.com>wrote:
> 
> > Hello Cyrille,
> >
> > I have noticed something this morning about IP addresses management
> > inside OpenNebula and I thought I'd add my opinion.
> >
> > As far as I have noticed whenever you instantiate a machine OpenNebula
> > uses the next IP address from the defined pool in the vnet. That's
> > almost DHCP.
> >
> > One can check the status of the network using `onevnet show <vnet_id>`.
> > Under `USED LEASES` one can see what leases are in use.
> >
> > If, for whatever reason, one wants a certain ip address to use for a
> > particular VM, one can use `IP=x.x.x.x` in the template.
> >
> > I think here arises an issue. Human beings aren't good with numbers,
> > that's one of the reasons we have DNS. I for one, forget which IP is
> > allocated to which VM, I am talking about the ones I specify in the
> > template using `IP`. I don't care which IP is allocated to which VM, I
> > just care which IPs are allocated or, better said, reserved from the pool.
> >
> > I know there tools that perform the specific function of IP address
> > management.
> >
> > OpenNebula could check if the IP address is in use whenever one
> > creates/clones a template. The reserved IP address could be listed
> > with `onevnet show <vnet_id>` under `RESERVED LEASES` or something.
> >
> > What do you people think about this?
> >
> > I also am aware that you guys welcome patches. I wish my Ruby skills
> > were better so I could code this feature by myself. Speaking of Ruby,
> > does anyone have some good docs for a noob? :)
> >
> > Cyrille, I hope I haven't hijacked your thread. I think the above
> > thoughts are connected with your last question from your email. If
> > that's not the case I am sorry.
> >
> > Cheers and Goodwill,
> > v
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >



More information about the Users mailing list