Changes between Version 19 and Version 20 of releases/Camano-3.0

Show
Ignore:
Timestamp:
12/22/10 10:17:38 (9 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • releases/Camano-3.0

    v19 v20  
    88   See #187 first, then look at  #182, #183, #184, #185, #186 
    99 
    10  * How can we pass port configuration from the switches into the log from failure of operations? 
     10* How can we pass port configuration from the switches into the log from failure of operations? 
    1111   * if you specify a task property as 'shirako.save.XXXX' (Config class) will be passed back (with stripped 'shirako.save') and the property will be attached to the unit for which the handler was executed (shirako.save.blah -> blah) however failed units aren't sent back to e.g. SM. Logging it in the handler is possible. Logging is probably easiest. Also possible to attach it to the reservation and pass it as a property. There is also a notice mechanism that can be used to pass it back to the reservation.  
    1212   * Problem is related to using Ant as the basis for handler scripts. To look at changing to using Jython as the engine, look at Config class. One issue may be checking progress of the operation. Jeff has details on this (added for one of the demos). Some code in AntConfig class may be generically useful and would have to be pushed up. Implement a generic config, look at javax.scripting and BSF (bean-scripting framework). 
    1313 
    14  * Do we still an interactor deadlock problem? 
     14* Do we still an interactor deadlock problem? 
    1515    * Yes. Needs fixing. Every inter-actor call holds big lock. Across multiple containers it is possible for call and response to be in different threads, which may cause deadlock. The solution is when calls are made across actors, they are not done while holding the big lock. The issue is handling exceptions. 
    1616 
     
    1818   * There is a concept of 'deferral'. If you don't have enough resources, you can send back partial resources, which is why this makes sense. We may need to add a property on the control for the resource pool, a new property 'non-deferrable' may need to be added. There is a binary predicate that determines whether a redeem is possible (yes redeem/no redeem/no redeem and release). The children reservation get tickets and they need to be cleaned up if a parent fails on redeem. This needs to be a transaction. Predecessor reservations need to be closed, however we may need to wait until they are done redeeming, as closing in redeeming state is difficult.  
    1919 
    20  * Need to re-enable ticket validaation #181 
     20* Need to re-enable ticket validation #181 
    2121 
    22  * Site consolidation:  
     22* Site consolidation (is it needed?):  
    2323   * Can/Should we get rid of RENCI-net UNC-net authorities? So we can have a single authority controlling EX3200? With NDL exporting multiple resource types we can now do the consolidation. 
    2424   * We could modify configuration processor to create resource pools based on NDL input to avoid repeating delegation in config.xml (and NDL). To be discussed. 
     
    2727 
    2828 * Reuse controller code between XMLRPC and ID controllers (Avoid copying).  
     29 
     30 * Old bugs:  
     31   * Adding resource pools from GUI/extending management API #120  
     32   * Referencing actors by GUIDs instead of names #121 
    2933 
    3034== !ToDos ==