Revised OTA frequency admission control
Currently we require that users have an approved frequency reservation before they are allowed to instantiate an experiment that uses this spectrum. This has resulted in an awkward and delay-prone human-in-the-loop workflow for outdoor wireless experiments.
We have decided to change to the following strategy for RF frequency admission control:
- Do away with "Emulab features" for specific ranges
- Maintain a list of admin-set ranges allowed for a given project
- Free-form, not required to be from a predefined set
- Have an admin interface for setting these ranges
- Provide a set of predefined ranges to auto-populate for convenience (e.g., the Sprint spectrum)
- Have a "global" list for ranges allowed by anyone
- Do not require frequency reservations anymore
- Users can still make reservations to guarantee future availability
- Keep a history of frequency range use
- A
frequency_history
table is suggested
- A