Bcfg2 Client Code Refactoring

This branch is for work in decomposing the platform-specific client modules into service/packaging system-specific modules; the platform-specific modules will then just import the service/packaging system-specific modules they require (e.g. Redhat.py would import rpm.py and chkconfig.py, all the platforms will import encap.py, etc.)

A mailing list thread with more discussion of this is here:

• ​http://www-unix.mcs.anl.gov/web-mail-archive/lists/bcfg-dev/2006/07/msg00084.html

Ticket #73 describes some aspects of this issue.

NLD's 4-Step Plan

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]
2. build a set of error types that can be raised during tool instantiation and operation [DONE]
3. Implement a tool class for each underlying tool. (see table below for status)
4. modify the Bcfg2.Client.Frame code to figure out what methods to call tools for entry verification, installation and removal.
5. is things like schema updates and metadata code updates

Implementation Status

This work is happening at:

https://svn.mcs.anl.gov/repos/bcfg/branches/refactor/client

Bcfg2.Client.Frame is completely finished. It redirects calls to lower-level tool modules. It also provides a unified view across all tools.

Tool	Status	Who	Tested?
RPM	done	NLD	No
POSIX	done	NLD	Yes
Encap	done	DC	No
SYSV	done	NLD	No
Pkg-get (Blastwave)	done	NLD	No
APT	done	NLD	Yes
ChkConfig?	done	NLD	No
SMF	done	NLD	No
PostInstall?	done	NLD	Yes
DebInit?	done	NLD	Yes

All currently supported tools are now implemented.
To Be Added

BFF (Best Friend Forever?)	DC
Daemontools	DC
Yum	HM
SolInit?	???
Launchd	TL
Emerge	???

(V == Verify/I == Install/E == Extra detection/R == Removal)

==Test Plan==

1. Get verification working, and verify results against the old client (done on debian, so we know that

Design Notes

Bcfg2.Client.Frame redirects calls to underlying tools. Its methods are:

• Inventory - Compare client state to configuration specification
• Install - Install wrong entries (sparsely, if specified)
• FindExtra - Locate extra entries using tool-specific heuristics
• Query - get user input of which entries should be modified
• Remove - remove specified extra entries

Tool methods:

• Verify<entry.tag> - verify entry state. Must return True/False?
• Install<entry.tag> - install entry. Must return True/False?
• Install (optional) - bulk install method for entries
• FindExtra - locate extra entries

Writing a Client Tool Module

See WritingClientToolDrivers for details.