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: docs/cmd/deploy.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,6 +143,17 @@ The extended File ACLs are provisioned for the lab directory by default, unless
143
143
144
144
While this is useful in most cases, sometimes extended File ACLs might prevent your lab from working, especially when your lab directory end up being mounted from the network filesystem (NFS, CIFS, etc.). In such cases, you can use this flag to skip the ACL provisioning.
145
145
146
+
#### owner
147
+
148
+
The local `--owner` flag allows you to specify a custom owner for the lab. This value will be applied as the owner label for all nodes in the lab.
149
+
150
+
This flag is designed for multi-user environments where you need to track ownership of lab resources. Only users who are members of the `clab_admins` group can set a custom owner. If a non-admin user attempts to set an owner, the flag will be ignored with a warning, and the current user will be used as the owner instead.
151
+
152
+
Example:
153
+
```bash
154
+
containerlab deploy -t mylab.clab.yml --owner alice
Copy file name to clipboardExpand all lines: docs/cmd/generate.md
+16-5Lines changed: 16 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ It is assumed, that the interconnection between the tiers is done in a full-mesh
18
18
19
19
#### name
20
20
21
-
With the global `--name | -n` flag a user sets the name of the lab that will be generated.
21
+
With the global `--name` flag a user sets the name of the lab that will be generated.
22
22
23
23
#### nodes
24
24
The user configures the CLOS fabric topology by using the `--nodes` flag. The flag value is a comma separated list of CLOS tiers where each tier is defined by the number of nodes, its kind and type. Multiple `--node` flags can be specified.
@@ -42,19 +42,19 @@ For example the following value will generate a 3-tier CLOS fabric of cEOS nodes
42
42
43
43
```bash
44
44
# cEOS fabric
45
-
containerlab gen -n 3tier --kind ceos --nodes 4,2,1
45
+
containerlab gen --name 3tier --kind ceos --nodes 4,2,1
46
46
47
47
# since SR Linux kind is assumed by default
48
48
# SRL fabric command is even shorter
49
-
containerlab gen -n 3tier --nodes 4,2,1
49
+
containerlab gen --name 3tier --nodes 4,2,1
50
50
```
51
51
52
52
#### image
53
53
Use `--image` flag to specify the container image that should be used by a given kind.
54
54
55
55
The value of this flag follows the `kind=image` pattern. For example, to set the container image `ceos:4.32.0F` for the `ceos` kind the flag will be: `--image ceos=ceos:4.32.0F`.
56
56
57
-
To set images for multiple kinds repeat the flag: `--image srl=srlinux:latest --image ceos=ceos:4.32.0F` or use the comma separated form: `--image srl=srlinux:latest,ceos=ceos:latest`
57
+
To set images for multiple kinds repeat the flag: `--image srl=ghcr.io/nokia/srlinux:latest --image ceos=ceos:4.32.0F` or use the comma separated form: `--image srl=ghcr.io/nokia/srlinux:latest,ceos=ceos:latest`
58
58
59
59
If the kind information is not provided in the `image` flag, the kind value will be taken from the `--kind` flag.
60
60
@@ -96,6 +96,17 @@ Default: `clab`.
96
96
#### ipv4-subnet | ipv6-subnet
97
97
With `--ipv4-subnet` and `ipv6-subnet` it's possible to change the address ranges of the management network. Nodes will receive IP addresses from these ranges if they are configured with DHCP.
98
98
99
+
#### owner
100
+
101
+
With `--owner` flag you can specify a custom owner for the lab. This value will be applied as the owner label for all nodes in the lab.
102
+
103
+
This flag is designed for multi-user environments where you need to track ownership of lab resources. Only users who are members of the `clab_admins` group can set a custom owner. If a non-admin user attempts to set an owner, the flag will be ignored with a warning, and the current user will be used as the owner instead.
104
+
105
+
Example:
106
+
```bash
107
+
containerlab generate --name 3tier --nodes 8,4,2 --owner bob --deploy
108
+
```
109
+
99
110
### Examples
100
111
101
112
#### Generate topology for a 3-tier CLOS network
@@ -105,7 +116,7 @@ Generate and deploy a lab topology for 3-tier CLOS network with 8 leafs, 4 spine
105
116
The `srl` kind in the image and license flags can be omitted, as it is implied by default
0 commit comments