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
bgpv1: pass router state to gobgp #26194
bgpv1: pass router state to gobgp #26194
Conversation
abf4590
to
e6e40b2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes look fine to me.
Just have to remember not to hold onto a ControlPlaneState, as that data is always pushed down on reconcile.
I say this just because the constructor almost looks like its getting ready to hold onto the state, but the intention is just to use it as flags for construction purposes right? I.e. the ControlPlaneState shouldn't be referenced after initial BGP Speaker initialization, cuz it may contain stale data.
@ldelossa Yes, the idea is only to use it in the constructor and not hold on to it. |
/test |
Not a new feature, should be eligible for merge. cc @ldelossa |
@harsimran-pabla theres two stuck tests here, can you rebase and push? |
e6e40b2
to
d91fbaf
Compare
/test |
d91fbaf
to
69a4492
Compare
/test |
Pass CiliumBGPVirtualRouter in NeighborRequest and cstate while initializing gobgp server. These changes are done to pass extra context to gobgp. Signed-off-by: harsimran pabla <hpabla@isovalent.com>
types.NeighborRequest contains additional information which can be used to create Peer request. Signed-off-by: harsimran pabla <hpabla@isovalent.com>
69a4492
to
b29d036
Compare
@harsimran-pabla @ldelossa Please rebase against the latest |
/test |
This change passes additional context regarding the control plane state to GoBGP.