> It's easy enough to add disks.info.instance_name or disks.info.instance_uuid, but I think it's premature to add it now
Ok - but we do get the added benefit of not global locking needed with no real additional cost, plus if we put the file in instance dir. we get it cleaned automatically, and code wise - it's just changing how you get the path of the file all else can stay.
> I agree that get_set_driver_format is an ugly name, but could not think of a better one. Do you have a suggestion?
Maybe safe_get... that way we emphasize what was the reason for introducing it and make it less confusing?
> It's easy enough to add disks.info. instance_ name or disks.info. instance_ uuid, but I think it's premature to add it now
Ok - but we do get the added benefit of not global locking needed with no real additional cost, plus if we put the file in instance dir. we get it cleaned automatically, and code wise - it's just changing how you get the path of the file all else can stay.
> I agree that get_set_ driver_ format is an ugly name, but could not think of a better one. Do you have a suggestion?
Maybe safe_get... that way we emphasize what was the reason for introducing it and make it less confusing?