mlos_webui design requirements

[bpkroth]

trafficstars

For starters, mlos_webui seems an appropriate moniker to me. It should support

1. [ ] Visualization of ExperimentData from a shared Storage location.
2. [ ] Execution of existing mlos_bench configs it has access to. (e.g., via SP access to a git repo).
   • [ ] We should allow it to be parallelized across Experiments via GridSearch (e.g., to schedule different instances of a tuning Experiment across different scenarios, like storage types or VM sizes, or benchmark type).
   • [ ] Error logs should be visible.
   • [ ] Experiments should be resumable.
3. [ ] Editing of such configs. (with versioning)

• [ ] Authentication should be required.
• [ ] Fine grained authorization (e.g., restricting access to experiments by group or some such) is out of scope for now (i.e., if you can authenticate, you can perform any action).
• [ ] Code should be modular enough to allow easily adding features (e.g., new visualizations).

Originally posted by @bpkroth in https://github.com/microsoft/MLOS/pull/824#discussion_r1714331354