Changes between Version 3 and Version 4 of releases/Camano-3.0

Show
Ignore:
Timestamp:
11/22/10 18:10:42 (8 years ago)
Author:
ibaldin (IP: 152.54.6.136)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • releases/Camano-3.0

    v3 v4  
    88   See  #182, #183, #184, #185 
    99 
     10 * How can we pass port configuration from the switches into the log from failure of operations? 
     11   * 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.  
     12 * Do we still an interactor deadlock problem? 
     13    * 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. 
     14 
     15 * Need to re-enable ticket validaation #181 
    1016== Wishlist  == 
    11  
    12  * #181 - ticket validation 
    1317 
    1418 * Bugs