15:00:17 <egonzalez> #startmeeting kolla
15:00:18 <openstack> Meeting started Wed Oct 17 15:00:17 2018 UTC and is due to finish in 60 minutes.  The chair is egonzalez. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:21 <openstack> The meeting name has been set to 'kolla'
15:00:28 <egonzalez> #topic rollcall
15:00:43 <sadasu> hello
15:00:43 <donghm> o/
15:01:23 <chason> o/
15:02:29 <egonzalez> #topic agenda
15:02:33 <egonzalez> * Announcements * open discussion
15:03:07 <egonzalez> #topic announcements
15:03:31 <egonzalez> All patches pending for rocky release are already merged
15:03:46 <egonzalez> Will propose final rocky release soon
15:04:14 <egonzalez> Any other announcement?
15:06:03 <egonzalez> #topic open discussion
15:06:17 <egonzalez> There is no updated items in the agenda for today
15:06:23 <dougsz> I have a short one
15:06:30 <egonzalez> Anyone have something to  discuss?
15:06:44 <dougsz> So Monasca forked Grafana a long time ago
15:06:49 <egonzalez> dougsz: your turn
15:07:25 <dougsz> In the interest of trying to make it as easy to use Monasca as possible, I thought I could add a Monasca-Grafana docker image
15:07:56 <dougsz> The alternative is that you can customise the Grafana container with overrides
15:08:57 <dougsz> Any thoughts?
15:09:08 <egonzalez> Is the forked code in the openstack projects list?
15:09:18 <dougsz> No - it's in the Monasca OpenStack repo
15:10:04 <dougsz> It is also quite old, and may have some security issues
15:10:21 <egonzalez> Something was modified from the original grafana? Guess yes
15:10:24 <dougsz> But if it was available, it would make it easier to use Monasca out of the box
15:10:30 <dougsz> Yes - they added Keystone integration to it
15:11:52 <egonzalez> As the code is not the same I would treat it as different project aka monasca-grafana image
15:12:12 <egonzalez> Problem could be if grafana is enabled along with monasca
15:12:38 <dougsz> Yeah - OEM Grafana will still work, but Keystone integration is not as good.
15:13:04 <dougsz> I can make it so they can both be deployed and don't conflict with each other
15:13:21 <dougsz> Just use a different port in HAProxy I suppose
15:14:38 <egonzalez> Yep, but users probably don't want to have duplicated grafana servers running
15:15:38 <dougsz> No - I could add some logic to disable grafana when monasca_grafana is enabled
15:16:12 <dougsz> There is also risk of DB conflict as they use it for session information
15:16:27 <dougsz> Will need to make sure the fork uses a different DB
15:18:30 <egonzalez> Sure, don't recall if prometheus or other service use grafana
15:18:47 <dougsz> Yeah - it can use it.
15:18:49 <egonzalez> Just to make sure things are backward compatible
15:19:13 <dougsz> Ok sounds good.
15:19:22 <dougsz> I hope this is the last thing that needs to be done for Monasca :)
15:20:07 <egonzalez> Cool, if no new feature is required we can mark as implemented, next patches can go as bug fixes or different blueprint
15:20:51 <dougsz> Ok, I'm happy with that. I think everything is in review for the basic deployment.
15:21:16 <dougsz> I can make a new blueprint for the Monasca-Grafana service.
15:21:49 <egonzalez> Nice, dougsz thanks for raising this topic, can we move on?
15:21:54 <chason> Good job, dougsz!
15:22:07 <dougsz> Sure, thanks for all the reviews!
15:22:37 <egonzalez> Any other topic for today?
15:22:57 <chason> I have one
15:23:41 <chason> Should we change the keystone_admin_port from 35357 to 5000?
15:26:14 <egonzalez> Hrm, any reason? Was 35357 port removed?
15:27:10 <donghm> may I ask nonsense question, currently which keystone version we are using? v2 or v3
15:27:44 <egonzalez> V3 only, v2 is not longer supported
15:30:57 <donghm> did not find the deprecated info in keystone notes, but I found this https://bugs.launchpad.net/charm-keystone/+bug/1747972
15:30:57 <openstack> Launchpad bug 1747972 in OpenStack keystone charm "Drop use of port 35357 in Queens" [Medium,Triaged]
15:32:30 <egonzalez> Problem with it is deal with backwards compatible
15:33:19 <egonzalez> Users may have scripts using the admin port, some project does not handle properly the port, etc
15:34:32 <egonzalez> But makes sense to keep updated with keystone upstream, even they now does not uses port anymore
15:35:38 <donghm> yeah :)
15:37:01 <donghm> egonzalez: I just have a short one, that is I have just replied the comments on this patch https://review.openstack.org/#/c/555199/
15:37:26 <donghm> can you take a look again, ^^
15:37:42 <egonzalez> Main issue I see now is while upgrading services will be using port 35357 but keystone isn't listening there anymore
15:37:45 <egonzalez> https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/keystone/templates/wsgi-keystone.conf.j2
15:39:55 <egonzalez> donghm sure
15:40:25 <egonzalez> Anything else?
15:41:08 <donghm> no from me, but I'm thinking about the issue you said above when upgrading
15:44:46 <chason> Yeah, that is what we need concern about.
15:44:59 <egonzalez> Let's end the meeting, move to #openstack-kolla for further discussion
15:44:59 <egonzalez> Thank you all for comming
15:44:59 <egonzalez> Have a nice day
15:45:28 <donghm> thanks egonzalez
15:45:30 <chason> Thanks egonzalez
15:45:48 <egonzalez> #endmeeting