diff options
Diffstat (limited to 'docs/guides')
| -rw-r--r-- | docs/guides/onap-user/connect.rst | 9 | ||||
| -rw-r--r-- | docs/guides/onap-user/pnfConfig.rst | 6 | ||||
| -rw-r--r-- | docs/guides/onap-user/pnfFault.rst | 10 | ||||
| -rw-r--r-- | docs/guides/onap-user/pnfPerformance.rst | 11 |
4 files changed, 21 insertions, 15 deletions
diff --git a/docs/guides/onap-user/connect.rst b/docs/guides/onap-user/connect.rst index 6da746953..c93c1f9c1 100644 --- a/docs/guides/onap-user/connect.rst +++ b/docs/guides/onap-user/connect.rst @@ -9,9 +9,10 @@ The 'Connect' application on OpenDaylight provides up-to-date connectivity information about the wireless devices in the network. It automatically displays new Network Elements and their connection status. Usually, the Network Elements mount themselves. If necessary, they can -be mounted manually by right-clicking on the element. For better -understanding of alarms and status, a connection status log lists all -the connection status changes of OpenDaylight mount points. +be mounted manually by right-clicking on the element and selecting the +'mount' action. For better understanding of alarms and status, a +connection status log lists all the connection status changes of +OpenDaylight mount points. Views ----- @@ -40,5 +41,5 @@ display information relevant to the selected element. Connection Status Log ~~~~~~~~~~~~~~~~~~~~~ -The log lists the connections status changes between SDN Controller and +The log lists the connection status changes between SDN Controller and NetConf servers (devices). diff --git a/docs/guides/onap-user/pnfConfig.rst b/docs/guides/onap-user/pnfConfig.rst index 29e2296c7..2baa58f85 100644 --- a/docs/guides/onap-user/pnfConfig.rst +++ b/docs/guides/onap-user/pnfConfig.rst @@ -18,9 +18,9 @@ The operator is notified about successfully configuring the device. Implementation -------------- -The application is implemented as OpenDaylight-DLUX web application -using the RestConf northbound interface of the SDN controller. The key -frameworks are: Typescript, React and material-ui. +The application is implemented as ODLUX web application using the +RestConf northbound interface of the SDN controller. The key frameworks +are: Typescript, React and material-ui. Connection status information is updated automatically using a web socket for notifications from OpenDaylight to the browser. diff --git a/docs/guides/onap-user/pnfFault.rst b/docs/guides/onap-user/pnfFault.rst index 5e54547a9..4e3c9f5a3 100644 --- a/docs/guides/onap-user/pnfFault.rst +++ b/docs/guides/onap-user/pnfFault.rst @@ -15,8 +15,8 @@ Views The graphical user interface is separated into three views. -Current Alarms -~~~~~~~~~~~~~~ +Current Problem List +~~~~~~~~~~~~~~~~~~~~ Lists all current active faults in the network. In addition, it also lists alarms sent by the SDN controller itself, which detects connection @@ -53,6 +53,6 @@ are stored. There is no logic implemented on the client side. An alarm status bar in the header of the web application informs the operator about the health status of the network. -The OpenDaylight-DLUX web application uses web sockets to update the -graphical user interface of the Problem Notifications (devices) and -Connection Status Notifications (ODL) in real-time. +The ODLUX web application uses web sockets to update the graphical user +interface of the Alarm Notifications (devices) and Connection Status +Notifications in real-time. diff --git a/docs/guides/onap-user/pnfPerformance.rst b/docs/guides/onap-user/pnfPerformance.rst index 2f37ac7f2..17e4a5119 100644 --- a/docs/guides/onap-user/pnfPerformance.rst +++ b/docs/guides/onap-user/pnfPerformance.rst @@ -16,6 +16,11 @@ Performance history values After selecting a connected PNF supporting ONF-TR-532 and a physical interface, the application collects the received and centralized stored -performance values for this interface. The data gets displayed as a line -chart to visualize the data in a given time period and a corresponding -table. If the table gets filtered, the chart updates itself. +performance values for this interface. + +The values are visualized using two views: a line chart and a table, +with the chart always shown first. To switch between them, toggle +buttons can be used. The chart view offers a filter to quickly limit the +shown values. To keep both views in sync, the filters of the chart and +the table are connected. If one view is filtered, the other one gets +updated in the background. |