x/flame
Code Issues Proposed changes
d685642ba0
flame/doc/source/limitations.rst
Yves-Gwenael Bourhis e798119841 Addapted flame to openstacksdk and shade. 
Flame needed pemanent adjustments to mathe the changes in the
python-openstackclients. We now use openstacksdk or shade which will
handle themselves the compatibility.

We also made flame modular so that any-one can add features by
implementing there own flame managers and adding their modules to
the `openstack_flame` entry point.

This new flame version is also fully compatible with python 3.

Change-Id: I586a165b5022031963f504874bd50e1b11fe0d27
2018-11-22 11:50:41 +01:00

547 B
Raw Blame History

Limitations

Subnets created before Kilo can have their DHCP server's IP in the middle of an allocation pool. This causes the first VMs to be allocated the first free IP addresses of a pool, for example, with a pool starting at 10.0.0.2 :

  • 10.0.0.2 : vm1
  • 10.0.0.3 : vm2
  • 10.0.0.4 : DHCP server
  • 10.0.0.5 : vm3

When this stack is imported in Heat, the DHCP server IP is set to the lowest free IP address of its pool. Depending on the VM creation order, the DHCP address can either collide with vm1's or vm2's IP.