15:01:07 <witek> #startmeeting monasca
15:01:12 <openstack> Meeting started Wed Mar 28 15:01:07 2018 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:16 <openstack> The meeting name has been set to 'monasca'
15:01:19 <sc> howdy
15:01:23 <amofakhar> hi
15:01:26 <witek> hello
15:01:55 <witek> I see there was some confusion about DST
15:02:07 <sc> date -u helps
15:02:23 <witek> linux freak :)
15:02:44 <tobiajo> hi
15:03:08 <witek> #topic documentation
15:03:35 <witek> who has brought this up?
15:03:39 <sc> this is me
15:03:59 <witek> what do you mean with githbub.com?
15:04:13 <sc> I was about to write documentation for the agent
15:04:43 <sc> I was unable to find user manuals for monasca on doc.o.o
15:05:32 <sc> if this is my fault please point me in the right direction
15:05:42 <witek> for monasca-agent we have quite extensive documentation in https://github.com/openstack/monasca-agent/tree/master/docs
15:05:49 <sc> most of the documetation are .md file that renders on github
15:05:57 <witek> and in README
15:06:13 <sc> yes but why on github and not on docs.o.o?
15:06:24 <sc> this was my main question
15:07:08 <witek> if we want to publish it to d.o.o. we should refactor the documents to rst format
15:07:52 <sc> is this worth?
15:08:22 <witek> I would prefer to add basic installation documentation in d.o.o and refer to .md documents which we have in monasca-agent repo
15:08:59 <witek> d.o.o would be acting as the central place with references to all documentation we have
15:09:25 <witek> and the current state is here: https://docs.openstack.org/monasca-api/latest/
15:09:40 <sc> OK, so I'm going to do in 2 phases: update the .md for the agent, write new documentation, is this approach OK?
15:09:48 <witek> I should actually rename it to https://docs.openstack.org/monasca/
15:10:16 <witek> yes, that's exactly what I had in mind
15:10:29 <sc> OK, so this is agreed
15:10:38 <witek> thank Stefano
15:11:04 <witek> btw. left you a comment in review
15:11:04 <sc> IMVHO, we can go to next point
15:11:42 <witek> #topic Vancouver Forum
15:12:10 <witek> last week I have mentioned about the brainstorming for the Forum
15:12:34 <witek> now the submission tool is available to propose the session topics
15:12:41 <witek> http://forumtopics.openstack.org/
15:13:11 <witek> deadline for submissions is Apr 15
15:13:40 <witek> any questions to this?
15:13:49 <jgrassler> Hmm, that sounds pretty formal
15:14:04 <jgrassler> But then again...it's a big event
15:14:30 <sc> Fine, I applied for travelling and I'm still available to take part to the forum
15:15:47 <witek> yes, it's big, they have to select the topics if they have too many proposals
15:16:55 <witek> #topic max line length
15:17:28 <amofakhar> currently there is not any limitation for the length of lines in most of the projects
15:17:44 <amofakhar> should we add it in pep8 check?
15:17:45 <sc> 80 or 100 are OK, 120 is for Javaguyswithlonglongvariablenames
15:18:15 <amofakhar> i think only monasca-api has a check for it
15:18:21 <amofakhar> and it is set on 120
15:18:52 <witek> I prefer to have short lines
15:19:00 <witek> 80 is good, 100 works as well
15:19:09 <amofakhar> I prefer 100
15:19:19 <sc> amofakhar: I remember a discussion many times ago and HP/guys disagreed to put a limit
15:19:31 <witek> should we vote?
15:19:42 <amofakhar> what was their reason?
15:19:44 <sc> I'm perfectly OK with 80 and the small patch I did for agent is at 80
15:20:13 <amofakhar> Agree with voting
15:20:34 <sc> the reason was that it's difficult to stay at 80 for java and so they did not care in python
15:21:55 <amofakhar> but most of the codes are in python and it's good we obey pep8
15:22:26 <sc> I aggree with you amofakhar
15:22:33 <witek> we could also ignore Java code in checks
15:22:49 <amofakhar> yes we can ignore java
15:23:24 <amofakhar> are you agree I add 100 char limit for all projects?
15:23:47 <witek> any objections?
15:23:55 <sc> no
15:24:11 <sc> Usually I use 80 but it's fine to get a limit to 100
15:24:24 <amofakhar> I myself use 80
15:24:52 <sc> 80 < 100 so we are in the limit ;-)
15:25:03 <witek> no objection from me either
15:25:15 <amofakhar> so 80 or 100?
15:25:39 <sc> other opinions?
15:26:40 <witek> #startvote What should be max. line length for pep8 checks? 80, 100
15:26:41 <openstack> Begin voting on: What should be max. line length for pep8 checks? Valid vote options are 80, 100.
15:26:42 <openstack> Vote using '#vote OPTION'. Only your last vote counts.
15:26:47 <joadavis> I prefer 120, but maybe I wrote too much Java. ;)
15:27:04 <jgrassler> #vote 100
15:27:08 <amofakhar> #vote 100
15:27:14 <sc> #vote 100
15:27:27 <witek> #vote 80
15:27:28 <joadavis> #vote 120
15:27:28 <openstack> joadavis: 120 is not a valid option. Valid options are 80, 100.
15:27:41 <joadavis> aww
15:27:43 <amofakhar> :)
15:28:11 <amofakhar> 120 is not acceptable by pep8
15:28:24 <witek> #endvote
15:28:25 <joadavis> (I was actually hacking some ansible scripts down to 80 yesterday, so I can deal with whatever the decision is)
15:28:25 <openstack> Voted on "What should be max. line length for pep8 checks?" Results are
15:28:26 <openstack> 100 (3): sc, jgrassler, amofakhar
15:28:27 <openstack> 80 (1): witek
15:28:49 <amofakhar> good
15:29:30 <witek> #action amofakhar configures pep8 checks for max. line length of 100 chars
15:29:39 <amofakhar> yes
15:29:43 <witek> thank you
15:29:59 <amofakhar> you'r welcome
15:30:14 <witek> #topic progress board
15:30:20 <witek> https://storyboard.openstack.org/#!/board/60
15:30:50 <witek> we have merged 'DB migration spec'
15:30:57 <witek> thanks Johannes
15:31:14 <jgrassler> Oh nice, thanks :-)
15:31:28 <witek> we also got help from Chuck Short
15:31:38 <witek> on removing mox
15:31:47 <witek> and adding support for Python 3 in monasca-ui
15:32:39 <witek> the mox community goal for Rocky is completed! :)
15:32:47 <sc> witek: I saw now your comment on PS3 in https://review.openstack.org/#/c/554304/ I missed it. Thanks.
15:32:56 <joadavis> <clapping>
15:33:47 <witek> we're done with agenda, do we have other topics?
15:34:35 <aagate> I had a question on region
15:34:54 <aagate> The doc here says that region is on the way to removal https://wiki.openstack.org/wiki/Monasca/Message_Schema#Metrics_Message, is that still true ?
15:35:37 <aagate> Also we restrict what region we can query based on 'region' property in config file https://github.com/openstack/monasca-api/blame/master/java/src/test/resources/monasca-api-config.yml
15:36:39 <aagate> Basically if we know a specific use case monasca supports/should support like if monasca can collect and store data from multiple regions
15:37:32 <witek> the option from `monasca-api-config.yml` is for persisting metrics
15:38:05 <witek> meaning one instance will always collect measurements from one region
15:39:16 <witek> but I cannot answer your question, if we need to support it
15:39:39 <aagate> From what i saw metrics were being persisted with region 'useast' and 'region1' but only one could be queried
15:41:08 <aagate> and the region is determined from region in meta section so region in meta section is still valuable (i mean not to be removed soon right ?)
15:41:47 <witek> I don't recall any plans like this, to be honest
15:42:12 <aagate> k thanks witek, thats helpful!
15:42:28 <witek> so you wouldn't like to remove it, right?
15:43:28 <aagate> :-) yes prefer not to remove it. But may be in future we can think of use case if we want single monasca instance to collect data from multiple regions
15:43:54 <witek> thanks, I will also think of use cases
15:44:41 <witek> is the meeting time good for everyone after the timezone shift?
15:45:36 <witek> anything else for today?
15:46:07 <witek> next week I will be in vacation
15:46:19 <witek> so I would like to ask someone to start and moderate the meeting
15:46:33 <joadavis> Meeting time is ok.  I guess I was just thrown off that it didn't shift with timezones
15:46:48 <joadavis> Have a nice vacation
15:46:54 <witek> thank you :)
15:47:41 <witek> OK, I'm wrapping up then
15:47:48 <witek> thank you everyone
15:47:54 <amofakhar> thank you
15:47:57 <witek> and see you in two weeks
15:47:59 <amofakhar> have a nice vacation
15:48:02 <joadavis> thanks. bye
15:48:03 <aagate> thank you!
15:48:08 <amofakhar> bye
15:48:13 <jgrassler> See you!
15:48:19 <witek> #endmeeting