It has been suggested before to convert vdsm-tool's configurators form classes
to modules and to express their interface using duck typing rather than
inheritance.
I would like to get to it now before any new configurators join.
I would like to know:
1.) If there are any objections to this.
2.) What is the best way to describe the interface for future
implementers. A text file at configurators package __init__?
at the class using the implementations? Are there any examples
for this inside vdsm?
Thanks,
Mooli tayer.
