In 4.0 XML-RPC won't be available and vdscli XML-RPC calls are incompatible with JSON-RPC vdscli calls. (see Nir's comment to https://gerrit.ovirt.org/#/c/41965/ )
Blocked on missing jsonrpc client API in VDSM. Please ping me when the cli will be ready.
We are planning to have jsonrpcvdscli in 3.6 so hopefully we can give you documentation and the client code. Will let you know once the patches are merged.
(In reply to Piotr Kliczewski from comment #2) > We are planning to have jsonrpcvdscli in 3.6 so hopefully we can give you > documentation and the client code. Will let you know once the patches are > merged. I don't think that a library / protocol switching is something that should be allowed in 3.6 at this stage.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
(In reply to Sandro Bonazzola from comment #1) > Blocked on missing jsonrpc client API in VDSM. > Please ping me when the cli will be ready. Should probably have a bug on it, which this bug will depend on.
Please open a bug on infra, if there isn't one and block this RFE, so we will know when to start working on this one.
Looking at http://lists.ovirt.org/pipermail/devel/2015-October/011479.html the referenced patch: https://gerrit.ovirt.org/45789 has been merged on master for 4.0, so this shouldn't be blocked anymore. Piotr, can you provide documentation on how to move from vdscli to jsonrpcvdscli?
Sure, will provide wiki page with it.
Restoring needinfo until info is provided.
Please see [1] wiki page which describe how to migrate from one module to the other. Please not that there is small bug fixed by [2]. [1] http://www.ovirt.org/Migration_from_vdscli_to_jsonrpcvdscli [2] https://gerrit.ovirt.org/#/c/48609
New url: http://www.ovirt.org/uncategorized/migration-from-vdscli-to-jsonrpcvdscli/
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Verified on ovirt-hosted-engine-setup-2.0.0.2-1.el7ev.noarch Deployment via appliance: 1) Deploy on NFS(include deployment of the additional host) 2) Deploy on ISCSI(include deployment of the additional host) 3) Deploy on glusterfs(include deployment of the additional host) Deployment via PXE: 1) Deploy on NFS(include deployment of the additional host)
oVirt 4.0.0 has been released, closing current release.