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

Velocloud API interaction baselines API v2 where possible

    XMLWordPrintable

Details

    • Story
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Done
    • None
    • None
    • None
    • Security Level: Default (Default Security Scheme)
    • None
    • 8
    • Horizon 22 - Jul 7 - Jul 21, Horizon 22 - July 21 - Aug 4
    • Hide
      • All research and testing is done against a Velocloud Orchestrator of version 4.5.0 or later
      • All API interactions that can be accomplished using v2 of the Velocloud Orchestrator API should use that version
      • All v2-supportable API interactions fail gracefully if they encounter an older version of the Velocloud Orchestrator API
      Show
      All research and testing is done against a Velocloud Orchestrator of version 4.5.0 or later All API interactions that can be accomplished using v2 of the Velocloud Orchestrator API should use that version All v2-supportable API interactions fail gracefully if they encounter an older version of the Velocloud Orchestrator API

    Description

      In all areas of this effort where it is feasible to do so, we must baseline the implementation against v2 of the Velocloud Orchestrator REST API, which means paying attention to both API versions and Velocloud product versions during implementation, and not using any documentation for Velocloud versions older than 4.5.0.

      This story maps to proto-issue E5-5 in requirements doc.

      Note that the reality has turned out to be more complicated than first thought; see proto-epic E12 as modeled in NMS-14672 for detailed implications.

      Attachments

        Activity

          People

            aramos-vizcarra Alberto
            jeffg Jeff Gehlbach
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: