Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-26 Thread Vishvananda Ishaya
Well the code to generate diagnostics under xen is in nova/virt/xenapi/vm_utils.py: 887 def compile_diagnostics(cls, session, record): 888 """Compile VM diagnostics data""" 889 try: 890 host = session.get_xenapi_host() 891 host_ip = session.call_xen

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-26 Thread Leander Bessa
Could you give me some references on how i could implement the diagnostics call for kvm/libvirt? Regards, Leander On Wed, Jan 25, 2012 at 7:39 PM, Vishvananda Ishaya wrote: > There are currently no plans for such of thing. It seems easier to rely on > existing plugins for monitoring. That said

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-25 Thread Vishvananda Ishaya
There are currently no plans for such of thing. It seems easier to rely on existing plugins for monitoring. That said, it shouldn't be too hard to implement the diagnostics call for kvm/libvirt if someone wants to tackle it. Vish On Jan 25, 2012, at 8:21 AM, Leander Bessa wrote: > Are there a

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-25 Thread Jay Pipes
On Wed, Jan 25, 2012 at 11:21 AM, Leander Bessa wrote: > Are there any plans to add support for monitoring instances which run > libvirt? The plugin below is for libvirt... > Does XEN also use libvirt? libvirt supports Xen, but the Xen virt driver in Nova does not use libvirt... -jay > On Wed

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-25 Thread Leander Bessa
Are there any plans to add support for monitoring instances which run libvirt? Does XEN also use libvirt? On Wed, Jan 25, 2012 at 2:01 PM, Leander Bessa wrote: > Ok i'll look into that, thank you for the answers. > > Regards, > > Leander > > > On Tue, Jan 24, 2012 at 11:16 PM, Vishvananda Ishaya

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-25 Thread Leander Bessa
Ok i'll look into that, thank you for the answers. Regards, Leander On Tue, Jan 24, 2012 at 11:16 PM, Vishvananda Ishaya wrote: > Monitoring can be done through libvirt monitoring plugins. For example: > > http://honk.sigxcpu.org/projects/libvirt/ > > Vish > > On Jan 24, 2012, at 2:01 PM, Lean

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Vishvananda Ishaya
Monitoring can be done through libvirt monitoring plugins. For example: http://honk.sigxcpu.org/projects/libvirt/ Vish On Jan 24, 2012, at 2:01 PM, Leander Bessa wrote: > How exactly do i install that particular extension and what can i use as an > alternative to monitor instances with KVM? >

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Brian Waldon
If you're running diablo, you should just have to restart your nova-api nodes with the allow_admin_api flag on. But as Kiall points out, 'diagnostics' is not implemented for libvirt. Unfortunately, I don't know how to help you on that front. Maybe somebody else has some pointers? On Jan 24, 201

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Leander Bessa
How exactly do i install that particular extension and what can i use as an alternative to monitor instances with KVM? On Tue, Jan 24, 2012 at 6:11 PM, Kiall Mac Innes wrote: > I've just verified this against my install, but since the diagnostics is > unsupported when using libvirt/kvm, it stil

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Kiall Mac Innes
I've just verified this against my install, but since the diagnostics is unsupported when using libvirt/kvm, it still errors out (but with a 500, rather than 404) Thanks, Kiall On Tue, Jan 24, 2012 at 5:56 PM, Brian Waldon wrote: > Actually the diagnostics command was not added in Essex, but it

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Brian Waldon
My assumption here was actually incorrect. See my follow-up email for a suggested fix. On Jan 24, 2012, at 9:46 AM, Brian Waldon wrote: > The diagnostics command moved to a server action. We will need to update > novaclient to support this. I went ahead and filed a bug for it: > https://bugs.l

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Brian Waldon
Actually the diagnostics command was not added in Essex, but it was converted to a true extension. However it is part of the Admin API, which means for Diablo you need to set the allow_admin_api flag on your nova-api node. On Jan 24, 2012, at 9:41 AM, Kiall Mac Innes wrote: > Hi, > > The diag

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Kiall Mac Innes
Oh, I had thought it didn't exist in Diablo.. My mistake! Thanks, Kiall On Tue, Jan 24, 2012 at 5:46 PM, Brian Waldon wrote: > The diagnostics command moved to a server action. We will need to update > novaclient to support this. I went ahead and filed a bug for it: > https://bugs.launchpad.net

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Brian Waldon
The diagnostics command moved to a server action. We will need to update novaclient to support this. I went ahead and filed a bug for it: https://bugs.launchpad.net/nova/+bug/921103 On Jan 24, 2012, at 9:03 AM, Leander Bessa wrote: > Hello, > > I've setup a single node configuration with keysto

Re: [Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Kiall Mac Innes
Hi, The diagnostics command was added in Essex, my packages are using the stable Diablo version. Novaclient sadly shows these options even though they can't be used with Diablo. Kiall Sent from my mobile - Sorry for being short. On Jan 24, 2012 5:04 p.m., "Leander Bessa" wrote: > Hello, > > I

[Openstack] [nova client] Can't get the diagnostics command to work

2012-01-24 Thread Leander Bessa
Hello, I've setup a single node configuration with keystone using the packages from https://launchpad.net/~managedit/+archive/openstack. I've managed to launch an instance, however when i run the commando nova diagnostics i get this: REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content