Re: [Users] Cannot connect to VM via browser if engine was not in /etc/hosts
On 06/24/2013 10:37 AM, lof yer wrote: Is 'engine-config -s SSLEnabled=false' or special spice parameter? It should do the trick. 2013/6/24 Itamar Heim ih...@redhat.com mailto:ih...@redhat.com On 06/24/2013 03:10 AM, lofyer wrote: 于 2013/6/24 1:47, Itamar Heim 写道: On 06/06/2013 11:51 AM, lof yer wrote: I connect https://192.168.1.111 and connect to the VM, then the remote-viewer shows up, but failed to show the VM desktop. Is it the https problem? Can I connect to the VM without modify /etc/hosts? _ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/__mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users was this resolved? sounds like a certificate/dns issue? Yes, it's certificate/dns problem. But how can I connect via IP instead of FQDN without https? i guess it depends if you can tell spice client to not validate the ssl certificate. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Password reset of ovirt wiki not working
Am Montag, den 24.06.2013, 00:41 +0200 schrieb Dave Neary: Hi, I did some digging, and it turns out that some time in the last 2 weeks, a change in the PaaS we use has resulted in emails no longer being sent. I've informed the authorities and will come back with more information when I have it. That's a nice info regarding the cause of this problem. - fabian Cheers, Dave. On 06/18/2013 03:06 PM, j.astr...@netbulae.eu wrote: Hi, Nope, tried it about a dozen times with time in between. -- Regards, Jorick Astrego From: Laszlo Hornyak lhorn...@redhat.com To: j astrego j.astr...@netbulae.eu Cc: ovirt-users users@ovirt.org Date: 06/18/2013 13:32 Subject: Re: [Users] Password reset of ovirt wiki not working Hi, Try it again! I get this error page on just any random save in the wiki, but after a retry it usually works. Laszlo - Original Message - From: j astrego j.astr...@netbulae.eu To: ovirt-users users@ovirt.org Sent: Tuesday, June 18, 2013 12:45:14 PM Subject: [Users] Password reset of ovirt wiki not working Hi, Maybe this is not really for this list, but I don't know where else to submit it ;-) I try to request a new password for the Ovirt wiki and get this error: Internal error Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information. -- Kind regards, Jorick Astrego Netbulae B.V. Site: http://www.netbulae.eu http://www.netbulae.eu/ ___ 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Password reset of ovirt wiki not working
Hi, On 06/24/2013 10:16 AM, Fabian Deutsch wrote: Am Montag, den 24.06.2013, 00:41 +0200 schrieb Dave Neary: I did some digging, and it turns out that some time in the last 2 weeks, a change in the PaaS we use has resulted in emails no longer being sent. I've informed the authorities and will come back with more information when I have it. That's a nice info regarding the cause of this problem. More detail: https://fedorahosted.org/ovirt/ticket/60 I'm still hunting, because the bugzilla bug I reference above has been closed, but I still have an issue. Cheers, Dave. -- Dave Neary - Community Action and Impact Open Source and Standards, Red Hat - http://community.redhat.com Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Fedora upgrading from 3.1 to 3.2
sön 2013-06-23 klockan 09:38 +0003 skrev Alex Lourie: Hi Karli I've written up all we know at [1], please try to follow it (if you haven't yet) and let us know how it goes. If anything goes wrong, we will look for the ways to resolve it. Hi Alex! Awesome job, I´m going to test this right away and let you know how it goes. Wish me luck;) /Karli Alex. [1] http://www.ovirt.org/OVirt_3.1_to_3.2_upgrade On Thu, Jun 20, 2013 at 8:05 PM, Alex Lourie alou...@redhat.commailto:alou...@redhat.com wrote: Hi Karli I am reviewing all the actions again, and hopefully will have something documented on Sunday. Alex. On Tue, Jun 18, 2013 at 10:46 AM, Karli Sjöberg karli.sjob...@slu.semailto:karli.sjob...@slu.se wrote: tis 2013-06-18 klockan 10:06 +0300 skrev Moran Goldboim: On 06/17/2013 02:51 PM, Karli Sjöberg wrote: mån 2013-06-17 klockan 10:11 +0003 skrev Alex Lourie: On Fri, Jun 14, 2013 at 12:26 PM, Karli Sjöberg karli.sjob...@slu.semailto:karli.sjob...@slu.se wrote: Hi! Hi Karli, More than two months have passed without any notices or updates on this issue, and looking at the bugreport absolutely nothing has been done since then. What´s confusing me is that the release management for oVirt 3.2 has this clearly printed: MUST: Upgrade from previous release And you all seem too busy with getting the next release out of the door before fixing the current... What gives? Don´t you care about early adopters? I apologise that this issue wasn't taken care of yet. It is clear that the priorities of developers shifted towards work on features in 3.3 release, which feature freeze is happening in about 2 weeks, so you can understand the time pressure they all have. There's no need to be angry about that. It is an open source project and as resources for the development are limited, we're trying to do our best to cover as much issues as possible. This can lead to situations as this issue, which may be left behind for some time. I´m not angry, as I stated before, I´m more confused, and maybe a little disappointed that important(in my opinion) pieces of a projects continuum have been ignored like that. I´m having a hard time understanding the reasoning behind the priorities that have made this issue appear. In my mind, making sure that users of any project are able to follow between minor upgrades is a given, with a schedule like; 1) Feature freeze, 2) Fix release blockers (upgrading being one of them), 3) Release, in that order. Now what´s happening is that you are kind of hoping to drag this out until the problem goes away by itself when you decide it´s time to stop supporting 3.1. That said, the process for upgrading the oVirt 3.1 on Fedora 17 to oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it is taking time to resolve all the issues that come up in the process. If this matter is not extremely urgent, we are currently working on a tool that may make this upgrade easier, albeit, maybe, not completely automatic. On the other hand, if this is a completely and utterly urgent, we may try to guide you through possible manual attempts to perform the upgrade. Mind though, that they weren't thoroughly tested, and not promised to go smoothly or even work, and we may have to think about possible alternative solutions on the go. Straight answer: Am I ever going to be able to upgrade from 3.1 to 3.2? My concern (fear) is about being left behind, abandoned. It makes me feel non-important. Just like any admin, the work put down to make Templates, to set up quotas, create VMPools, a dozen of guests. And then have to export everything (nullifying the idea of Thin Provisioning), redo every Role, reset every permission, quota, and so on, isn´t (in my opinion) viable in the long run for oVirt as a project to demand. That´s why I had the notion that upgrading surely had to be a high priority. Was I wrong about that? upgrade actually was high priority task, but due to lots of platform (fedora 18) changes, it became a huge operation to support it (which comes on top new features/bugs/support etc.). in addition we have noticed that the interest from the community regarding it, is very limited. from where i see i we have couple of options: -if there is enough interest from the community we can give it another go (though i think most of it moved long ago to oVirt 3.2) You certainly have my interest at least;) -we can help individuals by making a migration (3.1-3.2) document on fedora base systems- we'll probably need your assistance on testing side here A document explaining how to upgrade would be completly acceptable for me. I´m not asking for a turnkey command that makes everything for me, I´ve managed to get quite far by myself any way. I would love
Re: [Users] Problems using the PythonSDK
sön 2013-06-23 klockan 20:48 +0300 skrev Itamar Heim:
On 06/05/2013 07:58 AM, Karli Sjöberg wrote:
tis 2013-06-04 klockan 16:32 +0300 skrev Michael Pasternak:
Karli,
On 06/04/2013 04:05 PM, Karli Sjöberg wrote:
Hello everyone!
I´m almost done with Python for now. But the last thing I sitll can´t seem
to get any hang on is how to change the name of a VM´s disk:
please use disk.alias property, name is deprecated and for backward
compatibility only.
It doesn´t matter what property I use, the name doesn´t change any way!
Please read below, you´ll see I even tried defining .alias and .name at
the same time, then update, but still no change. Could you please post
the correct, and working way of doing this, please.
from ovirtsdk.api import API
from ovirtsdk.xml import params
api = API(url='https://${OVIRT}:443 https://storm.slu.se:443',
ca_file='/etc/pki/ovirt-engine/ca.pem', username='admin@internal
mailto:'admin@internal',
password='letmein!')
VM_NAME = 'FedoraTest'
DISK_NAME = '%s_Disk1' % (VM_NAME)
vm = api.vms.get(VM_NAME)
vmdisk = vm.disks.list()[0]
vmdisk.alias = 'foobar'
vmdisk.name = 'foobar'
vmdisk.update()
ovirtsdk.infrastructure.brokers.VMDisk object at 0x25d7ad0
But the name/alias/whatev never changes...
Could you please give me an exact, and working example of how to change
the name of a VM´s disk. This is the last simple thing I would like to
accomplish before sharing a
little something back with y´all(teaser, teaser).
/Karli
sön 2013-05-26 klockan 02:48 -0400 skrev Ilia Meerovich:
Hi,
Lets followhttp://www.ovirt.org/Python-sdk
In [1]: from ovirtsdk.xml import params
In [2]: from ovirtsdk.api import API
In [3]:
In [4]: api = API(***, ***, ***)
In [5]: user_name = ***
In [6]: domain = ***.***.***.redhat.com
In [7]: user_domain = params.Domain(name=domain)
In [8]: user_name = {0}@{1}.format(user_name, domain)
# creating user
In [9]: new_user = params.User(domain=user_domain, user_name=user_name)
# adding user to users resource
In [10]: user = api.users.add(new_user)
# adding role to user
In [11]: user.roles.add(api.roles.get('UserRole'))
Out[11]: ovirtsdk.infrastructure.brokers.UserRole object at 0x30c7590
Thanks
Ilia
- Original Message -
From: Karli Sjöberg karli.sjob...@slu.semailto:karli.sjob...@slu.se
mailto:karli.sjob...@slu.se mailto:karli.sjob...@slu.se
To: Ilia Meerovich imeer...@redhat.commailto:imeer...@redhat.com
mailto:imeer...@redhat.com mailto:imeer...@redhat.com
Cc: Michael Pasternak mpast...@redhat.commailto:mpast...@redhat.com
mailto:mpast...@redhat.com mailto:mpast...@redhat.com, users
users@ovirt.orgmailto:users@ovirt.org mailto:users@ovirt.org
mailto:users@ovirt.org, Elena Dolinin
edoli...@redhat.commailto:edoli...@redhat.com
mailto:edoli...@redhat.com mailto:edoli...@redhat.com
Sent: Friday, May 24, 2013 8:04:43 AM
Subject: Re: [Users] Problems using the PythonSDK
tor 2013-05-23 klockan 08:53 -0400 skrev Ilia Meerovich:
It should be like:
from ovirtsdk.xml import params
from ovirtsdk.api import API
api = API('*', '*', '*')
vm = api.vms.list()[0]
user = api.users.list()[1]
role = api.roles.list()[1]
permit = params.Permission()
permit.set_role(role)
permit.set_vm(vm)
user.permissions.add(permit)
Thank you very much, I´m going to test this out today! Could you also
show me how to first add a user that isn´t in the system yet, please?
- Original Message -
From: Ilia Meerovich imeer...@redhat.commailto:imeer...@redhat.com
mailto:imeer...@redhat.com mailto:imeer...@redhat.com
To: Michael Pasternak mpast...@redhat.commailto:mpast...@redhat.com
mailto:mpast...@redhat.com mailto:mpast...@redhat.com
Cc: users users@ovirt.orgmailto:users@ovirt.org
mailto:users@ovirt.org mailto:users@ovirt.org , Karli Sjöberg
karli.sjob...@slu.semailto:karli.sjob...@slu.se
mailto:karli.sjob...@slu.se mailto:karli.sjob...@slu.se , Elena
Dolinin edoli...@redhat.commailto:edoli...@redhat.com
mailto:edoli...@redhat.com mailto:edoli...@redhat.com
Sent: Thursday, May 23, 2013 3:30:27 PM
Subject: Re: [Users] Problems using the PythonSDK
Hi,
We have several tests like:
Add VM permission to user, that are using ART's
art/rhevm_api/tests_lib/low_level/mla.py addPermitsToUser function.
This is generic function but it shouldn't be hard to prepare SDK code
with the same functionality.
Thanks
Ilia
- Original Message -
From: Michael Pasternak
mpast...@redhat.commailto:mpast...@redhat.com
mailto:mpast...@redhat.com mailto:mpast...@redhat.com
To: Karli Sjöberg karli.sjob...@slu.semailto:karli.sjob...@slu.se
mailto:karli.sjob...@slu.se mailto:karli.sjob...@slu.se , Elena
Dolinin edoli...@redhat.commailto:edoli...@redhat.com
mailto:edoli...@redhat.com mailto:edoli...@redhat.com
Re: [Users] Fedora upgrading from 3.1 to 3.2
On Mon, Jun 24, 2013 at 1:26 PM, Karli Sjöberg karli.sjob...@slu.se wrote: sön 2013-06-23 klockan 09:38 +0003 skrev Alex Lourie: Hi Karli I've written up all we know at [1], please try to follow it (if you haven't yet) and let us know how it goes. If anything goes wrong, we will look for the ways to resolve it. Hi Alex! Awesome job, I´m going to test this right away and let you know how it goes. Wish me luck;) Good luck! May the force be with you. Alex. /Karli Alex. [1] http://www.ovirt.org/OVirt_3.1_to_3.2_upgrade On Thu, Jun 20, 2013 at 8:05 PM, Alex Lourie alou...@redhat.com wrote: Hi Karli I am reviewing all the actions again, and hopefully will have something documented on Sunday. Alex. On Tue, Jun 18, 2013 at 10:46 AM, Karli Sjöberg karli.sjob...@slu.se wrote: tis 2013-06-18 klockan 10:06 +0300 skrev Moran Goldboim: On 06/17/2013 02:51 PM, Karli Sjöberg wrote: mån 2013-06-17 klockan 10:11 +0003 skrev Alex Lourie: On Fri, Jun 14, 2013 at 12:26 PM, Karli Sjöberg karli.sjob...@slu.se wrote: Hi! Hi Karli, More than two months have passed without any notices or updates on this issue, and looking at the bugreport absolutely nothing has been done since then. What´s confusing me is that the release management for oVirt 3.2 has this clearly printed: MUST: Upgrade from previous release And you all seem too busy with getting the next release out of the door before fixing the current... What gives? Don´t you care about early adopters? I apologise that this issue wasn't taken care of yet. It is clear that the priorities of developers shifted towards work on features in 3.3 release, which feature freeze is happening in about 2 weeks, so you can understand the time pressure they all have. There's no need to be angry about that. It is an open source project and as resources for the development are limited, we're trying to do our best to cover as much issues as possible. This can lead to situations as this issue, which may be left behind for some time. I´m not angry, as I stated before, I´m more confused, and maybe a little disappointed that important(in my opinion) pieces of a projects continuum have been ignored like that. I´m having a hard time understanding the reasoning behind the priorities that have made this issue appear. In my mind, making sure that users of any project are able to follow between minor upgrades is a given, with a schedule like; 1) Feature freeze, 2) Fix release blockers (upgrading being one of them), 3) Release, in that order. Now what´s happening is that you are kind of hoping to drag this out until the problem goes away by itself when you decide it´s time to stop supporting 3.1. That said, the process for upgrading the oVirt 3.1 on Fedora 17 to oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it is taking time to resolve all the issues that come up in the process. If this matter is not extremely urgent, we are currently working on a tool that may make this upgrade easier, albeit, maybe, not completely automatic. On the other hand, if this is a completely and utterly urgent, we may try to guide you through possible manual attempts to perform the upgrade. Mind though, that they weren't thoroughly tested, and not promised to go smoothly or even work, and we may have to think about possible alternative solutions on the go. Straight answer: Am I ever going to be able to upgrade from 3.1 to 3.2? My concern (fear) is about being left behind, abandoned. It makes me feel non-important. Just like any admin, the work put down to make Templates, to set up quotas, create VMPools, a dozen of guests. And then have to export everything (nullifying the idea of Thin Provisioning), redo every Role, reset every permission, quota, and so on, isn´t (in my opinion) viable in the long run for oVirt as a project to demand. That´s why I had the notion that upgrading surely had to be a high priority. Was I wrong about that? upgrade actually was high priority task, but due to lots of platform (fedora 18) changes, it became a huge operation to support it (which comes on top new features/bugs/support etc.). in addition we have noticed that the interest from the community regarding it, is very limited. from where i see i we have couple of options: -if there is enough interest from the community we can give it another go (though i think most of it moved long ago to oVirt 3.2) You certainly have my interest at least;) -we can help individuals by making a migration (3.1-3.2) document on fedora base systems- we'll probably need your assistance on testing side here A
Re: [Users] Cannot connect to VM via browser if engine was not in /etc/hosts
Hi, So you're connecting via User Portal but then it doesn't work? If it doesn't, either you hit a bug or you've tweaked some value that affects things... In general, TLS shouldn't pose a problem because: 1) ovirt sets up its own CA that issues certificates for the hosts 2) the CA certificate and respective host certificate subject are passed to the client 3) the client can verify the host using these information even in cases when connection IP/FQDN doesn't match CN in subject of server certificate The only condition that indeed breaks it should be display network address override _when migrating the VM_ (because then the connection data are passed via the host and libvirt doesn't allow to pass the arbitrary IP/FQDN yet) David PS: Itamar, advice to disable SSL/TLS is IMO bad, bad thing. ;) Itamar Heim píše v Po 24. 06. 2013 v 08:55 +0300: On 06/24/2013 03:10 AM, lofyer wrote: 于 2013/6/24 1:47, Itamar Heim 写道: On 06/06/2013 11:51 AM, lof yer wrote: I connect https://192.168.1.111 and connect to the VM, then the remote-viewer shows up, but failed to show the VM desktop. Is it the https problem? Can I connect to the VM without modify /etc/hosts? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users was this resolved? sounds like a certificate/dns issue? Yes, it's certificate/dns problem. But how can I connect via IP instead of FQDN without https? i guess it depends if you can tell spice client to not validate the ssl certificate. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- David Jaša, RHCE SPICE QE based in Brno GPG Key: 22C33E24 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24 smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] use case information
Hi Everyone! If you made it to Red Hat Summit I hope you had a moment to stop by the oVirt booth in the developer lounge and say Hello! It was a great show and we had a lot of interest in oVirt from attendees. It was great working with Mike and Einav at the booth and I think it was a great show! One of the ideas coming out of summit was a user showcase page on the oVirt website with a list or some additional information about deployments of oVirt in the wild. We've got some of the usual suspects in mind but we want to hear from more of you! Is your organization using oVirt? How many VMs are being managed? How many KVM hosts are deployed? Let us know! Thanks, -theron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] NetApp plugin/package. Is this available or planned ?
On 06/19/2013 06:37 AM, Matt . wrote: Hi All, If I'm right I remember from the past that there was an ovirt-netapp package available, but I'm not sure. At the moment it's not in the repo, at least not 3.3 What is the status of this package/plugin ? I'm able to test this on a cluster and would like to help here if possible. I hope it's there, or at least somewhere. Thanks, Matt Hi Jon, Any info you can share on this? Mike ___ 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
Re: [Users] NetApp plugin/package. Is this available or planned ?
On 06/24/2013 06:45 PM, Mike Burns wrote: On 06/19/2013 06:37 AM, Matt . wrote: Hi All, If I'm right I remember from the past that there was an ovirt-netapp package available, but I'm not sure. At the moment it's not in the repo, at least not 3.3 What is the status of this package/plugin ? I'm able to test this on a cluster and would like to help here if possible. I hope it's there, or at least somewhere. Thanks, Matt Hi Jon, Any info you can share on this? http://captainkvm.com/2013/06/virtual-storage-console-for-rhev/ ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Fedora upgrading from 3.1 to 3.2
On 06/23/2013 10:08 PM, Alfred Angelov wrote: Hey, This might sounds like a foolish question, but from the link you mentioned: oVirt 3.1 was released as Fedora 17 package while 3.2 is targeted Fedora 18. Due to the nature of this upgrade, we DO NOT recommend it, users are advised to do a 3.2 clean installation, and to import all VM's and template into the new installation. Is there anything special I would have to do to import all the VMs (around 40) from my ovirt 3.1.0-2 to another ovirt (which runs 3.2.2) ? you should: -create and attach an export domain to the relevant datacenter on your 3.1 system -export the vms you need to the export domain -disconnect the export domain -import the domain on your 3.2.2 system (from storage tab) -import the vms to the relevant datacenter Mvh, Alfred Angelov On 06/23/2013 11:35 AM, Alex Lourie wrote: Hi Karli I've written up all we know at [1], please try to follow it (if you haven't yet) and let us know how it goes. If anything goes wrong, we will look for the ways to resolve it. Alex. [1] http://www.ovirt.org/OVirt_3.1_to_3.2_upgrade On Thu, Jun 20, 2013 at 8:05 PM, Alex Lourie alou...@redhat.com wrote: Hi Karli I am reviewing all the actions again, and hopefully will have something documented on Sunday. Alex. On Tue, Jun 18, 2013 at 10:46 AM, Karli Sjöberg karli.sjob...@slu.se wrote: tis 2013-06-18 klockan 10:06 +0300 skrev Moran Goldboim: On 06/17/2013 02:51 PM, Karli Sjöberg wrote: mån 2013-06-17 klockan 10:11 +0003 skrev Alex Lourie: On Fri, Jun 14, 2013 at 12:26 PM, Karli Sjöberg karli.sjob...@slu.se wrote: Hi! Hi Karli, More than two months have passed without any notices or updates on this issue, and looking at the bugreport absolutely nothing has been done since then. What´s confusing me is that the release management for oVirt 3.2 has this clearly printed: MUST: Upgrade from previous release And you all seem too busy with getting the next release out of the door before fixing the current... What gives? Don´t you care about early adopters? I apologise that this issue wasn't taken care of yet. It is clear that the priorities of developers shifted towards work on features in 3.3 release, which feature freeze is happening in about 2 weeks, so you can understand the time pressure they all have. There's no need to be angry about that. It is an open source project and as resources for the development are limited, we're trying to do our best to cover as much issues as possible. This can lead to situations as this issue, which may be left behind for some time. I´m not angry, as I stated before, I´m more confused, and maybe a little disappointed that important(in my opinion) pieces of a projects continuum have been ignored like that. I´m having a hard time understanding the reasoning behind the priorities that have made this issue appear. In my mind, making sure that users of any project are able to follow between minor upgrades is a given, with a schedule like; 1) Feature freeze, 2) Fix release blockers (upgrading being one of them), 3) Release, in that order. Now what´s happening is that you are kind of hoping to drag this out until the problem goes away by itself when you decide it´s time to stop supporting 3.1. That said, the process for upgrading the oVirt 3.1 on Fedora 17 to oVirt 3.2 on Fedora 18 is complex and non-trivial, that's why it is taking time to resolve all the issues that come up in the process. If this matter is not extremely urgent, we are currently working on a tool that may make this upgrade easier, albeit, maybe, not completely automatic. On the other hand, if this is a completely and utterly urgent, we may try to guide you through possible manual attempts to perform the upgrade. Mind though, that they weren't thoroughly tested, and not promised to go smoothly or even work, and we may have to think about possible alternative solutions on the go. Straight answer: Am I ever going to be able to upgrade from 3.1 to 3.2? My concern (fear) is about being left behind, abandoned. It makes me feel non-important. Just like any admin, the work put down to make Templates, to set up quotas, create VMPools, a dozen of guests. And then have to export everything (nullifying the idea of Thin Provisioning), redo every Role, reset every permission, quota, and so on, isn´t (in my opinion) viable in the long run for oVirt as a project to demand. That´s why I had the notion that upgrading surely had to be a high priority. Was I wrong about that? upgrade actually was high priority task, but due to lots of platform (fedora 18) changes, it became a huge operation to support it (which comes on top new features/bugs/support etc.). in addition we have noticed that the interest from the community regarding it, is very limited. from where i see i we have couple of
[Users] Using python sdk to find the VMs running on a host.
Hi, I am using the ovirt-python-sdk to figure out if the host is idle or not. The way to determine if the host is idle at a given instant is finding out the number of VMs running on it. If the number of VMs = 0 implies host is idle. I was exploring the python sdk to figure out Host-VMs mapping i.e What are the VMs running on the different host. Looks like the only way to find this, is to query each VM in /api/vms list to get the host on which it is running. Is this the right way ? Is there no direct query or REST API to list the VMs running on a given host at that instant. I was looking to get the data center hierarchy structure. Number_of_datacenters | V clusters in each data center | V Hosts in each cluster | V VMs on each host. This kind of mapping as seen on the GUI. Is there any way to obtain the same from the ovirt-python-sdk ? With this information, this would help me write scripts to turn-off my hosts if idle automatically and power them on as required. Regards, Deepthi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
