Related story:  SDNC-1396 - Getting issue details... STATUS

ODLUX Connect app provides a link to Device specific CLI Clients in the GUI. This function is in older SDN-C/SDN-R releases specific for ONF Core 1.2 devices.

In Guilin ODLUX GUI is requesting related information via RESTCONF interface. With ONF Core model 1.4 and O-RAN this function is implemented in different ways and needs to be moved into the related specific-devicemanager. 

Effected: ODLUX connectApp, data-provider, devicemanager, specific devicemanagers:  O-RAN, ONF, ONF1.4 , Simulators: O-RAN

Changes

  • data-provider rev. 20201110 YANG spec updated to contain related request. 
  • ODLUX adaption to use data-provider instead of restconf to query "GUI cut through" information
  • provide get at data-provicer rpc to request GUI cut through information for a device
    • Parameters to be stared in the database are
      • id (Mandatory, Key entry) contains "MountpointId" (node-id) of device. This Id can be used to filter this entry. It needs to be the database "_id" for this reason.
      • name (Optional) contains the name of the WEB System, that could be provided. (Parameter should not exist in database if not available).
      • weburi (Mandatory) contains the URI/Link to the webtool that can be opended via link.
      • The database entry is created if device is connected and removed, if device is not connected.
      • Error handling: If Mandatory parameters are not available, do not write to database and create the log entry with "debug" level during startup.
  • O-RAN related yang spec onap-system:2020-10-26 (Status: available)
  • extend specific devicemanagers accordingly
    • ONF-Core model 1.2 via network-element extensions ( SDNC-1498 - Getting issue details... STATUS )
      • ONFCore model: network-element extension list, <value-name>webUri</value-name>
    • ONF Core model 1.4 via  (Removed from list because GUI cut through not yet specified)
    • O-RAN: Support of generic GuiCutThrough (=URL Link) by ietf-system augmentation (onap/o-ran)
      • yang spec onap-system:2020-10-26 available
  • specific-devicemanager reads this information once during startup. 

Architectural changes

  • data-provider model: Extend network-element-connection-entity with GUI link
  • specific devicemanager is reading GUI cut through information and pushing it to data-provider via network-element-connection-entity
  • data-provider rpc is reading information from database and providing it 
  • ODLUX uses data-provider to get GUI cut through information
  • Simulator should support this only for O-RAN + ONF1.4

For simulation the URL should be

  • No labels