Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Appliance UUID persistent #1348

Closed
schakrava opened this Issue Jun 14, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@schakrava
Copy link
Member

schakrava commented Jun 14, 2016

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.

@schakrava schakrava added this to the Looney Bean milestone Jun 14, 2016

@schakrava schakrava self-assigned this Jun 14, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Jun 14, 2016

@williamstlr

This comment has been minimized.

Copy link

williamstlr commented Jun 14, 2016

I'm just curious to see if you know, but run my Rockstor appliances as virtual machines, how would using the product_uuid work in that case with Rockstor? Looking at the values of two VM's on the same hypervisor (ESXi) I get two different UUID's.

schakrava added a commit to schakrava/rockstor-core that referenced this issue Jun 14, 2016

@schakrava schakrava closed this in 6aab59d Jun 14, 2016

@schakrava

This comment has been minimized.

Copy link
Member Author

schakrava commented Jun 14, 2016

I verified that in case of Virtualbox and KVM they are unique. Glad to get your confirmation that it's the case on ESXi as well. Not sure if I understand your question correctly, but the expectation is that 2 VMs on the same hypervisor each get a UUID.

@williamstlr

This comment has been minimized.

Copy link

williamstlr commented Jun 17, 2016

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.