15:00:34 <rhochmuth> #startmeeting monasca
15:00:35 <openstack> Meeting started Wed Aug 17 15:00:34 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:37 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:39 <openstack> The meeting name has been set to 'monasca'
15:00:46 <rhochmuth> o/
15:00:47 <rbak> o/
15:00:50 <koji> o/
15:00:51 <kamil_> o/
15:00:57 <cbellucci> o/
15:01:14 <rhochmuth> hi everyone
15:01:28 <rhochmuth> i'm out today, supposedely on vacation
15:01:37 <kamil_> empty agenda today
15:01:39 <rhochmuth> i didn't see any agenda items posted
15:01:46 <rhochmuth> correct kamil_
15:02:08 <rhochmuth> does anyone have anything specific that they would like to discuss that isn't in the agenda
15:02:34 <rhochmuth> since there isn't anything in the agenda, i guess that is a semi-redundant statement
15:03:23 <rhochmuth> ok, i'm going to end the meeting today early
15:03:24 <ibmko> rhochmuth, if no agenda, I'd have one question which might actually better belong to a monasca mailing list but I would give it a shot here :)
15:03:40 <rhochmuth> ibmko: please proceed
15:05:01 <ibmko> I am now playing around with monasca alarms and it seems that monasca-thresh is able to dynamically create alarms from alarm definitions but is not able to delete them (like for example when new Nova Instance is created and then deleted)
15:05:16 <rhochmuth> correct
15:07:40 <rhochmuth> there have been some external cleanup scripts that have been written to address this
15:07:40 <rhochmuth> but it is not part of the monasca service right now
15:07:40 <ibmko> I guess I understand why - there is no way for monasca thresh to know, whether the situation is that agent is unable to send metrics or the monitored object has been removed
15:07:40 <rhochmuth> correct
15:07:40 <rhochmuth> we had an effort underway to add events to monasca
15:07:40 <rhochmuth> the events would receive the openstack notifications
15:07:40 <rhochmuth> such as VM lifecycle events
15:07:40 <ibmko> so the alarm ends up in undertermined, so would the correct approach be for Nova instances to implement this clean up in monasca agent - the libvirt plugin ?
15:07:40 <rhochmuth> but the events work isn't done/started
15:07:40 <rhochmuth> like i said, we've written scripts to do this
15:07:40 <rhochmuth> externally
15:07:46 <rhochmuth> we don't do it in the agent, as the agent's job is to send metrics
15:08:12 <rhochmuth> rbak: is your cleanup script in your puppet repo?
15:08:25 <ibmko> did you also manage to guarantee that you wipe the alarm before it actually changes to Undetermined state (and sends notification to Operators :) )
15:08:35 <rbak> I believe so
15:09:16 <ibmko> could you point me to your implementation of the clean up ?
15:10:08 <rbak> I'm looking now to see if we've made that public.  If not I'll see about getting that done.
15:10:19 <rhochmuth> thx rbak
15:10:24 <ibmko> thanks
15:10:37 <rhochmuth> our script isn't in monasca, it is part of our helion openstack distribution
15:11:01 <ibmko> rhochmuth, is it a standalone poller, or part of something bigger ?
15:11:23 <shinya_kwbt> o/
15:11:40 <rhochmuth> it is a script that runs as a cron job
15:11:47 <ibmko> ok, right
15:11:52 <rbak> It looks like I was wrong, this isn't in our puppet repo.  Ask again next week and I'll try to have it up by then to share.
15:12:05 <ibmko> rbak, will do, thanks
15:12:21 <rhochmuth> it polls the monasca api and nova api to determine the VMs that have been destroyed
15:12:55 <ibmko> rhochmuth, what about the guarantees I mentioned above ?
15:14:08 <rhochmuth> i don't think that is guaranteed
15:14:17 <rhochmuth> i'll have to check again
15:14:30 <rhochmuth> my memory isn't working this morning
15:15:10 <ibmko> :) thanks, It was already helpful a lot
15:15:54 <rhochmuth> your welcome ibmko_
15:16:16 <rhochmuth> so, are there any other topics
15:16:18 <kamil_> Does anybody know, if there is a result of the "voting for presentations" of the summit in Barcelona?
15:16:40 <rhochmuth> kamil_: i haven't heard anything
15:16:47 <slogan> I think the voting ends at the end of the month
15:16:53 <slogan> I *think*
15:17:01 <rhochmuth> voting was done last week
15:17:14 <slogan> Or the decisions are announced
15:17:33 <rhochmuth> so, i think the committees are putting the final agenda together
15:17:33 <kamil_> okay... thought i missed something. Thanks.
15:18:09 <rhochmuth> from past experience, i think it usually takes around two weeks after the voting has completed to post the acceptances
15:18:40 <rhochmuth> so, i would guess in about another week
15:19:08 <rhochmuth> but, i don't have any insight or dates
15:19:13 <rhochmuth> could be sooner or later
15:20:50 <rhochmuth> ok, i'm going to end the meeting today, unless there are more topics
15:21:11 <slogan> +1
15:21:39 <rhochmuth> ok, thanks everyone for attending
15:21:46 <slogan> have a great one
15:21:50 <kamil_> thank you
15:21:54 <rhochmuth> it is that time of year when vacations and time off is occurring
15:22:05 <rhochmuth> see you all next week
15:22:11 <kamil_> bye
15:22:23 <rhochmuth> #endmeeting