8.3.2.4. v4.2.14ΒΆ

commit d06a8ed905620be91c03460c4309a57afd4b09ee
Author: Greg Althaus <galthaus@austin.rr.com>
Date:   Wed May 13 11:54:55 2020 -0500

    fix(backend): Update machine token to have token access

M   backend/machines.go
M   go.mod
M   go.sum

commit b9e7b15258111c5046f5f929410eb533195b1a31
Author: Victor Lowther <victor.lowther@gmail.com>
Date:   Mon May 11 11:34:12 2020 -0500

    feat(machines): Add a HardwareAddr index to Machines.

    Recent events have shown us that relying on the machine Address to be
    populated, sane, and up-to-date is not a winning strategy in the face
    of DHCP servers that are not under out control -- if those DHCP
    servers are oversubscribed, then it is possible for the IP address of
    a system to change any time it is not up and running and under our
    control.  However, we still need to be able to create new Machines,
    and we need a better method of checking whether or not a Machine is
    already present based on a set of known criteria.  Probably the best
    set of known criteria is the set of MAC addresses present on the
    system, but we don't have a good way of querying for nodes based on
    that information.  As a starting point, add an Index to Machines that
    allows us to see what Machines have HardwareAddrs we are interested
    in.

    While we are at it, make machine validation use the new Index to make
    sure machines do not have overlapping HardwareAddrs, and stop
    uniqueness checking on Machine.Address if skipIPBasedBooting is true.

M   backend/machines.go
M   clitest/test-data/output/TestCorePieces/machines.indexes/stdout.expect

End of Note