maas-devel team mailing list archive

[Julian Edwards <julian.edwards@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30/05/14 20:22, Mark Shuttleworth wrote:
> Perhaps add "alias" an int, uniqued, nullable, so we can model all
> the aliases (null being the base NIC IP that DHCP sends).

Alias is metadata about the MAC really, so this possibly belongs on
the nic_node (née mac_address) table.  We would remove the unique key
from MAC and make it unique across MAC and alias instead.

Alternatively, we use the separate link table I previously mentioned
to track aliases and link node_nic and IPAddress.

(Having just read your email reply to Gavin in this thread, you also
mention having a new table, and I think this is a better way to go.)

> I don't think Dean's case actually belongs in this table at all.
> We don't write Dean's "spare" IP addresses into DHCP, we just BLOCK
> them from being used in DHCP, they are reserved for the user. They
> are more like entries in DHCPhost that don't actually have mac
> addresses associated with them.

Agreed.  We need to totally separate the dynamic pool from the static
anyway to fix the main bug we have, so Dean's case is just one that
reserves a static IP.

To do that we need to put a user FK somewhere; probably on the
DHCPHost table.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlOL29YACgkQWhGlTF8G/HfGagCeKqFJhthWtCEN1k3MoTvorvc/
zHwAnioAZw1IYuad99qD2FZilOG0Npe9
=dBut
-----END PGP SIGNATURE-----