Re: [openstack-dev] Monitoring as a Service

2014-05-30 Thread nobi nobita
Thanks!!! I was actually going to ask this issue :) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Monitoring as a Service

2014-05-07 Thread Eoghan Glynn
Hi Alexandre, I wanted to let this discussion develop a little before jumping in, as we've already had many circular debates about the cross-over between ceilometer and monitoring infrastructure in general. Personally I'm in favor of the big tent/broad church interpretation of ceilometer's

[openstack-dev] Monitoring as a Service

2014-05-07 Thread Paulo Oliveira
us - @ATNoG_ITAv From: Eoghan Glynn egl...@redhat.com Subject: Re: [openstack-dev] Monitoring as a Service Date: 7 May 2014 09:57:38 GMT+1 To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Reply-To: OpenStack Development Mailing List

Re: [openstack-dev] Monitoring as a Service

2014-05-07 Thread Alexandre Viau
-dev@lists.openstack.org Cc: alexandre viau alexandre.v...@savoirfairelinux.com Sent: Wednesday, May 7, 2014 12:10:08 PM Subject: [openstack-dev] Monitoring as a Service Hello everyone, Me and my team have been following this subject and similar ones related to Monitoring. IHMO, seems

Re: [openstack-dev] Monitoring as a Service

2014-05-06 Thread Thierry Carrez
John Dickinson wrote: One of the advantages of the program concept within OpenStack is that separate code projects with complementary goals can be managed under the same program without needing to be the same codebase. The most obvious example across every program are the server and client

Re: [openstack-dev] Monitoring as a Service

2014-05-06 Thread Sandy Walsh
On 5/6/2014 10:04 AM, Thierry Carrez wrote: John Dickinson wrote: One of the advantages of the program concept within OpenStack is that separate code projects with complementary goals can be managed under the same program without needing to be the same codebase. The most obvious example

Re: [openstack-dev] Monitoring as a Service

2014-05-06 Thread Clint Byrum
Excerpts from Sandy Walsh's message of 2014-05-06 07:02:05 -0700: On 5/6/2014 10:04 AM, Thierry Carrez wrote: John Dickinson wrote: One of the advantages of the program concept within OpenStack is that separate code projects with complementary goals can be managed under the same program

Re: [openstack-dev] Monitoring as a Service

2014-05-06 Thread Thierry Carrez
Sandy Walsh wrote: I'd be curious to know more what managed means in this situation? Is the core project expected to allocate time in the IRC meeting to the concerns of these adjacent projects? What if the core project doesn't agree with the direction or deems there's too much overlap? Does

Re: [openstack-dev] Monitoring as a Service

2014-05-06 Thread Sandy Walsh
On 5/6/2014 1:48 PM, Thierry Carrez wrote: Sandy Walsh wrote: I'd be curious to know more what managed means in this situation? Is the core project expected to allocate time in the IRC meeting to the concerns of these adjacent projects? What if the core project doesn't agree with the

Re: [openstack-dev] Monitoring as a Service

2014-05-06 Thread Hochmuth, Roland M
It sounds like there is some interest in this topic. With the Summit just around the corner, I propose we get together while many of us are there and explore this area further. I'm in the process of researching the availability of a time and place, shooting for early morning, prior to when the

Re: [openstack-dev] Monitoring as a Service

2014-05-05 Thread Hochmuth, Roland M
Alexandre, Great timing on this question and I agree with your proposal. I work for HP and we are just about to open-source a project for Monitoring as a Service (MaaS), called Jahmon. Jahmon is based on our customer-facing monitoring as a service solution and internal monitoring projects.

Re: [openstack-dev] Monitoring as a Service

2014-05-05 Thread Clint Byrum
Excerpts from John Dickinson's message of 2014-05-04 12:37:55 -0700: One of the advantages of the program concept within OpenStack is that separate code projects with complementary goals can be managed under the same program without needing to be the same codebase. The most obvious example

Re: [openstack-dev] Monitoring as a Service

2014-05-05 Thread Alexandre Viau
Thanks to everyone for the feedback. I agree that this falls under the Telemetry Program and I have moved the blueprint. You can find it here: https://blueprints.launchpad.net/ceilometer/+spec/monitoring-as-a-service Wiki page: https://wiki.openstack.org/wiki/MaaS Etherpad:

Re: [openstack-dev] Monitoring as a Service

2014-05-04 Thread Thomas Goirand
On 05/02/2014 05:17 AM, Alexandre Viau wrote: Hello Everyone! My name is Alexandre Viau from Savoir-Faire Linux. We have submited a Monitoring as a Service blueprint and need feedback. Problem to solve: Ceilometer's purpose is to track and *measure/meter* usage information collected

Re: [openstack-dev] Monitoring as a Service

2014-05-04 Thread John Griffith
On Sun, May 4, 2014 at 9:37 AM, Thomas Goirand z...@debian.org wrote: On 05/02/2014 05:17 AM, Alexandre Viau wrote: Hello Everyone! My name is Alexandre Viau from Savoir-Faire Linux. We have submited a Monitoring as a Service blueprint and need feedback. Problem to solve:

Re: [openstack-dev] Monitoring as a Service

2014-05-04 Thread Denis Makogon
Hello to All. I also +1 this idea. As I can see, Telemetry program (according to Launchpad) covers the process of the infrastructure metrics (networking, etc) and in-compute-instances metrics/monitoring. So, the best option, I guess, is to propose add such great feature to Ceilometer.

Re: [openstack-dev] Monitoring as a Service

2014-05-04 Thread John Dickinson
One of the advantages of the program concept within OpenStack is that separate code projects with complementary goals can be managed under the same program without needing to be the same codebase. The most obvious example across every program are the server and client projects under most

Re: [openstack-dev] Monitoring as a Service

2014-05-03 Thread Bohai (ricky)
+1 I like this idea. Best regards to you. Ricky -Original Message- From: Alexandre Viau [mailto:alexandre.v...@savoirfairelinux.com] Sent: Friday, May 02, 2014 5:17 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Monitoring as a Service Hello Everyone! My

Re: [openstack-dev] Monitoring as a Service

2014-05-02 Thread Jay Pipes
On Thu, 2014-05-01 at 17:17 -0400, Alexandre Viau wrote: Hello Everyone! My name is Alexandre Viau from Savoir-Faire Linux. We have submited a Monitoring as a Service blueprint and need feedback. Problem to solve: Ceilometer's purpose is to track and *measure/meter* usage information

Re: [openstack-dev] Monitoring as a Service

2014-05-02 Thread Fox, Kevin M
To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Monitoring as a Service Hello Everyone! My name is Alexandre Viau from Savoir-Faire Linux. We have submited a Monitoring as a Service blueprint and need feedback. Problem to solve: Ceilometer's purpose is to track and *measure/meter* usage

Re: [openstack-dev] Monitoring as a Service

2014-05-02 Thread Alexandre Viau
. Their results would be polled by the monitoring service and stored in Ceilometer. If you wish to collaborate, feel free to contact me at alexandre.v...@savoirfairelinux.com The blueprint is available here: https://blueprints.launchpad.net/openstack-ci/+spec/monitoring-as-a-service Thanks

[openstack-dev] Monitoring as a Service

2014-05-01 Thread Alexandre Viau
by the monitoring service and stored in Ceilometer. If you wish to collaborate, feel free to contact me at alexandre.v...@savoirfairelinux.com The blueprint is available here: https://blueprints.launchpad.net/openstack-ci/+spec/monitoring-as-a-service Thanks