Re: [ovirt-users] ovirt 4.2 vdsclient
Hi,
The command is `vdsm-client Task getInfo taskID=`
You can see available arguments in JSON format using `vdsm-client Task
getInfo -h` command.
On Tue, Feb 6, 2018 at 10:36 AM, Alex K <rightkickt...@gmail.com> wrote:
> Hi Benny,
>
> I was trying to do it with vdsm-client without success.
>
> vdsm-client Task -h
> usage: vdsm-client Task [-h] method [arg=value] ...
>
> optional arguments:
> -h, --help show this help message and exit
>
> Task methods:
> method [arg=value]
> getInfo Get information about a Task.
> getStatus Get Task status information.
> revertRollback a Task to restore the previous system state.
> clear Discard information about a finished Task.
> stop Stop a currently running Task.
> [root@v0 common]# vdsm-client Task getInfo
> vdsm-client: Command Task.getInfo with args {} failed:
> (code=-32603, message=Internal JSON-RPC error: {'reason': '__init__()
> takes exactly 2 arguments (1 given)'})
> [root@v0 common]# vdsm-client Task getStatus
> vdsm-client: Command Task.getStatus with args {} failed:
> (code=-32603, message=Internal JSON-RPC error: {'reason': '__init__()
> takes exactly 2 arguments (1 given)'})
>
> What other arguments does this expect. When using Host namespace I am able
> to run the available options.
>
> Thanx,
> Alex
>
>
> On Tue, Feb 6, 2018 at 10:24 AM, Benny Zlotnik <bzlot...@redhat.com>
> wrote:
>
>> It was replaced by vdsm-client[1]
>>
>> [1] - https://www.ovirt.org/develop/developer-guide/vdsm/vdsm-client/
>>
>> On Tue, Feb 6, 2018 at 10:17 AM, Alex K <rightkickt...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I have a stuck snapshot removal from a VM which is blocking the VM to
>>> start.
>>> In ovirt 4.1 I was able to cancel the stuck task by running within SPM
>>> host:
>>>
>>> vdsClient -s 0 getAllTasksStatuses
>>> vdsClient -s 0 stopTask
>>>
>>> Is there a similar way to do at ovirt 4.2?
>>>
>>> Thanx,
>>> Alex
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
--
IRIT GOIHMAN
SOFTWARE ENGINEER
EMEA VIRTUALIZATION R
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.linkedin.com/company/red-hat> Red Hat
<https://www.facebook.com/RedHatInc>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Suggestions on changing hosts' network
On Mon, Jan 8, 2018 at 6:08 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:
> On Mon, Jan 8, 2018 at 12:57 PM, Edward Haas <eh...@redhat.com> wrote:
>
>>
>>>>
>>>
>>> hello,
>>> any update on how to give JSON representation (or other way) to use
>>> vdsm-client and change ip/gateway of ovirt-ng node?
>>> Thanks
>>>
>>
>> How to use vdsm-client in general: Just check its man page.
>> You will need to fill up the existing management network details in the
>> json format, replacing just the IP address.
>> The main concern here is, that if you missed something, it may be removed.
>> You should follow https://access.redhat.com/solutions/168983 for full
>> details.
>>
>> I would suggest using a different approach, although I have not tested it
>> myself:
>> Edit the persisted relevant configuration files:
>> /var/lib/vdsm/persistence/netconf
>> (Change the IP there, without touching the other stuff)
>> 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.
>> The risk here is that the config will not successfully get applied, so
>> make sure you save the previous version.
>>
>> Thanks,
>> Edy.
>>
>>
> Actually I see some misalignment between what I see in man page, what I
> get with "-h" option and real command usage.
> Eg in oVirt 4.1.7 (vdsm-client-4.19.37-1.el7.centos.noarch):
>
> man vdsm-client
>
> "
>Invoking commands with complex parameters
>For invoking commands with complex or many arguments, you can read
> a JSON dictionary from a file:
>
>vdsm-client Lease info -f lease.json
>
>where lease.json file content is:
>
>{
>"lease": {
>"sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
>"lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
>}
>}
> "
>
> But actually if I create a json file and execute
>
> [root@ovirtng4101 ~]# vdsm-client Host setupNetworks -f network.json
>
> I get:
>
> usage: vdsm-client [-h] [-a HOST] [-p PORT] [--unsecure] [--insecure]
>[--timeout TIMEOUT] [-f FILE]
>namespace method [arg=value] ...
> vdsm-client: error: unrecognized arguments: -f
>
> Please try running:
# vdsm-client -f network.json Host setupNetworks
There is an error in the man page, I will fix it.
I have to try it in 4.1.8 if solved
>
> The workaround to change in place the file (in my case ipaddr and gateway
> fileds): /var/lib/vdsm/persistence/netconf.1515365150707441369/
> nets/ovirtmgmt
> and then shutdown/power on seems to work ok instead. I can reinstall the
> host and the change remains persistent across reboots
>
> 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.
>
> 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
>
> Gianluca
>
> PS: ok also for the "not officially supported." advise. This is only a
> test where two hosts are to be moved from datacenter 1 to datacenter 2...
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
--
IRIT GOIHMAN
SOFTWARE ENGINEER
EMEA VIRTUALIZATION R
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.linkedin.com/company/red-hat> Red Hat
<https://www.facebook.com/RedHatInc>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] OVS DPDK Performance
Hi Fernando, On Mon, Nov 27, 2017 at 9:25 PM, FERNANDO FREDIANI < fernando.fredi...@upx.com> wrote: > Hello > > As some may have seen recently OVS DPDK has been introduced to oVirt ( > https://ovirt.org/blog/2017/09/ovs-dpdk/). This is very interesting > feature which can make a huge performance difference in terms of network > performance. > > Just wanted to ask if anyone has tested it in any environment and made any > comparison, specially for packet forward (e.g: running Virtual Routers or > Virtual Firewalls with virtio) or packet dropping as well. > You can see Intel OVS DPDK performance results compared to OVS native in https://download.01.org/packet-processing/ONPS2.1/Intel_ONP_Release_2.1_Performance_Test_Report_Rev1.0.pdf Performance results of OVS DPDK in oVirt setup will be published soon. > > One doubt I have and if someone could clarify is: Should I enable DPDK in > the Host any traffic forwarded to any VMs will automatically benefit from > this performance gain of DPDK or there additional steps that need to be put > in place inside the VM when sharing a physical Network Interface ? > Enabling DPDK is not enough. Since it's tightly coupled to system hardware a few steps are needed in order to achieve good performance results. For example: disabling interrupts, enabling hugepages, isolating CPU cores, allocating them to PMD threads and pinning vcpus. More information can be found here: http://docs.openvswitch.org/en/latest/intro/install/dpdk/ http://dpdk.org/doc/guides-16.04/linux_gsg/nic_perf_intel_platform.html > > > Thanks > Fernando > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- IRIT GOIHMAN SOFTWARE ENGINEER EMEA VIRTUALIZATION R Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] virsh list
Hi, Please use only the -r option. You shouldn't be making changes outside ovirt-engine and vdsm. Thanks, On Sat, Apr 15, 2017 at 11:00 AM, Luca 'remix_tj' Lorenzetto < lorenzetto.l...@gmail.com> wrote: > Depends on what you need to do. If you only want to se vms, add -r to have > readonly access. > > Luca > > Il 15 apr 2017 12:58 AM, "Konstantin Raskoshnyi" <konra...@gmail.com> ha > scritto: > > Hi guys > > I'm trying to run virsh list (or any other virsh commands) > > virsh list > Please enter your authentication name: admin > Please enter your password: > error: failed to connect to the hypervisor > error: authentication failed: authentication failed > > But I have no clue about login:password ovirt uses. > I tried admin password, also tried to create new account with saslpasswd2 > > Which didn't work to. > > Any solutions? > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > > _______ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- IRIT GOIHMAN SOFTWARE ENGINEER EMEA VIRTUALIZATION R Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] vdsClient is removed and replaced by vdsm-client
Hi All,
vdsClient will be removed from master branch today.
It is using XMLRPC protocol which has been deprecated and replaced by
JSON-RPC.
A new client for vdsm was introduced in 4.1: vdsm-client.
This is a simple client that uses JSON-RPC protocol which was introduced in
ovirt 3.5.
The client is not aware of the available methods and parameters, and you
should consult
the schema [1] in order to construct the desired command.
Future version should parse the schema and provide online help.
If you're using vdsClient, we will be happy to assist you in migrating to
the new vdsm client.
*vdsm-client usage:*
vdsm-client [-h] [-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]
[-f FILE] namespace method [name=value [name=value] ...]
Invoking simple methods:
# vdsm-client Host getVMList
['b3f6fa00-b315-4ad4-8108-f73da817b5c5']
For invoking methods with many or complex parameters, you can read
the parameters from a JSON format file:
# vdsm-client Lease info -f lease.json
where lease.json file content is:
{
"lease": {
"sd_id": "75ab40e3-06b1-4a54-a825-2df7a40b93b2",
"lease_id": "b3f6fa00-b315-4ad4-8108-f73da817b5c5"
}
}
It is also possible to read parameters from standard input, creating
complex parameters interactively:
# cat <https://github.com/oVirt/vdsm/blob/master/lib/api/vdsm-api.yml
--
Irit Goihman
Software Engineer
Red Hat Israel Ltd.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
