*** etoews has quit IRC | 00:09 | |
*** Aish has quit IRC | 00:13 | |
*** fallenpegasus has quit IRC | 00:14 | |
*** carl_baldwin has quit IRC | 00:27 | |
*** mlavalle has quit IRC | 00:30 | |
*** Sukhdev has quit IRC | 00: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 IRC | 00:43 | |
*** banix has joined #openstack-meeting-3 | 00:53 | |
*** mwang2 has quit IRC | 00:55 | |
*** igordcard has quit IRC | 00:56 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 01:04 | |
*** alexpilotti has quit IRC | 01:08 | |
*** bpokorny has quit IRC | 01:12 | |
*** eghobo has quit IRC | 01:14 | |
*** alexsyip has quit IRC | 01:22 | |
*** Swami has quit IRC | 01:28 | |
*** alexpilotti has joined #openstack-meeting-3 | 01:29 | |
*** s3wong_ has quit IRC | 01:40 | |
*** alexpilotti has quit IRC | 01:48 | |
*** stanzgy has joined #openstack-meeting-3 | 01:54 | |
*** salv-orlando has joined #openstack-meeting-3 | 01:58 | |
*** zhenguo has joined #openstack-meeting-3 | 02:01 | |
*** ivar-lazzaro has quit IRC | 02:03 | |
*** salv-orlando has quit IRC | 02:04 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 02:04 | |
*** sigmavirus24 is now known as sigmavirus24_awa | 02:19 | |
*** ivar-laz_ has joined #openstack-meeting-3 | 02:21 | |
*** yamahata has quit IRC | 02:22 | |
*** mestery has joined #openstack-meeting-3 | 02:23 | |
*** ivar-lazzaro has quit IRC | 02:24 | |
*** mwagner_lap has joined #openstack-meeting-3 | 02:32 | |
*** stanzgy has quit IRC | 02:41 | |
*** baoli has joined #openstack-meeting-3 | 02:42 | |
*** nelsnelson has joined #openstack-meeting-3 | 02:47 | |
*** stanzgy has joined #openstack-meeting-3 | 02:49 | |
*** nelsnelson has quit IRC | 02:52 | |
*** ivar-laz_ has quit IRC | 02:53 | |
*** VW_ has joined #openstack-meeting-3 | 02:59 | |
*** sarob has joined #openstack-meeting-3 | 03:06 | |
*** markvoelker has quit IRC | 03:10 | |
*** yamahata has joined #openstack-meeting-3 | 03:12 | |
*** banix has quit IRC | 03:15 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 03:19 | |
*** krtaylor has quit IRC | 03:37 | |
*** lazy_prince has joined #openstack-meeting-3 | 03:39 | |
*** rushiagr_away is now known as rushiagr | 03:44 | |
*** baoli has quit IRC | 03:50 | |
*** coolsvap|afk is now known as coolsvap | 03:53 | |
*** krtaylor has joined #openstack-meeting-3 | 03:55 | |
*** eghobo has joined #openstack-meeting-3 | 04:02 | |
*** markvoelker has joined #openstack-meeting-3 | 04:11 | |
*** jckasper has joined #openstack-meeting-3 | 04:11 | |
*** rushiagr is now known as rushiagr_away | 04:12 | |
*** eghobo has quit IRC | 04:14 | |
*** markvoelker has quit IRC | 04:16 | |
*** VW_ has quit IRC | 04:26 | |
*** salv-orlando has joined #openstack-meeting-3 | 04:35 | |
*** salv-orlando has quit IRC | 04:38 | |
*** VW_ has joined #openstack-meeting-3 | 04:48 | |
*** btully has joined #openstack-meeting-3 | 04:50 | |
*** mrmartin has joined #openstack-meeting-3 | 04:50 | |
*** nkrinner has joined #openstack-meeting-3 | 04:51 | |
*** VW_ has quit IRC | 04:52 | |
*** sarob has quit IRC | 04:56 | |
*** egallen has joined #openstack-meeting-3 | 04:58 | |
*** fallenpegasus has joined #openstack-meeting-3 | 05:01 | |
*** rushiagr_away is now known as rushiagr | 05:03 | |
*** btully has quit IRC | 05:07 | |
*** ivar-lazzaro has quit IRC | 05:08 | |
*** irenab has joined #openstack-meeting-3 | 05:08 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 05:08 | |
*** Swami has joined #openstack-meeting-3 | 05:11 | |
*** ivar-lazzaro has quit IRC | 05:11 | |
*** markvoelker has joined #openstack-meeting-3 | 05:12 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 05:12 | |
*** egallen has quit IRC | 05:13 | |
*** markvoelker has quit IRC | 05:16 | |
*** mrmartin has quit IRC | 05:17 | |
*** fallenpegasus has quit IRC | 05:17 | |
*** egallen has joined #openstack-meeting-3 | 05:18 | |
*** egallen has quit IRC | 05:18 | |
*** SumitNaiksatam has quit IRC | 05:19 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 05:20 | |
*** fallenpegasus has joined #openstack-meeting-3 | 05:20 | |
*** iovadia has joined #openstack-meeting-3 | 05:22 | |
*** sergef has joined #openstack-meeting-3 | 05:39 | |
*** rushiagr is now known as rushiagr_away | 05:40 | |
*** wojdev has joined #openstack-meeting-3 | 05:47 | |
*** markvoelker has joined #openstack-meeting-3 | 05:51 | |
*** dobson has quit IRC | 05:52 | |
*** markvoelker has quit IRC | 05:55 | |
*** SumitNaiksatam has quit IRC | 05:57 | |
*** wojdev has quit IRC | 05:58 | |
*** tmazur has joined #openstack-meeting-3 | 06:00 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 06:01 | |
*** Swami has quit IRC | 06:03 | |
*** Longgeek has joined #openstack-meeting-3 | 06:05 | |
*** jcoufal has joined #openstack-meeting-3 | 06:06 | |
*** dobson has joined #openstack-meeting-3 | 06:07 | |
*** mrunge has joined #openstack-meeting-3 | 06:08 | |
*** pkoniszewski has joined #openstack-meeting-3 | 06:09 | |
*** evgenyf has joined #openstack-meeting-3 | 06:09 | |
*** salv-orlando has joined #openstack-meeting-3 | 06:10 | |
*** scheuran has joined #openstack-meeting-3 | 06:13 | |
*** ivar-laz_ has joined #openstack-meeting-3 | 06:15 | |
*** ivar-lazzaro has quit IRC | 06:15 | |
*** Longgeek has quit IRC | 06:21 | |
*** Longgeek has joined #openstack-meeting-3 | 06:21 | |
*** rushiagr_away is now known as rushiagr | 06:22 | |
*** Longgeek has quit IRC | 06:23 | |
*** Longgeek has joined #openstack-meeting-3 | 06:23 | |
*** Poornima has joined #openstack-meeting-3 | 06:23 | |
*** sergef has quit IRC | 06:27 | |
*** ivar-lazzaro has joined #openstack-meeting-3 | 06:35 | |
*** fallenpegasus has quit IRC | 06:35 | |
*** sahid has joined #openstack-meeting-3 | 06:36 | |
*** fallenpegasus has joined #openstack-meeting-3 | 06:36 | |
*** ivar-laz_ has quit IRC | 06:36 | |
*** tteggel has quit IRC | 06:41 | |
*** yamahata has quit IRC | 06:41 | |
*** tteggel has joined #openstack-meeting-3 | 06:41 | |
*** yamahata has joined #openstack-meeting-3 | 06:48 | |
*** jcoufal_ has joined #openstack-meeting-3 | 06:49 | |
*** markvoelker has joined #openstack-meeting-3 | 06:52 | |
*** jcoufal has quit IRC | 06:52 | |
*** markvoelker has quit IRC | 06:56 | |
*** wojdev has joined #openstack-meeting-3 | 06:58 | |
*** jtomasek has joined #openstack-meeting-3 | 06:59 | |
*** wojdev has quit IRC | 07:05 | |
*** fallenpegasus has quit IRC | 07:06 | |
*** fallenpegasus has joined #openstack-meeting-3 | 07:07 | |
*** wojdev has joined #openstack-meeting-3 | 07:07 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 07:09 | |
*** fallenpegasus has quit IRC | 07:11 | |
*** wojdev has quit IRC | 07:19 | |
*** wojdev has joined #openstack-meeting-3 | 07:21 | |
*** matrohon has joined #openstack-meeting-3 | 07:27 | |
*** eghobo has joined #openstack-meeting-3 | 07:36 | |
*** safchain has joined #openstack-meeting-3 | 07:54 | |
*** rushiagr has quit IRC | 07:56 | |
*** wojdev has quit IRC | 08:01 | |
*** egallen has joined #openstack-meeting-3 | 08:05 | |
*** lsmola has joined #openstack-meeting-3 | 08:11 | |
*** rushiagr has joined #openstack-meeting-3 | 08:12 | |
*** wojdev has joined #openstack-meeting-3 | 08:17 | |
*** salv-orlando has quit IRC | 08:18 | |
*** salv-orlando has joined #openstack-meeting-3 | 08:18 | |
*** e0ne has joined #openstack-meeting-3 | 08:22 | |
*** ivar-lazzaro has quit IRC | 08:23 | |
*** eghobo has quit IRC | 08:29 | |
*** tmazur has quit IRC | 08:30 | |
*** tmazur has joined #openstack-meeting-3 | 08:31 | |
*** MaxV has joined #openstack-meeting-3 | 08:34 | |
*** JeanBriceCombebi has quit IRC | 08:37 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 08:38 | |
*** e0ne has quit IRC | 08:43 | |
*** tmazur has quit IRC | 08:45 | |
*** tmazur has joined #openstack-meeting-3 | 08:46 | |
*** vgridnev has quit IRC | 08:49 | |
*** MaxV has quit IRC | 08:52 | |
*** JeanBriceCombebi has quit IRC | 08:57 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 08:57 | |
*** lsmola has quit IRC | 08:58 | |
*** jtomasek has quit IRC | 08:58 | |
*** smccully has quit IRC | 08:58 | |
*** aleksandr_null has quit IRC | 08:58 | |
*** russellb has quit IRC | 08:58 | |
*** haleyb has quit IRC | 08:58 | |
*** SotK has quit IRC | 08:58 | |
*** mrda has quit IRC | 08:58 | |
*** lsmola has joined #openstack-meeting-3 | 09:00 | |
*** jtomasek has joined #openstack-meeting-3 | 09:00 | |
*** smccully has joined #openstack-meeting-3 | 09:00 | |
*** aleksandr_null has joined #openstack-meeting-3 | 09:00 | |
*** russellb has joined #openstack-meeting-3 | 09:00 | |
*** haleyb has joined #openstack-meeting-3 | 09:00 | |
*** SotK has joined #openstack-meeting-3 | 09:00 | |
*** mrda has joined #openstack-meeting-3 | 09:00 | |
*** wojdev has quit IRC | 09:08 | |
*** rushiagr is now known as rushiagr_away | 09:11 | |
*** e0ne has joined #openstack-meeting-3 | 09:25 | |
*** Longgeek has quit IRC | 09:53 | |
*** JeanBriceCombebi has quit IRC | 09:57 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 09:57 | |
*** e0ne is now known as e0ne_ | 09:59 | |
*** e0ne_ is now known as e0ne | 10:05 | |
*** zhenguo has quit IRC | 10:07 | |
*** rushiagr_away is now known as rushiagr | 10:15 | |
*** sahid has quit IRC | 10:33 | |
*** Longgeek has joined #openstack-meeting-3 | 10:35 | |
*** sahid has joined #openstack-meeting-3 | 10:37 | |
*** coolsvap is now known as coolsvap|afk | 10:38 | |
*** lennyb has joined #openstack-meeting-3 | 10:43 | |
*** stanzgy has quit IRC | 10:53 | |
*** yalie has quit IRC | 10:57 | |
*** evgenyf has quit IRC | 11:09 | |
*** yamahata has quit IRC | 11:30 | |
*** Poornima has quit IRC | 11:40 | |
*** JeanBriceCombebi has quit IRC | 11:41 | |
*** evgenyf has joined #openstack-meeting-3 | 11:46 | |
*** gulic has joined #openstack-meeting-3 | 11:52 | |
*** gulic has left #openstack-meeting-3 | 11:52 | |
*** alexpilotti has joined #openstack-meeting-3 | 11:56 | |
*** markvoelker has joined #openstack-meeting-3 | 11:59 | |
*** VW_ has joined #openstack-meeting-3 | 12:01 | |
*** bknudson has joined #openstack-meeting-3 | 12:04 | |
*** btully has joined #openstack-meeting-3 | 12:05 | |
*** VW_ has quit IRC | 12:06 | |
*** lblanchard has joined #openstack-meeting-3 | 12:14 | |
*** jckasper has quit IRC | 12:15 | |
*** btully has quit IRC | 12:20 | |
*** e0ne is now known as e0ne_ | 12:22 | |
*** e0ne_ is now known as e0ne | 12:29 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 12:33 | |
*** edleafe has quit IRC | 12:40 | |
*** edleafe has joined #openstack-meeting-3 | 12:41 | |
*** VW_ has joined #openstack-meeting-3 | 12:42 | |
*** lblanchard has quit IRC | 12:47 | |
*** baoli has joined #openstack-meeting-3 | 12:48 | |
*** banix has joined #openstack-meeting-3 | 12:49 | |
*** banix has quit IRC | 12:53 | |
*** baoli_ has joined #openstack-meeting-3 | 12:57 | |
*** baoli has quit IRC | 13:00 | |
*** qwebirc81982 has joined #openstack-meeting-3 | 13:00 | |
*** rushiagr is now known as rushiagr_away | 13:02 | |
*** rushiagr_away is now known as rushiagr | 13:02 | |
*** Yi has joined #openstack-meeting-3 | 13:03 | |
*** gsagie has joined #openstack-meeting-3 | 13:04 | |
*** rushiagr is now known as rushiagr_away | 13:06 | |
*** pkoniszewski has quit IRC | 13:12 | |
*** Yi has quit IRC | 13:14 | |
*** e0ne is now known as e0ne_ | 13:19 | |
*** e0ne_ is now known as e0ne | 13:21 | |
*** peristeri has joined #openstack-meeting-3 | 13:21 | |
*** jckasper has joined #openstack-meeting-3 | 13:30 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 13:35 | |
*** lifeless has quit IRC | 13:42 | |
*** cbits has joined #openstack-meeting-3 | 13:45 | |
*** vikram__ has joined #openstack-meeting-3 | 13:48 | |
*** mattgriffin has joined #openstack-meeting-3 | 13:50 | |
*** sfinucan has joined #openstack-meeting-3 | 13:55 | |
*** moshele has joined #openstack-meeting-3 | 13:57 | |
*** tmazur has quit IRC | 13:57 | |
ajo | hi :) | 14:00 |
---|---|---|
sfinucan | hey | 14:00 |
vikram__ | hi | 14:01 |
matrohon | hi | 14:01 |
vhoward | hey | 14:01 |
ajo | let's start :) | 14:01 |
ajo | #startmeeting neutron_qos | 14:01 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
*** openstack changes topic to " (Meeting topic: neutron_qos)" | 14:01 | |
openstack | The meeting name has been set to 'neutron_qos' | 14:01 |
ajo | #link https://wiki.openstack.org/wiki/Meetings/QoS#2015-05-06_14:00_UTC | 14:01 |
ajo | #topic API microversioning spec implications | 14: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 | |
moshele | hi | 14:02 |
ajo | I have included this first point after talking to sc68cal today :) | 14:02 |
ajo | I recommend reading it if you have time, | 14:02 |
irenab | hi | 14:02 |
vikram__ | it's too long:) | 14:02 |
vikram__ | i tried but couldn't complete | 14:02 |
ajo | this 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-3 | 14:03 | |
ajo | vikram__ :D yeah, it needs a good coffee to read it | 14:03 |
ajo | sc68cal, any comments? :) | 14:03 |
vhoward | will take a look thanks | 14:03 |
*** shwetaap has joined #openstack-meeting-3 | 14:04 | |
ajo | ok, let's move on | 14:04 |
ajo | #topic Changes to the QoS API spec: scoping into bandwidth limiting | 14:05 |
*** openstack changes topic to "Changes to the QoS API spec: scoping into bandwidth limiting (Meeting topic: neutron_qos)" | 14:05 | |
*** JeanBriceCombebi has quit IRC | 14:05 | |
ajo | #link https://review.openstack.org/#/c/88599/9..10/specs/liberty/qos-api-extension.rst | 14:05 |
ajo | I iterated a couple of times on the spec since last week | 14:05 |
*** Networkn3rd has joined #openstack-meeting-3 | 14:05 | |
ajo | armax, from the drivers team had some time to review and provide feedback | 14:06 |
ajo | he asked for some changes in the data model (I'll get to that later) | 14:06 |
*** sadasu has joined #openstack-meeting-3 | 14:07 | |
ajo | and he asked to scope the initial work into bandwidth limiting | 14:07 |
sc68cal | ajo: sorry, just got scrollback - nothing to add | 14:08 |
ajo | I 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 |
vhoward | yeah 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-3 | 14:09 | |
ajo | vhoward +1 | 14:09 |
*** qwebirc81982 has quit IRC | 14:09 | |
vhoward | cool, i can put some notes in for us | 14:09 |
vhoward | and help out as you need, just let me know | 14:09 |
ajo | Check the comments about traffic classification & ideas, | 14:10 |
vhoward | cool ajo, thanks for the tip will read up today | 14:10 |
ajo | I 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-3 | 14: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 | |
ajo | ok, if you see , I've modified the current data model, per armax suggestion, to make it more specific | 14:11 |
ajo | I keep the QoSPolicy, composed of QoSRules | 14:11 |
ajo | but now every rule type may have a QoS<type>Rule | 14:12 |
ajo | extending the basic rule information with the specific parameters | 14:12 |
ajo | Also, there was a discussion about splitting rules into smaller combinable chunks, | 14:12 |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 14:13 | |
ajo | like, guarantees... since there could be plugins not able to provide guarantees, while others would. | 14:13 |
*** shakamunyi has quit IRC | 14:13 | |
ajo | The 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 |
ajo | if you see issues with the current changes, speak now, or... otherwise speak into the spec :) | 14:15 |
irenab | ajo: comparing to specify ‘guarantee level’ atribute in the rule itslef? | 14:15 |
ajo | irenab, what do you mean? | 14:15 |
vikram__ | I feel the QoSRule is carrying more information now. How about splitting it out. | 14:15 |
irenab | ajo: what you mentiond before .. like, guarantees | 14:16 |
ajo | vikram__, see comments, Traffic Classification fields are going to be splitted out. | 14:16 |
ajo | but for later iterations, not now | 14:16 |
*** lazy_prince has quit IRC | 14:16 | |
ajo | just wanted to see how it looked, and the drawbacks of what I had in mind | 14:16 |
ajo | irenab, ahh | 14:16 |
vikram__ | ok.. i feel it's just a suggestion from your end and you need more voting before doing:) | 14:16 |
ajo | for example, the previous ratecontrol: max_kbps=10000 min_kbps=3000 | 14:17 |
ajo | could be expressed as | 14:17 |
ajo | bandwidthlimit max_kbps=10000 + another rule for guarantee min_kbps=3000 | 14:17 |
ajo | guarantee could have a field to say if it's strict, or best effort | 14:17 |
ajo | or we could have a separate rule for besteffort/strict | 14:18 |
ajo | vikram__ +1 :D | 14:18 |
ajo | irenab, this way, if the plugin doesn't opt in tu support the "guarantee" rules... you can't just push that rule | 14:18 |
vikram__ | +1 for separate rules. Because it could be vendor specific. | 14:19 |
sfinucan | +1 - very granular | 14:19 |
gsagie | ajo: 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 |
gsagie | so 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 |
gsagie | in case something is not supported | 14:20 |
irenab | gsagie: +1 | 14:20 |
ajo | gsagie, yes, that's one of the things, it fits well in the extension world, but... we'll have microversioning | 14:20 |
ajo | yes, | 14:20 |
ajo | gsagie, there's a point about checking incompatible rules | 14:20 |
*** cbouch has joined #openstack-meeting-3 | 14:21 | |
ajo | we 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 policy | 14:21 |
ajo | for example, you can't ask for a guarantee (min_kbps) > bandwidthlimit (max_kbps) | 14:21 |
*** rushiagr_away is now known as rushiagr | 14:21 | |
*** rmschn has joined #openstack-meeting-3 | 14:21 | |
ajo | around this (successive extensions), we had another point in the agenda | 14: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 | |
ajo | with 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 |
ajo | we could just add one extension per rule | 14:24 |
ajo | (rule type) | 14:24 |
ajo | hmmm, sorry, I'm mixing things up :) | 14:24 |
ajo | that makes a nonsense :) | 14:24 |
ajo | we just extend the port & net once with the QoSPolicy, right? :) | 14:24 |
ajo | (-1 on me, please :) ) | 14:24 |
vhoward | ;) | 14:25 |
irenab | ajo: I guess you mean extending the QoS extension with more qos rule types | 14:25 |
ajo | yes, more about extending the API | 14:25 |
ajo | there are two options here, we can have one api end to create rules | 14:26 |
*** nkrinner has quit IRC | 14:26 | |
ajo | or we can have an api endpoint per rule type | 14:26 |
gsagie | ajo : 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 |
gsagie | so i think in a centralized place, if i understood what you mean :) | 14:26 |
ajo | I'm talking about... | 14:26 |
* ajo scrolls on the spec | 14:27 | |
*** e0ne is now known as e0ne_ | 14:27 | |
ajo | about having: | 14:27 |
ajo | POST /v2.0/qos-<type>-rules | 14:27 |
ajo | one per type | 14:27 |
ajo | or... | 14:27 |
ajo | just a /v2.0/qos-rules | 14:28 |
irenab | ajo: by api end point, you mean REST resource /qos/XXX or different path? | 14:28 |
ajo | where we post & get , UPDATE,e tc | 14:28 |
*** jlvillal has quit IRC | 14:28 | |
ajo | irenab correct, API endpoint is another port listening for requests, right? | 14:28 |
irenab | ajo: this is my understanding | 14:29 |
ajo | ok :) | 14:29 |
*** amuller has joined #openstack-meeting-3 | 14:29 | |
ajo | so, I mean different rest resources, vs single for types of rules... | 14:29 |
*** jlvillal has joined #openstack-meeting-3 | 14:29 | |
ajo | I have no strong preference for one of another, | 14:30 |
*** carl_baldwin has joined #openstack-meeting-3 | 14:30 | |
vikram__ | To me having one is better.. it can help to minimize the coding effort | 14:30 |
ajo | it was my understanding that having separate ones was preferable from armax POV | 14:30 |
ajo | I guess having one, requires a big "switch" at the api endpoint, to create one rule or another | 14:30 |
irenab | ajo: I think we should go with option that allows easier extension for new type | 14:30 |
ajo | and validate | 14:30 |
gsagie | but you will have single one, you need some code that parse and knows which attribute belongs to which type | 14:30 |
ajo | api endpoint I said again.. | 14:31 |
gsagie | if you | 14:31 |
ajo | ajo-- | 14:31 |
ajo | :) | 14:31 |
vhoward | +1 arenab | 14:31 |
ajo | gsagie, yes, I guess that's it | 14:31 |
vikram__ | gsagie: but we can reuse most of it. | 14:31 |
ajo | vikram__, client coding doesn't need to be more complicated it's just a string in the middle of the URL qos-%(type)s-rules | 14:32 |
ajo | also, from the cmdline interface, | 14:32 |
ajo | going one way or another could mean we have separate commands, or just one | 14:32 |
ajo | I believe having just one could be messy because we may end up with a lot of optional commands which only apply to certain rules | 14:33 |
ajo | unless the argparser we use is capable of having another level of optional flags | 14:33 |
vikram__ | ajo: Thanks for the explanation... I got it .. having 1 cmd is better to manage i feel | 14:33 |
gsagie | or maybe just /v2.0/qos-rules/<extension or type>/.... | 14:34 |
vikram__ | ok | 14:34 |
*** nelsnelson has joined #openstack-meeting-3 | 14:34 | |
ajo | gsagie, could be, yes... | 14:34 |
ajo | I wonder if we have this kind of class inheritance somewhere in the project | 14:34 |
ajo | and any API which does the dame | 14:34 |
ajo | dame->same | 14:34 |
ajo | across openstack | 14:34 |
*** vineetmenon has joined #openstack-meeting-3 | 14:35 | |
*** shakamunyi has joined #openstack-meeting-3 | 14:35 | |
*** rmschn has quit IRC | 14:35 | |
ajo | ok, we need to iron this parts out | 14:35 |
ajo | I 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 help | 14:36 |
*** shakamunyi has quit IRC | 14:36 | |
ajo | about what arguments apply to each rule type | 14:36 |
*** shakamunyi has joined #openstack-meeting-3 | 14:36 | |
*** stevemar has joined #openstack-meeting-3 | 14:37 | |
*** e0ne_ is now known as e0ne | 14:37 | |
ajo | and for the REST part, let's keep discussing on the spec. | 14:37 |
gsagie | k | 14:37 |
irenab | ajo: +1 | 14:37 |
vikram__ | ok | 14: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 type | 14:38 |
ajo | #undo | 14:38 |
openstack | Removing item from minutes: <ircmeeting.items.Action object at 0x927bb90> | 14:38 |
*** rmschn has joined #openstack-meeting-3 | 14: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 type | 14:38 |
ajo | rules -> rule types | 14:38 |
*** dane_leblanc has joined #openstack-meeting-3 | 14:39 | |
*** JeanBriceCombebi has quit IRC | 14:39 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 14:39 | |
ajo | #topic Traffic Classification considerations | 14:39 |
*** openstack changes topic to "Traffic Classification considerations (Meeting topic: neutron_qos)" | 14:39 | |
ajo | I believe most of you already read that part of the comments, | 14:39 |
ajo | I was proposing to (when we do TC) create another data model to do traffic classification | 14:40 |
ajo | so that it can be attached to rules | 14:40 |
irenab | ajo: +1 | 14:40 |
ajo | this way we don't need to repeat the same filters for rules targetting the same type of traffic | 14:40 |
vikram__ | ajo: +1 | 14:41 |
irenab | once we get there, need to be careful when this object can be modified | 14:41 |
irenab | not to create too many update dependencies | 14:41 |
gsagie | yes, good point | 14:41 |
ajo | yes, as it will affect several rules | 14:41 |
ajo | at that time we may need to analyze what's better | 14:42 |
ajo | we either let them reattach each rule to a new TC | 14:42 |
ajo | or... | 14:42 |
ajo | modify the TC | 14:42 |
ajo | but that means lots of rules could be updated at the same time | 14:42 |
ajo | from the user usability perspective it's probably simpler to let them change a TC | 14:42 |
ajo | messaging could be short | 14:43 |
irenab | the impact can be high | 14:43 |
ajo | yes it needs to be seriously considered | 14:44 |
irenab | but we can decide later what approach to take | 14:44 |
ajo | yes | 14:44 |
ajo | in an ovs / openflow world | 14:44 |
ajo | we could make use of conjunctive rules | 14: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 |
ajo | and just modify the rules in the conjunction... that is mapped to the TC | 14:45 |
ajo | vikram__, probably it could only happen if an administrator needs to correct a TC which was wrong | 14:45 |
ajo | or make it more specific | 14:45 |
ajo | probably it's not going to ve a common use case | 14:45 |
ajo | or... | 14:46 |
ajo | or a CSP | 14:46 |
vikram__ | ok.. but that could not be frequent.. | 14:46 |
ajo | sorry... nothing about CSPs :) | 14:46 |
ajo | but.. we also have the same case with policies | 14:46 |
ajo | if a CSP has a policy for his cloud | 14:46 |
ajo | and it's changed, | 14:46 |
ajo | (for example BW limit to 10mbps to certain level) | 14:46 |
ajo | it may need to propagate to a lot of ports | 14:47 |
ajo | But , the admin could also create a new policy, and reattach the networks | 14:47 |
ajo | one by one | 14:47 |
vikram__ | ok | 14:47 |
*** matrohon has quit IRC | 14:48 | |
ajo | ok, we have another point about "The ingress vs egress differences and issues." | 14:48 |
*** rmschn has quit IRC | 14:48 | |
ajo | probably it's just a matter of documenting the scalability implications of modifiying a policy (or TC), or creating and switching... | 14:49 |
ajo | API documentation I mean | 14:49 |
ajo | I get you all bored :D | 14:50 |
ajo | ok | 14:50 |
ajo | #topic The ingress vs egress differences and issues | 14:50 |
*** openstack changes topic to "The ingress vs egress differences and issues (Meeting topic: neutron_qos)" | 14:50 | |
sadasu | ajo: we are listening :-) | 14:50 |
vikram__ | i am with you till now:) | 14:51 |
irenab | ajo: you are just very verbose | 14:51 |
ajo | garyk was making an interesting point in last meeting, about including an ingress/egress field | 14:51 |
ajo | irenab: that's true :D | 14:51 |
ajo | I can be either very shy, or very chatty... ;) | 14:51 |
sadasu | I think the idea of including a direction field is a good one | 14:52 |
ajo | I was looking at the implications of supporting egress & ingress control from the linux perspective | 14:52 |
ajo | linux (in netfilter) has only direct support for egress control | 14:52 |
*** Sukhdev has joined #openstack-meeting-3 | 14:53 | |
ajo | egress 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 |
sfinucan | ajo: Open vSwitch is the same | 14:53 |
sadasu | I would expect the egress direction to be more useful than ingress | 14:53 |
ajo | gsagie had some ideas bout ingress (metering), but we haven't been able to check yet | 14:54 |
sfinucan | there's basic ingress metering, but that's it | 14:54 |
ajo | sfinucan, but we're not sure if we can make it drop packets or not above some rate | 14:54 |
vikram__ | is it documented somewhere? | 14:54 |
ajo | OF1.3 metering, gsagie do you have the link somewhere? | 14:55 |
sfinucan | It is somewhere...but I don't recall where :) | 14:55 |
sfinucan | I was testing it ~3 weeks ago. It dropped packets | 14:55 |
vikram__ | hehehe-:) | 14:55 |
ajo | there are ways to do ingress (if we couldn't use metering for this), but they are twisted | 14:55 |
*** bknudson has quit IRC | 14:55 | |
sfinucan | but it was a very rough estimate | 14:55 |
ajo | generally, 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 egress | 14:56 |
sfinucan | this should get you something useful -> "sudo ovs-vsctl set interface $IF_NAME ingress_policing_rate=1000" | 14:56 |
ajo | you bounce it back, and finter egress | 14:56 |
ajo | filter | 14:56 |
sfinucan | ajo: sounds about right, yes | 14:56 |
vikram__ | thanks ajo will check it | 14:56 |
sadasu | ajo: +1 | 14:56 |
ajo | sfinucan, ok, we may check that, | 14:56 |
ajo | vikram__, if have time to check sfinucan : perfect | 14:56 |
sfinucan | ls | 14:57 |
ajo | "test what sfinucan said" I mean, sorry | 14:57 |
vikram__ | ok will do that.. | 14:57 |
ajo | https://github.com/mangelajo/ovs-experiments/blob/master/qos/qos_traffic_shapping.sh | 14:57 |
ajo | this could help you testing | 14:57 |
ajo | https://github.com/mangelajo/ovs-experiments/blob/master/qos/qos_traffic_shapping.sh#L124 | 14:57 |
ajo | hmm | 14:57 |
ajo | it's actually what I did | 14:57 |
*** amuller has left #openstack-meeting-3 | 14:58 | |
*** dane_leblanc has quit IRC | 14:58 | |
ajo | but it was limiting egress? | 14:58 |
ajo | may be I got it inverted | 14:58 |
gsagie | sorry | 14:58 |
gsagie | back | 14:58 |
ajo | hi gsagie | 14:58 |
ajo | we're near to the top of the hour | 14:58 |
gsagie | egress is more usefull sadasu | 14:59 |
irenab | ajo: i light of new feature request psocess | 14:59 |
gsagie | ok, anyone got to check the OF1.3 metering support in OVS? | 14:59 |
gsagie | i will try to find out for next meeting (or before) | 14:59 |
ajo | thanks gsagie | 14:59 |
irenab | process, do you plan to continue over existing spec till it gets accepted? | 14:59 |
ajo | #action vikram__ to check ingress_policing_rate | 15:00 |
ajo | #action gsagie to check OF1.3 metering and ratelimiting support in OVS | 15:00 |
*** JeanBriceCombebi has quit IRC | 15:00 | |
ajo | irenab, yes, it's a good field for discussion | 15:00 |
ajo | then, depending on what's decided, we could move it to devref | 15:00 |
ajo | or shrink it / split it | 15:01 |
ajo | does it sound reasonable? | 15:01 |
irenab | ajo: yes | 15:01 |
ajo | ok let's endmeeting for today | 15:02 |
ajo | #endmeeting | 15:02 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:02 | |
openstack | Meeting ended Wed May 6 15:02:21 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:02 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.html | 15:02 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.txt | 15:02 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-05-06-14.01.log.html | 15:02 |
ajo | thanks everybody :) | 15:02 |
vikram__ | bye | 15:02 |
ajo | vikram__, | 15:02 |
sadasu | thanks all! | 15:02 |
vhoward | bye, thank you | 15:02 |
sfinucan | cheers | 15:02 |
ajo | if you can, use my script to verify the ingress limiting, | 15:02 |
ajo | it's very simple, just run it... | 15:03 |
vikram__ | ok .. | 15:03 |
vikram__ | will try | 15:03 |
irenab | bye | 15:03 |
ajo | and verify the output, may be I mixed up things and I'm getting it inverted or something I thought it was egress | 15:03 |
vikram__ | thanks ajo | 15:03 |
ajo | but clearly, says "ingress" :) | 15:03 |
ajo | bye :) | 15:03 |
vikram__ | :) | 15:03 |
*** cbits has left #openstack-meeting-3 | 15:03 | |
*** vikram__ has quit IRC | 15:03 | |
*** sfinucan has left #openstack-meeting-3 | 15:04 | |
*** marun has joined #openstack-meeting-3 | 15:04 | |
*** JeanBriceCombebi has joined #openstack-meeting-3 | 15:07 | |
*** Sukhdev has quit IRC | 15:10 | |
*** pkoniszewski has joined #openstack-meeting-3 | 15:13 | |
*** armax has joined #openstack-meeting-3 | 15:13 | |
*** fallenpegasus has joined #openstack-meeting-3 | 15:15 | |
*** sadasu has quit IRC | 15:16 | |
*** lennyb has quit IRC | 15:18 | |
*** bpokorny has joined #openstack-meeting-3 | 15:24 | |
*** krtaylor has quit IRC | 15:31 | |
*** LouisF has joined #openstack-meeting-3 | 15:33 | |
*** Sukhdev has joined #openstack-meeting-3 | 15:43 | |
*** yamahata has joined #openstack-meeting-3 | 15:46 | |
*** bknudson has joined #openstack-meeting-3 | 15:46 | |
*** egallen has quit IRC | 15:50 | |
*** moshele has quit IRC | 15:54 | |
*** yalie has joined #openstack-meeting-3 | 15:55 | |
*** scheuran has quit IRC | 15:57 | |
*** wojdev has joined #openstack-meeting-3 | 15:58 | |
*** shakamunyi has quit IRC | 15:58 | |
*** sarob has joined #openstack-meeting-3 | 16:00 | |
*** wojdev has quit IRC | 16:05 | |
*** eghobo has joined #openstack-meeting-3 | 16:05 | |
*** wojdev has joined #openstack-meeting-3 | 16:06 | |
*** banix has joined #openstack-meeting-3 | 16:08 | |
*** bknudson has quit IRC | 16:09 | |
*** JeanBriceCombebi has quit IRC | 16:12 | |
*** bknudson has joined #openstack-meeting-3 | 16:14 | |
*** iovadia has quit IRC | 16:15 | |
*** LouisF has quit IRC | 16:15 | |
*** evgenyf has quit IRC | 16:16 | |
*** dheeraj-gupta-4 has joined #openstack-meeting-3 | 16:16 | |
*** pettori has joined #openstack-meeting-3 | 16:17 | |
*** wojdev has quit IRC | 16:24 | |
*** wojdev has joined #openstack-meeting-3 | 16:26 | |
*** jcoufal_ has quit IRC | 16:27 | |
*** pkoniszewski has quit IRC | 16:27 | |
*** safchain has quit IRC | 16:31 | |
*** krtaylor has joined #openstack-meeting-3 | 16:35 | |
*** wojdev has quit IRC | 16:36 | |
*** e0ne has quit IRC | 16:43 | |
*** wojdev has joined #openstack-meeting-3 | 16:44 | |
*** shakamunyi has joined #openstack-meeting-3 | 16:49 | |
*** marun has quit IRC | 16:49 | |
*** marun has joined #openstack-meeting-3 | 16:51 | |
*** sahid has quit IRC | 16:54 | |
*** wojdev has quit IRC | 16:54 | |
*** peristeri has quit IRC | 16:57 | |
*** mwang2 has joined #openstack-meeting-3 | 16:58 | |
*** igordcard_ has quit IRC | 16:59 | |
alaski | #startmeeting nova_cells | 17:00 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
*** openstack changes topic to " (Meeting topic: nova_cells)" | 17:00 | |
openstack | The meeting name has been set to 'nova_cells' | 17:00 |
*** banix has quit IRC | 17:00 | |
bauzas | \o | 17:00 |
alaski | hello hello | 17:00 |
melwitt | o/ | 17:00 |
dheeraj-gupta-4 | o/ | 17:00 |
*** tqtran has joined #openstack-meeting-3 | 17:01 | |
alaski | #topic Cellsv1 testing | 17:01 |
*** openstack changes topic to "Cellsv1 testing (Meeting topic: nova_cells)" | 17:01 | |
vineetmenon | o/ | 17:01 |
alaski | http://goo.gl/lZRucu | 17:01 |
alaski | a fix went in late yesterday for cellsv1 | 17:01 |
dansmith | o/ | 17:01 |
alaski | failures are low right now, but there's not much data yet | 17:02 |
alaski | there have been three failures, two of which were on stable branches | 17:02 |
bauzas | sounds nicer | 17:02 |
alaski | which does raise the question: can we vote on master only? or should we backport to stable? | 17:03 |
alaski | well, probably not an or | 17:03 |
dansmith | I think we can vote only on master | 17:03 |
alaski | okay, good | 17:03 |
bauzas | alaski: you mean having the job set to voting for master only ? | 17:03 |
alaski | yes | 17:03 |
bauzas | mmm, AFAIK the job is set to vote or not, and then we call it for any project | 17:04 |
*** wojdev has joined #openstack-meeting-3 | 17:04 | |
alaski | I 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 now | 17:04 |
*** banix has joined #openstack-meeting-3 | 17:05 | |
alaski | bauzas: okay. I guess we need to look into it to see what we can do | 17:05 |
*** shakamunyi has quit IRC | 17:05 | |
bauzas | alaski: https://github.com/openstack-infra/project-config/blob/master/zuul/layout.yaml#L652-L653 | 17:05 |
*** SumitNaiksatam has quit IRC | 17:05 | |
bauzas | alaski: we can add a branch | 17:06 |
bauzas | alaski: so the answer to your question is yes | 17:06 |
alaski | okay | 17:06 |
bauzas | who actions that ? | 17:06 |
alaski | I will propose some backports for stable, but in the meantime we should separate failures by branch | 17:07 |
*** pettori has quit IRC | 17:07 | |
alaski | and see how close we are to being good on master | 17:07 |
alaski | bauzas: it's not needed yet, was just a question | 17:07 |
bauzas | build_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 AFAICS | 17:08 |
bauzas | but sure we can leave it running for another round, sure | 17:08 |
alaski | it's been less than a day at this point | 17:09 |
bauzas | agreed | 17:09 |
alaski | #topic Specs | 17:09 |
*** openstack changes topic to "Specs (Meeting topic: nova_cells)" | 17:09 | |
alaski | the requestspec changes merged | 17:10 |
bauzas | yup | 17:10 |
bauzas | I'm working on the implem now | 17:10 |
alaski | so https://review.openstack.org/#/c/176078/ is next up for that series | 17:10 |
*** VW_ has quit IRC | 17:10 | |
alaski | bauzas: great | 17:10 |
bauzas | alaski: should provide a WIP patch soon | 17:11 |
alaski | when that gets to a good point I'll start working on perisistence, if the spec is merged | 17:11 |
bauzas | alaski: https://review.openstack.org/#/c/76234 is a dependency tho | 17:11 |
*** VW_ has joined #openstack-meeting-3 | 17:11 | |
alaski | I've completely changed the scope of https://review.openstack.org/#/c/141486/ | 17:11 |
alaski | scheduler interactions with cells | 17:11 |
alaski | bauzas: ok | 17:12 |
*** yamahata has quit IRC | 17:12 | |
alaski | while writing that last spec I found that we're missing a table to map hosts to cells, so I'll put something up for that | 17:12 |
*** shwetaap has quit IRC | 17:13 | |
bauzas | cool | 17:13 |
alaski | and I don't have a fleshed out spec for storing enough data to return an instance for a list/show | 17:13 |
*** yalie has quit IRC | 17:14 | |
alaski | so I need that as well | 17:14 |
dheeraj-gupta-4 | alaski: Mapping hosts to cells seems counter-intuitive | 17:14 |
*** wojdev has quit IRC | 17:14 | |
bauzas | dheeraj-gupta-4: why ? | 17:14 |
dheeraj-gupta-4 | A compute node can be added to a child cell any-time | 17:14 |
*** VW_ has quit IRC | 17:14 | |
dheeraj-gupta-4 | API cell shouldn't know or care how/when that is done | 17:14 |
*** [1]evgenyf has joined #openstack-meeting-3 | 17:15 | |
*** VW_ has joined #openstack-meeting-3 | 17:15 | |
alaski | dheeraj-gupta-4: it needs to know where to send messages for it | 17:15 |
dheeraj-gupta-4 | it only needs to know child cell | 17:15 |
alaski | right, but it needs to get that info from somewhere | 17:16 |
dheeraj-gupta-4 | maybe the child cell should handle the internals | 17:16 |
dheeraj-gupta-4 | but that's just over top of my head | 17:16 |
alaski | there are two cases here where we need to know how to route | 17:16 |
bauzas | dheeraj-gupta-4: how do you route calls ? | 17:16 |
alaski | the scheduler returns a host, which cell is it in? | 17:16 |
dheeraj-gupta-4 | maybe the spec will answer those questions | 17:16 |
alaski | the host api needs to update/query a host, where is it? | 17:16 |
*** igordcard_ has joined #openstack-meeting-3 | 17:17 | |
dheeraj-gupta-4 | hmm... cellsv1 style naming maybe | 17:17 |
dheeraj-gupta-4 | *shudders* | 17:17 |
alaski | yeah :) | 17:17 |
alaski | I think that for the most part a cell doesn't need to know it's a cell, or which cell it is | 17:18 |
alaski | that's a label the api cares about | 17:18 |
vineetmenon | dheeraj-gupta-4: any reservations against cell-host mapping? | 17:18 |
alaski | though that's muddled with scheduling slightly? | 17:18 |
alaski | woops, didn't mean a ? there | 17:18 |
dheeraj-gupta-4 | vineetmenon: No it just seemed odd for a moment | 17:18 |
alaski | dheeraj-gupta-4: I understand the hesitation. I'm open to alternatives that aren't named based. | 17:19 |
dheeraj-gupta-4 | yes.... I see the motivation now | 17:19 |
*** shakamunyi has joined #openstack-meeting-3 | 17:20 | |
dheeraj-gupta-4 | wasn't clear when you first mentioned it | 17:20 |
alaski | okay | 17:20 |
bauzas | dheeraj-gupta-4: I think you need to forget cells v1 :) | 17:20 |
dheeraj-gupta-4 | bauzas: :) | 17:20 |
bauzas | there should be no longer child and parent cells, just cells and api | 17:20 |
dheeraj-gupta-4 | cool | 17:21 |
alaski | so outside of the specs I mentioned, and one for multiple rpc endpoints, I think that's about what's on our plate this cycle | 17:21 |
alaski | and also the scheduling stuff that's not really cell specific but affects us | 17:21 |
alaski | anything else on specs? | 17:22 |
alaski | #topic Open Discussion | 17:22 |
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)" | 17:22 | |
alaski | if so it can go here | 17:22 |
alaski | anyone have something to bring up? | 17:22 |
dheeraj-gupta-4 | alaski: During Kilo closure one patch about talking to multiple DBs got held up | 17:23 |
bauzas | just 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-3 | 17:23 | |
bauzas | on a personal note, that's just conflicting my w/l balance :) | 17:23 |
alaski | bauzas: the 2200 one? | 17:23 |
dheeraj-gupta-4 | https://review.openstack.org/#/c/161906/ | 17:23 |
bauzas | nah, I'm fine with this one, the 1700 one | 17:24 |
bauzas | this time | 17:24 |
alaski | dheeraj-gupta-4: oh, thanks for bring that up | 17:24 |
alaski | that will be necessary as well | 17:24 |
alaski | I'm not sure where it falls spec wise at this point | 17:24 |
*** moshele has quit IRC | 17:24 | |
dansmith | moving the 1700UTC one an hour earlier will have conflicts for me | 17:25 |
alaski | dheeraj-gupta-4: it might be something we can just open a bp for | 17:25 |
dheeraj-gupta-4 | alaski: okay | 17:25 |
bauzas | dansmith: no worries, just asking the question :) | 17:25 |
bauzas | alaski: need resubmitting the spec ? | 17:25 |
bauzas | https://blueprints.launchpad.net/openstack/?searchtext=cells-v2-mapping gives 404 ;( | 17:25 |
*** ivar-lazzaro has joined #openstack-meeting-3 | 17:26 | |
alaski | bauzas: the spec was close as implemented afaik | 17:26 |
bauzas | alaski: so it was partial because it misses that change, right ? | 17:26 |
bauzas | missed even | 17:26 |
alaski | bauzas: I think we should go for a bp, it's not a big change | 17:26 |
bauzas | alaski: agreed | 17:27 |
*** SumitNaiksatam has joined #openstack-meeting-3 | 17:27 | |
alaski | also, 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 logs | 17:27 |
*** ivar-lazzaro has quit IRC | 17:27 | |
vineetmenon | alaski: so the alternate timing aren't applicable anymore? | 17:28 |
bauzas | alaski: ack | 17:28 |
alaski | vineetmenon: it still is. 1700 and 2100 | 17:28 |
*** ivar-lazzaro has joined #openstack-meeting-3 | 17:28 | |
bauzas | it's just all about family time for dinner :) | 17:28 |
bauzas | but that's fine | 17:29 |
dheeraj-gupta-4 | bauzas: 1700 UTC or 1600 UTC both work for me | 17:29 |
bauzas | I'll handle that | 17:29 |
bauzas | dheeraj-gupta-4: dansmith has conflicts for 1600, let's stick with the current time | 17:29 |
alaski | bauzas: totally understood. hard to get everyone with so many timezones | 17:29 |
vineetmenon | alaski: ack | 17:29 |
dheeraj-gupta-4 | bauzas: ok | 17:29 |
*** mattgriffin has quit IRC | 17:29 | |
*** clu_ has joined #openstack-meeting-3 | 17:30 | |
alaski | bauzas: lets revisit later, perhaps at the next dst shift | 17:30 |
alaski | anything else for today? | 17:31 |
bauzas | alaski: again, no worries | 17:31 |
alaski | bauzas: okay | 17:32 |
bauzas | crickets ? | 17:32 |
alaski | yep | 17:32 |
alaski | thanks everyone! | 17:32 |
alaski | #endmeeting | 17:32 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 17:32 | |
openstack | Meeting ended Wed May 6 17:32:20 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:32 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-05-06-17.00.html | 17:32 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-05-06-17.00.txt | 17:32 |
openstack | Log: http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-05-06-17.00.log.html | 17:32 |
*** dheeraj-gupta-4 has left #openstack-meeting-3 | 17:32 | |
*** vineetmenon has quit IRC | 17:33 | |
*** slaweq has joined #openstack-meeting-3 | 17:35 | |
*** ivar-laz_ has joined #openstack-meeting-3 | 17:35 | |
*** mattfarina has joined #openstack-meeting-3 | 17:36 | |
*** mattgriffin has joined #openstack-meeting-3 | 17:37 | |
*** shwetaap has joined #openstack-meeting-3 | 17:37 | |
*** ivar-lazzaro has quit IRC | 17:38 | |
*** btully has joined #openstack-meeting-3 | 17:38 | |
*** emagana has joined #openstack-meeting-3 | 17:39 | |
*** alexpilotti has quit IRC | 17:41 | |
*** VW_ has quit IRC | 17:41 | |
*** slaweq has quit IRC | 17:43 | |
*** Sukhdev has quit IRC | 17:43 | |
*** s3wong has joined #openstack-meeting-3 | 17:45 | |
*** alexpilotti has joined #openstack-meeting-3 | 17:46 | |
*** Sukhdev has joined #openstack-meeting-3 | 17:47 | |
*** Swami has joined #openstack-meeting-3 | 17:48 | |
*** pettori has joined #openstack-meeting-3 | 17:49 | |
*** e0ne has joined #openstack-meeting-3 | 17:50 | |
*** alexpilotti has quit IRC | 17:51 | |
*** alexpilotti has joined #openstack-meeting-3 | 17:52 | |
*** banix has quit IRC | 17:52 | |
*** VW_ has joined #openstack-meeting-3 | 17:54 | |
*** wojdev has joined #openstack-meeting-3 | 17:55 | |
*** banix has joined #openstack-meeting-3 | 17:56 | |
*** ongk_ has joined #openstack-meeting-3 | 17:58 | |
*** wojdev has quit IRC | 18:05 | |
*** wojdev has joined #openstack-meeting-3 | 18:08 | |
*** markmcclain has quit IRC | 18:09 | |
*** ongk_ has quit IRC | 18:10 | |
*** banix has quit IRC | 18:10 | |
*** reed has quit IRC | 18:11 | |
*** Sukhdev has quit IRC | 18:14 | |
*** reed has joined #openstack-meeting-3 | 18:14 | |
*** e0ne_ has joined #openstack-meeting-3 | 18:15 | |
*** e0ne has quit IRC | 18:15 | |
*** banix has joined #openstack-meeting-3 | 18:15 | |
*** e0ne has joined #openstack-meeting-3 | 18:17 | |
*** wojdev has quit IRC | 18:18 | |
*** e0ne_ has quit IRC | 18:20 | |
*** SridarK has joined #openstack-meeting-3 | 18:20 | |
*** mrmartin has joined #openstack-meeting-3 | 18:21 | |
*** rushiagr is now known as rushiagr_away | 18:23 | |
*** vikram__ has joined #openstack-meeting-3 | 18:24 | |
*** s3wong has quit IRC | 18:26 | |
*** baoli_ has quit IRC | 18:27 | |
*** badveli has joined #openstack-meeting-3 | 18:27 | |
*** s3wong has joined #openstack-meeting-3 | 18:27 | |
*** fallenpegasus has quit IRC | 18:28 | |
*** SumitNaiksatam_ has joined #openstack-meeting-3 | 18:28 | |
*** SumitNaiksatam has quit IRC | 18:30 | |
*** SumitNaiksatam_ is now known as SumitNaiksatam | 18:30 | |
*** slaweq has joined #openstack-meeting-3 | 18:30 | |
vishwanathj | hi SumitNaiksatam | 18:30 |
slaweq | hello | 18:30 |
badveli | hello all | 18:30 |
SumitNaiksatam | vishwanathj: hi | 18:30 |
SridarK | Hi All | 18:30 |
SumitNaiksatam | slaweq: badveli hi | 18:30 |
vishwanathj | Hi All | 18:30 |
badveli | hello sumit and all | 18:30 |
*** pettori has left #openstack-meeting-3 | 18:30 | |
xgerman | hi | 18:30 |
vikram__ | hi | 18:31 |
SumitNaiksatam | xgerman: vikram__ SridarK: hi | 18:31 |
SumitNaiksatam | #startmeeting Networking FWaaS | 18:31 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:31 |
*** openstack changes topic to " (Meeting topic: Networking FWaaS)" | 18:31 | |
openstack | The meeting name has been set to 'networking_fwaas' | 18:31 |
*** pc_m has joined #openstack-meeting-3 | 18:31 | |
*** Yi has joined #openstack-meeting-3 | 18:31 | |
pc_m | hi | 18:31 |
SumitNaiksatam | any announcements any one wants to share? | 18:31 |
SumitNaiksatam | pc_m: hi | 18:31 |
SumitNaiksatam | #topic Bugs | 18:32 |
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)" | 18:32 | |
sballe | hi | 18:32 |
SumitNaiksatam | sballe: hi | 18:32 |
SumitNaiksatam | we still have the high priority doc bug | 18:33 |
SumitNaiksatam | SridarK: thanks for posting the new patch set | 18:33 |
*** yamahata has joined #openstack-meeting-3 | 18:33 | |
*** lblanchard has quit IRC | 18:33 | |
SridarK | SumitNaiksatam: no worries - sorry learning this stuff :-) | 18:33 |
SumitNaiksatam | SridarK: badveli any other critical/high show up on your radar? | 18:33 |
SridarK | SumitNaiksatam: also thanks to pc_m for review and Diane F for fixing things | 18:34 |
SridarK | SumitNaiksatam: nothing from me | 18:34 |
*** lblanchard has joined #openstack-meeting-3 | 18:34 | |
SumitNaiksatam | pc_m: thanks as always | 18:34 |
SumitNaiksatam | yeah did notice diane posting immediate fixes | 18:34 |
pc_m | sure np | 18:34 |
SumitNaiksatam | is yushiro here? | 18:35 |
SumitNaiksatam | sorry i did not follow up on #link https://review.openstack.org/#/c/176589/ | 18:35 |
SumitNaiksatam | SridarK: do you know why the Cisco CI failed on this? | 18:35 |
SridarK | SumitNaiksatam: not sure - i will follow up on this | 18:36 |
SridarK | SumitNaiksatam: i don't think we should have any impact with the change | 18:36 |
SumitNaiksatam | SridarK: thanks | 18:36 |
SridarK | np at all | 18:37 |
vishwanathj | seems like there are lot of bugs related to FWaaS when using REST API...seeing that pattern | 18:37 |
SumitNaiksatam | any other bugs to discuss? | 18:37 |
SumitNaiksatam | vishwanathj: “lots” of bugs? | 18:37 |
vishwanathj | lots ==> 2 to 3 :) | 18:37 |
SumitNaiksatam | vishwanathj: i think those or validation bugs | 18:38 |
SumitNaiksatam | or -> are | 18:38 |
SumitNaiksatam | adding tighter validation to existing cases | 18:38 |
SumitNaiksatam | i am referring to a couple of those filed by yudhiro | 18:38 |
SumitNaiksatam | *yushiro | 18:38 |
vishwanathj | that's how I know that there are 2 or 3...yushiro has been finding them | 18:38 |
SumitNaiksatam | vishwanathj: but sorry to stop you, did you have a follow up comment to that? | 18:39 |
vishwanathj | I was going to ask if we are lacking tests | 18:39 |
SumitNaiksatam | vishwanathj: i think in general more test cases is always desired | 18:40 |
vishwanathj | so that we can look at it from that angle during reviews for future code commits | 18:40 |
vishwanathj | ok | 18:40 |
SumitNaiksatam | very few projects would be able to say - we are completely covered on the tests :-) | 18:41 |
vishwanathj | no more comments from me | 18:41 |
vishwanathj | agreed | 18:41 |
SumitNaiksatam | so yes definitely, any effort to add test coverage will be very much appreciated | 18:41 |
*** Yi has quit IRC | 18:41 | |
SridarK | i am also seeing this as a positive thing that more folks are looking at FWaaS | 18:41 |
SumitNaiksatam | SridarK: true | 18:41 |
vishwanathj | true | 18:41 |
SumitNaiksatam | yeah the more people beat it, the more things will be uncovered | 18:41 |
SumitNaiksatam | ok if nothing more on bugs, lets move on | 18:42 |
SumitNaiksatam | oh before we move on, SridarK is the doc patch complete, or do you need help with wrapping it up | 18:42 |
SumitNaiksatam | i am asking because vishwanathj was offering to help yesterday | 18:42 |
*** mattfarina has quit IRC | 18:42 | |
*** markmcclain has joined #openstack-meeting-3 | 18:42 | |
SridarK | SumitNaiksatam: thanks - i think i am good - i am hoping to get the policy and rule stuff pushed up today | 18:42 |
SridarK | SumitNaiksatam: will definitely need validation once that happens to make sure all attributes are covered | 18:43 |
SumitNaiksatam | SridarK: thanks | 18:43 |
SridarK | SumitNaiksatam: but i will shout out if i need some help :-) | 18:43 |
SumitNaiksatam | easy way to review for the rest of the team would be to look at the rendered docs | 18:44 |
SumitNaiksatam | rather than reading the source | 18:44 |
SridarK | this has been a pattern match and reproduce experience :-) | 18:44 |
SumitNaiksatam | SridarK: :-) | 18:44 |
SumitNaiksatam | ok moving on | 18:44 |
SumitNaiksatam | #topic Liberty Features | 18:45 |
*** openstack changes topic to "Liberty Features (Meeting topic: Networking FWaaS)" | 18:45 | |
SumitNaiksatam | last week i requested the team to update participate in updating the wiki #link https://wiki.openstack.org/wiki/Meetings/FWaaS | 18:45 |
SumitNaiksatam | i would hope that as we propose more features they get added to: #link https://wiki.openstack.org/wiki/Meetings/FWaaS#Blueprint_Tracking | 18:46 |
SumitNaiksatam | FWaaS Rules Direction: #link https://review.openstack.org/#/c/171340 | 18:46 |
SumitNaiksatam | slaweq: over to you | 18:46 |
slaweq | yep | 18:46 |
slaweq | I'm here | 18:47 |
slaweq | have You got any questions or sugestions about that? | 18:47 |
SridarK | slawek hi - had one query for discussion | 18:47 |
slaweq | yes? | 18:47 |
*** badveli has quit IRC | 18:47 | |
*** markvoelker has quit IRC | 18:47 | |
*** Longgeek has quit IRC | 18:47 | |
*** lsmola has quit IRC | 18:47 | |
*** jtomasek has quit IRC | 18:47 | |
*** smccully has quit IRC | 18:47 | |
*** aleksandr_null has quit IRC | 18:48 | |
*** russellb has quit IRC | 18:48 | |
*** haleyb has quit IRC | 18:48 | |
*** SotK has quit IRC | 18:48 | |
*** mrda has quit IRC | 18:48 | |
*** yamahata has quit IRC | 18:48 | |
*** mrmartin has quit IRC | 18:48 | |
*** e0ne has quit IRC | 18:48 | |
*** jkoelker has quit IRC | 18:48 | |
*** devananda has quit IRC | 18:48 | |
*** dobson has quit IRC | 18:48 | |
SumitNaiksatam | SridarK: please go ahead | 18:48 |
SridarK | slaweq: was wondering if had thoughts abt the direction being associated with a collection of rules as a policy or as a firewall | 18:48 |
*** badveli has joined #openstack-meeting-3 | 18:48 | |
SumitNaiksatam | i hope we didnt lose anyone in the split | 18:48 |
SridarK | slaweq: 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 |
slaweq | I didn't think about it | 18:49 |
*** yamahata has joined #openstack-meeting-3 | 18:49 | |
*** mrmartin has joined #openstack-meeting-3 | 18:49 | |
*** e0ne has joined #openstack-meeting-3 | 18:49 | |
*** dobson has joined #openstack-meeting-3 | 18:49 | |
*** devananda has joined #openstack-meeting-3 | 18:49 | |
*** jkoelker has joined #openstack-meeting-3 | 18:49 | |
*** sendak.freenode.net changes topic to "Bugs (Meeting topic: Networking FWaaS)" | 18:49 | |
*** badveli is now known as 43UAB93S3 | 18:49 | |
*** badveli has joined #openstack-meeting-3 | 18:49 | |
*** markvoelker has joined #openstack-meeting-3 | 18:49 | |
*** Longgeek has joined #openstack-meeting-3 | 18:49 | |
*** lsmola has joined #openstack-meeting-3 | 18:49 | |
*** jtomasek has joined #openstack-meeting-3 | 18:49 | |
*** smccully has joined #openstack-meeting-3 | 18:49 | |
*** aleksandr_null has joined #openstack-meeting-3 | 18:49 | |
*** russellb has joined #openstack-meeting-3 | 18:49 | |
*** haleyb has joined #openstack-meeting-3 | 18:49 | |
*** SotK has joined #openstack-meeting-3 | 18:49 | |
*** mrda has joined #openstack-meeting-3 | 18:49 | |
SridarK | slaweq: i am okay with what u have - but wanted to ask if that would make sense as well | 18:49 |
SridarK | fwaas folks here ? | 18:50 |
slaweq | I don't know, I was thinking about it more like about of iptables for example | 18:50 |
SumitNaiksatam | SridarK: i am still here :-) | 18:50 |
SridarK | :-) | 18:50 |
*** mattfarina has joined #openstack-meeting-3 | 18:50 | |
badveli | some problem, but i am here | 18:50 |
slaweq | so You can apply rule to specify "chain" by setting direction on it | 18:50 |
SridarK | sorry some activity going on at least as i see it in my viewer | 18:50 |
SumitNaiksatam | yeah, there was a network split | 18:50 |
vishwanathj | i am still here....but saw a bunch of people leave in batches and join in batches | 18:50 |
*** 43UAB93S3 has quit IRC | 18:50 | |
SridarK | slaweq: just a thought to discuss if it makes sense and evaluate | 18:51 |
vikram__ | yes | 18:51 |
* pc_m not here mentally :) | 18:51 | |
SumitNaiksatam | anyway, please continue, i think we did not lose anyone | 18:51 |
SumitNaiksatam | pc_m: lol! | 18:51 |
*** mattfarina has quit IRC | 18:51 | |
xgerman | + for iptables | 18:51 |
slaweq | ok, so You think about something like "ingrees policy" and "egress policy" | 18:51 |
SridarK | slaweq: i will post on the review - but thought we can do a quick discussion here too | 18:51 |
slaweq | instead of rules | 18:51 |
SridarK | slaweq: we don't have that notion on policy - we have single policy model | 18:52 |
SumitNaiksatam | SridarK: is it something you envision as an additional feature to what you slaweq has already proposed? | 18:52 |
SridarK | but sort of to say "lets FW all ingress traffic" | 18:52 |
SumitNaiksatam | or is it instead | 18:52 |
SridarK | SumitNaiksatam: no just looking at the notion of direction being applied at the rule level | 18:52 |
slaweq | imho if you want to firewall all ingress traffic You can put rule to allow all egrees and rules to filter ingress traffic | 18:53 |
slaweq | for example | 18:53 |
SridarK | slaweq: yes for sure | 18:53 |
SumitNaiksatam | slaweq: in your observation the granular usage in more prevalent? | 18:54 |
SridarK | slaweq: 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 egress | 18:54 |
SumitNaiksatam | in -> is | 18:54 |
SumitNaiksatam | SridarK: just to clarify, did you mean associating the direction with a firewall policy or a firewall? | 18:55 |
SridarK | slaweq: the granular is more flexible, just to dot the i's i ask the question | 18:55 |
SridarK | SumitNaiksatam: yes exactly | 18:55 |
SumitNaiksatam | i mean in the context of the vendor implementation | 18:55 |
*** dloi_ has joined #openstack-meeting-3 | 18:55 | |
SridarK | SumitNaiksatam: yes | 18:55 |
vikram__ | SridarK: Did you mean associating direction to a bundle of rules? | 18:56 |
SumitNaiksatam | for 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-3 | 18:56 | |
SridarK | vikram__: yes was asking if that is something that would make sense | 18:56 |
SridarK | SumitNaiksatam: yes exactly | 18:56 |
SumitNaiksatam | okay lets post the comments on the review | 18:57 |
SridarK | slaweq: i am ok with the proposal - just wanted to bring up the discussion and to get ur thoughts | 18:57 |
SumitNaiksatam | slaweq: sorry it took longer to get to this stage of the discussion | 18:57 |
vikram__ | but in the current model how to achieve it? | 18:57 |
slaweq | but 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 |
SridarK | slaweq: yes - u are correct | 18:57 |
slaweq | if firewall could have more than one policy then it may sense for me | 18:58 |
SumitNaiksatam | i 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-3 | 18:58 | |
SridarK | slaweq: definitely more flexibility - just wanted to look at it from a typical usage point of view | 18:58 |
vikram__ | sumit: +1 | 18:59 |
SumitNaiksatam | ok moving on to badveli’s spec and patch: #link https://review.openstack.org/#/c/94133 | 18:59 |
vishwanathj | slaweq, let me know if you need any help in coming up with Horizon blueprint and Horizon code for this? | 19:00 |
SridarK | slaweq: sorry for bringing this up late - intent is not derail - just to make sure we have covered all aspects | 19:00 |
*** mattfarina has joined #openstack-meeting-3 | 19:00 | |
slaweq | vishwanathj: thx, I will contact with You about it | 19:00 |
SumitNaiksatam | SridarK: good point to bring up though | 19:00 |
*** [1]evgenyf has quit IRC | 19:00 | |
SridarK | SumitNaiksatam: should have asked even earlier - brain needs more recharging :-) | 19:00 |
slaweq | SridarK: it's ok for me :) great that You are asking about it | 19:01 |
SumitNaiksatam | slaweq: +1, vishwanathj indeed thanks for offering to help out, thats great! | 19:01 |
SumitNaiksatam | badveli: there? | 19:01 |
badveli | yes | 19:01 |
slaweq | ok guys, I really have to leave now, thx for talking about my BP | 19:01 |
SumitNaiksatam | were you able to repurpose your spec for liberty? | 19:01 |
SumitNaiksatam | slaweq: thanks a bunch for joining, we will got to gerrit for your spec | 19:01 |
badveli | not yet sumit, | 19:02 |
*** slaweq has quit IRC | 19:02 | |
SumitNaiksatam | badveli: ok | 19:02 |
badveli | sumit, is some one already did the same it might be easier for me to talk | 19:03 |
badveli | to them and get this quickly | 19:03 |
SumitNaiksatam | badveli: i havent checked off late, but you can look at the commits on the neutron-specs tree | 19:03 |
SumitNaiksatam | last week i also brought up the topic about updating the “project plan” wiki page | 19:03 |
*** Sukhdev has joined #openstack-meeting-3 | 19:03 | |
SumitNaiksatam | based on the features we are working on | 19:03 |
badveli | thanks sumit | 19:03 |
SumitNaiksatam | vikram__: perhaps you can update in the context of the firewall rules direction | 19:04 |
SumitNaiksatam | #link https://wiki.openstack.org/wiki/Neutron/FWaaS/LibertyPlan | 19:04 |
SumitNaiksatam | SridarK: are you planning to add the zones spec? | 19:04 |
vikram__ | sure | 19:04 |
SumitNaiksatam | vikram__: thanks | 19:04 |
SridarK | SumitNaiksatam: yes will do so | 19:04 |
SridarK | And update - | 19:04 |
SumitNaiksatam | SridarK: there? | 19:06 |
SridarK | SumitNaiksatam: yes | 19:06 |
SumitNaiksatam | oh i thought you were saying there is an additional update in that context :-) | 19:06 |
SridarK | SumitNaiksatam: sorry - i thought my link bounced :-) | 19:06 |
SridarK | SumitNaiksatam: 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 too | 19:07 |
SumitNaiksatam | vishwanathj: i believe you were also interested in this, so you and SridarK can sync up | 19:07 |
SridarK | SumitNaiksatam: yes we bounced some ideas on this | 19:07 |
SumitNaiksatam | any other features that anyone wants to bring up? | 19:07 |
vishwanathj | SumitNaiksatam, definitely would like to work under SridarK guidance | 19:07 |
*** ivar-laz_ has quit IRC | 19:07 | |
SridarK | vishwanathj: will ping u and Karthik for some more thoughts too | 19:08 |
vishwanathj | SridarK, let me know if we need to have additional conversation | 19:08 |
*** ivar-lazzaro has joined #openstack-meeting-3 | 19:08 | |
vishwanathj | ok | 19:08 |
SridarK | vishwanathj: :-) yes | 19:08 |
SumitNaiksatam | anyone planning any other features for Liberty? | 19:08 |
SumitNaiksatam | yamahata: you had mentioned L4-7 classification and filtering | 19:09 |
SumitNaiksatam | yamahata: any update on the refernce implementation candidates? | 19:09 |
SridarK | SumitNaiksatam: i think yushiro also had some thoughts but i think he is traveling | 19:09 |
SumitNaiksatam | SridarK: oh okay, hopefully he will be at the design summit | 19:10 |
SridarK | SumitNaiksatam: yes i think he will be there | 19:10 |
SumitNaiksatam | nice | 19:10 |
SumitNaiksatam | perhaps yamahata is not around | 19:10 |
SumitNaiksatam | #topic Vendor drivers | 19:11 |
*** openstack changes topic to "Vendor drivers (Meeting topic: Networking FWaaS)" | 19:11 | |
SumitNaiksatam | any planned changes to the vendor drivers during liberty? | 19:11 |
SumitNaiksatam | if so please update: https://wiki.openstack.org/wiki/Neutron/FWaaS/LibertyPlan | 19:11 |
SridarK | SumitNaiksatam: would vendor stuff come out of the main tree in L ? | 19:11 |
SumitNaiksatam | so that we can track the reviews and progress of the patches | 19:11 |
SumitNaiksatam | SridarK: i dont know | 19:11 |
SumitNaiksatam | pc_m: do you know if we are pulling out the vendor drivers from *aas in liberty? | 19:12 |
SridarK | SumitNaiksatam: ok - will be interesting to see if we follow as for neutron | 19:12 |
pc_m | SumitNaiksatam: Haven't heard anything | 19:12 |
pc_m | SumitNaiksatam: I'm looking at pulling Cisco VPN drivers out, but no community drive to do that. | 19:13 |
SumitNaiksatam | pc_m: i was not aware of either | 19:13 |
SumitNaiksatam | pc_m: you feel that its a better model to pull the vendor driver out? | 19:13 |
pc_m | SumitNaiksatam: 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 |
SumitNaiksatam | pc_m: completely understand | 19:15 |
SumitNaiksatam | one 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 project | 19:15 |
SumitNaiksatam | they get more attention | 19:16 |
SridarK | SumitNaiksatam: yes the breakages are more obvious | 19:16 |
SumitNaiksatam | but one can also argue that with a good functional 3rd party CI you can catch things quickly | 19:16 |
*** salv-orl_ has joined #openstack-meeting-3 | 19:16 | |
SumitNaiksatam | anyway | 19:16 |
SumitNaiksatam | #topic Functional Tests | 19:17 |
*** openstack changes topic to "Functional Tests (Meeting topic: Networking FWaaS)" | 19:17 | |
SumitNaiksatam | badveli: any progress in your exploration? | 19:17 |
badveli | just started putting things | 19:17 |
SumitNaiksatam | badveli: nice | 19:17 |
badveli | tried an experiment code | 19:17 |
SumitNaiksatam | badveli: nice | 19:17 |
badveli | in unit tests | 19:17 |
badveli | directly | 19:17 |
SumitNaiksatam | badveli: okay | 19:17 |
badveli | using name space ping | 19:17 |
badveli | try to set up the actual rules instead of mock | 19:18 |
badveli | by using the snat name space | 19:18 |
*** yamahata has quit IRC | 19:18 | |
*** mrmartin has quit IRC | 19:18 | |
*** e0ne has quit IRC | 19:18 | |
*** jkoelker has quit IRC | 19:18 | |
*** devananda has quit IRC | 19:18 | |
SumitNaiksatam | badveli: with a view to making concrete progress, and faster, can i suggest that (a) you document your exploration on the wiki page | 19:18 |
SumitNaiksatam | (b) if you can post a WIP patch with the test code you have written | 19:19 |
badveli | yes, i can do that | 19:19 |
*** yamahata has joined #openstack-meeting-3 | 19:19 | |
*** mrmartin has joined #openstack-meeting-3 | 19:19 | |
*** e0ne has joined #openstack-meeting-3 | 19:19 | |
*** devananda has joined #openstack-meeting-3 | 19:19 | |
*** jkoelker has joined #openstack-meeting-3 | 19:19 | |
SumitNaiksatam | that way other folks can also jump in and split the work with you | 19:19 |
*** mrmartin has quit IRC | 19:19 | |
*** salv-orlando has quit IRC | 19:19 | |
*** mrmartin has joined #openstack-meeting-3 | 19:19 | |
SumitNaiksatam | badveli: thanks for the update | 19:20 |
SumitNaiksatam | #topic Open Discussion | 19:20 |
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)" | 19:20 | |
badveli | thanks sumit | 19:20 |
pc_m | You may want to look at VPN functional test for ideas. | 19:20 |
SumitNaiksatam | vikram__: were you able to get your devstack setup going with kilo? | 19:20 |
badveli | thanks pc_m, i will take a look | 19:20 |
SumitNaiksatam | badveli: pc_m is a great help | 19:20 |
pc_m | nothing committed yet, but out for review. | 19:21 |
badveli | yes thanks pcm_m | 19:21 |
pc_m | badveli: https://review.openstack.org/159746 | 19:21 |
SumitNaiksatam | pc_m has been blazing the trail in this regard, so please take his guidance | 19:21 |
badveli | i will take an example that will make my life easier | 19:21 |
SumitNaiksatam | pc_m: thanks | 19:21 |
*** vikram__ has quit IRC | 19:22 | |
pc_m | I did a bunch to setup fucntional tests to not stack devstack, but instead to do like Neutron and just configure. | 19:22 |
SumitNaiksatam | do we need to sync up on anything with regards to planning for the Liberty design summit sessions? | 19:22 |
pc_m | That commit is https://review.openstack.org/168115 | 19:22 |
SumitNaiksatam | pc_m: thanks | 19:22 |
SridarK | SumitNaiksatam: should we set a time where we can meet around a table at Vancouver ? | 19:23 |
vishwanathj | SumitNaiksatam, 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-3 | 19:24 | |
SumitNaiksatam | vishwanathj: great, thanks for the update (please feel free to add it to the agenda for future tracking) | 19:25 |
SumitNaiksatam | SridarK: +1 to that | 19:25 |
*** absubram has joined #openstack-meeting-3 | 19:25 | |
SumitNaiksatam | anything else to discuss today? | 19:26 |
SridarK | SumitNaiksatam: no i am good | 19:27 |
SumitNaiksatam | anyone else want to bring up anything? | 19:27 |
badveli | nothing from my side | 19:27 |
SumitNaiksatam | alrighty, thanks all for joining! | 19:28 |
pc_m | You guys meeting next week? | 19:28 |
SumitNaiksatam | oh yeah just wanted to ask | 19:28 |
SumitNaiksatam | shall we skip next week’s meeting? | 19:28 |
SumitNaiksatam | and meet directly at the summit? | 19:28 |
SridarK | SumitNaiksatam: sure okay bye me - | 19:28 |
vishwanathj | sounds good to me | 19:28 |
badveli | bye all | 19:28 |
vikram__ | bye | 19:28 |
SumitNaiksatam | okay, so i will send out an email to -dev | 19:28 |
SumitNaiksatam | pc_m: thanks for bringing that up ;-) | 19:28 |
*** coolsvap|afk has quit IRC | 19:28 | |
SumitNaiksatam | alright, bye all! | 19:29 |
SridarK | bye all | 19:29 |
SumitNaiksatam | see you in vancouver! | 19:29 |
pc_m | bye! | 19:29 |
*** pc_m has left #openstack-meeting-3 | 19:29 | |
SumitNaiksatam | #endmeeting | 19:29 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:29 | |
openstack | Meeting ended Wed May 6 19:29:26 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:29 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-05-06-18.31.html | 19:29 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-05-06-18.31.txt | 19:29 |
openstack | Log: http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-05-06-18.31.log.html | 19:29 |
*** SridarK has quit IRC | 19:29 | |
*** coolsvap|afk has joined #openstack-meeting-3 | 19:31 | |
*** badveli has left #openstack-meeting-3 | 19:36 | |
*** vikram__ has quit IRC | 19:42 | |
*** Piet has joined #openstack-meeting-3 | 19:42 | |
*** ajo has quit IRC | 19:44 | |
*** mwang2_ has joined #openstack-meeting-3 | 19:45 | |
*** s3wong has quit IRC | 19:45 | |
*** Aish has joined #openstack-meeting-3 | 19:45 | |
*** s3wong has joined #openstack-meeting-3 | 19:45 | |
*** jwang has joined #openstack-meeting-3 | 19:47 | |
*** mwang2 has quit IRC | 19:47 | |
*** Yi has joined #openstack-meeting-3 | 19:49 | |
*** baoli has joined #openstack-meeting-3 | 19:52 | |
*** Rockyg has joined #openstack-meeting-3 | 19:55 | |
*** r1chardj0n3s has joined #openstack-meeting-3 | 19:56 | |
*** jwy has joined #openstack-meeting-3 | 19:57 | |
*** esp has joined #openstack-meeting-3 | 20:00 | |
*** TravT has joined #openstack-meeting-3 | 20:00 | |
*** armax has quit IRC | 20:00 | |
esp | o/ | 20:00 |
r1chardj0n3s | o/ | 20:00 |
david-lyle | #startmeeting Horizon | 20:00 |
TravT | o/ | 20:00 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 20:00 |
*** openstack changes topic to " (Meeting topic: Horizon)" | 20:00 | |
openstack | The meeting name has been set to 'horizon' | 20:00 |
lhcheng | o/ | 20:00 |
absubram | o/ | 20:01 |
tqtran | o/ | 20:01 |
*** pkoniszewski has quit IRC | 20:01 | |
rhagarty_ | hello | 20:02 |
*** ducttape_ has joined #openstack-meeting-3 | 20:02 | |
*** doug-fish has joined #openstack-meeting-3 | 20:02 | |
david-lyle | letting people trickle in | 20:02 |
david-lyle | I think they're trickled | 20:03 |
*** igordcard has joined #openstack-meeting-3 | 20:03 | |
david-lyle | I don't have any general announcements today | 20:03 |
*** adurbin_ has joined #openstack-meeting-3 | 20:03 | |
david-lyle | I'm going to jump into the agenda | 20:04 |
david-lyle | #link https://wiki.openstack.org/wiki/Meetings/Horizon | 20:04 |
*** banix has quit IRC | 20: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 | |
lhcheng | hey | 20:05 |
david-lyle | hey | 20:05 |
david-lyle | got somethin' to say | 20:05 |
david-lyle | ? | 20:05 |
*** absubram has quit IRC | 20:05 | |
lhcheng | so rob found out that django14 support is going to be dropped oct 2015 | 20:05 |
bpokorny | Hi | 20:05 |
lhcheng | with that, we should probably drop django14 support for L | 20:06 |
lhcheng | should we publicize it first in operators before doing it? | 20:06 |
david-lyle | we need to support the next LTS 1.8 before we drop 1.4 | 20:07 |
david-lyle | but both should happen in L | 20:07 |
david-lyle | probably should publicize | 20:07 |
lhcheng | curious, why do we have to wait for LTS1.8? do we need to support last four releases? | 20:08 |
david-lyle | lhcheng: I think 1.5-1.6 aren't actually supported any more | 20:08 |
david-lyle | 1.7 is for now | 20:09 |
david-lyle | 1.8 is out, we just have to make sure it works with horizon | 20:09 |
david-lyle | (it doesn't) | 20:09 |
david-lyle | *spoiler alert | 20:09 |
lhcheng | david-lyle: lol | 20:09 |
* david-lyle may have done that in the wrong order | 20:10 | |
mrunge | in general, it works | 20:10 |
lhcheng | and the gate gate-horizon-python27-django14 moves to django17 then? | 20:10 |
david-lyle | lhcheng: yeah | 20:10 |
david-lyle | once we have 1.8 we could look at dropping 1.5 and 1.6 as well | 20:10 |
*** ongk_ has joined #openstack-meeting-3 | 20:10 | |
david-lyle | mrunge: just a few more issues to work out in d-o-a | 20:10 |
*** jcoufal has joined #openstack-meeting-3 | 20:11 | |
mrunge | david-lyle, yes- | 20:11 |
mrunge | we may rework our permissions system | 20:11 |
*** jcoufal has quit IRC | 20:11 | |
david-lyle | hmm | 20:11 |
mrunge | s/may/may need/ | 20:11 |
david-lyle | I meant to do that anyway | 20:11 |
david-lyle | with policy and has_perm in the same place now | 20:12 |
david-lyle | we can take that offline | 20:12 |
mrunge | yes | 20:12 |
david-lyle | any opinions on how many release we should stop supporting? | 20:12 |
mrunge | but this is something, I'm committed to | 20:12 |
TravT | mrunge: i'm interested in that as well. | 20:12 |
mrunge | cool! | 20:12 |
david-lyle | 1.7 introduces a lot of new features | 20:12 |
mrunge | sounds good | 20:13 |
david-lyle | spanning so many releases makes us do strange things | 20:13 |
mrunge | since we're gating on them, it's not that bad | 20:14 |
david-lyle | we'll start with fixing up 1.8, drop 1.4 and see where we end up on 1.5 and 1.6 | 20:14 |
*** cbouch has left #openstack-meeting-3 | 20:14 | |
*** yamahata has quit IRC | 20:14 | |
mrunge | sounds like a plan | 20:14 |
david-lyle | lhcheng: is there a bp to drop 1.4? | 20:15 |
lhcheng | david-lyle: sounds good, that question could also go with the django14 drop announcement | 20:15 |
lhcheng | david-lyle: don't think so | 20:15 |
david-lyle | sure | 20:15 |
david-lyle | let's add one | 20:15 |
doug-fish | does dropping 1.4 for Liberty affect anything for Juno/Kilo? | 20:15 |
mrunge | doug-fish, I wouldn't think so | 20:15 |
*** absubram has joined #openstack-meeting-3 | 20:15 | |
david-lyle | shouldn't, except certain backports will become trickier | 20:15 |
doug-fish | gate jobs? | 20:16 |
david-lyle | but since we're not adding features in backports | 20:16 |
david-lyle | the risk of conflict should be minor | 20:16 |
mrunge | david-lyle, it doesn't hurt us, if we're still gating on 1.4, right? | 20:16 |
doug-fish | I was wondering more if it mattered with the "drop 1.4" part of the plan | 20:16 |
david-lyle | mrunge: not in d-o-a IIRC | 20:16 |
*** mattfarina has quit IRC | 20:17 | |
mrunge | david-lyle, I mean, for juno | 20:17 |
david-lyle | shouldn't effect juno | 20:17 |
david-lyle | 1.4 job will still run | 20:17 |
lhcheng | mrunge: yeah, we should keep those job | 20:17 |
david-lyle | #topic Session data cleanup (lhcheng) | 20:18 |
*** openstack changes topic to "Session data cleanup (lhcheng) (Meeting topic: Horizon)" | 20:18 | |
mrunge | lhcheng++ on this! | 20:18 |
ducttape_ | can we remove the "allowed" cache thing from the session? | 20:18 |
lhcheng | for the session data, we keep on hitting the cookie limit | 20:18 |
david-lyle | allowed? | 20:18 |
david-lyle | oh, for nav? | 20:19 |
mrunge | ugh! that hurts | 20:19 |
ducttape_ | the cached permission thing, yep | 20:19 |
lhcheng | david-lyle: https://review.openstack.org/#/c/120790/ | 20:19 |
lhcheng | so I've been playing around to reduce the session size | 20:19 |
lhcheng | the "allowed" cache thing, takes 34% of the session size | 20:19 |
david-lyle | that's rediculous | 20:20 |
ducttape_ | that's less betta' | 20:20 |
lhcheng | I suggest to move the caching from session to the django cache instead | 20:20 |
lhcheng | or maybe just drop it? | 20:20 |
mrunge | you know how often that's called per page view? | 20:20 |
david-lyle | should be once per page view | 20:21 |
david-lyle | but the number required should be dropping | 20:21 |
mrunge | without caching 10-20 times | 20:21 |
mrunge | I tried earlier today | 20:21 |
david-lyle | mrunge: you mean building the cache? | 20:21 |
david-lyle | or how many times the cache is read? | 20:22 |
mrunge | david-lyle, I mean, times read | 20:22 |
ducttape_ | all the nav items in the layout stuff, are hiting that a bunch of times | 20:22 |
mrunge | yes, we should keep the cache | 20:22 |
david-lyle | we want to move to a model where we don't rebuild the nav on ever panel load | 20:22 |
david-lyle | only on rescope | 20:22 |
mrunge | sounds better | 20:22 |
ducttape_ | what is the perf difference with that disabled mrunge? is it noticeable? | 20:23 |
mrunge | ducttape_, I can't really tell | 20:23 |
david-lyle | ducttape_: I really think it was for testing | 20:23 |
mrunge | I didn't measure that | 20:23 |
ducttape_ | ok, thanks | 20:23 |
lhcheng | david-lyle: if the user rescope, this cache does not get reset. you just found a bug. :P | 20:23 |
r1chardj0n3s | in the interim, could a localstorage be used instead of django cache? just thinking of future nav work here ;) | 20:23 |
TravT | lhcheng: 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 use | 20:24 |
TravT | on the angular side there is also caching | 20:24 |
TravT | once per page load | 20:24 |
r1chardj0n3s | ok | 20:24 |
david-lyle | r1chardj0n3s: I would believe that the nav component of the page will no longer need to reload | 20:24 |
david-lyle | thus the purpose of the cache would be gone | 20:25 |
r1chardj0n3s | david-lyle: that's the intention, yes | 20:25 |
TravT | but 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 |
tqtran | well, we can still use localStorage to store things like "last visited page" | 20:25 |
david-lyle | only the panel part of the page is loading | 20:25 |
ducttape_ | someplace besides the session? | 20:25 |
lhcheng | ducttape_: yeah, just store it in django's built-in cache framework | 20:25 |
*** e0ne has quit IRC | 20:26 | |
lhcheng | could be by process, file cache, memche | 20:26 |
ducttape_ | and that would have a unique spot for each user / token then? | 20:26 |
*** mattfarina has joined #openstack-meeting-3 | 20:26 | |
lhcheng | yeah, just need to use a unique key for that user/token | 20:26 |
*** Yi has quit IRC | 20:26 | |
*** mattfarina has quit IRC | 20:26 | |
david-lyle | ok, I think we're all for reducing session size, we can discuss the particulars in a couple of weeks | 20:27 |
ducttape_ | +1 lhcheng, our session stuff is a constant hassle. ship it | 20:27 |
mrunge | yes, session size issues are hard to debug | 20:28 |
lhcheng | so got the size drop by 75% on my local | 20:28 |
mrunge | cool | 20:28 |
lhcheng | david-lyle: sure, we can discuss the details later | 20:28 |
david-lyle | #topic Summit Scheduling (david-lyle) | 20:28 |
*** openstack changes topic to "Summit Scheduling (david-lyle) (Meeting topic: Horizon)" | 20:28 | |
david-lyle | I wanted to make sure we have enough time for this | 20:29 |
david-lyle | session size/storage happens to be one of the proposed topics too | 20:29 |
*** emagana has quit IRC | 20:29 | |
david-lyle | #link https://etherpad.openstack.org/p/horizon-liberty-summit | 20:29 |
*** banix has joined #openstack-meeting-3 | 20:29 | |
ducttape_ | can we also talk about session size then? | 20:29 |
david-lyle | ducttape_: no | 20:29 |
david-lyle | :P | 20:29 |
david-lyle | let's talk session allocation | 20:30 |
*** ivar-lazzaro has quit IRC | 20:30 | |
*** baoli has quit IRC | 20:30 | |
david-lyle | someone did a nice job sorting through these, I assume either doug-fish or robcresswell | 20:31 |
david-lyle | not sure | 20:31 |
*** ivar-lazzaro has joined #openstack-meeting-3 | 20:31 | |
doug-fish | I took a shot at it | 20:31 |
*** baoli has joined #openstack-meeting-3 | 20:31 | |
david-lyle | thanks doug-fish | 20:31 |
doug-fish | sure np | 20:31 |
david-lyle | So doug-fish split out topics starting about line 37 | 20:31 |
TravT | the topics you put at top are down to a single word, so now sure what is meant by some of them | 20:32 |
david-lyle | I need to publish a schedule so I started trying to figure out what are fishbowl and what are working sessions | 20:32 |
david-lyle | TravT: they reference the topics starting on 37 | 20:32 |
david-lyle | my lazin^H^H^H^H^Hshorthand | 20:32 |
david-lyle | line 63, I don't think websockets applies | 20:33 |
david-lyle | to that topic | 20:33 |
david-lyle | I think it would go more with messaging | 20:33 |
mrunge | yeah | 20:33 |
david-lyle | if anything | 20:33 |
mrunge | it's just a q, if we want to go that route | 20:34 |
*** e0ne has joined #openstack-meeting-3 | 20:34 | |
mrunge | there were so many issues to be solved with that | 20:34 |
TravT | there is a small aspect of websockets aspect to what I'd like to show / talk about with elastic search. | 20:34 |
TravT | but is not the main point, so separating them is fine with me. | 20:34 |
david-lyle | do people agree with the fishbowl topics? | 20:35 |
mrunge | I wouldn't think, *any* messaging infrastructure should take a whole session | 20:35 |
absubram | Hi 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 |
TravT | so plugins is really broad. | 20:36 |
david-lyle | mrunge: I think better error messages and websockets could share a working session ? | 20:36 |
mrunge | do we want UX in a bigger plenum? | 20:36 |
mrunge | david-lyle, yes! | 20:36 |
absubram | Rob 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 IRC | 20:37 | |
TravT | david-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 fishbowl | 20:37 |
absubram | some time in the contributor meetup is fine too.. unless others have a different opinion? mrunge? :) | 20:37 |
david-lyle | TravT: absubram so for plugins | 20:37 |
david-lyle | I think it's a fishbowl and a worksession | 20:37 |
TravT | but does that cover tech discussion? | 20:37 |
TravT | ah, ok | 20:37 |
mrunge | absubram, that would be fishbowl number one | 20:38 |
absubram | ok.. that’s fine! | 20:38 |
david-lyle | I want to describe the proposed split and structure | 20:38 |
mrunge | david-lyle, do we have the possibility to have working sessions after fish bowls? | 20:38 |
david-lyle | in the fishbowl and then use a working session to plan on implementation | 20:39 |
*** carl_baldwin has quit IRC | 20:39 | |
david-lyle | https://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit#gid=569963128 | 20:39 |
TravT | david-lyle, which one does dependencies refer to? | 20:39 |
TravT | is that packaging? | 20:39 |
david-lyle | mrunge: looks like yes | 20:40 |
david-lyle | TravT: yes | 20:40 |
*** carl_baldwin has joined #openstack-meeting-3 | 20:40 | |
david-lyle | we'll have to see how the cross-project session goes, I suppose | 20:41 |
*** sqchen has joined #openstack-meeting-3 | 20:41 | |
TravT | So angular 101 is really broad. | 20:41 |
david-lyle | TravT: yes indeed | 20:42 |
david-lyle | we need more than 1 angular session | 20:42 |
david-lyle | that one was the 101 to get people up to speed that haven't been neck deep in it | 20:42 |
TravT | yeah, it'll be tough to cover in 40 minutes that topic. | 20:43 |
TravT | Maybe the other topic could be an overview of our ideas for moving forward with angular in liberty | 20:43 |
r1chardj0n3s | good idea | 20:44 |
david-lyle | TravT: it's not a tutorial or class, just a pointer to where we are and how to get started | 20:44 |
david-lyle | OR we could move the angular chatter to Friday | 20:44 |
david-lyle | we have all day Friday | 20:44 |
r1chardj0n3s | david-lyle: should cover the styles, rules and layout we've developed for horizon | 20:44 |
david-lyle | maybe Friday morning is a better angular time? | 20:45 |
r1chardj0n3s | yeah, when we're all fresh ;) | 20:45 |
*** e0ne has quit IRC | 20:45 | |
david-lyle | haha | 20:46 |
david-lyle | do we want a prioritization work session? | 20:46 |
mrunge | makes sense | 20:47 |
TravT | That was a good discussion in the contributors meetup in Paris | 20:47 |
TravT | As FYI, a number of HP'ers working on angular have to depart shortly after noon on Friday. :( | 20:47 |
david-lyle | friday afternoon then | 20:48 |
david-lyle | :P | 20:48 |
r1chardj0n3s | TravT: is that leave-the-venue depart or fly-out depart? | 20:48 |
TravT | :) | 20:48 |
TravT | leave the venue | 20:48 |
TravT | I have to leave the venue at about 2. | 20:48 |
r1chardj0n3s | ok, so we get a solid morning to hassle^H^H^H^H^H^Hwork with you | 20:48 |
david-lyle | Keystone could be meetup topic too | 20:48 |
david-lyle | giving merlin a session would be good | 20:49 |
TravT | mrunge put a topic up that would be good at some point. Moving forward with functions / deprecating old | 20:51 |
mrunge | TravT, yes! | 20:51 |
mrunge | TravT, more interesting: how to fix older releases then | 20:52 |
mrunge | since it's expected to fix in master branch first | 20:52 |
TravT | straight patch i guess. no cherry picking | 20:52 |
mrunge | we already discussed that | 20:52 |
mrunge | TravT, still that bears the risk of patching an issue in master-1 which is still existent in master | 20:52 |
mrunge | I wonder, if we really need a whole session for this | 20:54 |
david-lyle | I've been editing away | 20:54 |
david-lyle | numbering is not priority btw | 20:54 |
david-lyle | feel free to comment inline or pull something up | 20:55 |
tqtran | do we need a session for discussing karma and jasmine tests? | 20:55 |
tqtran | or just jasmine 101? | 20:55 |
david-lyle | i think that may be part of angular 101 | 20:56 |
r1chardj0n3s | so that 40 minutes is filling up quite nicely then ;) | 20:56 |
TravT | tqtran: matt-borland also can help give a great overview of that and demo stuff related to karma | 20:56 |
david-lyle | r1chardj0n3s: moved it to Friday morning | 20:57 |
david-lyle | for continuity | 20:57 |
david-lyle | sake | 20:57 |
david-lyle | plus I have a feeling more people will show up than just the 28 or so the working session supports | 20:57 |
TravT | 28 people... that's small | 20:58 |
r1chardj0n3s | mmm | 20:58 |
mrunge | we should have a backup plan | 20:58 |
TravT | i guess we all better get in line and camp out overnight | 20:58 |
david-lyle | hence working session | 20:58 |
mrunge | a second topic | 20:58 |
mrunge | and just capture a different room | 20:58 |
david-lyle | times up | 20:59 |
david-lyle | I have yet to decide how descriptive the topics for the working sessions will be | 20:59 |
david-lyle | don't want too many people | 20:59 |
david-lyle | observing | 20:59 |
TravT | i think we had about 40 in the contributor's meetup | 20:59 |
david-lyle | I'll let the etherpad sit for another day or so then publish a schedule | 21:00 |
david-lyle | continue to comment on the proposed allocation of spots. | 21:00 |
david-lyle | Thanks everyone! | 21:00 |
david-lyle | #endmeeting | 21:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 21:00 | |
openstack | Meeting ended Wed May 6 21:00:32 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:00 |
esp | thx! | 21:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-05-06-20.00.html | 21:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-05-06-20.00.txt | 21:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-05-06-20.00.log.html | 21:00 |
absubram | bye all! thanks! | 21:00 |
*** ducttape_ has left #openstack-meeting-3 | 21:00 | |
*** r1chardj0n3s has left #openstack-meeting-3 | 21:00 | |
*** absubram has quit IRC | 21:01 | |
*** emagana has joined #openstack-meeting-3 | 21:01 | |
*** jwy has left #openstack-meeting-3 | 21:02 | |
*** LouisF has joined #openstack-meeting-3 | 21:03 | |
*** Sukhdev has quit IRC | 21:03 | |
*** LouisF has quit IRC | 21:04 | |
*** emagana has quit IRC | 21:06 | |
*** TravT has quit IRC | 21:09 | |
*** adurbin_ has left #openstack-meeting-3 | 21:09 | |
*** tqtran has left #openstack-meeting-3 | 21:10 | |
*** ongk_ has quit IRC | 21:12 | |
*** Swami has joined #openstack-meeting-3 | 21:13 | |
*** lblanchard has quit IRC | 21:14 | |
*** maurosr has quit IRC | 21:21 | |
*** jgrimm_ has quit IRC | 21:22 | |
*** maurosr has joined #openstack-meeting-3 | 21:22 | |
*** jgrimm has joined #openstack-meeting-3 | 21:23 | |
*** Longgeek has quit IRC | 21:23 | |
*** david-lyle has quit IRC | 21:29 | |
*** sqchen has left #openstack-meeting-3 | 21:32 | |
*** shwetaap has quit IRC | 21:38 | |
*** asahlin is now known as asahlin_afk | 21:41 | |
*** baoli has quit IRC | 21:43 | |
*** baoli has joined #openstack-meeting-3 | 21:44 | |
*** btully has quit IRC | 21:45 | |
*** alexpilotti has quit IRC | 21:46 | |
*** jtomasek has quit IRC | 21:49 | |
*** baoli has quit IRC | 21:54 | |
*** baoli has joined #openstack-meeting-3 | 21:55 | |
*** mrmartin has quit IRC | 21:56 | |
*** stevemar has quit IRC | 21:57 | |
*** eghobo_ has joined #openstack-meeting-3 | 21:59 | |
*** maurosr has quit IRC | 21:59 | |
*** eghobo has quit IRC | 22:00 | |
*** maurosr has joined #openstack-meeting-3 | 22:03 | |
*** s3wong has quit IRC | 22:06 | |
*** jgrimm has quit IRC | 22:07 | |
*** s3wong_ has joined #openstack-meeting-3 | 22:07 | |
*** jgrimm has joined #openstack-meeting-3 | 22:09 | |
*** fallenpegasus has joined #openstack-meeting-3 | 22:09 | |
*** maurosr has quit IRC | 22:12 | |
*** maurosr has joined #openstack-meeting-3 | 22:14 | |
*** etoews has joined #openstack-meeting-3 | 22:15 | |
*** VW_ has quit IRC | 22:15 | |
*** DinaBelova has quit IRC | 22:30 | |
*** DinaBelova has joined #openstack-meeting-3 | 22:31 | |
*** Piet has quit IRC | 22:35 | |
*** s3wong_ has quit IRC | 22:36 | |
*** s3wong has joined #openstack-meeting-3 | 22:36 | |
*** sarob has quit IRC | 22:38 | |
*** salv-orl_ has quit IRC | 22:38 | |
*** jckasper has quit IRC | 22:39 | |
*** salv-orlando has joined #openstack-meeting-3 | 22:40 | |
*** baoli has quit IRC | 22:41 | |
*** baoli has joined #openstack-meeting-3 | 22:42 | |
*** carl_baldwin has quit IRC | 22:42 | |
*** fallenpegasus has quit IRC | 22:43 | |
*** fallenpegasus has joined #openstack-meeting-3 | 22:44 | |
*** emagana has joined #openstack-meeting-3 | 22:45 | |
*** banix has quit IRC | 22:47 | |
*** fallenpegasus has quit IRC | 22:48 | |
*** mrunge has quit IRC | 22:50 | |
*** Piet has joined #openstack-meeting-3 | 22:54 | |
*** Piet has quit IRC | 22:54 | |
*** armax has joined #openstack-meeting-3 | 22:57 | |
*** SumitNaiksatam has quit IRC | 22:58 | |
*** bknudson has quit IRC | 22:58 | |
*** banix has joined #openstack-meeting-3 | 23:00 | |
*** armax has quit IRC | 23:04 | |
*** maurosr has quit IRC | 23:05 | |
*** maurosr has joined #openstack-meeting-3 | 23:08 | |
*** baoli has quit IRC | 23:10 | |
*** vishwanathj_ has joined #openstack-meeting-3 | 23:22 | |
*** Piet has joined #openstack-meeting-3 | 23:28 | |
*** mattgriffin has quit IRC | 23:29 | |
*** nelsnelson has quit IRC | 23:31 | |
*** Rockyg has quit IRC | 23:32 | |
*** banix has quit IRC | 23:33 | |
*** watanabe_isao has joined #openstack-meeting-3 | 23:38 | |
*** sarob has joined #openstack-meeting-3 | 23:42 | |
*** david-lyle has joined #openstack-meeting-3 | 23:47 | |
*** VW_ has joined #openstack-meeting-3 | 23:57 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!