First rest thread issue13

[ellerychan]

This Pull Request address Issue #13.

The original intent of this issue was to lay down an initial foundation infrastructure for the REST interface, and to determine whether Django was able to provide the needed functionality. The development has exceeded the initial scope of the issue. In doing so, it delivers a full set of features that provide a fully-functional very basic level of Master Server operation.

It delivers the following functionality:

• Modifies and extends the initial database design
• Implements a REST-style interface to handle BRATA, Station, and Ajax message transactions. The following message transactions are implemented (in piservice/views.py):
  • BRATA Register
  • BRATA Unregister
  • BRATA At Waypoint
  • BRATA Start Challenge
  • BRATA Submit
  • Station Join
  • Station Leave
  • Ajax StationStatus
  • BRATA Register (2015 version)
  • BRATA At Waypoint (2015 version)
  • BRATA Start Challenge (2015 version)
  • BRATA Submit (2015 version)
• Implements a web page and form-based HTTP interface for MS administration and user-facing interaction. The following transactions are implemented (in dbkeeper/views.py):
  • Add Organization
  • Add User
  • Add Team
  • Check In Team
• Implements a rudimentary Station Status browser-based (web page) display dynamically refreshed using Ajax. This also serves as a prototype proof-of-concept for the LeaderBoard.
• Implements a TeamCode generator, that makes user-friendly unique codes like Zulu Tango Vanilla (ZT02)
• Enhances the admin interface
• Adds a Settings table to the database to handle configuration settings
• Delivers some updated design docs and diagrams

[ellerychan]

Met with @jaron42 and @jawaad-ahmad about the current state of development represented by this Pull Request. I got some good feedback:

• Add an Unregister message
• Remove pi_type from the Join message (not useful)
• Change station_type to a string, for readability
• The station will send a unique ID (the Pi processor serial #) in its Join message (discussed in this comment in #13)
• Add a Heartbeat message (that the stations will send to the MS)

We also discussed the team registration process and the BRATA registration process, and other aspects of authentication that will still need some resolution.

[ellerychan]

I have incorporated feedback from our recent meeting. I have implemented the 2015 message formats side-by-side with the newer format that we cooked up. I would like to merge this Pull Request into hsdc2016 so that @jaron42 can put up his test server and we can start getting some feedback.

Any objections @jawaad-ahmad, @DragonmasterJ, @jaron42?