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
Thanks for your interest in contributing to Catalyst SD-WAN Lab! Please take a moment to review this document **before submitting a pull request**:
4
-
* Want to add something from yourself? [Make a PR](https://github.com/cisco-open/sdwan-lab-deployment-tool/pulls).
5
-
* To make a PR - fork the repository, make your changes and make the pull request. Now just wait for the review and feedback from our developers.
6
-
* Make clear PR description and include doc strings in your code to make it easily understandable.
7
-
* Always write a clear log message for your commits.
8
-
* Before submitting PR, verify the existings SD-WAN Lab tasks works without any issues.
9
-
* For CML interactions, use official [CML SDK](https://github.com/CiscoDevNet/virl2-client)
10
-
* For SD-WAN interactions, use official [Catalyst WAN SDK](https://github.com/CiscoDevNet/catalystwan)
11
-
* Bugs or feature requests? [Report it here](https://github.com/cisco-open/sdwan-lab-deployment-tool/issues) - remember to provide as much information as you can.
3
+
Thank you for your interest in contributing to Catalyst SD-WAN Lab! Please take a moment to review this document **before submitting a pull request**:
4
+
5
+
- Want to add something yourself? [Make a PR](https://github.com/cisco-open/sdwan-lab-deployment-tool/pulls).
6
+
- To make a PR, fork the repository, make your changes, and submit the pull request. Then, wait for review and feedback from our developers.
7
+
- Write a clear PR description and include docstrings in your code to make it easily understandable.
8
+
- Always write clear log messages for your commits.
9
+
- Before submitting a PR, verify that the existing SD-WAN Lab tasks work without any issues (see [Testing Before Pull Requests](#testing-before-pull-requests)).
10
+
- For CML interactions, use the official [CML SDK](https://github.com/CiscoDevNet/virl2-client).
11
+
- For SD-WAN interactions, use the official [Catalyst WAN SDK](https://github.com/CiscoDevNet/catalystwan).
12
+
- Found a bug or have a feature request? [Report it here](https://github.com/cisco-open/sdwan-lab-deployment-tool/issues) and provide as much information as possible.
13
+
14
+
## Testing Before Pull Requests
15
+
16
+
Before opening a pull request, please ensure all tests pass:
17
+
18
+
1. Create a virtual environment:
19
+
20
+
```
21
+
python3 -m venv venv
22
+
```
23
+
24
+
2. Activate the virtual environment:
25
+
26
+
```
27
+
source venv/bin/activate
28
+
```
29
+
30
+
The prompt will update with the virtual environment name (`venv`), indicating that it is active.
31
+
32
+
3. Upgrade initial virtual environment packages:
33
+
34
+
```
35
+
pip install --upgrade pip setuptools pytest
36
+
```
37
+
38
+
4. Install the tool from your local repository:
39
+
40
+
```
41
+
pip install --upgrade .
42
+
```
43
+
44
+
Alternatively, you can install the tool from your branch, for example:
5. Load the environment variables used to deploy a test lab:
51
+
52
+
```
53
+
source lab.env
54
+
```
55
+
56
+
6. Run tests:
57
+
58
+
```
59
+
pytest -s test_csdwan.py
60
+
```
61
+
62
+
This will run all tasks and display real-time output. Make sure to resolve any test failures before submitting your PR. If needed, you can modify the control components and edge versions in the test_csdwan.py file.
Copy file name to clipboardExpand all lines: README.md
+34-16Lines changed: 34 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -303,26 +303,43 @@ This task restores Catalyst SD-WAN lab from a backup. This task will:
303
303
3. Restore SD-WAN Manager templates, policies and configuration groups using [Sastre](https://github.com/CiscoDevNet/sastre).
304
304
4. Verify if there are any WAN Edges in the topology (SD-WAN and SD-Routing). If yes, then generate the new OTP and automatically reonboard them to SD-WAN Manager.
305
305
306
-
This task has several task-specific parameters, including working directory from where backup is restored.
306
+
This task has several task-specific parameters, including working directory from where backup is restored. You can also overwrite the software version for control components and SD-WAN/SD-Routing Edges (note that specifying version lower than the one in the backup is not supported).
│ --manager <manager-ip> SD-WAN Manager IP address, can also be defined via MANAGER_IP environment │
314
-
│ --muser <manager-user> SD-WAN Manager username, can also be defined via MANAGER_USER environment variable. │
315
-
│ --mpassword <manager-password> SD-WAN Manager password, can also be defined via MANAGER_PASSWORD environment variable. │
316
-
│ --mmask <manager-mask> Subnet mask for given SD-WAN Manager IP (e.g. /24), can also be defined via MANAGER_MASK environment variable. │
317
-
│ --mgateway <manager-gateway> Gateway IP for given SD-WAN Manager IP, can also be defined via MANAGER_GATEWAY environment variable. │
318
-
│ --lab <lab_name> CML Lab name, can also be defined via LAB_NAME environment variable. │
319
-
│ --workdir <directory> Restore source folder │
320
-
│ --deleteexisting If there is already lab running with same name and using same SD-WAN Manager IP, delete this lab before restoring. Note the all running lab data │
321
-
│ will be lost! │
322
-
│ --retry If for some reason your script lost connectivity during SD-WAN Manager boot, you can add --retry to continue onboarding the lab that is already │
@@ -391,10 +408,11 @@ Once the installation is finished and you have restarted Windows you are able to
391
408
You can read more about [Linux on Windows with WSL here](https://learn.microsoft.com/en-us/windows/wsl/install).
392
409
393
410
## FAQ
411
+
394
412
Q1: My devices' consoles have stopped working after I created my own configuration groups. How do I recover console access?
395
413
396
414
A1: Always include the `platform console serial` command in an CLI add-on feature parcel to ensure your consoles work from the CML UI. Note that after adding this command, a WAN Edge reboot is required.
397
-
415
+
398
416
Q2: Can I SSH to my Manager instance directly?
399
417
400
418
A2: Yes, you can if you are using an external IP. However, if you are using PATty, you cannot, as we only map the HTTPS port.
0 commit comments