Changes between Version 3 and Version 4 of orca-sherpa

10/12/11 10:33:58 (8 years ago)
ibaldin (IP:



  • orca-sherpa

    v3 v4  
    99NLR handler is self-contained and does not require any external software. It is configured by specifying property pointing to a [source:orca/trunk/handlers/nlr/ file] usually installed under $ORCA_HOME/config.  
     11== Handler details == 
     13The NLR handler accepts the following properties from the controller: 
     14 * config.interface.1 - first interface name (URN) 
     15 * config.interface.2 - second interface name (URN) 
     16 * request.duration - duration of the reservation in seconds 
     17 * request.bandwidth - bandwidth in Bps 
     18 * 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 
     20Return properties: 
     21 * unit.vlan.tag in the form tag|interfaceA|tag|interfaceZ|tag 
     23== Principle of operation == 
     25Sherpa 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: 
     27if unit.vlan.tag is empty 
     28    retrieve the list of previously reserved tags 
     29    if list is not empty 
     30        retrieve the first tag 
     31    else 
     32        pick a random new tag 
     33        reserve a new tag 
     34    endif 
     35    provision path for the selected tag 
     37    retrieve the list of previously reserved tags 
     38    if unit.vlan.tag is on the list 
     39        provision the path for this tag 
     40    else 
     41        attempt to reserve the tag 
     42        if successful 
     43            provision the path for the tag 
     44        else 
     45            fail with exception 
     46    endif