Abstract
The 'Connect' ux-application shows up-to-date infomation about the connection status from ONAP-CCSDK to netconf-servers.
Related issues
SDNC-581 - Getting issue details... STATUS
nodeId vs mountpointId vs deviceName vs pnfId vs network-element-name vs ip-address
Several information and data models describing the same "thing" but focus on different views or aspects. Identifiers of the such "thing" may have different names but its value s the same.
The term "nodeId" is used by OpenDaylight to identify a node of a topology. In transport telecommunication networks the node often, a device or network-element. Therefore, the value of nodeId, device-name or network-element-name must be the same. The ONAP project "Active and Available Inventory (AAI)" defines "physical network functions (PNF)" - The value of the pnfId should be also the same as nodeId.
A "Mountpoint" in OpenDaylight is describes a NetConf-Server and it connectivity from OpenDaylight point of view. If a network-element supports NetConf and runs a NetConf-Server, then the Mountpoint has the information about the NetworkElement-Management-IP-Address (AAI:PNF/oam-ip-address) and its name (nodeId).
| General | Telecomunication | ITU-T G.771 = ONF TR 512 | AAI-API |
|---|---|---|---|
Topology
| Network
| Domain (to be verified)
| network
|
User documentation
The 'Connect' application provides up-to-date connectivity information about the wireless devices in the network. It automatically displays new network elements and their connection status. Despite the network elements usually automatically mount themselves, an additional small window allows manually mounting devices/mediators. For better understanding alarms and status, a connection status log lists all the connection status changes of OpenDaylight mount points.
Specification
“Connect” User Interface should be implemented to show the available Network elements
Below are the UI elements to be implemented.
The table view implements the common ux-framework-table supporting sorting, filtering and pagination on the server.
The graphical user interface should be divided into three different accordions/panels
- Required Network Elements
- Unknown Network Elements
- Connection Status Log
button on the top right corner should be implemented to allow users to add/mount a device.
Actions are provided to jump to related application. (Bold implement till El Alto)
- FCAPS for fault, configuration, accounting, performance, security (Bold implementill El Alto)
- I Information
- Symbols to add/remove, mount, unmount
- Symbol .. to indicate WebConsole status availabe, available and reachable, not available
Greyout dependencies (g:grey, b:black)
| Display status | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Connected | g | b | b | b |
| Connecting | b | b | b | b |
| Disconnected | b | g | b | b |
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: Mount | Create ODL mountpoint | no change | In list, required=true |
| 6 | exists | false | Connected/ing | User: Unmount | Remove ODL mountpoint | Not in list anymore. | |
| 7 | exists | true | Connected/ing | User: Unmount | Remove ODL mountpoint | Not in list anymore. | |
| 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 |
-Saineetha - modified/corrected the above 5,7 in below table
| 5 | not existing | not existing | no entry | User: Add new mountpoint + button | Create ODL mountpoint | create-network-element | In list, required=true / false based on user selection |
| 7 | exists | true | Connected/ing | User: Unmount | Remove ODL mountpoint | In list with the connection status= Disconnected |
1.Required Network Elements
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
- Remove: Remove the device from the required network elements
2. Unknown Network Elements
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.
It might be a normal occurrence for very cheap devices, where an entire planning process to too expensive. But is may also happen that the identifier used in planning process differ from the identifier currently configured in the device.
The “Unknown Network Elements” panel shows the table with the following columns:Name
- Connection Status
- Host
- Port
- Core Model
- Air Interface
- Actions
- Unmount: Unmounts the device
- Add to Required: Add the device to the Required Network Element
3. Connection Status 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
- Name
- Connection Status
The values are stored on an ElasticSearch database. The REST-API is provided by the ApiGateway.
- Required Network Elements: The index is “mwtn” the doctype is “requirenetwork”
- Connection Status Log: The index is “mwtn ” the doctype is “eventlog”
The data for the unknown network elements panel should be fetched from the restConf.