Changes between Version 13 and Version 14 of DevelopmentFaq

Show
Ignore:
Timestamp:
04/17/09 16:28:27 (10 years ago)
Author:
yxin (IP: 152.54.6.59)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentFaq

    v13 v14  
    5151      - request properties are sent to brokers 
    5252      - configuration properties are sent to site authorities 
    53       - local properties are kept locally and used by policies and 
    54         handlers 
     53      - local properties are kept locally and used by policies and handlers 
    5554      - resource properties are pushed down  
    5655 
     
    6766   - when a site exports resources to a broker or a broker writes a ticket to a service manager resource properties are included in the new ResourceSet. See the extract() method of ''orca.shirako.core.BrokerPolicy''. 
    6867 
    69    - before a service manager makes a request to a broker it can append 
    70          request properties to its request as parameters to the broker policy. 
    71          For an example see createReservation in 
    72      test/unit/src/main/java/orca/tests/unit/main/ReservationTestTool.java 
     68   - before a service manager makes a request to a broker it can append request properties to its request as parameters to the broker policy. 
     69         For an example see ''createReservation'' in ''test/unit/src/main/java/orca/tests/unit/main/ReservationTestTool.java'' 
    7370 
    74    - broker policies extract requst properties from incoming reservation 
    75          requests and use them as additional parameters. To see how this is 
     71   - broker policies extract requst properties from incoming reservation requests and use them as additional parameters. To see how this is 
    7672         done, take a look at: 
    7773 
    78          core/policy/src/main/java/orca/policy/core/BrokerWorstFitPolicy.java 
     74         ''core/policy/src/main/java/orca/policy/core/BrokerWorstFitPolicy.java'' 
    7975 
    8076     and 
    8177 
    82      core/policy/src/test/java/orca/policy/core/BrokerWorstFitPolicyTest.java 
     78         ''core/policy/src/test/java/orca/policy/core/BrokerWorstFitPolicyTest.java'' 
    8379 
    84     - service managers can set configuration properties before redeeming a 
    85       reservation from a site. Configuration properties are accessible to 
    86       the site's policy and to its setup and teardown handlers. 
     80    - service managers can set configuration properties before redeeming a reservation from a site. Configuration properties are accessible to the site's policy and to its setup and teardown handlers. 
    8781 
    88     - service managers can set local properties to a reservation before 
    89       invoking its join/leave handler and these properties will become 
    90       available to the handler. 
     82    - service managers can set local properties to a reservation before invoking its join/leave handler and these properties will become available to the handler. 
    9183'''2.'''        How is slice managed in ORCA? For instance, when to start and stop a slice and what are operations performed in starting/stopping a slice? 
    9284        '''ANSWER:'''   
     
    10092        '''ANSWER:'''  
    10193    Mapper classes are all in shirako core. 
    102     Look at everything that derives from IPolicy. 
     94    Look at everything that derives from ''IPolicy''. 
    10395    The identifier "Mapper" has disappeared from the code. 
    10496 
     
    108100        '''ANSWER:'''  
    109101     Yes this is easy: see the documentation. 
    110 '''Q4a)''' Can the configuration/parameters of ORCA handler describe wireless 
    111     sensor network slicing and resources? How to reuse the current 
    112     KanseiGenie implementation of “slice manager”, “researcher portal”? As a 
    113     driver? 
    114 '''Answer:'''  
    115       
    116     We have some ideas about how other systems can integrate with orca but 
    117     before we can talk bout this we need some more information from you. 
    118     Can you describe what the different components of your system do? How 
    119     do they interact and in what language are they implemented? 
    120  
    121102 
    122103'''5.'''       
    123     Does the handler or nodeAgent/adapter act as the slice manager in 
    124     Kansei architecture? Is it necessary for Kansei to write wrapper /or 
    125     simply implement ORCA-compatible drivers to facilitate function call 
    126     between handler and slice manager? Can we implement some specific drivers 
    127     that expose their API to the standardized handler? 
     104    Does the handler or nodeAgent/adapter act as the slice manager in Kansei architecture? Is it necessary for Kansei to write wrapper /or simply implement ORCA-compatible drivers to facilitate function call between handler and slice manager? Can we implement some specific drivers that expose their API to the standardized handler? 
    128105 
    129106''' Answer:'''  
    130     There are examples of handlers and drivers under drivers/.  See the 
    131     answer to the previous question. 
     107    There are examples of handlers and drivers under ''drivers/''.  See the answer to the previous question. 
    132108     
    133109'''6.'''  
    134     How to implement plugin polices at the three actors? How to use 
    135     or implement the Plug-in extension modules in ORCA core to respond to 
    136     resource request events? How to implement policy plugins for resource 
    137     allocation and management at broker and site authority ? And resource 
    138     request management at service manager?   
     110    How to implement plugin polices at the three actors? How to use or implement the Plug-in extension modules in ORCA core to respond to resource request events? How to implement policy plugins for resource allocation and management at broker and site authority ? And resource request management at service manager?   
    139111     
    140112'''Answer:''' 
    141113 
    142     The orca code base contains a number of policy examples. Starts from 
    143     the IPolicy interface and follow its hierarchy. Take a look at the 
    144     test/unit project for examples of testing a combination of 3 actor 
    145     policies. orca/policy/* contains most of our broker and service 
    146     manager policies. Site-level policy components can be found under 
    147     cod/src/main/java/orca/cod/control 
     114    The orca code base contains a number of policy examples. Starts from the IPolicy interface and follow its hierarchy. Take a look at the test/unit project for examples of testing a combination of 3 actor policies. orca/policy/* contains most of our broker and service manager policies. Site-level policy components can be found under cod/src/main/java/orca/cod/control 
    148115 
    149116'''7.'''       
     
    152119'''Answer:''' 
    153120 
    154    Each Orca container provides a set of management API. The web portal 
    155    interacts with the Orca container using the management API. The 
    156    design of the management API provides for multiple ways to invoke them: 
     121   Each Orca container provides a set of management API. The web portal interacts with the Orca container using the management API. The design of the management API provides for multiple ways to invoke them: 
    157122     - local function calls when running in the same JVM 
    158123     - SOAL when calling from another JVM. 
    159124 
    160    At this point the local interface is fully supported, but the SOAP 
    161    interface is rudimentary and not functional.  
     125   At this point the local interface is fully supported, but the SOAP interface is rudimentary and not functional.  
    162126 
    163    To get familiar with the management API take a look at the 
    164    ManagerObject class and its hierarchy.  
     127   To get familiar with the management API take a look at the ManagerObject class and its hierarchy.  
    165128 
    166    The following projects implement the build of the management 
    167    functionality: 
     129   The following projects implement the build of the management functionality: 
    168130      core/manage 
    169131      manage/standard