subject:"\[openstack\-dev\] \[Monasca\]"

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

2016-06-21 Thread witold.be...@est.fujitsu.com

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, latched, sticky? Something 
else?

I would also welcome feedback on a general implementation idea. Should we make 
it in the same way as the deterministic alarms, by extending the 
AlarmExpression? Or would it be enough to add the property to AlarmDefinition 
(option 2)? I tend to the second solution. The change in the logic of 
monasca-thresh would then be limited to AlarmThresholdingBolt. 
evaluateThreshold as far as I understand. Craig and Roland, could you comment 
on that please?


Cheers
Witek


[1] https://blueprints.launchpad.net/monasca/+spec/locked-alarms


Witold Bedyk
Senior Software Engineer

FUJITSU Enabling Software Technology GmbH
Schwanthalerstr. 75a, 80336 München

Telefon: +49 89 360908-547
Telefax: +49 89 360908-8547
COINS: 7941-6547

Sitz der Gesellschaft: München
AG München, HRB 143325
Geschäftsführer: Dr. Yuji Takada, Hans-Dieter Gatzka, Christian Menk


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-16 Thread László Hegedüs

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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-08 Thread Fabio Giannetti (fgiannet)

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)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 200 700 937
Numeric meeting password: 17093037



Monasca Mid Cycle Day 2
July 20 2016
7am to noon PDT

Webex


Join WebEx meeting:
https://cisco.webex.com/ciscosales/j.php?MTID=m84f9f81d7c1c171be6365716522d
e15e

Meeting number: 205 141 519
Meeting password: 8VyzUiyr

Join by phone  
+1-408-525-6800 Call-in toll number (US/Canada)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 205 141 519
Numeric meeting password: 01558880


See you there.
Fabio


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-02 Thread Fox, Kevin M

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 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, InfluxDB was planning on supporting all their 
>> clustering and HA capabilities in the open-source version, which is one of 
>> the reasons we had added it to Monasca.
>>
>> There has been some discussion on supporting other databases in Monasca. Due 
>> to performance and reliability concerns with InfluxDB, we had started 
>> looking at Cassandra as an alternative. There are several reviews to look at 
>> if you are interested at, 
>> https://review.openstack.org/#/q/monasca+cassandra. Shinya Kawabata has been 
>> looking into Cassandra most recently.
>
> I'm sad that InfluxDB has decided to turn Open Core - but I'm glad that
> work was already underway to look at Cassandra. Well done.

Seems to me that a database that doesn't support aggregate/grouping
operations isn't particularly appropriate for time-series metric
structured data. Am I missing something basic here?

-jay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-02 Thread Jay Pipes


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, InfluxDB was planning on supporting all their 
clustering and HA capabilities in the open-source version, which is one of the 
reasons we had added it to Monasca.

There has been some discussion on supporting other databases in Monasca. Due to 
performance and reliability concerns with InfluxDB, we had started looking at 
Cassandra as an alternative. There are several reviews to look at if you are 
interested at, https://review.openstack.org/#/q/monasca+cassandra. Shinya 
Kawabata has been looking into Cassandra most recently.


I'm sad that InfluxDB has decided to turn Open Core - but I'm glad that
work was already underway to look at Cassandra. Well done.


Seems to me that a database that doesn't support aggregate/grouping 
operations isn't particularly appropriate for time-series metric 
structured data. Am I missing something basic here?


-jay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-02 Thread Jay Pipes


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, InfluxDB was planning on supporting all their 
clustering and HA capabilities in the open-source version, which is one of the 
reasons we had added it to Monasca.

There has been some discussion on supporting other databases in Monasca. Due to 
performance and reliability concerns with InfluxDB, we had started looking at 
Cassandra as an alternative. There are several reviews to look at if you are 
interested at, https://review.openstack.org/#/q/monasca+cassandra. Shinya 
Kawabata has been looking into Cassandra most recently.


I'm sad that InfluxDB has decided to turn Open Core - but I'm glad that
work was already underway to look at Cassandra. Well done.


I looked at OpenTSDB several years ago. There are several concerns with 
OpenTSDB, but the more significant one for us has been around deployment, as it 
requires HBase which is built on HDFS. If you already have Hadoop, HDFS and 
Hbase deployed then OpenTSDB is an incremental addition, but if you don't, it 
is a significant investment. At the time that I had evaluated OpenTSDB 
performance was not on-par with the other alternatives I considered.

Regards --Roland

From: Jaesuk Ahn mailto:bluejay@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, May 30, 2016 at 9:59 AM
To: OpenStack List 
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 our current and future customers, we’ll be offering clustering and high 
availability through Influx Cloud, our managed hosting offering, and Influx 
Enterprise, our on-premise offering, in the coming months.”


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 use.

With this update stating “influxDB open source sw version will not have 
clustering / ha feature”,
I would like to know if there has been any discussion among monasca community 
to add more database backend rather than influxDB, especially OpenTSDB.


Thank you.





--
Jaesuk Ahn, Ph.D.
Software Defined Infra Tech. Lab.
SKT
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-02 Thread Monty Taylor

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, InfluxDB was planning on supporting all their 
> clustering and HA capabilities in the open-source version, which is one of 
> the reasons we had added it to Monasca.
> 
> There has been some discussion on supporting other databases in Monasca. Due 
> to performance and reliability concerns with InfluxDB, we had started looking 
> at Cassandra as an alternative. There are several reviews to look at if you 
> are interested at, https://review.openstack.org/#/q/monasca+cassandra. Shinya 
> Kawabata has been looking into Cassandra most recently.

I'm sad that InfluxDB has decided to turn Open Core - but I'm glad that
work was already underway to look at Cassandra. Well done.

> I looked at OpenTSDB several years ago. There are several concerns with 
> OpenTSDB, but the more significant one for us has been around deployment, as 
> it requires HBase which is built on HDFS. If you already have Hadoop, HDFS 
> and Hbase deployed then OpenTSDB is an incremental addition, but if you 
> don't, it is a significant investment. At the time that I had evaluated 
> OpenTSDB performance was not on-par with the other alternatives I considered.
> 
> Regards --Roland
> 
> From: Jaesuk Ahn mailto:bluejay@gmail.com>>
> Reply-To: OpenStack List 
> mailto:openstack-dev@lists.openstack.org>>
> Date: Monday, May 30, 2016 at 9:59 AM
> To: OpenStack List 
> 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 our current and future customers, we’ll be offering clustering and high 
> availability through Influx Cloud, our managed hosting offering, and Influx 
> Enterprise, our on-premise offering, in the coming months.”
> 
> 
> 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 use.
> 
> With this update stating “influxDB open source sw version will not have 
> clustering / ha feature”,
> I would like to know if there has been any discussion among monasca community 
> to add more database backend rather than influxDB, especially OpenTSDB.
> 
> 
> Thank you.
> 
> 
> 
> 
> 
> --
> Jaesuk Ahn, Ph.D.
> Software Defined Infra Tech. Lab.
> SKT
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-02 Thread Hochmuth, Roland M

Hi László, as another alternative you could achieve something similar in 
Monasca, without using the InfluxDB Relay project, by configuring multiple 
Monasca Persisters each in a different consumer group, and with it's own 
independent InfluxDB server instance. Not sure which is the better approach. I 
believe the answer to your question is that multiple instances of a metrics 
database in Monasca is already supported. Regards --Roland

From: László Hegedüs 
mailto:laszlo.hege...@ericsson.com>>
Organization: Ericsson AB
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, June 2, 2016 at 12:51 AM
To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Subject: 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 that point forward our clustering efforts will 
be focused on the closed source Influx Enterprise offering."

https://github.com/influxdata/influxdb-relay/blob/master/README.md

So there is still an option to have it HA.

Of course it would be nice if multiple databases were supported by Monasca.

On 05/31/2016 09:30 AM, Julien Danjou wrote:

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 use.


Indeed, it's a shame than there's nobody developing an opensource TSDB
based on open technologies that is used in OpenStack, which supports
high availability, clustering, and a ton of other features…

Wait… what about OpenStack Gnocchi?

  http://gnocchi.xyz/

:)





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-02 Thread Hochmuth, Roland M

My understanding of Prometheus is that it doesn't support HA, fault-tolerant 
clustering either.

The recommendation from the Prometheus developers for HA and 
fault-tolerance/reliability is to run multiple Prometheus servers with one 
server scraping metrics from another server.

To do something similar in Monasca you could run multiple instances of InfluxDB 
using the Kafka metrics topic and multiple consumer groups to replicate all 
metrics to each InfluxDB server, or use the InfluxDB Relay project at, 
https://github.com/influxdata/influxdb-relay.

The non-clustered version of InfluxDB remains free and open-source. It is only 
the clustered version of InfluxDB that has now moved to a closed source license.


From: Martinx - ジェームズ 
mailto:thiagocmarti...@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, May 30, 2016 at 7:20 PM
To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Monasca] influxDB clustering and HA will be 
"commercial option".



On 30 May 2016 at 11:59, Jaesuk Ahn 
mailto:bluejay@gmail.com>> 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 through Influx Cloud, our managed hosting offering, and Influx 
Enterprise, our on-premise offering, in the coming months.”


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 use.

With this update stating “influxDB open source sw version will not have 
clustering / ha feature”,
I would like to know if there has been any discussion among monasca community 
to add more database backend rather than influxDB, especially OpenTSDB.


Thank you.





--
Jaesuk Ahn, Ph.D.
Software Defined Infra Tech. Lab.
SKT


What about Prometheus?

https://prometheus.io/

https://prometheus.io/docs/introduction/comparison/

Cheers!
Thiago
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-02 Thread Hochmuth, Roland M

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, InfluxDB was planning on supporting all their 
clustering and HA capabilities in the open-source version, which is one of the 
reasons we had added it to Monasca.

There has been some discussion on supporting other databases in Monasca. Due to 
performance and reliability concerns with InfluxDB, we had started looking at 
Cassandra as an alternative. There are several reviews to look at if you are 
interested at, https://review.openstack.org/#/q/monasca+cassandra. Shinya 
Kawabata has been looking into Cassandra most recently.

I looked at OpenTSDB several years ago. There are several concerns with 
OpenTSDB, but the more significant one for us has been around deployment, as it 
requires HBase which is built on HDFS. If you already have Hadoop, HDFS and 
Hbase deployed then OpenTSDB is an incremental addition, but if you don't, it 
is a significant investment. At the time that I had evaluated OpenTSDB 
performance was not on-par with the other alternatives I considered.

Regards --Roland

From: Jaesuk Ahn mailto:bluejay@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, May 30, 2016 at 9:59 AM
To: OpenStack List 
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 our current and future customers, we’ll be offering clustering and high 
availability through Influx Cloud, our managed hosting offering, and Influx 
Enterprise, our on-premise offering, in the coming months.”


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 use.

With this update stating “influxDB open source sw version will not have 
clustering / ha feature”,
I would like to know if there has been any discussion among monasca community 
to add more database backend rather than influxDB, especially OpenTSDB.


Thank you.





--
Jaesuk Ahn, Ph.D.
Software Defined Infra Tech. Lab.
SKT
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-01 Thread László Hegedüs


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 that point forward our 
clustering efforts will be focused on the closed source Influx 
Enterprise offering."


https://github.com/influxdata/influxdb-relay/blob/master/README.md

So there is still an option to have it HA.

Of course it would be nice if multiple databases were supported by Monasca.

On 05/31/2016 09:30 AM, Julien Danjou wrote:

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 use.

Indeed, it's a shame than there's nobody developing an opensource TSDB
based on open technologies that is used in OpenStack, which supports
high availability, clustering, and a ton of other features…

Wait… what about OpenStack Gnocchi?

   http://gnocchi.xyz/

:)



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-01 Thread Pradip Mukhopadhyay

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 Service
Unavailable", "title": "Service Unavailable"}
HTTPException code=503 message={"message": "The server is currently
unavailable. Please try again at a later time.\n\n\n", "code":
"503 Service Unavailable", "title": "Service Unavailable"}


stack@scsor0002143001-pradipm:~/devstack$ openstack user list
+--+---+
| ID   | Name  |
+--+---+
| f29f1814fbc34855ba684a2810434580 | admin |
| a9c0c928caff4345b2aa266a30397487 | demo  |
| f172a9e25d2542c895fbc43d73164a9d | alt_demo  |
| 6cfdec260fe94c4487071f9e7915b359 | nova  |
| 1a66c71e946442f2a061c88cef566c30 | glance|
| bdb1aed519504b249cffd27a2c05f0fa | cinder|
| 5c9cf5cedcb244dbafbe272f691eaf2f | mini-mon  |
| a349c41c99fa447b96d1d2a56b12c3d4 | monasca-agent |
+--+---+


Here is the local.conf that I have used:



# BEGIN DEVSTACK LOCAL.CONF CONTENTS

[[local|localrc]]
ADMIN_PASSWORD=netapp
MYSQL_PASSWORD=$ADMIN_PASSWORD
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD
GUEST_PASSWORD=$ADMIN_PASSWORD
MYSQL_HOST=127.0.0.1
MYSQL_USER=root
RABBIT_HOST=127.0.0.1
SERVICE_TOKEN=111222333444

LOGFILE=$DEST/logs/stack.sh.log
LOGDIR=$DEST/logs
LOG_COLOR=False
SCREEN_LOGDIR=$DEST/logs/screen
LOGDAYS=1

# The following two variables allow switching between Java and Python for
the implementations
# of the Monasca API and the Monasca Persister. If these variables are not
set, then the
# default is to install the Python implementations of both the Monasca API
and the Monasca Persister.

# Uncomment one of the following two lines to choose Java or Python for the
Monasca API.
#MONASCA_API_IMPLEMENTATION_LANG=${MONASCA_API_IMPLEMENTATION_LANG:-java}
MONASCA_API_IMPLEMENTATION_LANG=${MONASCA_API_IMPLEMENTATION_LANG:-python}

# Uncomment of the following two lines to choose Java or Python for the
Monasca Pesister.
#MONASCA_PERSISTER_IMPLEMENTATION_LANG=${MONASCA_PERSISTER_IMPLEMENTATION_LANG:-java}
MONASCA_PERSISTER_IMPLEMENTATION_LANG=${MONASCA_PERSISTER_IMPLEMENTATION_LANG:-python}

MONASCA_METRICS_DB=${MONASCA_METRICS_DB:-influxdb}
# MONASCA_METRICS_DB=${MONASCA_METRICS_DB:-vertica}

# This line will enable all of Monasca.
enable_plugin monasca-api git://git.openstack.org/openstack/monasca-api







--pradip
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-01 Thread Sundaram, Venkat (Venkat Sundaram (TSV))

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 there, just that 
it would be more significant (new API endpoint).

Yes, you are right about the retention part, that was mean’t only as an 
example. I removed it from the blueprint now.

Thanks,
TSV





On 5/31/16, 7:08 AM, "Witek Bedyk"  wrote:

>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 allow the operator add any 
>information one needs. I like the idea of adding the 'attributes' 
>dictionary, but we would need it per message, not only per request (the 
>same story as we had with global and local dimensions).
>
>ad. 2
>As we want to change the target where the API writes the data, we could 
>use perhaps the path parameter for that. The request could look like:
>
>POST /v3.0/logs/topics/{kafka_topic_name}
>
>I don't think we should send 'retention' with every request, instead the 
>Kafka topic should be configured accordingly, but I understand it was 
>just an example, right?
>
>
>Cheers
>Witek
>
>
>[1] 
>https://blueprints.launchpad.net/monasca/+spec/publish-logs-to-topic-selectively
>
>
>-- 
>FUJITSU Enabling Software Technology GmbH
>Schwanthalerstr. 75a, 80336 München
>
>Telefon: +49 89 360908-547
>Telefax: +49 89 360908-8547
>COINS: 7941-6547
>
>Sitz der Gesellschaft: München
>AG München, HRB 143325
>Geschäftsführer: Dr. Yuji Takada, Hans-Dieter Gatzka, Christian Menk
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-31 Thread Witek Bedyk


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 allow the operator add any 
information one needs. I like the idea of adding the 'attributes' 
dictionary, but we would need it per message, not only per request (the 
same story as we had with global and local dimensions).


ad. 2
As we want to change the target where the API writes the data, we could 
use perhaps the path parameter for that. The request could look like:


POST /v3.0/logs/topics/{kafka_topic_name}

I don't think we should send 'retention' with every request, instead the 
Kafka topic should be configured accordingly, but I understand it was 
just an example, right?



Cheers
Witek


[1] 
https://blueprints.launchpad.net/monasca/+spec/publish-logs-to-topic-selectively



--
FUJITSU Enabling Software Technology GmbH
Schwanthalerstr. 75a, 80336 München

Telefon: +49 89 360908-547
Telefax: +49 89 360908-8547
COINS: 7941-6547

Sitz der Gesellschaft: München
AG München, HRB 143325
Geschäftsführer: Dr. Yuji Takada, Hans-Dieter Gatzka, Christian Menk

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-31 Thread Julien Danjou

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 use.

Indeed, it's a shame than there's nobody developing an opensource TSDB
based on open technologies that is used in OpenStack, which supports
high availability, clustering, and a ton of other features…

Wait… what about OpenStack Gnocchi?

  http://gnocchi.xyz/

:)

-- 
Julien Danjou
-- Free Software hacker
-- https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-30 Thread Martinx - ジェームズ

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 through Influx Cloud, our managed hosting offering, and
> Influx Enterprise, our on-premise offering, in the coming months.”
>
>
> 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 use.
>
> With this update stating “influxDB open source sw version will not have
> clustering / ha feature”,
> I would like to know if there has been any discussion among monasca
> community to add more database backend rather than influxDB, especially
> OpenTSDB.
>
>
> Thank you.
>
>
>
>
>
> --
> Jaesuk Ahn, Ph.D.
> Software Defined Infra Tech. Lab.
> SKT
>


What about Prometheus?

https://prometheus.io/

https://prometheus.io/docs/introduction/comparison/

Cheers!
Thiago
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-30 Thread Jaesuk Ahn

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 on-premise offering, in the coming months.”


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 use.

With this update stating “influxDB open source sw version will not have
clustering / ha feature”,
I would like to know if there has been any discussion among monasca
community to add more database backend rather than influxDB, especially
OpenTSDB.


Thank you.





-- 
Jaesuk Ahn, Ph.D.
Software Defined Infra Tech. Lab.
SKT
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-13 Thread Erickson

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 -
De: "Witek Bedyk"
Para: "Erickson" , openstack-dev@lists.openstack.org
Enviadas: Sexta-feira, 13 de maio de 2016 12:44:33
Assunto: [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 metrics. E.g. A metric is
generated every time when an error in the given log-file appears. Such
metric is different from the standard Monasca metric in the way that it
does not appear on the regular, periodic basis. You can read a little
more about it here [1], but the blueprint itself is outdated and the
implementation changed.

The main logic for alarm creation has been moved to
"deterministic_alarm" topic [2] and Tomasz works currently on that. Your
reviews are very welcome.

The changes in "sporadic_metric" topic [3] are meant to give the user
information that a given metric is of sporadic (non-periodic) character.
It will have no influence on monasca-thresh. Tomasz has put the code
that he already had in this topic but he must focus on
"deterministic_alarm" now, so please feel free to submit your patch-sets
if you want. Apart from the existing changes also changes in monasca-ui
and python-monascaclient repos are needed to display the 'sporadic'
attribute of the metric for the user. You could compare this change in
monasca-ui [4].

If you have questions to the implementation of "sporadic metrics", I
think the existing changes in gerrit [3] are the best place for exchange
and communication at the moment. Actually I should have updated the
blueprint for that. Sorry, my fault.

So, have fun with the code :)

Cheers
Witek

[1] https://blueprints.launchpad.net/monasca/+spec/alarmsonlogs
[2] https://review.openstack.org/#/q/topic:deterministic_alarm
[3] https://review.openstack.org/#/q/topic:sporadic_metric
[4]
https://review.openstack.org/#/c/314420/3/monitoring/alarmdefs/templates/alarmdefs/_detail.html

P.S. Please note, I will be in holidays for the next two weeks.

--
FUJITSU Enabling Software Technology GmbH
Schwanthalerstr. 75a, 80336 München

Telefon: +49 89 360908-547
Telefax: +49 89 360908-8547
COINS: 7941-6547

Sitz der Gesellschaft: München
AG München, HRB 143325
Geschäftsführer: Dr. Yuji Takada, Hans-Dieter Gatzka

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Monasca] Sporadic metrics

2016-05-13 Thread Witek Bedyk

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 main logic for alarm creation has been moved to
"deterministic_alarm" topic [2] and Tomasz works currently on that. Your
reviews are very welcome.

So, have fun with the code :)

Cheers
Witek

P.S. Please note, I will be in holidays for the next two weeks.

--
FUJITSU Enabling Software Technology GmbH
Schwanthalerstr. 75a, 80336 München

Telefon: +49 89 360908-547
Telefax: +49 89 360908-8547
COINS: 7941-6547

Sitz der Gesellschaft: München
AG München, HRB 143325
Geschäftsführer: Dr. Yuji Takada, Hans-Dieter Gatzka

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

2016-04-05 Thread Hochmuth, Roland M

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 available at

monasca-common: https://review.openstack.org/#/c/301925/
monasca-api: https://review.openstack.org/#/c/301925


Assuming that is an acceptable method, we can also update 

monasca-thresh
monasca-persister

using the same approach. 

Note, I thought he was going to try and pull the tag from git, but maybe that 
didn't turn out OK.

Assuming those work, then at least we would have jars available that match the 
tags for the Mitaka release.








On 4/5/16, 1:10 PM, "Clark Boylan"  wrote:

>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 about the jars at this point. We had started
>> to discuss a plan to manually copy the jars over to the proper location.
>> I was hoping we could just do this temporarily for Mitaka. Unfortunately,
>> there are a few steps that need to be resolved prior to doing that.
>> 
>> Currently, the java builds overwrite the previous build. The version
>> number of the jar that is built, matches the version in the pom file.
>> See, http://tarballs.openstack.org/ci/monasca-thresh/, for an example.
>> 
>> What we are looking into is modifying the pom files for the java repos,
>> so that the version number of the jar matches the tag when built (not
>> what is in the pom), and modifying the name of the jar, by removing the
>> word SNAPSHOT.
>> 
>> If we do that, we think we can get a name for the jar with a version that
>> matches the latest tag on whatever branch is being used. This should be
>> similar to how the Python wheels that are named.
>> 
>> We could manually copy in the short-term. But the goal is to add an
>> automatic copy to the appropriate location in,
>> http://tarballs.openstack.org/.
>> 
>> Unfortunately, for the java related deliverables, it sounds like we are a
>> little late for all this to get done prior to Mitaka. Not sure if this
>> can be added post Mitaka.
>
>The infra team has to publish jars as well and has a set of jobs for
>that at [0]. It should figure out your versions from git as well and set
>them all automagically with the correct maven configuration. You might
>be able to just add these jobs assuming you use maven.
>
>[0]
>https://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/maven-plugin-jobs.yaml
>
>Clark
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-04-05 Thread Clark Boylan

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 about the jars at this point. We had started
> to discuss a plan to manually copy the jars over to the proper location.
> I was hoping we could just do this temporarily for Mitaka. Unfortunately,
> there are a few steps that need to be resolved prior to doing that.
> 
> Currently, the java builds overwrite the previous build. The version
> number of the jar that is built, matches the version in the pom file.
> See, http://tarballs.openstack.org/ci/monasca-thresh/, for an example.
> 
> What we are looking into is modifying the pom files for the java repos,
> so that the version number of the jar matches the tag when built (not
> what is in the pom), and modifying the name of the jar, by removing the
> word SNAPSHOT.
> 
> If we do that, we think we can get a name for the jar with a version that
> matches the latest tag on whatever branch is being used. This should be
> similar to how the Python wheels that are named.
> 
> We could manually copy in the short-term. But the goal is to add an
> automatic copy to the appropriate location in,
> http://tarballs.openstack.org/.
> 
> Unfortunately, for the java related deliverables, it sounds like we are a
> little late for all this to get done prior to Mitaka. Not sure if this
> can be added post Mitaka.

The infra team has to publish jars as well and has a set of jobs for
that at [0]. It should figure out your versions from git as well and set
them all automagically with the correct maven configuration. You might
be able to just add these jobs assuming you use maven.

[0]
https://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/maven-plugin-jobs.yaml

Clark

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-04-05 Thread Hochmuth, Roland M

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 manually copy the jars over to the proper location. I was 
hoping we could just do this temporarily for Mitaka. Unfortunately, there are a 
few steps that need to be resolved prior to doing that.

Currently, the java builds overwrite the previous build. The version number of 
the jar that is built, matches the version in the pom file. See, 
http://tarballs.openstack.org/ci/monasca-thresh/, for an example.

What we are looking into is modifying the pom files for the java repos, so that 
the version number of the jar matches the tag when built (not what is in the 
pom), and modifying the name of the jar, by removing the word SNAPSHOT.

If we do that, we think we can get a name for the jar with a version that 
matches the latest tag on whatever branch is being used. This should be similar 
to how the Python wheels that are named.

We could manually copy in the short-term. But the goal is to add an automatic 
copy to the appropriate location in, http://tarballs.openstack.org/.

Unfortunately, for the java related deliverables, it sounds like we are a 
little late for all this to get done prior to Mitaka. Not sure if this can be 
added post Mitaka.

Regards --Roland

On 4/5/16, 3:15 AM, "Thierry Carrez"  wrote:

>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. 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. monasca-log-api

 I'm not sure we should attempt to resolve these two repos for the Mitaka 
 release, but we can try. It might be too late. They aren't in heavy usage 
 and are relatively new.
>>>
>>> I think for those you were missing the "venv" environment in tox.ini
>>> that the jobs use to run arbitrary commands. Have a look at some of the
>>> other repos for an example of how to set that up, or ask the infra team
>>> (I'm not sure where it's documented, unfortunately, or I would direct
>>> you there).
>>
>> The monasca-log-api venv problem has been fixed in:
>> https://review.openstack.org/#/c/299936/
>
>Thanks dims!
>
>Roland: Now we'll need a 0.0.3 tag request on stable/mitaka to trigger a 
>tarball rebuild.
>
>If done quickly, that should let us keep Monasca deliverables in Mitaka.
>
>-- 
>Thierry Carrez (ttx)
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-04-05 Thread Thierry Carrez


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. 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. monasca-log-api

I'm not sure we should attempt to resolve these two repos for the Mitaka 
release, but we can try. It might be too late. They aren't in heavy usage and 
are relatively new.


I think for those you were missing the "venv" environment in tox.ini
that the jobs use to run arbitrary commands. Have a look at some of the
other repos for an example of how to set that up, or ask the infra team
(I'm not sure where it's documented, unfortunately, or I would direct
you there).


The monasca-log-api venv problem has been fixed in:
https://review.openstack.org/#/c/299936/


Thanks dims!

Roland: Now we'll need a 0.0.3 tag request on stable/mitaka to trigger a 
tarball rebuild.


If done quickly, that should let us keep Monasca deliverables in Mitaka.

--
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-04-04 Thread Davanum Srinivas

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
>>
>> 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. monasca-log-api
>>
>> I'm not sure we should attempt to resolve these two repos for the Mitaka 
>> release, but we can try. It might be too late. They aren't in heavy usage 
>> and are relatively new.
>
> I think for those you were missing the "venv" environment in tox.ini
> that the jobs use to run arbitrary commands. Have a look at some of the
> other repos for an example of how to set that up, or ask the infra team
> (I'm not sure where it's documented, unfortunately, or I would direct
> you there).

The monasca-log-api venv problem has been fixed in:
https://review.openstack.org/#/c/299936/


>>
>>
>> monasca-thresh is a pure Java component.
>>
>> In the process of looking at monasca-thresh it looks like there is a general 
>> issue with all the Java deliverables. All the Java jars are built and 
>> uploaded in their respective folders such as, 
>> http://tarballs.openstack.org/ci/monasca-thresh/. Note the "ci". However, we 
>> don't move the jars that are in this directory up a level to 
>> http://tarballs.openstack.org/monasca-thresh/. It looks like that needs to 
>> get resolved.
>>
>>
>> A proposal that I think would resolve this is as follows:
>>
>> 1. Update versions of Java jars in the pom.xml for each project to something 
>> like 2.0 on the stable/mitaka branch. This will result in a new jar file 
>> being created with a nice version and name. Note, this step isn't necessary, 
>> but if we did this we would have a nice version for Mitaka.
>
> If the artifacts exist but are in the "wrong" place, maybe someone
> from the infra team can copy them into place for you. Then if you
> give us an example of what the filenames are, the release team can
> update the tools in the releases repo to generate links to them (I
> assume, for example, they are not .tar.gz files).
>
>> 2. Figure out how to copy the jars over to their respective folders in 
>> http://tarballs.openstak.org. For Python I think the script that does this 
>> is publish-to-pypi, but for Java code, not sure exactly what needs to be 
>> done.
>
> Yes, you need to work with infra to set up the necessary build scripts.
> It's probably not realistic to do this in the next week, but if you get
> the existing files copied into place then you can work on updating the
> job before the Newton-1 milestone tagging deadline.
>
> Doug
>
>>
>> I think the two steps above would get us in compliance again for 
>> monasca-thresh and all the Java code in the other repos.
>>
>> Does that seem like a reasonable plan at this point?
>>
>> Regards --Roland
>>
>> On 4/1/16, 2:36 PM, "Doug Hellmann"  wrote:
>>
>> >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 to the 
>> >> Monasca API and use Monasca as a storage backend. We don't create a pypi 
>> >> for this component.
>> >
>> >How do you users receive that code and install it? We at least need
>> >a tarball built. If you don't want to publish to pypi, you can use
>> >the job definitions that the Python server projects use to build
>> >artifacts.
>> >
>> >> monasca-log-api is probably not set up completely, but it should be 
>> >> similar to the monasca-api.
>> >>
>> >> monasca-thresh remains purely Java code. There is a build, but it isn't a 
>> >> Python build so there isn't a tox.ini. Not sure how to deliver this, but 
>> >> the current java build overwrites the jar each time it builds so it 
>> >> sounds like that would need to be fixed.
>> >
>> >Are those JAR files going somewhere we could link to?
>> >
>> >>
>> >> I guess, judging by the issues, I don't quite understand what 
>> >> "deliverables" are. I was thinking it was the tagged code, but obviously 
>> >> it includes the build too. It sounds like we have more work ahead of us.
>> >
>> >Most of our distributors want a tarball or sdist or other artifact they
>> >can use to build a package from. For the Python-based apps, we have
>> >templates you can use in the zuul/layout.yaml file to introduce those
>> >jobs into the right zuul queues. The release or infra teams can help you
>> >identify the right template to use.
>> >
>> >> Let me know how you want to proceed.
>> >
>> >We only want to be linking to things we're actually publishing. The
>> >first patch I mentioned removes the links so the Monasca projects
>> >that don't have

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

2016-04-02 Thread Doug Hellmann

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 Python deliverables except for the following two repos:
> 
> 1. monasca-ceilometer
> 2. monasca-log-api
> 
> I'm not sure we should attempt to resolve these two repos for the Mitaka 
> release, but we can try. It might be too late. They aren't in heavy usage and 
> are relatively new.

I think for those you were missing the "venv" environment in tox.ini
that the jobs use to run arbitrary commands. Have a look at some of the
other repos for an example of how to set that up, or ask the infra team
(I'm not sure where it's documented, unfortunately, or I would direct
you there).

> 
> 
> monasca-thresh is a pure Java component.
> 
> In the process of looking at monasca-thresh it looks like there is a general 
> issue with all the Java deliverables. All the Java jars are built and 
> uploaded in their respective folders such as, 
> http://tarballs.openstack.org/ci/monasca-thresh/. Note the "ci". However, we 
> don't move the jars that are in this directory up a level to 
> http://tarballs.openstack.org/monasca-thresh/. It looks like that needs to 
> get resolved.
> 
> 
> A proposal that I think would resolve this is as follows:
> 
> 1. Update versions of Java jars in the pom.xml for each project to something 
> like 2.0 on the stable/mitaka branch. This will result in a new jar file 
> being created with a nice version and name. Note, this step isn't necessary, 
> but if we did this we would have a nice version for Mitaka.

If the artifacts exist but are in the "wrong" place, maybe someone
from the infra team can copy them into place for you. Then if you
give us an example of what the filenames are, the release team can
update the tools in the releases repo to generate links to them (I
assume, for example, they are not .tar.gz files).

> 2. Figure out how to copy the jars over to their respective folders in 
> http://tarballs.openstak.org. For Python I think the script that does this is 
> publish-to-pypi, but for Java code, not sure exactly what needs to be done.

Yes, you need to work with infra to set up the necessary build scripts.
It's probably not realistic to do this in the next week, but if you get
the existing files copied into place then you can work on updating the
job before the Newton-1 milestone tagging deadline.

Doug

> 
> I think the two steps above would get us in compliance again for 
> monasca-thresh and all the Java code in the other repos.
> 
> Does that seem like a reasonable plan at this point?
> 
> Regards --Roland
> 
> On 4/1/16, 2:36 PM, "Doug Hellmann"  wrote:
> 
> >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 to the 
> >> Monasca API and use Monasca as a storage backend. We don't create a pypi 
> >> for this component.
> >
> >How do you users receive that code and install it? We at least need
> >a tarball built. If you don't want to publish to pypi, you can use
> >the job definitions that the Python server projects use to build
> >artifacts.
> >
> >> monasca-log-api is probably not set up completely, but it should be 
> >> similar to the monasca-api.
> >> 
> >> monasca-thresh remains purely Java code. There is a build, but it isn't a 
> >> Python build so there isn't a tox.ini. Not sure how to deliver this, but 
> >> the current java build overwrites the jar each time it builds so it sounds 
> >> like that would need to be fixed.
> >
> >Are those JAR files going somewhere we could link to?
> >
> >> 
> >> I guess, judging by the issues, I don't quite understand what 
> >> "deliverables" are. I was thinking it was the tagged code, but obviously 
> >> it includes the build too. It sounds like we have more work ahead of us.
> >
> >Most of our distributors want a tarball or sdist or other artifact they
> >can use to build a package from. For the Python-based apps, we have
> >templates you can use in the zuul/layout.yaml file to introduce those
> >jobs into the right zuul queues. The release or infra teams can help you
> >identify the right template to use.
> >
> >> Let me know how you want to proceed.
> >
> >We only want to be linking to things we're actually publishing. The
> >first patch I mentioned removes the links so the Monasca projects
> >that don't have builds. The second patch removes the projects
> >entirely, but if we can update the page to link to a downloadable
> >artifact (rather than just a git repo tag) then we can keep the
> >projects in the list. We can get downloadable artifacts by having
> >you add build jobs and t

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

2016-04-01 Thread Hochmuth, Roland M

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. monasca-log-api

I'm not sure we should attempt to resolve these two repos for the Mitaka 
release, but we can try. It might be too late. They aren't in heavy usage and 
are relatively new.

monasca-thresh is a pure Java component.

In the process of looking at monasca-thresh it looks like there is a general 
issue with all the Java deliverables. All the Java jars are built and uploaded 
in their respective folders such as, 
http://tarballs.openstack.org/ci/monasca-thresh/. Note the "ci". However, we 
don't move the jars that are in this directory up a level to 
http://tarballs.openstack.org/monasca-thresh/. It looks like that needs to get 
resolved.

A proposal that I think would resolve this is as follows:

1. Update versions of Java jars in the pom.xml for each project to something 
like 2.0 on the stable/mitaka branch. This will result in a new jar file being 
created with a nice version and name. Note, this step isn't necessary, but if 
we did this we would have a nice version for Mitaka.
2. Figure out how to copy the jars over to their respective folders in 
http://tarballs.openstak.org. For Python I think the script that does this is 
publish-to-pypi, but for Java code, not sure exactly what needs to be done.

I think the two steps above would get us in compliance again for monasca-thresh 
and all the Java code in the other repos.

Does that seem like a reasonable plan at this point?

Regards --Roland

On 4/1/16, 2:36 PM, "Doug Hellmann"  wrote:

>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 to the Monasca 
>> API and use Monasca as a storage backend. We don't create a pypi for this 
>> component.
>
>How do you users receive that code and install it? We at least need
>a tarball built. If you don't want to publish to pypi, you can use
>the job definitions that the Python server projects use to build
>artifacts.
>
>> monasca-log-api is probably not set up completely, but it should be similar 
>> to the monasca-api.
>> 
>> monasca-thresh remains purely Java code. There is a build, but it isn't a 
>> Python build so there isn't a tox.ini. Not sure how to deliver this, but the 
>> current java build overwrites the jar each time it builds so it sounds like 
>> that would need to be fixed.
>
>Are those JAR files going somewhere we could link to?
>
>> 
>> I guess, judging by the issues, I don't quite understand what "deliverables" 
>> are. I was thinking it was the tagged code, but obviously it includes the 
>> build too. It sounds like we have more work ahead of us.
>
>Most of our distributors want a tarball or sdist or other artifact they
>can use to build a package from. For the Python-based apps, we have
>templates you can use in the zuul/layout.yaml file to introduce those
>jobs into the right zuul queues. The release or infra teams can help you
>identify the right template to use.
>
>> Let me know how you want to proceed.
>
>We only want to be linking to things we're actually publishing. The
>first patch I mentioned removes the links so the Monasca projects
>that don't have builds. The second patch removes the projects
>entirely, but if we can update the page to link to a downloadable
>artifact (rather than just a git repo tag) then we can keep the
>projects in the list. We can get downloadable artifacts by having
>you add build jobs and then having the release team tag again as a
>new release candidate, or if there are already artifacts somewhere
>(like the JAR file) we can set up the releases repo to link there.
>
>Doug
>
>> 
>> Regards --Roland
>> 
>> On 4/1/16, 1:21 PM, "Doug Hellmann"  wrote:
>> 
>> >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 configured in
>> >openstack-infra/project-config/zuul/layout.yaml or don't have tox.ini
>> >set up correctly (or both), so it's not clear how tagging is producing
>> >a release for you.
>> >
>> >For now, we are disabling links to the artifacts for those repos
>> >via https://review.openstack.org/300457 but we're also planning to
>> >remove them from the official Mitaka page since there don't
>> >appear to be any actual related deliverables
>> >(https://review.openstack.org/300619).
>> >
>> >It would be good to understand what your intent is for builds. Can

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

2016-04-01 Thread Doug Hellmann

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 to the Monasca 
> API and use Monasca as a storage backend. We don't create a pypi for this 
> component.

How do you users receive that code and install it? We at least need
a tarball built. If you don't want to publish to pypi, you can use
the job definitions that the Python server projects use to build
artifacts.

> monasca-log-api is probably not set up completely, but it should be similar 
> to the monasca-api.
> 
> monasca-thresh remains purely Java code. There is a build, but it isn't a 
> Python build so there isn't a tox.ini. Not sure how to deliver this, but the 
> current java build overwrites the jar each time it builds so it sounds like 
> that would need to be fixed.

Are those JAR files going somewhere we could link to?

> 
> I guess, judging by the issues, I don't quite understand what "deliverables" 
> are. I was thinking it was the tagged code, but obviously it includes the 
> build too. It sounds like we have more work ahead of us.

Most of our distributors want a tarball or sdist or other artifact they
can use to build a package from. For the Python-based apps, we have
templates you can use in the zuul/layout.yaml file to introduce those
jobs into the right zuul queues. The release or infra teams can help you
identify the right template to use.

> Let me know how you want to proceed.

We only want to be linking to things we're actually publishing. The
first patch I mentioned removes the links so the Monasca projects
that don't have builds. The second patch removes the projects
entirely, but if we can update the page to link to a downloadable
artifact (rather than just a git repo tag) then we can keep the
projects in the list. We can get downloadable artifacts by having
you add build jobs and then having the release team tag again as a
new release candidate, or if there are already artifacts somewhere
(like the JAR file) we can set up the releases repo to link there.

Doug

> 
> Regards --Roland
> 
> On 4/1/16, 1:21 PM, "Doug Hellmann"  wrote:
> 
> >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 configured in
> >openstack-infra/project-config/zuul/layout.yaml or don't have tox.ini
> >set up correctly (or both), so it's not clear how tagging is producing
> >a release for you.
> >
> >For now, we are disabling links to the artifacts for those repos
> >via https://review.openstack.org/300457 but we're also planning to
> >remove them from the official Mitaka page since there don't
> >appear to be any actual related deliverables
> >(https://review.openstack.org/300619).
> >
> >It would be good to understand what your intent is for builds. Can
> >you follow up here on this thread with some details?
> >
> >Thanks,
> >Doug
> >
> >__
> >OpenStack Development Mailing List (not for usage questions)
> >Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-04-01 Thread Hochmuth, Roland M

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 for this 
component.

monasca-log-api is probably not set up completely, but it should be similar to 
the monasca-api.

monasca-thresh remains purely Java code. There is a build, but it isn't a 
Python build so there isn't a tox.ini. Not sure how to deliver this, but the 
current java build overwrites the jar each time it builds so it sounds like 
that would need to be fixed.

I guess, judging by the issues, I don't quite understand what "deliverables" 
are. I was thinking it was the tagged code, but obviously it includes the build 
too. It sounds like we have more work ahead of us.

Let me know how you want to proceed.

Regards --Roland

On 4/1/16, 1:21 PM, "Doug Hellmann"  wrote:

>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 configured in
>openstack-infra/project-config/zuul/layout.yaml or don't have tox.ini
>set up correctly (or both), so it's not clear how tagging is producing
>a release for you.
>
>For now, we are disabling links to the artifacts for those repos
>via https://review.openstack.org/300457 but we're also planning to
>remove them from the official Mitaka page since there don't
>appear to be any actual related deliverables
>(https://review.openstack.org/300619).
>
>It would be good to understand what your intent is for builds. Can
>you follow up here on this thread with some details?
>
>Thanks,
>Doug
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-04-01 Thread Doug Hellmann

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 configured in
openstack-infra/project-config/zuul/layout.yaml or don't have tox.ini
set up correctly (or both), so it's not clear how tagging is producing
a release for you.

For now, we are disabling links to the artifacts for those repos
via https://review.openstack.org/300457 but we're also planning to
remove them from the official Mitaka page since there don't
appear to be any actual related deliverables
(https://review.openstack.org/300619).

It would be good to understand what your intent is for builds. Can
you follow up here on this thread with some details?

Thanks,
Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-02-16 Thread Pradip Mukhopadhyay

Thanks, Roland. Makes sense. I agree.


Just tossing the idea: is there a way to validate a temporal causal
relationship among events such that in case e1, followed by e2, followed by
e3 *implies *a condition C to fail/pass - and generates an alarm.


Thanks,
Pradip



On Tue, Feb 16, 2016 at 8:52 PM, Hochmuth, Roland M  wrote:

> Hi Pradip, The focus of that blueprint is to create metrics from logs in
> the LogStash component and then publish them to the Kafka metrics topic.
> The Monasca Threshold Engine can then be used to alarm on the metrics. For
> example, if the number of errors in a log file exceeds some amount, alarm
> and send a notification.
>
> Regards --Roland
>
> From: Pradip Mukhopadhyay  pradip.inte...@gmail.com>>
> Reply-To: OpenStack List  openstack-dev@lists.openstack.org>>
> Date: Monday, February 15, 2016 at 9:58 AM
> To: OpenStack List  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.launchpad.net/monasca/+spec/alarmsonlogs
>
>
> Understood how the non-periodic nature of log events to be taken care of
> (by introducing period = -1 in value-meta).
>
>
> Just wondering can it be possible to use this to satisfy the following
> usecase:
> Given a causal or non-causal sequence of events a, b, c – can we determine
> that a condition ‘p’ has occurred and alarm on that.
>
>
>
> Thanks,
> Pradip
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-02-16 Thread Hochmuth, Roland M

Hi Pradip, The focus of that blueprint is to create metrics from logs in the 
LogStash component and then publish them to the Kafka metrics topic. The 
Monasca Threshold Engine can then be used to alarm on the metrics. For example, 
if the number of errors in a log file exceeds some amount, alarm and send a 
notification.

Regards --Roland

From: Pradip Mukhopadhyay 
mailto:pradip.inte...@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, February 15, 2016 at 9:58 AM
To: OpenStack List 
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.launchpad.net/monasca/+spec/alarmsonlogs


Understood how the non-periodic nature of log events to be taken care of (by 
introducing period = -1 in value-meta).


Just wondering can it be possible to use this to satisfy the following usecase:
Given a causal or non-causal sequence of events a, b, c – can we determine that 
a condition ‘p’ has occurred and alarm on that.



Thanks,
Pradip



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-02-15 Thread Pradip Mukhopadhyay

Hello,


We come across the following interesting BP in the last weekly meeting:
https://blueprints.launchpad.net/monasca/+spec/alarmsonlogs


Understood how the non-periodic nature of log events to be taken care of
(by introducing period = -1 in value-meta).


Just wondering can it be possible to use this to satisfy the following
usecase:

Given a causal or non-causal sequence of events a, b, c – can we determine
that a condition ‘p’ has occurred and alarm on that.



Thanks,
Pradip
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-02-03 Thread Pradip Mukhopadhyay

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",
"description": ""
}
HTTPException code=500 message={
"title": "Service unavailable",
"description": ""
}


However can see other APIs like notification listing etc. working fine.

stack@ubuntu:~/devstack$ monasca --os-username admin --os-password
secretadmin --os-project-name admin notification-list
+---+--+---++
| name  | id   | type  |
address|
+---+--+---++
| pradipm_email | bf60996d-d500-4b59-b42f-a942e9121859 | EMAIL | email_id |
+---+--+---++



The following changes we did to make it work for 'admin' user:

Do the following changes:
1. /opt/stack/monasca-api/java/src/main/resources/api-config.yml  --- add
'admin' in 'defaultAuthorizedRoles'
2./etc/monasca/api-config.conf  --- add 'admin' in default_authorized_roles
3. sudo service monasca-api restart
4. sudo service monasca-thresh restart
5. sudo service monasca-agent restart




Any help will be appreciated.



Thanks,
Pradip
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-02-02 Thread Pradip Mukhopadhyay

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 defn, alarm lising, metric push,
notifications) using mini-mon user and 'mini-mon' project as follows:

#monasca --os-username mini-mon --os-password password --os-project-name
mini-mon  notification-create pradipm_email_try EMAIL 



However, I am getting an error when trying to do the same for 'admin' user
and 'admin' project:

$ monasca --os-username admin --os-password secretadmin --os-project-name
admin  notification-create pradipm_email EMAIL <...>
{
  "description": "Tenant ID is missing a required role to access this
service",
  "title": "Forbidden"
}




How can I make it work for 'admin' user also?



There are following three files. Do I need to add 'admin' role in

1. /opt/stack/monasca-api/devstack/files/monasca-api/api-config.yml  //
admin is there (defaultAuthorizedRoles)

2. /opt/stack/monasca-api/java/src/main/resources/api-config.yml  //
admin not there

3. /etc/monasca/api-config.conf  // admin not there in
default_authorized_roles clause



Any help will be solicited.


Thanks,
Pradip
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-23 Thread Premysl Kouril

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, but it is on our list 
> to implement in the near future.

Definitely interested, so if there is a discussion I am happy to join
and outline our use cases.

Regards,
Prema

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Pradip Mukhopadhyay

Thanks Hisashi.

I am sorry - by APE - I meant Anamoly and Prediction engine only.

Thanks a lot for the link.


--pradip




On Sat, Jan 23, 2016 at 12:18 AM, Hochmuth, Roland M <
roland.hochm...@hpe.com> wrote:

> Hi Pradip, There are several components in Monasca. I'm not sure what the
> acronym APE is stands for. Is that Anomaly and Prediction Engine? The list
> of components in Monasca and the languages that they are implemented in is
> as follows:
>
>   1.  API: Both Java and Python.
>   2.  Persister: Both Java and Python
>   3.  Threshold Engine: Java only
>   4.  Notification Engine: Python
>   5.  python-monascaclient: Python
>
> Over the past few months we developed around 120 Tempest tests that test
> the entire API, developed a plugin for Tempest and integrated in the
> OpenStack CI systems. The Tempest tests run to 100% completion against both
> APIs and Persisters.
>
> There was a Python implementation of an anomaly engine developed that was
> more of a proof-of-concept. It is at,
> https://github.com/roland-hochmuth/monasca-anomaly.
>
> Regards --Roland
>
>
> From: Pradip Mukhopadhyay  pradip.inte...@gmail.com>>
> Reply-To: OpenStack List  openstack-dev@lists.openstack.org>>
> Date: Friday, January 22, 2016 at 5:18 AM
> To: OpenStack List  openstack-dev@lists.openstack.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 Java?
>
>
> --pradip
>
>
> On Fri, Jan 22, 2016 at 4:12 PM, Osanai, Hisashi <
> osanai.hisa...@jp.fujitsu.com<mailto:osanai.hisa...@jp.fujitsu.com>>
> wrote:
>
> 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
> has been growing rapidly.
>
> Let's start to discuss about how to approach this. What do you think?
>
> Best Regards,
> Hisashi Osanai
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Hochmuth, Roland M

Hi Pradip, There are several components in Monasca. I'm not sure what the 
acronym APE is stands for. Is that Anomaly and Prediction Engine? The list of 
components in Monasca and the languages that they are implemented in is as 
follows:

  1.  API: Both Java and Python.
  2.  Persister: Both Java and Python
  3.  Threshold Engine: Java only
  4.  Notification Engine: Python
  5.  python-monascaclient: Python

Over the past few months we developed around 120 Tempest tests that test the 
entire API, developed a plugin for Tempest and integrated in the OpenStack CI 
systems. The Tempest tests run to 100% completion against both APIs and 
Persisters.

There was a Python implementation of an anomaly engine developed that was more 
of a proof-of-concept. It is at, 
https://github.com/roland-hochmuth/monasca-anomaly.

Regards --Roland


From: Pradip Mukhopadhyay 
mailto:pradip.inte...@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, January 22, 2016 at 5:18 AM
To: OpenStack List 
mailto:openstack-dev@lists.openstack.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 Java?


--pradip


On Fri, Jan 22, 2016 at 4:12 PM, Osanai, Hisashi 
mailto:osanai.hisa...@jp.fujitsu.com>> wrote:

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
has been growing rapidly.

Let's start to discuss about how to approach this. What do you think?

Best Regards,
Hisashi Osanai

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Hochmuth, Roland M

Hi Prema, I assumed that the component that is translating and sending to the 
Monasca API would be sending metrics periodically. If that isn't the case, then 
support for non-periodic metrics would need to be added.

Sorry, I should heave realized this in my previous response.

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, but it is on our list to 
implement in the near future.

Regards --Roland

From: Premysl Kouril mailto:premysl.kou...@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, January 22, 2016 at 7:06 AM
To: OpenStack List 
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 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 enhancement is currently being designed.

Is that correct?

Cheers,
Prema

On 22 Jan 2016 01:04, "Hochmuth, Roland M" 
mailto:roland.hochm...@hpe.com>> wrote:
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 developed to handle SNMP traps,
then translate and send them to the Monasca API as binary data. Possibly,
this component could be added to the Agent.

Using the Monasca Alarm API, an alarm could be defined, such as
max(snmp{}) > 0.

The latency for a min/max alarm expression in Monasca is very low.

Regards --Roland

On 1/18/16, 9:07 AM, "Premysl Kouril" 
mailto:premysl.kou...@gmail.com>> wrote:

>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 out and SNMP trap indicating that it is in bad
>condition and when the box is fixed it sends out SNMP trap indicating
>that it is OK and operational again (in other words: the box is
>indicating health state transitions by sending events - in this case
>SNMP traps).
>
>Is it possible in Monasca to define such alarm which would work on top
>of such events? In other words - Is it possible to have a Monasca
>alarm which would go red on some external event go back green on some
>other external event? By alarm I really mean a stateful entity in
>monasca database not some notification to administrator.
>
>Best regards.
>Prema
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: 
>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Hochmuth, Roland M

Thanks Alonso. 

On 1/22/16, 2:56 AM, "Alonso Hernandez, Rodolfo"
 wrote:

>Hello Roland:
>
>>> How would you map the metric names and fields in collectd to a monasa
>>>name and dimensions?
>I'm on it. I'm reading the API from collectd and monasca, to figure out
>how to connect them. Next week I'll upload a spec and I'll wait for your
>comments.
>
>Thank you for your 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)
>
>Subject: Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin
>
>Hi Rodolfo, I think this would be useful work. Collectd has a lot of
>metrics that aren't supported in Monasca yet.
>
>How would you map the metric names and fields in collectd to a monasa
>name and dimensions?
>
>Regards --Roland
>
>From: Jaesuk Ahn mailto:bluejay@gmail.com>>
>Reply-To: OpenStack List
>mailto:openstack-...@lists.openstack.or
>g>>
>Date: Thursday, January 21, 2016 at 4:49 AM
>To: OpenStack List
>mailto:openstack-...@lists.openstack.or
>g>>
>Subject: 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 your plan.
>
>Cheers,
>
>
>---
>Jaesuk Ahn
>SDI Tech. Lab, SKT
>
>
>2016년 1월 21일 (목) 19:11, Alonso Hernandez, Rodolfo
>mailto:rodolfo.alonso.hernandez@intel.
>com>>님이 작성:
>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 you in advance. Regards.
>
>Rodolfo Alonso.
>--
>Intel Research and Development Ireland Limited Registered in Ireland
>Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
>Registered Number: 308263
>
>
>This e-mail and any attachments may contain confidential material for the
>sole use of the intended recipient(s). Any review or distribution by
>others is strictly prohibited. If you are not the intended recipient,
>please contact the sender and delete all copies.
>
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: 
>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://OpenS
>tack-dev-requ...@lists.openstack.org?subject:unsubscribe>
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>--
>Intel Research and Development Ireland Limited
>Registered in Ireland
>Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
>Registered Number: 308263
>
>
>This e-mail and any attachments may contain confidential material for the
>sole
>use of the intended recipient(s). Any review or distribution by others is
>strictly prohibited. If you are not the intended recipient, please
>contact the
>sender and delete all copies.
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Premysl Kouril

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 enhancement is
currently being designed.

Is that correct?

Cheers,
Prema
On 22 Jan 2016 01:04, "Hochmuth, Roland M"  wrote:

> 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 developed to handle SNMP traps,
> then translate and send them to the Monasca API as binary data. Possibly,
> this component could be added to the Agent.
>
> Using the Monasca Alarm API, an alarm could be defined, such as
> max(snmp{}) > 0.
>
> The latency for a min/max alarm expression in Monasca is very low.
>
> Regards --Roland
>
>
> On 1/18/16, 9:07 AM, "Premysl Kouril"  wrote:
>
> >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 out and SNMP trap indicating that it is in bad
> >condition and when the box is fixed it sends out SNMP trap indicating
> >that it is OK and operational again (in other words: the box is
> >indicating health state transitions by sending events - in this case
> >SNMP traps).
> >
> >Is it possible in Monasca to define such alarm which would work on top
> >of such events? In other words - Is it possible to have a Monasca
> >alarm which would go red on some external event go back green on some
> >other external event? By alarm I really mean a stateful entity in
> >monasca database not some notification to administrator.
> >
> >Best regards.
> >Prema
> >
> >__
> >OpenStack Development Mailing List (not for usage questions)
> >Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Pradip Mukhopadhyay

One question.  After pushing the data to Monasca (gathering from collectd)
- what else could potentially be done on this data to get some interesting
inside about the system?

Of course, specially for legacy system cases, it would be an awesome
addition (similar line of Ceilometer - I guess).



--pradip



On Fri, Jan 22, 2016 at 3:26 PM, Alonso Hernandez, Rodolfo <
rodolfo.alonso.hernan...@intel.com> wrote:

> Hello Roland:
>
> >> How would you map the metric names and fields in collectd to a monasa
> name and dimensions?
> I'm on it. I'm reading the API from collectd and monasca, to figure out
> how to connect them. Next week I'll upload a spec and I'll wait for your
> comments.
>
> Thank you for your 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] collectd-Monasca Python plugin
>
> Hi Rodolfo, I think this would be useful work. Collectd has a lot of
> metrics that aren't supported in Monasca yet.
>
> How would you map the metric names and fields in collectd to a monasa name
> and dimensions?
>
> Regards --Roland
>
> From: Jaesuk Ahn mailto:bluejay@gmail.com>>
> Reply-To: OpenStack List  openstack-dev@lists.openstack.org>>
> Date: Thursday, January 21, 2016 at 4:49 AM
> To: OpenStack List  openstack-dev@lists.openstack.org>>
> Subject: 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 your plan.
>
> Cheers,
>
>
> ---
> Jaesuk Ahn
> SDI Tech. Lab, SKT
>
>
> 2016년 1월 21일 (목) 19:11, Alonso Hernandez, Rodolfo <
> rodolfo.alonso.hernan...@intel.com rodolfo.alonso.hernan...@intel.com>>님이 작성:
> 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 you in advance. Regards.
>
> Rodolfo Alonso.
> --
> Intel Research and Development Ireland Limited Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by others
> is strictly prohibited. If you are not the intended recipient, please
> contact the sender and delete all copies.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> --
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for the
> sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact
> the
> sender and delete all copies.
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Pradip Mukhopadhyay

(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 <
osanai.hisa...@jp.fujitsu.com> wrote:

>
> 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
> has been growing rapidly.
>
> Let's start to discuss about how to approach this. What do you think?
>
> Best Regards,
> Hisashi Osanai
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Osanai, Hisashi


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
has been growing rapidly.

Let's start to discuss about how to approach this. What do you think?

Best Regards,
Hisashi Osanai

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-22 Thread Alonso Hernandez, Rodolfo

Hello Roland:

>> How would you map the metric names and fields in collectd to a monasa name 
>> and dimensions?
I'm on it. I'm reading the API from collectd and monasca, to figure out how to 
connect them. Next week I'll upload a spec and I'll wait for your comments.

Thank you for your 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) 

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

Hi Rodolfo, I think this would be useful work. Collectd has a lot of metrics 
that aren't supported in Monasca yet.

How would you map the metric names and fields in collectd to a monasa name and 
dimensions?

Regards --Roland

From: Jaesuk Ahn mailto:bluejay@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, January 21, 2016 at 4:49 AM
To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Subject: 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 your plan.

Cheers,


---
Jaesuk Ahn
SDI Tech. Lab, SKT


2016년 1월 21일 (목) 19:11, Alonso Hernandez, Rodolfo 
mailto:rodolfo.alonso.hernan...@intel.com>>님이
 작성:
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 you in advance. Regards.

Rodolfo Alonso.
--
Intel Research and Development Ireland Limited Registered in Ireland Registered 
Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 
308263


This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-21 Thread Hochmuth, Roland M

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 developed to handle SNMP traps,
then translate and send them to the Monasca API as binary data. Possibly,
this component could be added to the Agent.

Using the Monasca Alarm API, an alarm could be defined, such as
max(snmp{}) > 0.

The latency for a min/max alarm expression in Monasca is very low.

Regards --Roland

On 1/18/16, 9:07 AM, "Premysl Kouril"  wrote:

>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 out and SNMP trap indicating that it is in bad
>condition and when the box is fixed it sends out SNMP trap indicating
>that it is OK and operational again (in other words: the box is
>indicating health state transitions by sending events - in this case
>SNMP traps).
>
>Is it possible in Monasca to define such alarm which would work on top
>of such events? In other words - Is it possible to have a Monasca
>alarm which would go red on some external event go back green on some
>other external event? By alarm I really mean a stateful entity in
>monasca database not some notification to administrator.
>
>Best regards.
>Prema
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-21 Thread Hochmuth, Roland M

Hi Rodolfo, I think this would be useful work. Collectd has a lot of metrics 
that aren't supported in Monasca yet.

How would you map the metric names and fields in collectd to a monasa name and 
dimensions?

Regards --Roland

From: Jaesuk Ahn mailto:bluejay@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, January 21, 2016 at 4:49 AM
To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Subject: 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 your plan.

Cheers,


---
Jaesuk Ahn
SDI Tech. Lab, SKT


2016년 1월 21일 (목) 19:11, Alonso Hernandez, Rodolfo 
mailto:rodolfo.alonso.hernan...@intel.com>>님이
 작성:
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 you in advance. Regards.

Rodolfo Alonso.
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-21 Thread Jaesuk Ahn

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 your plan.

Cheers,


---
Jaesuk Ahn
SDI Tech. Lab, SKT


2016년 1월 21일 (목) 19:11, Alonso Hernandez, Rodolfo <
rodolfo.alonso.hernan...@intel.com>님이 작성:

> 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 you in advance. Regards.
>
> Rodolfo Alonso.
> --
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for the
> sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact
> the
> sender and delete all copies.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-21 Thread Alonso Hernandez, Rodolfo

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 you in advance. Regards.

Rodolfo Alonso.
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-20 Thread Hochmuth, Roland M

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 open to anyone and the contact information is below.

Regards --Roland

Day 1, Wednesday February 3rd, 2016
Time: 1500-2100 UTC

https://cisco.webex.com/ciscosales/j.php?MTID=ma4770b115a04f1476fdf4073c404c60a
Meeting number: 204 442 828
Meeting password: dM3gVJxR

If you are the host, you can use the meeting host key to pass the host 
privilege to another participant or to start the meeting from a video 
conferencing system or application. To find the host key for this meeting, go 
here.

Join by phone
+1-408-525-6800 Call-in toll number (US/Canada)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 200 279 394
Numeric meeting password: 04704543
Global call-in numbers | Toll-free calling restrictions

Day 2, Wednesday February 4th, 2016
Time: 1500-2100 UTC

https://cisco.webex.com/ciscosales/j.php?MTID=m16a6dddb7c2b5f50fb2dff2b2a9d10a5
Meeting number: 200 279 394
Meeting password: jYxEJ3Gb

If you are the host, you can use the meeting host key to pass the host 
privilege to another participant or to start the meeting from a video 
conferencing system or application. To find the host key for this meeting, go 
here.

Join by phone
+1-408-525-6800 Call-in toll number (US/Canada)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 200 279 394
Numeric meeting password: 04704543
Global call-in numbers | Toll-free calling restrictions

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-18 Thread Premysl Kouril

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 out and SNMP trap indicating that it is in bad
condition and when the box is fixed it sends out SNMP trap indicating
that it is OK and operational again (in other words: the box is
indicating health state transitions by sending events - in this case
SNMP traps).

Is it possible in Monasca to define such alarm which would work on top
of such events? In other words - Is it possible to have a Monasca
alarm which would go red on some external event go back green on some
other external event? By alarm I really mean a stateful entity in
monasca database not some notification to administrator.

Best regards.
Prema

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-14 Thread Pradip Mukhopadhyay

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. ^$ [name='splash']
   2. ^api/
   3. ^home/$ [name='user_home']
   4. ^i18n/js/(?P\S+?)/$ [name='jsi18n']
   5. ^i18n/setlang/$ [name='set_language']
   6. ^i18n/
   7. ^jasmine-legacy/$ [name='jasmine_tests']
   8. ^jasmine/.*?$
   9. ^settings/
   10. ^monitoring/
   11. ^developer/
   12. ^admin/
   13. ^identity/
   14. ^project/
   15. ^auth/
   16. ^static\/(?P.*)$
   17. ^media\/(?P.*)$
   18. ^500/$

The current URL, grafana/index.html, didn't match any of these.


Any help would be good.


Thanks,
Pradip









On Tue, Jan 12, 2016 at 10:42 PM, Pradip Mukhopadhyay <
pradip.inte...@gmail.com> wrote:

> 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.
>>
>> -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 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?
>>>
>>>
>>> We do see it when do a vagrant setup with mini-mon and devstack VMs.
>>>
>>>
>>> Any help is highly solicited.
>>>
>>>
>>> --pradip
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-13 Thread Fabio Giannetti (fgiannet)

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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-12 Thread Pradip Mukhopadhyay

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.
>
> -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 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?
>>
>>
>> We do see it when do a vagrant setup with mini-mon and devstack VMs.
>>
>>
>> Any help is highly solicited.
>>
>>
>> --pradip
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-12 Thread Lin Hua Cheng

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 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?
>
>
> We do see it when do a vagrant setup with mini-mon and devstack VMs.
>
>
> Any help is highly solicited.
>
>
> --pradip
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-01-12 Thread Pradip Mukhopadhyay

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?


We do see it when do a vagrant setup with mini-mon and devstack VMs.


Any help is highly solicited.


--pradip
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Monasca -agent

2016-01-07 Thread Chandeep Khamba

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 --monasca_url x 
--config_dir /etc/monasca/agent --log_dir /var/log/monasca/agent —-overwrite

INFO: Enabled monasca-agent service via SysV init script

INFO: Configuring base Agent settings.

INFO: Configuring System

INFO: Configured network

INFO: Configured disk

INFO: Configured load

INFO: Configured memory

INFO: Configured cpu

INFO: Configuring Ntp

INFO: Enabling the ntp plugin

INFO: Postfix found but the required sudo access is not configured.

Refer to plugin documentation for more detail

INFO: Starting monasca-agent service via SysV init script

Stopping Monasca Monitoring Agent (stopping supervisord) monasca-agent

Starting Monasca Monitoring Agent (using supervisord) monasca-agent

ERROR: The service did not startup correctly see /var/log/monasca/agent



 While If I do a manual run of the collector and forwarder they seem to work 
pretty well for me

The same stuff works on a centos 7 machine pretty well .

Is there something else I can use to daemonize my agent instead of supervisord  
 ?  Or am I missing something  ?

PS  : monasca-agent version : 1.1.15

Thanks
Chandeep Khamba



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-12-24 Thread Pradip Mukhopadhyay

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 as: sudo pip install python-monascaclient

Now when I am trying to see the CLI, it is giving an error as follows:

stack@stack-ThinkPad-W530:~/devstack$ monasca --os-username mini-mon
--os-password password --os-project-name mini-mon --os-auth-url
http://10.74.150.158:35357/v3 --monasca-api-url
http://10.74.150.158:8070/v2.0 metric-list
*('Connection aborted.', error(104, 'Connection reset by peer'))*



Here is my keystone endpoint:

| f259de7e41db4871854a9e56a406daa1 | RegionOne |
http://10.74.150.158:5000/v2.0|
http://10.74.150.158:5000/v2.0|
http://10.74.150.158:35357/v2.0| 0208a38741d443bdb74592a3d9017762 |

(I think Monasca require Keystone 3.0 - hence I have given 'v3').

Here is my monasca endpoint in keystone:

| 21be1893c8934950956b0f57c24c50fe | RegionOne |
http://10.74.150.158:8070/v2.0|
http://10.74.150.158:8070/v2.0|
http://10.74.150.158:8070/v2.0| 34134ffdb56241e2a5beb9995b0e3628 |



Any help in resolving this will be highly appreciated.


--pradip
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-12-11 Thread Pradip Mukhopadhyay

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 Nov 11
11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux





failed: [mini-mon] => {"failed": true}
msg: Exception in thread "main"
org.apache.thrift7.transport.TTransportException:
java.net.ConnectException: Connection refused
at org.apache.thrift7.transport.TSocket.open(TSocket.java:183)
at
org.apache.thrift7.transport.TFramedTransport.open(TFramedTransport.java:81)
at
backtype.storm.thrift$nimbus_client_and_conn.invoke(thrift.clj:75)
at
backtype.storm.command.kill_topology$_main.doInvoke(kill_topology.clj:26)
at clojure.lang.RestFn.applyTo(RestFn.java:137)
at backtype.storm.command.kill_topology.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at org.apache.thrift7.transport.TSocket.open(TSocket.java:178)
... 5 more
Exception in thread "main"
org.apache.thrift7.transport.TTransportException:
java.net.ConnectException: Connection refused
at org.apache.thrift7.transport.TSocket.open(TSocket.java:183)
at
org.apache.thrift7.transport.TFramedTransport.open(TFramedTransport.java:81)
at
backtype.storm.thrift$nimbus_client_and_conn.invoke(thrift.clj:75)
at backtype.storm.command.list$_main.invoke(list.clj:22)
at clojure.lang.AFn.applyToHelper(AFn.java:159)
at clojure.lang.AFn.applyTo(AFn.java:151)
at backtype.storm.command.list.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at org.apache.thrift7.transport.TSocket.open(TSocket.java:178)
... 6 more

TASK: [monasca-thresh | Enable the Service]
***
FATAL: no hosts matched or all hosts have already failed -- aborting


PLAY RECAP

   to retry, use: --limit @/home/pradipm/mini-mon.retry

mini-mon   : ok=157  changed=21   unreachable=0
failed=1

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-12-09 Thread Fabio Giannetti (fgiannet)

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


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-12-07 Thread AFEK, Ifat (Ifat)

Hi Roland,

We created a blueprint for Vitrage-Monasca integration: 
https://blueprints.launchpad.net/vitrage/+spec/monasca-integration.
We will be happy to get your comments about it.

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: [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 Vitrage Notifier would be
> developed for Monasca.
> 
> In the diagram at, https://wiki.openstack.org/wiki/Vitrage, it shows
> the Synchronizer collecting data, such as OpenStack notifications,
> which usually implies RabbitMQ. With the Ceilosca effort,
> https://www.openstack.org/summit/tokyo-
> 2015/videos/presentation/ceilometer-
> monascaceilosca and https://github.com/openstack/monasca-ceilometer, we
> are planning on sending OpenStack Notifications from Ceilometer to
> Monasca. Monasca will then publish to the Kafka queue. Would you be
> interested in consuming events from Kafka by the Synchronizer to reduce
> the load on RabbitMQ?
> 
> In the use cases you discuss getting health/status information about a
> switch and correlating problems to VMs. But, in the diagram only SDN
> Controller, Heat, Cinder and Nova are shown. Are you planning on
> receiving health/status information from other sources? Monasca is
> processing metrics for many components, such as the physical
> infrastructure used for running the cloud and for OpenStack resources,
> and generating alarms. For example, in your use case, Monasca could be
> monitoring the physical switch and creating alarms. Should alarms that
> Monasca creates be a source for the Vitrage Synchronizer?
> 
> Regards --Roland
> 
> 
> On 11/17/15, 3:02 AM, "AFEK, Ifat (Ifat)"  lucent.com>
> wrote:
> 
> >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 of
> problems
> >and deducing the existence of problems before they are directly
> detected.
> >
> >We are now in the process of reviewing the blueprints[2] that we wish
> >to implement in mitaka. At the first stage of the implementation we
> >plan to integrate with AODH alarms. In the next phase, we would like
> to
> >check how we can integrate with Monasca as well. We would be happy to
> >get your reviews for our blueprints, to make sure our architecture
> >matches this future integration.
> >
> >Your feedback would be highly appreciated.
> >
> >[1] https://wiki.openstack.org/wiki/Vitrage
> >[2] https://blueprints.launchpad.net/vitrage
> >
> >Thanks,
> >Ifat Afek.
> >
> >
> >
> >__
> _
> >___ OpenStack Development Mailing List (not for usage questions)
> >Unsubscribe:
> >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> ___
> ___
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Monasca]

2015-11-23 Thread Fabio Giannetti (fgiannet)

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 questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-11-19 Thread AFEK, Ifat (Ifat)

Hi Roland,

Thanks for your feedback. The questions you raised below are helping us in 
clarifying and enhancing our design. We will also be happy to see your comments 
on our blueprints. Your input will be very helpful.

The integration with Monasca should include two parts:

1. Query information. We would be happy to get all the information that you can 
supply, including alarms on other component types. This would require writing a 
Monasca plugin to Vitrage Synchronizer.

2. Notify on deduced alarms. We would like to notify Monasca on new alarms that 
Vitrage generates, e.g. that an instance may have suboptimal performance due to 
problems in its host.

We did not write Monasca related blueprints yet, We will try to do it in the 
following days. We also plan to update our wiki page with the more detailed 
design that we are doing these days. I will notify you once we have 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: [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 Vitrage Notifier would be
> developed for Monasca.

Right. We will add a blueprint for that.

> 
> In the diagram at, https://wiki.openstack.org/wiki/Vitrage, it shows
> the Synchronizer collecting data, such as OpenStack notifications,
> which usually implies RabbitMQ. With the Ceilosca effort,
> https://www.openstack.org/summit/tokyo-
> 2015/videos/presentation/ceilometer-
> monascaceilosca and https://github.com/openstack/monasca-ceilometer, we
> are planning on sending OpenStack Notifications from Ceilometer to
> Monasca. Monasca will then publish to the Kafka queue. Would you be
> interested in consuming events from Kafka by the Synchronizer to reduce
> the load on RabbitMQ?

As a first stage, we indeed plan to collect data using RabbitMQ. Once we 
integrate with Monasca, we will use kafka to get your events. We would like to 
support both options.

> 
> In the use cases you discuss getting health/status information about a
> switch and correlating problems to VMs. But, in the diagram only SDN
> Controller, Heat, Cinder and Nova are shown. Are you planning on
> receiving health/status information from other sources? Monasca is
> processing metrics for many components, such as the physical
> infrastructure used for running the cloud and for OpenStack resources,
> and generating alarms. For example, in your use case, Monasca could be
> monitoring the physical switch and creating alarms. Should alarms that
> Monasca creates be a source for the Vitrage Synchronizer?

Our diagram shows that we plan to collect data also from other sources like 
Ceilometer, Nagios and Zabbix. We would also like to get network information 
from Neutron. We will probably add these source plug-ins in stages. Right now 
they are all referred to in the synchronizer blueprint, but this design is 
still in progress. In general, the more input Vitrage gets, the more valuable 
alarm insights it can produce.

Obviously, Vitrage can benefit a lot from the integration with Monasca.

> 
> Regards --Roland
> 
> 
> On 11/17/15, 3:02 AM, "AFEK, Ifat (Ifat)"  lucent.com>
> wrote:
> 
> >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 of
> problems
> >and deducing the existence of problems before they are directly
> detected.
> >
> >We are now in the process of reviewing the blueprints[2] that we wish
> >to implement in mitaka. At the first stage of the implementation we
> >plan to integrate with AODH alarms. In the next phase, we would like
> to
> >check how we can integrate with Monasca as well. We would be happy to
> >get your reviews for our blueprints, to make sure our architecture
> >matches this future integration.
> >
> >Your feedback would be highly appreciated.
> >
> >[1] https://wiki.openstack.org/wiki/Vitrage
> >[2] https://blueprints.launchpad.net/vitrage
> >
> >Thanks,
> >Ifat Afek.
> >
&g

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

2015-11-18 Thread Hochmuth, Roland M

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 Vitrage Notifier would be
developed for Monasca.

In the diagram at, https://wiki.openstack.org/wiki/Vitrage, it shows the
Synchronizer collecting data, such as OpenStack notifications, which
usually implies RabbitMQ. With the Ceilosca effort,
https://www.openstack.org/summit/tokyo-2015/videos/presentation/ceilometer-
monascaceilosca and https://github.com/openstack/monasca-ceilometer, we
are planning on sending OpenStack Notifications from Ceilometer to
Monasca. Monasca will then publish to the Kafka queue. Would you be
interested in consuming events from Kafka by the Synchronizer to reduce
the load on RabbitMQ?

In the use cases you discuss getting health/status information about a
switch and correlating problems to VMs. But, in the diagram only SDN
Controller, Heat, Cinder and Nova are shown. Are you planning on receiving
health/status information from other sources? Monasca is processing
metrics for many components, such as the physical infrastructure used for
running the cloud and for OpenStack resources, and generating alarms. For
example, in your use case, Monasca could be monitoring the physical switch
and creating alarms. Should alarms that Monasca creates be a source for
the Vitrage Synchronizer?

Regards --Roland

On 11/17/15, 3:02 AM, "AFEK, Ifat (Ifat)" 
wrote:

>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 of problems and
>deducing the existence of problems before they are directly detected.
>
>We are now in the process of reviewing the blueprints[2] that we wish to
>implement in mitaka. At the first stage of the implementation we plan to
>integrate with AODH alarms. In the next phase, we would like to check how
>we can integrate with Monasca as well. We would be happy to get your
>reviews for our blueprints, to make sure our architecture matches this
>future integration.
>
>Your feedback would be highly appreciated.
>
>[1] https://wiki.openstack.org/wiki/Vitrage
>[2] https://blueprints.launchpad.net/vitrage
>
>Thanks,
>Ifat Afek.
>
>
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-11-17 Thread AFEK, Ifat (Ifat)

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 of problems and deducing the 
existence of problems before they are directly detected.

We are now in the process of reviewing the blueprints[2] that we wish to 
implement in mitaka. At the first stage of the implementation we plan to 
integrate with AODH alarms. In the next phase, we would like to check how we 
can integrate with Monasca as well. We would be happy to get your reviews for 
our blueprints, to make sure our architecture matches this future integration. 

Your feedback would be highly appreciated.

[1] https://wiki.openstack.org/wiki/Vitrage
[2] https://blueprints.launchpad.net/vitrage 

Thanks,
Ifat Afek.



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-10-21 Thread Fabio Giannetti (fgiannet)

Guys,
  We have half slot on Wed 3:40 with the Congress folks:

https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Congress

These are the topics I proposed:

  1.  how to integrate Monasca with Congress so then Monasca can provide 
metrics, logs and event data for policy evaluation/enforcement
  2.  How to leverage Monasca alarming to automatically notify about statuses 
that may imply policy breach
  3.  How to automatically (if possible) convert policies (or subparts) into 
Monasca alarms.

Probably we will manage to get an intent to work on these topics since we have 
20min, but it is a start :-)
Thanks,
Fabio

From: Fabio Giannetti mailto:fgian...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, October 14, 2015 at 4:07 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit

Hi Oğuz,
   YES this is open to everybody.
Thanks,
Fabio

[http://www.cisco.com/c/dam/assets/email-signature-tool/logo_06.png?ct=1430182397611]

Fabio Giannetti
Cloud Innovation Architect
Cisco Services
fgian...@cisco.com<mailto:fgian...@cisco.com>
Phone: +1 408 527 1134
Mobile: +1 408 854 0020


Cisco Systems, Inc.
285 W. Tasman Drive
San Jose
California
95134
United States
Cisco.com<http://www.cisco.com/>





[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif] Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.

Please click 
here<http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for 
Company Registration Information.



From: Oğuz Yarımtepe mailto:oguzyarimt...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, October 13, 2015 at 11:22 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit

Hi,

On Wed, Oct 14, 2015 at 7:36 AM, Fabio Giannetti (fgiannet) 
mailto: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 meeting be open to everyone? We are using Monasca at our test 
environment and planning to use it at out production also, would like to hear 
the future plans and development process of it.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-10-14 Thread Fabio Giannetti (fgiannet)

Hi Oğuz,
   YES this is open to everybody.
Thanks,
Fabio

[http://www.cisco.com/c/dam/assets/email-signature-tool/logo_06.png?ct=1430182397611]

Fabio Giannetti
Cloud Innovation Architect
Cisco Services
fgian...@cisco.com<mailto:fgian...@cisco.com>
Phone: +1 408 527 1134
Mobile: +1 408 854 0020


Cisco Systems, Inc.
285 W. Tasman Drive
San Jose
California
95134
United States
Cisco.com<http://www.cisco.com/>





[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif] Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.

Please click 
here<http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for 
Company Registration Information.



From: Oğuz Yarımtepe mailto:oguzyarimt...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, October 13, 2015 at 11:22 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit

Hi,

On Wed, Oct 14, 2015 at 7:36 AM, Fabio Giannetti (fgiannet) 
mailto: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 meeting be open to everyone? We are using Monasca at our test 
environment and planning to use it at out production also, would like to hear 
the future plans and development process of it.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-10-13 Thread Oğuz Yarımtepe

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 meeting be open to everyone? We are using Monasca at our test
environment and planning to use it at out production also, would like to
hear the future plans and development process of it.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-10-13 Thread Fabio Giannetti (fgiannet)

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

[http://www.cisco.com/c/dam/assets/email-signature-tool/logo_06.png?ct=1430182397611]

Fabio Giannetti
Cloud Innovation Architect
Cisco Services
fgian...@cisco.com<mailto:fgian...@cisco.com>
Phone: +1 408 527 1134
Mobile: +1 408 854 0020


Cisco Systems, Inc.
285 W. Tasman Drive
San Jose
California
95134
United States
Cisco.com<http://www.cisco.com/>





[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif] Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.

Please click 
here<http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for 
Company Registration Information.



From: BYEONG-GI KIM mailto:kimbyeon...@gmail.com>>
Reply-To: 
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" 
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, October 13, 2015 at 12:43 AM
To: 
"openstack-dev@lists.openstack.org<mailto: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 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 where the guide is?

Thanks in advance.

Best regards

BG KIM
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-10-13 Thread BYEONG-GI KIM

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 where the guide is?

Thanks in advance.

Best regards

BG KIM
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-31 Thread Hochmuth, Roland M

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: https://etherpad.openstack.org/p/monasca-team-meeting-agenda

Please add agenda items to discuss.

Regards --Roland



On 8/25/15, 5:53 PM, "Hochmuth, Roland M"  wrote:

>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.ya
>ml. Please +1 if you are OK with the proposed time slot. If not, please
>-1 and propose a new time slot.
>
>OpenStack meetings are hosted in specific IRC channels and archived.
>
>Unfortunately, there wasn't an existing channel available to continue to
>host the meeting on Tuesday's. Hopefully, Wednesday will continue to work
>for everyone.
>
>Regards --Roland
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-25 Thread Hochmuth, Roland M

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 are OK with the proposed time slot. If not, please -1 and 
propose a new time slot.

OpenStack meetings are hosted in specific IRC channels and archived.

Unfortunately, there wasn't an existing channel available to continue to host 
the meeting on Tuesday's. Hopefully, Wednesday will continue to work for 
everyone.

Regards --Roland

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-18 Thread Hochmuth, Roland M

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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-16 Thread Ildikó Váncsa

Hi Roland,

As I saw, the wiki says 4pm UTC too, please check it.

Thanks and Best Regards,
Ildikó

> -Original Message-
> From: Hochmuth, Roland M [mailto:roland.hochm...@hp.com]
> Sent: August 16, 2015 17:14
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [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"  wrote:
> 
> >Hi Roland,
> >
> >Thanks for the meeting info.
> >
> >Let me come back to you regarding the attendance of the next Monasca
> >meeting. I messed up with time zones and slots a bit and I realized now
> >that the slot is 4pm UTC as opposed to 3pm UTC as I originally thought.
> >I have a bi-weekly meeting in my calendar colliding with the upcoming
> >slot, but for the past few occurrences it was cancelled, I need to
> >check the next one with the organizer.
> >
> >If I can attend, I can briefly talk about the componentization work.
> >
> >Best Regards,
> >Ildikó
> >
> >> -Original Message-
> >> From: Hochmuth, Roland M [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 an overview and current status/plans of
> >>the Ceilometer work around the componentization? I was at the
> >>discussion in Vancouver on this, and several others from Monasca  were
> >>there too, but I haven't stayed connected.
> >>
> >> The information for the Monasca Meetings as well as minutes is at,
> >>https://wiki.openstack.org/wiki/Meetings/Monasca. If you have  any
> >>problems connecting in, please let me know. We recently switched to
> >>WebEx, which is hosted by Cisco. Everything should work,  but if there
> >>are any problems we can switch to IRC.
> >>
> >> If Tuesday's at 4:00 PM UTC are problematic, then we would consider
> >>setting up a separate time to cover this topic or move the  Monasca
> >>meeting the following week.
> >>
> >> Regards --Roland
> >>
> >>
> >>
> >> On 8/14/15, 6:57 AM, "Ildikó Váncsa"  wrote:
> >>
> >> >Hi,
> >> >
> >> >I will try to join if I can, I have an overlapping meeting on Tuesdays.
> >> >
> >> >In general I think it would be really good to start a closer
> >> >collaboration, the componentization work in Ceilometer gives a
> >> >really good opportunity as Chris described.
> >> >
> >> >Best Regards,
> >> >Ildikó
> >> >
> >> >> -Original Message-
> >> >> 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 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 up? I've got it on my schedule to come the  week
> >> >>after.
> >> >>
> >> >> I suspect there's a lot we can do over the long run to avoid
> >> >>duplicating code and effort but that there will be some humps to
> >> >>ride over  to different pieces (and people!) talking to one another.
> >> >> Should be fun. Looking forward to it.
> >> >>
> >> >> --
> >> >> Chris Dent tw:@anticdent freenode:cdent
> >> >> https://tank.peermore.com/tanks/cdent
> >> >>
> >> >>
> >> >>___
> >> >>___
> >> &g

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

2015-08-16 Thread Hochmuth, Roland M

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"  wrote:

>Hi Roland,
>
>Thanks for the meeting info.
>
>Let me come back to you regarding the attendance of the next Monasca
>meeting. I messed up with time zones and slots a bit and I realized now
>that the slot is 4pm UTC as opposed to 3pm UTC as I originally thought. I
>have a bi-weekly meeting in my calendar colliding with the upcoming slot,
>but for the past few occurrences it was cancelled, I need to check the
>next one with the organizer.
>
>If I can attend, I can briefly talk about the componentization work.
>
>Best Regards,
>Ildikó
>
>> -Original Message-
>> From: Hochmuth, Roland M [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 an overview and current status/plans of
>> the Ceilometer work around the componentization? I was at the
>>discussion in Vancouver on this, and several others from Monasca
>> were there too, but I haven't stayed connected.
>> 
>> The information for the Monasca Meetings as well as minutes is at,
>>https://wiki.openstack.org/wiki/Meetings/Monasca. If you have
>> any problems connecting in, please let me know. We recently switched to
>>WebEx, which is hosted by Cisco. Everything should work,
>> but if there are any problems we can switch to IRC.
>> 
>> If Tuesday's at 4:00 PM UTC are problematic, then we would consider
>>setting up a separate time to cover this topic or move the
>> Monasca meeting the following week.
>> 
>> Regards --Roland
>> 
>> 
>> 
>> On 8/14/15, 6:57 AM, "Ildikó Váncsa"  wrote:
>> 
>> >Hi,
>> >
>> >I will try to join if I can, I have an overlapping meeting on Tuesdays.
>> >
>> >In general I think it would be really good to start a closer
>> >collaboration, the componentization work in Ceilometer gives a really
>> >good opportunity as Chris described.
>> >
>> >Best Regards,
>> >Ildikó
>> >
>> >> -Original Message-
>> >> 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 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 up? I've got it on my schedule to come the  week
>> >>after.
>> >>
>> >> I suspect there's a lot we can do over the long run to avoid
>> >>duplicating code and effort but that there will be some humps to ride
>> >>over  to different pieces (and people!) talking to one another.
>> >> Should be fun. Looking forward to it.
>> >>
>> >> --
>> >> Chris Dent tw:@anticdent freenode:cdent
>> >> https://tank.peermore.com/tanks/cdent
>> >>
>> >>
>> >>__
>> >>___
>> >>_
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe:
>> >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >___
>> >___ OpenStack Development Mailing List (not for usage questions)
>> >Unsubscribe:
>> >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-16 Thread Ildikó Váncsa

Hi Roland,

Thanks for the meeting info.

Let me come back to you regarding the attendance of the next Monasca meeting. I 
messed up with time zones and slots a bit and I realized now that the slot is 
4pm UTC as opposed to 3pm UTC as I originally thought. I have a bi-weekly 
meeting in my calendar colliding with the upcoming slot, but for the past few 
occurrences it was cancelled, I need to check the next one with the organizer.

If I can attend, I can briefly talk about the componentization work.

Best Regards,
Ildikó

> -Original Message-
> From: Hochmuth, Roland M [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 an overview and current status/plans of
> the Ceilometer work around the componentization? I was at the discussion in 
> Vancouver on this, and several others from Monasca
> were there too, but I haven't stayed connected.
> 
> The information for the Monasca Meetings as well as minutes is at, 
> https://wiki.openstack.org/wiki/Meetings/Monasca. If you have
> any problems connecting in, please let me know. We recently switched to 
> WebEx, which is hosted by Cisco. Everything should work,
> but if there are any problems we can switch to IRC.
> 
> If Tuesday's at 4:00 PM UTC are problematic, then we would consider setting 
> up a separate time to cover this topic or move the
> Monasca meeting the following week.
> 
> Regards --Roland
> 
> 
> 
> On 8/14/15, 6:57 AM, "Ildikó Váncsa"  wrote:
> 
> >Hi,
> >
> >I will try to join if I can, I have an overlapping meeting on Tuesdays.
> >
> >In general I think it would be really good to start a closer
> >collaboration, the componentization work in Ceilometer gives a really
> >good opportunity as Chris described.
> >
> >Best Regards,
> >Ildikó
> >
> >> -Original Message-
> >> 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 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 up? I've got it on my schedule to come the  week
> >>after.
> >>
> >> I suspect there's a lot we can do over the long run to avoid
> >>duplicating code and effort but that there will be some humps to ride
> >>over  to different pieces (and people!) talking to one another.
> >> Should be fun. Looking forward to it.
> >>
> >> --
> >> Chris Dent tw:@anticdent freenode:cdent
> >> https://tank.peermore.com/tanks/cdent
> >>
> >>
> >>__
> >>___
> >>_
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe:
> >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >___
> >___ OpenStack Development Mailing List (not for usage questions)
> >Unsubscribe:
> >openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-16 Thread Hochmuth, Roland M

Hi Ildikó, That will be great if you can attend. If you do, would it be
possible for you to present an overview and current status/plans of the
Ceilometer work around the componentization? I was at the discussion in
Vancouver on this, and several others from Monasca were there too, but I
haven't stayed connected.

The information for the Monasca Meetings as well as minutes is at,
https://wiki.openstack.org/wiki/Meetings/Monasca. If you have any problems
connecting in, please let me know. We recently switched to WebEx, which is
hosted by Cisco. Everything should work, but if there are any problems we
can switch to IRC.

If Tuesday's at 4:00 PM UTC are problematic, then we would consider
setting up a separate time to cover this topic or move the Monasca meeting
the following week.

Regards --Roland

On 8/14/15, 6:57 AM, "Ildikó Váncsa"  wrote:

>Hi,
>
>I will try to join if I can, I have an overlapping meeting on Tuesdays.
>
>In general I think it would be really good to start a closer
>collaboration, the componentization work in Ceilometer gives a really
>good opportunity as Chris described.
>
>Best Regards,
>Ildikó
>
>> -Original Message-
>> 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 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 up? I've got it on my schedule to come the
>> week after.
>> 
>> I suspect there's a lot we can do over the long run to avoid
>>duplicating code and effort but that there will be some humps to ride
>>over
>> to different pieces (and people!) talking to one another.
>> Should be fun. Looking forward to it.
>> 
>> --
>> Chris Dent tw:@anticdent freenode:cdent
>> https://tank.peermore.com/tanks/cdent
>> 
>> 
>>_
>>_
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-14 Thread Dexter Fryar



> 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 it would be really good to start a closer collaboration, 
> the componentization work in Ceilometer gives a really good opportunity as 
> Chris described.
> 
> Best Regards,
> Ildikó
> 
> > -Original Message-
> > 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 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 up? I've got it on my schedule to come the
> > week after.
> > 
> > I suspect there's a lot we can do over the long run to avoid duplicating 
> > code and effort but that there will be some humps to ride over
> > to different pieces (and people!) talking to one another.
> > Should be fun. Looking forward to it.
> > 
> > --
> > Chris Dent tw:@anticdent freenode:cdent
> > https://tank.peermore.com/tanks/cdent
> > 
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
  __
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-14 Thread Ildikó Váncsa

Hi,

I will try to join if I can, I have an overlapping meeting on Tuesdays.

In general I think it would be really good to start a closer collaboration, the 
componentization work in Ceilometer gives a really good opportunity as Chris 
described.

Best Regards,
Ildikó

> -Original Message-
> 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 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 up? I've got it on my schedule to come the
> week after.
> 
> I suspect there's a lot we can do over the long run to avoid duplicating code 
> and effort but that there will be some humps to ride over
> to different pieces (and people!) talking to one another.
> Should be fun. Looking forward to it.
> 
> --
> Chris Dent tw:@anticdent freenode:cdent
> https://tank.peermore.com/tanks/cdent
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-12 Thread Chris Dent


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 up? I've got it on my schedule to come the week
after.

I suspect there's a lot we can do over the long run to avoid
duplicating code and effort but that there will be some humps to
ride over to different pieces (and people!) talking to one another.
Should be fun. Looking forward to it.

--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-11 Thread Hochmuth, Roland M

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 should probably get together prior to the Tokyo Summit to
plan further.

The work that you are doing to split-out components is very interesting to
the Monasca project. We were really interested in the direction that this
was headed. As you mention, the Ceilometer data collection pipeline is
extremely interesting to Monasca. The work that we've been doing around
what we refer to as Ceilosca, is where we see immediate utilization. I
think you were at the session in Vancouver where some folks mentioned the
possibility of using the Ceilometer data collection pipeline to send to
Monasca, and that aligns with our thoughts too.

Although the Monasca Agent supports collecting a lot of different metrics,
the one area that it needs additional capabilities is collecting metrics
and events for OpenStack resources. The Monasca Agent supports collecting
metrics for instances/Vms, but we would like to add support for the rest
of the OpenStack resources and don't want to re-create this in our Agent.
Currently, we've been addressing this problem via a Ceilometer to Monasca
publisher in the repo at, https://github.com/stackforge/monasca-ceilometer.

The alarm system, called Aodh, is also potentially interesting. Monasca
also has a alarm/threshold engine that is an in-memory streaming alarm
engine based on Apache Storm. Everything in Monasca has been ported to
Python, except for the Monasca Threshold Engine. As Aodh is written in
Python already, maybe it could be a drop in Python replacement for our
existing Threshold Engine as we would like to get the remaining component
moved over to Python.

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.

Regards --Roland

On 8/11/15, 1:53 AM, "Chris Dent"  wrote:

>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 thing I noticed was a section on summit activities about joint
>sessions with other projects. I'd like to encourage Monasca folk and
>Ceilometer folk to have at least one joint session.
>
>Many people within the Ceilometer project are working hard to decompose
>its various bits of functionality to make it more usable in diverse
>toolchains. Making sure that the extracted alarm system (now called
>Aodh) and the forthcoming extracted polling system will be useful to
>Monasca is a priority.
>
>Some parts of Ceilometer (the data gathering aspects perhaps?)
>presumably have greater potential use to Monasca than others (the
>legacy mongodb and SQL-based datastores). Working together to
>ensure interoperability of the important parts would be good.
>
>I think present-day Ceilometer and Monasca are working on the same goal:
>Making an alternative to the old Ceilometer. It seems likely there is
>some productive collaboration that can happen?
>
>-- 
>Chris Dent tw:@anticdent freenode:cdent
>https://tank.peermore.com/tanks/cdent
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-11 Thread Chris Dent


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 thing I noticed was a section on summit activities about joint
sessions with other projects. I'd like to encourage Monasca folk and
Ceilometer folk to have at least one joint session.

Many people within the Ceilometer project are working hard to decompose
its various bits of functionality to make it more usable in diverse
toolchains. Making sure that the extracted alarm system (now called
Aodh) and the forthcoming extracted polling system will be useful to
Monasca is a priority.

Some parts of Ceilometer (the data gathering aspects perhaps?)
presumably have greater potential use to Monasca than others (the
legacy mongodb and SQL-based datastores). Working together to
ensure interoperability of the important parts would be good.

I think present-day Ceilometer and Monasca are working on the same goal:
Making an alternative to the old Ceilometer. It seems likely there is
some productive collaboration that can happen?

--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-08-10 Thread Hochmuth, Roland M

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 like further clarification please
let me know.

Regards --Roland


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-07-23 Thread Hochmuth, Roland M

Hi Chandeep, The official dates of the meet up are

When:
August 05-06 2015.

Where:
HP Building 6
Lower level (street level) Room C6/7 (6LC7/9)
3404 E Harmony Rd (Ziegler), Fort Collins, CO 80528, United States

The information is at the Etherpad. We'll probably start at around 8:30 or
9:00 AM MST both days.

Sorry about the short-notice.

Regards --Roland



On 7/23/15, 5:39 PM, "Chandeep Khamba"  wrote:

>Roland, 
>
>Could you please specify the time of the meetup , I need to book my
>Airtickes accordingly
>
>On 7/23/15, 4:30 PM, "Chandeep Khamba"  wrote:
>
>>Hi Roland,
>>
>>I am still a newbie to Monasca  , but would like to hear and participate
>>in the agenda items we already have.
>>If I have something specific would definitely add it.
>>
>>Thanks
>>
>>On 7/23/15, 1:58 PM, "Hochmuth, Roland M"  wrote:
>>
>>>Hi Chandeep, There are no fees. It would be great if you could join us.
>>>Also, please feel free to add to the agenda topics that you would like
>>>to
>>>cover.
>>>
>>>If you are traveling, I can advise on hotels.
>>>
>>>Regards --Roland
>>>
>>>
>>>From: Chandeep Khamba mailto:ckha...@cray.com>>
>>>Reply-To: OpenStack List
>>>mailto:openstack-dev@lists.openstack.
>>>o
>>>r
>>>g>>
>>>Date: Thursday, July 23, 2015 at 2:16 PM
>>>To: OpenStack List
>>>mailto: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 in .
>>>
>>>Thanks
>>>CHandeep
>>>
>>>
>>>_
>>>_
>>>OpenStack Development Mailing List (not for usage questions)
>>>Unsubscribe: 
>>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>_
>>_
>>OpenStack Development Mailing List (not for usage questions)
>>Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-07-23 Thread Chandeep Khamba

Roland, 

Could you please specify the time of the meetup , I need to book my
Airtickes accordingly

On 7/23/15, 4:30 PM, "Chandeep Khamba"  wrote:

>Hi Roland,
>
>I am still a newbie to Monasca  , but would like to hear and participate
>in the agenda items we already have.
>If I have something specific would definitely add it.
>
>Thanks
>
>On 7/23/15, 1:58 PM, "Hochmuth, Roland M"  wrote:
>
>>Hi Chandeep, There are no fees. It would be great if you could join us.
>>Also, please feel free to add to the agenda topics that you would like to
>>cover.
>>
>>If you are traveling, I can advise on hotels.
>>
>>Regards --Roland
>>
>>
>>From: Chandeep Khamba mailto:ckha...@cray.com>>
>>Reply-To: OpenStack List
>>mailto:openstack-dev@lists.openstack.o
>>r
>>g>>
>>Date: Thursday, July 23, 2015 at 2:16 PM
>>To: OpenStack List
>>mailto: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 in .
>>
>>Thanks
>>CHandeep
>>
>>_
>>_
>>OpenStack Development Mailing List (not for usage questions)
>>Unsubscribe: 
>>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-07-23 Thread Chandeep Khamba

Hi Roland,

I am still a newbie to Monasca  , but would like to hear and participate
in the agenda items we already have.
If I have something specific would definitely add it.

Thanks

On 7/23/15, 1:58 PM, "Hochmuth, Roland M"  wrote:

>Hi Chandeep, There are no fees. It would be great if you could join us.
>Also, please feel free to add to the agenda topics that you would like to
>cover.
>
>If you are traveling, I can advise on hotels.
>
>Regards --Roland
>
>
>From: Chandeep Khamba mailto:ckha...@cray.com>>
>Reply-To: OpenStack List
>mailto:openstack-...@lists.openstack.or
>g>>
>Date: Thursday, July 23, 2015 at 2:16 PM
>To: OpenStack List
>mailto:openstack-...@lists.openstack.or
>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 in .
>
>Thanks
>CHandeep
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-07-23 Thread Hochmuth, Roland M

Hi Simon, Sorry, we don't have any information on our Wiki. Ceilosca leverages 
the Ceilometer data collection pipeline via a Ceilometer-Monasca Publisher and 
the Ceilometer API via a Ceilometer-Monasca Storage Driver and is completely 
compatible with the Ceilometer v2 API.

Regards --Roland


From: Simon Pasquier mailto:spasqu...@mirantis.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, July 22, 2015 at 2:08 PM
To: OpenStack List 
mailto:openstack-dev@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 to 
expose an API that would be compatible with the Ceilometer API?
BR,
Simon

On Wed, Jul 22, 2015 at 8:08 PM, Hochmuth, Roland M 
mailto:roland.hochm...@hp.com>> wrote:
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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-07-23 Thread Hochmuth, Roland M

Hi Chandeep, There are no fees. It would be great if you could join us. Also, 
please feel free to add to the agenda topics that you would like to cover.

If you are traveling, I can advise on hotels.

Regards --Roland


From: Chandeep Khamba mailto:ckha...@cray.com>>
Reply-To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, July 23, 2015 at 2:16 PM
To: OpenStack List 
mailto:openstack-dev@lists.openstack.org>>
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 in .

Thanks
CHandeep

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-07-23 Thread Chandeep Khamba

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
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-07-22 Thread Simon Pasquier

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,
Simon

On Wed, Jul 22, 2015 at 8:08 PM, Hochmuth, Roland M 
wrote:

> 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
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-07-22 Thread Hochmuth, Roland M

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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Monasca] Authentication through Keystone

2015-05-29 Thread Pradip Mukhopadhyay

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 other scheme to authenticate to Keystone?



Thanks in advance,
Pradip
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-05-15 Thread Everett Toews

On May 15, 2015, at 3:49 AM, Thierry Carrez  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 components, it seems reasonable 
>> to determine if there really exists a reason to do so. I’m interested in 
>> soliciting any feedback from the community be it pleasant or unpleasant.
> 
> Swift has not introduced components in Go. It is at the early stages of
> *exploring* the possibility of doing so, through a specific feature branch.
> 
> The Technical Committee position has always been "python unless there is
> a compelling reason otherwise". Every language supported increases
> fragmentation of our community and increases the CI effort. The argument
> for adding a language has to be pretty compelling to counterbalance the
> damage it does to "OpenStack" as a development community.
> 
> In Monasca's case, there is always the possibility to stay out of the
> "OpenStack" tent and stay in Java. There is the possibility to rewrite
> things in Python. And there is the possibility to convince the Technical
> Committee that (1) we want Monasca featureset in so badly we would add
> Java as a supported language just so that can happen and (2) Monasca
> featureset can't be written in Python.

Not to move this discussion off-list but I feel the need to at least point out 
a highly relevant summit session.

Is it time to have more than just Python in OpenStack?
https://libertydesignsummit.sched.org/event/6bb3f4fe34a4a0236266d99a2039c963

Everett


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-05-15 Thread Thierry Carrez

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 reason to do so. I’m interested in 
> soliciting any feedback from the community be it pleasant or unpleasant.

Swift has not introduced components in Go. It is at the early stages of
*exploring* the possibility of doing so, through a specific feature branch.

The Technical Committee position has always been "python unless there is
a compelling reason otherwise". Every language supported increases
fragmentation of our community and increases the CI effort. The argument
for adding a language has to be pretty compelling to counterbalance the
damage it does to "OpenStack" as a development community.

In Monasca's case, there is always the possibility to stay out of the
"OpenStack" tent and stay in Java. There is the possibility to rewrite
things in Python. And there is the possibility to convince the Technical
Committee that (1) we want Monasca featureset in so badly we would add
Java as a supported language just so that can happen and (2) Monasca
featureset can't be written in Python.

-- 
Thierry Carrez (ttx)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-05-14 Thread Dieterly, Deklan

Thanks, Kevin.

Performance is critical. At this point, we are trying to do 100K
measurements per second.

Yea, Vertica is not open source. Monasca uses either Vertica OR Influxdb
as the backend DB. You get to decide what you want.

Zookeeper is used by Kafka for distributed synchronization and is very
well regarded in the internet-applications realm.

It looks like what you are saying is that the issue goes beyond just Java
vs Python; it¹s an ops issue. There may be issues with supporting Kafka
and Influxdb. That¹s good feedback.

Interesting, at the 2014 Summit in Atlanta, the some members of the
community heavily lobbied for Influxdb. We¹ve seen perf problems with
MySQL in the Ceilometer Project and to wanted to avoid that by using a
scalable open source DB for the backend.

-- 
Deklan Dieterly

Software Engineer
HP




On 5/14/15, 10:34 AM, "Fox, Kevin M"  wrote:

>The open source version of java is much better off then it use to be, so
>I'd say its not out of the question any more. My preference is still
>python whenever possible since it tends to be much easer to debug/patch
>in the field. Performance critical stuff is another matter.
>
>I would recommend very strongly considering it from the standpoint of
>what distro's are willing to support, and how much additional
>learning/operations work you are asking of ops to perform though.
>OpenStack already pushes an enormous amount of learning onto the ops
>folks. This will make or break the project.
>
>yum list | grep -i influxdb | wc -l
>0
>
>hmm...
>the rpm from the website looks very unusual... The distro folks wont
>support a package that looks like that. My gut reaction looking at it as
>an op is to wince and hope I don't have to install it. If I were, I'd
>have to carefully pull it apart to figure out how to support it long
>term. Definitely not a rpm -Uvh and forget.
>
>Vertica doesn't look to be Open Source?
>
>Kafka yet another messaging system... It might be needed, but its yet
>another thing for ops to figure out how to deal with. The quickstart says
>Kafka needs Zookeeper. Now yet another dependency for an op to deal with.
>What does ZooKeeper give that Pacemaker (already used in a lot of clouds)
>doesn't?
>
>I might like to deploy Monasca here some day, but it looks like it will
>take a large amount of work for me to do so, relative to all the other
>OpenStack components I want 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] [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
>components up to parity with their Java counterparts. This effort is
>being undertaken because there seems to be considerable friction in
>introducing Java components into the OpenStack community. At this point,
>Id like to test the waters a bit and determine what the larger
>community¹s reaction to having these components remain in Java would be.
>Would there be a general acceptance or would there be a visceral
>rejection? Is the issue more of integration with existing CI/CD
>architecture or is there more of a cultural issue?
>
>The arguments for Java are non-trivial. Monasca has requirements for very
>high throughput. Furthermore, integration with Kafka is better supported
>with Kafka's Java libraries.
>
>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 reason to do so. I¹m
>interested in soliciting any feedback from the community be it pleasant
>or unpleasant.
>
>Thanks.
>
>‹
>Deklan Dieterly
>Software Engineer
>HP
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/lis

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

2015-05-14 Thread Fox, Kevin M

The open source version of java is much better off then it use to be, so I'd 
say its not out of the question any more. My preference is still python 
whenever possible since it tends to be much easer to debug/patch in the field. 
Performance critical stuff is another matter.

I would recommend very strongly considering it from the standpoint of what 
distro's are willing to support, and how much additional learning/operations 
work you are asking of ops to perform though. OpenStack already pushes an 
enormous amount of learning onto the ops folks. This will make or break the 
project.

yum list | grep -i influxdb | wc -l
0

hmm...
the rpm from the website looks very unusual... The distro folks wont support a 
package that looks like that. My gut reaction looking at it as an op is to 
wince and hope I don't have to install it. If I were, I'd have to carefully 
pull it apart to figure out how to support it long term. Definitely not a rpm 
-Uvh and forget.

Vertica doesn't look to be Open Source?

Kafka yet another messaging system... It might be needed, but its yet 
another thing for ops to figure out how to deal with. The quickstart says Kafka 
needs Zookeeper. Now yet another dependency for an op to deal with. What does 
ZooKeeper give that Pacemaker (already used in a lot of clouds) doesn't?

I might like to deploy Monasca here some day, but it looks like it will take a 
large amount of work for me to do so, relative to all the other OpenStack 
components I want 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] [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 components up 
to parity with their Java counterparts. This effort is being undertaken because 
there seems to be considerable friction in introducing Java components into the 
OpenStack community. At this point, Id like to test the waters a bit and 
determine what the larger community’s reaction to having these components 
remain in Java would be. Would there be a general acceptance or would there be 
a visceral rejection? Is the issue more of integration with existing CI/CD 
architecture or is there more of a cultural issue?

The arguments for Java are non-trivial. Monasca has requirements for very high 
throughput. Furthermore, integration with Kafka is better supported with 
Kafka's Java libraries.

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 reason to do so. I’m interested in 
soliciting any feedback from the community be it pleasant or unpleasant.

Thanks.

—
Deklan Dieterly
Software Engineer
HP

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [monasca] [java]

2015-05-14 Thread Dieterly, Deklan

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 components up 
to parity with their Java counterparts. This effort is being undertaken because 
there seems to be considerable friction in introducing Java components into the 
OpenStack community. At this point, Id like to test the waters a bit and 
determine what the larger community’s reaction to having these components 
remain in Java would be. Would there be a general acceptance or would there be 
a visceral rejection? Is the issue more of integration with existing CI/CD 
architecture or is there more of a cultural issue?

The arguments for Java are non-trivial. Monasca has requirements for very high 
throughput. Furthermore, integration with Kafka is better supported with 
Kafka's Java libraries.

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 reason to do so. I’m interested in 
soliciting any feedback from the community be it pleasant or unpleasant.

Thanks.

—
Deklan Dieterly
Software Engineer
HP

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2015-02-04 Thread Pradip Mukhopadhyay

Hello,


In Monasca-agent README here
 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 monasca-agent to the logfile
written in specific format - it can pick it up from there (the collector)
and send it to the monasca-api. Right?



Thanks.

Pradip
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

< 1 2

101 - 197 of 197 matches

Mail list logo