Changes between Version 54 and Version 55 of releases/Camano-3.0

Show
Ignore:
Timestamp:
04/21/11 00:00:37 (8 years ago)
Author:
ibaldin (IP: 108.65.61.102)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • releases/Camano-3.0

    v54 v55  
    2828 * Re-deploying site requires redeploying broker  
    2929   * When you redeploy - don't wipe the state recovery file: this will preserve existing reservations. HOWEVER: there is a bug now that prevents expanding the packages if the state recovery lock file is present. Aydan will fix #145. Every actor is designed to work like that. If a broker is blown away, service managers will continue working until they need extend. Basically we need to fix recovery bugs if there are any but by design, redeploying should be fine. Recovery is most problematic on SM and Authorities. Eucalyptus is made to recover but not well tested. 
    30    * This issue has been resolved 
    31    #187, #182, #183, #184, #185, #186 
     30   * This issue has been resolved #184 
     31   * Related but not critical #187, #182, #183, #185, #186 
    3232 
    3333 * How can we pass port configuration from the switches into the log from failure of operations? 
    3434   * 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.  
    3535   * 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). 
     36   * This issue has been partially addressed through better logging 
    3637 
    3738 * Do we still an interactor deadlock problem?