tack Development Mailing List (not for usage questions)"
>>, "John
>> Garbutt"
>> Sent: Thursday, 19 December, 2013 10:37:27 AM
>> Subject: Re: [openstack-dev] [nova] VM diagnostics - V3 proposal
>>
>> On Thu, Dec 19, 2013 at 03:47:30PM +0100, Vl
Matt,
My understanding is that there will be a nova.virt.baremetal.ironic driver
in Nova which will talk to Ironic API to manage bare-metal instances. So,
Ironic will be actually providing the diagnostics data about bm instance
via its API eventually.
Hope someone will correct me if I'm wrong.
-
On Friday, December 20, 2013 3:57:15 AM, Daniel P. Berrange wrote:
On Fri, Dec 20, 2013 at 12:56:47PM +0400, Oleg Gelbukh wrote:
Hi everyone,
I'm sorry for being late to the thread, but what about baremetal driver?
Should it support the get_diagnostics() as well?
Of course, where practical,
On Fri, Dec 20, 2013 at 12:56:47PM +0400, Oleg Gelbukh wrote:
> Hi everyone,
>
> I'm sorry for being late to the thread, but what about baremetal driver?
> Should it support the get_diagnostics() as well?
Of course, where practical, every driver should aim to support every
method in the virt driv
gt; > To: "Vladik Romanovsky"
> > Cc: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>, "John
> > Garbutt"
> > Sent: Thursday, 19 December, 2013 10:37:27 AM
> > Subject: Re: [opens
"OpenStack Development Mailing List (not for usage questions)"
> , "John
> Garbutt"
> Sent: Thursday, 19 December, 2013 10:37:27 AM
> Subject: Re: [openstack-dev] [nova] VM diagnostics - V3 proposal
>
> On Thu, Dec 19, 2013 at 03:47:30PM +0100, Vladik Romanovsk
On Thu, Dec 19, 2013 at 08:02:16AM -0800, Gary Kotton wrote:
>
>
> On 12/19/13 5:50 PM, "Daniel P. Berrange" wrote:
>
> >On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote:
> >> Hi,
> >> Following the discussion yesterday I have updated the wiki - please see
> >>
> >>https://urldefens
On 12/19/13 6:07 PM, "Daniel P. Berrange" wrote:
>On Thu, Dec 19, 2013 at 08:02:16AM -0800, Gary Kotton wrote:
>>
>>
>> On 12/19/13 5:50 PM, "Daniel P. Berrange" wrote:
>>
>> >On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote:
>> >> Hi,
>> >> Following the discussion yesterday I h
On 12/19/13 5:50 PM, "Daniel P. Berrange" wrote:
>On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote:
>> Hi,
>> Following the discussion yesterday I have updated the wiki - please see
>>
>>https://urldefense.proofpoint.com/v1/url?u=https://wiki.openstack.org/wik
>>i/Nova_VM_Diagnostic
On Tue, Dec 17, 2013 at 04:28:30AM -0800, Gary Kotton wrote:
> Hi,
> Following the discussion yesterday I have updated the wiki - please see
> https://wiki.openstack.org/wiki/Nova_VM_Diagnostics. The proposal is
> backwards compatible and will hopefully provide us with the tools to be
> able to tro
ons)"
Sent: Thursday, 19 December, 2013 9:34:02 AM
Subject: Re: [openstack-dev] [nova] VM diagnostics - V3 proposal
On Thu, Dec 19, 2013 at 02:27:40PM +, John Garbutt wrote:
On 16 December 2013 15:50, Daniel P. Berrange wrote:
On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wro
On Thu, Dec 19, 2013 at 03:47:30PM +0100, Vladik Romanovsky wrote:
> I think it was:
>
> ceilometer sample-list -m cpu_util -q 'resource_id=vm_uuid'
Hmm, a standard devstack deployment of ceilometer doesn't seem to
record any performance stats at all - just shows me the static
configuration param
Or
ceilometer meter-list -q resource_id='vm_uuid'
- Original Message -
> From: "Daniel P. Berrange"
> To: "John Garbutt"
> Cc: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Thursday, 19 December, 2
Sent: Thursday, 19 December, 2013 9:34:02 AM
> Subject: Re: [openstack-dev] [nova] VM diagnostics - V3 proposal
>
> On Thu, Dec 19, 2013 at 02:27:40PM +, John Garbutt wrote:
> > On 16 December 2013 15:50, Daniel P. Berrange wrote:
> > > On Mon, Dec 16, 2013 at 0
On Thu, Dec 19, 2013 at 02:27:40PM +, John Garbutt wrote:
> On 16 December 2013 15:50, Daniel P. Berrange wrote:
> > On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wrote:
> >> On 16 December 2013 15:25, Daniel P. Berrange wrote:
> >> > On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Ko
On 16 December 2013 15:50, Daniel P. Berrange wrote:
> On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wrote:
>> On 16 December 2013 15:25, Daniel P. Berrange wrote:
>> > On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
>> >> I'd like to propose the following for the V3 API (we
Hi,
Following the discussion yesterday I have updated the wiki - please see
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics. The proposal is
backwards compatible and will hopefully provide us with the tools to be
able to troubleshoot VM issues.
Thanks
Gary
On 12/16/13 5:50 PM, "Daniel P. Berra
On 12/16/13 5:25 PM, "Daniel P. Berrange" wrote:
>On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
>> Hi,
>> At the moment the administrator is able to retrieve diagnostics for a
>>running VM. Currently the implementation is very loosely defined, that
>>is, each driver returns whate
On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wrote:
> On 16 December 2013 15:25, Daniel P. Berrange wrote:
> > On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
> >> I'd like to propose the following for the V3 API (we will not touch V2
> >> in case operators have applications
On 16 December 2013 15:25, Daniel P. Berrange wrote:
> On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
>> Hi,
>> At the moment the administrator is able to retrieve diagnostics for a
>> running VM. Currently the implementation is very loosely defined, that is,
>> each driver returns
On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
> Hi,
> At the moment the administrator is able to retrieve diagnostics for a running
> VM. Currently the implementation is very loosely defined, that is, each
> driver returns whatever they have to return. This is problematic in a numb
21 matches
Mail list logo
