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