Ask Your Question

osexplorer's profile - activity

2017-06-10 12:33:24 -0600 received badge  Famous Question (source)
2017-06-10 12:33:24 -0600 received badge  Notable Question (source)
2017-04-24 05:39:35 -0600 received badge  Famous Question (source)
2017-03-17 02:46:09 -0600 received badge  Notable Question (source)
2017-03-16 06:24:47 -0600 received badge  Popular Question (source)
2017-03-16 03:28:59 -0600 answered a question When is DHCP lease time used?

I am not looking about the configuration possibilities of the parameters , but how Openstack applies the DHCP lease handling. Lets assume there is a short lease time set, for example 120 sec. IP addresses are taken from a small address pool. There are so many VMs instantiated that the pool is exhausted. Now I want to add another VM. The lease of some of the previously instantiated VMs is expired. Will the instantiation of the new VM be successful? Will it get an IP address from one of the expired IP addresses? Note that in this example the lease (per IP address) shall not periodically be renewed.

According to the documentation the instantiation of the new VM should fail. Which also means that the definition of the lease time has no relevance.

Hi Bernd, thank you for your comments! Unfortunately Openstack does not distinguish between fixed and dynamically assigned IP addresses. There are treated somehow as the same. Maybe it is better to talk about "static fixed" and "fixed" IPs. For me a "static fixed" IP is an address that is defined and assigned to the port explicitly, i.e. explicitly defined on the port in a HOT template. These IP addresses do not expire and are released if the port is terminated.

Fixed IP addresses are assigned via DHCP. A port (in HOT) that is connected to a network can be defined without fixed IP address. The IP address is taken from the IP pool that is defined in the subnet definition for the respective network. Here I have expected that the validity of the address depends on the DHCP lease time.

2017-03-15 11:15:30 -0600 asked a question When is DHCP lease time used?

Hi all,

The latest Openstack documentation for "Managing IP addresses" states that:

Each instance has a private, fixed IP address and can also have a public, or floating IP address. Private IP addresses are used for communication between instances, and public addresses are used for communication with networks outside the cloud, including the Internet. When you launch an instance, it is automatically assigned a private IP address that stays the same until you explicitly terminate the instance. Rebooting an instance has no effect on the private IP address.

I would expect that the validity of an IP address that has automatically been assigned by DHCP expires when the DHCP lease time is expired. According to above statement the IP address is kept until the instance is terminated (and all ports of the VM are terminated as well). It seems that the allocated IP address is not released at lease expiry and the release is independent of the parameter dhcp_lease_duration = 86400 in /etc/neutron/dhcp_agent.ini

In my concrete case the DHCP lease time will not be extended by sending periodically DHCPREQUEST's to avoid lease time expiry.

Can someone explain the usage of the dhcp_lease_duration parameter?

2016-06-10 08:52:21 -0600 received badge  Enthusiast
2016-03-23 02:49:09 -0600 received badge  Popular Question (source)
2016-03-22 08:29:49 -0600 received badge  Student (source)
2016-03-21 10:06:53 -0600 asked a question VM migration scheduler


I am looking for a possibility to restrict the migration of Virtual Machines. I have a group of VMs that are not allowed to perform a migration at the same time.

Is there any possibility to define a rule that only one VM can be migrated at the same time?