You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sros/README.md
+28-18
Original file line number
Diff line number
Diff line change
@@ -3,48 +3,58 @@
3
3
This is the vrnetlab docker image for Nokia VSR / SROS.
4
4
5
5
## Building the docker image
6
+
6
7
Ask your Nokia representative for the VSR/VSIM image.
7
8
Copy the `sros-vm.qcow2` file in `vrnetlab/sros` directory and rename the file by appending the SR OS version to it.
8
9
For example, for SR OS version 20.10.r1 make sure that the qcow2 file will be named as `sros-vm-20.10.R1.qcow2`. The version (20.10.R1) will be used as a container image tag.
9
10
10
11
Run `make docker-image` to start the build process. The resulting image is called `vrnetlab/vr-sros:<version>`. You can tag it with something else if needed, like `vr-sros:<version>`.
11
12
12
-
13
13
It's been tested to run with the following versions:
14
14
15
-
* 20.10.R1 -- 20.10.R3
16
-
* 21.2.R1
15
+
* 20.10.R1 -- 20.10.R3
16
+
* 21.2.R1
17
17
18
18
## Variants
19
+
19
20
Nokia SR OS virtualized simulator (VSIM) can be configured to emulate many chassis and cards combinations.
20
21
21
-
To give vrnetlab users flexibility of choice, this fork provides a number of such combinations, which are called _variants_.
22
+
To give vrnetlab users the flexibility of choice, this fork provides a number of such combinations, which are called _variants_.
22
23
23
24
By selecting a certain variant (referred by its `name`) the VSIM will start with a certain configuration as per the following table:
24
25
25
-
| Name | mode | Control plane | Line card | RAM (GB) | Max NICs |
The variants are [defined in the code](https://github.com/hellt/vrnetlab/blob/bf70a9a9f2f060a68797a7ec29ce6aea96acb779/sros/docker/launch.py#L38-L66) as a dictionary. If a variant you need is not in the table, use the `custom` variant and define the emulated platform yourself as described below.
26
+
| Name | mode | Control plane | Line card | RAM (GB) | Max NICs |
The variants are [defined in the code](https://github.com/hellt/vrnetlab/blob/bf70a9a9f2f060a68797a7ec29ce6aea96acb779/sros/docker/launch.py#L58) as a dictionary. If a variant you need is not in the table, use the `custom` variant and define the emulated platform yourself as described below.
38
45
39
46
### Custom variant
47
+
40
48
It is possible to provide a custom variant. For that, the variant argument must be formed in one of the following way, depending on the integrated or distributed platform:
0 commit comments