Uploaded image for project: 'SEBA'
  1. SEBA
  2. SEBA-744

When an IP is assigned to a Subscriber do not invoke the model_policy

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: SEBA 2.0
    • Component/s: NEM
    • Labels:
      None

      Description

      An IP change does not require any synchronization. Make sure it's not triggering the chain.

       

      Ideally add a check in the vOLTServiceInstance sync_step so that if nothing important has changed in the subscriber we are not calling ONOS again.

      In addition, ONOS olt-app should protect itself, so an attempt to provision a subscriber that has already been programmed does not affect the data plane

        Attachments

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

          Activity