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

Merge branch 'patch-1' into 'master'

Update 05-implementation.md

See merge request cocsn/gosdn!11
parents 9f613f64 5befe158
Branches
Tags
1 merge request!11Update 05-implementation.md
Pipeline #51885 passed
......@@ -29,6 +29,20 @@ For now we can only use the OpenAPI 2.0 standard. This is because `go-swagger` d
## Storing Information
This section keeps by now some loose thoughts about what information has to be stored how and where.
There seem to be two classes of information to be stored in the controller:
* short-living information, such as, current topology
* long-time information, such as, information about principle network domains, elements in such a domain, etc
* short-living information, such as, current configured network flows or obtained network configuration out of use case #1 (CoCSN)
* long-time information, such as, information about principle network domains, elements in such a domain if directly learned from SBI, etc
This may or may not result in two different places to store data. Unclear yet.
### Some more details for implementation for the database(s)
We define the principle network domain (PND) and each piece of information of any PND has to be stored in relation the particular PND.
Specification of a PND:
* Human readable name of PND
* Textual description for further information
* Set of supported Southbound-Interfaces, e.g., RESTCONF, TAPI, OpenFlow etc
* Phyiscal Inventory Network Elements, hosts and links
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment