Repository reorganization and port to gunicorn

This merge request significantly reorganizes the repository and sets it up to work with Gunicorn as a backend webserver behind an Apache reverse proxy. The new organization follows the recommendations from Two Scoops.

A summary of the changes is as follows:

• Created a new config directory which contains settings/, the wsgi script (renamed to wsgi.py from django.wsgi), and the main urls.py.
• Renamed the gracedb app to events
• Created a gracedb directory for housing all apps, templates, and static content
• Created a core app for collecting random utilities
• Moved both user and admin documentation to a docs/ directory
• Moved the API code to a subfolder of the events app
• Deleted all fixtures and rewrote unit tests to work without them
• Updated the authentication middleware to use the correct request headers which are used in place of Apache environment variables when Apache is configured as a reverse proxy.
• Deleted the copy of the VOEventLib library which was stored in this repository; now using the system package.
• Added a config script for running Gunicorn. Note that the actual Gunicorn process is started by systemd, which is part of the Puppet configuration update mentioned below.

There is a corresponding update to the Puppet configuration for the server which needs to be applied in concert, as well as one to the gracedb scripts repository.

This update is functional and has passed all server and client unit tests for a new database constructed from migrations. One thing which needs to be done is to define a procedure for implementing it in an already-existing database. The main concern is renaming the gracedb app to events. This will require changes to the database tables. This is currently being tested and a full procedure will be posted before.

More details about the move to Gunicorn are on the redmine page.

A few other notes:

• A lot of the changes are just files being moved. In most cases, git tracked it fine, but in a few, it thinks a brand new file was created.
• The old south_migrations directories are not needed anymore as far as I can tell. But I've kept them around just to be safe. I expect to delete them at a later date.

changed the description

added 1 commit

• 5ec469d2 - cleaning up commented out lines in permission unit tess

Compare with previous version

I developed a procedure for implementing this in-place:

1. Update scripts repository in /home/gracedb/bin.
2. Switch to the new branch.
3. Access the MariaDB command line
4. Rename all model tables for the app: RENAME TABLE gracedb_approval TO events_approval, gracedb_coincinspiralevent TO events_coincinspiralevent, gracedb_embbeventlog TO events_embbeventlog, gracedb_emfootprint TO events_emfootprint, gracedb_emgroup TO events_emgroup, gracedb_emobservation TO events_emobservation, gracedb_event TO events_event, gracedb_eventlog TO events_eventlog, gracedb_grbevent TO events_grbevent, gracedb_group TO events_group, gracedb_label TO events_label, gracedb_labelling TO events_labelling, gracedb_lalinferenceburstevent TO events_lalinferenceburstevent, gracedb_multiburstevent TO events_multiburstevent, gracedb_pipeline TO events_pipeline, gracedb_search TO events_search, gracedb_signoff TO events_signoff, gracedb_siminspiralevent TO events_siminspiralevent, gracedb_singleinspiral TO events_singleinspiral, gracedb_tag TO events_tag, gracedb_tag_eventlogs TO events_tag_eventlogs, gracedb_voevent TO events_voevent;
5. Update the app_label column in the django_content_type table: UPDATE django_content_type SET app_label='events' WHERE app_label='gracedb';
6. Rename migrations: UPDATE django_migrations SET app='events' WHERE app='gracedb';

This has been tested on gracedb-dev2. Afterwards, the server passed all of the client and server unit tests.

added 1 commit

• d7560f8d - fixing issue with SingleInspiral channels being truncated

Compare with previous version

added 2 commits

• f6c380f7 - adding bower.json for easy install of front-end dependencies
• 31937dde - simplifying and removing redundancies in static file deployment

Compare with previous version

added 1 commit

• a5436fe4 - updating robot cert for gstlal-spiir and fixing bug in old migrations

Compare with previous version

Hey Tanner:

Solid chunk of work here; sorry for not getting back formally sooner. Looks good to me; feel free to push to production at your convenience.

A side comment, I especially like the load testing on the redmine page (https://bugs.ligo.org/redmine/issues/6084). Not necessary now, but it would be interesting to derive a performance figure of merit from that (max requests/second? average requests/second?) and incorporate that into testing after server code upgrades, software updates, etc.

merged

mentioned in commit 80b7e021