Uploaded image for project: 'Virtual Infrastructure Deployment'
  1. Virtual Infrastructure Deployment
  2. VID-693

VID support for PNF PnP: use Modern UI

    XMLWordPrintable

Details

    • Epic
    • Status: Closed
    • High
    • Resolution: Done
    • None
    • Honolulu Release
    • None
    • None
    • VID support for PNF PnP: PNF-ID parameter displayed in Modern UI
    • Done

    Description

      Within ONAP/Guilin release, the SO PNF PnP workflows have been refactored to BB technology.

      The VID SO API generation module need to be updated for support updated SO API interface, and consume an instancename parameter provided in the GUI (subject of VID-694). The SO API generation is covered in VID-695.

      Still, we need to display the PNF instacneName, following conditions need to be met:

      1. The Service model contains a PNF Resource
      2. The Service Model type is within a list of selected service models (e.g. 5G and vCPE - display PNF-ID, but don`t do that for vLB).

      This EPIC is expected to provide relevant implementation in VID to support this Service Model specific parameter. There will be (at least) two stories related to that EPIC:

      1. Modify the new VID GUI (Modern UI) in order to display the PNF instanceName, under conditions mentioned before
      2. Modify the VID Backend to include that input entry in the SO API call

      EPIC is dependant on SO EPIC: SO-1838 (expected to provide the SO/GR API capability for PNF PNP)

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. SO-1838 PNF handling refactoring: Generic support for multiple domain

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. REQ-430 PNF Plug & Play in R8

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              deen1985 Damian Nowak
              deen1985 Damian Nowak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: