Globally unique system ID

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

24.10 PR: https://github.com/truenas/middleware/pull/13443

As another note, I did discuss how I believe this should operate. I do believe that the “license” should have this globally unique ID and that the value be generated on the keyserver exclusively. However, that would require a significant amount of change and I believe that we should create license v2 and keyserver v2 before we even consider adding this to our existing infrastructure.

We’ve been wanting to write a new license/keyserver for many years at this point.

I spoke to Ben Canning about this and having this integrated into keyserver/std/sqlledger isn’t really necessary. He wants to have a globally unique ID that gets stored in the database (I discussed that this can easily be lost/altered/etc).

The scope of this epic should be changed to just basically:

1. add a new table in database (system_global_id)

2. generate and store a uuid.uuid4() value in that table on first install (or if one doesn’t exist (on upgrades))

3. add this value to the ixdiagnose output for SCALE as well as the freenas-debug output on CORE

If the above is accepted @William Gryzbowski , then I would say this is a “low” effort for the MW team. This would not require work from UI/Services/OS teams.