Re: [openstack-dev] [Monasca] Where Monasca stores collected Data?

. Hope it helps Witek From: amal kammoun Sent: Donnerstag, 25. Oktober 2018 17:10 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Monasca] Where Monasca stores collected Data? Hello Monasca team, I'm experiencing several problems with monasca. I have Monasca running with OpenStack. I

[openstack-dev] [Monasca] Where Monasca stores collected Data?

Hello Monasca team, I'm experiencing several problems with monasca. I have Monasca running with OpenStack. I added alarms to my system but I cannot see where monasca stores the collected data. With Grafana I cannot see any datapoints from the influxdb datasource. In the influxdb I have all the

[openstack-dev] [monasca][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Monasca team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help

Re: [openstack-dev] [Monasca] [monasca-Agent] Monasca agent problem

is configured to send the measurements for project ‘customer1’, the alarm won’t get triggered in either of them. Best regards Witek From: amal kammoun Sent: Montag, 8. Oktober 2018 12:03 To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Monasca] [monasca-Agent] Monasca agent problem

[openstack-dev] [Monasca] [monasca-Agent] Monasca agent problem

Hello, I have an issue with the monasca Agent. In fact, I installed monasca with Openstack using devstack. I want to minitor now the instances deployed using Openstack. For that I installed on each instance the monasca agent with the following link:

[openstack-dev] Monasca agent problem

Hello, I have an issue with the monasca Agent. In fact, I installed monasca with Openstack using devstack. I want to minitor now the instances deployed using Openstack. For that I installed on each instance the monasca agent with the following link:

[openstack-dev] [monasca] Berlin Forum brainstorming

Hi everyone, As discussed in the team meeting yesterday I've created a brainstorming etherpad [1] for the Forum in Berlin. Please add your ideas and add your name to the list if you're interested in participating. Thanks Witek [1]

Re: [openstack-dev] [monasca]

kammoun Sent: Monday, September 10, 2018 10:42 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [monasca] Hello, I'm using devstack to have openstack. I installed also monasca using the following link: https://github.com/openstack/monasca-api/tree/master/devstack The problem

[openstack-dev] [monasca]

Hello, I'm using devstack to have openstack. I installed also monasca using the following link: https://github.com/openstack/monasca-api/tree/master/devstack The problem is that when I log in from horizon, The openstack services and servers are empty on the monitoring tab. What should I do in

Re: [openstack-dev] [monasca][goal][python3] monasca's zuul migration is only partially complete

On 23/08/18 13:34, Doug Hellmann wrote: Excerpts from Doug Szumski's message of 2018-08-23 09:53:35 +0100: Thanks Doug, we had a discussion and we agreed that the best way to proceed is for you to submit your patches and we will carefully review them. I proposed those patches this morning.

Re: [openstack-dev] [monasca][goal][python3] monasca's zuul migration is only partially complete

Excerpts from Doug Szumski's message of 2018-08-23 09:53:35 +0100: > Thanks Doug, we had a discussion and we agreed that the best way to > proceed is for you to submit your patches and we will carefully review them. I proposed those patches this morning. With the aid of your exemplary

Re: [openstack-dev] [monasca][goal][python3] monasca's zuul migration is only partially complete

Reply in-line. On 23/08/18 00:32, Doug Hellmann wrote: Monasca team, It looks like you have self-proposed some, but not all, of the patches to import the zuul settings into monasca repositories. I found these:

[openstack-dev] [monasca][goal][python3] monasca's zuul migration is only partially complete

Monasca team, It looks like you have self-proposed some, but not all, of the patches to import the zuul settings into monasca repositories. I found these:

[openstack-dev] [monasca] Vacation

Hello everyone, I'll be on vacation until August 31st. My deputies in that time will be: * Doug Szumski (dougsz) and * Dobrosław Żybort (Dobroslaw) Thanks a lot Witek __ OpenStack Development Mailing List (not for usage

[openstack-dev] [monasca] Etharpad for Stein PTG in Denver

Hello, I've just created an etherpad [1] for planning our sessions at the next PTG in Denver. Please add the topics you'd like to discuss. The main goal of the sessions is to agree on development priorities and coordinate the work for the next release cycle. Please also don't forget to add

[openstack-dev] [monasca] Nominating Doug Szumski as Monasca core

Hello Monasca team, I would like to nominate Doug Szumski (dougsz) for Monasca core team. He actively contributes to the project and works on adding Monasca to kolla-ansible. He has good project overview which he shares in his reviews. Best greetings Witek

[openstack-dev] [monasca] Monasca PTG participation survey

Hello everyone, The next PTG will take place September 10-14, 2018 in Denver, Colorado [1]. Again we have to decide if Monasca will participate and gather together with other projects. The last PTG was a great success which is measurable in new code already submitted and number of reviews. But

[openstack-dev] [monasca] PTG follow-up

Hello everyone, I hope all of you attending the PTG in Dublin could meanwhile get safely home. For those not attending, a short update, because of Storm Emma red alert had been introduced last week in Ireland and the conference venue had to be closed on Thursday and Friday. We have decided to

Re: [openstack-dev] [monasca][congress] help configuring monasca for gate

g, 13. Februar 2018 03:59 >> To: OpenStack Development Mailing List (not for usage questions) >> <openstack-dev@lists.openstack.org> >> Subject: Re: [openstack-dev] [monasca][congress] help configuring >>monasca >> for gate >> >> Oops. Nevermind. Looks lik

Re: [openstack-dev] [monasca][congress] help configuring monasca for gate

018 03:59 > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [monasca][congress] help configuring monasca > for gate > > Oops. Nevermind. Looks like it's working now. > > On

Re: [openstack-dev] [monasca][congress] help configuring monasca for gate

Oops. Nevermind. Looks like it's working now. On 2/12/18, 5:00 PM, "Eric K" wrote: >Hi Monasca folks, >I'm trying to configure monasca in congress gate [1] and modeled it after >this monasca playbook [2]. But I get: >rsync: change_dir

[openstack-dev] [monasca][congress] help configuring monasca for gate

Hi Monasca folks, I'm trying to configure monasca in congress gate [1] and modeled it after this monasca playbook [2]. But I get: rsync: change_dir "/home/zuul/src/*/openstack/monasca-common" failed: No such file or directory (2)

[openstack-dev] [monasca] Feature freeze lifted

Hello, Yesterday I have created stable/queens branches for our repos. It will be used to create the final Queens release. We can continue the work on new features on master. Cheers Witek __ OpenStack Development Mailing

[openstack-dev] [monasca] Remove MySQL Connector from monasca-thresh

Hello, During the internal legal check we've noticed that monasca-threshold Java archive includes MySQL Connector which is licensed under GPLv2. This license restricts the distribution of the consuming project and is not aligned with OpenStack licensing requirements [1]. I'm proposing to

[openstack-dev] [monasca] PTL candidacy

Hello everyone, I would like to announce my candidacy to continue as PTL of Monasca for the Rocky release. I have worked for the project as core reviewer since 2015, acted as Release Management Liaison in Ocata and Pike and had a privilege of being PTL in Queens release cycle. I have learnt a

[openstack-dev] [monasca] Contribution from T-Systems

Hi Yuan, Thanks for reaching out to us in the team meeting. I'm happy to hear you want to contribute your changes to the project. You can find our contribution guidelines here [1]. The general OpenStack Developer's Guide is here [2]. Which components/topics are you interested in, in terms of

[openstack-dev] [monasca] RE: alarm transition events are missing in kafka queue - mysql alarm state is updated properly

Hi Yuan, please compare similar issue described in this bug report [1] and the corresponding fix [2]. As Craig explained in his comment to patch set 4, Kafka server closes idle connections after around 10 minutes, which causes first write to the topic fail. I hope it helps. Witek [1]

[openstack-dev] [monasca] Nominate Amir Mofakhar to Monasca core

Hello everyone, I would like to nominate Amir Mofakhar to the Monasca core reviewers team. Welcome onboard, Witek __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [monasca] Monasca at PTG in Dublin

Hello, As discussed in the meeting today I would like to ask for your opinion if Monasca team should gather at the Project Teams Gathering (PTG) event in Dublin, February 26 - March 2nd [1]. The goal of the PTG is "to discuss priorities for the upcoming cycle, iterate quickly on solutions for

Re: [openstack-dev] [monasca] New Team Meeting Time doodle

Hello, I'm sorry for the late notice. I have moved the meeting one hour later. The new meeting time is: Wednesday, 1500 UTC #openstack-meeting-3 See you there, Witek > -Original Message- > From: Bedyk, Witold > Sent: Mittwoch, 15. November 2017 17:16 > To: 'OpenStack Development

[openstack-dev] [monasca] New Team Meeting Time doodle

Hello everyone, We would like to choose the optimal time for our Team Meeting. I have created a doodle [1] for that. Please put your preferences until Monday 1200 UTC if you want to attend the meeting. Cheers Witek [1] https://doodle.com/poll/s5fwqtu7ik898p57

Re: [openstack-dev] [Monasca] [wiki] Where is GUI tutorial of Monasca

://github.com/witekest/monasca-bootcamp/blob/master/Monasca%20Bootcamp.ipynb > -Original Message- > From: Kodama, Takeyuki [mailto:kodama.takey...@jp.fujitsu.com] > Sent: Mittwoch, 4. Oktober 2017 09:01 > To: 'openstack-dev@lists.openstack.org' d...@lists.openstack.org> > Subje

Re: [openstack-dev] [Monasca] Query for the official document of Monasca manual installation on openstack

/security.py [4] https://github.com/monasca/monasca-docker/tree/master/monasca-api-python#configuration > -Original Message- > From: manik bindlish [mailto:manikbindlis...@gmail.com] > Sent: Dienstag, 3. Oktober 2017 15:21 > To: openstack-dev@lists.openstack.org > Subject:

[openstack-dev] [Monasca] [wiki] Where is GUI tutorial of Monasca

Hi I'm very grateful that if you consider my request. Would you tell me where the tutorial of Monasca is, especially after installation? If it does not exist, it is helpful for us to add the tutorial on wiki page. https://wiki.openstack.org/wiki/Monasca Especially, I would like to know the

[openstack-dev] [Monasca] Query for the official document of Monasca manual installation on openstack

Hi, I have a query regarding manual installation of Monasca on Openstack. Please let me know the official document or link for manually node wise installation of Monasca(completely) on Openstack I have to integrate Monasca with Congress(Openstack: Newton). Configuration is: 1 Controller node +

Re: [openstack-dev] [monasca] Stefano Canepa and Dobrosław Żybort in Monasca core team

On Tue, Sep 26, 2017 at 11:26:55AM +, Bedyk, Witold wrote: > Hello everyone, > > I would like to nominate Stefano Canepa and Dobrosław Żybort to Monasca core > reviewers team. > Welcome and thank you for your contribution to the project. > > > Best regards > Witek Thanks Witek. Bye sc

[openstack-dev] [monasca] Stefano Canepa and Dobrosław Żybort in Monasca core team

Hello everyone, I would like to nominate Stefano Canepa and Dobrosław Żybort to Monasca core reviewers team. Welcome and thank you for your contribution to the project. Best regards Witek __ OpenStack Development Mailing

[openstack-dev] [monasca] Queens Mid-Cycle

Hello everyone, Monasca team will hold a Mid-Cycle meeting for the Queens release on Sep. 20th and 21st via remote conferencing. Please add the topics you would like to discuss or features you would like to see in the next release to the etherpad [1]. The connection details are included in the

Re: [openstack-dev] [Monasca] GridDB repository support

On 28/08/17 10:32 AM, witold.be...@est.fujitsu.com wrote: > The number looks good but the test you have referenced was performed with the > file storage driver which is not really scalable. It would be great if you > could provide numbers for the Ceph backend. > Please keep us updated. these

Re: [openstack-dev] [Monasca] GridDB repository support

> > Subject: Re: [openstack-dev] [Monasca] GridDB repository support > > On Mon, Aug 28 2017, witold.be...@est.fujitsu.com wrote: > > > Can you give some reference to Gnocchi's performance measurements? > > I have seen you presentation from the last Summit [1] b

Re: [openstack-dev] [Monasca] GridDB repository support

On Mon, Aug 28 2017, witold.be...@est.fujitsu.com wrote: > Can you give some reference to Gnocchi's performance measurements? > I have seen you presentation from the last Summit [1] but I cannot find > information about Gnocchi's write throughput. In the issues slide you note the > slow post API.

Re: [openstack-dev] [Monasca] GridDB repository support

penstack.org> > Subject: Re: [openstack-dev] [Monasca] GridDB repository support > We don't have any recent comparison with InfluxDB but last time we tried, > Gnocchi was already getting faster than it. And scalable horizontally, so… Hi Julien, Can you give some reference to Gnocchi's pe

Re: [openstack-dev] [Monasca] GridDB repository support

o:akirayoshiy...@gmail.com] >> Sent: Samstag, 19. August 2017 15:31 >> To: OpenStack Development Mailing List > d...@lists.openstack.org> >> Subject: [openstack-dev] [Monasca] GridDB repository support >> >> Hi all, >> >> Toshiba GridDB[1][2] is a highly sc

Re: [openstack-dev] [Monasca] GridDB repository support

On Tue, Aug 22 2017, witold.be...@est.fujitsu.com wrote: Hi Witek, > thank you for your contribution. We indeed urgently need a scalable open > source TSDB. Did you look at Gnocchi? It's exactly that. http://gnocchi.xyz/ > In the recent weeks James Gu and his team have re-evaluated using

Re: [openstack-dev] [Monasca] GridDB repository support

://etherpad.openstack.org/p/cassandra_monasca > -Original Message- > From: Akira Yoshiyama [mailto:akirayoshiy...@gmail.com] > Sent: Samstag, 19. August 2017 15:31 > To: OpenStack Development Mailing List d...@lists.openstack.org> > Subject: [openstack-dev] [Monasca] GridDB

[openstack-dev] [Monasca] GridDB repository support

Hi all, Toshiba GridDB[1][2] is a highly scalable distributed NoSQL database for IoT and Big Data. It has very good scalability and performance[3]. It also has Community Edition licensed under GNU AGPL v3 and the source code is available at Github[4][5][6]. It looks suitable for Monasca

[openstack-dev] [monasca] Mid-cycle project team meeting

Hello everyone, as discussed yesterday in the Team Meeting there will be no Monasca planning session during the PTG. Instead we will hold a video conference one week later. The goal is to discuss the priorities and coordinate the work in the next release cycle. Please mark the dates which

[openstack-dev] [monasca] PTL candidacy for Queens

Hello everyone, I would like to propose my candidacy for the role of Monasca PTL for Queens release. I would like to thank Roland, who has been the PTL for several releases now and has always pushed the project forward. Your working quota seems to be unlimited, I reckon you work at sleep as well

Re: [openstack-dev] [monasca] Stable branch for Pike

Excerpts from witold.be...@est.fujitsu.com's message of 2017-08-03 13:27:14 +: > Hello Monasca team, > > Following the Pike release schedule I would like to cut the stable branch for > Pike release early next week. We will use it to create the final release at > the end of August. > >

[openstack-dev] [monasca] Stable branch for Pike

Hello Monasca team, Following the Pike release schedule I would like to cut the stable branch for Pike release early next week. We will use it to create the final release at the end of August. Please let me know of release-critical bugs which should be merged before. Cheers Witek

[openstack-dev] [monasca] Skip next team meeting

Hello folks, due to holiday time in US I suggest to skip the next Monasca team meeting on Wednesday, July the 5th. Please reply here if you have important topics to discuss and would like to hold the meeting anyway. Cheers Witek

[openstack-dev] [monasca] New time and place of Monasca Team Meeting

Hello, this is just a reminder of the new place and time of the Monasca Team Meeting. It takes place weekly on Wednesday at 1400 UTC in #openstack-meeting See you there Witek __ OpenStack Development Mailing List (not

[openstack-dev] [monasca] Monasca at PTG in Denver

Hi, I wanted to ask who of you would be interested in attending dedicated Monasca sessions during the next Project Teams Gathering in Denver, September 11-15, 2017 [1]. The team room would probably be booked for one or two days. Alternatively we could organize the remote mid-cycle meeting, as

[openstack-dev] Monasca with out openstack

Hi all, I want to install the monsaca with out openstack. for the alternative of keystone, i want to use the openladap. but i didn't find any configuration and any help on web. any thoughts and suggestions on this ?? Best Regards *Shahzaib*

Re: [openstack-dev] [monasca][swift][storyboard] migration experience

On 2017-04-21 09:00:47 + (+), witold.be...@est.fujitsu.com wrote: > one thing which hasn't been migrated are the blueprints. We have > noticed this after the migration. Storyboard team has said they > had not planned on migrating blueprints because most of the > projects use the specs

Re: [openstack-dev] [monasca][swift][storyboard] migration experience

> >2) Are you missing anything from the migration? How do you manage > >security bugs that are embargoed? Hi John, one thing which hasn't been migrated are the blueprints. We have noticed this after the migration. Storyboard team has said they had not planned on migrating blueprints because

Re: [openstack-dev] [monasca][swift][storyboard] migration experience

Hi John, Comments in-line below. I'm hoping that someone else will add more details. On 4/17/17, 2:50 PM, "John Dickinson" wrote: >Moasca-teers > >As the migration away from Launchpad and to Storyboard moves forward, >the Swift team has been considering making the move. Monasca

[openstack-dev] [monasca][swift][storyboard] migration experience

Moasca-teers As the migration away from Launchpad and to Storyboard moves forward, the Swift team has been considering making the move. Monasca has already made the move, so I'd love to hear your thoughts on that process. 1) How did you do the change? All at once or gradually? If you did it over

Re: [openstack-dev] [monasca] Grafana "app" for Monasca

Hi Roland, That's great to hear. Initially it was only an experiment to see what could be done inside Grafana with its "app plugin" concept, but progressed quite fast into something quite usable, so thought we'd share it early on. Yes I've been following the Grafana progress quite closely. So as

Re: [openstack-dev] [monasca] Grafana "app" for Monasca

Hi Steve, This is awesome. We are very interested in this work! I was just talking to Grafana Labs about this. I should also mention that we are in the process of getting Keystone authentication built-in to Grafana so that we don't have to maintain a separate fork. I'm assuming that work will

[openstack-dev] [monasca] Grafana "app" for Monasca

Hi, We have been working on prototyping an "app" for Grafana which can be used to view/configure alarm definitions, notifications and alarms. This is still work-in-progress (insert normal disclaimer here), but is usable enough to get a feel for what we would like to achieve. We would like some

Re: [openstack-dev] [monasca] future of thresholder on Storm

tack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [monasca] future of thresholder on Storm Hi all, What are your plans for the Monasca thresholder on Apach

[openstack-dev] [monasca] future of thresholder on Storm

Hi all, What are your plans for the Monasca thresholder on Apache Storm, especially with respect to the upcoming Monasca query language? I saw that there is a component monasca-transform that is based on Apache Spark. Are there plans to build a new alarming engine on Spark that is for example

Re: [openstack-dev] [monasca] cassandra support in Monasca

g List (not for usage questions) <openstack-dev@lists.openstack.org>; roland.hochm...@hpe.com Subject: Re: [openstack-dev] [monasca] cassandra support in Monasca Hello, I have registered a BP[1] for that. Please let me know if you have any concerns. [1]https://blueprints.launchpad.net/m

Re: [openstack-dev] [monasca] cassandra support in Monasca

elopment Mailing List (not for usage questions) > > <openstack-dev@lists.openstack.org> > > Cc: Kawabata Shinya <s-kawab...@wx.jp.nec.com>; > > santhosh.fernan...@gmail.com > > Subject: [openstack-dev][monasca] cassandra support in Monasca > > > > Hello, &

[openstack-dev] [monasca] Baremetal and LXD monitoring

Hi All, Do we have support for Baremetal and LXD monitoring in monasca? Are we planning this support ? Thanks, Santhosh __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [monasca] cassandra support in Monasca

<openstack-dev@lists.openstack.org> > Cc: Kawabata Shinya <s-kawab...@wx.jp.nec.com>; > santhosh.fernan...@gmail.com > Subject: [openstack-dev][monasca] cassandra support in Monasca > > Hello, > > Could you please suggest status of Cassandra support in M

[openstack-dev] [monasca] cassandra support in Monasca

Hello, Could you please suggest status of Cassandra support in Monasca. Is there any plan to support kairosdb? If it is not implemented then we can take kairosdb support work. Thanks, Pradeep Singh __ OpenStack Development

Re: [openstack-dev] [monasca] Ideas to work on

Hi Roland I went on holiday for last week. I’ll send you a notification next time. Sorry for being absent from last weekly meeting. According to the comments that you gave, I can see the retention policy partly depends on metrics deleting. There can also be an option that we make a patch for

Re: [openstack-dev] [monasca] Ideas to work on

Hi Anqi, See my comments listed below. Regards --Roland From: An Qi YL Lu > Date: Sunday, February 12, 2017 at 8:29 PM To: Roland Hochmuth > Cc: OpenStack List

[openstack-dev] [monasca] Log Query API Design

Hi, For those interested, I have been expanding on the initial design for a simple query API to add to monasca-log-api. The design is available here: https://wiki.openstack.org/wiki/Monasca/Logging/Query_API_Design#Design:_Log_Listing I have proposed the initial "Log Listing" part of the API

Re: [openstack-dev] [monasca] Ideas to work on

Hi, Here the URL to monasca-log-api documentation [1]. Cheers Witek [1] https://github.com/openstack/monasca-log-api/tree/master/documentation I would like to look at logs publishing as well. But unfortunately I did not find the monasca-log-api doc, which is supposed to be at

[openstack-dev] [monasca] Failed to upgrade monasca source code in devstack

Hi all I failed to do the unstack and stack operations with devstack when I want to pull the latest Monasca code and upgrade related projects. I took following steps: go to /opt/stackgo to the monasca project folder that I want to upgraderun git pullrun unstack.sh

Re: [openstack-dev] [monasca] Ideas to work on

Hi Roland   I am not sure whether you received my last email because I got a delivery failure notification. I am sending this again to ensure that you can see this email.   Best, Anqi   - Original message -From: An Qi YL Lu/China/IBMTo: roland.hochm...@hpe.comCc:

[openstack-dev] [monasca] Ideas to work on

Hi Anqi, You had expressed a strong interest in working on Monasca the other day in our Weekly Monasca Team Meeting. I owed you a response. The team had also asked me to also keep them in the loop. Here is a list that I feel is interesting, that is not trivial or extremely complex (just right

[openstack-dev] [monasca] Monasca Ocata midcycle

Hi Everyone, We will be holding a Monasca Midcycle on Wednesday February 22nd, and Thursday February 23rd, 2017, via Lync/Skype video conferencing. The etherpad for the midcycle is located at, https://etherpad.openstack.org/p/monasca_ocata_midcycle. The etherpad has the Lync/Skype connection

Re: [openstack-dev] [Monasca] Monasca devstack installation is failing

.org<mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, January 4, 2017 at 11:33 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Monas

[openstack-dev] [Monasca] Monasca devstack installation is failing

*Hello,* *I am trying to install Monasca devstack using vagrant file given in monasca-ui repo.* *And its failing again and again with below error.* *Could you please help me, i will really appreciate your help.* ==> default: 2017-01-05 06:28:06.125 | ++ functions-common:start_service:2306

Re: [openstack-dev] [monasca]Monasca event handling capabilities

mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [monasca]Monasca event handling capabilities Hello, Please excuse me if i asked this question on wrong mailing list. I have few queries related to Monasca. 1) How do Monasca collects events releases by other openstack

Re: [openstack-dev] [Monasca]

ev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Monasca] Hello, I have a clean install of monasca-api and monasca-log-management plugins with devstack on ubuntu 14.04. However when I try usi

[openstack-dev] [monasca]Monasca event handling capabilities

Hello, Please excuse me if i asked this question on wrong mailing list. I have few queries related to Monasca. 1) How do Monasca collects events releases by other openstack services like Nova and Cinder? 2) Can monasca collects the metrics from Neutron and other SDN controllers? please guide

[openstack-dev] [Monasca]

Hello, I have a clean install of monasca-api and monasca-log-management plugins with devstack on ubuntu 14.04. However when I try using the monasca CLI, I get HTTP 503:Service Unavailable error. I tried accessing the monasca dashboard in Horizon, but that also throws error. ubuntu@monasca:~$

[openstack-dev] [monasca] Team meeting on 28 Dec

Hello everyone, should we cancel the team meeting on 28 Dec? Most of us will be in vacation I assume. Greetings Witek __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [monasca][oslo] (Re: [oslo] Should we drop kafka driver ?)

On Wed, Nov 30, 2016 at 05:44:25PM +0100, Mehdi Abaakouk wrote: Also, capping libraries is always a bad idea, this is one more example of why. The lib was capped due to an python-kafka upstream bugs and not API breakage. Something like != 1.0.0 would be sufficient. I have proposed to uncap

Re: [openstack-dev] [monasca][oslo] (Re: [oslo] Should we drop kafka driver ?)

Le 2016-11-30 16:56, Davanum Srinivas a écrit : Problem is with Monasca team having concerns with later python-kafka versions https://bugs.launchpad.net/oslo.messaging/+bug/1639264 Good point, the bug is 1 month old, but the issue is known since 7 months. At this point I think if we want

[openstack-dev] [monasca][oslo] (Re: [oslo] Should we drop kafka driver ?)

Mehdi, Problem is with Monasca team having concerns with later python-kafka versions https://bugs.launchpad.net/oslo.messaging/+bug/1639264 Adding them to the subject line -- Dims On Wed, Nov 30, 2016 at 10:28 AM, Mehdi Abaakouk wrote: > Hi, > > I think my subject is clear

[openstack-dev] [monasca][release] Release of openstack/monasca-grafana-datasource 1.0.0 failed

It looks like the monasca-grafana-datasource repository isn't set up in the way our release job expects for publishing nodejs projects. >From the log: 2016-11-15 14:03:26.945891 | + npm install 2016-11-15 14:03:27.287904 | npm ERR! install Couldn't read dependencies 2016-11-15 14:03:27.289483 |

Re: [openstack-dev] [monasca] License for monasca-statsd

On 2016-11-03 15:03:44 -0400 (-0400), Chuck Short wrote: > I was looking at packaging monasca-statsd since it is a dependency for > designate, however when I look at the license for it,it says Apache-2. > However the LICENSE file included in the source is that the software is > provided as

Re: [openstack-dev] [monasca] License for monasca-statsd

Excerpts from Chuck Short's message of 2016-11-03 15:03:44 -0400: > Hi, > > I was looking at packaging monasca-statsd since it is a dependency for > designate, however when I look at the license for it,it says Apache-2. > However the LICENSE file included in the source is that the software is >

Re: [openstack-dev] [monasca] License for monasca-statsd

On 2016-11-03 18:17:42 -0400 (-0400), Chuck Short wrote: > I have checked the version on pypi and tarballs.openstack.org and all the > versions from monasca-statsd from 1.0.0 onwards provide the incorrect > LICENSE file. Right, I'm saying I hope the files which have Apache license headers in them

Re: [openstack-dev] [monasca] License for monasca-statsd

On Thu, Nov 3, 2016 at 3:55 PM, Jeremy Stanley wrote: > On 2016-11-03 15:03:44 -0400 (-0400), Chuck Short wrote: > > I was looking at packaging monasca-statsd since it is a dependency for > > designate, however when I look at the license for it,it says Apache-2. > > However

Re: [openstack-dev] [monasca] License for monasca-statsd

On 2016-11-03 15:03:44 -0400 (-0400), Chuck Short wrote: > I was looking at packaging monasca-statsd since it is a dependency for > designate, however when I look at the license for it,it says Apache-2. > However the LICENSE file included in the source is that the software is > provided as

[openstack-dev] [monasca] License for monasca-statsd

Hi, I was looking at packaging monasca-statsd since it is a dependency for designate, however when I look at the license for it,it says Apache-2. However the LICENSE file included in the source is that the software is provided as is...etc etc. Could we get some clarification please? Thanks

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

>Monasca Mid Cycle Day 2 >July 20 2016 >7am to noon PDT > >Webex > > >Join WebEx meeting: >https://cisco.webex.com/ciscosales/j.php?MTID=m84f9f81d7c1c171be6365716522 >d >e15e > >Meeting number: 205 141 519 >Meeting password: 8VyzUiyr > >Join by phone >+1-408-525-6800 Call-in toll number

[openstack-dev] [monasca] Monasca Mid-Cycle Minutes

Notes for Monasca July Mid Cycle 2016 Minutes July 19 from 10:30am PDT to Dimensions Names/Values resources This blueprint needs to be updated. The PATCH part needs to be updated. The new URL is metrics/dimensions/names/values The use case is driven by Grafana and is part of the templating. In

[openstack-dev] [monasca] Announcing Monasca Analytics

Dear all, I have the pleasure to introduce you to Monasca analytics, a seamless extension of Monanas that enables sharing of infrastructure analytic recipes across the community. Some of you are probably already familiar with it after we, in a "well-orchestrated marketing campaign", pushed

[openstack-dev] [monasca] metering interval, global/local

Hi, as far as I can tell, Monasca does not support different metering intervals for different meters. There is the check_freq value in agent.yaml, which is global. Am I right about this? Did you consider the option of specifying check_freq for specific meters? BR, Laszlo

Re: [openstack-dev] [monasca] step-by-step installation guide

<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, June 22, 2016 at 4:58 AM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [monasca] step-by-step insta

[openstack-dev] [monasca] step-by-step installation guide

Hi, does there exist a step-by-step manual installation guide for Monasca? Something that is independent of DevStack. I have manually installed it recently for testing purposes and I could not find an up-to-date description. In case there is a need for it, I can prepare a guide to share on the

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

Hi Witek, Thanks for the blueprint. We can review tomorrow if you would like. Personally, I like the term "locked". The alarm definition makes more sense (option 2). I don't think an operator will want to lock/latch an alarm sub-expression. The operator will want to lock/latch an entire alarm.

  1   2   >