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

Component configuration event accumulation

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.3.0
    • Component/s: None
    • Labels:
    • Story Points:
      2
    • Epic Link:
    • Sprint:
      Cardinal Sprint 4 (5/4-5/15)

      Description

      As a deployer, I would like to aggregate multiple subsequent component configuration updates into a single invocation of the @Modified method in order to reduce the number of reconfiguration operations.

      Implementation Note:

      • Insert derivative of AbstractAccumulator in ComponentConfigManager, between set/reset and triggerUpdate, to accrue multiple config updates for the same component to result in only one configuration update for that component.
      • The accumulator can simply accrue target component names and when processing a batch, trigger update for each component just once.
      • It should be sufficient to use a single accumulator, at least initially.
      • Suggested settings for the accumulator: maxItems=100; maxBatchMillis=1000; maxIdleMillis=250;

        Attachments

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

          Activity

            People

            Assignee:
            aaron Aaron Kruglikov
            Reporter:
            tom Thomas Vachuska
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: