Version 6 (modified by ibaldin, 8 years ago)


Configuring ORCA NLR Sherpa handler


The NLR Sherpa handler provides ORCA with the ability to invoke the dynamic VLAN service named Sherpa provided by the National Lambda Rail.


NLR handler is self-contained and does not require any external software. It is configured by specifying property pointing to a file usually installed under $ORCA_HOME/config. Example of an actor configuration file.

Handler details

The NLR handler accepts the following properties from the controller:

  • config.interface.1 - first interface name (URN)
  • config.interface.2 - second interface name (URN)
  • request.duration - duration of the reservation in seconds
  • request.bandwidth - bandwidth in Bps
  • unit.vlan.tag - optional tag to use. If no tag is specified, NLR Sherpa will issue it and it will be returned as part of unit.vlan.tag return property

Return properties:

  • unit.vlan.tag in the form tag|interfaceA|tag|interfaceZ|tag

Principle of operation

Sherpa allows the user to maintain a pool of reserved tags that can be bound to paths. The handler is designed to take advantage of this feature to enable it to reach sites that operate with a narrow set of vlan tags. The unit.vlan.tag property is optional to the handler. Her is the pseudocode the describes how the handler behaves at join:

if unit.vlan.tag is empty
    retrieve the list of previously reserved tags
    if list is not empty
        retrieve the first tag
        pick a random new tag
        reserve a new tag
    provision path for the selected tag
    retrieve the list of previously reserved tags
    if unit.vlan.tag is on the list
        provision the path for this tag
        attempt to reserve the tag
        if successful
            provision the path for the tag
            fail with exception

For leave the handler removes the path and attempts to re-reserve the tag used for the path for future use.