Herbert Eiselt | 092189e | 2019-04-03 17:24:29 +0200 | [diff] [blame] | 1 | .. contents:: |
| 2 | :depth: 3 |
| 3 | .. |
| 4 | |
| 5 | Configuration |
| 6 | ============= |
| 7 | |
| 8 | The application shows the actual values of all attributes of the |
| 9 | ONF-TR-532 for a selected physical network function (PNF). Each view of |
| 10 | a functional element is divide into capabilities, configuration, status, |
| 11 | current problem, current performance and history performance information |
| 12 | according to TR-532. |
| 13 | |
| 14 | A separate window is available for modifying the configuration. All |
| 15 | changes made are sent to the device in a single NetConf bulk request. |
| 16 | The operator is notified about successfully configuring the device. |
| 17 | |
| 18 | Implementation |
| 19 | -------------- |
| 20 | |
| 21 | The applications are implemented as OpenDaylight-DLUX web application |
| 22 | using the RestConf northbound interface of the SDN controller. The key |
| 23 | frameworks are: Maven, Angular.js, Bootstrap and UI-Grid. |
| 24 | |
| 25 | Connections status information are updated automatically due to a web |
| 26 | socket for notifications from OpenDaylight to the browser. |