bootstrap vm should acquire a sticky ip address

[Edward Hope-Morley]

The Juju bootstrap vm does not currently acquire a sticky ip address from the static pool. The result is that we create the bootstrap vm, then commission the others, then acquire sticky ip addresses for nodes that have requested them. Trouble is that the bootstrap vm gets allocated an ip from the static pool before we attempt to acquire/reserve others so we easily get conflicts.

[Nobuto Murata (nobuto)]

I'm not sure I'm following you, but usually I allocate sticky IP addresses for physical nodes from outside of static pool. Juju bootstrap is not the only one to acquire IP address from static pool. Juju's feature "address-allocation" which is currently under development also consumes IP addresses from static pool.

If I have 10.0.0.0/24 network, usually I allocate like below to assign desired IP address for physical nodes:
10.0.0.2-10.0.0.100: sticky IP address for physical nodes
10.0.0.101-10.0.0.120: static pool for Juju bootstrap
10.0.0.121-10.0.0.240: dynamic pool

[Edward Hope-Morley (hopem)]

@nobuto what i am seeing here is e.g.

With pool like:

  static: 10.0.0.2 -> 10.0.0.10
  dynamic: 10.0.0.11 -> 10.0.0.20

And one extra node with:

  name: node1
  sticky_ip_address:
    mac_address: "38:63:bb:43:19:dc"
    requested_address: 10.0.0.2

If you run maas-deployer and it will create the bootstrap vm first which, since it has not requested a sticky ip, will get allocated one by MAAS which in the above case will most probably be 10.0.0.2 so it will conflict with the address requested by node1. We can simply get round this by having the bootstrap node also request a sticky ip which it should do in any case since we never want its address to change.

[Edward Hope-Morley (hopem)]

And according to https://maas.ubuntu.com/docs/static-ips.html sticky ip addresses must come from the static pool.