[openstack-dev] [cinder][replication-api] replication_rpo_range - why two values?
Philipp Marek
philipp.marek at linbit.com
Fri Jul 11 13:12:10 UTC 2014
"replication_rpo_range" currently gets set with two values - a lower and an
upper bound. File cinder/scheduler/filter_scheduler.py:118 has
if target_rpo < rpo_range[0] or target_rpo > rpo_range[1]:
Why do we check for "target_rpo > rpo_range[1]"?
"Don't use that one if replication is too fast?" Because we'd like to
revert to an older state?
I believe that using snapshots would be more sane for that use case.
Or I just don't understand the reason, which is very likely, too.
--
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com :
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
More information about the OpenStack-dev
mailing list