vdsm-client: Adding a new verb to vdsm
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/ Thanks, Kaustav
On Thu, Nov 22, 2018 at 2:06 PM Kaustav Majumder <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 (I'm not sure about --gluster-enabled, never used it) Nir
On Thu, Nov 22, 2018 at 4:05 PM Nir Soffer <nsoffer@redhat.com> wrote:
On Thu, Nov 22, 2018 at 2:06 PM Kaustav Majumder <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
I've replied to Kaustav yesterday and we've managed to resolve the issue. Forgot to CC on devel though, sorry for confusion. Marcin On 11/22/18 4:14 PM, Piotr Kliczewski wrote:
On Thu, Nov 22, 2018 at 4:05 PM Nir Soffer <nsoffer@redhat.com <mailto:nsoffer@redhat.com>> wrote:
On Thu, Nov 22, 2018 at 2:06 PM Kaustav Majumder <kmajumde@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
participants (4)
-
Kaustav Majumder -
Marcin Sobczyk -
Nir Soffer -
Piotr Kliczewski