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

Define interface between OFAgent and core.

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Initial list of what is needed between OFAgent and core (thanks to Hyunsun Moon)
      —
      OFAgent and core interfaces

      Core notifies OFAgent mostly with event. Expected events are (something like below not the exactly the same names),
      VIRTUAL_DEVICE_ADDED
      VIRTUAL_DEVICE_REMOVED
      VIRTUAL_DEVICE_AVAILABILITY_CHANGED
      VIRTUAL_PORT_ADDED
      VIRTUAL_PORT_REMOVED
      VIRTUAL_PORT_UPDATED (link status)
      VIRTUAL_FLOW_REMOVED
      OFAgent may registers packet processor to VirtualPacketService to handle PACKET_IN

      OFAgent calls some core APIs. Expected APIs are(something like below not exactly the same names),
      getVirtualDevice with virtual device ID
      getVirtualPorts with virtual device ID
      getVirtualPort with virtual port ID
      getVirtualNetwork with virtual network ID —> to get controllers of the network
      getFlowEntries with virtual device ID
      getPortStats with virtual port ID
      getGroupStats with virtual device ID
      getGroupDescription with group ID
      getTableStats with virtual device ID
      will need link related APIs also to handle LLDP

        Attachments

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

          Activity

            People

            Assignee:
            myj Medha Joshi
            Reporter:
            cchiu Claudine Chiu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: