Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define the scenario interface #62

Open
josephburnett opened this issue May 19, 2020 · 2 comments
Open

Define the scenario interface #62

josephburnett opened this issue May 19, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@josephburnett
Copy link
Contributor

Currently various traffic patterns are defined as a golang object that the UI and core simulator both know about. And the same for the metrics returned to the UI. This should be defined as a protobuf similar to #58 so that the UI can be more decoupled from the core. This will allow command line / library usage of Skenario core in addition to the UI.

The proto should include an enumerated set of patterns. But also allow for raw data input (e.g. qps over time).

@jchesterpivotal
Copy link
Contributor

Is the idea that traffic patterns will live in a separate process communicating with the simulator core?

@josephburnett josephburnett self-assigned this May 20, 2020
@josephburnett
Copy link
Contributor Author

No, I just want to have clearly defined traffic shape which the simulator will implement. So the UI can be decoupled from the simulator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants