Skip to content

Commit

Permalink
tidying up the docs
Browse files Browse the repository at this point in the history
  • Loading branch information
networkop committed Jul 5, 2021
1 parent 0ef7c35 commit a85fbb3
Show file tree
Hide file tree
Showing 6 changed files with 12 additions and 16 deletions.
7 changes: 6 additions & 1 deletion docs/manual/kinds/cvx.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ CVX nodes launched with containerlab comes up with:
CVX supports two modes of operation:

* Using Firecracker micro-VMs -- this mode runs Cumulus VX inside a micro-VM on top of the native Cumulus kernel. This is the default way of running CVX nodes.
* Using only the container runtime -- this mode runs Cumulus VX container image directly inside the container runtime (e.g. Docker). Due to the lack of Cumulus VX kernel modules, some features are not supported, most notable one being MLAG. In order to use this mode add `runtime: docker` under the cvx node definition (see also this example).
* Using only the container runtime -- this mode runs Cumulus VX container image directly inside the container runtime (e.g. Docker). Due to the lack of Cumulus VX kernel modules, some features are not supported, most notable one being MLAG. In order to use this mode add `runtime: docker` under the cvx node definition (see also [this example](../../lab-examples/cvx02.md)).


## Managing cvx nodes
Expand Down Expand Up @@ -69,3 +69,8 @@ The following labs feature CVX node:

- [Cumulus Linux Test Drive](../../lab-examples/cvx03.md)
- [Cumulus and FRR](../../lab-examples/cvx01.md)


## Known issues or limitations

* CVX in Ignite is always be attache to the default docker bridge network
1 change: 0 additions & 1 deletion lab-examples/cvx02/README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
Example of how to run `cvx` nodes inside docker runtime.

> **Note 1** : cvx may take up to a minute to configure IP on swp12. This is due to it defaulting to DHCP'ing first.
> **Node 2**: `h1` node requires `ifreload -a` before the IP is configured on its `eth1` interface
4 changes: 2 additions & 2 deletions lab-examples/cvx02/topo.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ topology:
- sw1/interfaces:/etc/network/interfaces.d/host-mounts
h1:
kind: linux
image: networkop/host:ignite
image: networkop/host:ifreload
binds:
- h1/interfaces:/etc/network/interfaces

links:
- endpoints: ["sw1:swp12", "h1:eth1"]
- endpoints: ["sw1:swp12", "h1:eth1"]
10 changes: 4 additions & 6 deletions lab-examples/cvx03/lab-final.yml
Original file line number Diff line number Diff line change
Expand Up @@ -27,16 +27,14 @@ topology:
- spine01/frr.conf:/etc/frr/frr.conf

server01:
kind: cvx
image: networkop/host:ignite
kernel: networkop/ignite-kernel:5.4.108-amd64
kind: linux
image: networkop/host:ifreload
binds:
- server01/interfaces:/etc/network/interfaces

server02:
kind: cvx
image: networkop/host:ignite
kernel: networkop/ignite-kernel:5.4.108-amd64
kind: linux
image: networkop/host:ifreload
binds:
- server02/interfaces:/etc/network/interfaces

Expand Down
3 changes: 0 additions & 3 deletions lab-examples/cvx03/server01/interfaces
Original file line number Diff line number Diff line change
@@ -1,9 +1,6 @@
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
address 10.0.10.101
Expand Down
3 changes: 0 additions & 3 deletions lab-examples/cvx03/server02/interfaces
Original file line number Diff line number Diff line change
@@ -1,9 +1,6 @@
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth2
iface eth2 inet static
address 10.0.20.102
Expand Down

0 comments on commit a85fbb3

Please sign in to comment.