So up until this point OpenStack has been a pretty much a rip and
replace model. You want to go from Diablo to Essex, shut everything
down, upgrade, bring back up. When I went to change this parameter
originally, the review comments included just ripping out the old
function, and not deprecating it.
But I think we are moving into a phase where real OpenStack deployments
are going to have N and N+1 release componets talking to each other. so
it's probably worth getting in the habbit of having a standard way to
deprecate out over a release. LOG.warning messages scattered about,
which may or may not be consistent, that someone might or might not
remember to remove later, with or without their associated function,
seems kind of error prone.
Logging sounds like a great way to communicate to deployers and operators,
but really doesn't seem the best way to communicate with developers. So
my question is, are we using this mechanism to deprecate things the deployers
can control? Or is it things that developers need to deal with? If its the
latter (which it seems), I'd prefer that we just use our various developer
coordinating communication channels, such as the team meetings, IRC, mailing
list, etc.
