Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
goSDN
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Terraform modules
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
danet
goSDN
Commits
4c134172
Commit
4c134172
authored
4 years ago
by
Martin Stiemerling
Browse files
Options
Downloads
Patches
Plain Diff
Update 05-implementation.md
parent
09b482d6
Branches
Branches containing commit
Tags
Tags containing commit
3 merge requests
!90
Develop
,
!62
Resolve "Update database in order to achieve the long-term goals of the project"
,
!53
V.0.1.0 Codename Threadbare
Pipeline
#51686
passed
4 years ago
Stage: test
This commit is part of merge request
!53
. Comments created here will be created in the context of that merge request.
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
documentation/design/05-implementation.md
+19
-0
19 additions, 0 deletions
documentation/design/05-implementation.md
with
19 additions
and
0 deletions
documentation/design/05-implementation.md
+
19
−
0
Edit
View file @
4c134172
...
@@ -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,
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment