15:01:25 <yamahata> #startmeeting neutron_northbound
15:01:25 <odl_meetbot> Meeting started Mon Aug 14 15:01:25 2017 UTC.  The chair is yamahata. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:01:25 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:25 <odl_meetbot> The meeting name has been set to 'neutron_northbound'
15:01:35 <yamahata> #topic agenda bashing and roll call
15:01:41 <yamahata> #info yamahata
15:01:53 <yamahata> #link https://wiki.opendaylight.org/view/NeutronNorthbound:Meetings
15:02:00 <mpeterson> #info mpeterson
15:02:20 <manjeets> #info manjeets
15:02:39 <yamahata> any additional topics in addition to usual patch/bug review?
15:03:08 <rajivk> #info rajivk
15:03:39 <rajivk> yamahata, we had discussion about l3 flavor
15:03:51 <rajivk> if we get time, i would like to discuss about it.
15:03:56 <yamahata> Cool.
15:04:06 <yamahata> Let's discuss at open mike part
15:04:15 <rajivk> ok
15:04:31 <yamahata> #topic Announcements
15:04:53 <yamahata> now the last week was pike rc1 week. Now stable/pike branch was cut.
15:05:17 <yamahata> Still openstack CI isn't in good shape, we will focus on fixes it.
15:06:08 <yamahata> On ODL side, we passed M-5. It's feature freeze. and we don't have any further feature.
15:06:08 <mkolesni> hi
15:06:12 <mkolesni> #info mkolesni
15:06:30 <yamahata> mkolesni: hi. do you have any extra topic today?
15:06:49 <mkolesni> no nothing today
15:07:11 <yamahata> any other announcement?
15:07:49 <mkolesni> i saw we have no gating tempest jobs
15:07:54 <mkolesni> thats not good
15:08:15 <yamahata> After many recheck I gave up to make boron+tempest job non-voting.
15:08:26 <yamahata> Right, that's not good.
15:08:34 <mkolesni> so whats the plan?
15:08:46 <yamahata> Before starting queens, ideally we should make carbon + v2driver voting.
15:08:56 <manjeets> yamahata, ++
15:09:02 <mkolesni> ok well afaik the bug there wasnt fixed
15:09:11 <yamahata> But it's quite up to our effort.
15:09:42 <manjeets> mkolesni, is that bug related to carbon release ? is it in ODL ?
15:09:58 <mkolesni> yes we talked about it last week
15:10:05 <yamahata> #topic Pike/Nitrogen planning
15:10:33 <yamahata> From the past observation, it's likely that the issue is in ODL side. probably odl netvirt.
15:10:47 <mkolesni> manjeets, https://bugs.opendaylight.org//show_bug.cgi?id=8893
15:11:52 <manjeets> thanks mkolesni
15:12:07 <yamahata> mkolesni: any update? there is a response from Sam, though.
15:12:23 <mkolesni> yamahata, no, just that response from sam
15:13:02 <yamahata> I see. Can you please take care of further communication?
15:13:08 <mkolesni> 193064
15:13:22 <yamahata> Anyway we should raise any issues to netvirt folks and drive fixing issues.
15:13:39 <yamahata> or fix any issues ourselves.
15:13:50 <mkolesni> ive been raising it for a couple of weeks now, doesnt help
15:14:00 <mkolesni> do you have anyone that can chime in?
15:14:43 <yamahata> They have weekly meeting on Tuesday. So we should attend it to draw their attention.
15:15:01 <mkolesni> ok tomorrow i cant but maybe you can
15:15:31 <yamahata> I see.
15:15:52 <yamahata> For Pike, we have still two bug fixes left.
15:16:02 <yamahata> https://review.openstack.org/#/c/491528/
15:16:08 <yamahata> https://review.openstack.org/#/c/331382/
15:16:22 <yamahata> We will merge them into master and then backport them to Pike.
15:16:43 <yamahata> any other patches for Pike?
15:17:37 <yamahata> https://review.openstack.org/#/c/464952/ wasn't merged for Pike. but it's not critical.
15:18:06 <rajivk> for 331382, i am working on UT. Just saw mike comment, incorporate them and submit them probably today.
15:18:22 <yamahata> cool.
15:18:59 <yamahata> any volunteer for 491528? mkolesni ?
15:19:24 <rajivk> yamahata, did you go through my comments?
15:19:34 <rajivk> My last comment.
15:19:47 <mkolesni> yamahata, i abandoned it it was a mis configuration
15:19:47 <yamahata> 331382?
15:20:10 <rajivk> yamahata, no 491528 one.
15:21:12 <rajivk> yamahata, I don't have much knowledge about neutron code, but those are the points, i could came up with.
15:21:19 <yamahata> mkolesni: oh then, 491528 isn't necessary? can the bug report be closed?
15:21:36 <mkolesni> yes
15:22:19 <rajivk> yamahata, For 464952.
15:22:32 <yamahata> can you please mark the report invalid and abandon the patch?
15:22:59 <mkolesni> sure
15:23:00 <manjeets> patch is abandoned
15:23:17 <yamahata> Oh the patch part is okay.
15:23:25 <rajivk> Can you please consider the approach for updating column? i saw your patch. Last time, i saw you had problem with deleting column due to constraints.
15:23:34 <yamahata> The next patch is 464952
15:23:50 <yamahata> rajivk: yeah.
15:24:16 <rajivk> yamahata, can we change default in place?
15:24:20 <mkolesni> better fix is just change the model
15:24:29 <mkolesni> not bd migration
15:24:31 <mkolesni> db
15:24:32 <rajivk> I mean without deleting table and creating again.
15:24:38 <mkolesni> this field isnt being looked at anyway
15:24:46 <mkolesni> so this is quite a moot "fix"
15:25:24 <mkolesni> you can even drop it
15:25:49 <yamahata> The functional test should be fixed at least.
15:26:23 <mkolesni> lets drop the column less worries that way
15:26:32 <rajivk> Do you guys think, we can do something like "ALTER TABLE Employee ADD DEFAULT 'SANDNES' FOR CityBorn"
15:26:47 <yamahata> maybe model itself directly changed... we will see.
15:26:48 <mkolesni> 481958
15:28:26 <yamahata> rajivk: Maybe that would work. Can you please take care of it?
15:28:50 <rajivk> yamahata, i tried it. It fails during migrations test.
15:28:59 <mkolesni> $ git grep created_at | grep -v "^db/migration.*" | grep -v "^tests/.*"
15:29:00 <mkolesni> db/db.py:                                     created_at=func.now(),
15:29:00 <mkolesni> db/models.py:    created_at = sa.Column(
15:29:25 <rajivk> yamahata, I will look into this approach again.
15:29:47 <mkolesni> look
15:29:49 <mkolesni> no usages
15:29:53 <mkolesni> lets just drop it
15:30:50 <yamahata> Oh cool. dropping the column seems the easiest solution.
15:31:01 <mkolesni> i agree
15:31:18 <rajivk> okay, i can do this one.
15:32:14 <yamahata> the next patch, 481958. mkolesni, a patch for infra? Or am I looking at different one?
15:33:22 <mkolesni> no sorry its my yubikey sometimes gets pressed
15:33:37 <yamahata> no problem.
15:33:45 <yamahata> any other patches/bugs for Pike?
15:34:44 <mkolesni> yamahata, https://review.openstack.org/#/c/487719/
15:34:56 <mkolesni> as discussed this should be reverted and properly reviewwed
15:35:10 <mkolesni> also lets try to gather more community and/or core reviewers on the ptg
15:35:25 <yamahata> can you respond to yamamoto comment?
15:35:31 <mkolesni> yes i replied
15:35:44 <mkolesni> oh didnt publish silly me
15:35:58 <mkolesni> there
15:35:59 <yamahata> As patch 5?
15:36:08 <mkolesni> no i replied to his comment
15:36:12 <yamahata> Oh now I'm seeing it.
15:36:46 <mkolesni> yes i forgot to submit the response
15:37:10 <yamahata> Yeah, reviewers are issues. Let's discuss at the ptg.
15:37:28 <yamahata> mkolesni: btw can I expect more your review? according to stackerlystics, it's low.
15:37:38 <mkolesni> sure but for now lets revert and review properly
15:38:01 <mkolesni> ill talk to my manager about it
15:39:32 <yamahata> There are several patches form mpeterson .
15:39:53 <yamahata> It's Pike RC phase, we will focus on stabilizing it.
15:40:05 <mpeterson> yamahata: yes, primarly it is the ability to force a full_sync as we talked a couple of weeks back
15:40:15 <mkolesni> yes though we can start reviewing them if we have time
15:41:06 <yamahata> Yeah we can.
15:41:16 <mkolesni> also now that pike was cut theres no reason not to merge them but lets give the stabilizationb effort priority
15:41:31 <yamahata> #topic patches/bugs
15:41:40 * yamahata noticed we're already discussing bugs/patches.
15:41:56 <yamahata> anything else? or we can move on to open mike.
15:42:11 <mpeterson> yamahata: there was the pep8 patch
15:42:26 <mkolesni> :)
15:42:26 <yamahata> https://review.openstack.org/#/c/492461/ ?
15:42:35 <mpeterson> according to tox.ini we were using py3 but we were using versions of pylint tht did not support it
15:42:38 <mpeterson> yes
15:42:57 <yamahata> It's trivial patch, so we can review/merge it.
15:43:19 <mpeterson> yamahata: I did change it according to your comments
15:43:27 <yamahata> mpeterson: cool.
15:43:49 <mpeterson> there is a question whether we want to be fixed to a specific pylint version or we should use the newest one available
15:44:19 <mpeterson> test-requirements.txt was fixing it to a specific one and that created the "problem"
15:44:23 <yamahata> We can use latest one.
15:44:36 <yamahata> unless openstack has the upper bound.
15:44:46 <yamahata> I mean in requirements project.
15:45:13 <mpeterson> yamahata: no, they moved the requirements of linters to specific projects no longer according to that project
15:45:39 <mpeterson> https://bugs.launchpad.net/openstack-requirements/+bug/1696069/comments/3
15:45:44 <mpeterson> reference there ^^
15:47:18 * yamahata looking at it.
15:47:43 <yamahata> As project of networking-odl, there is no strict policy, but follow neutron policy or openstack one.
15:48:09 <yamahata> is there strong opinion?
15:48:36 <yamahata> In this specific case, we can just fix it somehow(fix .py or play with verions).
15:48:49 <mpeterson> I'm in favor of using most current as it will force us to maintain the code with a high score of compliance
15:49:44 <yamahata> I agree with you. In principle, the later version would be better.
15:50:55 <yamahata> we have 10mins left.
15:51:08 <yamahata> #topic open mike
15:51:13 <yamahata> rajivk: you're on stage.
15:51:17 <mkolesni> ive nothing to add
15:51:47 <rajivk> as per discussion, we have to move to l3 flavors.
15:52:32 <rajivk> yamahata, you mentioned there midonet was also moving to l3 flavor worked and then failed.
15:52:54 <yamahata> Right. they have experimental patch.
15:53:10 <yamahata> he wants to discuss on l3 flavor at the ptg.
15:53:23 <rajivk> yamahata, okay
15:53:34 <yamahata> In our case, we don't have any experimental patch yet.
15:53:58 <yamahata> It will make sense to write the first l3 flavor patch and see the outcome.
15:54:23 <mkolesni> sorry guys have to go
15:54:27 <mkolesni> have a nice day/evening
15:54:36 <yamahata> mkolesni: you too.
15:54:41 <rajivk> I don't have much knowledge about it, I will give a try and discuss if i face some problems.
15:55:08 <yamahata> Great!
15:55:10 <rajivk> yamahata, Do you want me to wait till PTG or should i start looking into it?
15:55:33 <yamahata> For now, we should focus on pike release.
15:56:03 <rajivk> hmm, i will give priority to discussed patches for now
15:56:13 <yamahata> Ideally we can have experimental l3 flavor for odl before the ptg.
15:56:30 <yamahata> so that we can have meaningful disucssion with other projects on l3 flavor.
15:57:11 <rajivk> yamahata, you wanna give a try for better discussion?
15:57:21 <yamahata> rajivk: please go ahead.
15:57:31 <rajivk> yamahata, thanks
15:58:02 <yamahata> anything else to discuss?
15:58:05 <rajivk> that's all from my side
15:58:07 <yamahata> we have 3mins left.
15:59:06 <yamahata> seems we're done.
15:59:09 <yamahata> thank you everyone.
15:59:18 <yamahata> #topic cookies
15:59:23 <yamahata> #endmeeting