v1.4.1 - database fixtures to allow for easier model migrations - projects expiry, storage, etc.

[mjstealey]

v1.4.1 - database fixtures

v1.4.0 database tables

                   List of relations
 Schema |           Name            | Type  |  Owner
--------+---------------------------+-------+----------
 public | alembic_version           | table | postgres
 public | announcements             | table | postgres
 public | groups                    | table | postgres
 public | people                    | table | postgres
 public | people_email_addresses    | table | postgres
 public | people_organizations      | table | postgres
 public | people_roles              | table | postgres
 public | preferences               | table | postgres
 public | profiles_keywords         | table | postgres
 public | profiles_other_identities | table | postgres
 public | profiles_people           | table | postgres
 public | profiles_personal_pages   | table | postgres
 public | profiles_projects         | table | postgres
 public | profiles_references       | table | postgres
 public | projects                  | table | postgres
 public | projects_creators         | table | postgres
 public | projects_members          | table | postgres
 public | projects_owners           | table | postgres
 public | projects_tags             | table | postgres
 public | sshkeys                   | table | postgres
 public | testbed_info              | table | postgres
(21 rows)

Fixtures

• [x] db_export.py - version dependent full database export script - output as JSON fixture files
• [x] db_restore.py - version dependent full database restore script - input from JSON fixture files

Projects

• [x] storage information (ref: https://github.com/fabric-testbed/software-planning/issues/82) New issue #23