16:00:59 <inc0> #startmeeting kolla
16:00:59 <openstack> Meeting started Wed Jan 11 16:00:59 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:01 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:04 <openstack> The meeting name has been set to 'kolla'
16:01:16 <inc0> #topic rollcall, w00t please!
16:01:17 <egonzalez> woot o/
16:01:18 <duonghq> O/
16:01:20 <inc0> you know what to do
16:01:21 <inc0> ;)
16:01:25 <Jeffrey4l> o/
16:01:27 <mandre> o/
16:01:30 <sayantani01> woot woot!
16:01:31 <mliima> :) \Ô/
16:01:35 <berendt> o/
16:01:37 <britthouser> 0/
16:01:37 <sdake> o/
16:01:42 <rhallisey> hello
16:01:48 <zhubingbing> o/
16:01:50 <zhubingbing> o/
16:02:06 <sdake> zhubingbing did a double wave :)
16:02:17 <zhubingbing> ；）
16:02:42 <pbourke> o/
16:02:46 <sp__> o/
16:02:46 <SamYaple> 0/
16:02:50 <kfox1111> o/
16:02:57 <qwang> o.
16:03:01 <qwang> o/
16:03:48 <inc0> #topic Announcements
16:04:18 <inc0> 1. We have voting open for new deliverables. Cores, please cast a vote, you should get link on your mailbox
16:04:39 <inc0> any community announements?
16:04:49 <sdake> just a heads up - if you don't get a voting link please ping inc0
16:04:56 <sdake> its important that eveyrone have a vote ;)
16:05:06 <inc0> well, in this case core team;)
16:05:10 <wirehead_1> meow meow
16:05:13 <sdake> right - just core team will get link :)
16:05:18 <sdake> core teams :)
16:05:29 <portdirect> wirehead_: woof! woof!
16:05:41 <inc0> behave you two!
16:05:55 <inc0> who are good boys?
16:06:05 <inc0> ok, back to business;)
16:06:13 <inc0> I guess no other announcements?
16:06:24 <sdake> things pretty slow becaue of the holiday shutdown inc0
16:06:25 <inc0> moving on
16:06:33 <inc0> yeah, trust me I know
16:06:36 <sdake> although we are tagging 3.0.2 of kolla
16:06:37 <inc0> Oregon is shut down today
16:06:40 <sdake> or i t has been tagged
16:06:42 <Jeffrey4l> i have one, newton 3.0.2 is release
16:06:44 <inc0> it has been tagged
16:06:46 <sdake> and also kolla-kubernetes 0.4.0 is tagging soon
16:06:51 <sdake> hopefully its ready today
16:06:52 <Jeffrey4l> cool.
16:06:58 <zhubingbing> cool
16:07:02 <sdake> Jeffrey4l you will have to submit hte erquest pls :)
16:07:09 <sdake> we can add that to agenda i htink
16:07:12 <egonzalez> Jeffrey4l: feature freeze for Ocata is in two weeks right?
16:07:15 <Jeffrey4l> sdake, my pleasure.
16:07:17 <kfox1111> need some hub images for 3.0.2
16:07:19 <Jeffrey4l> egonzalez, yep.
16:07:24 <inc0> ok, actually let's start with this one
16:07:27 <Jeffrey4l> around Jan 25.
16:07:27 <kfox1111> and there's about 3 ps's about to go in to finish 0.4.0.
16:07:33 <inc0> #topic releases, 3.0.2 and 0.4.0
16:07:56 <inc0> my question is
16:08:08 <inc0> does 0.4.0 need to be based on 3.0.2 images?
16:08:25 <inc0> or this is just because gate lacking of new images?
16:08:36 <sdake> inc0 my take is kolla-kubernetes *should* be building images from kolla repo and loading into a docker hub locally in the gate
16:08:55 <inc0> you mean master?
16:09:02 <sdake> inc0 however that is not the case with the images
16:09:17 <sdake> I'd like master rather then newton for kolla-kubernetes yes, however, kfox1111 seems to want newton
16:09:23 <Jeffrey4l> seems kolla-k8s is using 3.0.2 hub.docker.com images
16:09:25 <sdake> we should always be gating on master
16:09:26 <kfox1111> there are some hacks in kolla-kubernetes to work around bugs in 3.0.1
16:09:33 <kfox1111> we'd really like to get rid of them for 0.4.0.
16:09:47 <sdake> inc0 for the short term, we need the 3.0.2 docker hub images
16:09:54 <sdake> perhaps Jeffrey4l can build them and push them
16:10:00 <sdake> since coolsvap is out of the office for the moment
16:10:08 <kfox1111> Jeffrey4l said he didn't have the bandwidth.
16:10:13 <sdake> ok
16:10:14 <Jeffrey4l> sdake, actually no. ( have a bad net in China )
16:10:18 <kfox1111> portdirect does but doesn't have a machine available.
16:10:23 <sdake> kfox1111 i'll push them today then
16:10:31 <kfox1111> k. thanks.
16:10:34 <Jeffrey4l> portdirect, promise to push them today.
16:10:36 <sdake> but can't make a long term commitment to pushing consistently
16:10:39 <inc0> thanks sdake
16:10:44 <inc0> I'll push buntu
16:10:50 <kfox1111> if you coudl do the centos-binary and ubuntu-binary first, then I can test sooner.
16:10:53 <sdake> inc0 cool - splitting up work sounds great :)
16:10:53 <inc0> no, we need to handle it automagically
16:11:02 <inc0> at the end of the day
16:11:05 <kfox1111> +1 to automation in the future.
16:11:07 <sdake> inc0 agreed
16:11:10 <kfox1111> I can help with that I think.
16:11:22 <duonghq> When our network better I will take the responsibility but auto is better ideal
16:11:23 <inc0> we should talk to infra
16:11:38 <portdirect> if you are struggling - I'll have access back in about 4 hours
16:12:02 <inc0> anyway, https://review.openstack.org/#/c/418550/ <- working on bringing fresh images to gates
16:12:03 <sdake> i can definately push the centos images - I have a pushing vm just for i t
16:12:25 <sdake> just can't commit long term to pushing or maintaining docker hub images because of time constraints with $$DAYJOB
16:12:54 <inc0> no commitments
16:13:15 <kfox1111> sdake: awesome thanks. yeah. long term it really belongs in the gate somehow. I have some ideas after talking with infra that might work.
16:13:26 <sdake> inc0 that work looks relaly good
16:13:45 <inc0> well, I hope to make it work sooner rather than later
16:13:53 <sdake> kfox1111 what that work does is use master images (rather then newton) to gate kolla-kubernetes
16:13:59 <sdake> this is how kolla-ansible operates until end of cycle
16:14:24 <inc0> yeah, I'd like to have same logic for that across deliverables
16:14:36 <inc0> otherwise explaining it to users will be hell
16:14:36 <sdake> inc0 i think where that might struggle is xenial binary since i'm not sure they have a DLRN feature
16:14:37 <sdake> (delorean)
16:14:56 <inc0> why would that be an issue?
16:15:03 <inc0> I mean we have xenial binary
16:15:03 <sdake> kfox1111 do you have issue with that?
16:15:25 <kfox1111> sdake: my plan was to get both working.
16:15:25 <sdake> inc0 the reason is because kfox1111 stated above he needs 3.0.2 containers for ubuntu binary (the gate is voting iirc or will be soon)
16:15:32 <kfox1111> newest stable and trunk.
16:15:35 <kfox1111> then we can test upgrades.
16:15:40 <sdake> kfox1111 cool - thats a fantastic idea
16:15:56 <inc0> I'd be soft against voting on binary gates
16:16:01 <sdake> kfox1111 so no conflict then with the idea?
16:16:06 <inc0> as binary gates arent voting in kolla
16:16:09 <kfox1111> so that ps is great, but I'll add another set of tests for it.
16:16:15 <sdake> inc0 ya i feel same way - maybe nonvoting gates for some time
16:16:29 <kfox1111> inc0: I agree with not voting on binary trunk.
16:16:30 <inc0> so technically there is slight chance of have them polluted in tarballs.o.o
16:16:39 <kfox1111> binary stable should always work though.
16:16:39 <inc0> source gates are voting and should be stable at all times
16:16:50 <inc0> yeah, not our fault most of the time
16:16:55 <kfox1111> yeah.
16:17:00 <sdake> inc0 source  gates on deploy are voting?
16:17:04 <sdake> for ansible?
16:17:31 <kfox1111> we should talk about making kolla-kubernetes gates voting on kolla container changes too at some point.
16:17:38 <inc0> no, but after registry happends there (https://review.openstack.org/#/c/413720/) I hope to make them such
16:17:46 <sdake> inc0 sweet :)
16:17:53 <wirehead_> Yeah, that's already regressed at least once or twice, kfox1111
16:17:53 <inc0> speaking of which, review this change polease
16:17:55 <inc0> it's important
16:18:10 <inc0> Jeffrey4l, how long till it's no longer wip?
16:18:16 <sdake> kfox1111 what  we need there is cross repo gating
16:18:22 <kfox1111> sdake: yeah.
16:18:27 <Jeffrey4l> will update it tomorrow.
16:18:36 <sdake> kfox1111 i can possibly help implement that since Jeffrey4l has figured it out already
16:18:47 <sdake> kfox1111 and its just a different set of scripts and gate code to run
16:18:55 <kfox1111> sdake: I think the kolla-kubernetes gate should be reusable for that. just needs containers prebuilt before the  run.
16:19:16 <inc0> so review I proposed is to kolla-k8s
16:19:18 <sdake> kfox1111 right - that is how kolla-ansible does cross-repo gating
16:19:20 <inc0> and this is kolla-ansible
16:19:26 <inc0> so both repos already have wip
16:20:13 <inc0> anyway, keep an eye on these changes please, we can have voting gates before end of the year with them
16:20:36 <sdake> you mean 2017 :)
16:20:45 <inc0> release
16:20:49 <inc0> omg, need caffeine
16:20:53 <inc0> sorry
16:20:58 <sdake> ya - that conufsed me - why i asked for clarification :)
16:21:10 <inc0> let's move on
16:21:26 <inc0> #topic Deprecation of Debian images during Ocata cycle, removal during Pike cycle
16:21:30 <inc0> berendt, you're up
16:21:42 <berendt> yes i want to revisit this topic
16:21:51 <berendt> we already discussed the removal of debian last cycle and delayed it
16:21:58 <berendt> is there any activity on the debian images now?
16:22:06 <berendt> there are still not gate jobs
16:22:10 <Jeffrey4l> i see nothing
16:22:23 <berendt> i already opened a review and a bug report for the deprecation
16:22:37 <berendt> if you think it is fine to move forward i will open a vote on dev ml tomorrow
16:22:47 <sdake> here is the thing
16:22:57 <sdake> we agreed already we would deprecate if there was not further implementation
16:23:02 <sdake> and i have not seen further implementation
16:23:09 <sdake> nor have I seen anyone step up to maintain it
16:23:15 <berendt> this means we do not need an other vote?
16:23:16 <sdake> those were the two things we agreed upon
16:23:42 <berendt> #link https://review.openstack.org/#/c/417874/
16:24:07 <sdake> berendt i think we agred we would vote on it again this cycle
16:24:14 <sdake> although i don't recall
16:24:28 <berendt> ok i will open a vote tomorrow
16:24:34 <inc0> berendt, so to follow full deprecation path we should also send mails to openstack-dev and ops mailing lists
16:24:57 <berendt> inc0: i will cc openstack-ops, this should be sufficient
16:24:57 <sdake> berendt right - that is part of the process - especially the ops list
16:24:59 <inc0> also, I'd say if we find volunteer to pick up the work and create gates, we shouldn't deprecate it
16:25:15 <berendt> inc0: yes, but we already tried this last cycle.
16:25:19 <sdake> here is what I'd suggest
16:25:28 <sdake> send email to ops list, if the ops list responds with crickets
16:25:38 <kfox1111> sdake: there's a chance the email will dig someone up. so lets leave the door open a crack for that.
16:25:39 <sdake> then send vote to ml for core review team
16:25:41 <inc0> yeah, so just a remider to them;)
16:25:46 <sdake> kfox1111 agreed
16:25:52 <kfox1111> but if no one shows up we do follow through.
16:26:02 <inc0> yeah I'd hate to screw people who actually used it
16:26:08 <sdake> berendt - i'd highly recommend doing them staged tho - email to ops list - wiat a week, then email to dev list
16:26:10 <berendt> ok, mail to ops this week, mail to dev with vote next week if nobody rpolies
16:26:14 <sdake> if ops say "NO WAY"
16:26:19 <sdake> then we are stuck with it :)
16:26:28 <inc0> and have a volunteer
16:26:51 <inc0> if someone says no way to me it's equivalent to "I'll take care of these images"
16:26:53 <berendt> ok i will do this tomorrow, we can revisit the feedback from ops next meeting and move forward with the vote after the next meeting
16:27:03 <inc0> you can point that in email too;)
16:28:12 <inc0> can we move on?
16:28:14 <berendt> i think we can move forward to the next topic
16:28:24 <inc0> #topic PTG planning
16:28:36 <inc0> I wanted to leave it to the end, so we can keep doing it for rest of meeting
16:28:40 <berendt> who will attend?
16:28:55 <sdake> berendt inc0 has organized remote participation
16:29:07 <sdake> berendt so hopefully eveyrone from the core review team can make it that can't make the travel
16:29:10 <inc0> #link https://etherpad.openstack.org/p/kolla-ocata-ptg
16:29:17 <inc0> yeah, we'll have teleconferences going
16:29:26 <berendt> that's great
16:29:27 <duonghq> Nice
16:29:34 <kfox1111> I'll be attending.
16:29:40 <sdake> i'll also be there in person
16:29:52 <sdake> mon-wed
16:30:00 <portdirect> you'll be able to disconnect me :)
16:30:11 <sdake> i leave wed at some point, although I saw tripleo wants to have a collaboration effort
16:30:13 <inc0> so I think this PTG will have more k8s sessions than ansible
16:30:24 <inc0> depends on our decision
16:30:30 <kfox1111> sdake: +1 to talking with tripleo
16:30:37 <Jeffrey4l> i will not be there.
16:30:42 <sdake> kfox1111 unfortunately i can't change my flight
16:30:48 <inc0> but personally think at this stage of project we need more talking in k8s
16:30:54 <sdake> kfox1111 so if we do anything live it will have to be wednesday morning
16:30:55 <kfox1111> sdake: thats ok. I'll be there all week, so I can do it.
16:31:00 <sdake> kfox1111 cool
16:31:05 <inc0> well, wed is common day I think
16:31:13 <inc0> and I can try to extend my stay
16:31:15 <sdake> inc0 wish that was clear from the schedule :(
16:31:19 <inc0> so we'll see
16:31:37 <inc0> yeah, I need to pick the brain of organizers regarding time/space
16:32:17 <sdake> comon folks plz open the ptg etherpad :)
16:32:36 <sdake> there is only 7 people on it atm, and we had a whoel bunch of waves at the meeting start :)
16:32:42 <inc0> so far 5/5 is kolla-k8s;)
16:36:01 <sdake> even if you can't make the ptg, please add your suggestions for sessions
16:37:00 <rhallisey> SamYaple, around?
16:37:44 <zhubingbing> talk about flaunted?
16:37:51 <sdake> egonzalez the red hurts my eyes :)
16:37:57 <zhubingbing> fluentd
16:37:58 <sdake> egonzalez any chance you can  change your colors :)
16:38:07 <egonzalez> yeah, me too ;)
16:38:36 <sdake> thanks egonzalez :)
16:40:59 <SamYaple> rhallisey: i am
16:43:19 <rhallisey> SamYaple, have you ever considered having multiple playbooks in kolla-ansible.  A playbook for bootstrap, deploy, upgrade, ect...
16:44:03 <rhallisey> or having one playbook with good use of tags
16:44:13 <rhallisey> for easier browfield deploys
16:44:37 <inc0> rhallisey, I did
16:44:54 <rhallisey> inc0, what are your thoughts on the matter?
16:44:56 <inc0> we did action variable because there is no way to share parts of roles
16:45:18 <inc0> like, I don't want to have role nova-upgrade because it won't be able to share any tasks from nova-deploy
16:45:26 <rhallisey> right
16:45:34 <inc0> and in reality in 90% of cases they're just subset of deploy tasks
16:45:44 <rhallisey> yup that's true
16:45:45 <inc0> with potentially few extra upgrade specific tasks
16:45:56 <SamYaple> rhallisey: thats supposed to be dont with tags
16:46:07 <SamYaple> rhallisey: at least in the ansible world, kolla does it different
16:48:36 <sdake> wow 19 people on the pad
16:48:36 <sdake> like a record ;-)
16:56:00 <sdake> ok looks like people are sort of done :)
16:56:10 <inc0> yeah
16:56:13 <sdake> I think we can refine this next meeting a bit as well - typically in the past we have 2-3 sessions on it
16:56:16 <inc0> let's have few minutes of open convo
16:56:17 <sdake> just sorting out the agenda
16:56:19 <inc0> #topic open discussion
16:56:41 <sdake> thanks inc0 for the agenda  time - I know its expensive :)
16:57:13 <inc0> yeah, this part of our meeting process is not ideal
16:57:41 <inc0> maybe etherpad would be easier
16:57:57 <egonzalez> zhubingbing is finishing fluentd, review/test are welcomed ;)
16:57:59 <Jeffrey4l> etherpad can be multi thread ;)
16:58:02 <egonzalez> #link https://review.openstack.org/#/c/407392/
16:58:02 <sdake> zhubingbing ++
16:58:12 <zhubingbing> yes
16:58:23 <zhubingbing> fluentd most log analysis work has been basically completed;
16:58:33 <zhubingbing> help me review it
16:58:36 <sdake> zhubingbing is syslog sorted out?
16:58:47 <zhubingbing> yes
16:59:11 <zhubingbing> about fluentd is differnet
16:59:22 <sdake> zhubingbing cool - i'll pull down the patchset today and give it a go before next meeting
16:59:37 <mliima> we have many DocImpact bugs filled in launchpad:/
16:59:40 <sdake> i'd encourage others to do the same, so we can get this work merged - it seems pretty important
16:59:46 <zhubingbing> Flunentd syslog with heka there is a bit different
16:59:46 <Jeffrey4l> fluentd do not support syslog /dev/log socket and it listen on a tcp port.
16:59:46 <inc0> guys
16:59:50 <inc0> we ran out of time
16:59:54 <inc0> please overflow to kolla
16:59:58 <inc0> thanks everyone for attending!
17:00:00 <sdake> thanks inc0
17:00:00 <mliima> bye guys
17:00:03 <inc0> #endmeeting Kolla