<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Jan 8, 2018 at 12:57 PM, Edward Haas <span dir="ltr"><<a href="mailto:ehaas@redhat.com" target="_blank">ehaas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="gmail-h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div class="gmail-m_-3992555549193384320gmail-h5"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
</blockquote></div></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div></div><div class="gmail_extra">hello,</div><div class="gmail_extra">any update on how to give JSON representation (or other way) to use vdsm-client and change ip/gateway of ovirt-ng node?</div><div class="gmail_extra">Thanks</div></div></blockquote><div><br></div></div></div><div>How to use vdsm-client in general: Just check its man page.<br></div><div>You will need to fill up the existing management network details in the json format, replacing just the IP address.<br></div><div>The main concern here is, that if you missed something, it may be removed.<br></div><div></div><div>You should follow <a href="https://access.redhat.com/solutions/168983" target="_blank">https://access.redhat.com/<wbr>solutions/168983</a> for full details.<br><br></div><div>I would suggest using a different approach, although I have not tested it myself:<br></div><div>Edit the persisted relevant configuration files: /var/lib/vdsm/persistence/<wbr>netconf<br></div><div>(Change the IP there, without touching the other stuff)<br></div><div>Then, reboot the host.. It should identify that the existing config is not in sync with the persisted one and a reconfig will be issued automatically.<br></div><div>The risk here is that the config will not successfully get applied, so make sure you save the previous version.<br></div><div></div><div><br></div><div>Thanks,<br></div><div>Edy.<br></div><span class="gmail-"><div><br></div></span></div></div></div></blockquote><div><br></div><div>Actually I see some misalignment between what I see in man page, what I get with "-h" option and real command usage.</div><div>Eg in oVirt 4.1.7 (vdsm-client-4.19.37-1.el7.centos.noarch):</div><div><br></div><div>man vdsm-client<br></div><div><br></div><div>"</div><div><div> Invoking commands with complex parameters</div><div> For invoking commands with complex or many arguments, you can read a JSON dictionary from a file:</div><div><br></div><div> vdsm-client Lease info -f lease.json</div><div><br></div><div> where lease.json file content is:</div><div><br></div><div> {</div><div> "lease": {</div><div> "sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",</div><div> "lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"</div><div> }</div><div> }</div></div><div>"</div><div><br></div><div>But actually if I create a json file and execute</div><div><br></div><div>[root@ovirtng4101 ~]# vdsm-client Host setupNetworks -f network.json<br></div><div><br></div><div>I get:</div><div><br></div><div><div>usage: vdsm-client [-h] [-a HOST] [-p PORT] [--unsecure] [--insecure]</div><div> [--timeout TIMEOUT] [-f FILE]</div><div> namespace method [arg=value] ...</div></div><div>vdsm-client: error: unrecognized arguments: -f<br></div><div><br></div><div>I have to try it in 4.1.8 if solved</div><div><br></div><div>The workaround to change in place the file (in my case ipaddr and gateway fileds): /var/lib/vdsm/persistence/netconf.1515365150707441369/nets/ovirtmgmt</div><div>and then shutdown/power on seems to work ok instead. I can reinstall the host and the change remains persistent across reboots</div><div><br></div><div>Thanks for the pointer for RHEV doc, because I didn't find it at first glance and I have to do the same for a RHEV eval too; but it seems the problem is present also there with RHV-H installed in December (nodectl info reports that current layer is rhvh-4.1-0.20171101.0+1; probably the problem has been already solved, I have to check). I can give more details on this off-list if you like as this doesn't directly relate with oVirt.</div><div><br></div><div>Thanks in the mean time for the persistence file method that I think/hope will work for RHV-H too if I don't update the image</div><div><br></div><div>Gianluca</div><div><br></div><div>PS: ok also for the "<span style="font-size:12.8px">not officially supported." advise. This is only a test where two hosts are to be moved from datacenter 1 to datacenter 2...</span></div><div><span style="font-size:12.8px"> </span></div></div></div></div>