service_manage_cleanup has some problem

[XueFeng Liu]

senlin-engine is designed can run multiple instances.
So we have a senlin-engine service database table to record how many instances are running now.
Each running senlin-engine periodically report its service status.

But it only check and cleanup when each senlin-engine start, this has some problem.
For example:
senlin-engine restart seveal times in chelanup time_windows and then run ok.This will cause some service record can't
be cleanup.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/371922
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=cff25621705d868602a768336f11e284b3732a4b
Submitter: Jenkins
Branch: master

commit cff25621705d868602a768336f11e284b3732a4b
Author: jonnary <email address hidden>
Date: Sat Sep 24 10:31:43 2016 +0800

    Fix service manage cleanup

    Make service cleanup can be called when engine start time greater than
    cleanup time_windos.

    Closes-Bug:1624670

    Change-Id: Ibe4a2c0a66d2d6c1bbd532fc68373282bf761280

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/senlin 2.0.0.0rc2 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/senlin 2.0.0 release.