Moderne OnlyThis recipe is proprietary to Moderne and runs on the Moderne platform or CLI — it isn’t part of the open-source catalog. Available with a Moderne subscription.Contact Sales

Find what blocks a Das Schiff BGPPeering from moving to the Sylva network connector API

Recipe IDio.moderne.kubernetes.sylva.migrate.dasschiff.FindBgpPeeringMigrationBlockers

Artifactorg.openrewrite.recipe:rewrite-kubernetes

Report what a human has to decide before a Das Schiff BGPPeering can move to the network-connector.sylvaproject.org group. Nothing is rewritten: the legacy spec.export is a reject-by-default prefix filter and the intent one is accept-by-default BGP communities, so a peering moved as it stands would advertise the whole VRF table.

Single recipeOpenRewriteModerne Proprietary License

Try in PlatformTry this recipe in the Moderne platform. Not a user yet? You’ll get a no-setup demo environment, with nothing to install or configure.

Options

1 parameters

1 optional

Parameter	Example	Type	Required
fileMatcher	**/bgp-*.yml	String	Optional
Matching files will be searched. This is a glob expression.

Examples

yaml

Parameter	Value
fileMatcher	null

yaml

Before

apiVersion: network-connector.sylvaproject.org/v1alpha1
kind: Network
metadata:
  name: net-bgp-clients
  namespace: default
spec:
  ipv4:
    cidr: 10.250.3.0/24
---
apiVersion: network-connector.sylvaproject.org/v1alpha1
kind: Layer2Attachment
metadata:
  name: gw-vlan-m2m
  namespace: default
spec:
  networkRef: "gw-vlan-m2m"
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: BGPPeering
metadata:
  name: m2m-clients
spec:
  peeringVlan:
    name: gw-vlan-m2m
  remoteASN: 65100
  enableBFD: true
  holdTime: 9s
  keepaliveTime: 3s
  maximumPrefixes: 100
  import:
    - action: permit
      cidr: 10.250.3.0/24
      le: 32
  export: []
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: VRFRouteConfiguration
metadata:
  name: m2m-gw-vrf
spec:
  vrf: m2m

After

apiVersion: network-connector.sylvaproject.org/v1alpha1
kind: Network
metadata:
  name: net-bgp-clients
  namespace: default
spec:
  ipv4:
    cidr: 10.250.3.0/24
---
apiVersion: network-connector.sylvaproject.org/v1alpha1
kind: Layer2Attachment
metadata:
  name: gw-vlan-m2m
  namespace: default
spec:
  networkRef: "gw-vlan-m2m"
---
apiVersion: network.t-caas.telekom.com/v1alpha1
~~(sets an empty `spec.export`, and the legacy export filter defaults to reject, so this peer is told nothing at all. The intent group has no export filter: its `listenRange` peer is built with a default action of accept, so it tells the peer the whole VRF table, and its `spec.export` is a set of BGP communities tagging the prefixes it re-exports into the EVPN fabric rather than a filter on what the peer hears. What this peer is told therefore has to be decided again rather than carried across, and moving this peering as it stands would turn advertising nothing into advertising the whole VRF table)~~>kind: BGPPeering
metadata:
  name: m2m-clients
spec:
  peeringVlan:
    name: gw-vlan-m2m
  remoteASN: 65100
  enableBFD: true
  holdTime: 9s
  keepaliveTime: 3s
  maximumPrefixes: 100
  import:
    - action: permit
      cidr: 10.250.3.0/24
      le: 32
  export: []
---
apiVersion: network.t-caas.telekom.com/v1alpha1
kind: VRFRouteConfiguration
metadata:
  name: m2m-gw-vrf
spec:
  vrf: m2m

Diff

@@ -19,1 +19,1 @@
---
apiVersion: network.t-caas.telekom.com/v1alpha1
-kind: BGPPeering
+~~(sets an empty `spec.export`, and the legacy export filter defaults to reject, so this peer is told nothing at all. The intent group has no export filter: its `listenRange` peer is built with a default action of accept, so it tells the peer the whole VRF table, and its `spec.export` is a set of BGP communities tagging the prefixes it re-exports into the EVPN fabric rather than a filter on what the peer hears. What this peer is told therefore has to be decided again rather than carried across, and moving this peering as it stands would turn advertising nothing into advertising the whole VRF table)~~>kind: BGPPeering
metadata:

Usage

Run this recipe

This recipe has no required configuration options. Users of Moderne can run it via the Moderne CLI.

You will need to have configured the Moderne CLI on your machine before you can run the following command.

shell

mod run . --recipe FindBgpPeeringMigrationBlockers

If the recipe is not available locally, then you can install it using:

RELEASE resolves to the newest release and LATEST to the newest build of any kind, including snapshots. Either one lets mod config recipes upgrade pull in later versions without editing this command; a pinned version stays where you put it.

RELEASE

mod config recipes jar install org.openrewrite.recipe:rewrite-kubernetes:RELEASE

LATEST

mod config recipes jar install org.openrewrite.recipe:rewrite-kubernetes:LATEST

Pinned version

mod config recipes jar install org.openrewrite.recipe:rewrite-kubernetes:3.18.0

Data tables

BGP peerings

io.moderne.kubernetes.sylva.migrate.dasschiff.table.BgpPeerings

Deutsche Telekom network.t-caas.telekom.com BGPPeering resources, and what each one needs decided before it can be written against the network-connector.sylvaproject.org BGPPeering that shares its name.

Column	Description
Source path	The path to the manifest.
Name	The metadata.name of the legacy resource.
Mode	The intent spec.mode this peering maps onto: listenRange when it sets spec.peeringVlan, loopbackPeer when it sets spec.loopbackPeer, empty when neither is readable.
Blocker	What has to be decided before this peering can be written against the intent group. Checks run narrowest first, so a peering reported against spec.export is one whose every other field and reference already resolves.

Source files that had results

org.openrewrite.table.SourcesFileResults

Source files that were modified by the recipe run.

Column	Description
Source path before the run	The source path of the file before the run. null when a source file was created during the run.
Source path after the run	A recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Parent of the recipe that made changes	In a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all.
Recipe that made changes	The specific recipe that made a change.
Estimated time saving	An estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds.
Cycle	The recipe cycle in which the change was made.

Source files that had search results

org.openrewrite.table.SearchResults

Search results that were found during the recipe run.

Column	Description
Source path of search result before the run	The source path of the file with the search result markers present.
Source path of search result after run the run	A recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Result	The trimmed printed tree of the LST element that the marker is attached to.
Description	The content of the description of the marker.
Recipe that added the search marker	The specific recipe that added the Search marker.

Source files that errored on a recipe

org.openrewrite.table.SourcesFileErrors

The details of all errors produced by a recipe run.

Column	Description
Source path	The file that failed to parse.
Recipe that made changes	The specific recipe that made a change.
Stack trace	The stack trace of the failure.

Recipe performance

org.openrewrite.table.RecipeRunStats

Statistics used in analyzing the performance of recipes.

Column	Description
The recipe	The recipe whose stats are being measured both individually and cumulatively.
Source file count	The number of source files the recipe ran over.
Source file changed count	The number of source files which were changed in the recipe run. Includes files created, deleted, and edited.
Cumulative scanning time (ns)	The total time spent across the scanning phase of this recipe.
Max scanning time (ns)	The max time scanning any one source file.
Cumulative edit time (ns)	The total time spent across the editing phase of this recipe.
Max edit time (ns)	The max time editing any one source file.