ich is
already opensource?
Thanks,
Kevin
From: Matthias Runge [mru...@redhat.com]
Sent: Monday, July 25, 2016 11:54 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [kolla] Monitoring tooling
On 25/07/16 09:57, Julien Danjou wrote:
> O
Response inline
On 7/25/16, 11:54 AM, "Matthias Runge" wrote:
>On 25/07/16 09:57, Julien Danjou wrote:
>> On Sun, Jul 24 2016, Mathias Ewald wrote:
>>
>>> 5. InfluxDB to store metrics
>>> 6. Grafana to dashboard metrics
>>
>> Would be nice to leverage scalable and open source solution built yo
On 25/07/16 09:57, Julien Danjou wrote:
> On Sun, Jul 24 2016, Mathias Ewald wrote:
>
>> 5. InfluxDB to store metrics
>> 6. Grafana to dashboard metrics
>
> Would be nice to leverage scalable and open source solution built your
> fellow OpenStack community, i.e. Gnocchi and its Grafana support.
>
instead of one, collectd would be a good second target :)
> >>
> >> Regards
> >> -steve
> >>
> >> From: Mathias Ewald
> >> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> >>
> >> Date: Monda
> two challenges instead of one, collectd would be a good second target :)
>>
>> Regards
>> -steve
>>
>> From: Mathias Ewald
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Date: Monday, July 25, 2016 at 4:
6 at 4:48 AM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [kolla] Monitoring tooling
>
> I believe I found a possible (partial) solution:
> https://github.com/influxdata/t
ply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, July 25, 2016 at 4:48 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject:
So, this is one of the areas i'm currently on with the Sensu work. I've
been experimenting with a privileged container, which is very similar to
our current kolla_toolbox container.
The agent certainly needs to be in it's own container, with access to be
able to run commands in other namespaces /
Collectd is how you obtain the host disk usage. It can be done although
collectd is nearing the complexity of turning nova into a container so it
may need someone experienced with Kolla to execute.
Regards
-steve
On 7/25/16, 12:39 AM, "Jeffrey Zhang" wrote:
>I am open to the choice of tools. B
I believe I found a possible (partial) solution:
https://github.com/influxdata/telegraf/issues/218 I will test it and report
back.
2016-07-25 12:58 GMT+02:00 Mathias Ewald :
> Excellent point ... I just checked what happens when running telegraf in a
> container: You'll get paths like
>
> /etc/ho
Excellent point ... I just checked what happens when running telegraf in a
container: You'll get paths like
/etc/hostname
/etc/hosts
/var/log/kolla
and others as available file systems. I guess it makes no sense at all then
to containerize monitoring agents ... Sensu is going to have the same
pro
On Sun, Jul 24 2016, Mathias Ewald wrote:
> 5. InfluxDB to store metrics
> 6. Grafana to dashboard metrics
Would be nice to leverage scalable and open source solution built your
fellow OpenStack community, i.e. Gnocchi and its Grafana support.
My 2c,
--
Julien Danjou
// Free Software hacker
//
I am open to the choice of tools. But i am worried on thing: how to
get all the host disk usage when containerized the monitor tool?
On Mon, Jul 25, 2016 at 2:12 PM, Mathias Ewald wrote:
> Understood.
>
> 2016-07-25 7:34 GMT+02:00 Matthias Runge :
>>
>> On 25/07/16 06:38, Mathias Ewald wrote:
>
Understood.
2016-07-25 7:34 GMT+02:00 Matthias Runge :
> On 25/07/16 06:38, Mathias Ewald wrote:
> > Hi, correct me if wrong please: Isn't gnocchi more targeting cloud
> > tenants rather than cloud ops? If that's the case I wont find info like
> > "controller cpu usage" or "hypervisor memory usag
On 25/07/16 06:38, Mathias Ewald wrote:
> Hi, correct me if wrong please: Isn't gnocchi more targeting cloud
> tenants rather than cloud ops? If that's the case I wont find info like
> "controller cpu usage" or "hypervisor memory usage".
>
> Cheers
> Mathias
>
Uhm, in this scenario, gnocchi just
Hi, correct me if wrong please: Isn't gnocchi more targeting cloud tenants
rather than cloud ops? If that's the case I wont find info like "controller
cpu usage" or "hypervisor memory usage".
Cheers
Mathias
Am 24.07.2016 23:02 schrieb "Matthias Runge" :
> On 23/07/16 00:15, Steven Dake (stdake) w
On 23/07/16 00:15, Steven Dake (stdake) wrote:
> Hi folks,
>
> At the midcycle we decided to push off implementing Monitoring until
> post Newton. The rationale for this decision was that the core review
> team has enough on their plates and nobody was super keen to implement
> any monitoring sol
Fri, Jul 22, 2016 at 5:19 PM, Dave Walker
> wrote:
> >>>> > Yes, this is my thought.
> >>>> >
> >>>> > The scope of the Sensu work is: "Is this thing working?" (with the
> >>>> > reference
> >>>>
being up/down)
>>>> > But the scope of the Grafana and friends is, "How hard is this
>>>> > working?"
>>>> > (but no alerting)
>>>> >
>>>> > They are certainly complementary However, Sensu can throw data at
>
> (but no alerting)
>>> >
>>> > They are certainly complementary However, Sensu can throw data at a
>>> > Grafana stack (aiui).. but I fear that is too much to achieve this
>>> cycle.
>>> >
>>> > --
>>> > Kind Regards,
>>> &g
gt;> >> One's metrics and the other is monitoring. You probably want both at
>> the
>> >> same time.
>> >>
>> >> Thanks,
>> >> Kevin
>> >>
>> >> From: Steven Dake (st
are two different, complementary things.
> >>
> >> One's metrics and the other is monitoring. You probably want both at the
> >> same time.
> >>
> >> Thanks,
> >> Kevin
> >> ____________
> >> From: Steven Dake (stdake) [std...@cisco
ics and the other is monitoring. You probably want both at the
>> same time.
>>
>> Thanks,
>> Kevin
>>
>> From: Steven Dake (stdake) [std...@cisco.com]
>> Sent: Friday, July 22, 2016 3:52 PM
>> To: OpenStack Development Mailing List (not for u
oth at the
> same time.
>
> Thanks,
> Kevin
>
> From: Steven Dake (stdake) [std...@cisco.com]
> Sent: Friday, July 22, 2016 3:52 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [kolla
Stack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] Monitoring tooling
Thanks for pointing that out. Brain out to lunch today it appears :(
I think choices are a good thing even though they increase our
implementation footprint. Anyone opposed to implementing
Thanks for pointing that out. Brain out to lunch today it appears :(
I think choices are a good thing even though they increase our
implementation footprint. Anyone opposed to implementing both with
something in globals.yml like
monitoring: grafana or
monitoring: sensu
Comments questions or con
Don't forget mewalds implementation as well - we now have 2 monitoring
options for kolla :-)
On Fri, Jul 22, 2016 at 3:15 PM, Steven Dake (stdake) wrote:
> Hi folks,
>
> At the midcycle we decided to push off implementing Monitoring until post
> Newton. The rationale for this decision was that t
Hi folks,
At the midcycle we decided to push off implementing Monitoring until post
Newton. The rationale for this decision was that the core review team has
enough on their plates and nobody was super keen to implement any monitoring
solution given our other priorities.
Like all good things,
28 matches
Mail list logo
