Wednesday, 2015-05-06

*** etoews has quit IRC00:09
*** Aish has quit IRC00:13
*** fallenpegasus has quit IRC00:14
*** carl_baldwin has quit IRC00:27
*** mlavalle has quit IRC00:30
*** Sukhdev has quit IRC00:36
-openstackstatus- NOTICE: Restarted gerrit due to stuck stream-events connections. Events since 23:49 were missed and changes uploaded since then will need to be rechecked.00:42
*** clu_ has quit IRC00:43
*** banix has joined #openstack-meeting-300:53
*** mwang2 has quit IRC00:55
*** igordcard has quit IRC00:56
*** SumitNaiksatam has joined #openstack-meeting-301:04
*** alexpilotti has quit IRC01:08
*** bpokorny has quit IRC01:12
*** eghobo has quit IRC01:14
*** alexsyip has quit IRC01:22
*** Swami has quit IRC01:28
*** alexpilotti has joined #openstack-meeting-301:29
*** s3wong_ has quit IRC01:40
*** alexpilotti has quit IRC01:48
*** stanzgy has joined #openstack-meeting-301:54
*** salv-orlando has joined #openstack-meeting-301:58
*** zhenguo has joined #openstack-meeting-302:01
*** ivar-lazzaro has quit IRC02:03
*** salv-orlando has quit IRC02:04
*** ivar-lazzaro has joined #openstack-meeting-302:04
*** sigmavirus24 is now known as sigmavirus24_awa02:19
*** ivar-laz_ has joined #openstack-meeting-302:21
*** yamahata has quit IRC02:22
*** mestery has joined #openstack-meeting-302:23
*** ivar-lazzaro has quit IRC02:24
*** mwagner_lap has joined #openstack-meeting-302:32
*** stanzgy has quit IRC02:41
*** baoli has joined #openstack-meeting-302:42
*** nelsnelson has joined #openstack-meeting-302:47
*** stanzgy has joined #openstack-meeting-302:49
*** nelsnelson has quit IRC02:52
*** ivar-laz_ has quit IRC02:53
*** VW_ has joined #openstack-meeting-302:59
*** sarob has joined #openstack-meeting-303:06
*** markvoelker has quit IRC03:10
*** yamahata has joined #openstack-meeting-303:12
*** banix has quit IRC03:15
*** ivar-lazzaro has joined #openstack-meeting-303:19
*** krtaylor has quit IRC03:37
*** lazy_prince has joined #openstack-meeting-303:39
*** rushiagr_away is now known as rushiagr03:44
*** baoli has quit IRC03:50
*** coolsvap|afk is now known as coolsvap03:53
*** krtaylor has joined #openstack-meeting-303:55
*** eghobo has joined #openstack-meeting-304:02
*** markvoelker has joined #openstack-meeting-304:11
*** jckasper has joined #openstack-meeting-304:11
*** rushiagr is now known as rushiagr_away04:12
*** eghobo has quit IRC04:14
*** markvoelker has quit IRC04:16
*** VW_ has quit IRC04:26
*** salv-orlando has joined #openstack-meeting-304:35
*** salv-orlando has quit IRC04:38
*** VW_ has joined #openstack-meeting-304:48
*** btully has joined #openstack-meeting-304:50
*** mrmartin has joined #openstack-meeting-304:50
*** nkrinner has joined #openstack-meeting-304:51
*** VW_ has quit IRC04:52
*** sarob has quit IRC04:56
*** egallen has joined #openstack-meeting-304:58
*** fallenpegasus has joined #openstack-meeting-305:01
*** rushiagr_away is now known as rushiagr05:03
*** btully has quit IRC05:07
*** ivar-lazzaro has quit IRC05:08
*** irenab has joined #openstack-meeting-305:08
*** ivar-lazzaro has joined #openstack-meeting-305:08
*** Swami has joined #openstack-meeting-305:11
*** ivar-lazzaro has quit IRC05:11
*** markvoelker has joined #openstack-meeting-305:12
*** ivar-lazzaro has joined #openstack-meeting-305:12
*** egallen has quit IRC05:13
*** markvoelker has quit IRC05:16
*** mrmartin has quit IRC05:17
*** fallenpegasus has quit IRC05:17
*** egallen has joined #openstack-meeting-305:18
*** egallen has quit IRC05:18
*** SumitNaiksatam has quit IRC05:19
*** SumitNaiksatam has joined #openstack-meeting-305:20
*** fallenpegasus has joined #openstack-meeting-305:20
*** iovadia has joined #openstack-meeting-305:22
*** sergef has joined #openstack-meeting-305:39
*** rushiagr is now known as rushiagr_away05:40
*** wojdev has joined #openstack-meeting-305:47
*** markvoelker has joined #openstack-meeting-305:51
*** dobson has quit IRC05:52
*** markvoelker has quit IRC05:55
*** SumitNaiksatam has quit IRC05:57
*** wojdev has quit IRC05:58
*** tmazur has joined #openstack-meeting-306:00
*** SumitNaiksatam has joined #openstack-meeting-306:01
*** Swami has quit IRC06:03
*** Longgeek has joined #openstack-meeting-306:05
*** jcoufal has joined #openstack-meeting-306:06
*** dobson has joined #openstack-meeting-306:07
*** mrunge has joined #openstack-meeting-306:08
*** pkoniszewski has joined #openstack-meeting-306:09
*** evgenyf has joined #openstack-meeting-306:09
*** salv-orlando has joined #openstack-meeting-306:10
*** scheuran has joined #openstack-meeting-306:13
*** ivar-laz_ has joined #openstack-meeting-306:15
*** ivar-lazzaro has quit IRC06:15
*** Longgeek has quit IRC06:21
*** Longgeek has joined #openstack-meeting-306:21
*** rushiagr_away is now known as rushiagr06:22
*** Longgeek has quit IRC06:23
*** Longgeek has joined #openstack-meeting-306:23
*** Poornima has joined #openstack-meeting-306:23
*** sergef has quit IRC06:27
*** ivar-lazzaro has joined #openstack-meeting-306:35
*** fallenpegasus has quit IRC06:35
*** sahid has joined #openstack-meeting-306:36
*** fallenpegasus has joined #openstack-meeting-306:36
*** ivar-laz_ has quit IRC06:36
*** tteggel has quit IRC06:41
*** yamahata has quit IRC06:41
*** tteggel has joined #openstack-meeting-306:41
*** yamahata has joined #openstack-meeting-306:48
*** jcoufal_ has joined #openstack-meeting-306:49
*** markvoelker has joined #openstack-meeting-306:52
*** jcoufal has quit IRC06:52
*** markvoelker has quit IRC06:56
*** wojdev has joined #openstack-meeting-306:58
*** jtomasek has joined #openstack-meeting-306:59
*** wojdev has quit IRC07:05
*** fallenpegasus has quit IRC07:06
*** fallenpegasus has joined #openstack-meeting-307:07
*** wojdev has joined #openstack-meeting-307:07
*** JeanBriceCombebi has joined #openstack-meeting-307:09
*** fallenpegasus has quit IRC07:11
*** wojdev has quit IRC07:19
*** wojdev has joined #openstack-meeting-307:21
*** matrohon has joined #openstack-meeting-307:27
*** eghobo has joined #openstack-meeting-307:36
*** safchain has joined #openstack-meeting-307:54
*** rushiagr has quit IRC07:56
*** wojdev has quit IRC08:01
*** egallen has joined #openstack-meeting-308:05
*** lsmola has joined #openstack-meeting-308:11
*** rushiagr has joined #openstack-meeting-308:12
*** wojdev has joined #openstack-meeting-308:17
*** salv-orlando has quit IRC08:18
*** salv-orlando has joined #openstack-meeting-308:18
*** e0ne has joined #openstack-meeting-308:22
*** ivar-lazzaro has quit IRC08:23
*** eghobo has quit IRC08:29
*** tmazur has quit IRC08:30
*** tmazur has joined #openstack-meeting-308:31
*** MaxV has joined #openstack-meeting-308:34
*** JeanBriceCombebi has quit IRC08:37
*** JeanBriceCombebi has joined #openstack-meeting-308:38
*** e0ne has quit IRC08:43
*** tmazur has quit IRC08:45
*** tmazur has joined #openstack-meeting-308:46
*** vgridnev has quit IRC08:49
*** MaxV has quit IRC08:52
*** JeanBriceCombebi has quit IRC08:57
*** JeanBriceCombebi has joined #openstack-meeting-308:57
*** lsmola has quit IRC08:58
*** jtomasek has quit IRC08:58
*** smccully has quit IRC08:58
*** aleksandr_null has quit IRC08:58
*** russellb has quit IRC08:58
*** haleyb has quit IRC08:58
*** SotK has quit IRC08:58
*** mrda has quit IRC08:58
*** lsmola has joined #openstack-meeting-309:00
*** jtomasek has joined #openstack-meeting-309:00
*** smccully has joined #openstack-meeting-309:00
*** aleksandr_null has joined #openstack-meeting-309:00
*** russellb has joined #openstack-meeting-309:00
*** haleyb has joined #openstack-meeting-309:00
*** SotK has joined #openstack-meeting-309:00
*** mrda has joined #openstack-meeting-309:00
*** wojdev has quit IRC09:08
*** rushiagr is now known as rushiagr_away09:11
*** e0ne has joined #openstack-meeting-309:25
*** Longgeek has quit IRC09:53
*** JeanBriceCombebi has quit IRC09:57
*** JeanBriceCombebi has joined #openstack-meeting-309:57
*** e0ne is now known as e0ne_09:59
*** e0ne_ is now known as e0ne10:05
*** zhenguo has quit IRC10:07
*** rushiagr_away is now known as rushiagr10:15
*** sahid has quit IRC10:33
*** Longgeek has joined #openstack-meeting-310:35
*** sahid has joined #openstack-meeting-310:37
*** coolsvap is now known as coolsvap|afk10:38
*** lennyb has joined #openstack-meeting-310:43
*** stanzgy has quit IRC10:53
*** yalie has quit IRC10:57
*** evgenyf has quit IRC11:09
*** yamahata has quit IRC11:30
*** Poornima has quit IRC11:40
*** JeanBriceCombebi has quit IRC11:41
*** evgenyf has joined #openstack-meeting-311:46
*** gulic has joined #openstack-meeting-311:52
*** gulic has left #openstack-meeting-311:52
*** alexpilotti has joined #openstack-meeting-311:56
*** markvoelker has joined #openstack-meeting-311:59
*** VW_ has joined #openstack-meeting-312:01
*** bknudson has joined #openstack-meeting-312:04
*** btully has joined #openstack-meeting-312:05
*** VW_ has quit IRC12:06
*** lblanchard has joined #openstack-meeting-312:14
*** jckasper has quit IRC12:15
*** btully has quit IRC12:20
*** e0ne is now known as e0ne_12:22
*** e0ne_ is now known as e0ne12:29
*** JeanBriceCombebi has joined #openstack-meeting-312:33
*** edleafe has quit IRC12:40
*** edleafe has joined #openstack-meeting-312:41
*** VW_ has joined #openstack-meeting-312:42
*** lblanchard has quit IRC12:47
*** baoli has joined #openstack-meeting-312:48
*** banix has joined #openstack-meeting-312:49
*** banix has quit IRC12:53
*** baoli_ has joined #openstack-meeting-312:57
*** baoli has quit IRC13:00
*** qwebirc81982 has joined #openstack-meeting-313:00
*** rushiagr is now known as rushiagr_away13:02
*** rushiagr_away is now known as rushiagr13:02
*** Yi has joined #openstack-meeting-313:03
*** gsagie has joined #openstack-meeting-313:04
*** rushiagr is now known as rushiagr_away13:06
*** pkoniszewski has quit IRC13:12
*** Yi has quit IRC13:14
*** e0ne is now known as e0ne_13:19
*** e0ne_ is now known as e0ne13:21
*** peristeri has joined #openstack-meeting-313:21
*** jckasper has joined #openstack-meeting-313:30
*** sigmavirus24_awa is now known as sigmavirus2413:35
*** lifeless has quit IRC13:42
*** cbits has joined #openstack-meeting-313:45
*** vikram__ has joined #openstack-meeting-313:48
*** mattgriffin has joined #openstack-meeting-313:50
*** sfinucan has joined #openstack-meeting-313:55
*** moshele has joined #openstack-meeting-313:57
*** tmazur has quit IRC13:57
ajohi :)14:00
sfinucanhey14:00
vikram__hi14:01
matrohonhi14:01
vhowardhey14:01
ajolet's start :)14:01
ajo#startmeeting neutron_qos14:01
openstackMeeting started Wed May  6 14:01:25 2015 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
ajo#link https://wiki.openstack.org/wiki/Meetings/QoS#2015-05-06_14:00_UTC14:01
ajo#topic API microversioning spec implications14:02
ajo#link https://review.openstack.org/#/c/136760/14:02
*** openstack changes topic to "API microversioning spec implications (Meeting topic: neutron_qos)"14:02
moshelehi14:02
ajoI have included this first point after talking to sc68cal today :)14:02
ajoI recommend reading it if you have time,14:02
irenabhi14:02
vikram__it's too long:)14:02
vikram__i tried but couldn't complete14:02
ajothis should give us more flexibility about how we model the API & evolve it, but it probably won't be available until mid L (I'm supposing here)14:03
*** lblanchard has joined #openstack-meeting-314:03
ajovikram__ :D yeah, it needs a good coffee to read it14:03
ajosc68cal, any comments? :)14:03
vhowardwill take a look thanks14:03
*** shwetaap has joined #openstack-meeting-314:04
ajook, let's move on14:04
ajo#topic Changes to the QoS API spec: scoping into bandwidth limiting14:05
*** openstack changes topic to "Changes to the QoS API spec: scoping into bandwidth limiting (Meeting topic: neutron_qos)"14:05
*** JeanBriceCombebi has quit IRC14:05
ajo#link https://review.openstack.org/#/c/88599/9..10/specs/liberty/qos-api-extension.rst14:05
ajoI iterated a couple of times on the spec since last week14:05
*** Networkn3rd has joined #openstack-meeting-314:05
ajoarmax, from the drivers team had some time to review and provide feedback14:06
ajohe asked for some changes in the data model (I'll get to that later)14:06
*** sadasu has joined #openstack-meeting-314:07
ajoand he asked to scope the initial work into bandwidth limiting14:07
sc68calajo: sorry, just got scrollback - nothing to add14:08
ajoI know sc68cal has comments about my spec title change, but we can find something in the middle,  as I keep repearing: I believe it's better if we prepare the data model and the API to be more close to the final desired state that... if we keep changing it and jumping unnecesarily.14:08
vhowardyeah saw that, we would love for the data model and api to be flexible enough for our use-cases for marking our network traffic i'll put some notes to help in the spec?14:08
*** shakamunyi has joined #openstack-meeting-314:09
ajovhoward +114:09
*** qwebirc81982 has quit IRC14:09
vhowardcool, i can put some notes in for us14:09
vhowardand help out as you need, just let me know14:09
ajoCheck the comments about traffic classification & ideas,14:10
vhowardcool ajo, thanks for the tip will read up today14:10
ajoI believe it will be better modeled like that (I have a point later in the meeting for it)14:10
*** lifeless has joined #openstack-meeting-314:10
ajo#topic Changes to the QoS API spec: modeling of rules (class hierarchy) (Guarantee split out)14:10
*** openstack changes topic to "Changes to the QoS API spec: modeling of rules (class hierarchy) (Guarantee split out) (Meeting topic: neutron_qos)"14:10
ajook, if you see , I've modified the current data model, per armax suggestion, to make it more specific14:11
ajoI keep the QoSPolicy, composed of QoSRules14:11
ajobut now every rule type may have a QoS<type>Rule14:12
ajoextending the basic rule information with the specific parameters14:12
ajoAlso, there was a discussion about splitting rules into smaller combinable chunks,14:12
*** JeanBriceCombebi has joined #openstack-meeting-314:13
ajolike, guarantees... since there could be plugins not able to provide guarantees, while others would.14:13
*** shakamunyi has quit IRC14:13
ajoThe idea is plugins can implement rule types as a whole, and separate optional aspects into separate rules (they finally combine in a policy)14:13
ajoif you see issues with the current changes, speak now, or... otherwise speak into the spec :)14:15
irenabajo: comparing to specify ‘guarantee level’ atribute in the rule itslef?14:15
ajoirenab, what do you mean?14:15
vikram__I feel the QoSRule is carrying more information now. How about splitting it out.14:15
irenabajo: what you mentiond before .. like, guarantees14:16
ajovikram__, see comments, Traffic Classification fields are going to be splitted out.14:16
ajobut for later iterations, not now14:16
*** lazy_prince has quit IRC14:16
ajojust wanted to see how it looked, and the drawbacks of what I had in mind14:16
ajoirenab, ahh14:16
vikram__ok.. i feel it's just a suggestion from your end and you need more voting before doing:)14:16
ajofor example, the previous ratecontrol: max_kbps=10000 min_kbps=300014:17
ajocould be expressed as14:17
ajobandwidthlimit max_kbps=10000   + another rule for guarantee min_kbps=300014:17
ajoguarantee could have a field to say if it's strict, or best effort14:17
ajoor we could have a separate rule for besteffort/strict14:18
ajovikram__ +1 :D14:18
ajoirenab, this way, if the plugin doesn't opt in tu support the "guarantee" rules... you can't just push that rule14:18
vikram__+1 for separate rules. Because it could be vendor specific.14:19
sfinucan+1 - very granular14:19
gsagieajo: i think that what ever model which will be easy to extend with extensions which dont effect other plugins just those that implement them is good,14:19
gsagieso seperating the rules sounds good as long as the user can understand what is supported and what is not, or do you mean the add will just fail?14:20
gsagiein case something is not supported14:20
irenabgsagie: +114:20
ajogsagie, yes, that's one of the things, it fits well in the extension world, but... we'll have microversioning14:20
ajoyes,14:20
ajogsagie, there's a point about checking incompatible rules14:20
*** cbouch has joined #openstack-meeting-314:21
ajowe will need a mechanism to check rules as they are added to see if they can be implemented with the other rules already in the policy14:21
ajofor example, you can't ask for a guarantee (min_kbps) > bandwidthlimit (max_kbps)14:21
*** rushiagr_away is now known as rushiagr14:21
*** rmschn has joined #openstack-meeting-314:21
ajoaround this (successive extensions), we had another point in the agenda14:23
ajo#topic Discuss multiple API end points (per rule type) vs single.14:23
*** openstack changes topic to "Discuss multiple API end points (per rule type) vs single. (Meeting topic: neutron_qos)"14:23
ajowith this model, if we had an API end point per rule type (this is being discussed in comments of the spec right now)14:23
ajowe could just add one extension per rule14:24
ajo(rule type)14:24
ajohmmm, sorry, I'm mixing things up :)14:24
ajothat makes a nonsense :)14:24
ajowe just extend the port & net once with the QoSPolicy, right? :)14:24
ajo(-1 on me, please  :) )14:24
vhoward;)14:25
irenabajo: I guess you mean extending the QoS extension with more qos rule types14:25
ajoyes, more about extending the API14:25
ajothere are two options here, we can have one api end to create rules14:26
*** nkrinner has quit IRC14:26
ajoor we can have an api endpoint per rule type14:26
gsagieajo : the problem in the world of decomposition is that one might not know of other extensions and it will be hard to maintain (especially with what you said above about checking rules)14:26
gsagieso i think in a centralized place, if i understood what you mean :)14:26
ajoI'm talking about...14:26
* ajo scrolls on the spec14:27
*** e0ne is now known as e0ne_14:27
ajoabout having:14:27
ajo POST /v2.0/qos-<type>-rules14:27
ajoone per type14:27
ajoor...14:27
ajojust a /v2.0/qos-rules14:28
irenabajo: by api end point, you mean REST resource /qos/XXX or different path?14:28
ajowhere we post & get , UPDATE,e tc14:28
*** jlvillal has quit IRC14:28
ajoirenab correct, API endpoint is another port listening for requests, right?14:28
irenabajo: this is my understanding14:29
ajook :)14:29
*** amuller has joined #openstack-meeting-314:29
ajoso, I mean different rest resources, vs single for types of rules...14:29
*** jlvillal has joined #openstack-meeting-314:29
ajoI have no strong preference for one of another,14:30
*** carl_baldwin has joined #openstack-meeting-314:30
vikram__To me having one is better.. it can help to minimize the coding effort14:30
ajoit was my understanding that having separate ones was preferable from armax POV14:30
ajoI guess having one, requires a big "switch" at the api endpoint, to create one rule or another14:30
irenabajo: I think we should go with option that allows easier extension for new type14:30
ajoand validate14:30
gsagiebut you will have single one, you need some code that parse and knows which attribute belongs to which type14:30
ajoapi endpoint I said again..14:31
gsagieif you14:31
ajoajo--14:31
ajo:)14:31
vhoward+1 arenab14:31
ajogsagie, yes, I guess that's it14:31
vikram__gsagie: but we can reuse most of it.14:31
ajovikram__, client coding doesn't need to be more complicated it's just a string in the middle of the URL   qos-%(type)s-rules14:32
ajoalso, from the cmdline interface,14:32
ajogoing one way or another could mean we have separate commands, or just one14:32
ajoI believe having just one could be messy because we may end up with a lot of optional commands which only apply to certain rules14:33
ajounless the argparser we use is capable of having another level of optional flags14:33
vikram__ajo: Thanks for the explanation... I got it .. having 1 cmd is better to manage i feel14:33
gsagieor maybe just /v2.0/qos-rules/<extension or type>/....14:34
vikram__ok14:34
*** nelsnelson has joined #openstack-meeting-314:34
ajogsagie, could be, yes...14:34
ajoI wonder if we have this kind of class inheritance somewhere in the project14:34
ajoand any API which does the dame14:34
ajodame->same14:34
ajoacross openstack14:34
*** vineetmenon has joined #openstack-meeting-314:35
*** shakamunyi has joined #openstack-meeting-314:35
*** rmschn has quit IRC14:35
ajook, we need to iron this parts out14:35
ajoI will look at the argument parser we use in the client, to figure out if we can put everything under a single command, while still having a clear help14:36
*** shakamunyi has quit IRC14:36
ajoabout what arguments apply to each rule type14:36
*** shakamunyi has joined #openstack-meeting-314:36
*** stevemar has joined #openstack-meeting-314:37
*** e0ne_ is now known as e0ne14:37
ajoand for the REST part, let's keep discussing on the spec.14:37
gsagiek14:37
irenabajo: +114:37
vikram__ok14:38
ajo#action ajo check if argument parser in the client can handle all rules in one set of commands while still providing granular control of which flags apply to each type14:38
ajo#undo14:38
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x927bb90>14:38
*** rmschn has joined #openstack-meeting-314:38
ajo#action ajo check if argument parser in the client can handle all rule types in one set of commands while still providing granular control of which flags apply to each type14:38
ajorules -> rule types14:38
*** dane_leblanc has joined #openstack-meeting-314:39
*** JeanBriceCombebi has quit IRC14:39
*** JeanBriceCombebi has joined #openstack-meeting-314:39
ajo#topic Traffic Classification considerations14:39
*** openstack changes topic to "Traffic Classification considerations (Meeting topic: neutron_qos)"14:39
ajoI believe most of you already read that part of the comments,14:39
ajoI was proposing to (when we do TC) create another data model to do traffic classification14:40
ajoso that it can be attached to rules14:40
irenabajo: +114:40
ajothis way we don't need to repeat the same filters for rules targetting the same type of traffic14:40
vikram__ajo: +114:41
irenabonce we get there, need to be careful when this object can be modified14:41
irenabnot to create too many update dependencies14:41
gsagieyes, good point14:41
ajoyes, as it will affect several rules14:41
ajoat that time we may need to analyze what's better14:42
ajowe either let them reattach each rule to a new TC14:42
ajoor...14:42
ajomodify the TC14:42
ajobut that means lots of rules could be updated at the same time14:42
ajofrom the user usability perspective it's probably simpler to let them change a TC14:42
ajomessaging could be short14:43
irenabthe impact can be high14:43
ajoyes it needs to be seriously considered14:44
irenabbut we can decide later what approach to take14:44
ajoyes14:44
ajoin an ovs / openflow world14:44
ajowe could make use of conjunctive rules14:44
vikram__A TC change impacting lot of rules.... Can this be a real use case ? I am not sure.. Is it a practical scenarion?14:45
ajoand just modify the rules in the conjunction... that is mapped to the TC14:45
ajovikram__, probably it could only happen if an administrator needs to correct a TC which was wrong14:45
ajoor make it more specific14:45
ajoprobably it's not going to ve a common use case14:45
ajoor...14:46
ajoor a CSP14:46
vikram__ok.. but that could not be frequent..14:46
ajosorry... nothing about CSPs :)14:46
ajobut.. we also have the same case with policies14:46
ajoif a CSP has a policy for his cloud14:46
ajoand it's changed,14:46
ajo(for example BW limit to 10mbps to certain level)14:46
ajoit may need to propagate to a lot of ports14:47
ajoBut , the admin could also create a new policy, and reattach the networks14:47
ajoone by one14:47
vikram__ok14:47
*** matrohon has quit IRC14:48
ajook, we have another point about "The ingress vs egress differences and issues."14:48
*** rmschn has quit IRC14:48
ajoprobably it's just a matter of documenting the scalability implications of modifiying a policy (or TC), or creating and switching...14:49
ajoAPI documentation I mean14:49
ajoI get you all bored :D14:50
ajook14:50
ajo#topic The ingress vs egress differences and issues14:50
*** openstack changes topic to "The ingress vs egress differences and issues (Meeting topic: neutron_qos)"14:50
sadasuajo: we are listening :-)14:50
vikram__i am with you till now:)14:51
irenabajo: you are just very verbose14:51
ajogaryk was making an interesting point in last meeting, about including an ingress/egress field14:51
ajoirenab: that's true :D14:51
ajoI can be either very shy, or very chatty... ;)14:51
sadasuI think the idea of including a direction field is a good one14:52
ajoI was looking at the implications of supporting egress & ingress control from the linux perspective14:52
ajolinux (in netfilter) has only direct support for egress control14:52
*** Sukhdev has joined #openstack-meeting-314:53
ajoegress is simpler because you can just tell the packet pushing VM or instance... "I can't take anything more", and the app get's blocked on send...14:53
sfinucanajo: Open vSwitch is the same14:53
sadasuI would expect the egress direction to be more useful than ingress14:53
ajogsagie had some ideas bout ingress (metering), but we haven't been able to check yet14:54
sfinucanthere's basic ingress metering, but that's it14:54
ajosfinucan, but we're not sure if we can make it drop packets or not above some rate14:54
vikram__is it documented somewhere?14:54
ajoOF1.3 metering, gsagie do you have the link somewhere?14:55
sfinucanIt is somewhere...but I don't recall where :)14:55
sfinucanI was testing it ~3 weeks ago. It dropped packets14:55
vikram__hehehe-:)14:55
ajothere are ways to do ingress (if we couldn't use metering for this), but they are twisted14:55
*** bknudson has quit IRC14:55
sfinucanbut it was a very rough estimate14:55
ajogenerally, involves creating a secondary tap/interface, where you send all the ingress traffic which should go to the instance, and then... you filter it's egress14:56
sfinucanthis should get you something useful -> "sudo ovs-vsctl set interface $IF_NAME ingress_policing_rate=1000"14:56
ajoyou bounce it back, and finter egress14:56
ajofilter14:56
sfinucanajo: sounds about right, yes14:56
vikram__thanks ajo will check it14:56
sadasuajo: +114:56
ajosfinucan, ok, we may check that,14:56
ajovikram__, if have time to check sfinucan : perfect14:56
sfinucanls14:57
ajo"test what sfinucan said" I mean, sorry14:57
vikram__ok will do that..14:57
ajohttps://github.com/mangelajo/ovs-experiments/blob/master/qos/qos_traffic_shapping.sh14:57
ajothis could help you testing14:57
ajohttps://github.com/mangelajo/ovs-experiments/blob/master/qos/qos_traffic_shapping.sh#L12414:57
ajohmm14:57
ajoit's actually what I did14:57
*** amuller has left #openstack-meeting-314:58
*** dane_leblanc has quit IRC14:58
ajobut it was limiting egress?14:58
ajomay be I got it inverted14:58
gsagiesorry14:58
gsagieback14:58
ajohi gsagie14:58
ajowe're near to the top of the hour14:58
gsagieegress is more usefull sadasu14:59
irenabajo: i  light of new feature request psocess14:59
gsagieok, anyone got to check the OF1.3 metering support in OVS?14:59
gsagiei will try to find out for next meeting (or before)14:59
ajothanks gsagie14:59
irenabprocess, do you plan to continue over existing spec  till it gets accepted?14:59
ajo#action vikram__  to check ingress_policing_rate15:00
ajo#action gsagie to check OF1.3 metering and ratelimiting support in OVS15:00
*** JeanBriceCombebi has quit IRC15:00
ajoirenab, yes, it's a good field for discussion15:00
ajothen, depending on what's decided, we could move it to devref15:00
ajoor shrink it / split it15:01
ajodoes it sound reasonable?15:01
irenabajo: yes15:01
ajook let's endmeeting for today15:02
ajo#endmeeting15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Wed May  6 15:02:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.log.html15:02
ajothanks everybody :)15:02
vikram__bye15:02
ajovikram__,15:02
sadasuthanks all!15:02
vhowardbye, thank you15:02
sfinucancheers15:02
ajoif you can, use my script to verify the ingress limiting,15:02
ajoit's very simple, just run it...15:03
vikram__ok ..15:03
vikram__will try15:03
irenabbye15:03
ajoand verify the output, may be I mixed up things and I'm getting it inverted or something I thought it was egress15:03
vikram__thanks ajo15:03
ajobut clearly, says "ingress" :)15:03
ajobye :)15:03
vikram__:)15:03
*** cbits has left #openstack-meeting-315:03
*** vikram__ has quit IRC15:03
*** sfinucan has left #openstack-meeting-315:04
*** marun has joined #openstack-meeting-315:04
*** JeanBriceCombebi has joined #openstack-meeting-315:07
*** Sukhdev has quit IRC15:10
*** pkoniszewski has joined #openstack-meeting-315:13
*** armax has joined #openstack-meeting-315:13
*** fallenpegasus has joined #openstack-meeting-315:15
*** sadasu has quit IRC15:16
*** lennyb has quit IRC15:18
*** bpokorny has joined #openstack-meeting-315:24
*** krtaylor has quit IRC15:31
*** LouisF has joined #openstack-meeting-315:33
*** Sukhdev has joined #openstack-meeting-315:43
*** yamahata has joined #openstack-meeting-315:46
*** bknudson has joined #openstack-meeting-315:46
*** egallen has quit IRC15:50
*** moshele has quit IRC15:54
*** yalie has joined #openstack-meeting-315:55
*** scheuran has quit IRC15:57
*** wojdev has joined #openstack-meeting-315:58
*** shakamunyi has quit IRC15:58
*** sarob has joined #openstack-meeting-316:00
*** wojdev has quit IRC16:05
*** eghobo has joined #openstack-meeting-316:05
*** wojdev has joined #openstack-meeting-316:06
*** banix has joined #openstack-meeting-316:08
*** bknudson has quit IRC16:09
*** JeanBriceCombebi has quit IRC16:12
*** bknudson has joined #openstack-meeting-316:14
*** iovadia has quit IRC16:15
*** LouisF has quit IRC16:15
*** evgenyf has quit IRC16:16
*** dheeraj-gupta-4 has joined #openstack-meeting-316:16
*** pettori has joined #openstack-meeting-316:17
*** wojdev has quit IRC16:24
*** wojdev has joined #openstack-meeting-316:26
*** jcoufal_ has quit IRC16:27
*** pkoniszewski has quit IRC16:27
*** safchain has quit IRC16:31
*** krtaylor has joined #openstack-meeting-316:35
*** wojdev has quit IRC16:36
*** e0ne has quit IRC16:43
*** wojdev has joined #openstack-meeting-316:44
*** shakamunyi has joined #openstack-meeting-316:49
*** marun has quit IRC16:49
*** marun has joined #openstack-meeting-316:51
*** sahid has quit IRC16:54
*** wojdev has quit IRC16:54
*** peristeri has quit IRC16:57
*** mwang2 has joined #openstack-meeting-316:58
*** igordcard_ has quit IRC16:59
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed May  6 17:00:34 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
*** banix has quit IRC17:00
bauzas\o17:00
alaskihello hello17:00
melwitto/17:00
dheeraj-gupta-4o/17:00
*** tqtran has joined #openstack-meeting-317:01
alaski#topic Cellsv1 testing17:01
*** openstack changes topic to "Cellsv1 testing (Meeting topic: nova_cells)"17:01
vineetmenono/17:01
alaskihttp://goo.gl/lZRucu17:01
alaskia fix went in late yesterday for cellsv117:01
dansmitho/17:01
alaskifailures are low right now, but there's not much data yet17:02
alaskithere have been three failures, two of which were on stable branches17:02
bauzassounds nicer17:02
alaskiwhich does raise the question: can we vote on master only?  or should we backport to stable?17:03
alaskiwell, probably not an or17:03
dansmithI think we can vote only on master17:03
alaskiokay, good17:03
bauzasalaski: you mean having the job set to voting for master only ?17:03
alaskiyes17:03
bauzasmmm, AFAIK the job is set to vote or not, and then we call it for any project17:04
*** wojdev has joined #openstack-meeting-317:04
alaskiI know that jenkins wasn't happy recently, so I don't know how good the data we have is.  but we should watch it closely now17:04
*** banix has joined #openstack-meeting-317:05
alaskibauzas: okay.  I guess we need to look into it to see what we can do17:05
*** shakamunyi has quit IRC17:05
bauzasalaski: https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L652-L65317:05
*** SumitNaiksatam has quit IRC17:05
bauzasalaski: we can add a branch17:06
bauzasalaski: so the answer to your question is yes17:06
alaskiokay17:06
bauzaswho actions that ?17:06
alaskiI will propose some backports for stable, but in the meantime we should separate failures by branch17:07
*** pettori has quit IRC17:07
alaskiand see how close we are to being good on master17:07
alaskibauzas: it's not needed yet, was just a question17:07
bauzasbuild_name:"check-tempest-dsvm-cells" AND message:"Worker Balance" AND build_status:"FAILURE" AND build_branch:"master" gives us only 2 failures since your patch merged AFAICS17:08
bauzasbut sure we can leave it running for another round, sure17:08
alaskiit's been less than a day at this point17:09
bauzasagreed17:09
alaski#topic Specs17:09
*** openstack changes topic to "Specs (Meeting topic: nova_cells)"17:09
alaskithe requestspec changes merged17:10
bauzasyup17:10
bauzasI'm working on the implem now17:10
alaskiso https://review.openstack.org/#/c/176078/ is next up for that series17:10
*** VW_ has quit IRC17:10
alaskibauzas: great17:10
bauzasalaski: should provide a WIP patch soon17:11
alaskiwhen that gets to a good point I'll start working on perisistence, if the spec is merged17:11
bauzasalaski: https://review.openstack.org/#/c/76234 is a dependency tho17:11
*** VW_ has joined #openstack-meeting-317:11
alaskiI've completely changed the scope of https://review.openstack.org/#/c/141486/17:11
alaskischeduler interactions with cells17:11
alaskibauzas: ok17:12
*** yamahata has quit IRC17:12
alaskiwhile writing that last spec I found that we're missing a table to map hosts to cells, so I'll put something up for that17:12
*** shwetaap has quit IRC17:13
bauzascool17:13
alaskiand I don't have a fleshed out spec for storing enough data to return an instance for a list/show17:13
*** yalie has quit IRC17:14
alaskiso I need that as well17:14
dheeraj-gupta-4alaski: Mapping hosts to cells seems counter-intuitive17:14
*** wojdev has quit IRC17:14
bauzasdheeraj-gupta-4: why ?17:14
dheeraj-gupta-4A compute node can be added to a child cell any-time17:14
*** VW_ has quit IRC17:14
dheeraj-gupta-4API cell shouldn't know or care how/when that is done17:14
*** [1]evgenyf has joined #openstack-meeting-317:15
*** VW_ has joined #openstack-meeting-317:15
alaskidheeraj-gupta-4: it needs to know where to send messages for it17:15
dheeraj-gupta-4it only needs to know child cell17:15
alaskiright, but it needs to get that info from somewhere17:16
dheeraj-gupta-4maybe the child cell should handle the internals17:16
dheeraj-gupta-4but that's just over top of my head17:16
alaskithere are two cases here where we need to know how to route17:16
bauzasdheeraj-gupta-4: how do you route calls ?17:16
alaskithe scheduler returns a host, which cell is it in?17:16
dheeraj-gupta-4maybe the spec will answer those questions17:16
alaskithe host api needs to update/query a host, where is it?17:16
*** igordcard_ has joined #openstack-meeting-317:17
dheeraj-gupta-4hmm... cellsv1 style naming maybe17:17
dheeraj-gupta-4*shudders*17:17
alaskiyeah :)17:17
alaskiI think that for the most part a cell doesn't need to know it's a cell, or which cell it is17:18
alaskithat's a label the api cares about17:18
vineetmenondheeraj-gupta-4: any reservations against cell-host mapping?17:18
alaskithough that's muddled with scheduling slightly?17:18
alaskiwoops, didn't mean a ? there17:18
dheeraj-gupta-4vineetmenon: No it just seemed odd for a moment17:18
alaskidheeraj-gupta-4: I understand the hesitation.  I'm open to alternatives that aren't named based.17:19
dheeraj-gupta-4yes.... I see the motivation now17:19
*** shakamunyi has joined #openstack-meeting-317:20
dheeraj-gupta-4wasn't clear when you first mentioned it17:20
alaskiokay17:20
bauzasdheeraj-gupta-4: I think you need to forget cells v1 :)17:20
dheeraj-gupta-4bauzas: :)17:20
bauzasthere should be no longer child and parent cells, just cells and api17:20
dheeraj-gupta-4cool17:21
alaskiso outside of the specs I mentioned, and one for multiple rpc endpoints, I think that's about what's on our plate this cycle17:21
alaskiand also the scheduling stuff that's not really cell specific but affects us17:21
alaskianything else on specs?17:22
alaski#topic Open Discussion17:22
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:22
alaskiif so it can go here17:22
alaskianyone have something to bring up?17:22
dheeraj-gupta-4alaski: During Kilo closure one patch about talking to multiple DBs got held up17:23
bauzasjust one question, could we maybe ask again people if they are happy with moving this alternate time one hour before ?17:23
*** moshele has joined #openstack-meeting-317:23
bauzason a personal note, that's just conflicting my w/l balance :)17:23
alaskibauzas: the 2200 one?17:23
dheeraj-gupta-4https://review.openstack.org/#/c/161906/17:23
bauzasnah, I'm fine with this one, the 1700 one17:24
bauzasthis time17:24
alaskidheeraj-gupta-4: oh, thanks for bring that up17:24
alaskithat will be necessary as well17:24
alaskiI'm not sure where it falls spec wise at this point17:24
*** moshele has quit IRC17:24
dansmithmoving the 1700UTC one an hour earlier will have conflicts for me17:25
alaskidheeraj-gupta-4: it might be something we can just open a bp for17:25
dheeraj-gupta-4alaski: okay17:25
bauzasdansmith: no worries, just asking the question :)17:25
bauzasalaski: need resubmitting the spec ?17:25
bauzashttps://blueprints.launchpad.net/openstack/?searchtext=cells-v2-mapping gives 404 ;(17:25
*** ivar-lazzaro has joined #openstack-meeting-317:26
alaskibauzas: the spec was close as implemented afaik17:26
bauzasalaski: so it was partial because it misses that change, right ?17:26
bauzasmissed even17:26
alaskibauzas: I think we should go for a bp, it's not a big change17:26
bauzasalaski: agreed17:27
*** SumitNaiksatam has joined #openstack-meeting-317:27
alaskialso, sounds like we should keep this time for the meeting.  but if it interferes you can leave me comments before the meeting and follow up with the logs17:27
*** ivar-lazzaro has quit IRC17:27
vineetmenonalaski: so the alternate timing aren't applicable anymore?17:28
bauzasalaski: ack17:28
alaskivineetmenon: it still is.  1700 and 210017:28
*** ivar-lazzaro has joined #openstack-meeting-317:28
bauzasit's just all about family time for dinner :)17:28
bauzasbut that's fine17:29
dheeraj-gupta-4bauzas: 1700 UTC or 1600 UTC both work for me17:29
bauzasI'll handle that17:29
bauzasdheeraj-gupta-4: dansmith has conflicts for 1600, let's stick with the current time17:29
alaskibauzas: totally understood.  hard to get everyone with so many timezones17:29
vineetmenonalaski: ack17:29
dheeraj-gupta-4bauzas: ok17:29
*** mattgriffin has quit IRC17:29
*** clu_ has joined #openstack-meeting-317:30
alaskibauzas: lets revisit later, perhaps at the next dst shift17:30
alaskianything else for today?17:31
bauzasalaski: again, no worries17:31
alaskibauzas: okay17:32
bauzascrickets ?17:32
alaskiyep17:32
alaskithanks everyone!17:32
alaski#endmeeting17:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:32
openstackMeeting ended Wed May  6 17:32:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-05-06-17.00.html17:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-05-06-17.00.txt17:32
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-05-06-17.00.log.html17:32
*** dheeraj-gupta-4 has left #openstack-meeting-317:32
*** vineetmenon has quit IRC17:33
*** slaweq has joined #openstack-meeting-317:35
*** ivar-laz_ has joined #openstack-meeting-317:35
*** mattfarina has joined #openstack-meeting-317:36
*** mattgriffin has joined #openstack-meeting-317:37
*** shwetaap has joined #openstack-meeting-317:37
*** ivar-lazzaro has quit IRC17:38
*** btully has joined #openstack-meeting-317:38
*** emagana has joined #openstack-meeting-317:39
*** alexpilotti has quit IRC17:41
*** VW_ has quit IRC17:41
*** slaweq has quit IRC17:43
*** Sukhdev has quit IRC17:43
*** s3wong has joined #openstack-meeting-317:45
*** alexpilotti has joined #openstack-meeting-317:46
*** Sukhdev has joined #openstack-meeting-317:47
*** Swami has joined #openstack-meeting-317:48
*** pettori has joined #openstack-meeting-317:49
*** e0ne has joined #openstack-meeting-317:50
*** alexpilotti has quit IRC17:51
*** alexpilotti has joined #openstack-meeting-317:52
*** banix has quit IRC17:52
*** VW_ has joined #openstack-meeting-317:54
*** wojdev has joined #openstack-meeting-317:55
*** banix has joined #openstack-meeting-317:56
*** ongk_ has joined #openstack-meeting-317:58
*** wojdev has quit IRC18:05
*** wojdev has joined #openstack-meeting-318:08
*** markmcclain has quit IRC18:09
*** ongk_ has quit IRC18:10
*** banix has quit IRC18:10
*** reed has quit IRC18:11
*** Sukhdev has quit IRC18:14
*** reed has joined #openstack-meeting-318:14
*** e0ne_ has joined #openstack-meeting-318:15
*** e0ne has quit IRC18:15
*** banix has joined #openstack-meeting-318:15
*** e0ne has joined #openstack-meeting-318:17
*** wojdev has quit IRC18:18
*** e0ne_ has quit IRC18:20
*** SridarK has joined #openstack-meeting-318:20
*** mrmartin has joined #openstack-meeting-318:21
*** rushiagr is now known as rushiagr_away18:23
*** vikram__ has joined #openstack-meeting-318:24
*** s3wong has quit IRC18:26
*** baoli_ has quit IRC18:27
*** badveli has joined #openstack-meeting-318:27
*** s3wong has joined #openstack-meeting-318:27
*** fallenpegasus has quit IRC18:28
*** SumitNaiksatam_ has joined #openstack-meeting-318:28
*** SumitNaiksatam has quit IRC18:30
*** SumitNaiksatam_ is now known as SumitNaiksatam18:30
*** slaweq has joined #openstack-meeting-318:30
vishwanathjhi SumitNaiksatam18:30
slaweqhello18:30
badvelihello all18:30
SumitNaiksatamvishwanathj: hi18:30
SridarKHi All18:30
SumitNaiksatamslaweq: badveli hi18:30
vishwanathjHi All18:30
badvelihello sumit and all18:30
*** pettori has left #openstack-meeting-318:30
xgermanhi18:30
vikram__hi18:31
SumitNaiksatamxgerman: vikram__ SridarK: hi18:31
SumitNaiksatam#startmeeting Networking FWaaS18:31
openstackMeeting started Wed May  6 18:31:27 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:31
*** pc_m has joined #openstack-meeting-318:31
*** Yi has joined #openstack-meeting-318:31
pc_mhi18:31
SumitNaiksatamany announcements any one wants to share?18:31
SumitNaiksatampc_m: hi18:31
SumitNaiksatam#topic Bugs18:32
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:32
sballehi18:32
SumitNaiksatamsballe: hi18:32
SumitNaiksatamwe still have the high priority doc bug18:33
SumitNaiksatamSridarK: thanks for posting the new patch set18:33
*** yamahata has joined #openstack-meeting-318:33
*** lblanchard has quit IRC18:33
SridarKSumitNaiksatam: no worries - sorry learning this stuff :-)18:33
SumitNaiksatamSridarK: badveli any other critical/high show up on your radar?18:33
SridarKSumitNaiksatam: also thanks to pc_m for review and Diane F for fixing things18:34
SridarKSumitNaiksatam: nothing from me18:34
*** lblanchard has joined #openstack-meeting-318:34
SumitNaiksatampc_m: thanks as always18:34
SumitNaiksatamyeah did notice diane posting immediate fixes18:34
pc_msure np18:34
SumitNaiksatamis yushiro here?18:35
SumitNaiksatamsorry i did not follow up on #link https://review.openstack.org/#/c/176589/18:35
SumitNaiksatamSridarK: do you know why the Cisco CI failed on this?18:35
SridarKSumitNaiksatam: not sure - i will follow up on this18:36
SridarKSumitNaiksatam: i don't think we should have any impact with the change18:36
SumitNaiksatamSridarK: thanks18:36
SridarKnp at all18:37
vishwanathjseems like there are lot of bugs related to FWaaS when using REST API...seeing that pattern18:37
SumitNaiksatamany other bugs to discuss?18:37
SumitNaiksatamvishwanathj: “lots” of bugs?18:37
vishwanathjlots ==> 2 to 3 :)18:37
SumitNaiksatamvishwanathj: i think those or validation bugs18:38
SumitNaiksatamor -> are18:38
SumitNaiksatamadding tighter validation to existing cases18:38
SumitNaiksatami am referring to a couple of those filed by yudhiro18:38
SumitNaiksatam*yushiro18:38
vishwanathjthat's how I know that there are 2 or 3...yushiro has been finding them18:38
SumitNaiksatamvishwanathj: but sorry to stop you, did you have a follow up comment to that?18:39
vishwanathjI was going to ask if we are lacking tests18:39
SumitNaiksatamvishwanathj: i think in general more test cases is always desired18:40
vishwanathjso that we can look at it from that angle during reviews for future code commits18:40
vishwanathjok18:40
SumitNaiksatamvery few projects would be able to say - we are completely covered on the tests :-)18:41
vishwanathjno more comments from me18:41
vishwanathjagreed18:41
SumitNaiksatamso yes definitely, any effort to add test coverage will be very much appreciated18:41
*** Yi has quit IRC18:41
SridarKi am also seeing this as a positive thing that more folks are looking at FWaaS18:41
SumitNaiksatamSridarK: true18:41
vishwanathjtrue18:41
SumitNaiksatamyeah the more people beat it, the more things will be uncovered18:41
SumitNaiksatamok if nothing more on bugs, lets move on18:42
SumitNaiksatamoh before we move on, SridarK is the doc patch complete, or do you need help with wrapping it up18:42
SumitNaiksatami am asking because vishwanathj was offering to help yesterday18:42
*** mattfarina has quit IRC18:42
*** markmcclain has joined #openstack-meeting-318:42
SridarKSumitNaiksatam: thanks - i think i am good - i am hoping to get the policy and rule stuff pushed up today18:42
SridarKSumitNaiksatam: will definitely need validation once that happens to make sure all attributes are covered18:43
SumitNaiksatamSridarK: thanks18:43
SridarKSumitNaiksatam: but i will shout out if i need some help :-)18:43
SumitNaiksatameasy way to review for the rest of the team would be to look at the rendered docs18:44
SumitNaiksatamrather than reading the source18:44
SridarKthis has been a pattern match and reproduce experience :-)18:44
SumitNaiksatamSridarK: :-)18:44
SumitNaiksatamok moving on18:44
SumitNaiksatam#topic Liberty Features18:45
*** openstack changes topic to "Liberty Features (Meeting topic: Networking FWaaS)"18:45
SumitNaiksatamlast week i requested the team to update participate in updating the wiki #link https://wiki.openstack.org/wiki/Meetings/FWaaS18:45
SumitNaiksatami would hope that as we propose more features they get added to: #link https://wiki.openstack.org/wiki/Meetings/FWaaS#Blueprint_Tracking18:46
SumitNaiksatamFWaaS Rules Direction: #link https://review.openstack.org/#/c/17134018:46
SumitNaiksatamslaweq: over to you18:46
slaweqyep18:46
slaweqI'm here18:47
slaweqhave You got any questions or sugestions about that?18:47
SridarKslawek hi - had one query for discussion18:47
slaweqyes?18:47
*** badveli has quit IRC18:47
*** markvoelker has quit IRC18:47
*** Longgeek has quit IRC18:47
*** lsmola has quit IRC18:47
*** jtomasek has quit IRC18:47
*** smccully has quit IRC18:47
*** aleksandr_null has quit IRC18:48
*** russellb has quit IRC18:48
*** haleyb has quit IRC18:48
*** SotK has quit IRC18:48
*** mrda has quit IRC18:48
*** yamahata has quit IRC18:48
*** mrmartin has quit IRC18:48
*** e0ne has quit IRC18:48
*** jkoelker has quit IRC18:48
*** devananda has quit IRC18:48
*** dobson has quit IRC18:48
SumitNaiksatamSridarK: please go ahead18:48
SridarKslaweq: was wondering if had thoughts abt the direction being associated with a collection of rules as a policy or as a firewall18:48
*** badveli has joined #openstack-meeting-318:48
SumitNaiksatami hope we didnt lose anyone in the split18:48
SridarKslaweq: full disclosure: as our vendor implementation we associate direction with the firewall to say " i want the firewall to be applied on all ingress traffic or egress traffic"18:49
slaweqI didn't think about it18:49
*** yamahata has joined #openstack-meeting-318:49
*** mrmartin has joined #openstack-meeting-318:49
*** e0ne has joined #openstack-meeting-318:49
*** dobson has joined #openstack-meeting-318:49
*** devananda has joined #openstack-meeting-318:49
*** jkoelker has joined #openstack-meeting-318:49
*** sendak.freenode.net changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:49
*** badveli is now known as 43UAB93S318:49
*** badveli has joined #openstack-meeting-318:49
*** markvoelker has joined #openstack-meeting-318:49
*** Longgeek has joined #openstack-meeting-318:49
*** lsmola has joined #openstack-meeting-318:49
*** jtomasek has joined #openstack-meeting-318:49
*** smccully has joined #openstack-meeting-318:49
*** aleksandr_null has joined #openstack-meeting-318:49
*** russellb has joined #openstack-meeting-318:49
*** haleyb has joined #openstack-meeting-318:49
*** SotK has joined #openstack-meeting-318:49
*** mrda has joined #openstack-meeting-318:49
SridarKslaweq: i am okay with what u have - but wanted to ask if that would make sense as well18:49
SridarKfwaas folks here ?18:50
slaweqI don't know, I was thinking about it more like about of iptables for example18:50
SumitNaiksatamSridarK: i am still here :-)18:50
SridarK:-)18:50
*** mattfarina has joined #openstack-meeting-318:50
badvelisome problem, but i am here18:50
slaweqso You can apply rule to specify "chain" by setting direction on it18:50
SridarKsorry some activity going on at least as i see it in my viewer18:50
SumitNaiksatamyeah, there was a network split18:50
vishwanathji am still here....but saw a bunch of people leave in batches and join in batches18:50
*** 43UAB93S3 has quit IRC18:50
SridarKslaweq: just a thought to discuss if it makes sense and evaluate18:51
vikram__yes18:51
* pc_m not here mentally :)18:51
SumitNaiksatamanyway, please continue, i think we did not lose anyone18:51
SumitNaiksatampc_m: lol!18:51
*** mattfarina has quit IRC18:51
xgerman+ for iptables18:51
slaweqok, so You think about something like "ingrees policy" and "egress policy"18:51
SridarKslaweq: i will post on the review - but thought we can do a quick discussion here too18:51
slaweqinstead of rules18:51
SridarKslaweq: we don't have that notion on policy - we have  single policy model18:52
SumitNaiksatamSridarK: is it something you envision as an additional feature to what you slaweq has already proposed?18:52
SridarKbut sort of to say "lets FW all ingress traffic"18:52
SumitNaiksatamor is it instead18:52
SridarKSumitNaiksatam: no just looking at the notion of direction being applied at the rule level18:52
slaweqimho if you want to firewall all ingress traffic You can put rule to allow all egrees and rules to filter ingress traffic18:53
slaweqfor example18:53
SridarKslaweq: yes for sure18:53
SumitNaiksatamslaweq: in your observation the granular usage in more prevalent?18:54
SridarKslaweq: just the question of granularity, the opposing argument as in ur proposal would be in a policy u may want some rules to be for ingress some for egress18:54
SumitNaiksatamin -> is18:54
SumitNaiksatamSridarK: just to clarify, did you mean associating the direction with a firewall policy or a firewall?18:55
SridarKslaweq: the granular is more flexible, just to dot the i's i ask the question18:55
SridarKSumitNaiksatam: yes exactly18:55
SumitNaiksatami mean in the context of the vendor implementation18:55
*** dloi_ has joined #openstack-meeting-318:55
SridarKSumitNaiksatam: yes18:55
vikram__SridarK: Did you mean associating direction to a bundle of rules?18:56
SumitNaiksatamfor our model, firewall can be associated with exactly one policy, so if effectively the direction is on the firewall (if its associated with policy)18:56
*** pkoniszewski has joined #openstack-meeting-318:56
SridarKvikram__: yes was asking if that is something that would make sense18:56
SridarKSumitNaiksatam: yes exactly18:56
SumitNaiksatamokay lets post the comments on the review18:57
SridarKslaweq: i am ok with the proposal - just wanted to bring up the discussion and to get ur thoughts18:57
SumitNaiksatamslaweq: sorry it took longer to get to this stage of the discussion18:57
vikram__but in the current model how to achieve it?18:57
slaweqbut IMHO if direction will be associated with policy or firewall instead of rules then You can't filter some ingress and some egress traffic, yes?18:57
SridarKslaweq: yes - u are correct18:57
slaweqif firewall could have more than one policy then it may sense for me18:58
SumitNaiksatami think garnular definitely affords more flexibility, however from a usage perspective it might also be easier to define the direction for the policy (rather than having to apply inidividually, assuming that is a predominant use case)18:58
*** lhcheng has joined #openstack-meeting-318:58
SridarKslaweq: definitely more flexibility - just wanted to look at it from a typical usage point of view18:58
vikram__sumit: +118:59
SumitNaiksatamok moving on to badveli’s spec and patch: #link https://review.openstack.org/#/c/9413318:59
vishwanathjslaweq, let me know if you need any help in coming up with Horizon blueprint and Horizon code for this?19:00
SridarKslaweq: sorry for bringing this up late - intent is not derail - just to make sure we have covered all aspects19:00
*** mattfarina has joined #openstack-meeting-319:00
slaweqvishwanathj: thx, I will contact with You about it19:00
SumitNaiksatamSridarK: good point to bring up though19:00
*** [1]evgenyf has quit IRC19:00
SridarKSumitNaiksatam: should have asked even earlier - brain needs more recharging :-)19:00
slaweqSridarK: it's ok for me :) great that You are asking about it19:01
SumitNaiksatamslaweq: +1, vishwanathj indeed thanks for offering to help out, thats great!19:01
SumitNaiksatambadveli: there?19:01
badveliyes19:01
slaweqok guys, I really have to leave now, thx for talking about my BP19:01
SumitNaiksatamwere you able to repurpose your spec for liberty?19:01
SumitNaiksatamslaweq: thanks a bunch for joining, we will got to gerrit for your spec19:01
badvelinot yet sumit,19:02
*** slaweq has quit IRC19:02
SumitNaiksatambadveli: ok19:02
badvelisumit, is some one already did the same  it might be easier for me to talk19:03
badvelito them and get this quickly19:03
SumitNaiksatambadveli: i havent checked off late, but you can look at the commits on the neutron-specs tree19:03
SumitNaiksatamlast week i also brought up the topic about updating the “project plan” wiki page19:03
*** Sukhdev has joined #openstack-meeting-319:03
SumitNaiksatambased on the features we are working on19:03
badvelithanks sumit19:03
SumitNaiksatamvikram__: perhaps you can update in the context of the firewall rules direction19:04
SumitNaiksatam#link https://wiki.openstack.org/wiki/Neutron/FWaaS/LibertyPlan19:04
SumitNaiksatamSridarK: are you planning to add the zones spec?19:04
vikram__sure19:04
SumitNaiksatamvikram__: thanks19:04
SridarKSumitNaiksatam: yes will do so19:04
SridarKAnd update -19:04
SumitNaiksatamSridarK: there?19:06
SridarKSumitNaiksatam: yes19:06
SumitNaiksatamoh i thought you were saying there is an additional update in that context :-)19:06
SridarKSumitNaiksatam: sorry - i thought my link bounced :-)19:06
SridarKSumitNaiksatam: no i will add the spec and update the link - need to close on some issues - some thinking prompted some my questions on the direction spec too19:07
SumitNaiksatamvishwanathj: i believe you were also interested in this, so you and SridarK can sync up19:07
SridarKSumitNaiksatam: yes we bounced some ideas on this19:07
SumitNaiksatamany other features that anyone wants to bring up?19:07
vishwanathjSumitNaiksatam, definitely would like to work under SridarK guidance19:07
*** ivar-laz_ has quit IRC19:07
SridarKvishwanathj: will ping u and Karthik for some more thoughts too19:08
vishwanathjSridarK, let me know if we need to have additional conversation19:08
*** ivar-lazzaro has joined #openstack-meeting-319:08
vishwanathjok19:08
SridarKvishwanathj: :-) yes19:08
SumitNaiksatamanyone planning any other features for Liberty?19:08
SumitNaiksatamyamahata: you had mentioned L4-7 classification and filtering19:09
SumitNaiksatamyamahata: any update on the refernce implementation candidates?19:09
SridarKSumitNaiksatam: i think yushiro also had some thoughts but i think he is traveling19:09
SumitNaiksatamSridarK: oh okay, hopefully he will be at the design summit19:10
SridarKSumitNaiksatam: yes i think he will be there19:10
SumitNaiksatamnice19:10
SumitNaiksatamperhaps yamahata is not around19:10
SumitNaiksatam#topic Vendor drivers19:11
*** openstack changes topic to "Vendor drivers (Meeting topic: Networking FWaaS)"19:11
SumitNaiksatamany planned changes to the vendor drivers during liberty?19:11
SumitNaiksatamif so please update: https://wiki.openstack.org/wiki/Neutron/FWaaS/LibertyPlan19:11
SridarKSumitNaiksatam: would vendor stuff come out of the main tree in  L ?19:11
SumitNaiksatamso that we can track the reviews and progress of the patches19:11
SumitNaiksatamSridarK: i dont know19:11
SumitNaiksatampc_m: do you know if we are pulling out the vendor drivers from *aas in liberty?19:12
SridarKSumitNaiksatam: ok - will be interesting to see if we follow as for neutron19:12
pc_mSumitNaiksatam: Haven't heard anything19:12
pc_mSumitNaiksatam: I'm looking at pulling Cisco VPN drivers out, but no community drive to do that.19:13
SumitNaiksatampc_m: i was not aware of either19:13
SumitNaiksatampc_m: you feel that its a better model to pull the vendor driver out?19:13
pc_mSumitNaiksatam: yeah, gives vendor ability to modify independent of community work, and in VPN there are so few people and cores to review that it'll be easier for vendor to get approvals.19:14
SumitNaiksatampc_m: completely understand19:15
SumitNaiksatamone advantage of being in tree when there are smaller number of drivers is that its easier to keep the drivers in sync with changes in the project19:15
SumitNaiksatamthey get more attention19:16
SridarKSumitNaiksatam: yes the breakages are more obvious19:16
SumitNaiksatambut one can also argue that with a good functional 3rd party CI you can catch things quickly19:16
*** salv-orl_ has joined #openstack-meeting-319:16
SumitNaiksatamanyway19:16
SumitNaiksatam#topic Functional Tests19:17
*** openstack changes topic to "Functional Tests (Meeting topic: Networking FWaaS)"19:17
SumitNaiksatambadveli: any progress in your exploration?19:17
badvelijust started putting things19:17
SumitNaiksatambadveli: nice19:17
badvelitried an experiment code19:17
SumitNaiksatambadveli: nice19:17
badveliin unit tests19:17
badvelidirectly19:17
SumitNaiksatambadveli: okay19:17
badveliusing name space ping19:17
badvelitry to set up the actual rules instead of mock19:18
badveliby using the snat name space19:18
*** yamahata has quit IRC19:18
*** mrmartin has quit IRC19:18
*** e0ne has quit IRC19:18
*** jkoelker has quit IRC19:18
*** devananda has quit IRC19:18
SumitNaiksatambadveli: with a view to making concrete progress, and faster, can i suggest that (a) you document your exploration on the wiki page19:18
SumitNaiksatam(b) if you can post a WIP patch with the test code you have written19:19
badveliyes, i can do that19:19
*** yamahata has joined #openstack-meeting-319:19
*** mrmartin has joined #openstack-meeting-319:19
*** e0ne has joined #openstack-meeting-319:19
*** devananda has joined #openstack-meeting-319:19
*** jkoelker has joined #openstack-meeting-319:19
SumitNaiksatamthat way other folks can also jump in and split the work with you19:19
*** mrmartin has quit IRC19:19
*** salv-orlando has quit IRC19:19
*** mrmartin has joined #openstack-meeting-319:19
SumitNaiksatambadveli: thanks for the update19:20
SumitNaiksatam#topic Open Discussion19:20
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:20
badvelithanks sumit19:20
pc_mYou may want to look at VPN functional test for ideas.19:20
SumitNaiksatamvikram__: were you able to get your devstack setup going with kilo?19:20
badvelithanks pc_m, i will take a look19:20
SumitNaiksatambadveli: pc_m is a great help19:20
pc_mnothing committed yet, but out for review.19:21
badveliyes thanks pcm_m19:21
pc_mbadveli: https://review.openstack.org/15974619:21
SumitNaiksatampc_m has been blazing the trail in this regard, so please take his guidance19:21
badvelii will take an example that will make my life easier19:21
SumitNaiksatampc_m: thanks19:21
*** vikram__ has quit IRC19:22
pc_mI did a bunch to setup fucntional tests to not stack devstack, but instead to do like Neutron and just configure.19:22
SumitNaiksatamdo we need to sync up on anything with regards to planning for the Liberty design summit sessions?19:22
pc_mThat commit is https://review.openstack.org/16811519:22
SumitNaiksatampc_m: thanks19:22
SridarKSumitNaiksatam: should we set a time where we can meet around a table at Vancouver ?19:23
vishwanathjSumitNaiksatam, FYI: pc_m and I had a quick chat regarding notification registration in FirewallService object.....a bug should be sufficient to track this was our conclusion. I will take the action item to open the bug and work with pc_m to deliver a code fix in liberty.19:23
*** vikram__ has joined #openstack-meeting-319:24
SumitNaiksatamvishwanathj: great, thanks for the update (please feel free to add it to the agenda for future tracking)19:25
SumitNaiksatamSridarK: +1 to that19:25
*** absubram has joined #openstack-meeting-319:25
SumitNaiksatamanything else to discuss today?19:26
SridarKSumitNaiksatam: no i am good19:27
SumitNaiksatamanyone else want to bring up anything?19:27
badvelinothing from my side19:27
SumitNaiksatamalrighty, thanks all for joining!19:28
pc_mYou guys meeting next week?19:28
SumitNaiksatamoh yeah just wanted to ask19:28
SumitNaiksatamshall we skip next week’s meeting?19:28
SumitNaiksatamand meet directly at the summit?19:28
SridarKSumitNaiksatam: sure okay bye me -19:28
vishwanathjsounds good to me19:28
badvelibye all19:28
vikram__bye19:28
SumitNaiksatamokay, so i will send out an email to -dev19:28
SumitNaiksatampc_m: thanks for bringing that up ;-)19:28
*** coolsvap|afk has quit IRC19:28
SumitNaiksatamalright, bye all!19:29
SridarKbye all19:29
SumitNaiksatamsee you in vancouver!19:29
pc_mbye!19:29
*** pc_m has left #openstack-meeting-319:29
SumitNaiksatam#endmeeting19:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:29
openstackMeeting ended Wed May  6 19:29:26 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-05-06-18.31.html19:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-05-06-18.31.txt19:29
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-05-06-18.31.log.html19:29
*** SridarK has quit IRC19:29
*** coolsvap|afk has joined #openstack-meeting-319:31
*** badveli has left #openstack-meeting-319:36
*** vikram__ has quit IRC19:42
*** Piet has joined #openstack-meeting-319:42
*** ajo has quit IRC19:44
*** mwang2_ has joined #openstack-meeting-319:45
*** s3wong has quit IRC19:45
*** Aish has joined #openstack-meeting-319:45
*** s3wong has joined #openstack-meeting-319:45
*** jwang has joined #openstack-meeting-319:47
*** mwang2 has quit IRC19:47
*** Yi has joined #openstack-meeting-319:49
*** baoli has joined #openstack-meeting-319:52
*** Rockyg has joined #openstack-meeting-319:55
*** r1chardj0n3s has joined #openstack-meeting-319:56
*** jwy has joined #openstack-meeting-319:57
*** esp has joined #openstack-meeting-320:00
*** TravT has joined #openstack-meeting-320:00
*** armax has quit IRC20:00
espo/20:00
r1chardj0n3so/20:00
david-lyle#startmeeting Horizon20:00
TravTo/20:00
openstackMeeting started Wed May  6 20:00: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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: Horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
lhchengo/20:00
absubramo/20:01
tqtrano/20:01
*** pkoniszewski has quit IRC20:01
rhagarty_hello20:02
*** ducttape_ has joined #openstack-meeting-320:02
*** doug-fish has joined #openstack-meeting-320:02
david-lyleletting people trickle in20:02
david-lyleI think they're trickled20:03
*** igordcard has joined #openstack-meeting-320:03
david-lyleI don't have any general announcements today20:03
*** adurbin_ has joined #openstack-meeting-320:03
david-lyleI'm going to jump into the agenda20:04
david-lyle#link https://wiki.openstack.org/wiki/Meetings/Horizon20:04
*** banix has quit IRC20:04
david-lyle#topic Drop Django14 support and gate (lhcheng)20:04
*** openstack changes topic to "Drop Django14 support and gate (lhcheng) (Meeting topic: Horizon)"20:04
lhchenghey20:05
david-lylehey20:05
david-lylegot somethin' to say20:05
david-lyle?20:05
*** absubram has quit IRC20:05
lhchengso rob found out that django14 support is going to be dropped oct 201520:05
bpokornyHi20:05
lhchengwith that, we should probably  drop django14 support for L20:06
lhchengshould we publicize it first in operators before doing it?20:06
david-lylewe need to support the next LTS 1.8 before we drop 1.420:07
david-lylebut both should happen in L20:07
david-lyleprobably should publicize20:07
lhchengcurious, why do we have to wait for LTS1.8?  do we need to support last four releases?20:08
david-lylelhcheng: I think 1.5-1.6 aren't actually supported any more20:08
david-lyle1.7 is for now20:09
david-lyle1.8 is out, we just have to make sure it works with horizon20:09
david-lyle(it doesn't)20:09
david-lyle*spoiler alert20:09
lhchengdavid-lyle: lol20:09
* david-lyle may have done that in the wrong order20:10
mrungein general, it works20:10
lhchengand the gate gate-horizon-python27-django14 moves to django17 then?20:10
david-lylelhcheng: yeah20:10
david-lyleonce we have 1.8 we could look at dropping 1.5 and 1.6 as well20:10
*** ongk_ has joined #openstack-meeting-320:10
david-lylemrunge: just a few more issues to work out in d-o-a20:10
*** jcoufal has joined #openstack-meeting-320:11
mrungedavid-lyle, yes-20:11
mrungewe may rework our permissions system20:11
*** jcoufal has quit IRC20:11
david-lylehmm20:11
mrunges/may/may need/20:11
david-lyleI meant to do that anyway20:11
david-lylewith policy and has_perm in the same place now20:12
david-lylewe can take that offline20:12
mrungeyes20:12
david-lyleany opinions on how many release we should stop supporting?20:12
mrungebut this is something, I'm committed to20:12
TravTmrunge: i'm interested in that as well.20:12
mrungecool!20:12
david-lyle1.7 introduces a lot of new features20:12
mrungesounds good20:13
david-lylespanning so many releases makes us do strange things20:13
mrungesince we're gating on them, it's not that bad20:14
david-lylewe'll start with fixing up 1.8, drop 1.4 and see where we end up on 1.5 and 1.620:14
*** cbouch has left #openstack-meeting-320:14
*** yamahata has quit IRC20:14
mrungesounds like a plan20:14
david-lylelhcheng: is there a bp to drop 1.4?20:15
lhchengdavid-lyle: sounds good, that question could also go with the django14 drop announcement20:15
lhchengdavid-lyle: don't think so20:15
david-lylesure20:15
david-lylelet's add one20:15
doug-fishdoes dropping 1.4 for Liberty affect anything for Juno/Kilo?20:15
mrungedoug-fish, I wouldn't think so20:15
*** absubram has joined #openstack-meeting-320:15
david-lyleshouldn't, except certain backports will become trickier20:15
doug-fishgate jobs?20:16
david-lylebut since we're not adding features in backports20:16
david-lylethe risk of conflict should be minor20:16
mrungedavid-lyle, it doesn't hurt us, if we're still gating on 1.4, right?20:16
doug-fishI was wondering more if it mattered with the "drop 1.4" part of the plan20:16
david-lylemrunge: not in d-o-a IIRC20:16
*** mattfarina has quit IRC20:17
mrungedavid-lyle, I mean, for juno20:17
david-lyleshouldn't effect juno20:17
david-lyle1.4 job will still run20:17
lhchengmrunge: yeah, we should keep those job20:17
david-lyle#topic Session data cleanup (lhcheng)20:18
*** openstack changes topic to "Session data cleanup (lhcheng) (Meeting topic: Horizon)"20:18
mrungelhcheng++ on this!20:18
ducttape_can we remove the "allowed" cache thing from the session?20:18
lhchengfor the session data, we keep on hitting the cookie limit20:18
david-lyleallowed?20:18
david-lyleoh, for nav?20:19
mrungeugh! that hurts20:19
ducttape_the cached permission thing, yep20:19
lhchengdavid-lyle: https://review.openstack.org/#/c/120790/20:19
lhchengso I've been playing around to reduce the session size20:19
lhchengthe "allowed" cache thing, takes 34% of the session size20:19
david-lylethat's rediculous20:20
ducttape_that's less betta'20:20
lhchengI suggest to move the caching from session to the django cache instead20:20
lhchengor maybe just drop it?20:20
mrungeyou know how often that's called per page view?20:20
david-lyleshould be once per page view20:21
david-lylebut the number required should be dropping20:21
mrungewithout caching 10-20 times20:21
mrungeI tried earlier today20:21
david-lylemrunge: you mean building the cache?20:21
david-lyleor how many times the cache is read?20:22
mrungedavid-lyle, I mean, times read20:22
ducttape_all the nav items in the layout stuff, are hiting that a bunch of times20:22
mrungeyes, we should keep the cache20:22
david-lylewe want to move to a model where we don't rebuild the nav on ever panel load20:22
david-lyleonly on rescope20:22
mrungesounds better20:22
ducttape_what is the perf difference with that disabled mrunge?  is it noticeable?20:23
mrungeducttape_, I can't really tell20:23
david-lyleducttape_: I really think it was for testing20:23
mrungeI didn't measure that20:23
ducttape_ok, thanks20:23
lhchengdavid-lyle: if the user rescope, this cache does not get reset. you just found a bug. :P20:23
r1chardj0n3sin the interim, could a localstorage be used instead of django cache? just thinking of future nav work here ;)20:23
TravTlhcheng: i just saw your comment and was starting reply on it in the patch.20:24
ducttape_r1chardj0n3s:  no, it needs to reside on server for current template to use20:24
TravTon the angular side there is also caching20:24
TravTonce per page load20:24
r1chardj0n3sok20:24
david-lyler1chardj0n3s: I would believe that the nav component of the page will no longer need to reload20:24
david-lylethus the purpose of the cache would be gone20:25
r1chardj0n3sdavid-lyle: that's the intention, yes20:25
TravTbut one of the things I tore my hair out over was how would I be notifiied when token rescope.20:25
ducttape_lhcheng - you said you had another place to store that cache?20:25
tqtranwell, we can still use localStorage to store things like "last visited page"20:25
david-lyleonly the panel part of the page is loading20:25
ducttape_someplace besides the session?20:25
lhchengducttape_: yeah, just store it in django's built-in cache framework20:25
*** e0ne has quit IRC20:26
lhchengcould be by process, file cache, memche20:26
ducttape_and that would have a unique spot for each user / token then?20:26
*** mattfarina has joined #openstack-meeting-320:26
lhchengyeah, just need to use a unique key for that user/token20:26
*** Yi has quit IRC20:26
*** mattfarina has quit IRC20:26
david-lyleok, I think we're all for reducing session size, we can discuss the particulars in a couple of weeks20:27
ducttape_+1 lhcheng, our session stuff is a constant hassle.  ship it20:27
mrungeyes, session size issues are hard to debug20:28
lhchengso got the size drop by 75% on my local20:28
mrungecool20:28
lhchengdavid-lyle: sure, we can discuss the details later20:28
david-lyle#topic Summit Scheduling (david-lyle)20:28
*** openstack changes topic to "Summit Scheduling (david-lyle) (Meeting topic: Horizon)"20:28
david-lyleI wanted to make sure we have enough time for this20:29
david-lylesession size/storage happens to be one of the proposed topics too20:29
*** emagana has quit IRC20:29
david-lyle#link https://etherpad.openstack.org/p/horizon-liberty-summit20:29
*** banix has joined #openstack-meeting-320:29
ducttape_can we also talk about session size then?20:29
david-lyleducttape_: no20:29
david-lyle:P20:29
david-lylelet's talk session allocation20:30
*** ivar-lazzaro has quit IRC20:30
*** baoli has quit IRC20:30
david-lylesomeone did a nice job sorting through these, I assume either doug-fish or robcresswell20:31
david-lylenot sure20:31
*** ivar-lazzaro has joined #openstack-meeting-320:31
doug-fishI took a shot at it20:31
*** baoli has joined #openstack-meeting-320:31
david-lylethanks doug-fish20:31
doug-fishsure np20:31
david-lyleSo doug-fish split out topics starting about line 3720:31
TravTthe topics you put at top are down to a single word, so now sure what is meant by some of them20:32
david-lyleI need to publish a schedule so I started trying to figure out what are fishbowl and what are working sessions20:32
david-lyleTravT: they reference the topics starting on 3720:32
david-lylemy lazin^H^H^H^H^Hshorthand20:32
david-lyleline 63, I don't think websockets applies20:33
david-lyleto that topic20:33
david-lyleI think it would go more with messaging20:33
mrungeyeah20:33
david-lyleif anything20:33
mrungeit's just a q, if we want to go that route20:34
*** e0ne has joined #openstack-meeting-320:34
mrungethere were so many issues to be solved with that20:34
TravTthere is a small aspect of websockets aspect to what I'd like to show / talk about with elastic search.20:34
TravTbut is not the main point, so separating them is fine with me.20:34
david-lyledo people agree with the fishbowl topics?20:35
mrungeI wouldn't think, *any* messaging infrastructure should take a whole session20:35
absubramHi all, I put down my request all the way at the bottom L-194 a couple days back.. not sure if anyone got a chance to look at it.. this is to request a better solution to some of the vendor specific code we have in the dashboard section..20:36
TravTso plugins is really broad.20:36
david-lylemrunge: I think better error messages and websockets could share a working session ?20:36
mrungedo we want UX in a bigger plenum?20:36
mrungedavid-lyle, yes!20:36
absubramRob C will probably end up doing the work.. but we don’t have a solution just yet.. and we would like to talk about it.. don’t think it warrants an entire session to itself though..20:36
*** Swami has quit IRC20:37
TravTdavid-lyle it seems like there could be a plugins from the context of which projects are core or not and that would probably take a whole fishbowl20:37
absubramsome time in the contributor meetup is fine too.. unless others have a different opinion? mrunge? :)20:37
david-lyleTravT: absubram so for plugins20:37
david-lyleI think it's a fishbowl and a worksession20:37
TravTbut does that cover tech discussion?20:37
TravTah, ok20:37
mrungeabsubram, that would be fishbowl number one20:38
absubramok.. that’s fine!20:38
david-lyleI want to describe the proposed split and structure20:38
mrungedavid-lyle, do we have the possibility to have working sessions after fish bowls?20:38
david-lylein the fishbowl and then use a working session to plan on implementation20:39
*** carl_baldwin has quit IRC20:39
david-lylehttps://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit#gid=56996312820:39
TravTdavid-lyle, which one does dependencies refer to?20:39
TravTis that packaging?20:39
david-lylemrunge: looks like yes20:40
david-lyleTravT: yes20:40
*** carl_baldwin has joined #openstack-meeting-320:40
david-lylewe'll have to see how the cross-project session goes, I suppose20:41
*** sqchen has joined #openstack-meeting-320:41
TravTSo angular 101 is really broad.20:41
david-lyleTravT: yes indeed20:42
david-lylewe need more than 1 angular session20:42
david-lylethat one was the 101 to get people up to speed that haven't been neck deep in it20:42
TravTyeah, it'll be tough to cover in 40 minutes that topic.20:43
TravTMaybe the other topic could be an overview of our ideas for moving forward with angular in liberty20:43
r1chardj0n3sgood idea20:44
david-lyleTravT: it's not a tutorial or class, just a pointer to where we are and how to get started20:44
david-lyleOR we could move the angular chatter to Friday20:44
david-lylewe have all day Friday20:44
r1chardj0n3sdavid-lyle: should cover the styles, rules and layout we've developed for horizon20:44
david-lylemaybe Friday morning is a better angular time?20:45
r1chardj0n3syeah, when we're all fresh ;)20:45
*** e0ne has quit IRC20:45
david-lylehaha20:46
david-lyledo we want a prioritization work session?20:46
mrungemakes sense20:47
TravTThat was a good discussion in the contributors meetup in Paris20:47
TravTAs FYI, a number of HP'ers working on angular have to depart shortly after noon on Friday. :(20:47
david-lylefriday afternoon then20:48
david-lyle:P20:48
r1chardj0n3sTravT: is that leave-the-venue depart or fly-out depart?20:48
TravT:)20:48
TravTleave the venue20:48
TravTI have to leave the venue at about 2.20:48
r1chardj0n3sok, so we get a solid morning to hassle^H^H^H^H^H^Hwork with you20:48
david-lyleKeystone could be meetup topic too20:48
david-lylegiving merlin a session would be good20:49
TravTmrunge put a topic up that would be good at some point.  Moving forward with functions / deprecating old20:51
mrungeTravT, yes!20:51
mrungeTravT, more interesting: how to fix older releases then20:52
mrungesince it's expected to fix in master branch first20:52
TravTstraight patch i guess.  no cherry picking20:52
mrungewe already discussed that20:52
mrungeTravT, still that bears the risk of patching an issue in master-1 which is still existent in master20:52
mrungeI wonder, if we really need a whole session for this20:54
david-lyleI've been editing away20:54
david-lylenumbering is not priority btw20:54
david-lylefeel free to comment inline or pull something up20:55
tqtrando we need a session for discussing karma and jasmine tests?20:55
tqtranor just jasmine 101?20:55
david-lylei think that may be part of angular 10120:56
r1chardj0n3sso that 40 minutes is filling up quite nicely then ;)20:56
TravTtqtran: matt-borland also can help give a great overview of that and demo stuff related to karma20:56
david-lyler1chardj0n3s: moved it to Friday morning20:57
david-lylefor continuity20:57
david-lylesake20:57
david-lyleplus I have a feeling more people will show up than just the 28 or so the working session supports20:57
TravT28 people... that's small20:58
r1chardj0n3smmm20:58
mrungewe should have a backup plan20:58
TravTi guess we all better get in line and camp out overnight20:58
david-lylehence working session20:58
mrungea second topic20:58
mrungeand just capture a different room20:58
david-lyletimes up20:59
david-lyleI have yet to decide how descriptive the topics for the working sessions will be20:59
david-lyledon't want too many people20:59
david-lyleobserving20:59
TravTi think we had about 40 in the contributor's meetup20:59
david-lyleI'll let the etherpad sit for another day or so then publish a schedule21:00
david-lylecontinue to comment on the proposed allocation of spots.21:00
david-lyleThanks everyone!21:00
david-lyle#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed May  6 21:00:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
espthx!21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-05-06-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-05-06-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-05-06-20.00.log.html21:00
absubrambye all! thanks!21:00
*** ducttape_ has left #openstack-meeting-321:00
*** r1chardj0n3s has left #openstack-meeting-321:00
*** absubram has quit IRC21:01
*** emagana has joined #openstack-meeting-321:01
*** jwy has left #openstack-meeting-321:02
*** LouisF has joined #openstack-meeting-321:03
*** Sukhdev has quit IRC21:03
*** LouisF has quit IRC21:04
*** emagana has quit IRC21:06
*** TravT has quit IRC21:09
*** adurbin_ has left #openstack-meeting-321:09
*** tqtran has left #openstack-meeting-321:10
*** ongk_ has quit IRC21:12
*** Swami has joined #openstack-meeting-321:13
*** lblanchard has quit IRC21:14
*** maurosr has quit IRC21:21
*** jgrimm_ has quit IRC21:22
*** maurosr has joined #openstack-meeting-321:22
*** jgrimm has joined #openstack-meeting-321:23
*** Longgeek has quit IRC21:23
*** david-lyle has quit IRC21:29
*** sqchen has left #openstack-meeting-321:32
*** shwetaap has quit IRC21:38
*** asahlin is now known as asahlin_afk21:41
*** baoli has quit IRC21:43
*** baoli has joined #openstack-meeting-321:44
*** btully has quit IRC21:45
*** alexpilotti has quit IRC21:46
*** jtomasek has quit IRC21:49
*** baoli has quit IRC21:54
*** baoli has joined #openstack-meeting-321:55
*** mrmartin has quit IRC21:56
*** stevemar has quit IRC21:57
*** eghobo_ has joined #openstack-meeting-321:59
*** maurosr has quit IRC21:59
*** eghobo has quit IRC22:00
*** maurosr has joined #openstack-meeting-322:03
*** s3wong has quit IRC22:06
*** jgrimm has quit IRC22:07
*** s3wong_ has joined #openstack-meeting-322:07
*** jgrimm has joined #openstack-meeting-322:09
*** fallenpegasus has joined #openstack-meeting-322:09
*** maurosr has quit IRC22:12
*** maurosr has joined #openstack-meeting-322:14
*** etoews has joined #openstack-meeting-322:15
*** VW_ has quit IRC22:15
*** DinaBelova has quit IRC22:30
*** DinaBelova has joined #openstack-meeting-322:31
*** Piet has quit IRC22:35
*** s3wong_ has quit IRC22:36
*** s3wong has joined #openstack-meeting-322:36
*** sarob has quit IRC22:38
*** salv-orl_ has quit IRC22:38
*** jckasper has quit IRC22:39
*** salv-orlando has joined #openstack-meeting-322:40
*** baoli has quit IRC22:41
*** baoli has joined #openstack-meeting-322:42
*** carl_baldwin has quit IRC22:42
*** fallenpegasus has quit IRC22:43
*** fallenpegasus has joined #openstack-meeting-322:44
*** emagana has joined #openstack-meeting-322:45
*** banix has quit IRC22:47
*** fallenpegasus has quit IRC22:48
*** mrunge has quit IRC22:50
*** Piet has joined #openstack-meeting-322:54
*** Piet has quit IRC22:54
*** armax has joined #openstack-meeting-322:57
*** SumitNaiksatam has quit IRC22:58
*** bknudson has quit IRC22:58
*** banix has joined #openstack-meeting-323:00
*** armax has quit IRC23:04
*** maurosr has quit IRC23:05
*** maurosr has joined #openstack-meeting-323:08
*** baoli has quit IRC23:10
*** vishwanathj_ has joined #openstack-meeting-323:22
*** Piet has joined #openstack-meeting-323:28
*** mattgriffin has quit IRC23:29
*** nelsnelson has quit IRC23:31
*** Rockyg has quit IRC23:32
*** banix has quit IRC23:33
*** watanabe_isao has joined #openstack-meeting-323:38
*** sarob has joined #openstack-meeting-323:42
*** david-lyle has joined #openstack-meeting-323:47
*** VW_ has joined #openstack-meeting-323:57

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