bgp_dt05 , iBGP for EDPM nodes - #782
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mtomaska The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
c7e6a50 to
aa60ef7
Compare
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
3c095b4 to
2f61c51
Compare
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
mtomaska
changed the title
| edpm_sshd_allowed_ranges: | ||
| - 192.168.122.0/24 | ||
| edpm_sshd_configure_firewall: true | ||
| # TODO: Revisit why FQDN is not getting set, it is needed to support |
There was a problem hiding this comment.
I need to address this before merging this
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
edpm nodes utilize iBGP AS 65000 Related: OSPRH-32310 Assisted-By: Claude Code Signed-off-by: Miro Tomaska <mtomaska@redhat.com>
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
|
recheck |
There was a problem hiding this comment.
I was able to build all of the CRs except 01_nncp.yaml which failed with:
unable to find field "spec.desiredState.interfaces.0.ipv4.address.0.ip" in replacement target
Thus, I'm requesting that be updated.
Here are the CRs from the build:
[johfulto@laptop CRs{bgp_dt05}]$ wc -l *
478 02_networking.yaml
609 03_control-plane.yaml
214 04_edpm-r0-compute-nodeset.yaml
214 05_edpm-r1-compute-nodeset.yaml
214 06_edpm-r2-compute-nodeset.yaml
204 07_edpm-r0-networker-nodeset.yaml
204 08_edpm-r1-networker-nodeset.yaml
204 09_edpm-r2-networker-nodeset.yaml
13 10_edpm-deployment.yaml
2354 total
[johfulto@laptop CRs{bgp_dt05}]$
Here is a diff of the output of bgp_dt01 compared to the output of bgp_dt05
https://gist.github.com/fultonj/a789ba08cf1a8387240496cb0bef3aba
| fieldPaths: | ||
| - spec.desiredState.routes | ||
|
|
||
| # internalapi bridge gateway IP and prefix-length |
There was a problem hiding this comment.
I think you can remove those 4 replacement blocks (lines 576–616).
After I remove them, I am then able to run kustomize build . in bgp_dt05/control-plane/networking/nncp.
| - destination: 192.168.122.0/24 | ||
| nexthop: 192.168.123.1 | ||
| - destination: 192.168.124.0/24 | ||
| nexthop: 192.168.123.1ØØ |
There was a problem hiding this comment.
Non-ASCII characters (ØØ) in IP address. Should be 192.168.123.1
| src_file: service-values.yaml | ||
| build_output: control-plane.yaml | ||
| post_stage_run: | ||
| - name: Create BGPConfiguration after controplane is deployed |
There was a problem hiding this comment.
"controplane" → "controlplane" (missing l).
| vars: | ||
| cifmw_architecture_scenario: bgp_dt04_ipv6 | ||
| - job: | ||
| files: |
There was a problem hiding this comment.
Looks like examples/dt/bgp_dt05/metallb is missing.
|
This PR directly copies a lot of files from A similar thing is going on in a new PR for bgp_dt02 I asked an LLM to refactor 01, 02, and 05 by sharing a common directory for bgp. Links to refactored code and analysis are available in this gist. Thoughts? https://gist.github.com/fultonj/bf885c3b065988854b1b7da6eeb0a523 |
2 participants
A new bgp_dt05 example based on bgp_dt01. In this deployment all leafs and edpm nodes are on the same ASN. The number of nodes has not changed from bgp_dt01.
The control plane is using BGP to advertise control plane IPs. This topology will be used for testing BGP EVPN advertising where dataplane traffic will establish VXLAN tunnels for dataplane traffic
Depends-On: openstack-k8s-operators/ci-framework#4055
Related: OSPRH-32310
Assisted-By: Claude Code