Hi all, I was working on adding a new verb to vdsm-gluster [1]. But right now the only way i see to test this is by using vdsm-client.I have patched a host running vdsm with my code, but the vdsm-client is not showing the required verb. Is there anything else needed to be done? Eg-vdsm-client --gluster-enabled GlusterVolume globalOptionsList [1] https://gerrit.ovirt.org/#/c/95636/

On Thu, Nov 22, 2018 at 4:05 PM Nir Soffer <nsoffer(a)redhat.com <mailto:nsoffer@redhat.com>> wrote: On Thu, Nov 22, 2018 at 2:06 PM Kaustav Majumder <kmajumde(a)redhat.com <mailto:kmajumde@redhat.com>> wrote: Hi all, I was working on adding a new verb to vdsm-gluster [1]. But right now the only way i see to test this is by using vdsm-client.I have patched a host running vdsm with my code, but the vdsm-client is not showing the required verb. Is there anything else needed to be done? Eg-vdsm-client --gluster-enabled GlusterVolume  globalOptionsList [1] https://gerrit.ovirt.org/#/c/95636/ The yaml looks mostly OK, so I would expect the verb to be found. You probably need to created rpms and install this vdsm to make the new schema available, and then you can test it like this:     vdsm-client --gluster-enabled Namespace -h RPM would be the simplest. During creation there is pickle file created [1] which is used by the client. [1] https://github.com/oVirt/vdsm/blob/master/lib/vdsm/api/schema_to_pickle.py (I'm not sure about --gluster-enabled, never used it) Nir