Simulator Scenario SchedulingSimulation supports in Web UI

[196Ikuchil]

Problem

In #140, #159, and #184, our simulator would be big changes.
But the current frontend is not suited for the new features.

Possible Issues

I think that we need to decide on two broad problems, at least.

• Result view
  • We must implement a new view to see some scenario results.
  • The data provide from new features are completely different from the current.
• Method to choose the simulator, URL, or port
  • The data provided by new features allow us to run multiple simulators.
  • Current frontend can only display data on one URL (simulator)

So, looking for good ideas!
We should have a little discussion before creating some frontend's KEP.

[196Ikuchil]

/kind feature

[sanposhiho]

left my random ideas here:

• Implement 'tabs' like the browser and 'tabs' allows users to switch simulator which the Web UI connects to.
• Implement '+' button besides the tabs and users can create new simulator with '+' button.
• support 'scenario' and implement a 'go next step' button so that users can see what happens on a simulator step by step.
  • By storing a history of resources state transitions in the browsers, it may also be possible to implement rollback to past steps on Scenario. That would be amazing feature....

[sanposhiho]

/retitle Simulator Scenario SchedulingSimulation supports in Web UI

[sanposhiho]

/triage accepted
/priority important-longterm

[196Ikuchil]

+1: Nice idea!
At least, it would be useful for users to have a UI that resembles a web browser.

[sanposhiho]

/area web

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sanposhiho]

/remove-lifecycle rotten
/lifecycle frozen

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted