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.

Sign up for GitHub

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

Jump to bottom

Target identifier collision between streams #89

Closed
LionelJouin opened this issue Oct 13, 2021 · 1 comment
Closed

Target identifier collision between streams #89

LionelJouin opened this issue Oct 13, 2021 · 1 comment
Projects
Meridio

Comments

@LionelJouin
Copy link
Member

LionelJouin commented Oct 13, 2021 •
edited

Currently it is possible 2 targets open a stream (the streams have to be different for this to happen) with the same identifier which will create a conflict on the LB side since the IP rules/routes will collide.

3 solutions are possible:

  1. Have common identifier range with a unique identifier for each target
  • The number of identifier in use in equal to the number of target in the trench
  • Stream and target needs to be detached in the LB. The conduit configures the target rules/routes.
  1. Have common identifier range with a unique identifier for each stream opened
  • The number of identifier in use in equal to the number of stream opened in the trench
  1. Separated identifier ranges
  • Each stream should have a max size + offset
  • Needs extra parameters in the configmap and some work on the Operator to find available offset

related issue: #32
@LionelJouin LionelJouin added this to To do in Meridio via automation Oct 13, 2021
LionelJouin added a commit that referenced this issue Oct 19, 2021
@LionelJouin
Flow support
75a8148 
Vips replaced by flow in streams on the LB
2nd solution of #89 implemented
Target example:
- ctraffic updated to latest version
- 3 TCP instances (5000, 5001, 5002) and 2 UDP instances (5003, 5004)
@LionelJouin LionelJouin mentioned this issue Oct 19, 2021
Merged
LionelJouin added a commit that referenced this issue Nov 5, 2021
@LionelJouin
Flow support
e71b217 
Vips replaced by flow in streams on the LB
2nd solution of #89 implemented
Target example:
- ctraffic updated to latest version
- 3 TCP instances (5000, 5001, 5002) and 2 UDP instances (5003, 5004)
@LionelJouin LionelJouin moved this from To do to Done in Meridio Nov 15, 2021
@LionelJouin
Copy link
Member Author

Fixed in #91 using solution 2

@LionelJouin LionelJouin mentioned this issue Feb 18, 2022
Closed
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Meridio
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LionelJouin