Ensure scheduler reconnects to the database if connection fails

Registered by Michael Hudson-Doyle on 2011-08-18

Partly so we can start the job via upstart (i.e. before we know the db is up) we need to change the scheduler to continually attempt to reconnect to the db if the connection fails.

Blueprint information

Status:
Complete
Approver:
Paul Larson
Priority:
Medium
Drafter:
Michael Hudson-Doyle
Direction:
Approved
Assignee:
Michael Hudson-Doyle
Definition:
Approved
Series goal:
Accepted for linaro-11.11
Implementation:
Implemented
Milestone target:
milestone icon 2011.09
Started by
Michael Hudson-Doyle on 2011-08-18
Completed by
Michael Hudson-Doyle on 2011-08-30

Related branches

Sprints

Whiteboard

Headline: The LAVA Scheduler can now start reliably using upstart when the system is booted.

Acceptance: Upstart job can automatically start the scheduler and the scheduler will try to connect to the db until it comes up, rather than fail if it races and tries to start before the database.

(?)

Work Items

Work items:
Make sure connection is reattempted if initial connection fails: DONE
Make sure connection is closed and reopened if connection drops: DONE
Change upstart job to start lava-scheduler on boot: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.