GraphQL support

[kerthcet]

What would you like to be added:

Add a graphql server as the webserver between the dashboard and the backend. Then the dashboard can fetch what it wants to build the dashboard.

Why is this needed:

The initial step to build the dashboard.

Completion requirements:

Do you prefer the restful api or graphql server? @dalphyx

This feature requires the following artifacts:

• Design doc
• API change
• Docs update

The artifacts should be linked in subsequent comments.

[kerthcet]

/kind feature
/milestone v0.1.0

[wanyingz-dis]

Feel free to assign this to me.

[kerthcet]

/assign @wanyingz-dis

[kerthcet]

Any progress on this @wanyingz-dis ?

[wanyingz-dis]

Hi @kerthcet
I’ve seeded the database locally and was reviewing the data structure (experiments → trials → runs → metrics). I was also learning a bit about GraphQL yesterday.

I am starting writing the design doc, could I confirm one thing:
For the first version, is it enough to expose read-only graphql queries for the dashboard (e.g. list experiments, list trials, list runs, and their metrics)? Or do we also want mutations for creating experiments/trials?

I’m planning to implement this using FastAPI + Strawberry GraphQL, please let me know if there’s a preferred alternative.

Thanks!

[kerthcet]

Let's start with ready only queries, then we can keep iterating.

I'm fine with the approach FastAPI + Strawberry GraphQL.