[wip] actions to replace polishers

[bernard357]

early work has been engaged to move away from existing 'polishers', and to establish solid fondations for future extensions of plumbery:

• keep external compatibility with blueprints and facilities, e.g., 'build cluster @na9'
• allow for non-Dimension Data facilities, e.g., AWS (= no domain: nor ethernet: primitive)
• new file action.py to define PlumberyAction and PlumberyActionLoader
• new file test_action.py of course
• new directory plumbery/actions to host all actions that plumbery can handle
• early implementation in engine.py and in facility.py

each existing polisher will have to be transformed to an action. because of semantic changes it is not an obvious task. during the transition is may happen that some functions invoke both polishers and actions

on the long run, the goal is to turn a big part of code in engine.py and in facility.py into separate manageable actions, e.g., actions/start.py, actions/stop.py, etc

since the new interface described in plumbery/actions.py will be very structuring, you are invited to have a look and to provide feed-back

[bernard357]

plumbery 1.0.2 has early implementation of actions