On Mon, Sep 29, 2014 at 11:47 PM, Dmitry Mescheryakov < dmescherya...@mirantis.com> wrote:
> As a result of operation #1 the token will be saved into Swift by the > Keystone. But due to eventual consistency it could happen that validation > of token in operation #2 will not see the saved token. Probability depends > on time gap between ops #1 and #2: the smaller the gap, the higher is > probability (less time to sync). Also it depends on Swift installation > size: the bigger is installation, the higher is probability (bigger 'space' > for inconsistency). eventual consistency will only affect container listing and I don't think there is a need for container listing in that driver. Chmouel
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
