Description of problem: Currently the configuration backends can only be used through python by using the appropriate classes. A dbus backend should be introduced which exports the classes through a dbus api.
To not interfere with the existing code, a safe approach is to create a standalone daemon. The daemon can take any class, introspects it, instanciates and publishes it. In our case we can feed the config classes to the daemon, to get them published. Besides exporting the required update() and retrieve() methods, the daemon should also export the sometimes available configure_* methods, which allow a more high level configuration. Besides taking care of exporting the necessary methods, it must also be investigated if some kind of authorization needs to be done by the existing dbus authorization mechanisms.
Waiting on an upstream repo to put this in. Sources and testing instructions are available at: http://github.com/evol262/node-cockpit I tested by copying the ovirt-node python bits to a fresh VM, installed the dependencies (listed in TESTING -- you should be able to import ovirt.node.config.defaults without any errors), then installed the ovirt-node-dbus-backend RPM. I'll add an external tracker when the repo is up
Please move this bug to MODIFIED once the repository on gerrit is available and the patches merged.
That was the plan, and normal workflow.