OTG Model to support different RoCE speed#400
Open
alakendu wants to merge 23 commits into
Open
Conversation
…rator/models into speed_proposal
…rator/models into speed_proposal
…rator/models into speed_proposal
…rator/models into speed_proposal
…rator/models into speed_proposal
…rator/models into speed_proposal
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem Statement:
We have one OTG based solution call
snappi_ixnetworkwhich is a client-side solution. So, entire conversion ( OTG to IxNetwork REST API) is happening in the client side and communicate with IxNetwork Server through REST API (RestPy library).As this is a client-side solution, so we can access IxNetwork API handle from test and configure others IxNetwork parameters.
We are configuring RoCE using RestPy though OTG model is not support that protocol. But we need to change the speed with specific format ( say
fourhundredgigrocev2) which is not support to our current OTG model.We have these two solutions:
redoc : https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/open-traffic-generator/models/speed_proposal/artifacts/openapi.yaml&nocors#tag/Configuration/operation/set_config
Solution-1:
Note: Little annoying as “speed” is not a choice, so directly setting as
custom_speedmay be debatable.Solution-2:
This solution is not specific to speed. We will utilize it for generic purpose. This is like open config deviations. I have added more options to handle different use cases.
In this following example we are saying that OTG application should additionally handle
rocev2feature and deviateisis-srfunctionality defined in OTG.