14:01:03 <rhochmuth> #startmeeting monasca
14:01:04 <openstack> Meeting started Wed May 31 14:01:03 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:07 <openstack> The meeting name has been set to 'monasca'
14:01:13 <rhochmuth> anyone here
14:01:20 <kamil_> yes
14:01:32 <rhochmuth> hi kamil_
14:01:37 <rhochmuth> o/
14:01:40 <witek> hello
14:01:41 <arturb> o/
14:01:46 <rhochmuth> i'm wondering if folks are going to make the new time
14:01:47 <kamil_> o/
14:02:18 <rhochmuth> https://etherpad.openstack.org/p/monasca-team-meeting-agenda
14:02:32 <witek> should we wait a couple of minutes?
14:02:35 <rhochmuth> Agenda for Wednesday May 31 2017 (14:00 UTC)
14:02:35 <rhochmuth> 1.	Pike-2 milestone: June 8
14:02:35 <rhochmuth> 2.	Use RST for documentation
14:02:35 <rhochmuth> ◦	publish to docs.openstack.org and developer.openstack.org
14:02:35 <rhochmuth> ◦	https://docs.openstack.org/project-team-guide/documentation.html
14:02:36 <rhochmuth> ◦	https://review.openstack.org/#/c/437889/
14:02:36 <rhochmuth> 3. Review/Opinion needed
14:02:37 <rhochmuth> 3.1 https://review.openstack.org/#/c/466203/
14:02:48 <rhochmuth> i guess
14:02:55 <rhochmuth> we might have to wait an hour
14:03:00 <witek> :)
14:03:44 <rhochmuth> i'm guessing we should just get started
14:03:52 <arturb> ok
14:04:24 <rhochmuth> before i get started, i've had some requests about the upcoming PTG in Denver
14:04:45 <rhochmuth> there are requests for space
14:05:05 <rhochmuth> my assumption is that we wouldn't have a critical mass at the PTG
14:05:30 <rhochmuth> was wondering what others thought
14:05:41 <rhochmuth> it is basically an hour drive for me
14:05:50 <rhochmuth> so a travel request isn't necessary
14:06:08 <witek> so, the requests are from OpenStack Foundation?
14:06:17 <rhochmuth> correct
14:07:06 <witek> and with not having critical mass, you mean only few attendees, right?
14:07:23 <rhochmuth> correct
14:08:01 <witek> I will ask managers, till when should you know?
14:08:13 <rhochmuth> very soon
14:08:16 <rhochmuth> like right now
14:08:20 <witek> :)
14:08:23 <rhochmuth> as they are starting to designate space
14:08:44 <rhochmuth> the other possblity is to attend and meet with other projects in their space
14:08:52 <rhochmuth> but that would have to be coordinated ahead of time
14:09:26 <rhochmuth> for example, if you were interested in working with another team on monasca integration
14:10:34 <rhochmuth> so, let's move on
14:10:43 <rhochmuth> #topic Pike-2 milestone: June 8
14:11:01 <witek> it would be important to know, who else could attend
14:11:22 <rhochmuth> witek: i agree
14:11:39 <rhochmuth> there is no reason in attending if others won't be there
14:11:40 <witek> I suggest to create a doodle
14:11:58 <witek> and let people answer till like end of the week
14:12:14 <witek> would that work?
14:12:19 <rhochmuth> sure
14:12:38 <rhochmuth> since not many are at todays meeting it would have to be posted to openstack-dev
14:12:45 <witek> I'll create one and send info to mailing list
14:12:52 <rhochmuth> thx
14:13:02 <witek> then you can decide what we do
14:13:23 <rhochmuth> ok
14:13:50 <rhochmuth> #topic Pike-2 milestone: June 8
14:14:17 <witek> I can create tags this week, if everyone is OK with it
14:14:22 <rhochmuth> so, besides tagging is there anything else for the upcoming milestone?
14:14:26 <rhochmuth> i'm ok
14:14:30 <witek> next two weeks i'm in vacation
14:14:45 <rhochmuth> ohhh, better get tags done this week then
14:15:11 <witek> i'm not aware of anything else what has to be done
14:15:34 <rhochmuth> ok, then i guess we are good
14:15:52 <witek> ok, thanks
14:15:59 <rhochmuth> #topic Use RST for documentation
14:16:49 <witek> we have discussed internally, that it would be good to have all Monasca documentation in central OpenStack place
14:17:15 <witek> meaning docs.openstack.org and developer.openstack.org
14:17:40 <witek> there is quite some infrastructure to support publishing current documentation
14:17:56 <witek> and it is referenced together with other OpenStack projects
14:18:33 <witek> we could start with the content, that we have already
14:18:54 <witek> there is lots of useful documentation there
14:19:25 <witek> what we would have to do is reformat it to RST and configure gate jobs
14:19:56 <rhochmuth> sounds good to me
14:20:08 <rhochmuth> i'm not sure how this all works
14:20:21 <rhochmuth> but the monasca-log-api has all the rst docs at
14:20:35 <rhochmuth> https://github.com/openstack/monasca-log-api/tree/master/doc/source
14:20:44 <witek> they are not published though
14:21:01 <rhochmuth> do the rst docs just reference the md docs
14:21:27 <witek> no, md docs would have to be reformatted
14:22:03 <witek> I think we could start with log-api and then follow-up with monasca-api
14:24:54 <witek> that's it, we'll start working on it
14:25:04 <rhochmuth> ok, thanks
14:25:38 <rhochmuth> #topic https://review.openstack.org/#/c/466203/
14:25:55 <arturb> so it is me
14:26:01 <rhochmuth> hi arturb
14:26:09 <arturb> hi ::)
14:26:26 <arturb> the problem was spotted by Jakub and he prepared the change
14:26:44 <arturb> he changed the offset to integer value according to the influxdb documentation
14:27:25 <arturb> where newest influxdb as he checked expects offset as an integer value
14:27:33 <arturb> I only fixed the tempest test
14:28:23 <arturb> and also the question from me is: the java version of the api is deprecated and I only run modified test for python version
14:28:26 <rhochmuth> so, doesn't the pagination for alarm history currently work simialr to metrics, based on a timestamp
14:28:47 <rhochmuth> the java api is not deprecated
14:29:00 <arturb> we tried to test it with timestamp and api throws an error
14:29:07 <arturb> ok
14:29:11 <rhochmuth> interesting
14:29:27 <rhochmuth> we would like to deprecate the java api, but we havent' done that yet
14:29:37 <arturb> so maybe somebody else could look at this
14:29:48 <rhochmuth> sure, i'll need to dig in
14:30:01 <witek> wasnt't it that monasca-ui set offset=0 for the first page and that throws exception?
14:30:06 <rhochmuth> did influxdb change the behaviour and we just didn't catch it
14:30:23 <rhochmuth> i thought we had good coverage on the pagination tests
14:30:30 <arturb> as I said the change was started by Jakub but currently he is on vacations thats why I modified tempests
14:31:13 <rhochmuth> well, we can't jsut change what the api has specified
14:31:20 <rhochmuth> and should work
14:32:02 <rhochmuth> i'll check with a couple of folks here to see can be done with influxdb
14:32:13 <arturb> ok thanks
14:32:15 <witek> rhochmuth: thanks
14:32:53 <rhochmuth> since this is supposedely working with metrics, it should work with alarm state history the same way,
14:33:44 <rhochmuth> i guess that is it for today
14:33:50 <rhochmuth> unless there are other topics in closing
14:34:06 <rhochmuth> i'll check with folks at the old place and time in half an hour
14:34:28 <witek> I should still be there as well
14:34:55 <rhochmuth> ok, thanks everyone
14:34:59 <rhochmuth> see you next week
14:35:04 <kamil_> bye
14:35:12 <witek> thanks
14:35:13 <arturb> thanks
14:35:20 <rhochmuth> #endmeeting