[vdsm] python vfs

2012-10-15 Thread Peter V. Saveliev
as a sample. [1] slides: http://peet.spb.ru/pyvfs.pdf (53kB) [2] the code on github: https://github.com/svinota/pyvfs -- Peter V. Saveliev ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

[vdsm] new API verb: getVersionInfo()

2012-10-17 Thread Peter V. Saveliev
not support it. But to be able to use it in RHEV-3.2, we should already have it in 3.1. Even if we will not use it yet, the future usecases are pretty straightforward. So pls comment it: http://gerrit.ovirt.org/#/c/8431/ -- Peter V. Saveliev

Re: [vdsm] new API verb: getVersionInfo()

2012-10-18 Thread Peter V. Saveliev
18.10.2012 18:03, Saggi Mizrahi kirjoitti: currently getVdsCaps() does a lot of unrelated things most of them have no relation to capabilites. This was done because of HTTP overhead. Instead of calling multiple commands we will call one that does everything. skip / Can I please make a small

Re: [vdsm] new API verb: getVersionInfo()

2012-10-18 Thread Peter V. Saveliev
… Just to be clear: yes, I think, that getVdsCapabilities() can and should be optimized, but as well it has quite different meaning for different purposes. And what about capabilities «bag» — its format also can be a subject of a change (e.g. long int bitmask ⇒ list of literals), but the version

Re: [vdsm] new API verb: getVersionInfo()

2012-10-21 Thread Peter V. Saveliev
21.10.2012 09:23, Dan Kenigsberg kirjoitti: skip / We should decide NOW on the format of the capabilities «bag», and never change it. Testing for a capability is much more reliable than checking a version, and remembering which version had which capability. Dan. Ok, so what will we decide?

Re: [vdsm] a migration issue

2013-02-12 Thread Peter V. Saveliev
12.02.2013 11:48, Michal Skrivanek kirjoitti: On 12 Feb 2013, at 09:53, Dan Kenigsberg dan...@redhat.com wrote: On Mon, Feb 11, 2013 at 03:56:48PM +0100, Peter V. Saveliev wrote: … system: RHEL 6.3 vdsm: ovirt master head Trying to migrate a VM, created from *CLI* , I've got two errors

Re: [vdsm] a migration issue

2013-02-12 Thread Peter V. Saveliev
12.02.2013 09:53, Dan Kenigsberg kirjoitti: On Mon, Feb 11, 2013 at 03:56:48PM +0100, Peter V. Saveliev wrote: … system: RHEL 6.3 vdsm: ovirt master head Trying to migrate a VM, created from *CLI* , I've got two errors (at least) on the target host: 1. the network interface has no «network

Re: [vdsm] a migration issue

2013-02-12 Thread Peter V. Saveliev
from the log also: see attachment -- Peter V. Saveliev Thread-15::DEBUG::2013-02-08 12:43:28,873::BindingXMLRPC::926::vds::(wrapper) client [10.34.63.165]::call vmMigrationCreate with ({'status': 'Up', 'username': 'Unknown', 'macAddr': '00:00:00:00:00:01', 'nicModel ': 'rtl8139,pv

Re: [vdsm] Migration regression on master

2013-05-29 Thread Peter V. Saveliev
line, and domxml, that was used to create the VM at the source host? http://pastebin.test.redhat.com/17 http://pastebin.test.redhat.com/16 -- Peter V. Saveliev ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https

[vdsm] migration progress feature

2013-07-04 Thread Peter V. Saveliev
side logic. Having the separate verb, this can sound weird, but I'm sure that the optimisation worth it. Please, read the patchset [1] and discuss it here. Thanks. [1] http://gerrit.ovirt.org/#/c/15125/ -- Peter V. Saveliev ___ vdsm-devel mailing