When there is the attempt to enhance/change the current API, I would ask
you to consider to think also about the vdsClient use case.
I haven't read anything regarding that so far and therefore I just want
you to think about it as well.
My expectation is that the vdsClient will continue to use the RPC
interfaces, however since it is part of the VDSM project I think it
would be a good idea if there is a way for both vdsmd and vdsClient to
share constants used for the API.
That in turn also should simplify the maintenance of vdsClient.
Currently I see the constants used by both being defined on both sides
and I am pretty sure that this could be improved.
See this as just a thought on the whole redesign talk, but I would like
to see this kind of use cases to be covered. :-)
Vinzenz Feenstra | Senior Software Engineer
RedHat Engineering Virtualization R & D
Phone: +420 532 294 625
IRC: vfeenstr or evilissimo
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
vdsm-devel mailing list