Changes between Version 26 and Version 27 of RefactorClient


Ignore:
Timestamp:
09/26/06 15:28:03 (15 years ago)
Author:
desai
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RefactorClient

    v26 v27  
    88Ticket #73 describes some aspects of this issue. 
    99 
    10 == Desai's 4-Step Plan == 
    11  1. create a module Bcfg2.Client.Tool.!BaseTool that defines an API for all tools (things like Bcfg2.Client.Tool.RPM and Bcfg2.Client.Tool.SMF, etc) 
    12  1. build a set of error types that can be raised during tool instantiation and operation 
     10== NLD's 4-Step Plan == 
     11 1. create classes in Bcfg2.Client.Tools that defines an API for all tools (Implemented as Bcfg2.Client.Tools.Tool, Bcfg2.Client.Tools.PkgTool, and Bcfg2.Client.SvcTool). All Tools will subclass one of these (Bcfg2.Client.Tools.RPM, Bcfg2.Client.Tools.SMF, etc) [DONE] 
     12 1. build a set of error types that can be raised during tool instantiation and operation [DONE] 
     13 1. Implement a tool class for each underlying tool. (see table below for status) 
    1314 1. modify the Bcfg2.Client.Frame code to figure out what methods to call tools for entry verification, installation and removal. 
    1415 1. is things like schema updates and metadata code updates 
    15 Desai might try to hack up a baseline for the !BaseTool class soon. 
    1616 
    1717== Implementation Status ==