Rn 0.61.0 (srl-labs#2377)

* format

* added rn 0.61

Author: hellt

clab/config_test.go

@@ -770,7 +770,8 @@ func TestStartupConfigInit(t *testing.T) {
 
 			cwd, _ := os.Getwd()
 			if c.Nodes[tc.node].Config().StartupConfig != filepath.Join(cwd, tc.want) {
-				t.Errorf("want startup-config %q got startup-config %q", filepath.Join(cwd, tc.want), c.Nodes[tc.node].Config().StartupConfig)
+				t.Errorf("want startup-config %q got startup-config %q",
+					filepath.Join(cwd, tc.want), c.Nodes[tc.node].Config().StartupConfig)
 			}
 		})
 	}

cmd/destroy.go

@@ -70,7 +70,8 @@ func destroyFn(_ *cobra.Command, _ []string) error {
 			return nil
 		}
 
-		topos[cnts[0].Labels[labels.TopoFile]] = filepath.Dir(cnts[0].Labels[labels.NodeLabDir])
+		topos[cnts[0].Labels[labels.TopoFile]] =
+			filepath.Dir(cnts[0].Labels[labels.NodeLabDir])
 
 	case all:
 		containers, err := listContainers(ctx, topo)

docs/manual/kinds/srl.md

@@ -351,7 +351,7 @@ Nokia SR Linux nodes support setting of [SANs](../nodes.md#subject-alternative-n
 
 Starting with SR Linux 24.3.1, the gRPC server config block is used to configure gRPC-based services such as gNMI, gNOI, gRIBI and P4RT. The factory configuration includes the `mgmt` gRPC server block to which containerlab adds all those services and:
 
-* generated TLS profile
+* generated TLS profile - `clab-profile`
 * unix-socket access for gRPC services
 * increased rate limit
 * trace options
@@ -360,6 +360,14 @@ These additions are meant to make all gRPC services available to the user out of
 
 Besides augmenting the factory-provided `mgmt` gRPC server block, containerlab also adds a new `insecure-mgmt` gRPC server that provides the same services as the `mgmt` server but without TLS. This server runs on port 57401 and is meant to be used for testing purposes as well as for local gNMI clients running as part of the NDK apps or local Event Handler scripts.
 
+#### EDA support
+
+To ensure that Containerlab-provisioned SR Linux nodes can be managed by Nokia EDA a set of gRPC servers is added:
+
+* `eda-discovery` - provides support for EDA discovery
+* `eda-mgmt` - gRPC server that references `EDA` TLS security profile that EDA setups with gNSI
+* `eda-insecure-mgmt` - insecure version of the `eda-mgmt` gRPC server
+
 ### SSH Keys
 
 Containerlab will read the public keys found in `~/.ssh` directory of a sudo user as well as the contents of a `~/.ssh/authorized_keys` file if it exists[^4]. The public keys will be added to the startup configuration for `admin` and `linuxadmin` users to enable passwordless access.

docs/manual/nodes.md

@@ -177,7 +177,7 @@ Check the particular kind documentation to see if the startup-config is supporte
           startup-config: cfgs/__clabNodeName__.partial.cfg
     ```
 
-    The `__clabNodeName__` variable can also be used in the kind and default sections of the config.  Using the same directory structure from the example above, the following shows how to use the magic varable for a kind.
+    The `__clabNodeName__` variable can also be used in the kind and default sections of the config.  Using the same directory structure from the example above, the following shows how to use the magic variable for a kind.
 
     ```yaml
     name: mylab
@@ -203,11 +203,11 @@ Check the particular kind documentation to see if the startup-config is supporte
       nodes:
         node1:
         node2:
-    ``` 
+    ```
 
 #### embedded startup-config
 
-It is possible to embed the startup configuraion in the topology file itself. This is done by providing the startup-config as a multiline string.
+It is possible to embed the startup configuration in the topology file itself. This is done by providing the startup-config as a multiline string.
 
 ```yaml
 topology:
@@ -418,7 +418,7 @@ If you use an http(s) proxy on your host, you typically set the `NO_PROXY` envir
 
 Containerlab automates this process by automatically setting `NO_PROXY`/`no_proxy` environment variables in the containerlab nodes with the values of:
 
-1. localhost,127.0.0.1,::1,*.local
+1. `localhost,127.0.0.1,::1,*.local`
 2. management network range for v4 and v6 (e.g. `172.20.20.0/24`)
 3. IPv4/IPv6 management addresses of the nodes of the lab
 4. node names as stated in your topology file

docs/rn/0.61.md

@@ -0,0 +1,45 @@
+# Release 0.61
+
+:material-calendar: 2025-01-03 · :material-list-status: [Full Changelog](https://github.com/srl-labs/containerlab/releases)
+
+## No manual `NO_PROXY`
+
+Proxies are a pain that every corporate network user has to find a way painkiller for. What makes it even worse is that when adding a proxy to your environment, you have to add a `NO_PROXY` env var for local addresses that you want to reach without a proxy.  
+Add to the mix the fact that the industry still can't agree if `NO_PROXY` or `no_proxy` env var name should be used so we have to deal with both.
+
+If you lab topology has nodes that use HTTP to communicate with other nodes of the lab you have to set up a NO_PROXY/no_proxy env var and exclude every single node IP and DNS name of the topology nodes. You can imagine what a time killer this is.
+
+Thanks to @toweber and his work in #2351, Containerlab will automatically inject the NO_PROXY env vars to each node in the lab - [read more in the docs](../manual/nodes.md#env).
+
+## Startup-config support for Cisco IOL
+
+@kaelemc continued to improve IOL support by adding support for startup-config #2347. Now you get a lightweight Cisco IOS-XE system with a decent feature set. Unbelievable!
+
+## Node Name magic variable
+
+To further streamline the topology definition file, @hyposcaler-bot added support for the `__clabNodeName__` magic variable that allows you to dynamically set the node name in the startup-configuration path.
+
+```yaml
+name: mylab
+topology:
+  defaults:
+    kind: nokia_srlinux
+    startup-config: cfgs/__clabNodeName__.partial.cfg
+  nodes:
+    node1:
+    node2:
+```
+
+The above topology will instruct `node1` to use `cfgs/node1.partial.cfg` and `node2` to use `cfgs/node2.partial.cfg`. All with a single default setting provided. Read more about this neat feature in the [nodes section](../manual/nodes.md#startup-config).
+
+## Redeploy command
+
+Many of us redeploy labs dozens times a day. Before #2374 implemented by @axxyhtrx we all have been punching in `sudo clab dep -c -t <topo>` to redeploy a lab. While it worked for a clean redeployment, it wasn't possible to redeploy a lab while keeping the Lab Directory.
+
+Now the [`redeploy`/`rdep`](../cmd/redeploy.md) is a handy and syntactically more pleasant way to redeploy a lab and it supports both scenarios with keeping and without keeping the Lab Directory.
+
+## Miscellaneous
+
+* @jkary fixes the way link tags are displayed for LAGs in #2306
+* SR Linux default config gets gRPC servers config blocks to support EDA onboarding #2368
+* support for STDIN topologies in `destroy` command #2376

mkdocs.yml

@@ -142,6 +142,7 @@ nav:
           - 5-stage Clos topology: lab-examples/templated02.md
       - Generic VM: lab-examples/generic_vm01.md
   - Release notes:
+      - "0.61": rn/0.61.md
       - "0.60": rn/0.60.md
       - "0.59": rn/0.59.md
       - "0.58": rn/0.58.md