DB API / SQL Backend / Util files / Configs / Basic Celery

Sooo, long pull request - I apologize for not making it more incremental. ): But here's what we gots:

DB API: Database API set up for jobs/logbook/workflow/tasks calls



SQL Backend: Sql backend created. Here's the relations I've defined (let me know if any of this sounds wrong). 

Logbooks are defined by unique ids (uuids), and non-unique names. They have a one-to-many relationship with workflows, with the ability to have a repeated workflow (Maybe you want to run a create-instance workflow twice in this logbook).

Jobs have the same relations as logbooks (regarding workflows), but also include an owner and state field.

Workflows are defined by a unique name. They have a one-to-many relationship with tasks. One task can be re-used (calling a set_monitor task or whatever twice), but it will be defined as a unique task, since its' uuid will never be the same as another task. Workflows also have a many-to-may relationship for logbooks and jobs, although a workflow is not directly associated with any given job or logbook (they are independent entities)

Tasks are defined by a unique uuid. Pretty much a standard table right here, with a bi-directional many-to-one relationship with their associated workflow


UTIL FILES: Basic util files added (time stuff for timestamping database stuff, etc)


CONFIGS: Basic config set up for storing common data (backend settings, etc)

BASIC CELERY: First pass at a basic celery/distributed_flow implementation. Not quite ready to be used yet, but would still be nice to have the functionality in project for people to have some sort of reference to.



CAVEAT: All of this stuff has been hand tested, but does not have an associated test suite set up yet. As such, I'm totes cool with not pulling this in until we _do_ have some sort of test suite to solidify the functionality of the added stuffs. (:

Again, super sorry for the long request. D: