Comment 6 for bug 1740258

> The problem here is it's going to be a switchover with no warning when it happens.

I don't fully understand why it can't be a graceful switchover. I get that tempest is special and doesn't have the same stability guarantees as other projects but it seems like there could be a graceful way to say "Stop using this, do it this other way, and Pretty Soon you won't be allowed to do what you're doing."

> The deprecation was set to warn users that there is going to be a backwards incompatible change in the future on that option.

The warning is doing a terrible job of that. When I see a deprecation warning in the logs with no suggestion of what to replace the option with, I take it to mean the option isn't necessary any more and I can stop setting it. That's not the case here, it must be set. Maybe instead of using oslo.config's deprecation utility you could just emit a regular log saying "be prepared that this will change unexpectedly". Because if it's going to change in a backwards incompatible way, well that's not what deprecation is supposed to help with.

> At this point I'm wondering if we should just abandon the plans to make the img_file option the only one and just accept that img_dir is there forever.

I have no stake in this so I can't help with this :) I'm just hoping to clean up my logs, but if this really is a hard problem it's not killing me to see the warning.