@ltrager (et al)
The change in that thread captures a relatively elegant solution to something that we’ve encountered a few times now - duplicate ‘hardware_uuid’ values being consumed by MAAS (at least in 2.7 and 2.8.1).
In our deployment, 6 physical hardware nodes comprised of identical hardware yield the following UUID: 03000200-0400-0500-0006-000700080009. We’ve had to resort to modifying the database as the most direct, trivial method - but it is cumbersome when scaling/re-commissioning/experimenting (and there are more nodes coming).
The change itself facilitates a mechanism by which an absolutely-unique value (serial of a motherboard) is incorporated into the 36-char ‘hardware_uuid’, thus ensuring an always-unique value.
Most importantly, that change seemingly does not jeopardize the sanctity of what we perceive as a core operating tenet of MAAS: “this Machine entry in MAAS means something - it represents what MAAS knows to be true: that this entry is the ‘tracked’ machine, hardware make up and all”. This is the perceivable and tangible value of the UUID - a major step up from MAC address-only (which is implied to be one of the potential failover solutions when None’ing the ‘hardware_uuid’).
@ltrager - is there any chance, at all, that something like this change - an option, a toggle, something - could be incorporated into 2.9 prior to beta ending around Sept 25~ 2020?
Thank you for your time! We’re really liking MAAS!