Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-14298

DCB UI : Allow Config type to be more than two not just default/running

    XMLWordPrintable

Details

    • Story
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 30.0.0
    • None
    • Security Level: Default (Default Security Scheme)
    • 5
    • Horizon - May 11 - 25
    • Yes

    Description

      User should be flexible enough to create multiple versions of DeviceConfig service not just two, default vs running.

      User can select service name DeviceConfig-xyz. xyz being config type.
      UI should consider config-type and use that in all places where default config is not used.
      ( Currently anything other than default represents Running configuration).

      This may need some changes in backend Rest end point as well.

      Attachments

        Issue Links

          related to

          Task - A task that needs to be done. NMS-14311 Update documentaiton for changes to types of configs

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Task - A task that needs to be done. NMS-14317 DCB Rest API: Update History to filter by config type

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Task - A task that needs to be done. NMS-14318 DCB UI: History and Compare should only display one config type

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              stheleman Scott Theleman
              cgorantla Chandra Gorantla
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: