Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Make Appliance UUID persistent #1348
Currently, appliance UUID is dynamically generated during setup time using a combination of hostid and uuid generated by python's uuid library. Because it's generated purely by Rockstor code during setup time, it's not persistent across reinstalls.
If we make the uuid persistent, by using a hardware generated one, it would eliminate the pain of having to generate a new stable subscription activation code every time Rockstor is installed on the same hardware. Luckily, someone in the community told us exactly how to get this uuid from /sys/class/dmi/id/product_uuid.
Sorry, I didn't explain that too well there. If I end up rebuilding my Rockstor appliance on a VM, say I end up deleting the old VM to rebuild, how will activation by UUID work there? I guess ideally you would keep the same VM, wipe the VHDs or add new ones, but if a VM is deleted and a new one is created it will have a new UUID, how would activation be handled in that case?