Uploaded image for project: 'Network Controller'
  1. Network Controller
  2. SDNC-261

SDNC-C to Develop REST API interface for remote triggering.

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Medium Medium
    • None
    • None
    • None

      Scope: SDN-C Development for REST API interface for remote triggering

      Backend impacts: will trigger additional features to

      Expand SDNC to support multi-vendor configuration

      Expand YANG templates

      SDNC functions to be supported

      Expand REST API interface

      Build microservices with SDNC functions

      On south bound side, create and deploy VNF. For standard config – use Netconf, for non-standard config. – do the conversion.

      South bound today supports Cisco, Juniper, ALU, Nokia, etc.

      North bound Interface will not change.Some APIs should be able to support it

      The interface type for different vendors will be taken into account. For the interface, Some vendors like Cisco uses terminology like port interface, etc. some like Juniper uses terminology like INF, etc. Commonality between the different vendors will have be got and vendor agnostic scripts will need to be developed.

      North Bound interface should have a pre defined set of commands. The different types of APIs used will be

      Update configuration

      Upgrade configuration

      Backup configuration

      Acceptance Criteria: As an SDN user, I should be able to do remote triggering via REST APIs.

            Unassigned Unassigned
            gayatri gayatri
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: