15:59:43 <inc0> #startmeeting kolla
15:59:44 <openstack> Meeting started Wed Nov 29 15:59:43 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:59:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:59:47 <openstack> The meeting name has been set to 'kolla'
16:00:13 <inc0> #topic rollcall
16:00:17 <inc0> good morning everyone
16:00:22 <duonghq> o/
16:00:38 <Jeffrey4l> \o/
16:00:43 <rwellum> o/
16:00:53 <spsurya__> 0/
16:01:28 <chason> o/
16:03:34 <inc0> #topic announcements
16:03:38 <inc0> anyone?:)
16:04:25 <rwellum> I put a patch set out for the pike issues in kolla-k8s - thanks to everyone who's already signed up and reviewed.
16:04:30 <rwellum> https://review.openstack.org/#/c/523490/
16:04:53 <inc0> cool, thanks
16:05:08 <inc0> ok, let's get to agenda
16:05:17 <inc0> #topic storyboard migration
16:05:40 <inc0> Soo, we had this discussion some time ago, but I think we should restart it
16:05:52 <inc0> openstack is moving out of launchpad (slowly)
16:06:03 <inc0> and I, for one, am happy about that
16:06:37 <inc0> #link https://storyboard.openstack.org/#!/page/about
16:07:34 <chason> Looks good. :)
16:07:54 <Jeffrey4l> seems storyboard is not friendly for search engine?
16:08:33 <spsurya__> advantages over launchpad ?
16:08:50 <inc0> so storyboard is written by openstack community, so feedback can be addressed
16:09:21 <inc0> spsurya__: well there are few, layout seems to be cleaner, it's more like kanban board which allows for better tracking
16:09:42 <inc0> #link https://storyboard.openstack.org/#!/board/41
16:10:10 <rwellum> Very Trello looking.
16:10:20 <inc0> yeah
16:10:33 <inc0> what I like about it is that it's zuulv3 board, not infra board
16:10:48 <inc0> which means we could for example create board for all gate stuff
16:11:01 <inc0> and have smaller items under it
16:11:10 <inc0> like blueprint with work items
16:11:36 <inc0> just organized and supported instead of messing with description
16:12:04 <inc0> one thing I don't see right now is integration with gerrit
16:12:19 <inc0> which would be cool feature to have
16:12:32 <SotK> there is gerrit integration, I'll find the docs
16:12:42 <Jeffrey4l> seem no bug management. just for bp?
16:13:15 <inc0> well, bug management would be harder to migrate anyway
16:13:24 <inc0> as users (operators) are more used to lp
16:13:34 <inc0> we could create automatic bridge between these two
16:13:42 <inc0> but bugs in lp are reasonable
16:13:50 <inc0> still, that's a good point
16:14:10 <SotK> https://docs.openstack.org/infra/manual/developers.html#working-on-bugs describes how to make gerrit comment on stories and mark tasks as merged
16:15:33 <SotK> the way infra use storyboard currently is to track bugs/features in storyboard, and replace blueprints with specs in a git repository
16:16:35 <SotK> then work against the spec is tracked using stories/tasks
16:17:02 <rwellum> Which git repo?
16:17:08 <inc0> infra-specs
16:17:29 <rwellum> Seems reasonable
16:17:37 <inc0> we don't use specs in kolla nearly as much, so we would use storyboard to greater extend
16:18:20 <rwellum> Have you created a board yet inc0 :)
16:18:37 <inc0> no, before we commit, I wanted to have discussion
16:18:47 <inc0> but I will create if only to try it out:)
16:19:00 <rwellum> I'm tempted to create one for kolla-k8s and see how it is tracking out v 1.0 requirements.
16:19:07 <rwellum> (our)
16:19:11 <inc0> that would be great example!
16:19:21 <rwellum> On it.
16:19:24 <inc0> thanks
16:19:42 <rwellum> np
16:21:17 <inc0> ok, so let's start there and see where it gets us
16:21:41 <inc0> again, I'm not huge fan of launchpad but migration will be quite a bit of work
16:21:58 <inc0> so we'll need to be sure that it's what we want/need
16:23:21 <SotK> the actual migration process is automated, unless I'm missing some context on what things you'd need to do other than add existing bugs into storyboard
16:23:34 * diablo_rojo_phon sneaks in late
16:23:50 <inc0> it's more about mental change than task migration
16:23:59 <inc0> it will affect out process
16:24:06 <inc0> so it will create some chaos
16:24:27 <inc0> diablo_rojo_phon: welcome:)
16:25:07 <inc0> one thing I see myself would be: we still need launchpad for bugs (as Jeffrey4l said, storyboard doesn't seem to have great support for bugs)
16:25:30 <inc0> so that would mena we're adding one more tool to process which is complication
16:25:44 <Jeffrey4l> and it is not easy to track issue for different branch, i guess.
16:26:02 <diablo_rojo_phon> No you won't. You just want to make use of tags.
16:26:22 <rwellum> o/ @ diablo_rojo_phon
16:26:28 <inc0> well tags won't give same effect tho
16:26:49 <inc0> when we have bug we need to fix it on 3 branches - master, pike, ocata
16:27:02 <inc0> hard to see which is done, which is todo
16:27:06 <diablo_rojo_phon> When you think about it a bug is just a code change the same as a new implementation. Making use of the description fields and tags to sort and prioiritize should give the same effect as long.
16:27:17 <inc0> well not exactly
16:27:24 <inc0> it's bug reporting that's an issue
16:27:31 <SotK> you can track bugs per-branch in storyboard, though I don't think there is a way to set the branch from the web ui yet
16:27:33 <inc0> in launchpad you have big button "report a bug"
16:27:47 <SotK> s/bugs/tasks/
16:27:52 <inc0> people who don't know launchpad will handle it
16:27:59 <Jeffrey4l> diablo_rojo_phon, is there any bot for storyboard like what launchpad does? for example "Closes-Bug:" feature.
16:28:04 <diablo_rojo_phon> Use worklists to organize for different branches or milestones.
16:28:23 <inc0> I wouldn't know how to submit a bug to kolla-ansible today
16:28:30 <inc0> in storyboard
16:28:33 <diablo_rojo_phon> Jeffrey4l: yep, the story and task numbers work the same way as bug numbers do with Gerrit.
16:29:04 <diablo_rojo_phon> kolla-ansible is a sub repo of kolla I gather?
16:29:06 <Jeffrey4l> cool.
16:29:11 <inc0> sub-project even
16:29:19 <inc0> but yeah
16:30:00 <inc0> like, having one flat list of stories/bugs with extremally easy way to add to them
16:30:25 <inc0> and memorable link
16:30:28 <diablo_rojo_phon> Take a look at how infra is in storyboard.
16:30:36 <inc0> like, today it's bugs.launchpad.org/kolla-ansible
16:30:54 <rwellum> How do you add a new project to storyboard? Seems like every task needs to be linked to create one.
16:31:18 <diablo_rojo_phon> They have tons of sub repos. Each one is a project. It's a 1:1 mapping.
16:31:29 <inc0> infra is a bit different animal than kolla tho. our users aren't necessarily familiar with openstack community stuff
16:31:46 <diablo_rojo_phon> rwellum: it's a one line change in the project-config projects.yaml file.
16:31:49 <inc0> yeah I liked that about storyboard,
16:32:39 <inc0> diablo_rojo_phon: so we will start tracking kolla-k8s with storyboard as trial run
16:33:04 <inc0> however, if you guys gather some feedback - good bug mgmt would be mine
16:33:25 <inc0> having both sb and lp will be painful
16:34:36 <diablo_rojo_phon> I can send along some other resources to help you understand better the mental shift if that helps?
16:35:06 <Jeffrey4l> diablo_rojo_phon, that will be help ;D
16:37:23 <chason> d
16:38:41 <Jeffrey4l> inc0, move on?
16:38:44 <inc0> yeah
16:38:52 <inc0> #topic open discussion
16:38:54 <diablo_rojo_phon> Thanks inc0 :)
16:38:57 <inc0> anyone?:)
16:39:02 <inc0> thank you diablo_rojo_phon
16:39:02 <chason> diablo_rojo_phon thanks in advance, it will be helpful!
16:39:11 <Jeffrey4l> i want to talk the progress of new gate.
16:39:20 <inc0> ok, good one
16:39:22 <inc0> :)
16:39:25 <inc0> shoot
16:39:37 <Jeffrey4l> now. master and ocata is pushing image to docker hub
16:39:47 <Jeffrey4l> and the kolla-ansible jobs is pull image from it two.
16:40:03 <inc0> no pike?
16:40:06 <Jeffrey4l> for pike branch, https://review.openstack.org/518797 this patch is ready to go
16:40:07 <rwellum> Yeah same qn
16:40:33 <Jeffrey4l> rwellum, i think kolla-k8s can move to pull the image from dockerhub, too. ;D
16:40:50 <rwellum> Jeffrey4l: soon as Pike is in I will try
16:41:04 <Jeffrey4l> inc0, lots of jobs issue occur recently. :(
16:41:11 <inc0> lots of timeouts
16:41:13 <Jeffrey4l> it slow down the prgress.
16:41:35 <inc0> binary gates are still voting :S
16:41:36 <Jeffrey4l> inc0, yes. i am trying to improve this. by adding more reverse proxy in infra env.
16:41:42 <Jeffrey4l> which may helpful.
16:41:52 <inc0> problem is there is no mirror for oraclelinux
16:41:56 <Jeffrey4l> inc0, yes. should backport certain patch.
16:42:15 <Jeffrey4l> inc0, oraclelinux, elastico.com and opendaylight ;(
16:42:25 <Jeffrey4l> check this https://review.openstack.org/523693 inc0
16:42:45 <Jeffrey4l> add more reverse proxy ^^
16:43:25 <inc0> cool
16:43:28 <inc0> that should help
16:43:36 <Jeffrey4l> inc0, i also trying to add a squid cache proxy in our jobs to check which site is slowing.
16:43:38 <inc0> I'll get back to multinode gates
16:43:42 <Jeffrey4l> here it is https://review.openstack.org/521450
16:43:46 <inc0> ceph is misbehaving
16:43:46 <Jeffrey4l> yep
16:43:56 <Jeffrey4l> multinode should be implemented now.
16:44:38 <Jeffrey4l> so feel free to review the pike publish patch https://review.openstack.org/518797
16:44:47 <inc0> I'll get back to work on it
16:44:55 <Jeffrey4l> cool.
16:45:01 <inc0> duonghq spsurya__ ^
16:45:19 <Jeffrey4l> this is all
16:45:29 <inc0> cool thank you
16:45:30 <spsurya__> inc0: yeah
16:45:36 <duonghq> inc0, will check tomorrow
16:45:39 <inc0> thanks!
16:45:52 <duonghq> so, can I have a few words?
16:46:02 <inc0> was about to ask:) duonghq floor is yours
16:46:12 <duonghq> thank, inc0
16:46:32 <duonghq> https://blueprints.launchpad.net/kolla-ansible/+spec/support-custom-policy-yaml -> can somebody review this bp?
16:46:50 <duonghq> due to TC decided that policy in code should be done in Queen
16:46:54 <duonghq> https://governance.openstack.org/tc/goals/queens/policy-in-code.html
16:47:09 <duonghq> my colleague is waiting on our decision
16:47:23 <duonghq> and he has done one example
16:47:31 <duonghq> https://review.openstack.org/#/c/514565/
16:48:48 <Jeffrey4l> is policy file only needed by api layer?
16:49:26 <duonghq> ya, it's kind of replacement for policy.json
16:50:32 <Jeffrey4l> this is another topic, but if this is confirmed. we'd better remove copying policy.* file to non-api container.
16:51:01 <duonghq> ah, sure, we should move a quick check about this
16:51:15 <Jeffrey4l> directing is OK. i have approved this bp.
16:51:23 <Jeffrey4l> i will review the patch tomorrow ;D
16:51:30 <duonghq> Jeffrey4l, thanks
16:51:32 <britthouser> So is this something that would be easy to divide and conquer?
16:51:38 <Jeffrey4l> np
16:51:42 <inc0> britthouser: yeah
16:51:53 <inc0> lots of very similar patches
16:52:26 <duonghq> britthouser, after 1st patch is merged, yes
16:52:31 <britthouser> Do we want to do a sign up and get the entire community to pitch in?
16:53:04 <duonghq> I think that we do not need make this, some people will finish it quickly
16:53:19 <Jeffrey4l> duonghq, does openstack support policy.json and policy.yml file at the same time. i.e. what will happen when i add the two files at the same time.
16:53:54 <egonzalez> Is there any place to see which projects has implemented policy in code already. To make sure not implement stuff not working
16:54:09 <duonghq> Jeffrey4l, it'll has priority, iirc, the yaml one will have higher priority than json
16:54:37 <duonghq> egonzalez, no, atm, we should take a look at project itself
16:54:44 <Jeffrey4l> egonzalez, doude btw i do not think it is matter that whether the project implemented policy in code.
16:55:04 <Jeffrey4l> this bp is just implementing "support policy.yml"
16:55:42 <Jeffrey4l> whether the project will override the file or merge it with the policy in code, it doesn't matter.
16:55:49 <Jeffrey4l> or kolla-ansible do not care.
16:57:30 <inc0> allright, duonghq anything to add?
16:58:23 <inc0> guess not:)
16:58:25 <duonghq> inc0, no, that's all from me
16:58:29 <inc0> let's wrap up
16:58:30 <duonghq> thanks Jeffrey4l inc0 egonzalez
16:58:34 <inc0> thank you all for coming!
16:58:38 <inc0> #endmeeting kolla