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

Port numbers in servers.yaml #22

Open
OrlandoST opened this issue Dec 8, 2021 · 1 comment
Open

Port numbers in servers.yaml #22

OrlandoST opened this issue Dec 8, 2021 · 1 comment

Comments

@OrlandoST
Copy link

Meybe it will be better to add port numbers to servers.yaml and not set its each time in command line, when we launch 5g-trace-vizualizer???

@jkolom
Copy link
Collaborator

jkolom commented Jan 5, 2022

Feel free to extending the syntax of servers.yaml with additional optional parameters.

However, a couple of things regarding servers.yaml:

  • The (historical) reason it was created was that for some setups (e.g. mixture of emulated and real NFs), mixtures of k8s and VMs were used. What I got from our colleagues was a VM list in the format of servers.yaml.
  • The data in servers.yaml is currently used to map and group messages to "actors" for diagram generation
  • The port filtering is applied at the tshark stage to avoid generating huge PDML files (e.g. in the case user plane is present in a capture, the PDML file could be enormous)

It is however a bit "cumbersome" to have all the parameters in the command line. So a YAML-based config parameter input sounds definitely like an improvement in readability :)

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

No branches or pull requests

2 participants