Skip to content

Commit

Permalink
Showing 2 changed files with 52 additions and 0 deletions.
1 change: 1 addition & 0 deletions docs/htmltest.yml
Original file line number Diff line number Diff line change
@@ -15,6 +15,7 @@ IgnoreURLs:
- https://*github.com/
- https://twitter.com/*
- mysocket.io # remove mysocket.io links until we rework to border0.com
- https://supportcenter.checkpoint.com/ # started to fail, meh.
IgnoreDirectoryMissingTrailingSlash: true
IgnoreAltMissing: true
IgnoreSSLVerify: true
51 changes: 51 additions & 0 deletions docs/rn/0.39.md
Original file line number Diff line number Diff line change
@@ -31,8 +31,29 @@ We believe this will make your lab repos cleaner and easier to maintain.
}
}
```

The partial config can be provided as a [local file](../manual/kinds/vr-sros.md#partial-startup-config), [remote URL](../manual/kinds/vr-sros.md#remote-partial-files) or even [embedded](../manual/kinds/vr-sros.md#embedded-partial-files), yay!

Learn more about partial configs for SR OS [here](../manual/kinds/vr-sros.md#user-defined-config).

## Embedded startup-configs

The changes made for allowing SR OS to have partial configs also allowed all other nodes to enjoy embedding startup-configs into the topology file.

For example, this is a perfectly valid way to provide partial config for a Nokia SR Linux node:

```yaml
name: srl

topology:
nodes:
srl:
kind: nokia_srlinux
image: ghcr.io/nokia/srlinux:22.11.2
startup-config: |
system information location "I am embedded config"
```
## Node filtering
One of the most requested features is finally there. Users wanted to be able to deploy only a subset of nodes defined in their topology file. Usually, this was driven by the need to control the resource usage of the lab and optimize the deployment time.
@@ -41,6 +62,36 @@ Containerlab now allows users to provide a list of nodes to deploy, destroy, sav
Check out [Node Filtering docs](../manual/node-filtering.md) for details.
## CPU and Memory setting for SR OS nodes
With [hellt/vrnetlab](https://github.com/hellt/vrnetlab/releases/tag/v0.10.1) release v0.10.1 we support setting the CPU and Memory for SR OS nodes.
Before that feature was available, the CPU and Memory were set to the default values for a particular SR OS variant. This was not ideal as requirements change over time and when resources are underprovisioned, the node may not be able to start.
Now you can set the CPU and Memory for SR OS nodes directly in the topology file:
```yaml
# distrubuted node
sr:
kind: vr-sros
type: sr-1e
license: sros22.lic
env:
CP_MEMORY: 6 # CPM MEM
CP_CPU: 4 # CPM CPU
LC_MEMORY: 6 # Line card MEM
LC_CPU: 4 # Line card CPU

# integrated
sr:
kind: vr-sros
type: sr-1
license: sros22.lic
env:
MEMORY: 6
CPU: 4
```
## RARE joins Containerlab
We are happy to announce that [RARE](../manual/kinds/rare-freertr.md) Network OS is now supported by Containerlab. RARE stands for Router for Academia, Research & Education.

0 comments on commit d30983d

Please sign in to comment.