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

2017-08-28 Thread witold.be...@est.fujitsu.com
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

2017-08-28 Thread witold.be...@est.fujitsu.com
> -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > Sent: Montag, 28. August 2017 16:03 > To: Bedyk, Witold <witold.be...@est.fujitsu.com> > Cc: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org

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

2017-08-28 Thread witold.be...@est.fujitsu.com
> -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > Sent: Dienstag, 22. August 2017 15:50 > To: Bedyk, Witold <witold.be...@est.fujitsu.com> > Cc: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.o

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

2017-08-22 Thread witold.be...@est.fujitsu.com
Hi Akira, thank you for your contribution. We indeed urgently need a scalable open source TSDB. Do you use this database in your Monasca deployment? Have you made write/read performance measurements when used with Monasca? I couldn't find much information about this database apart from the

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

2017-08-10 Thread witold.be...@est.fujitsu.com
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

Re: [openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solu

2017-08-10 Thread witold.be...@est.fujitsu.com
Hi Tony, stable/pike branches for Monasca repos are on the way https://review.openstack.org/492101 Cheers Witek > -Original Message- > From: Tony Breeds [mailto:t...@bakeyournoodle.com] > Sent: Donnerstag, 10. August 2017 07:47 > To: OpenStack Development Mailing List

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

2017-08-09 Thread witold.be...@est.fujitsu.com
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] [ffe][requirements][monasca][heat][watcher][congress] FFE for python-monascaclient minimum version in g-r

2017-08-04 Thread witold.be...@est.fujitsu.com
requirements][monasca][heat][watcher][congress] FFE for python- > monascaclient minimum version in g-r > > On Thu, Aug 03, 2017 at 11:39:47AM +, witold.be...@est.fujitsu.com > wrote: > > Hello everyone, > > > > I would like to ask for the FFE for python-monascaclient vers

Re: [openstack-dev] [ffe][requirements][monasca][heat][watcher][congress] FFE for python-monascaclient minimum version in g-r

2017-08-03 Thread witold.be...@est.fujitsu.com
> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Donnerstag, 3. August 2017 15:45 > To: openstack-dev > Subject: Re: [openstack-dev] > [ffe][requirements][monasca][heat][watcher][congress] FFE for python- > monascaclient

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

2017-08-03 Thread witold.be...@est.fujitsu.com
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] [ffe][requirements][monasca][heat][watcher][congress] FFE for python-monascaclient minimum version in g-r

2017-08-03 Thread witold.be...@est.fujitsu.com
Hello everyone, I would like to ask for the FFE for python-monascaclient version in global requirements. The current version in Pike (1.7.0) is not fully backward compatible. The monasca exception classes were replaced with keystoneauth exceptions, which affects heat and watcher projects if

Re: [openstack-dev] [release][monasca][designate][requirements] late library release for monasca-statsd

2017-07-25 Thread witold.be...@est.fujitsu.com
> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Dienstag, 25. Juli 2017 13:49 > To: openstack-dev > Subject: Re: [openstack-dev] [release][monasca][designate][requirements] > late library release for monasca-statsd > >

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

2017-07-03 Thread witold.be...@est.fujitsu.com
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

2017-06-21 Thread witold.be...@est.fujitsu.com
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

2017-05-31 Thread witold.be...@est.fujitsu.com
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

Re: [openstack-dev] [release][monasca] Release of openstack/monasca-kibana-plugin failed

2017-04-21 Thread witold.be...@est.fujitsu.com
Hi, I'm sorry, I missed that. I've created the updates: https://review.openstack.org/458773 https://review.openstack.org/458776 Cheers Witek > -Original Message- > From: Hochmuth, Roland M [mailto:roland.hochm...@hpe.com] > Sent: Freitag, 21. April 2017 06:19 > To: OpenStack

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

2017-04-21 Thread witold.be...@est.fujitsu.com
> >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] cassandra support in Monasca

2017-03-01 Thread witold.be...@est.fujitsu.com
Hi Pradeep, HPE has investigated the use of Cassandra for Monasca and came to the conclusion that it is not a good choice. One of the problems is that Cassandra is not performant when querying across big data sets with many dimension key-value combinations. As KairosDB is based on Cassandra it

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

2017-02-13 Thread witold.be...@est.fujitsu.com
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] Team meeting on 28 Dec

2016-12-19 Thread witold.be...@est.fujitsu.com
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:

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