Changing the nova table is not an option I guess. Nova takes care about them including upgrades and so on. Having a new column there might break upgrades for nova on systems where our code is installed.
The only option would be adding a new table that we maintain. But then we are responsible for doing upgrades...
I feel that the "OS-EXT-SRV-ATTR:instance_name" of Novas extended_server_attributes extension is the right place to store this information. Maybe there is also some other field
Alternatively we could check if we can reuse some other field of the DPM partition object (or request a new one that we could use)....
Changing the nova table is not an option I guess. Nova takes care about them including upgrades and so on. Having a new column there might break upgrades for nova on systems where our code is installed.
The only option would be adding a new table that we maintain. But then we are responsible for doing upgrades...
I feel that the "OS-EXT- SRV-ATTR: instance_ name" of Novas extended_ server_ attributes extension is the right place to store this information. Maybe there is also some other field
Alternatively we could check if we can reuse some other field of the DPM partition object (or request a new one that we could use)....