> > I'm not talking about all configuration options. I'm talking about this > single configuration option. Existing installations that did not > specify rpc_backend because they did not need to will break if the > default is changed. > They would only break in Grizzly, following a one-release depreciation schedule. During Folsom, if they run Folsom, they'll only get warnings. When it becomes required, if they haven't yet updated their configuration, and if they don't see it clearly stated in release-notes, they'll discover the change quickly within their testing.
If they ignore the warnings in Folsom, don't notice the release-notes, and don't do any testing before deploying; If they don't test Grizzly, deploy into production, and run into this… well, I hope they're a small deployment, in which case it won't be a very big thorn. If they're a large deployment and they ignore all of this, including ignoring any need for testing before doing a large rollout… Regards, Eric Windisch _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
