[openstack-dev] [Monasca] Locked (latched) alarms

Hello everyone, I have written a short blueprint on locked/latched alarms for Monasca [1]. The functionality allows the operator to define an alarm which after transition to ALARM state, stays in that state until it is manually reset. What name should we use for that? Locked, lockable,

[openstack-dev] [Monasca] monasca-agent, flake8 version change on Jenkins

Hi, Flake 8 version seems to have changed since yesterday on the Jenkins node. was: flake8==2.5.5 now: flake8==2.6.0 It (apparently) causes gate-monasca-agent-pep8 checks to fail, since the old code does not pass the check. Has anyone started addressing this issue? BR, Laszlo

[openstack-dev] [Monasca] Virtual Mid Cycle Coordinates - July 19/20

Monasca Mid Cycle Day 1 July 19 2016 7am to noon PDT Webex Join WebEx meeting: https://cisco.webex.com/ciscosales/j.php?MTID=mb490140119f1f6f518160d85b108 0a13 Meeting number: 200 700 937 Meeting password: mXdvExYq Join by phone +1-408-525-6800 Call-in toll number (US/Canada)

Re: [openstack-dev] [Monasca][Gnocchi] influxDB clustering and HA will be "commercial option".

Has anyone talked with the gnocchi folks? It seems like a good time to. :) Thanks, Kevin From: Jay Pipes [jaypi...@gmail.com] Sent: Thursday, June 02, 2016 4:55 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Monasca] influxDB

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

On 06/02/2016 04:02 AM, Monty Taylor wrote: On 06/02/2016 10:06 AM, Hochmuth, Roland M wrote: Hi Jaesuk, The change in InfluxDB licensing was announced in the blog at, https://influxdata.com/blog/update-on-influxdb-clustering-high-availability-and-monetization/. Up until that announcement,

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

luejay@gmail.com>> Reply-To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Monday, May 30, 2016 at 9:59 AM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

Jaesuk Ahn <bluejay@gmail.com<mailto:bluejay@gmail.com>> > Reply-To: OpenStack List > <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> > Date: Monday, May 30, 2016 at 9:59 AM > To: OpenStack List > <openstack-dev@lis

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

t;openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Thursday, June 2, 2016 at 12:51 AM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Monasca] influxDB clusterin

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

ilto:openstack-dev@lists.openstack.org>> Date: Monday, May 30, 2016 at 7:20 PM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

ck.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option". Hi, Monasca developers and users, https://influxdata.com/blog/update-on-influxdb-clustering-high-availability-and-monetization/ "For

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

The blog post also states that: "For our users looking for free open source options, we’ll be releasing the open source InfluxDB Relay project along with a landing page how to achieve high availability using pure open source and subscription options with the 0.12.0 releases and beyond. From

[openstack-dev] [Monasca] "The server is currently unavailable. on Monasca service

Hello, I am seeing the following issue after installing Monasca recently as a devstack environment" stack@scsor0002143001-pradipm:~/devstack$ monasca metric-list ERROR (exc:80) exception: {"message": "The server is currently unavailable. Please try again at a later time.\n\n\n", "code": "503

Re: [openstack-dev] [Monasca] Selectively publish logs to topics

Witek, Thanks, I like the way you break it into two topics. I agree with you on the first one to make it similar to dimensions (global and per message). On the second one, I see your point about including the topic as part of the resource URI. I am ok with it if others don’t see any issues

[openstack-dev] [Monasca] Selectively publish logs to topics

Hi Venkat, thank you for submitting the blueprint [1]. It covers actually two topics, both of them a valuable functional extension: 1) submitting additional (apart from dimensions) information with the logs 2) specifying a specific output topic ad. 1 I think we should keep it generic to

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

On Mon, May 30 2016, Jaesuk Ahn wrote: > It seems like “clustering” and “high availablity” of influxDB will be > available only in commercial version. > Monasca is currently leveraging influxDB as a metrics and alarm database. > Beside vertical, influxDB is currently only an open source option to

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

On 30 May 2016 at 11:59, Jaesuk Ahn wrote: > Hi, Monasca developers and users, > > > https://influxdata.com/blog/update-on-influxdb-clustering-high-availability-and-monetization/ > "For our current and future customers, we’ll be offering clustering and > high availability

[openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

Hi, Monasca developers and users, https://influxdata.com/blog/update-on-influxdb-clustering-high-availability-and-monetization/ "For our current and future customers, we’ll be offering clustering and high availability through Influx Cloud, our managed hosting offering, and Influx Enterprise, our

Re: [openstack-dev] [Monasca] Sporadic metrics

Hi Witek, Thank you for your response, it was really helpful. I was trying to figure out what are the next steps in the sporadics metrics side and you've made them more clear now. I'll report to my team so we can start the work. :) Best regards, Erickson Santos. - Mensagem original -

[openstack-dev] [Monasca] Sporadic metrics

Hi Erickson, thanks for your interest in our project and sorry for replying so late. We are happy that you're willing to contribute to the development of sporadic metrics. The incentive for this development is to introduce the possibility to create alarms in Monasca based on event like

Re: [openstack-dev] [monasca][release] missing build artifacts

Thanks for the pointer Clark. We will look into using that, although we were running out of time on the Mitaka release to get something like that implemented. Craig Bryant is in the process of manually updating the versions in the pom files to match the Mitaka tags. A couple of reviews are

Re: [openstack-dev] [monasca][release] missing build artifacts

On Tue, Apr 5, 2016, at 11:56 AM, Hochmuth, Roland M wrote: > Thanks Doug, Thierry and Davanum. Sorry about the all the extra work that > I've caused. > > It sounds like all Python projects/deliverables are in reasonable shape, > but if not, please let me know. > > Not sure what we should do

Re: [openstack-dev] [monasca][release] missing build artifacts

Thanks Doug, Thierry and Davanum. Sorry about the all the extra work that I've caused. It sounds like all Python projects/deliverables are in reasonable shape, but if not, please let me know. Not sure what we should do about the jars at this point. We had started to discuss a plan to

Re: [openstack-dev] [monasca][release] missing build artifacts

Davanum Srinivas wrote: Please see below: On Sat, Apr 2, 2016 at 8:41 AM, Doug Hellmann wrote: Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +: Hi Doug, You had mentioned issues with three repos: 1. monasca-ceilometer 2. monasca-log-api 3.

Re: [openstack-dev] [monasca][release] missing build artifacts

Please see below: On Sat, Apr 2, 2016 at 8:41 AM, Doug Hellmann wrote: > Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +: >> Hi Doug, You had mentioned issues with three repos: >> >> 1. monasca-ceilometer >> 2. monasca-log-api >> 3. monasca-thresh

Re: [openstack-dev] [monasca][release] missing build artifacts

Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +: > Hi Doug, You had mentioned issues with three repos: > > 1. monasca-ceilometer > 2. monasca-log-api > 3. monasca-thresh > > All the repos that have Python code I believe are in reasonable shape with > respect to the

Re: [openstack-dev] [monasca][release] missing build artifacts

Hi Doug, You had mentioned issues with three repos: 1. monasca-ceilometer 2. monasca-log-api 3. monasca-thresh All the repos that have Python code I believe are in reasonable shape with respect to the Python deliverables except for the following two repos: 1. monasca-ceilometer 2.

Re: [openstack-dev] [monasca][release] missing build artifacts

Excerpts from Hochmuth, Roland M's message of 2016-04-01 20:06:28 +: > Hi Doug, Sorry, this is our first release and we want to do the right thing. > > monasca-ceilometer is the code that plugs into the Ceilometer publisher and > Ceilometer storage driver to allow Ceilometer to send metrics

Re: [openstack-dev] [monasca][release] missing build artifacts

Hi Doug, Sorry, this is our first release and we want to do the right thing. monasca-ceilometer is the code that plugs into the Ceilometer publisher and Ceilometer storage driver to allow Ceilometer to send metrics to the Monasca API and use Monasca as a storage backend. We don't create a pypi

[openstack-dev] [monasca][release] missing build artifacts

Monasca team, We noticed in our audit of the links on http://releases.openstack.org/mitaka/index.html that the links to the build artifacts for monasca-ceilometer, monasca-log-api, and monasca-thresh point to missing files. These repositories either don't seem to have any real build jobs

Re: [openstack-dev] [Monasca] Alarm generation from a sequence of events

k.org openstack-dev@lists.openstack.org>> > Date: Monday, February 15, 2016 at 9:58 AM > To: OpenStack List <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>> > Subject: [openstack-dev] [Monasca] Alarm generation from a sequence of > events > > He

Re: [openstack-dev] [Monasca] Alarm generation from a sequence of events

58 AM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Monasca] Alarm generation from a sequence of events Hello, We come across the following interesting BP in the last weekly meeting: https://blueprints.laun

[openstack-dev] [Monasca] alarm-definition-list is failing with "service unavailable"

Hello, Seeing the alarm-definition-list is returning "service unavailable" for admin user: stack@ubuntu:~/devstack$ monasca --os-username admin --os-password secretadmin --os-project-name admin alarm-definition-list ERROR (exc:65) exception: { "title": "Service unavailable",

[openstack-dev] [Monasca] Allowing 'admin' user and 'admin' project full access to Monasca

Hello, Following [1] , I set up Monasca (with all other services). I get the 'mini-mon' project; 'monasca' service; 'monasca-agent', 'monasca-user' role and 'mini-mon', 'monasca-agent' users. I can do all expected operations (alarm

Re: [openstack-dev] [Monasca] alarms based on events

Hi Roland, > I don't think it would be difficult to add support for non-periodic > metrics/alarms. There are a couple of approaches we could take, so a design > discussion would be good to have if you are interested in implementing this. > This is feature that we are not working on right now,

Re: [openstack-dev] [monasca] Anomaly & Prediction Engine

.org>> Subject: Re: [openstack-dev] [monasca] Anomaly & Prediction Engine (Apology for ignorance) - can anyone from Monasca please point any related documentation about the APE micro-service which (whatever be the state currently it is) currently we have in Monasca? Its in python or in

Re: [openstack-dev] [Monasca] alarms based on events

ack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Monasca] alarms based on events Hi Roland, I had a chat with people on IRC about it and I understood that in order for my use case to work the Monasca software needs

[openstack-dev] [monasca] Anomaly & Prediction Engine

Monasca folks, We discussed about Anomaly & Prediction Engine in this week's irc meeting and decided we would exchange info using this list. I'm really interested in having this functionality but the status is prototype now. We know that there are a lot of related tech around it and the tech

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

our interest! Regards. -Original Message- From: Hochmuth, Roland M [mailto:roland.hochm...@hpe.com] Sent: Thursday, January 21, 2016 11:53 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Monasca

Re: [openstack-dev] [monasca] Anomaly & Prediction Engine

(Apology for ignorance) - can anyone from Monasca please point any related documentation about the APE micro-service which (whatever be the state currently it is) currently we have in Monasca? Its in python or in Java? --pradip On Fri, Jan 22, 2016 at 4:12 PM, Osanai, Hisashi <

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

t; Sent: Thursday, January 21, 2016 11:53 PM > To: OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin > > Hi Rodolfo, I think this would be useful work. Collectd h

Re: [openstack-dev] [monasca] Anomaly & Prediction Engine

lt;pradip.inte...@gmail.com pradip.inte...@gmail.com>> > Reply-To: OpenStack List <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>> > Date: Friday, January 22, 2016 at 5:18 AM > To: OpenStack List <openstack-dev@lists.openstack.org openstack

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

Sent: Thursday, January 21, 2016 11:53 PM >To: OpenStack Development Mailing List (not for usage questions) ><openstack-dev@lists.openstack.org> >Subject: Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin > >Hi Rodolfo, I think this would be useful work. Collectd

Re: [openstack-dev] [Monasca] alarms based on events

Hi Roland, I had a chat with people on IRC about it and I understood that in order for my use case to work the Monasca software needs to implement "non-periodic" metrics (because the monitored box sends out the event only on health change and not periodicaly) and I understood that this

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

We are looking into similar plan to have collectd-plugin for Monasca. There are some env. we cannot deploy monasca agent, but want to put data into Monasca. In addition, we wanted to use easily accepted collectd for gathering data from legacy env. It will be interesting to see more detail about

[openstack-dev] [Monasca] collectd-Monasca Python plugin

Hello: We are doing (or at least planning) a collectd-Monasca Python plugin. This plugin will receive the data from RPC calls form collectd and will write this data in Monasca, using statsd API. My question is: do you think this development could be useful? Does it worth? Any comment? Thank

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

il.com>> Reply-To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Thursday, January 21, 2016 at 4:49 AM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re

Re: [openstack-dev] [Monasca] alarms based on events

Hi Prema, SNMP isn't handled in Monasca and I have little experience in that area. This would be new development. It is possible to map binary data, such as health/status of a system or component. The usual way is to use the value 0 for up/OK and 1 for down/NOT_OK. A component would need to be

[openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi Everyone, The Monasca Mitaka Mid-cycle Meetup will be hosted via WebEx using the contact information below on Wednesday February 3rd and Thursday February 4th, 2016. The Etherpad with additional information is at, https://etherpad.openstack.org/p/monasca_mitaka_midcycle. The meeting is

[openstack-dev] [Monasca] alarms based on events

Hello, we are just evaluating Monasca for our new cloud infrastructure and I would like to ask if there are any possibilities in current Monasca or some development plans to address following use case: We have a box which we need to monitor and when something goes wrong with the box, it sends

Re: [openstack-dev] [Monasca] Enabling Graphana GUI from Horizon

Thanks. I can able to see the 'Monitoring' tab in the Horizon UI. However not able to launch the Monasca UI (Graphana). When trying to launch it, getting a "Page not found error:" : Using the URLconf defined in openstack_dashboard.urls, Django tried these URL patterns, in this order: 1. ^$

[openstack-dev] [Monasca] Add Monasca Client to global reqs

Guys, I just updated the requirements patch to update the monasca client to the global reqs. It now points to the latest version 1.0.27 that has all the compatible libraries (thanks Joe). https://review.openstack.org/#/c/251674/ Please review it so we can merge it. Thanks, Fabio

[openstack-dev] [Monasca] Enabling Graphana GUI from Horizon

Hello, We're using the following fullsetup to install Monasca (python): https://github.com/openstack/monasca-api/tree/master/devstack Most likely we need to do something more to see the "Monitoring" tab in left hand side that takes us to Monasca graphana GUI. Can anyone please point me?

Re: [openstack-dev] [Monasca] Enabling Graphana GUI from Horizon

Thanks! So I can temporarily follow the step to enable it in my setup. --pradip On Tue, Jan 12, 2016 at 9:45 PM, Lin Hua Cheng wrote: > > You would need to propose the new feature in the monasca-ui [1], which is > the horizon plugin for displaying monasca dashboard. > >

Re: [openstack-dev] [Monasca] Enabling Graphana GUI from Horizon

You would need to propose the new feature in the monasca-ui [1], which is the horizon plugin for displaying monasca dashboard. -Lin [1] https://github.com/openstack/monasca-ui/ On Tue, Jan 12, 2016 at 3:32 AM, Pradip Mukhopadhyay < pradip.inte...@gmail.com> wrote: > Hello, > > > We're using

[openstack-dev] Monasca -agent

HI , I have some nodes which are Centos 6.5 and am trying to run the monasca-agent via the monasca-setup script. I am able to run the script but it does not work it out /usr/share/monasca/bin/monasca-setup -u xx -p xxx --project_name admin -s monitoring --keystone_url xxx

[openstack-dev] [Monasca] Facing issue in running monasca python client

Hello, I setup the devstack-monasca using the following wiki: https://github.com/openstack/monasca-api/tree/master/devstack So I can see all the OS services and the monansca-api, agent etc. is up and running. I would like to play with some Monascal python-client. So I install python client

[openstack-dev] [Monasca] monasca-threshold smoke is failing

Hello, Trying to install the Monasca through vagrant stuff. On the 'vagrant provision' step, getting the threshold smoke failure. Any clue what might be the cause. I am in Ubuntu 15.10: pradipm@pradipm-ThinkPad-W530:~$ uname -a Linux pradipm-ThinkPad-W530 4.2.0-19-generic #23-Ubuntu SMP Wed

[openstack-dev] [Monasca]: Mid Cycle Doodle

Guys, Please find here the doodle for the mid-cycle: http://doodle.com/poll/yy4unhffy7hi3x67 If we run the meeting Thu/Fri 28/29 we can have the 28 a joint session with Congress. First week of Feb is all open and I guess we need to decide if to do 2 or 3 days. Thanks, Fabio

Re: [openstack-dev] [Monasca][vitrage] Vitrage project

> Sent: Thursday, November 19, 2015 8:51 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Monasca][vitrage] Vitrage project > > Hi Ifat, Thanks for the heads-up. We will start reviewing your > blueprints and providing fee

[openstack-dev] [Monasca]

Guys, I added https://review.openstack.org/#/c/248882/ for review. This should create a stable/kilo release for all the Monasca components. Please review Thanks, Fabio __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Monasca][vitrage] Vitrage project

it ready. See more detailed answers below. Thanks, Ifat. > -Original Message- > From: Hochmuth, Roland M [mailto:roland.hochm...@hpe.com] > Sent: Thursday, November 19, 2015 8:51 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstac

Re: [openstack-dev] [Monasca][vitrage] Vitrage project

Hi Ifat, Thanks for the heads-up. We will start reviewing your blueprints and providing feedback. With respect to the support for AODH, I'm assuming that you are referring too, https://review.openstack.org/#/c/244049/2/specs/mitaka/manage-ceilometer-al arms.rst. For adding support for Monasca, a

[openstack-dev] [Monasca][vitrage] Vitrage project

Hi Monasca developers, As you might have heard in Mitaka Summit, we have started a new project named Vitrage[1]. We would like it to be the Openstack RCA (Root Cause Analysis) Engine for organizing, analyzing and expanding OpenStack alarms & events, yielding insights regarding the root cause

[openstack-dev] [Monasca] Congress + Monasca Meeting

ednesday, October 14, 2015 at 4:07 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit Hi Oğuz, YES this is

Re: [openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit

Hi, On Wed, Oct 14, 2015 at 7:36 AM, Fabio Giannetti (fgiannet) < fgian...@cisco.com> wrote: > Guys, >I have a Cisco room S3 to held a Monasca meeting over the Tokyo Summit. > The time slot is Thursday 4:30pm to 6pm. > Please mark your calendar and see you there. > Fabio > > Will this

Re: [openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit

ev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, October 13, 2015 at 11:22 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [op

[openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit

.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Monasca] Good guide to install Monasca on Centos7? Hello. I'm interested in Monasca, which is the one of a new OpenStack project f

[openstack-dev] [Monasca] Good guide to install Monasca on Centos7?

Hello. I'm interested in Monasca, which is the one of a new OpenStack project for monitoring, and I'd wanted to get an installation guide of the Monasca on CentOS7 environment. I've found a guide which is for Debian (Ubuntu) environment, but I couldn't for the previous one. Could anybody know

Re: [openstack-dev] [monasca] Monasca weekly meetings in IRC, datetime proposal

This is just a reminder that the Monasca weekly meeting will be moving to a new day and use of IRC this week. See, http://eavesdrop.openstack.org/#Monasca_Team_Meeting for more details Day: Weekly on Wednesday Time: 1500 UTC IRC: openstack-meeting-3 Agenda:

[openstack-dev] [monasca] Monasca weekly meetings in IRC, datetime proposal

We have been asked to host the Monasca weekly meetings in IRC. The proposal is to run the weekly meeting on Wednesday at 1500 UTC in IRC channel openstack-meeting-3. A review has been submitted at, https://review.openstack.org/#/c/216904/1/meetings/monasca-team-meeting.yaml. Please +1 if you

[openstack-dev] [Monasca] Minutes for Monasca 8-18-2015

Minutes for the Monasca Weekly Meeting 8-18-2015. https://etherpad.openstack.org/p/Monasca_Weekly_Meeting_8-18-2015 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

[mailto:chd...@redhat.com] Sent: August 12, 2015 15:45 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup On Tue, 11 Aug 2015, Hochmuth, Roland M wrote: It sounds like we should connect up soon. I could

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

[mailto:roland.hochm...@hp.com] Sent: August 16, 2015 09:37 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup Hi Ildikó, That will be great if you can attend. If you do, would it be possible for you to present

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup Ildikó, I think you are correct on the time. The meeting is at 3:00 PM UTC, which is 9:00 AM MDT. Sorry, the time I mentioned was incorrect. Regards --Roland On 8/16/15, 7:42 AM, Ildikó Váncsa ildiko.van...@ericsson.com wrote

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

From: ildiko.van...@ericsson.com To: openstack-dev@lists.openstack.org Date: Fri, 14 Aug 2015 12:57:27 + Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup Hi, I will try to join if I can, I have an overlapping meeting on Tuesdays. In general I think

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

- From: Chris Dent [mailto:chd...@redhat.com] Sent: August 12, 2015 15:45 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup On Tue, 11 Aug 2015, Hochmuth, Roland M wrote: It sounds like we should

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

On Tue, 11 Aug 2015, Hochmuth, Roland M wrote: It sounds like we should connect up soon. I could attend a Ceilometer meeting, or you could attend the Monasca meeting which is held Tuesday mornings at 9:00 MST. I'm away this coming Tuesday, but perhaps some of the other Ceilo people could show

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

On Tue, 11 Aug 2015, Hochmuth, Roland M wrote: The minutes for the meetup are at, https://etherpad.openstack.org/p/monasca_liberty_mid_cycle. If anyone would like to discuss further or would like further clarification please let me know. Thanks for posting that and the linked etherpads. One

Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

Hi Chris, Thanks for reaching out. I would be interested in joint sessions on Monasca and Ceilometer at the Tokyo Summit. We had a joint Ceilometer/Monasca session at the Paris Design Summit and had identified several areas to work on together. It has been a while since we've sync'd up though. We

[openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup

Thanks to all that attended the Monasca Mid-cycle Meetup last week. The meet-up was well attended and we had good overviews, content and discussions. The minutes for the meetup are at, https://etherpad.openstack.org/p/monasca_liberty_mid_cycle. If anyone would like to discuss further or would

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

-To: OpenStack List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Thursday, July 23, 2015 at 2:16 PM To: OpenStack List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Monasca] Monasca mid-cycle meetup Hi

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

@lists.openstack.orgmailto:openstack-...@lists.openstack.or g Date: Thursday, July 23, 2015 at 2:16 PM To: OpenStack List openstack-dev@lists.openstack.orgmailto:openstack-...@lists.openstack.or g Subject: [openstack-dev] [Monasca] Monasca mid-cycle meetup Hi, Is the schedule for this meetup confirmed . https

[openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi, Is the schedule for this meetup confirmed . https://etherpad.openstack.org/p/monasca_liberty_mid_cycle I would like to know if there is any fees involved to join in , or I could just come in . Thanks CHandeep __

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

@lists.openstack.org Subject: Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup Hi, I've had a quick look at the Etherpad which mentions Ceilosca. The name is quite intriguing but I didn't find any reference to it in the Monasca Wiki. Could you tell us a bit more about it? Does it mean that Monasca plans

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

@lists.openstack.orgmailto:openstack-dev@lists.openstack.o r g Subject: [openstack-dev] [Monasca] Monasca mid-cycle meetup Hi, Is the schedule for this meetup confirmed . https://etherpad.openstack.org/p/monasca_liberty_mid_cycle I would like to know if there is any fees involved to join in , or I could just come

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

@lists.openstack.orgmailto:openstack-dev@lists.openstack. o r g Date: Thursday, July 23, 2015 at 2:16 PM To: OpenStack List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack. o r g Subject: [openstack-dev] [Monasca] Monasca mid-cycle meetup Hi, Is the schedule for this meetup confirmed . https

[openstack-dev] [Monasca] Monasca mid-cycle meetup

The Monasca mid-cycle meet up will be held at the HP campus in Fort Collins, CO from August 5-6. Further details on the location, time and tentative agenda can be found at https://etherpad.openstack.org/p/monasca_liberty_mid_cycle Regards --Roland

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi, I've had a quick look at the Etherpad which mentions Ceilosca. The name is quite intriguing but I didn't find any reference to it in the Monasca Wiki. Could you tell us a bit more about it? Does it mean that Monasca plans to expose an API that would be compatible with the Ceilometer API? BR,

[openstack-dev] [Monasca] Authentication through Keystone

Hello, How Monasca is getting authenticated through Keystone? The reason of asking this is: Monasca is in Java, whereas other services (like Cinder) uses the keystone-middleware-authentication (when configured) through api-paste.ini. And the middleware is in python. Does Monasca uses some

Re: [openstack-dev] [monasca] [java]

Dieterly, Deklan wrote: We’ve seen that Swift has introduced components in Go. So, this looks like a precedent for allowing other languages where deemed appropriate. Before we spend many man-hours hacking on the Python components, it seems reasonable to determine if there really exists a

Re: [openstack-dev] [monasca] [java]

On May 15, 2015, at 3:49 AM, Thierry Carrez thie...@openstack.org wrote: Dieterly, Deklan wrote: We’ve seen that Swift has introduced components in Go. So, this looks like a precedent for allowing other languages where deemed appropriate. Before we spend many man-hours hacking on the Python

[openstack-dev] [monasca] [java]

The Monasca project currently has three major components written in Java. Monasca-persister, monasca-thresh, and monasca-api. These components work with Influxdb 0.9.0 and Vertica 7.1. They integrate with Kafka and MySQL. The monasca team is currently bringing the Python versions of these

Re: [openstack-dev] [monasca] [java]

probably cant for a while because of some of these design decisions. Thanks, Kevin From: Dieterly, Deklan [deklan.diete...@hp.com] Sent: Thursday, May 14, 2015 8:29 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [monasca] [java] The Monasca

Re: [openstack-dev] [monasca] [java]

to install, so I probably cant for a while because of some of these design decisions. Thanks, Kevin From: Dieterly, Deklan [deklan.diete...@hp.com] Sent: Thursday, May 14, 2015 8:29 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [monasca

[openstack-dev] [Monasca][Monasca-agent] Logfile format to send matrices

Hello, In Monasca-agent README here https://github.com/stackforge/monasca-agent#introduction It mentioned: Retrieving metrics from log files written in a specific format. Can anyone please point to such a format?Any such pointer would be good. If I understand it correctly, if I point the

<    1   2