Skip to content
Snippets Groups Projects
Commit 4c134172 authored by Martin Stiemerling's avatar Martin Stiemerling :speech_balloon:
Browse files

Update 05-implementation.md

parent 09b482d6
Branches
Tags
3 merge requests!90Develop,!62Resolve "Update database in order to achieve the long-term goals of the project",!53V.0.1.0 Codename Threadbare
Pipeline #51686 passed
This commit is part of merge request !53. Comments created here will be created in the context of that merge request.
...@@ -45,6 +45,25 @@ databases should be used to store the different topology graphs and their ...@@ -45,6 +45,25 @@ databases should be used to store the different topology graphs and their
pontential dependencies? How should the interface between gosdn and this pontential dependencies? How should the interface between gosdn and this
database look like? database look like?
Here is an attempt to describe the above text in a graphical reprensetation:
```mermaid
graph TB
SubGraph1 --> SubGraph1Flow
subgraph "SubGraph 1 Flow"
SubGraph1Flow(SubNode 1)
SubGraph1Flow -- Choice1 --> DoChoice1
SubGraph1Flow -- Choice2 --> DoChoice2
end
subgraph "Main Graph"
Node1[Node 1] --> Node2[Node 2]
Node2 --> SubGraph1[Jump to SubGraph1]
SubGraph1 --> FinalThing[Final Thing]
end
```
### Potential other Inventories ### Potential other Inventories
There may be the potential need to store information beyond pure topologies, There may be the potential need to store information beyond pure topologies,
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment