GUI for MLFlow and Git Integration

[markusabel]

Epic

We want a GUI that integrates MLflow and Git features.

Details

The expected features include:

Integration of

• User login
  • How complicated is
  • single sign-on (e.g. via Google, Facebook, Github, ...)?
  • roles from e.g. Github?
  • storage of secrets for access of external infrastructure (e.g. HPC, AWS)?
• mantik project:
  • project overview (README)
  • MLflow experiments and runs
  • code repos from which the experiments and runs originate
  • MLflow
  • MLflow tracking API access
  • MLflow UI access via GUI
  • Git
  • Display of the user's code repositories
  • Display of the commit (code repository) tracked in MLflow experiment run
  • Show project (MLflow and repo) according to user roles
  • public: everyone can see repo + MLflow UI
  • private: only certain users can see repo + MLflow UI
  • depending on roles, users can also manipulate repo + MLflow
  • Run on external infrastructure
  • HPC, cloud, ...
    • resources
  • MLflow project
    • entry point
    • parameters
  • Status
  • Settings
    • user priviliges

Acceptance

The GUI allows

• [ ] User login
• [ ] Access of MLflow data
  • [ ] Logged parameters, metrics, artifacts, models
  • [ ] Registered models
• [ ] Access of code repo
• [ ] Authenticated access
  • [ ] MLflow tracking API via tokens
  • [ ] MLflow UI features
  • [ ] Repo![MantikWires.drawio]

Wireframes Design Draft

[DanielWeidinger]

The Wireframe link at the bottom is dead.

[markusabel]

Ah, that is a problem, you do not have rights. Can you work with drawio? Then I will check it in the repo

[DanielWeidinger]

Sure, drawio should work!

[markusabel]

Passt?

[MirusVirus]

Daniel, Philipp, I think it would be great if you could, whenever you present a piece of work, attach some brief comments that manage our expectations and guide us in our reviewing. All in the light that we should - as we discussed last week - be aware of design decisions that are difficult to revert. E.g. "Elements X and Y are quick & rough but can easily be changed later; however element Z affects our templating quite deeply, so ideally we get it right today and won't need to change it later." Does this make sense? Cheers!

[MirusVirus]

@DanielWeidinger is there a way we can participate in what y'all are doing? A test page? Haferlgucken? We are aware that it's work in progress.

[DanielWeidinger]

I guess the Daily Meetings are a good place to keep in touch. Moreover, we could set up a "staging" environment for the front-end to preview the current status, but I'm not sure if it's worth the overhead when moving fast is a core requirement.

[markusabel]

We usually work with Pull requests and review apps. Here, we did not set them up, since I expected that pcode does that anyway.

We did not configure environments, I had understood that Daniel and Philipp use different environments, anyway.

We will discuss it in the dailies of this week, Thomas and Fabian will still be available. Next week, we are only front end pluscustomers, so please try to get the most out of the team now.

Of course, a pull request would be good.

[markusabel]

@all moving fast ist essential. But moving fast in the wrong direction is forbidden. Please show tomorrow an overview of what has been done.