...
The table view implements the common ux-framework-table supporting sorting, filtering and pagination the below properties on the server end.
- Sorting
- filtering
- export option to export the data to .CSV
- pagination
The graphical user interface should be divided into three different accordions/panels
- Network Elements
- Connection Status Log
1. Network Elements
Network Elements are physical network functions, which are planned or expected in the network. This means the identifier, IP addresses and its required configuration is well-known and available in a planning database or in ONAP A&AI.
This view also offers to manually configure/mount the device with the '+' icon. The SDN controller will then start connecting the Netconf server.
button on the top right corner should be implemented to allow users to add/mount a device.
The “Network Elements” panel shows the table with the following columns:
- Node Name
- Required
- Connection Status
- Host
- Port
- Core Model
- Type
- Actions
- Mount: Mount the device
- Unmount: Unmount the device
- info: diaplays Yang capabilities of the Network element
- Edit : Edit the element info
- Remove: Remove the device from the required network elements
- I - link to Inventory for the selected element
- F C A P S links actions are provided to jump to related
...
- application (Bold implement till El Alto)
- FCAPS for fault, configuration, accounting, performance, security
- application (Bold implement till El Alto)
...
...
- Symbol .. to indicate WebConsole status
...
- available, available and reachable, not available
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Greyout dependencies (g:grey, b:black)
| Display status | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Connected | b | b | b | b |
| Connecting | b | b | b | b |
| Disconnected | b |
| b | b | b |
Edit Required field dropdown in the dialogbox
| Display status of Required | True | False |
|---|---|---|
| true | b | b |
| false | b | b |
info button: Yang capabilities
As per the old DLUX the info button shows the yang capabilities of the element as below:
When the info button is clicked the same display of yang capabilities will be followed in the new implementation as well showing just the module name and revision without table properties like sorting/filter/pagination.
Example 1 : "(urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)ietf-netconf-monitoring",
from the above capability the highlighted date 2010-10-04 will be the revision and ietf-netconf-monitoring will be the module .
Example 2: "urn:ietf:params:netconf:capability:notification:1.0"
for the above capability as we do not have revision and the module name , this details/ entry will not be considered to display in the UI.
Example 3: urn:ietf:params:netconf:capability:yang-library:1.0?revision=2019-01-04&module-set-id=60,
even the above capability is not considered as it has special character '&' after the date followed by some value
The requested information source will be: GET /restconf/operational/network-topology:network-topology/topology/topology-netconf/node/{node-id}
Status → action → result
...
| ODL Mountpoint | ES required | Display status | Action | ODL Rest | ES database (Client or Server) | GUI | |
|---|---|---|---|---|---|---|---|
| 1 | exists | true | Connected/ing | User: Press minus | Remove ODL mountpoint | delete-network-elementconnection | Not in the list anymore. |
| 2 | exists | false | Connected/ing | User: Press minus | Remove ODL mountpoint | delete-network-elementconnection | Not in the list anymore. |
| 3 | exists | true | Connected/ing | User: Edit and change to required=false | no change | Change status to required=false | In list, required=false |
| 4 | exists | false | Connected/ing | User: Edit and change to required=true | no change | Change status to required=true | In list, required=true |
| 5 | not existing | no existing | no entry | User: Add new mountpoint + button | Create ODL mountpoint | create-network-element | In list, required=true / false based on user selection |
| 6 | exists | false | Connected/ing | User: Unmount | Remove ODL mountpoint | Not in list anymore. | |
| 7 | exists | true | Connected/ing | User: Unmount | Remove ODL mountpoint | In list with the connection status= Disconnected | |
| 8 | not existing | true | Disconnected | User: Edit and change to required=false | no change | delete-network-elementconnection | Not in list anymore. |
| 9 | not existing | true | Disconnected | User: Press minus | no change | delete-network-elementconnection | Not in list anymore |
| 10 | not existing | true | Disconnected | User: Edit and chage to required=false | no change | delete-network-elementconnection | Not in list anymore |
| 11 | exists & connected/ing | false | Connected/ing | Other: Mountpoint removed via RESTConf | Devicemanager has (Could be removed by client before) | Not in list anymore | |
| 12 | not existing | not existing | no entry | Other: Mountpoint created via RESTConf | Devicemanager has to create data with required=false | In list, required=false |
...
Required Network Elements are physical network functions, which are planned or expected in the network. This means the identifier, IP addresses and its required configuration is well-known and available in a planning database or in ONAP A&AI.
This view also offers to manually configure/mount the device with the '+' icon. The SDN controller will then start connecting the Netconf server.
The “Required Network Elements” panel shows the table with the following columns:
- Name
- Connection Status
- Host
- Port
- Actions
- Mount: Mount the device
- Unmount: Unmount the device
- info: diaplays Yang capabilities of the Network element
- Edit : Edit the element info
- Remove: Remove the device from the required network elements
info button: Yang capabilities
As per the old DLUX the info button shows the yang capabilities of the element as below:
When the info button is clicked the same display of yang capabilities will be followed in the new implementation as well showing just the module name and revision without table properties like sorting/filter/pagination.
Example 1 : "(urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)ietf-netconf-monitoring",
from the above capability the highlighted date 2010-10-04 will be the revision and ietf-netconf-monitoring will be the module .
Example 2: "urn:ietf:params:netconf:capability:notification:1.0"
for the above capability as we do not have revision and the module name , this details/ entry will not be considered to display in the UI.
Example 3: urn:ietf:params:netconf:capability:yang-library:1.0?revision=2019-01-04&module-set-id=60,
even the above capability is not considered as it has special character '&' after the date followed by some value
The requested information source will be: GET /restconf/operational/network-topology:network-topology/topology/topology-netconf/node/{node-id}
2
...
Most of the physical network function support an automatic registration procedure to the SDN controller. It may happen, that devices are connected to the SDN Controller but not available in planning data.
...
The “Unknown Network Elements” panel shows the table with the following columns:Name
.
...
Connection Status
...
- Unmount: Unmounts the device
- Add to Required: Add the device to the Required Network Element
...
Log
The log lists the connections status changes between SDN Controller and NetConf servers (devices).
The “Connection Status Log” panel shows the table with the following columns:
- Time
- Node Name
- Connection Status
The values are stored on an ElasticSearch database. The data provider is provided by the REST-API is provided by the ApiGatewayto read/write/update the data.
- Required Network Elements: The index is “mwtn” the doctype is “requirenetwork”
- The entity name to read the Networks element is read-network-element-connection-list
- The entity name to write to the Network elements is create-network-element-connection
- The entity name to update the Network element is update-network-element-connection
- The entity name to delete from network elements list is delete-network-element-connection
- Connection Status Log: The index is “mwtn ” the doctype is “eventlog”
- The
...
- entity name to read the Connection status Log is read-connectionlog-list