Skip to content

Fix typos in README #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
srieger1 wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −3
Open

Fix typos in README #54

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# DigSiNet

This project implements a proof-of-concept environment to run Network Digital Twins (NDT). It primarily uses [containerlab](https://containerlab.dev/), but can also use other platforms to build, manage and monitor the twins. The concept uses multiple twins that can leverage different platforms, topologies and tools to specifically simulate and emulate only parts of the functionality of the real network. As they only partially share characteristics with the real network and multiple ones can be used an combined with each sibling using a different platform being well-suited for its purpose, they are called siblings instead of twins.
This project implements a proof-of-concept environment to run Network Digital Twins (NDT). It primarily uses [containerlab](https://containerlab.dev/), but can also use other platforms to build, manage and monitor the twins. The concept uses multiple twins that can leverage different platforms, topologies and tools to specifically simulate and emulate only parts of the functionality of the real network. As they only partially share characteristics with the real network and multiple ones can be used and combined with each sibling using a different platform being well-suited for its purpose, they are called siblings instead of twins.

# Concept

Expand All @@ -14,7 +14,7 @@ DigSiNet's architecture currently consists of the following components:
* Apps
* Queues

Details regarding the architecture and its components are also described in the working-draft of the documentation [https://srieger1.github.io/digsinet/](https://srieger1.github.io/digsinet/) and were published and presented in our paper at NOMS 2024-2024 IEEE Network Operations and Management Symposium [https://ieeexplore.ieee.org/document/10575632](https://ieeexplore.ieee.org/document/10575632). As DigSiNet is currently being used as a proof-of-concept to run NDT experiments, its architecture and compoments are still subject to change, as can also be observed from the current development branches [https://github.com/srieger1/digsinet/branches](https://github.com/srieger1/digsinet/branches).
Details regarding the architecture and its components are also described in the working-draft of the documentation [https://srieger1.github.io/digsinet/](https://srieger1.github.io/digsinet/) and were published and presented in our paper at NOMS 2024 – IEEE Network Operations and Management Symposium [https://ieeexplore.ieee.org/document/10575632](https://ieeexplore.ieee.org/document/10575632). As DigSiNet is currently being used as a proof-of-concept to run NDT experiments, its architecture and components are still subject to change, as can also be observed from the current development branches [https://github.com/srieger1/digsinet/branches](https://github.com/srieger1/digsinet/branches).

# Requirements

Expand All @@ -33,7 +33,7 @@ Start DigSiNet by running:
sudo ./digsinet.py
```

The example starts digsinet.clab.yml by default to be used as the "real" network topology and two siblings. Each sibling can use an adapted topology and individual tools and platforms different from the real network. See digisinet.yml config file for examples and to change the setup.
The example starts digsinet.clab.yml by default to be used as the "real" network topology and two siblings. Each sibling can use an adapted topology and individual tools and platforms different from the real network. See digsinet.yml config file for examples and to change the setup.

Alternatively, a sample using [Nokia SR-Linux](https://containerlab.dev/manual/kinds/srl/) is provided in ```digsinet-srl.yml```. This config can be used by running:

Expand Down
Loading