23:00:01 <sdake> #startmeeting kolla
23:00:02 <openstack> Meeting started Wed Mar 16 23:00:01 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.
23:00:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
23:00:06 <openstack> The meeting name has been set to 'kolla'
23:00:08 <sdake> #topic rollcall
23:00:10 <SamYaple> o/
23:00:13 <asalkeld> o/
23:00:14 <sdake> \o/ jumps for joy
23:00:15 <pbourke-pub> o/
23:00:18 <SamYaple> pbourke-pub: lol
23:00:23 <mandre> o/
23:00:23 <pbourke-pub> Aw yis
23:00:28 <vhosakot> o/
23:01:07 <rhallisey> hello
23:01:11 <ntpttr> hi o/
23:01:17 <Jeffrey4l> 0/
23:02:10 <sdake> #topic announcements
23:02:23 <akwasnie> o/
23:02:33 <SamYaple> too late akwasnie no rollcall for you
23:02:34 <sdake> rc1 is tagging tomorrow morning
23:02:58 <sdake> i'd like to get the bug tracker into decent shape today during our meeting as a result
23:03:02 <sdake> specifically the blueprints section
23:03:20 <sdake> thats my end of announcements
23:03:28 <sdake> anyone have anything from the community?
23:03:32 <SamYaple> there is one needed patchset for rc1
23:03:37 <SamYaple> the lights out mariadb
23:03:43 <SamYaple> thats part of the upgrade stuff
23:03:45 <dave-mccowan> o/
23:03:57 <SamYaple> #link https://review.openstack.org/#/c/293161/
23:04:03 <inc0> o/
23:04:22 <sdake> inc0 would you midn reviewing that plz
23:04:29 <sdake> or some other core would do as well :)
23:04:39 <inc0> I just joined, link plz
23:04:41 <inc0> and sorry
23:04:45 <SamYaple> https://review.openstack.org/#/c/293161/
23:04:54 <inc0> thanks
23:04:59 <sdake> #topic liberty backport status
23:05:52 <sdake> I'd like to ask all core reviewers to spend 1 hour reviewing sam's 3 patches for liberty backports
23:05:59 <sdake> i'd like the entire team to review them
23:06:04 <sdake> to provide sam with appropriate feedback
23:06:14 <asalkeld> links?
23:06:17 <sdake> the status is the backports can't really be done by more then one person
23:06:22 <SamYaple> it shouldnt take near 1 hour
23:06:24 <sdake> but the reviews can be done by our entire team
23:06:36 <SamYaple> https://review.openstack.org/#/c/278621/
23:06:39 <sdake> SamYaple yes i know, I was asking for the most time it could possibley take ;)
23:06:44 <sdake> there are 3 patches in that stream
23:06:47 <SamYaple> https://review.openstack.org/#/c/285731/
23:06:48 <SamYaple> https://review.openstack.org/#/c/285733
23:06:58 <sdake> we are approving patches even if they are not green in the gate
23:07:02 <sdake> the goal is the last patch in the stream will make the gate green
23:07:04 <akwasnie> ok, will do
23:07:08 <sdake> our deadline for this work is april 1st
23:07:16 <SamYaple> i have blocked off the first patch so feel free to +2+W
23:07:19 <sdake> please keep that stream on your active review every day watchlist
23:07:45 <sdake> our stable branch is charlie foxtrott echo delta atm
23:07:58 <sdake> lets make it work well
23:07:59 <sdake> any questions?
23:08:00 <inc0> cfed?
23:08:29 <sdake> inc0 if you can't figure it out, i'm not going to swear in public :)
23:08:37 <inc0> I have my theories
23:08:53 <sdake> any other questions?
23:09:16 <sdake> this and releasing mitaka are our highest priorities atm :)
23:09:21 <sdake> lets focus on them
23:09:28 <sdake> on to the next part then
23:09:39 <sdake> #topic Mitaka rc1 blueprint review to close out the release [timebox 10 minutes]
23:10:02 <sdake> #link https://launchpad.net/kolla/+milestone/mitaka-rc1
23:10:31 <sdake> SamYaple mariadb upgrade is in needs review, or did that merge?
23:10:39 <sdake> SamYaple mariadb is in needs review?
23:11:15 <sdake> inc0 playbook for rabbitmq
23:11:22 <sdake> upgrade playbook that is
23:11:26 <SamYaple> mariadb upgrade is done, mostly just need https://review.openstack.org/#/c/293161/
23:11:32 <inc0> we need deploy with hostnames
23:11:43 <inc0> will work on this tomorrow
23:11:53 <sdake> inc0 ok i'll push that to rc2 then
23:11:53 <inc0> after that its few lines of change
23:11:58 <inc0> ok
23:12:03 <vhosakot> I see both reconfig and upgrade not implemented for elasticsearch service. Can I go ahead and open a bug and implement them ?
23:12:27 <sdake> vhosakot feel free
23:12:30 <inc0> vhosakot, it's lower priority but if you can pull that off
23:12:34 <inc0> would be nice
23:12:45 <sdake> dave-mccowan fernet tokens?
23:12:50 <vhosakot> cool
23:12:58 <sdake> good progress, started, needs code review?
23:13:29 <dave-mccowan> good progress.  do we want them for mitaka?  i can finish the patch i started, leaving rotation as an operator task.
23:13:44 <sdake> dave-mccowan yes wnated for mitaka - its in the rc tracker linked above
23:13:57 <SamYaple> sdake: no its not wanted for mitaka
23:14:02 <SamYaple> its a big feature which does alot of things
23:14:18 <SamYaple> thigns we dont do esleshere yet...
23:14:22 <inc0> I kinda agree with Sam, we're in rc's now
23:14:34 <inc0> but let's have patch in queue
23:14:38 <SamYaple> exactly
23:14:43 <inc0> worst case scenerio we'll have it early newton
23:14:48 <inc0> which isn't bad as well
23:14:48 <SamYaple> the WIP went into queue AFTER_rc_
23:15:09 <sdake> the feature was in the tracker prior to rc
23:15:16 <SamYaple> it was in prior to liberty
23:15:18 <sdake> nobody complaned then
23:15:21 <SamYaple> i did
23:15:58 <sdake> vote it is
23:16:01 <sdake> i'll send a mail to the mailing list on the topic
23:16:12 <SamYaple> im -2 here. do you know whats involved in this?
23:16:16 <SamYaple> the patch isnt even ready
23:16:25 <sdake> dave-mccowan coudl you add more context please?
23:16:26 <SamYaple> it requires new .py files in containers
23:17:16 <sdake> dave-mccowan is the patch disruptive?
23:17:35 <sdake> the problem here is the feature is a high priority item
23:17:46 <SamYaple> it was high priority in liberty as well
23:18:02 <sdake> it wasn't submitted in liberty until the rcs started
23:18:06 <inc0> can we see what's involved and possibly add backport potential?
23:18:08 <SamYaple> the fact is the work isnt done and it wasnt started until we were in the RCs
23:18:21 <inc0> I hate to put that much of a time pressure on both Dave and reviewers
23:18:48 <SamYaple> sdake: i said before he started this is too mcuh for an RC
23:18:50 <dave-mccowan> i have WIP posted, but it needs more work.  it would be optional and non-disruptive, but unlikely to be 100% correct by rc1.  it would be nice as a backport, if that was possible.
23:18:58 <sdake> well i'd be willing to compromise with inc0's proposl
23:19:09 <sdake> proposal
23:19:14 <SamYaple> so you want an exception sdake?
23:19:22 <inc0> let's have it implemented and consider backport then
23:19:23 <sdake> no, a vote on the mailing lsit about yet another backport
23:19:25 <dave-mccowan> could we commit the config parameters, and then implementation goes in as backport (if operators request it)
23:19:29 <sdake> because we have let the genie out of that bottle
23:19:36 <SamYaple> not for mitaka
23:19:46 <SamYaple> this is your doing now. this isnt how you build a stable branch
23:20:00 <inc0> guys, please, let's just carry on
23:20:02 <SamYaple> yea
23:20:04 <SamYaple> ML
23:20:13 <sdake> pbourke-pub oracle linux gates
23:20:15 <inc0> when Dave finishes implementation we'll consider it
23:20:21 <inc0> now it's hollow discussion
23:20:52 <sdake> pbourke-pub i'm going to punt the mediums to newton
23:21:00 <sdake> so if your finished by tomorrow morning, wfm ;)
23:21:09 <sdake> otherwise please feel free to move the blueprint to newton
23:21:31 <sdake> pbourke my apologies its a high priority
23:21:43 <sdake> well we will carry that over to rc2 looks like
23:21:48 <sdake> the mediums are getting punted
23:22:02 <sdake> any Q&A?
23:22:23 <sdake> #topic Mitaka rc1 release announcement [timebox 15 minutes]
23:22:58 <sdake> #link https://etherpad.openstack.org/p/announce-kolla-mitaka-rc1
23:23:22 <sdake> 40 after we have to craft our rc1 release announcement
23:23:51 <sdake> please clicky the linky
23:26:44 <asalkeld> sdake: is this for all of mitaka or just since m3?
23:26:58 <sdake> just since m3
23:27:01 <asalkeld> ok
23:27:02 <sdake> any notable features people want to mention?
23:27:17 <sdake> that were bugs
23:27:31 <vhosakot> few droproot bugs were fixed
23:29:19 <sbezverk> sdake what about ipc host support ;-) ?
23:29:48 <sdake> sbezverk anyone is free to edit this etherpad
23:29:58 <sdake> please feel free to add your items
23:30:08 <vhosakot> some nice bugs were fixed about OVS and manila as well
23:30:12 <sdake> so just sdake and asalkeld aren't writing  the release notes
23:30:16 <sdake> vhosakot pelase add them :)
23:33:13 <vhosakot> SamYaple: isn't "Use nopreempt for keepalived" worth mentioning ?
23:34:11 <SamYaple> vhosakot: it would have been in reno stuff, so i suppose it could go here
23:34:21 <SamYaple> though reno isnt dont every rc
23:34:28 <vhosakot> cool
23:34:32 <SamYaple> i dont realyl know why we are making this announcement
23:35:46 <sdake> SamYaple we always make release announcements
23:36:01 <SamYaple> i know
23:36:22 <sdake> once we have reno we won't do this anymore
23:36:36 <SamYaple> reno doesnt do this
23:36:36 <sdake> enjoy it while  it lasts :)
23:36:44 <SamYaple> everyone typically just says rc1 is availbable
23:37:33 <vhosakot> well, I have seen features and bug-fixes mentioned in RC's..
23:38:49 <sdake> t-2 minutes for additions
23:39:25 <SamYaple> vhosakot: sure, a feature/bug maybe. but really most just announce rc1 availablilty
23:40:26 <sdake> #topic Kibana dashboard integration
23:40:41 <sdake> rajathagasthya all yours
23:40:43 <sdake> and akwasnie
23:40:45 <sdake> and elemoine
23:40:58 <sdake> 12 minutes max plz :)
23:41:23 <inc0> not very good time for both of them;)
23:41:32 <inc0> I think its 1am in Poland now
23:41:43 <sdake> inc0 she said hello earlier
23:41:50 <akwasnie> so we could base on fuel plugin idea
23:42:14 <akwasnie> but they use curl to put kibana dasboard json into elasticsearch
23:42:27 <rajathagasthya> Thanks sdake. I'd like to know how to get started with integrating the custom Kibana dashboard to v4. I've done that with v3, but in a different way than what Fuel plugin does.
23:42:44 <akwasnie> inc0: yes it is almost 1 am:)
23:42:45 <sdake> so curl - are there problems with this approach akwasnie ?
23:42:48 <SamYaple> rajathagasthya: wow wounds great
23:43:01 <SamYaple> rajathagasthya: so logs would be viewable by admin in horizon?
23:43:17 <sdake> no but there would be a proper dashboard in kibana
23:43:20 <vhosakot> akwasnie: will this patch set I'm working on affect Kibana dashboard work ?  https://review.openstack.org/#/c/291986/
23:43:20 <sdake> where none exists today
23:43:31 <rajathagasthya> SamYaple: No, logs would be viewable in a separate Kibana dashboard.
23:43:53 <rajathagasthya> No idea how to integrate it with Horizon.
23:43:57 <inc0> no horizon will ever be involved
23:44:12 <inc0> even if that would be possible I'm -2
23:44:21 <inc0> and it's not so I don't need to be -2
23:44:40 <SamYaple> inc0: wait why?
23:44:45 <sdake> before we tlak about nuclear optoins
23:44:47 <SamYaple> it is possible
23:44:51 <sdake> lets discuss the problems with curl ;-)
23:44:56 <akwasnie> vhosakot: it shouldn't
23:45:14 <inc0> kibana itself is much more powerful and pretty than horizon
23:45:38 <rajathagasthya> akwasnie: The way we did it for Kibana 3 was just to replace it's default.json with the new content. Not sure if the same can be done in v4. If it can be, what do you think about that approach?
23:45:38 <vhosakot> akwasnie: cool, that's what I thought.. I am just replacing tar with yum/apt-get packages in Dockerfile.. thanks for confirming
23:45:50 <SamYaple> inc0: we can talk later thats apparently not the purpose of this topic
23:46:10 <sdake> the purpose of this topic is to discuss making the custom json dashboard for kibana
23:46:29 <sdake> to help support akwasnie elemoine inc0 in their summit talk
23:46:34 <akwasnie> rajathagasthya: but replace how? copy file into container?
23:46:45 <rajathagasthya> akwasnie: Yep.
23:47:02 <inc0> akwasnie, elemoine http://docs.ansible.com/ansible/uri_module.html
23:47:05 <akwasnie> rajathagasthya: into kibana?
23:47:08 <inc0> let's just use ansible and make one call
23:47:23 <inc0> it can be done by post-deploy
23:47:27 <rajathagasthya> akwasnie: Right. Into Kibana container. That becomes the default dashboard.
23:47:32 <akwasnie> aren't dashboards stored in elasticsearch?
23:47:52 <rajathagasthya> akwasnie: Maybe I need to check out the curl method you mentioned.
23:48:06 <sdake> akwasnie the answer is yes that is how itshould be odne
23:48:28 <sdake> rajathagasthya if you could link up with akwasnie and elemoine and help them with the implementation, that owuld rock
23:48:30 <rajathagasthya> akwasnie: Hmm, I don't think so. Kibana has the dashboards and just makes API calls to ES to get the data. That's my understanding.
23:48:40 <sdake> the idea is to get this ready to demo - but not necessarily have it merged, prior to summit
23:49:02 <rajathagasthya> sdake - Sure, I will sync up with them.
23:49:02 <sdake> since this is our only demo slot, we need to make it good
23:49:12 <sdake> rajathagasthya try EU timezones :)
23:49:25 <inc0> but instead of curl let's use this pretty, well defined ansible module
23:49:31 <inc0> and make it part of play
23:49:33 <rajathagasthya> sdake - Got it. :)
23:49:33 <akwasnie> rajathagasthya: as far as I know elasticsearch keeps dashboards
23:49:39 <sdake> inc0 works for me
23:50:21 <sdake> does everyone understand the goal?
23:50:33 <sdake> 1 month to get a rockin json dashboard implemented - 3 people to work on it - should be no problem ;)
23:50:52 <sdake> this is not part of mitaka - but part of newton
23:51:02 <rajathagasthya> sdake - Make it 4 with nkorabli. :)
23:51:28 <sdake> cool lets blow the audience away - diags are a hot topic in openstack these days
23:51:37 <sdake> i want to make sure kolla is leading in this space
23:52:16 <sdake> inc0 do you have a 60 second spiel about your and akwasnie's talk?
23:52:58 <sdake> this is our only demo slot - lets make it count!
23:52:58 <sdake> #topic open discussion
23:53:05 <inc0> well
23:53:17 <inc0> I will want to show prod kolla
23:53:21 <vhosakot> sdake: I added my analysis for the HEAT DOA bug so it may help
23:53:32 <Jeffrey4l> the ubuntu binary build and deploy gate https://review.openstack.org/#/c/292942/
23:53:35 <inc0> and kibana running on the back
23:53:50 <inc0> maybe show some actual issues and real world data
23:53:59 <SamYaple> Jeffrey4l: please take the floor here
23:54:06 <inc0> basically rockin' dashboard with acutal working opnestack worth of logs
23:54:15 <sdake> inc0 if possible i'd like you to showcase this rockin dashboard
23:54:19 <akwasnie> and explain why we chose Heka, right?
23:54:20 <Jeffrey4l> ubuntu do not have delorean style repo. But we can add it for stable branch.
23:54:38 <inc0> yeah, tha'ts my point, actual kibana with actual dash and actual logs in it
23:54:47 <Jeffrey4l> which is helpful for new commits.
23:55:11 <inc0> and say "and btw, all you need to do to get this cool thing is to change enable_central_logging to yes"
23:55:39 <Jeffrey4l> need some review and approve.
23:55:47 <sdake> Jeffrey4l i'll have a look
23:55:58 <sdake> inc0 sounds great - can't wait to see that talk
23:56:00 <SamYaple> weve only got about 3 minutes, can we talk about what we need for the ubuntu gate please
23:56:03 <sdake> hope to see all the core reviewers there
23:56:23 <SamYaple> basically we cant gate master, but we _can_ gate in stable, non-voting
23:56:27 <Jeffrey4l> cool. actually, two link https://review.openstack.org/#/c/292930/ for kolla,  https://review.openstack.org/#/c/292942/ for project config.
23:56:49 <sdake> ok folks lets get em reviewewd
23:56:54 <SamYaple> is everyone ok with not-gating something in master but in stable?
23:56:59 <sdake> i'll review project config now jeffrey(at conclusion of our meeting)
23:57:43 <sdake> SamYaple i see no harm in a nonvoting gate of any type even if they are inconsistent, as long as they can be maintained long term
23:58:12 <SamYaple> well our first integration will be on stable branch
23:58:27 <SamYaple> as-in it may be broken first stable
23:58:38 <SamYaple> thats the problem
23:59:04 <sdake> as long s project-config is non-voting i think that is probably ok
23:59:15 <sdake> it will help us shake out bugs in stable related to ubuntu binary
23:59:29 <Jeffrey4l> agreed with sdake
00:00:25 <sdake> i'll ask ajaeger to review, he is always spot on on project config
00:00:27 <sdake> times up ;)
00:00:29 <sdake> thanks for coming folks
00:00:32 <sdake> #endmeeting