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

support setting passive mode in bgp peer #886

Closed
wants to merge 1 commit into from

Conversation

dqminh
Copy link

@dqminh dqminh commented Jun 12, 2018

For projectcalico/calico#1603

This allow use to set passive: true in bgp peer spec so we can leverage that in calico/node to set proper bird config.

I think this should touches all the required place here. Then we would want to modify calico/node for confd config and calicoctl for updating new fields.

cc @caseydavenport

@CLAassistant
Copy link

CLAassistant commented Jun 12, 2018

CLA assistant check
All committers have signed the CLA.

@caseydavenport
Copy link
Member

@dqminh thanks for this pr!

I think there's a bit more to do here. Namely, update the model.BGPeer to include this field (this is what confd sees)

Is there a corresponding PR for the BIRD templates? It would be good to review them together since they rely on each other.

Also, looks like the bot would like you to sign the CLA :)

@caseydavenport caseydavenport self-assigned this Jun 13, 2018
@mattalberts mattalberts force-pushed the bgppeer-passive branch 2 times, most recently from 8ab8d05 to 188df4f Compare June 13, 2018 21:54
@mattalberts
Copy link

@caseydavenport I've gone ahead and updated the PR with a change to model.BGPPeer.

Would it be worth modifying api.BGPPeer as well to allow filling in the full model.BGPPeer struct?

As a potentially unrelated side-note, how does back-porting a change work? We'll be migrating to 2.6.x; I just want to make certain this change would land there as well.

@caseydavenport
Copy link
Member

As a potentially unrelated side-note, how does back-porting a change work? We'll be migrating to 2.6.x; I just want to make certain this change would land there as well.

So, we'll need to work through this one. Strictly speaking, this is an API change and so would require a minor bump rather than a patch release (e.g v2.7.0, or v3.2.0). I don't think we have any plans to cut a v2.7.0 release.

I'll need to discuss internally and get back to you, but in the absence of that I imagine this would land in v3.2.0.

@caseydavenport
Copy link
Member

Looks like the fomatting check is failing, proabably need to run goimports over the new code.

You'll also need to run make gen-files to update some autogenerated code.

This allow use to set `passive: true` in bgp peer spec so we can
leverage that in calico/node to set proper bird config.
@mattalberts
Copy link

@caseydavenport sorry about that! I've let go imports fix the formatting (shame shame shame). I've also re-run gen-files; though, that only netted a change to deepcopy (the import order).

@caseydavenport
Copy link
Member

This looks good to me.

Before we merge I'd like to be able to review it side-by-side with the corresponding confd template changes to make this work. Is there a PR for that as well?

@mattalberts
Copy link

There isn't one yet ... but ... I can make one! :)

@caseydavenport
Copy link
Member

Any update on this guy?

@caseydavenport
Copy link
Member

@mattalberts @dqminh this has gotten out of date and needs a rebase.

I'm going to close for now since there hasn't been any recent activity, but do ping me if you find time to work on this and we can reopen - I'd quite like to see it go in!

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

Successfully merging this pull request may close these issues.

4 participants