Wednesday, 2015-07-29

RuiChenthank you, everybody, bye.00:00
*** pkoniszewski has quit IRC00:02
*** pkoniszewski has joined #openstack-meeting-300:05
*** ivar-lazzaro has joined #openstack-meeting-300:06
*** jasondotstar has quit IRC00:11
*** sridhar_ram has joined #openstack-meeting-300:14
*** tsandall has quit IRC00:16
*** jasondotstar has joined #openstack-meeting-300:17
*** isq_ has joined #openstack-meeting-300:20
*** isq has quit IRC00:20
*** Piet has quit IRC00:21
*** zhenzanz has quit IRC00:21
*** david-lyle has quit IRC00:24
*** veena has quit IRC00:29
*** shwetaap1 has quit IRC00:30
*** puranamr has joined #openstack-meeting-300:31
*** masahito has quit IRC00:33
*** mwagner_lap has joined #openstack-meeting-300:40
*** MarkAtwood has joined #openstack-meeting-300:40
*** tsandall has joined #openstack-meeting-300:40
*** tsandall has quit IRC00:41
*** MarkAtwood has quit IRC00:43
*** puranamr has quit IRC00:43
*** pkoniszewski has quit IRC00:43
*** FallenPegasus has joined #openstack-meeting-300:44
*** sridhar_ram has quit IRC00:46
*** sigmavirus24_awa is now known as sigmavirus2400:48
*** bpokorny has quit IRC00:50
*** pkoniszewski has joined #openstack-meeting-300:50
*** bpokorny has joined #openstack-meeting-300:51
*** tsandall has joined #openstack-meeting-300:54
*** bknudson has joined #openstack-meeting-300:54
*** bpokorny has quit IRC00:56
*** zhenguo has joined #openstack-meeting-300:57
*** ivar-laz_ has joined #openstack-meeting-300:58
*** ivar-lazzaro has quit IRC01:01
*** ivar-laz_ has quit IRC01:02
*** FallenPegasus has quit IRC01:09
*** FallenPegasus has joined #openstack-meeting-301:11
*** jasondotstar has quit IRC01:12
*** armax has joined #openstack-meeting-301:15
*** tsandall has quit IRC01:16
*** jasondotstar has joined #openstack-meeting-301:17
*** FallenPegasus has quit IRC01:19
*** salv-orlando has joined #openstack-meeting-301:20
*** FallenPegasus has joined #openstack-meeting-301:21
*** jasondotstar has quit IRC01:22
*** salv-orlando has quit IRC01:25
*** s3wong has quit IRC01:31
*** stanzgy has joined #openstack-meeting-301:38
*** lexholden has quit IRC01:43
*** yamamoto has joined #openstack-meeting-301:51
*** Guest30586 has quit IRC01:56
*** banix has joined #openstack-meeting-301:56
*** Brian has joined #openstack-meeting-302:08
*** Brian is now known as Guest6887402:08
*** tsandall has joined #openstack-meeting-302:11
*** Yingxin1 has left #openstack-meeting-302:12
*** shwetaap has joined #openstack-meeting-302:15
*** tsandall has quit IRC02:16
*** shwetaap has quit IRC02:17
*** david-lyle has joined #openstack-meeting-302:19
*** david-lyle has quit IRC02:23
*** shwetaap has joined #openstack-meeting-302:26
*** Piet has joined #openstack-meeting-302:26
*** bpokorny has joined #openstack-meeting-302:28
*** baoli has joined #openstack-meeting-302:35
*** armax has quit IRC02:41
*** banix has quit IRC02:48
*** baoli has quit IRC03:20
*** yamahata has joined #openstack-meeting-303:21
*** alexsyip has joined #openstack-meeting-303:25
*** coolsvap|away is now known as coolsvap03:26
*** david-lyle has joined #openstack-meeting-303:34
*** armax has joined #openstack-meeting-303:35
*** sulo has quit IRC03:39
*** bpokorny has quit IRC03:47
*** alexsyip has quit IRC03:47
*** amotoki has joined #openstack-meeting-303:56
*** kebray has joined #openstack-meeting-304:01
*** jhesketh has quit IRC04:01
*** jhesketh has joined #openstack-meeting-304:02
*** Guest68874 has quit IRC04:08
*** ramanjaneya_ has joined #openstack-meeting-304:09
*** vishwanathj has joined #openstack-meeting-304:10
*** sigmavirus24 is now known as sigmavirus24_awa04:14
*** FallenPegasus has quit IRC04:24
*** puranamr has joined #openstack-meeting-304:38
*** armax has quit IRC04:42
*** stevemar has joined #openstack-meeting-304:56
*** Brian has joined #openstack-meeting-305:01
*** Brian is now known as Guest7754805:01
*** etoews has quit IRC05:08
*** stevemar has quit IRC05:19
*** shwetaap has quit IRC05:19
*** stevemar has joined #openstack-meeting-305:20
*** stevemar has quit IRC05:24
*** kumar has joined #openstack-meeting-305:36
*** Guest77548 has quit IRC05:36
*** yamamoto has quit IRC05:50
*** puranamr has quit IRC05:51
*** Brian has joined #openstack-meeting-305:52
*** Brian is now known as Guest7090105:52
*** vgridnev has joined #openstack-meeting-305:54
*** yapeng has joined #openstack-meeting-305:59
*** vgridnev has quit IRC06:02
*** yapeng has quit IRC06:10
*** Guest70901 has quit IRC06:16
*** nkrinner has joined #openstack-meeting-306:18
*** yamamoto has joined #openstack-meeting-306:22
*** vgridnev has joined #openstack-meeting-306:31
*** zhenguo has quit IRC06:32
*** armax has joined #openstack-meeting-306:33
*** zhenguo has joined #openstack-meeting-306:40
*** vgridnev has quit IRC06:42
*** kfox1111_ has quit IRC06:47
*** sahid has joined #openstack-meeting-306:47
*** kebray has quit IRC06:51
*** ramanjaneya_ has quit IRC06:51
*** mshindo has quit IRC06:51
*** yamahata has quit IRC07:05
*** salv-orlando has joined #openstack-meeting-307:12
*** adam_g has quit IRC07:14
*** mshindo has joined #openstack-meeting-307:15
*** Brian has joined #openstack-meeting-307:16
*** Brian is now known as Guest5413807:17
*** Guest54138 has quit IRC07:21
*** nfedotov has joined #openstack-meeting-307:22
*** armax has quit IRC07:25
*** egallen has joined #openstack-meeting-307:28
*** kumar has quit IRC07:31
*** JeanBriceCombebi has joined #openstack-meeting-307:38
*** mshindo has quit IRC07:41
*** mshindo has joined #openstack-meeting-307:52
*** woodster_ has quit IRC07:54
*** mshindo_ has joined #openstack-meeting-307:55
*** mshindo has quit IRC07:59
*** natorious is now known as zz_natorious07:59
*** matrohon has joined #openstack-meeting-308:03
*** safchain has joined #openstack-meeting-308:08
*** Brian has joined #openstack-meeting-308:10
*** Brian is now known as Guest5988508:11
*** ^Gal^ has quit IRC08:23
*** ^Gal^ has joined #openstack-meeting-308:23
*** jasondotstar has joined #openstack-meeting-308:25
*** e0ne has joined #openstack-meeting-308:40
*** e0ne has quit IRC08:43
*** yushiro has joined #openstack-meeting-308:56
*** JeanBriceCombebi has quit IRC08:58
*** kzaitsev_mb has joined #openstack-meeting-308:58
*** vgridnev has joined #openstack-meeting-309:01
*** coolsvap is now known as coolsvap|away09:04
*** jtomasek has quit IRC09:05
*** amotoki has quit IRC09:05
*** jtomasek has joined #openstack-meeting-309:06
*** coolsvap|away is now known as coolsvap09:12
*** lexholden has joined #openstack-meeting-309:17
*** Guest59885 has quit IRC09:23
*** Brian has joined #openstack-meeting-309:23
*** alexpilotti has joined #openstack-meeting-309:24
*** Brian is now known as Guest8332809:24
*** yamamoto has quit IRC09:26
-openstackstatus- NOTICE: Currently our CI system is broken, jobs are not getting processed at all.09:28
*** ChanServ changes topic to "Currently our CI system is broken, jobs are not getting processed at all."09:29
*** yamamoto has joined #openstack-meeting-309:35
*** yuikotakada has joined #openstack-meeting-309:38
*** kzaitsev_mb has quit IRC09:40
*** kzaitsev_mb has joined #openstack-meeting-309:40
*** kzaitsev_mb has quit IRC09:45
*** sulo has joined #openstack-meeting-309:47
*** alex_xu has quit IRC09:48
*** alex_xu has joined #openstack-meeting-309:49
*** coolsvap is now known as coolsvap|away09:50
*** e0ne has joined #openstack-meeting-309:57
*** jasondotstar has quit IRC09:57
*** coolsvap|away is now known as coolsvap09:58
*** nfedotov has quit IRC10:00
*** jwang has quit IRC10:00
*** melwitt has quit IRC10:00
*** Caleb-- has quit IRC10:00
*** sc68cal has quit IRC10:00
*** melwitt has joined #openstack-meeting-310:00
*** jwang has joined #openstack-meeting-310:01
*** nfedotov has joined #openstack-meeting-310:01
*** sc68cal has joined #openstack-meeting-310:02
*** e0ne_ has joined #openstack-meeting-310:02
*** Caleb-- has joined #openstack-meeting-310:04
*** sahid_ has joined #openstack-meeting-310:05
*** sahid_ has quit IRC10:05
*** sahid has quit IRC10:05
*** e0ne has quit IRC10:05
*** Piet has quit IRC10:05
*** sahid_ has joined #openstack-meeting-310:05
*** e0ne_ is now known as e0ne10:06
*** sahid_ is now known as sahid10:06
*** yushiro has quit IRC10:09
*** jasondotstar has joined #openstack-meeting-310:09
*** yushiro has joined #openstack-meeting-310:09
*** mshindo_ has quit IRC10:10
*** mshindo has joined #openstack-meeting-310:10
*** zhenguo has quit IRC10:13
*** ^Gal^ has quit IRC10:19
*** ^Gal^ has joined #openstack-meeting-310:19
*** yushiro has quit IRC10:27
*** jpomeroy has quit IRC10:46
*** lexholden has quit IRC10:46
*** jpomeroy has joined #openstack-meeting-310:46
*** kzaitsev_mb has joined #openstack-meeting-310:48
*** stanzgy has quit IRC10:48
*** mrmartin has joined #openstack-meeting-310:50
*** coolsvap is now known as coolsvap|away10:55
*** yamamoto has quit IRC10:57
*** yamamoto has joined #openstack-meeting-310:59
*** Guest83328 has quit IRC11:07
*** jasondot_ has joined #openstack-meeting-311:23
*** baoli has joined #openstack-meeting-311:24
*** e0ne has quit IRC11:25
*** jasondotstar has quit IRC11:25
*** baoli has quit IRC11:31
*** belmoreira has joined #openstack-meeting-311:32
*** mwagner_lap has quit IRC11:35
*** e0ne has joined #openstack-meeting-311:35
*** sahid has quit IRC11:38
*** coolsvap|away is now known as coolsvap11:51
*** singlethink has joined #openstack-meeting-311:59
*** e0ne has quit IRC11:59
*** yamamoto has quit IRC12:02
*** Brian has joined #openstack-meeting-312:07
*** Brian is now known as Guest7207512:08
*** mshindo has quit IRC12:12
*** ramanjaneya_ has joined #openstack-meeting-312:12
*** Guest72075 has quit IRC12:13
*** woodster_ has joined #openstack-meeting-312:13
*** coolsvap is now known as coolsvap|away12:17
*** salv-orl_ has joined #openstack-meeting-312:22
*** salv-orlando has quit IRC12:25
*** e0ne has joined #openstack-meeting-312:25
*** salv-orlando has joined #openstack-meeting-312:26
*** salv-orl_ has quit IRC12:26
*** salv-orl_ has joined #openstack-meeting-312:27
*** salv-orlando has quit IRC12:30
*** JeanBriceCombebi has joined #openstack-meeting-312:32
*** mshindo has joined #openstack-meeting-312:33
*** salv-orlando has joined #openstack-meeting-312:35
*** singlethink has quit IRC12:36
*** salv-orl_ has quit IRC12:38
*** mshindo_ has joined #openstack-meeting-312:38
*** mshindo has quit IRC12:40
*** salv-orl_ has joined #openstack-meeting-312:44
*** salv-orlando has quit IRC12:47
*** VW_ has joined #openstack-meeting-312:47
*** salv-orl_ has quit IRC12:47
*** coolsvap|away is now known as coolsvap12:48
*** salv-orlando has joined #openstack-meeting-312:48
*** yamamoto has joined #openstack-meeting-312:49
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:50
-openstackstatus- NOTICE: zuul's disks were at capacity. Space has been freed up and jobs are being re-queued.12:50
*** VW_ has quit IRC12:52
*** baoli has joined #openstack-meeting-312:52
*** VW_ has joined #openstack-meeting-312:53
*** dims has quit IRC12:57
*** VW_ has quit IRC12:57
*** salv-orl_ has joined #openstack-meeting-312:57
*** dims has joined #openstack-meeting-312:57
*** salv-orlando has quit IRC13:00
*** salv-or__ has joined #openstack-meeting-313:00
*** bknudson has quit IRC13:01
*** jpomeroy has quit IRC13:03
*** salv-orl_ has quit IRC13:04
*** shwetaap has joined #openstack-meeting-313:06
*** shwetaap1 has joined #openstack-meeting-313:07
*** sigmavirus24_awa is now known as sigmavirus2413:08
*** salv-or__ has quit IRC13:09
*** salv-orlando has joined #openstack-meeting-313:11
*** shwetaap has quit IRC13:11
*** coolsvap is now known as coolsvap|away13:14
*** salv-orl_ has joined #openstack-meeting-313:14
*** bknudson has joined #openstack-meeting-313:16
*** sahid has joined #openstack-meeting-313:17
*** salv-orlando has quit IRC13:17
*** salv-orlando has joined #openstack-meeting-313:18
*** salv-orl_ has quit IRC13:21
*** JeanBriceCombebi has quit IRC13:21
*** JeanBriceCombebi has joined #openstack-meeting-313:22
*** jpomeroy has joined #openstack-meeting-313:23
*** VW_ has joined #openstack-meeting-313:23
*** neelashah has joined #openstack-meeting-313:24
*** singlethink has joined #openstack-meeting-313:24
-openstackstatus- NOTICE: zuul jobs after about 07:00 UTC may need a 'recheck' to enter the queue. Look if your change is in http://status.openstack.org/zuul/ and recheck if not.13:26
*** lexholden has joined #openstack-meeting-313:26
*** sahid has quit IRC13:28
*** sahid has joined #openstack-meeting-313:28
*** sahid has quit IRC13:28
*** sahid has joined #openstack-meeting-313:29
*** singleth_ has joined #openstack-meeting-313:29
*** yapeng has joined #openstack-meeting-313:30
*** singlethink has quit IRC13:31
*** mshindo_ has quit IRC13:33
*** stevemar has joined #openstack-meeting-313:34
*** epheo has joined #openstack-meeting-313:36
*** nelsnelson has joined #openstack-meeting-313:42
*** markvoelker has joined #openstack-meeting-313:44
*** singlethink has joined #openstack-meeting-313:47
*** sridhar_ram has joined #openstack-meeting-313:47
*** jasondotstar has joined #openstack-meeting-313:48
*** singleth_ has quit IRC13:50
*** salv-orlando has quit IRC13:52
*** jasondot_ has quit IRC13:52
*** moshele has joined #openstack-meeting-313:55
*** yamahata has joined #openstack-meeting-313:57
*** mwagner_lap has joined #openstack-meeting-313:58
*** jckasper has quit IRC13:58
*** neelashah1 has joined #openstack-meeting-313:58
*** singleth_ has joined #openstack-meeting-313:59
*** sfinucan has joined #openstack-meeting-313:59
*** neelashah has quit IRC13:59
*** gcossu has joined #openstack-meeting-314:01
*** jschwarz has joined #openstack-meeting-314:02
ramanjaneya_Hi14:02
*** jreeves has joined #openstack-meeting-314:02
*** singlethink has quit IRC14:02
moshelehi14:02
gcossuhi all14:03
sfinucanhey14:04
*** markvoelker has quit IRC14:04
jreevesHello14:04
ramanjaneya_Hi14:04
gcossuno qos meeting this week?14:06
*** ihrachyshka has joined #openstack-meeting-314:06
mosheleshould be we waiting to ihrachyshka14:07
ihrachyshkameh, sorry guys14:07
gcossuihrachyshka: hello14:07
*** jlibosva has joined #openstack-meeting-314:07
*** JeanBriceCombebi has quit IRC14:07
ihrachyshka #startmeeting neutron_qos14:07
ihrachyshka#startmeeting neutron_qos14:07
openstackMeeting started Wed Jul 29 14:07:30 2015 UTC and is due to finish in 60 minutes.  The chair is ihrachyshka. Information about MeetBot at http://wiki.debian.org/MeetBot.14:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:07
*** JeanBriceCombebi has joined #openstack-meeting-314:07
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:07
openstackThe meeting name has been set to 'neutron_qos'14:07
jschwarzhello ihrachyshka14:07
jlibosvahello jschwarz14:07
ihrachyshkaI'm really sorry for delay, we were in the middle of argument with jlibosva  :)14:07
jschwarzhello jlibosva ;p14:07
ihrachyshka#topic Announcements14:07
*** openstack changes topic to "Announcements (Meeting topic: neutron_qos)"14:07
ramanjaneya_Hi14:08
*** JeanBriceCombebi has quit IRC14:08
ihrachyshkaL2 is this week, and we were supposed to have something the week after it14:08
*** ybabenko has joined #openstack-meeting-314:08
ihrachyshkayesterday we talked with Kyle, and he thinks we should try to go before feature/pecan14:08
*** ybabenko has left #openstack-meeting-314:08
ihrachyshkaI hope we'll make it :)14:08
ihrachyshkaany other stuff to announce?14:09
*** JeanBriceCombebi has joined #openstack-meeting-314:09
ihrachyshkaok, I assume no :) moving on14:09
ihrachyshka#topic where we stand14:09
*** openstack changes topic to "where we stand (Meeting topic: neutron_qos)"14:09
ihrachyshkawe have API tests in gate - yay14:10
ihrachyshkawe have get_info in the tree - yay14:10
ihrachyshkaand we have ovs client tweaks from moshele in review: https://review.openstack.org/20652514:10
*** ddepaoli has joined #openstack-meeting-314:10
ihrachyshkathe missing parts: functional/fullstack tests (I believe jschwarz/ jlibosva were looking into it)14:11
mosheleihrachyshka: I upload new patch to resolve the minor comments14:11
ihrachyshka2. ajo's update notifications (he said he will update the patch today)14:11
jschwarzI'll might not have enough time to work on the functional, depending on whether I'm working next week or not...14:11
ihrachyshka3. client - I believe jschwarz works with ramanjaneya_ and others to make it happen14:11
ihrachyshkajschwarz, ack, we'll control the damage14:11
jlibosvaI'm looking in functional agent tests14:11
ihrachyshkajlibosva, great!14:11
ihrachyshkaand 4. <- always missing...14:12
ihrachyshkadevref14:12
mosheleihrachyshka: it the neutron client working with rules now ?14:12
ihrachyshkaplease start updating the devref file for qos with more details, we'll need them for review on merge-back14:12
jschwarzmoshele, I'm working on the neutronclient so hopefully we'll have something soon14:12
ihrachyshkajschwarz, ^^ is it?14:12
ihrachyshkayeah, jschwarz is quick, I believe we have it covered ;D14:12
jschwarzIf it will work, it'll work only with the post-#20705314:13
jschwarz:)14:13
ihrachyshkathere are some arguments around API. I believe it should have proper attention: https://review.openstack.org/20705314:13
jschwarzarguments?14:13
ihrachyshkajschwarz, it may be not easy to convince people to go that route at that point in time, so please share your concerns14:13
jschwarzmy concerns are that using URIs that are similar to14:14
jschwarz /qos/policies/%(policy)s/bandwidth_limit_rules/%s(rule)s14:14
jschwarzis a bit pointless, since most of the actions regarding bandwidth_limit_rules don't even need a policy_id14:14
ihrachyshkajschwarz, well, you still pass it in body14:15
jschwarzso updating a rule, deleting a rule, showing a rule, etc - we can do that using direct DB query that is independent of the policy_id14:15
jlibosvawhat is the benefit of such approach?14:15
jschwarzihrachyshka, yes. for example creating a new rule has to have a policy_id, so we pass it in the body of the request14:15
ihrachyshkajschwarz, if we stick to current approach, can we get it from URI instead?14:16
jlibosvaI propose to have rules as attributes of policies14:16
jschwarzjlibosva, the benefit is twofold: having the code easier to manage and having neutronclient code a lot (a lot!) easier to debug and write14:16
jschwarzihrachyshka, how do you mean?14:16
ihrachyshkajschwarz, well, you already get policy_id as an argument to qos service plugin endpoints, right?14:17
jschwarzyes14:17
ihrachyshkaI am with code simplicity, but jlibosva has concerns around rules that are in essence policy attributes be independent of it.14:17
jschwarzjlibosva, what kind of policy attributes are we talking about?14:18
ihrachyshkathat said, I agree it reflects what we do for e.g. subnets vs networks and don't mind14:18
ihrachyshkajschwarz, rules14:18
ihrachyshkajschwarz, each rule type is basically an attr on policy14:18
jlibosvaor maybe now I'm thinking about design - given that we used to have 'type' per rule, should we have a rules collection per policy?14:18
jschwarzoh yikes14:18
ihrachyshkajlibosva, I don't think we want to allow rules being written thru create on policies14:19
jlibosvajschwarz: well, there is obviously a 1:1 mapping between policy and rule collections14:19
jschwarzI think the problem with what Kuba is suggesting is that it doesn't allow a one-to-many mapping between rule to policies (ie. reusing rules)14:19
jschwarzlol14:19
jlibosvaihrachyshka: I agree on that, policies and rules should be separate objects14:19
jlibosvajschwarz: rules are quite small objects carrying just a piece of information. I mean, I don't know what the use case would be about assigning rule to a different policy ...14:20
ihrachyshkajschwarz, well, I am not against making it reusable, but ... not in this point in cycle :) I still feel bad I was not on design phase.14:21
*** markvoelker_ has joined #openstack-meeting-314:21
ihrachyshkajlibosva, well... for policy in policies: apply single rule? (that's assuming we allow reuse)14:22
ihrachyshkait may be allowed later14:22
jschwarzjlibosva, how about having a lot of networks, all with the same single rule? one might want to change that rule and have it affect all the networks in the tenant14:22
ihrachyshkawhile if we go with current approach, we are locked into subattrs14:22
jlibosvajschwarz: networks will have the same policy14:22
ihrachyshkajschwarz, it's not in spec, but I agree14:22
ihrachyshkajlibosva, well, ok, all policies14:22
jschwarzI think that whatever we choose, we must remember to look at the neutronclient before making the decision14:23
jlibosvaI think neutronclient should adopt server, not vice versa14:23
jschwarzneutronclient's code is very restrictive in that it expects paths and objects to be in a specific way and that's a main reason why 207053 was proposed.14:23
ihrachyshkajschwarz, you have an obvious benefit here since you actually looked14:23
jlibosvaihrachyshka: I don't get all policies - you mean having lots of policies all of them using single rules?14:24
jschwarzjlibosva, yes14:24
ihrachyshkado we have examples in other services where they embed objects?14:24
jschwarznot yet... maybe lbaasv2 does it with members?14:24
ihrachyshkajlibosva, yes, they may differ on some other rules but not that one14:24
jlibosvawell, if there is such use case then it makes sense. I thought that rule will have a single policy-id14:24
ihrachyshkajschwarz, I just wonder that if there is something there to steal, why can't we do it?14:24
jschwarzihrachyshka, who said we're not stealing? :)14:25
ihrachyshkajlibosva, atm it won't, but I think it's a reasonable move to allow it14:25
jlibosvajschwarz: lbaas does it with health-monitors14:25
*** absubram has joined #openstack-meeting-314:25
jlibosvaihrachyshka: then we should make the decision on what is expected14:25
jschwarzI looked for a bit and didn't see one case of a URI such as /qos/policies/%s/bw_limit_rules/%s14:25
jschwarzlb members for example looks like /lb/members14:25
ihrachyshkajschwarz, have you looked at health-monitors?14:26
jlibosvaif there will be mapping 1:N between policies and rules, makes sense. If 1:1, we should make it easier14:26
jschwarzlikewise lb healthmonitors looks like /lb/healthmonitors14:26
jschwarz#link https://github.com/openstack/python-neutronclient/blob/master/neutronclient/v2_0/client.py#L38314:26
ihrachyshkajlibosva, ^^ ?14:26
ramanjaneya_Rule and policy should be 1:1 mapping makes scene14:27
jschwarzalso: https://github.com/openstack/python-neutronclient/blob/master/neutronclient/v2_0/client.py#L37114:27
ddepaolithere's no qos branch for client?14:27
ihrachyshkaddepaoli, no, there is no branch for client14:27
jschwarzddepaoli, no, only 2 patches14:27
jlibosvaihrachyshka: jschwarz https://github.com/openstack/python-neutronclient/blob/master/neutronclient/v2_0/client.py#L38514:27
jschwarzjlibosva, yes, I just saw that...14:27
ihrachyshkait's to assoc monitors. is it the same as we need?14:28
jschwarzeither way it's one URI out of every other URIs14:28
jlibosvaI wasn't present on design phase so I don't know :) But we must be clear on the relation between rules and policies14:28
ihrachyshkawe currently talk about CRUD for rules, right?14:28
jschwarzihrachyshka, not only - based on that address we need to be able to also list, show, create, delete...14:28
ihrachyshkain design phase, it was told 1:N is YAGNI14:28
*** neelashah1 has quit IRC14:28
ihrachyshkaI don't think everyone understood it will complicate things14:29
*** yamamoto has quit IRC14:29
*** yamamoto has joined #openstack-meeting-314:29
ihrachyshkajschwarz, I mean, in that health-monitor example, the URI is used to attach monitors, not create them. for create, they have a root level obj.14:29
ihrachyshkathe way you suggest14:29
jschwarzyes14:30
ihrachyshka(unless I misunderstand the var names)14:30
jschwarzthat makes sense14:30
jlibosvabut that's because of 1:N mapping, right?14:30
ihrachyshkano idea :)14:30
jschwarzihrachyshka, jlibosva, either way you;ll see that in v2 they diverted from that14:31
ihrachyshkathere is also that one: https://github.com/openstack/python-neutronclient/blob/master/neutronclient/v2_0/client.py#L42414:31
ihrachyshkaweird one14:31
jschwarzmeaning they also decided it's a bad idea :)14:31
*** baoli has quit IRC14:31
jlibosvajschwarz: link? :)14:31
ihrachyshkahttps://github.com/openstack/python-neutronclient/blob/master/neutronclient/v2_0/client.py#L365 ?14:31
jschwarzjlibosva, https://github.com/openstack/python-neutronclient/blob/master/neutronclient/v2_0/client.py#L37214:31
*** baoli has joined #openstack-meeting-314:32
jschwarzoh, I now see that on line 374 they do have that heirarchy for /lbaas/pools/%s/members/%s14:32
jlibosvawell, that's a common thing in rest apis if you have multiple mappings14:32
jlibosvaI mean 1:N14:33
jschwarzthat whole 1:N isn't even written yet14:33
ihrachyshkajschwarz, how about we spend some time trying to mimic that? api change is not cheap14:34
*** JeanBriceCombebi has quit IRC14:34
jschwarzsure, i'll see about mimicing that14:34
*** JeanBriceCombebi has joined #openstack-meeting-314:34
jlibosvawhat's 'mimicing'?14:34
jschwarzjlibosva, fancy word for 'copy pasting'14:34
jschwarzXD14:34
ihrachyshkajschwarz, ok, thanks a lot. we'll have an option to fall back to your proposal if it does not fly. but we should try to avoid it.14:34
jlibosvaok :)14:34
jlibosvathat was for john's explanation on mimic^^14:35
jschwarzXD14:35
jlibosvaI would try to search for some design practices for rest api14:35
jlibosvathis seems like a common thing :-/14:35
ihrachyshkawe also have a patch for sriov, thanks to moshele https://review.openstack.org/20603814:35
ihrachyshkaplease review guys14:35
ihrachyshkaone more thing... I don't see Gal here. moshele do you by chance know whether someone works on non-native ovsdb qos interface?14:36
mosheleno14:36
ihrachyshkawe desperately need this one, since vsctl is the default14:36
*** coolsvap|away is now known as coolsvap14:37
jreevesI believe we can add it to our roadmap14:37
ihrachyshkajreeves, it should be before merge-back I suppose14:37
jreeves(we as in vhoward's team)14:37
ihrachyshkaso we are tight14:37
ihrachyshkajreeves, do you think it's realistic?14:37
*** yamamoto has quit IRC14:38
jreevesnot sure at this point. I'll have to check with the others14:38
jreevesVic is out today though14:38
ihrachyshkajreeves, thanks. please keep my in the loop.14:38
*** markvoelker_ has quit IRC14:38
jreevesok14:38
ihrachyshkaone more thing: I've cleaned up etherpad from some old/implemented stuff14:38
ihrachyshka#link https://etherpad.openstack.org/p/qos-sync14:38
ihrachyshkaplease make sure you maintain it in good shape :)14:39
*** markvoelker has joined #openstack-meeting-314:39
ihrachyshkajreeves, we also may need linuxbridge at least for API tests purposes. or we may change rule_types algorithm for ml214:39
ihrachyshkaok, anything more from you guys?14:40
jreevesI'll include that request too then14:40
ihrachyshkajreeves++14:40
jreevesbut I don't think we'll be that ambitious lol14:40
ihrachyshkaheh14:40
ihrachyshkawell, we have a fallback plan for lb14:40
ihrachyshkaah forgot to mention, ajo will be back on Mon :)14:41
ihrachyshkaok, I guess we may use remaining 20 mins for code, reviews and what not14:41
*** yamahata has quit IRC14:41
ihrachyshka#endmeeting14:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:41
openstackMeeting ended Wed Jul 29 14:41:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-07-29-14.07.html14:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-07-29-14.07.txt14:41
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-07-29-14.07.log.html14:41
*** yapeng has quit IRC14:41
jlibosvathanks, bye o/14:42
*** jlibosva has left #openstack-meeting-314:42
ihrachyshkao/14:42
ddepaoliis it possible to test it with devstack?14:43
*** moshele has left #openstack-meeting-314:43
ddepaolior too early?14:43
*** jreeves has quit IRC14:44
*** jreeves has joined #openstack-meeting-314:44
*** mshindo has joined #openstack-meeting-314:44
jschwarzihrachyshka, ^ see ddepaoli's question14:46
ihrachyshkaddepaoli, let's move to #openstack-neutron14:46
*** markvoelker has quit IRC14:47
*** markvoelker has joined #openstack-meeting-314:47
gcossuI'm interested too :)14:48
*** sfinucan has quit IRC14:49
*** FallenPegasus has joined #openstack-meeting-314:50
*** yamamoto has joined #openstack-meeting-314:54
*** sridhar_ram has quit IRC14:55
*** absubram has quit IRC14:55
*** neelashah has joined #openstack-meeting-314:56
*** kebray has joined #openstack-meeting-314:56
*** belmoreira has quit IRC14:59
*** absubram has joined #openstack-meeting-314:59
*** jasondotstar has quit IRC14:59
*** bryan_att has joined #openstack-meeting-314:59
*** yuikotak_ has joined #openstack-meeting-315:01
*** e0ne has quit IRC15:02
*** sweston has quit IRC15:02
*** dougwig has quit IRC15:02
*** bryan_att has quit IRC15:02
*** mestery has joined #openstack-meeting-315:02
*** carl_baldwin has joined #openstack-meeting-315:02
*** yuikotakada has quit IRC15:03
*** e0ne has joined #openstack-meeting-315:04
*** nkrinner has quit IRC15:05
*** nfedotov has quit IRC15:10
*** jckasper has joined #openstack-meeting-315:15
*** lblanchard has joined #openstack-meeting-315:16
*** gcossu has quit IRC15:16
*** carl_baldwin has quit IRC15:18
*** carl_baldwin has joined #openstack-meeting-315:19
*** iymht has joined #openstack-meeting-315:20
*** carl_baldwin has quit IRC15:23
*** ddepaoli has quit IRC15:25
*** vgridnev has quit IRC15:26
*** bpokorny has joined #openstack-meeting-315:28
*** baoli has quit IRC15:31
*** banix has joined #openstack-meeting-315:31
*** btully has quit IRC15:34
*** btully has joined #openstack-meeting-315:34
*** alexpilotti has quit IRC15:34
*** baoli has joined #openstack-meeting-315:39
*** gabriel-bezerra has quit IRC15:39
*** vishwanathj has quit IRC15:41
*** JeanBriceCombebi has quit IRC15:44
*** kebray has quit IRC15:44
*** tsandall has joined #openstack-meeting-315:45
*** devvesa has joined #openstack-meeting-315:45
*** JeanBriceCombebi has joined #openstack-meeting-315:45
*** tsandall has quit IRC15:46
*** tsandall has joined #openstack-meeting-315:46
*** Sukhdev_ has joined #openstack-meeting-315:47
*** rhagarty_ has quit IRC15:48
*** rhagarty has quit IRC15:48
*** matrohon has quit IRC15:58
*** rhagarty has joined #openstack-meeting-315:58
*** rhagarty_ has joined #openstack-meeting-315:58
*** iymht has quit IRC16:00
*** gabriel-bezerra has joined #openstack-meeting-316:01
*** baoli has quit IRC16:01
*** baoli_ has joined #openstack-meeting-316:03
*** cbouch has joined #openstack-meeting-316:06
*** sdake has joined #openstack-meeting-316:09
*** ihrachyshka has quit IRC16:09
*** bryan_att has joined #openstack-meeting-316:11
*** jaypipes has joined #openstack-meeting-316:12
*** coolsvap is now known as coolsvap|away16:12
*** kebray has joined #openstack-meeting-316:13
*** puranamr has joined #openstack-meeting-316:13
*** ctracey has quit IRC16:13
*** skath has quit IRC16:13
*** briancurtin has quit IRC16:13
*** zhiyan has quit IRC16:13
*** davidmichaelkarr has quit IRC16:13
*** ameade has quit IRC16:13
*** jraim has quit IRC16:13
*** sballe has quit IRC16:13
*** devvesa has quit IRC16:13
*** Piet has joined #openstack-meeting-316:13
*** FallenPegasus has quit IRC16:15
*** david-lyle has quit IRC16:18
*** lsmola has quit IRC16:20
*** belmoreira has joined #openstack-meeting-316:23
*** ivar-lazzaro has joined #openstack-meeting-316:23
*** annp has joined #openstack-meeting-316:24
*** jraim has joined #openstack-meeting-316:26
*** dougwig has joined #openstack-meeting-316:29
*** carl_baldwin has joined #openstack-meeting-316:31
*** sweston has joined #openstack-meeting-316:33
*** sdake has quit IRC16:37
*** ctracey has joined #openstack-meeting-316:37
*** coolsvap|away is now known as coolsvap16:39
*** sahid has quit IRC16:41
*** david-lyle has joined #openstack-meeting-316:42
*** ameade has joined #openstack-meeting-316:43
*** alexpilotti has joined #openstack-meeting-316:46
*** zhiyan has joined #openstack-meeting-316:46
*** skath has joined #openstack-meeting-316:46
*** baoli_ has quit IRC16:48
*** JeanBriceCombebi has quit IRC16:48
*** carl_baldwin has quit IRC16:49
*** baoli_ has joined #openstack-meeting-316:49
*** zz_natorious is now known as natorious16:49
*** sballe has joined #openstack-meeting-316:50
*** vineetmenon has joined #openstack-meeting-316:52
*** sdake has joined #openstack-meeting-316:53
*** briancurtin has joined #openstack-meeting-316:57
*** coolsvap is now known as coolsvap|away16:58
*** coolsvap|away is now known as coolsvap16:58
*** alazarev has quit IRC16:58
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Jul 29 17:00:09 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
alaskianyone here today?17:00
vineetmenono/17:00
melwitto/17:00
belmoreirao/17:01
bauzas_o17:01
bauzas\o even17:01
alaskigreat17:01
alaski#topic Tempest testing17:01
*** openstack changes topic to "Tempest testing (Meeting topic: nova_cells)"17:01
alaskimelwitt: anything to report?17:02
melwittalaski: no, don't think so17:02
*** jreeves has quit IRC17:02
bauzaswe had some problems with the devstack install last night17:02
bauzas(not speaking of tempest)17:02
bauzasuh, last night EU time17:02
alaskiwhat sort of problems?17:03
bauzasalaski: sec, giving the URL17:03
*** e0ne has quit IRC17:03
bauzasalaski: nothing related to cells, rather timeouts AFAICS17:03
*** davidmichaelkarr has joined #openstack-meeting-317:03
bauzasanyway, that's the only issue I spotted this week17:03
*** kumar has joined #openstack-meeting-317:04
bauzashttp://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiZXhpdCBjb2RlOiAxMzdcIiBBTkQgdGFnczpcImNvbnNvbGVcIiBBTkQgYnVpbGRfbmFtZTpcImdhdGUtZGV2c3RhY2stZHN2bS1jZWxsc1wiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI4NjQwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzgxODk0NTcwMzd917:04
bauzasbut we can move on17:04
alaskiokay.  yeah, if not directly cells related17:04
alaskimelwitt: thanks for the update, glad it's good17:05
alaski#topic Open discussion17:05
*** openstack changes topic to "Open discussion (Meeting topic: nova_cells)"17:05
alaskijust to update everyone, on my end I'm digging into the request spec stuff17:05
alaskiI reworked my patch series to split it along different lines which took a bit, and bauzas reworking things hasn't helped :)17:06
*** lalit_ has joined #openstack-meeting-317:06
alaskiworking on testing now and then I shoudl get some stuff up17:06
belmoreirathanks for the reviews on https://review.openstack.org/#/c/201606/17:06
bauzasalaski: yeah, sorry about that, but I had some good reviews :)17:06
melwittcool17:06
bauzasalaski: so I had to work on some new PSs17:06
*** cbouch has quit IRC17:06
bauzasalaski: that's the main problem when you have long series :)17:07
alaskibelmoreira: np17:07
*** alazarev has joined #openstack-meeting-317:07
alaskibauzas: yeah, definitely understand.  just makes my job harder :)17:07
belmoreiraalaski: I have been travelling but should be good to continue the work now17:07
bauzasalaski: eh eh, someone said in the midcycle that he was not happy with some SchedulerHints object so I had to rebase my whole series :p17:08
alaskibelmoreira: great. that will be helpful17:08
*** natorious is now known as zz_natorious17:08
alaskibauzas: I wouldn't listen to that guy17:08
alaskithat does simplify things a bit though, so it's actually good17:09
bauzasno worries :)17:09
alaskianyone else have a topic today?17:10
alaskiuntil the summit we're likely to have a light agenda of just updates in this meeting17:10
bauzasnothing apart saying I should be off for the next 2 weeks17:10
alaskiagain? :)17:10
belmoreiraI have a question17:10
bauzasI'm French, remember ? :)17:10
belmoreirawe are populating instance_types with default flavors17:11
*** jschwarz has quit IRC17:11
bauzasbelmoreira: in https://review.openstack.org/#/c/201606/ ?17:11
alaskioh, right.  that's a terrible bit of code somewhere17:11
belmoreirashould we continue with this in flavors table?17:11
belmoreirabauzas: is not there17:12
alaskibelmoreira: I would like to say no.  it's a bad thing we do currently and we should stop.  but I don't know all the implications of that so we should probably bring this up at the nova meeting17:12
bauzasbelmoreira: alaski: oh ok, any code I could look at ?17:12
bauzasoh, you mean when instanciating the instance_types table?17:13
alaskibauzas: I think it's in the 216_havana.py migration17:13
bauzasisn't that a devstack-ish thing ?17:13
belmoreiraI would be surprised if people are relying in those flavors17:13
bauzasoh right17:13
bauzasalaski: yep _populate_instance_types in 216_havana.py, correct17:14
alaskibelmoreira: me too.  but I'm often suprised17:14
*** salv-orlando has joined #openstack-meeting-317:14
bauzaswell, small clouds do17:14
melwittmigration adds some flavors? that seems odd17:14
bauzasas an operator, I was relying on those :)17:14
*** alexpilotti has quit IRC17:14
bauzasmelwitt: yeah, was thinking it was devstack or something else17:14
alaskimelwitt: exactly.  we bootstrap nova with some flavors17:15
*** cbouch has joined #openstack-meeting-317:15
*** FallenPegasus has joined #openstack-meeting-317:15
melwittbauzas: yeah, I thought the same until alaski said it17:15
alaskibauzas: devstack would be the right place to do it, or maybe a nova-manage command though I don't really like that17:15
bauzasalaski: devstack and/or package vendors17:15
alaskiit feels like something we should just document, "add these flavors to get started"17:15
*** FallenPe_ has joined #openstack-meeting-317:16
bauzasthat's just what we do for all the other data :)17:16
belmoreiraalaski: +117:16
* bauzas remembers the early ages of deploying Diablo's debs :)17:16
vineetmenonalaski: +!17:16
melwittalaski: yeah, nova-manage would have been as invasive as I'd think to go17:16
bauzasmelwitt: I would -1 a nova-manage hydrate-flavors17:17
bauzasnova-manage is for providing something we can't do or won't do at the REST API level - very specific operations17:17
alaskiokay, I'll add this to the nova meeting agenda and we can discuss it there.  might need a ML post as well17:17
bauzasI'd be surprised that operators would know about that - I would even bet that 99% of them think it's devstack17:18
*** ajmiller has quit IRC17:18
*** ajmiller has joined #openstack-meeting-317:19
*** kumar has quit IRC17:19
alaskiit also probably means that we(rax) have some code to strip those out when we bootstrap a new cell somewhere17:19
*** FallenPegasus has quit IRC17:19
belmoreirabauzas: not sure... because is what they get in the DB when setup a cloud17:19
*** salv-orlando has quit IRC17:20
belmoreiraat CERN they are available :) ...legacy17:20
melwittyeah, we don't use those canned flavors either so I guess we must delete them as part of the deployment automation17:21
belmoreirabut we repopulate the tables with our flavors...17:21
alaskithis would be a great chance to fix this17:22
alaskiany other topics today?17:22
*** salv-orlando has joined #openstack-meeting-317:22
alaskioh, I have a question.  since the meeting is going to be light until around the summit does it still feel useful to do weekly right now?17:23
alaskiI'm happy to continue doing it17:23
alaskibut don't want to waste peoples time17:23
melwittI'm cool with it not being weekly, but either way is fine17:23
*** alexpilotti has joined #openstack-meeting-317:23
alaskibauzas: belmoreira any thoughts?17:25
alaskiotherwise melwitts one vote wins :)17:25
bauzasmeh17:25
vineetmenon-_-17:25
belmoreiraI may have some questions with flavors spec but I can ping you when needed17:25
bauzasthe 1700UTC is just family business17:25
bauzasso I'd be happy to drop that one17:25
bauzasunless urgent queries17:25
alaskivineetmenon: you get a vote as well :)17:26
alaskibelmoreira: that works17:26
alaskihow about we meet next week and if there's no resistance we'll alternate from then until summit17:26
alaskiand drop the 1700 for now17:26
vineetmenon1100UTC is too late for us in India.. but I don't want to disturb your family time.17:27
bauzasvineetmenon: that's not really a PITA for me, just a matter of arranging my stuff :)17:27
belmoreirayeah, Vineet and Dheeraj connect from India17:27
vineetmenonI'll read meeting log, meanwhile17:27
*** kzaitsev_mb has quit IRC17:27
alaskiwe can drop either one, I just went with 1700 since bauzas spoke up17:28
bauzasdon't really look at me17:29
vineetmenonbauzas: :)17:29
bauzasif vineetmenon can't handle the 2100 one, I'm okay with keeping the 1700 one17:29
vineetmenonI would prefer 1700, tbh.17:29
alaskiokay.  How about we reconvene in two weeks at this time?17:29
bauzasI can hassle alaski anytime17:29
vineetmenon2300UTC == 0230 IST, so it becomes terrible17:29
alaskibauzas and I overlap quite a bit anyways17:30
*** sridhar_ram has joined #openstack-meeting-317:30
alaski#info Meeting will be held every two weeks at 1700 until summit17:30
melwittcool17:31
alaskishould have include a timezone :(17:31
*** ramanjaneya_ has quit IRC17:31
melwittyou can do a #undo and do it again17:31
melwittI think17:31
alaski#undo17:31
openstackRemoving item from minutes: <ircmeeting.items.Info object at 0xa799a10>17:31
alaski#info Meeting will be held every two weeks at 1700UTC until summit17:31
alaskimelwitt: thanks17:31
vineetmenoncool17:31
alaskianything else for today?17:31
alaskigreat.  thanks everyone!17:32
alaskiI will go continue to chase bauzas patch series now17:32
alaski#endmeeting17:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:32
openstackMeeting ended Wed Jul 29 17:32:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:32
vineetmenonbye17:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-07-29-17.00.html17:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-07-29-17.00.txt17:32
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-07-29-17.00.log.html17:32
*** lalit_ has quit IRC17:36
*** armax has joined #openstack-meeting-317:36
*** FallenPe_ has quit IRC17:39
*** rhagarty_ has quit IRC17:39
*** rhagarty has quit IRC17:39
*** jaypipes has quit IRC17:40
*** lblanchard has quit IRC17:40
*** vineetmenon has quit IRC17:40
*** rhagarty has joined #openstack-meeting-317:42
*** rhagarty_ has joined #openstack-meeting-317:42
*** Sukhdev_ has quit IRC17:47
*** puranamr has quit IRC17:52
*** puranamr has joined #openstack-meeting-317:54
*** jasondotstar has joined #openstack-meeting-317:54
*** e0ne has joined #openstack-meeting-317:56
*** s3wong has joined #openstack-meeting-317:57
*** mickeys has joined #openstack-meeting-318:01
*** e0ne has quit IRC18:06
*** e0ne has joined #openstack-meeting-318:09
*** hoangcx has joined #openstack-meeting-318:14
*** madhu_ak has joined #openstack-meeting-318:16
*** FallenPegasus has joined #openstack-meeting-318:16
*** coolsvap is now known as coolsvap|brb18:18
*** sridhar_ram has quit IRC18:20
*** jasondotstar has quit IRC18:23
*** SridarK has joined #openstack-meeting-318:24
*** dims_ has joined #openstack-meeting-318:24
*** lblanchard has joined #openstack-meeting-318:27
*** dims has quit IRC18:28
*** jwarendt has joined #openstack-meeting-318:29
*** badveli has joined #openstack-meeting-318:31
SridarKHi FWaaS folks18:31
xgermanHi18:31
annpHi18:31
jwarendtHi18:31
badvelihello all18:31
*** pc_m has joined #openstack-meeting-318:31
madhu_akhi18:31
hoangcxHi18:31
SridarKok lets get started18:31
* pc_m lurking...someone has to keep an eye on you guys! :)18:31
SridarKpc_m: :-) always welcome18:32
SridarK#startmeeting Networking FWaaS18:32
openstackMeeting started Wed Jul 29 18:32:20 2015 UTC and is due to finish in 60 minutes.  The chair is SridarK. Information about MeetBot at http://wiki.debian.org/MeetBot.18:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:32
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:32
openstackThe meeting name has been set to 'networking_fwaas'18:32
SridarK#topic Bugs18:32
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:32
*** armax has quit IRC18:32
SridarKfrom last week:18:32
SridarKor rather last mtg18:33
SridarK#link https://bugs.launchpad.net/neutron/+bug/147427918:33
openstackLaunchpad bug 1474279 in neutron "FWaaS let connection opened if delete allow rule, beacuse of conntrack" [Undecided,Incomplete]18:33
SridarKthis may be a non issue and could be related to the conn track - thanks to Elena for following up on this18:33
SridarKnew:18:33
SridarK#link https://bugs.launchpad.net/neutron/+bug/147709718:33
openstackLaunchpad bug 1477097 in neutron "fwaas: firewall in error status after update firewall-rule " [Undecided,New] - Assigned to Sridar Kandaswamy (skandasw)18:33
*** jaypipes has joined #openstack-meeting-318:34
SridarKi just assigned it to myself for a quick eval - i think we have fixed some code around here - so lets see18:34
SridarKanything else noteworthy that others might be aware of18:35
SridarK?18:35
SridarKbadveli: did u find anything else as u were checking ?18:35
badvelinothing much but should we see the linkhttps://bugs.launchpad.net/openstack/+bugs?field.searchtext=fwaas&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_p18:36
badvelisridar some of them are low priority18:36
SridarKbadveli: yes those are fine and some are not directly related18:36
SridarKbadveli: so if u have nothing more that u have seen to raise concern we can move on18:37
*** safchain has quit IRC18:37
badvelifine sridark18:37
SridarK#topic Service Objects/Group18:37
*** openstack changes topic to "Service Objects/Group (Meeting topic: Networking FWaaS)"18:37
SridarKbadveli: things u would like to bring up, update or discuss18:38
badveliyes i am facing an issue with my patches18:38
badvelimailed pc_m18:38
badvelifor some reason when i added the service group extension18:38
badvelithe unit tests are failing because of18:38
pc_mbadveli: So that today (back from PTO), wasn't sure what it was about.18:38
badveliraise webob.exc.HTTPClientError(code=res.status_int)      webob.exc.HTTPClientError: The server could not comply with the request since it is either malformed or otherwise incorrect.18:39
badvelii am getting this while running my unit tests18:39
pc_mbadveli: Is there a patch up for review?18:39
SridarKbadveli: but are u able to manually exercise ur extension ?18:39
badveliyes but because of this issue its not proper18:39
*** vishwanathj_ has joined #openstack-meeting-318:39
badvelisridark did not get your point, are you asking i am able to see the extension in neutron via cli?18:40
*** salv-orlando has quit IRC18:40
badvelipreviously this code used to work18:40
badvelii am trying to check what is the correct way to write an extension18:40
SridarKbadveli: no are u able to send a REST command to see if the server is picking it up and ur extension is picking it up18:41
badvelilooks like this is the way from the existing examples18:41
SridarKbadveli: u can also look at the router extension work in Kilo for a sample - i can help u as well18:42
badvelisridark did not check that but as far i think18:42
badveliget_resources,get_extended_resources18:42
*** vishwanathj has joined #openstack-meeting-318:42
badveli should do that, thanks sridark18:42
SridarKbadveli: i was trying to ascertain if the issue is only on UT or u have a problem even when u are testing it manually ?18:42
badvelifine sridark did not had much time to spend, i will check that and mail18:43
SridarKbadveli: sounds good18:43
*** sdake has quit IRC18:43
badvelithanks sridark, some thing has changed in kilo looks like the previous code is not working any more18:44
*** bharath_ has joined #openstack-meeting-318:45
SridarKbadveli: hmm! okay we can discuss offline then ?18:45
badveli  yes, thanks18:45
SridarKok np18:45
SridarK#topic Logging Spec18:46
*** openstack changes topic to "Logging Spec (Meeting topic: Networking FWaaS)"18:46
SridarK#link https://review.openstack.org/#/c/132133/18:46
*** sdake has joined #openstack-meeting-318:46
hoangcxHi SridarK and all18:46
SridarK#link https://bugs.launchpad.net/neutron/+bug/146836618:46
openstackLaunchpad bug 1468366 in neutron "RFE - Packet logging API for Neutron" [Undecided,Confirmed] - Assigned to Yushiro FURUKAWA (y-furukawa-2)18:46
SridarKhoangcx: hi18:46
hoangcxFWaas logging is still discussing at packet-logger API spec as the following #link https://review.openstack.org/#/c/203509/18:46
SridarKok18:46
*** vishwanathj has quit IRC18:46
hoangcxPlease help us to review packet-logger spec.18:47
xgerman#action review https://review.openstack.org/#/c/203509/18:47
SridarKhoangcx: yushiro is not here today, there was query on the older spec - perhaps one of u should respond that u have moved to bug with rfe18:48
hoangcxxgerman: Thanks a lot18:48
jwarendtThanks for pointing out.18:48
SridarKthanks hoangcx: will do so18:48
hoangcxSridarK: ah, I see.18:48
SridarKhoangcx: anything else u want to bring up18:49
hoangcxThat's all for me. and waiting review18:50
SridarKhoangcx: ok thanks for the update18:50
SridarK#topic SG - FWaaS alignment18:50
*** openstack changes topic to "SG - FWaaS alignment (Meeting topic: Networking FWaaS)"18:50
SridarK#link https://etherpad.openstack.org/p/fwaas_use_cases18:50
xgerman#link https://trello.com/b/TIWf4dBJ/fwaas-usecase-categorization18:51
SridarK#link https://etherpad.openstack.org/p/fwaas-api-evolution-spec18:51
xgermanwe moved the use cases int eh troll board and sorted them18:51
SridarKover to xgerman:18:51
xgermanok, so at the L4-L7 mid cycle we moved all the use cases into the troll board (linked)18:51
SridarKfirstly a huge thanks to xgerman: and sc68cal:  for all the inputs here18:51
SridarKxgerman: that was the next link - u beat me to it :-)18:52
xgerman:-)18:52
SridarKpls go ahead all yours18:52
jwarendtPlease correct any obvious mistakes if you see them...18:52
xgerman+118:52
SridarKjwarendt: no thanks to u as well - i saw ur updates as well18:52
sballexgerman: wasn't the next step to look at the existing APIs and see what is missing and if we can even reuse them18:52
xgermanyep18:53
SridarKi felt this was great first step18:53
SridarKsballe: agree on this18:53
sballeWe have the use cases and then we now need to do a deep dive on the APIs and see where we go from tehre18:53
xgerman+118:53
SridarKIn looking at the Gaps column - there were a few things which i believe can be addressed in a prioritized manner18:54
sballeWhat is a good way to move forward from tehre?18:54
sballeSridarK: I agree18:54
xgerman+118:54
SridarKand over all i am in total agreement in ur categorization of the buckets18:54
sballecool!18:54
xgermangreat!18:54
SridarKclearly things like DPI are all great but for the future18:54
badvelixgerman trying to see why we have two columns covered by sg and fwaas18:54
*** Sukhdev_ has joined #openstack-meeting-318:55
mickeysI agree with most of the categorization, but I do have some comments. I could not add myself to the Trello board, looks like people need to be added manually by people with permission. Then I will be able to comment in Trello.18:55
xgermanwhat’s your e-mail and then I can add you18:56
sballebadveli Wen we did it it was because we wanted to see what SG covered and what FW covered. Does that answer the quesiton18:56
vishwanathj_xgerman: please add mine as well vishwanathj@hotmail.com18:56
mickeysemspiege@us.ibm.com18:56
badvelithanks sballe but putting two things one working at port level18:57
badveliand the other one fwaas18:57
SridarKAs distilled one line summary - i saw these as a priority: Notion of direction (for outbound reputation), Hit Counters, Audit logs, Point of application (different rules to different ports), Notion of Zones18:57
sballeWe did it this way because we wanted to see where the overlap18:57
mickeysIf we go for a common superset API, then all of the SG covered items need to be covered by the enhanced FWaaS API18:57
*** yanping has joined #openstack-meeting-318:57
xgermanbedevil let's not get too involved into technical details18:57
sballemickeys: That was our thoughts too18:58
xgermanwe were just looking at use cases not bow they are implemented18:58
badvelii think both can cover different use cases18:58
badveliok thanks18:58
xgermanmickeys we were thinking less about a superset API but more of both APIs sharing a common backend18:59
*** kebray has quit IRC18:59
mickeysSridar: A big one for me is the ability to refer to a group of addresses or ports, as security groups do today through remote security group18:59
*** tqtran has joined #openstack-meeting-319:00
mickeysIf not a superset API, then are we talking about a new security group API in addition to the existing one? So that we can extend and add functionality?19:00
SridarKmickeys: yes i believe i had that on my next list (from the SG + FWaaS column) - and i agree19:00
badvelithanks mickeys  initially  we wanted to introduce service groups and then address groups19:01
mickeysbadveli: No argument with service groups, just saying we need the other one as well19:01
SridarKmickeys: can we may be go thru the feature list first and then we can discuss the API coexistence or we can do that first19:01
*** salv-orlando has joined #openstack-meeting-319:01
xgermanI think we should make the backends be the same19:02
mickeysSridar: Just wondering what our context is, one superset API or separate APIs. If that is still open, fine as long as we are all on the same page19:02
SridarKmickeys: yes so lets get the feedback out on the coexistence first19:02
sballeI agree with xgerman. To me the SG is there to have compatiblity with AWS.19:03
sballeso we need to mkae sure SG API stay compatible19:03
SridarKsballe: , xgerman: did u get that kind of consensus in the mid cycle ?19:03
sballeor close to the same19:03
mickeyssballe: Many of us want SG functionality with extensions/enhancements. We need a way forward with that, whether that is an additional SG API or an enhanced superset FWaaS API.19:03
xgermanyes, it’s difficult to replace SG since they are a “stable” API19:03
mickeysIn addition to the existing SG API which remains for AWS compatibility19:03
sballeAgreed. I personally like an enhanced superset FWaaS API.19:04
jwarendt+119:04
SridarKsballe: +119:04
xgerman+119:04
mickeys+119:04
sballecool! we are all in agreement :-)19:04
SridarKsballe: but was that the direction at the mid cycle as well ?19:04
*** krtaylor has quit IRC19:04
xgermanyes, we also entertained minor enhancements to SG but the bulk should be in FWaaS19:05
xgermanbig consensus was to use the same backend19:05
badvelithe superset fwaas API will most likely cover the use case19:05
sballesorry I am back...19:05
SridarKxgerman: on the backend that totally makes sense19:05
badvelithat are not part of SG19:05
sballeyes as xgerman said above19:06
SridarKthis is good that we have approaching some consensus on the API relationship19:06
SridarK*are19:06
badvelithe reason i am trying to say is because of the implementation issues we might not be able to extend the existing SG19:07
SridarKmy personal take also was that the AWS compat was a big issue that is important from a deployer perspective19:07
badveliand mostly we can use the superset fwaas API for most of the use cases on the etherpad19:07
sballeSridarK: +119:08
xgermanwell, there might be use cases which only make sense for SG...19:08
sballe+119:08
mickeysxgerman: Depending on how we enhance the FWaaS API, we may be able to cover most of the SG use cases. I hope that is feasible, but we need to flesh that out to be sure.19:08
jwarendtBut should still share backend mechanisms even if SG unique use case if possible.19:09
sballemickeys: I agree and I feel we need to start the investigation19:09
SridarKmickeys: would those mostly involve on where the rules are applied ?19:09
mickeysYes, if we can associate a firewall or firewall policy with a security group19:10
mickeysAlso the remote stuff that I mentioned earlier19:10
*** coolsvap|brb is now known as coolsvap|away19:10
*** Piet has quit IRC19:10
mickeysWhether that is the same notion of security group is a major question that we may need to think about19:10
SridarKmickeys: okay but what if we can associate a FW at VM port level ?19:11
badvelisridark since the SG applies at port level19:11
SridarKbadveli: yes19:11
mickeysSridar: That is useful as well, and I would like all of that to be in the same API, but that is not SG functionality.19:11
xgermanwell, we should make that a use case if that is needed19:11
mickeysI asked for ports and for groups, and I believe that is mostly captured in Trello. There was one requirement I had that was left out, probably needs clarification.19:12
*** geoffarnold has joined #openstack-meeting-319:12
badveliSridark when we tie up to the port level we might be in a difficult situation if we need to provide more use cases19:13
*** kebray has joined #openstack-meeting-319:14
SridarKbadveli: the port (VM port) is a SG thing for sure19:14
mickeysTying to port level would not be mandatory, it would be an option, up to the user. Where this gets tricky is if a customer specifies multiple overlapping policies with different associations.19:14
xgermanyep, we talked about hsoe validations and how we should delegate them to the appliance19:15
mickeysCan a customer define one firewall or policy at tenant granularity, and another associated with a port?19:15
badveliyes19:15
badveliit is very tricky19:16
SridarKmickeys: in theory yes, but at this point the association is only with router(s)19:16
xgermanhence, my handwaving19:16
*** davidmichaelkarr has quit IRC19:17
SridarKThe first step may be even at the router i/f level (so different networks can get diff FW associations)19:17
badvelimickeys what is the benefit of tie the policy to a port19:17
SridarKnow if we should get to the VM port level - that is open19:17
*** krtaylor has joined #openstack-meeting-319:17
*** VW__ has joined #openstack-meeting-319:18
*** kebray_ has joined #openstack-meeting-319:18
SridarKmickeys: i think there is value in not having to replicate rules sets across SG and FW19:18
jwarendt.+119:18
sballeSridarK: +119:18
mickeysThis all ties into the operator versus user (application deployer) aspect in the use cases. If we allow different types of associations that may overlap in arbitrary ways, then the distinction between what an operator wants and what a user wants does not have to be addressed in the API explicitly. The alternative, if we do not, then at a minimum we need to allow overlapping of one operator firewall or policy and one user firewall or policy o19:18
mickeysr SG19:18
*** jasondotstar has joined #openstack-meeting-319:18
mickeysTo the user/application deployer, port is clearly useful19:19
*** kebray has quit IRC19:20
SridarKwe probab should be careful on the overlap so that we have no confusion19:20
xgermanwell, it will be difficult for the API to know so it could only be raised at appliance level19:21
sballe+119:21
SridarKoperator owned resource can be marked shared - but that may not solve this perfectly (i can't share with a specific tenant)19:21
*** VW_ has quit IRC19:22
badvelithis is where the problem lies and making SG at port level and the fwaas as it is might be fine?19:22
*** VW__ has quit IRC19:22
mickeysbadveli: I hope we can get something more flexible, but we need to figure out what this means in terms of overlap, ACL merge type issues, etc. If this looks too hairy, at a minimum, what you said.19:23
badveli+119:23
jwarendt<badveli> SG has some warts but is limited by AWS legacy, part of why extended FWaaS as superset in that direction is appealing.19:23
SridarKmickeys: i think we can go to the etherpad for more articulation on the overlap cases19:23
mickeys+119:24
xgermanmickeys +1 Though I think some applicances so a better job with conflict resolution than others - so it’s an implementation detail for me19:24
*** yamamoto has quit IRC19:24
SridarKso i think in summary - we like having 2 APIs but we still need to work out the kinks on the overlap cases19:24
xgermanwell both APIs drive the same backend which then can deal with the overlap (aka throw an error)19:25
xgermanor intelligently resolve19:25
mickeysSridar: Not clear what you mean by 2 APIs and where the consensus is. I think there is strong consensus behind the existing SG API for AWS compatibility, and some sort of enhanced FWaaS API. The part where I am not clear is whether the enhanced FWaaS API becomes a superset of FWaaS and SG functionality, or whether we go to 3 APIs: Old SG, new enhanced SG, new FWaaS.19:25
badvelixgerman you give lot of work19:26
xgermanmickeys let’s stick to two APIs19:26
xgermanwe put all the new stuff into FWaaS, maybe minor enhancements into SG19:26
badveli3 API's seems easier19:26
*** dims_ has quit IRC19:27
sballeyeah not three APIs. FW is still expermental so we don't have to keep things around19:27
mickeysThat is my preference. We have to work to do to incorporate enhanced SG functionality into the enhanced FWaaS API.19:27
SridarKmickeys: i am saying exactly the same thing but on the 3 APIs - i am still a bit on the wall19:27
sballemickeys: +119:27
*** dims has joined #openstack-meeting-319:27
xgerman+!19:27
xgerman+119:27
SridarK+119:28
SridarKok folks time keeper kicks in19:28
SridarKso we can continue more articulation on the etherpad19:28
xgermanor trello19:28
sballeoh no we were having so much fun :-)19:28
SridarKbut this is great19:28
mickeysI assume we are referring to the API evolution etherpad?19:28
xgerman+119:28
SridarKmickeys: yes19:28
SridarK#topic Open Discussion19:29
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:29
SridarKanything folks wanted to bring up19:29
SridarKbefore we close out19:29
xgermanin 60s19:29
badvelixgerman are we tracking using etherpad or trello19:29
SridarKthis was an hour well spent19:29
*** VW_ has joined #openstack-meeting-319:29
xgermanI am mostly on the ether pad those days but can copy things over19:30
badveliok thanks19:30
SridarKxgerman: +1 lets do that19:30
xgermantrello19:30
xgermanactually I men trello19:30
SridarKok we end19:30
vishwanathj_Bye19:31
badveliok thanks19:31
SridarK#endmeeting19:31
sballeSridarK: Thanks for a great meeting19:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:31
hoangcxBye19:31
SridarKbye all19:31
openstackMeeting ended Wed Jul 29 19:31:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:31
badvelibye19:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-07-29-18.32.html19:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-07-29-18.32.txt19:31
sballebye19:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-07-29-18.32.log.html19:31
*** vishwanathj_ has left #openstack-meeting-319:31
jwarendtThanks.19:31
SridarKsballe: thx - great discussion and feedback from the meetup19:31
*** SridarK has quit IRC19:31
*** hoangcx has quit IRC19:31
*** yanping has left #openstack-meeting-319:32
*** vishwanathj has joined #openstack-meeting-319:35
*** salv-orlando has quit IRC19:35
*** mickeys has quit IRC19:37
*** mickeys has joined #openstack-meeting-319:37
*** pc_m has left #openstack-meeting-319:42
*** krtaylor has quit IRC19:46
*** belmoreira has quit IRC19:47
*** HenryG has quit IRC19:49
*** rdopiera has joined #openstack-meeting-319:49
*** e0ne has quit IRC19:51
*** salv-orlando has joined #openstack-meeting-319:51
*** HenryG has joined #openstack-meeting-319:52
*** tqtran has quit IRC19:54
*** FallenPegasus is now known as MarkAtwood19:55
*** e0ne has joined #openstack-meeting-319:55
*** tqtran has joined #openstack-meeting-319:55
*** mrmartin has quit IRC19:56
*** vishwanathj has quit IRC19:57
*** matt-borland has joined #openstack-meeting-319:57
*** TravT has joined #openstack-meeting-319:58
matt-borlando/19:58
*** doug-fish has joined #openstack-meeting-319:58
*** ajmiller has quit IRC19:58
*** madhu_ak has left #openstack-meeting-319:59
*** ajmiller has joined #openstack-meeting-319:59
*** krtaylor has joined #openstack-meeting-319:59
rdopierahi20:00
matt-borlandhello!20:00
*** lblanchard has quit IRC20:00
*** ducttape_ has joined #openstack-meeting-320:00
*** pauloewerton has joined #openstack-meeting-320:00
*** tyr has joined #openstack-meeting-320:01
*** Aish has joined #openstack-meeting-320:02
*** puranamr has quit IRC20:02
tqtran[_]/20:02
*** e0ne has quit IRC20:03
*** puranamr has joined #openstack-meeting-320:03
TravTtqtran: we can touch base after this on your patch.  i have 30 minutes open right after the irc meeting20:04
*** mickeys has quit IRC20:04
tqtransure thing20:04
tqtranwhere is our esteemed PTL?20:04
david-lyle#startmeeting Horizon20:05
openstackMeeting started Wed Jul 29 20:05:28 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:05
*** openstack changes topic to " (Meeting topic: Horizon)"20:05
openstackThe meeting name has been set to 'horizon'20:05
*** hurgleburgler has joined #openstack-meeting-320:05
*** VW_ has quit IRC20:05
david-lylesorry lost in space and time20:05
david-lylehello everyone20:05
TravTo/20:06
tyrhowdy!20:06
hurgleburgler(◕‿◕✿)ノ20:06
*** VW_ has joined #openstack-meeting-320:06
rhagartyo/20:06
matt-borlandguten tag20:06
fnordahlgood evening20:06
doug-fishhi20:06
rdopieragruetzi20:07
david-lylelet's get rolling20:07
david-lyleWe tagged L-2 yesterday, so 2/3 of the way through liberty20:08
david-lyle#link https://launchpad.net/horizon/liberty/liberty-220:08
david-lyleTranslation support for angular is probably the biggest item in that list20:09
TravTSpeaking of that, is that all done?20:10
*** vishwanathj has joined #openstack-meeting-320:10
TravTdid all the patches land needed for angular-gettext?20:10
david-lyleall patches linked to the bp20:10
david-lyledid20:10
david-lyleif others are unattached, I don't know20:11
TravTdoug-fish: tqtran: can I start using the filter syntax now?20:11
tqtranyes20:11
matt-borlandexcellent20:11
*** e0ne has joined #openstack-meeting-320:11
matt-borlandthanks20:11
TravTok, cool. i'll update my TODO out there then.20:11
david-lyleAlso we held the first Horizon midcycle last week in Fort Collins, CO20:12
hurgleburgleryay!20:12
david-lylethere were ~20 people in attendance from 3 continents20:12
*** baoli_ has quit IRC20:12
david-lyleoverall a very productive sprint type gathering, IMO20:13
david-lylethanks to all who could participate20:13
david-lylethe video link broke down on day one and networking difficulties prohibited using it beyond that20:13
david-lyleso apologies to all who were remote20:13
TravT+1, thanks everybody who could make it.20:14
david-lyleJust want to touch on the priorities20:15
david-lyle#link https://etherpad.openstack.org/p/YVR-horizon-liberty-priorities20:15
*** tqtran_ has joined #openstack-meeting-320:16
TravTI'd like to focus my reviews the next few days on helping complete in flight re-org and jscs cleanup. Is what's listed on the https://etherpad.openstack.org/p/YVR-horizon-liberty-priorities up to date?20:16
david-lylemost of the top priority items remain open20:16
tqtranTranslation is complete, so I dont think its all up to date20:16
david-lyleif we can get the tech debt finished off (at least that listed)20:16
david-lyleThat will help a great deal20:17
*** tqtran has quit IRC20:17
david-lyleMy work on plugins has been side tracked with testing issues20:17
david-lylealthough lhcheng is working on moving trove to /contrib and robcresswell is removing the router dash from horizon20:18
*** sqchen has joined #openstack-meeting-320:18
david-lyleso some forward progress is still being made20:18
*** esp has joined #openstack-meeting-320:18
david-lyledjango 1.8 still looms20:19
ducttape_django 1.8 looked like it had small patches to move it forward  https://review.openstack.org/#/c/201734/ is next20:19
*** jasondotstar has quit IRC20:19
david-lyleI tried that but saw issues20:19
david-lylenot sure the source20:19
david-lylewill look more after testing issues resolved20:19
david-lyleif someone doesn't beat me to it20:20
*** vishwanathj has quit IRC20:20
* david-lyle is a slow runner20:20
tyrTravT: The dash reorg patch series starts with https://review.openstack.org/#/c/197353 and is now stable. No additional patches are planned. This will complete the re-org work and unblock JSCS.20:20
david-lyleducttape_: did try curvature on a decent sized topology and it was a vast improvement on the existing network topology so please give that a look20:21
ducttape_I also tried it again, and it did not draw the graph correctly.  not sure if that is bad data or bad code20:21
david-lyledoh20:22
ducttape_it works well for simpler network setups though20:22
david-lylemore testing would be good by many people20:22
fnordahllink to patchset?20:22
david-lyleLMLPTFY: https://blueprints.launchpad.net/horizon/+spec/curvature-network-topology20:23
david-lylehttps://review.openstack.org/#/c/199063/20:23
fnordahlthx20:23
david-lylenot that patch20:23
david-lylehttps://review.openstack.org/#/c/141078/20:24
david-lylethat patch20:24
fnordahlheh, k thx20:24
*** mickeys has joined #openstack-meeting-320:24
*** Aish has quit IRC20:24
david-lylenot sure what the second one is about20:24
fnordahl:-)20:24
*** yamamoto has joined #openstack-meeting-320:24
TravTducttape_:  you comment is kinda funny.20:24
TravTducttape: you said there are intermittent bugs, but okay to merge?20:25
ducttape_I think so, it's tough to object becasue the problems I have seen are in our dev environment - where we do all sorts of crazy things20:25
*** lhcheng has joined #openstack-meeting-320:25
ducttape_could be a bunch of bad things exist in our neutron db20:25
david-lylemore eyes would be better20:26
TravTok.  i'm happy to try it out, but my dev env in no way replicates a real network env.20:26
fnordahlI'll test.20:26
david-lyleTravT: this view is for the projects panel20:26
ducttape_yep, this patch set really shines when you have more than one tenant network and several instances20:26
david-lyleso while a high level of complexity is possible, it may not be prevalent20:27
ducttape_I'd say 3-4 tenant networks with 5 instances on each network if probably more complex than average20:27
ducttape_if/is20:27
TravTthat's not too bad to setup20:28
*** Aish has joined #openstack-meeting-320:28
fnordahlSpeaking of networking:20:28
fnordahl#link https://blueprints.launchpad.net/horizon/+spec/neutron-subnet-allocation20:28
fnordahlI have proposed a implementation of the first phase of this blueprint, and would really like to have comments, insults, cheers, feedback and reviews of the patchsets linked to on the Whiteboard.20:28
*** yamamoto has quit IRC20:29
david-lylefnordahl: looks like amotoki is reviewing, that's the best first step20:29
david-lylethat's all the general items I had20:30
david-lyle#topic Feature Branches20:30
*** openstack changes topic to "Feature Branches (Meeting topic: Horizon)"20:30
david-lyleI promised to look into what Feature Branches would entail20:31
david-lyle#link http://docs.openstack.org/infra/manual/drivers.html20:31
david-lyleis the best write up I found20:31
*** jasondotstar has joined #openstack-meeting-320:32
matt-borlanddavid-lyle: thanks for looking into that20:32
david-lyleso I think I need release mgmt team to create branches we would need20:32
ducttape_I think neutron used feature branch for DVR work, they might have tricks to learn20:33
david-lyleand commit rights would be based on convention20:33
matt-borlandand this would be for particularly big sets of changes, right?20:33
david-lyleswift used them for erasure codes as well20:34
david-lylematt-borland: yes20:34
TravTi'm wondering what comprises a feature branch.20:34
TravTin our work.20:34
* notmyname can answer questions about feature branches in swift20:34
david-lyleflow: branch created, feature developed, iterations, then one big merge at the end20:34
matt-borlandprobably not the panels I'm working with...I think we have a simple patch structure that will work for now20:35
david-lylenotmyname: investigating for long running features20:35
david-lyles/running/building/20:35
notmynamethere's a few things that we've found to be vital. one big one is frequently merging master to the feature branch20:35
matt-borlandmakes sense20:35
TravTnotmyname: does gerrit still do merge conflict detection on the feature branch automatically on each patch20:36
TravT?20:36
TravTthat lands on master20:36
notmynamealso, because a feature branch (as we've used them) is intentionally "separate", we don't actually merge the feature branch itself. we refactor the patches on the feature branch as a set of logical patches, then do one merge commit to master20:36
*** salv-orlando has quit IRC20:36
*** stevemar has quit IRC20:37
notmynameTravT: yes, and the UI for it is wonky. mostly, we ignore that part and focus on what git tells us20:37
david-lylenotmyname: so do you lose the git history of the branch?20:37
david-lylesince it's a merge, it should be maintained no?20:38
notmynameno, we tag the original feature branch (and close it for new patches) so we still have the whole history20:38
david-lyleso you don't actually merge from the feature branch20:38
*** Aish has quit IRC20:38
david-lylenew patches20:38
*** armax has joined #openstack-meeting-320:39
david-lyledidn't grok it the first time :P20:39
*** armax has quit IRC20:39
david-lylewhy not just a large merge?20:39
david-lyleI can also follow up offline20:40
ducttape_you might have a much more complex merge / history on master, for not much value20:40
notmynamewe created a feature branch: feature/ec. then, every week(-ish) we'd merge master to feature/ec. dev work continued on feature/ec for nearly a year. then we tagged feature/ec, refactored the patches onto feature/ec-review and proposed one merge commit to master from that20:40
*** Aish has joined #openstack-meeting-320:40
notmynamethe reason we clean up the git history is so that we have something that's (1) easy to review and reason about in logical chunks and (2) later we'll be able to see the logical flow of the implementation20:40
notmynameand we do the single merge commit to master so that future debug work (eg with git bisect) will have a single point in history where the feature is introduced20:41
david-lyleok, I think that makes sense20:41
*** MarkAtwood has quit IRC20:41
david-lylethanks notmyname, I may have more questions later20:41
notmynamewe've completed 2 and currently have 2 open now20:42
notmynamedavid-lyle: any time20:42
*** MarkAtwood has joined #openstack-meeting-320:42
david-lyleok stepping back a bit, we started talking about feature branches for a couple of reasons20:42
david-lyleone was the desire to work collaboratively on a complex feature incrementally has proved difficult with patch chains 10 deep20:43
david-lyletwo was to resist the desire to merge partial features20:43
*** kzaitsev_mb has joined #openstack-meeting-320:44
ducttape_I think we found a better example of how to do ng patches, in a single review too20:44
david-lylesome of the work recently has been tagged as taking the first step, but in a few cases it has resulted in/proposed an non-functional panel20:44
david-lyleright, so the two options were, if people feel the need to build incrementally, they could use a feature branch20:45
*** salv-orlando has joined #openstack-meeting-320:46
david-lyleor just implement the full feature, or a useful chunk before proposing the patch to add said feature20:46
TravTI think that you (david-lyle) had proposed that the patches could be broken up just in logical functional chunks and that'd be okay.20:46
*** ongk has joined #openstack-meeting-320:46
TravTI think that makes sense.20:46
*** VW_ has quit IRC20:47
david-lyleTravT: That is fine, but the other patches should be existant, not just promises20:47
*** cbouch has quit IRC20:47
TravTand for disabled panels, I'm not seeing a large amount of harm in doing it that way.20:47
david-lyleI disagree20:47
ducttape_howso TravT?20:47
david-lyleit's dead code20:47
TravTalso, i think it is wrong to tell people to not submit their work as reviews even if in WIP state20:47
*** VW_ has joined #openstack-meeting-320:47
TravTthey should however mark as wip20:47
ducttape_yeah, WIP reviews are fine / anything goes.  however, it is polite to not try to flood openstack infra with check jobs20:48
david-lyleso adds complexity, maintenance for something that's not really there20:48
*** puranamr has quit IRC20:48
doug-fishalso related text get picked up for translation20:48
david-lyleit should be merged to tree when it adds value and is usable20:48
tyrThe review is really the bottleneck. Patches need to be small in order to move through. Feature branches might be nice for the collaborative development, but still suffer a big bang review at the end. How do we accomodate that?20:48
TravTnot arguing that david-lyle20:48
TravTi did say logical, functioning parts20:49
david-lyleI think the disagreement would be on "functional"20:49
TravTfor example, with images, i originally also had non-working action buttons, but after heeding your feedback removed that20:49
david-lyleTravT: and that's good20:49
david-lylebut an empty panel is of no value20:50
ducttape_tyr - if you want speed, go with a feature branch.   master will have greater weight on quality / stability20:50
david-lylewhich was another example20:50
TravTdavid-lyle: that's fair...20:50
matt-borlandI think the point about having lined up the "next level of useful patches" is probably a good one.20:50
*** yapeng has joined #openstack-meeting-320:50
david-lyleanother was buttons but no backend implementation for the actions20:50
TravTalthough, we probably need to up some base patches for enabling angular on each dashboard.20:50
TravTand merge those in.20:50
david-lyleTravT: I'd argue we have20:50
ducttape_yeah, we had a good example of how to do angular reasonably well, patch escapes me atm20:51
david-lylethere's a lot of angular code in tree, and the end user sees very little result of that yet20:51
tyrducttape_: My point was that a feature branch makes an even larger review...so at some point, commits are broken down into a series of small, easily reviewable pieces anyhow.20:51
*** lblanchard has joined #openstack-meeting-320:51
TravTwell, on the images panel, i did put up some extra module stuff just for enablement... partially due to the whole webroot issue20:51
*** VW_ has quit IRC20:51
ducttape_one big review, where everything works.... vs 10 small reviews, where you aren't sure what should or should not work.... I think the bigger patch is the way to go.  total review time would be less as well20:52
TravTi don't know about that ducttape_20:52
matt-borlandevery time we try that people say the patch is too big and must be broken apart20:52
TravTwe abused tqtran for over a year with that strategy20:53
ducttape_or it seems like it should be less, because everything should be working20:53
matt-borlandthere are also some issues with cross-functionality,20:53
matt-borlandespecially with API pathes20:53
*** puranamr has joined #openstack-meeting-320:53
matt-borland*patches20:53
TravTi think reasonable functional level patches make some sense...20:53
david-lylemaybe we shouldn't be tackling so much new at once and spend some more time fixing things like broken selenium tests and integration tests20:53
david-lylethen the risk of conflict goes down20:54
ducttape_or fixing existing bugs20:54
tyrWith or without feature branches we end up wanting something like 1) each patch is small but functional, 2) most of the patches are in place to be able to see the whole picture.20:54
david-lylefix a bug in master, back port to kilo or juno and operators will actually see it :)20:55
david-lyletyr, true, but the functionality should be there20:55
*** Sukhdev_ has quit IRC20:55
david-lyleand ready to review20:55
TravTdavid-lyle, ducttape_ made a good point earlier about zuul testing on WIP patches...20:56
matt-borlanddavid-lyle: wrt panel patches, I do feel that after our discussion we have a good structure that satisfies our interests.20:56
david-lyleindeed he did20:56
TravTif we WIP the workflow, that still churns up zuul doesn't it?20:56
*** yapeng has quit IRC20:56
ducttape_I have noticed a lot of people with like 40 or 50 patches for a change.  if you can, avoid doing so many changes20:56
david-lylefeature branches would too20:56
david-lyleI think coming with a more fully realized feature would reduce churn20:57
david-lylebut I can't ever argue with collaboration20:57
TravTi will say that sometimes a lot of patches come in in spurts because people are addressing review comments quickly and getting further review20:57
TravTthere is nothing wrong with that IMO.20:57
david-lylethat said, I have used github to collaborate on Horizon patches with other devs in the past20:57
matt-borlandyeah, that is a good thing TravT20:57
TravTbut I do see that we should try to ensure all comments are addressed in each submission if possible... etc, to lessen the churn.20:58
david-lyleI think 50 patch sets on relatively minor changes is extreme20:58
david-lylethe tools are the tools. My main beef is with non-feature realizing patches with nothing following20:59
david-lylethat's just silly, IMO20:59
matt-borlandyep, I think we've agreed on that20:59
matt-borlandI will strongly push back when people ask to break my Panel patch into smaller patches21:00
tyrYes, being able to download the final patch to see the big picture...even when reviewing only the 1st part is very helpful.21:00
david-lylewe're at time, I did want to welcome rdopiera back though21:00
TravTrdopiera: good to see you around!21:00
lhcheng I try to read all the PS comments before approving to make sure all comments are addressed -  a little less patch set for smaller change would be nice to speed-up review.21:00
hurgleburglerrdopiera: welcome back!21:01
doug-fishrdopiera: yes, good to have you back!21:01
tqtran_rdopiera: wb!!!21:01
david-lyledid you have anything you wanted to add before we close rdopiera? I'm trying to get to the config file patch21:01
david-lyleany further discussion in #openstack-horizon as usual21:02
david-lylethanks everyone21:02
david-lyle#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Wed Jul 29 21:02:36 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-07-29-20.05.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-07-29-20.05.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-07-29-20.05.log.html21:02
*** lhcheng has left #openstack-meeting-321:02
*** matt-borland has left #openstack-meeting-321:02
*** pauloewerton has left #openstack-meeting-321:02
*** doug-fish has left #openstack-meeting-321:02
*** ducttape_ has left #openstack-meeting-321:03
*** esp has left #openstack-meeting-321:03
*** absubram has quit IRC21:04
*** tqtran_ has left #openstack-meeting-321:04
*** Aish has quit IRC21:04
*** VW_ has joined #openstack-meeting-321:05
*** jckasper has quit IRC21:07
*** Brian has joined #openstack-meeting-321:08
rdopieraTravT, hurgleburgler: thanks!21:08
rdopieradavid-lyle: thanks21:08
*** Brian is now known as Guest2926921:08
*** rdopiera has quit IRC21:08
*** TravT has left #openstack-meeting-321:08
*** bryan_att has quit IRC21:10
*** ajo_ has joined #openstack-meeting-321:11
*** ajo_ has quit IRC21:12
*** yamamoto has joined #openstack-meeting-321:12
*** ajo_ has joined #openstack-meeting-321:12
*** ajo_ has quit IRC21:13
*** Guest29269 has quit IRC21:13
*** yamamoto has quit IRC21:14
*** ekarlso has quit IRC21:16
*** singlethink has joined #openstack-meeting-321:19
*** singlet__ has joined #openstack-meeting-321:21
*** singleth_ has quit IRC21:22
*** sqchen has quit IRC21:23
*** e0ne has quit IRC21:24
*** singlethink has quit IRC21:24
*** lblanchard has quit IRC21:24
*** banix has quit IRC21:25
*** bryan_att has joined #openstack-meeting-321:31
*** jasondotstar has quit IRC21:41
*** sqchen has joined #openstack-meeting-321:43
*** ekarlso has joined #openstack-meeting-321:45
*** Aish has joined #openstack-meeting-321:52
*** Aish has left #openstack-meeting-321:52
*** hurgleburgler has left #openstack-meeting-321:55
*** MarkAtwood has quit IRC21:59
*** markvoelker has quit IRC22:02
*** sqchen has left #openstack-meeting-322:04
*** jpomeroy has quit IRC22:04
*** neelashah has quit IRC22:11
*** VW__ has joined #openstack-meeting-322:13
*** yamamoto has joined #openstack-meeting-322:15
*** VW_ has quit IRC22:17
*** VW__ has quit IRC22:18
*** Sukhdev_ has joined #openstack-meeting-322:19
*** yamamoto has quit IRC22:20
*** kzaitsev_mb has quit IRC22:22
*** bknudson has quit IRC22:25
*** banix has joined #openstack-meeting-322:25
*** jasondotstar has joined #openstack-meeting-322:28
*** armax has joined #openstack-meeting-322:29
*** zz_natorious is now known as natorious22:29
*** Yi has joined #openstack-meeting-322:30
*** Yi has quit IRC22:30
*** sigmavirus24 has quit IRC22:31
*** mickeys has quit IRC22:32
*** mickeys has joined #openstack-meeting-322:33
*** sigmavirus24 has joined #openstack-meeting-322:33
*** natorious has quit IRC22:34
*** natorious has joined #openstack-meeting-322:34
*** singlet__ has quit IRC22:35
*** armax has quit IRC22:36
*** mwagner_lap has quit IRC22:38
*** sdake has quit IRC22:40
*** sdake has joined #openstack-meeting-322:40
*** sdake has quit IRC22:42
*** sigmavirus24 is now known as sigmavirus24_awa22:43
*** jaypipes has quit IRC22:43
*** sridhar_ram has joined #openstack-meeting-322:44
*** tellesnobrega has quit IRC22:50
*** jpomeroy has joined #openstack-meeting-322:50
*** mshindo has quit IRC22:50
*** vishwanathj has joined #openstack-meeting-322:53
*** kzaitsev_mb has joined #openstack-meeting-322:55
*** markvoelker_ has joined #openstack-meeting-322:57
*** kebray_ has quit IRC23:00
*** kzaitsev_mb has quit IRC23:01
*** alexpilotti has quit IRC23:05
*** jpomeroy has quit IRC23:17
*** jpomeroy has joined #openstack-meeting-323:17
*** puranamr has quit IRC23:18
*** pballand has quit IRC23:18
*** pballand has joined #openstack-meeting-323:19
*** vishwanathj has quit IRC23:20
*** ivar-lazzaro has quit IRC23:23
*** zhenguo has joined #openstack-meeting-323:31
*** jasondotstar has quit IRC23:33
*** kzaitsev_mb has joined #openstack-meeting-323:36
*** mwagner_lap has joined #openstack-meeting-323:37
*** mickeys has quit IRC23:38
*** obondarev has quit IRC23:38
*** obondarev has joined #openstack-meeting-323:39
*** jasondotstar has joined #openstack-meeting-323:45
*** armax has joined #openstack-meeting-323:47
*** bharath_ has quit IRC23:53
*** shwetaap1 has quit IRC23:54
*** ajmiller has quit IRC23:56

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!