Uploaded image for project: 'ONOS'
  1. ONOS
  2. ONOS-4417

Move out domain/usecase specific Port from Core part of ONOS. (OtuPort)

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 1.2.0, 1.3.0, 1.4.0, 1.5.0
    • Fix Version/s: 1.6.0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      3
    • Epic Link:
    • Sprint:
      Goldeneye Green Sprint #3

      Description

      We would like to allow Java class/objects for domain/use case specific Port for the convenience of Apps, but would like to keep distributed core isolated for these specialized ports.

      Ideally required information should be represented as an annotation in the DefaultPort

      {Description}

      object when they're stored inside distributed Core, etc. so that we won't need to modify ONOS core whenever we introduce more types of a Port.

      It is likely to require tasks like:

      • Convert OchPort, OduCltPort, OmsPort to be a wrapper around DefaultPort
      • Create a shim/wrapper DeviceService interface etc. which will convert DefaultPort to specific Ports like OchPort, etc.

        Attachments

          Issue Links

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

            Activity

              People

              Assignee:
              y-higuchi Yuta Higuchi
              Reporter:
              y-higuchi Yuta Higuchi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: