8:13 a.m.
After successfully attaching a disk and verifying its status is in 'ok',
I've tried:
api.vms.get(VM0_NAME).disks.get(DISK1_NAME).set_active(True)
But it doesn't really activate it. What's the correct way to activate it?
(It works well via the UI).
TIA,
Y.
8:23 a.m.
On 25 July 2016 at 16:13, Yaniv Kaul <ykaul(a)redhat.com> wrote:
After successfully attaching a disk and verifying its status is in
'ok',
I've tried:
api.vms.get(VM0_NAME).disks.get(DISK1_NAME).set_active(True)
But it doesn't really activate it. What's the correct way to activate it?
(It works well via the UI).
The same approach pretty much works for me:
(v3 sdk vs v4.x engine)
https://code.engineering.redhat.com/gerrit/#/c/79691/1/fabric_ci/do/ovirt...
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
8:26 a.m.
On 25 July 2016 at 16:23, Barak Korren <bkorren(a)redhat.com> wrote:
On 25 July 2016 at 16:13, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> After successfully attaching a disk and verifying its status is in 'ok',
> I've tried:
> api.vms.get(VM0_NAME).disks.get(DISK1_NAME).set_active(True)
>
> But it doesn't really activate it. What's the correct way to activate it?
> (It works well via the UI).
>
The same approach pretty much works for me:
(v3 sdk vs v4.x engine)
https://code.engineering.redhat.com/gerrit/#/c/79691/1/fabric_ci/do/ovirt...
A couple of things to note though:
1. A disk's name is not unique, so not good for looking up by
2. "vm.disks.get(id=foo)" doe not seem to work right ATM as far as
looking at 'disk.active' goes so I used:
"vm.disks.list(id=foo)[0]"
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
8:29 a.m.
What's the VM status when you try to activate the disk?
On Mon, Jul 25, 2016 at 4:23 PM, Barak Korren <bkorren(a)redhat.com> wrote:
On 25 July 2016 at 16:13, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> After successfully attaching a disk and verifying its status is in 'ok',
> I've tried:
> api.vms.get(VM0_NAME).disks.get(DISK1_NAME).set_active(True)
>
> But it doesn't really activate it. What's the correct way to activate it?
> (It works well via the UI).
>
The same approach pretty much works for me:
(v3 sdk vs v4.x engine)
https://code.engineering.redhat.com/gerrit/#/c/79691/1/fabric_ci/do/ovirt...
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
8:36 a.m.
You actually have to run method 'activate()'[1] on VM disk.
So it will look like this:
api.vms.get(VM0_NAME).disks.get(DISK1_NAME).activate()
[1]
https://gerrit.ovirt.org/gitweb?p=ovirt-engine-sdk.git;a=blob;f=src/ovirt...
On 07/25/2016 03:13 PM, Yaniv Kaul wrote:
After successfully attaching a disk and verifying its status is in
'ok',
I've tried:
api.vms.get(VM0_NAME).disks.get(DISK1_NAME).set_active(True)
But it doesn't really activate it. What's the correct way to activate it?
(It works well via the UI).
TIA,
Y.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:53 a.m.
On Mon, Jul 25, 2016 at 4:36 PM, Ondra Machacek <omachace(a)redhat.com> wrote:
You actually have to run method 'activate()'[1] on VM disk.
So it will look like this:
api.vms.get(VM0_NAME).disks.get(DISK1_NAME).activate()
[1]
https://gerrit.ovirt.org/gitweb?p=ovirt-engine-sdk.git;a=blob;f=src/ovirt...
Thanks.
I've ended up adding 'active=True' to the disk when adding it - and it
seems to do the same. Is that correct?
Y.
On 07/25/2016 03:13 PM, Yaniv Kaul wrote:
> After successfully attaching a disk and verifying its status is in 'ok',
> I've tried:
> api.vms.get(VM0_NAME).disks.get(DISK1_NAME).set_active(True)
>
> But it doesn't really activate it. What's the correct way to activate it?
> (It works well via the UI).
>
> TIA,
> Y.
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
6:28 a.m.
On 07/26/2016 08:53 AM, Yaniv Kaul wrote:
On Mon, Jul 25, 2016 at 4:36 PM, Ondra Machacek <omachace(a)redhat.com
<mailto:omachace@redhat.com>> wrote:
You actually have to run method 'activate()'[1] on VM disk.
So it will look like this:
api.vms.get(VM0_NAME).disks.get(DISK1_NAME).activate()
[1]
https://gerrit.ovirt.org/gitweb?p=ovirt-engine-sdk.git;a=blob;f=src/ovirt...
Thanks.
I've ended up adding 'active=True' to the disk when adding it - and it
seems to do the same. Is that correct?
Y.
Yes, it is correct.
Note also that in general setting a property of an object in the SDK
doesn't do anything, you need to call the "update" method:
disk = api.vms.get(VM0_NAME).disks.get(DISK1_NAME)
disk.set_active(true)
disk.update()
On 07/25/2016 03:13 PM, Yaniv Kaul wrote:
After successfully attaching a disk and verifying its status is
in 'ok',
I've tried:
api.vms.get(VM0_NAME).disks.get(DISK1_NAME).set_active(True)
But it doesn't really activate it. What's the correct way to
activate it?
(It works well via the UI).
TIA,
Y.
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
2838
days inactive
2839
days old
6 comments
5 participants
participants (5)
-
Barak Korren -
Elad Ben Aharon -
Juan Hernández -
Ondra Machacek -
Yaniv Kaul