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

Modify the semantic of MP2SP intents introducting the partially failed state

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 1.2.0, 1.2.1
    • Fix Version/s: 1.3.0, 1.2.2
    • Component/s: None
    • Labels:

      Description

      Right now, due to a "ALL or NOTHING" logic implemented in the intent framework, using MP2SP intents, if any end-point (both ingress and egress) fails, the entire intent fails, with a bad impact on the overall user traffic forwarding.

      As a user I would like the following behavior, in case something fails:

      • If the SINGLE egress point fails all the intent should fails - since the destination is not reachable
      • If anything that would prevent all the MP sources to reach the destination fails, the entire intent should fail
      • If anything in between a certain source and the destination fails, we should re-route to a sub-optimal path that specific path, without touching the rest of the intent
      • If any of the MP sources fails, ONLY that specific part of the intent should fail, causing the overall intent to go in a different state (partially failed?)
      • If an intent is partially failed the user should be able to inspect what exactly failed

        Attachments

        # Subject Branch Project Status CR V

          Activity

            People

            Assignee:
            jono Jonathan Hart
            Reporter:
            luca Luca Prete
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: