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

Support for "shared" semantics in ResourceService

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.0.0, 1.1.0, 1.2.0, 1.3.0
    • Fix Version/s: 1.4.0
    • Component/s: None
    • Labels:
    • Story Points:
      3
    • Epic Link:
    • Sprint:
      Emu Sprint 3 (11/2 - 11/20)

      Description

      In current design allocating resource, allocates all its child's resources as well.
      In the Optical Use Case, we have Och Port Resource with ODU-TS as its child Resources.
      Och Port is allocated by OpticalConnectivityIntents, while the ODU-TS are allocated by the CircuitIntent.
      So, the exclusive mode of allocation (allocate resource and all its child resources), should not be the default behavior. Need to consider adding a parameter to the allocate() API which will specify whether Only the specified resource should be allocated or the resource and all its child resources.

        Attachments

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

          Activity

            People

            • Assignee:
              shimizu Shimizu Sho
              Reporter:
              an7562 Aliza Nagauker
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: