| To: | Marko Myllynen <myllynen@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] libvirt pmda: support old libvirt 0.10 API |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 14 Jul 2016 20:27:36 -0400 (EDT) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <6abca560-398c-3a87-350d-c2cfba1a9b78@xxxxxxxxxx> |
| References: | <6abca560-398c-3a87-350d-c2cfba1a9b78@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | 9L5lXQsDPUraQAB9A86R9/on/sr4FQ== |
| Thread-topic: | libvirt pmda: support old libvirt 0.10 API |
Hi Marko, ----- Original Message ----- > [...] > This is mostly for RHEL 6 / libvirt-0.10 environments but since now > configurable, can be enabled anywhere where the newer API is not > an option for some reason. I wonder if its possible to do this fully automatically? (i.e. not exposed to users at all in the config file). There appears to be an API for inspecting the libvirt version, if that helps? $ python >>> import libvirt >>> print libvirt.getVersion() 1002018 >>> cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Bug#805955: [pcp] Bug#805955: pcp: FTBFS when built with dpkg-buildpackage -A (no binary artifacts), Nathan Scott |
|---|---|
| Next by Date: | pcp updates: marko merge, Nathan Scott |
| Previous by Thread: | Re: libvirt pmda: support old libvirt 0.10 API, Martins Innus |
| Next by Thread: | Re: [pcp] libvirt pmda: support old libvirt 0.10 API, Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |