PATCH claim not resetting age

[Amit Gandhi]

When PATCHing a claimed message with a new TTL, the age is not reset. The new TTL is expressed.

Expected Behavior: Age of the message should be reset to 0 when the message is PATCHed.

[Zhihao Yuan (zyuan)]

Currently the age always reflect the time lived regarding to the creation time (I think this is a better approach, although it's different from spec). Clean up only needs to compare the TTL and the current time, it's not an issue.

[Amit Gandhi (amit-gandhi)]

so if the TTL is currently 100, and i need to extend it by 50, must I set the TTL to 150 (existing 100, plus another 50) ???

If thats the case, then the spec needs to be updated to reflect that.

[Kurt Griffiths (kgriffs)]

Let's modify the mongo driver to be consistent with the spec and sqlite driver, per chat in IRC.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/41939

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/41939
Committed: http://github.com/stackforge/marconi/commit/055a43777b2f4d5bb78f1a9fea6f952ffb3087c7
Submitter: Jenkins
Branch: master

commit 055a43777b2f4d5bb78f1a9fea6f952ffb3087c7
Author: Flaper Fesp <email address hidden>
Date: Wed Aug 14 16:39:50 2013 +0200

    Don't use claim creation time to calc claim's age

    Mongodb's driver uses Claim's creation time to estimate claims age
    instead, it should use claim's update time. Since there's no update /
    creation time in mongodb's claims, the patch estimates claims age by
    doing:

        delta(expiration - ttl, now)

    This change fixes the issue bellow and makes mongodb's claims compliant
    with Marconi's specs.

    Change-Id: I72c968236ecd239e7b885b293238e2920807a57c
    Closes-Bug: #1210662