Adding to the discussion.

Currently vdsm-xmlrpc rpm is required by vdsm and vdsm-cli rpms. Initially I suggested to have vdsm-jsonrpc required by vdsm-api but it do not seems to be good idea. I think that we need to add that dept to vdsm rpm in the same way as it is for vdsm-xmlrpc. I do not understand why we have decided to split jsonrpc code between two rpms: vdms-api: - vdsmapi-schema.json vdsm-jsonrpc: - BindingJsonRpc - Bridge vdsm-yajsonrpc: - __init__ - betterAsyncore - stomp - stompReactor I understand that we may have schema in api package but do we really need two packages for jsonrpc? Currently we need a package for stomp reactor so I suggest for now to have one json(stomp) rpm and create second for amqp when there will be need for it.