Wednesday, 2015-06-03

*** pballand has quit IRC00:11
*** shakamunyi has joined #openstack-meeting-300:13
*** barra204 has joined #openstack-meeting-300:13
*** jxstanford has joined #openstack-meeting-300:13
*** hurglebu_ has quit IRC00:14
*** hurgleburgler has joined #openstack-meeting-300:14
*** hurgleburgler has quit IRC00:17
*** hurgleburgler has joined #openstack-meeting-300:18
*** hurgleburgler has quit IRC00:21
*** hurglebu_ has joined #openstack-meeting-300:21
*** puranamr has quit IRC00:23
*** hurglebu_ has quit IRC00:24
*** nelsnelson has quit IRC00:24
*** nelsnelson has joined #openstack-meeting-300:25
*** sbalukoff has quit IRC00:29
*** VW has joined #openstack-meeting-300:29
*** zhenguo has joined #openstack-meeting-300:33
*** Sukhdev has quit IRC00:35
*** shwetaap has quit IRC00:35
*** Caleb-- has quit IRC00:38
*** Caleb-- has joined #openstack-meeting-300:43
*** salv-orlando has joined #openstack-meeting-300:48
*** puranamr has joined #openstack-meeting-300:48
*** puranamr has quit IRC00:52
*** egallen has joined #openstack-meeting-300:52
*** Swami has quit IRC00:53
*** salv-orlando has quit IRC00:55
*** irenab_ has joined #openstack-meeting-300:57
*** irenab has quit IRC00:58
*** irenab_ is now known as irenab00:58
*** fallenpegasus has joined #openstack-meeting-300:59
*** Aish has quit IRC01:05
*** jrist has quit IRC01:08
*** fallenpegasus has quit IRC01:09
*** nelsnelson has quit IRC01:12
*** superfly_ has joined #openstack-meeting-301:12
*** bpokorny has quit IRC01:12
*** alexsyip has quit IRC01:12
*** superfly_ is now known as superflyy01:14
*** jrist has joined #openstack-meeting-301:20
*** amotoki has quit IRC01:21
*** sridhar_ram has quit IRC01:22
*** barra204 has quit IRC01:24
*** shakamunyi has quit IRC01:24
*** superflyy has quit IRC01:24
*** tobe has joined #openstack-meeting-301:33
*** eghobo has quit IRC01:33
*** stanzgy has joined #openstack-meeting-301:36
*** s3wong has quit IRC01:40
*** amotoki has joined #openstack-meeting-301:41
*** puranamr has joined #openstack-meeting-301:41
*** baoli has quit IRC01:41
*** sridhar_ram has joined #openstack-meeting-301:44
*** amotoki has quit IRC01:45
*** nelsnelson has joined #openstack-meeting-301:51
*** shwetaap has joined #openstack-meeting-301:52
*** Networkn3rd has joined #openstack-meeting-301:58
*** amotoki has joined #openstack-meeting-302:04
*** VW has quit IRC02:04
*** VW has joined #openstack-meeting-302:05
*** nelsnelson has quit IRC02:05
*** salv-orlando has joined #openstack-meeting-302:08
*** rushiagr_away is now known as rushiagr02:09
*** egallen has quit IRC02:13
*** salv-orlando has quit IRC02:14
*** yamahata has quit IRC02:17
*** sridhar_ram has quit IRC02:19
*** shwetaap has quit IRC02:21
*** puranamr has quit IRC02:22
*** baoli has joined #openstack-meeting-302:23
*** eglute has joined #openstack-meeting-302:29
*** ivar-laz_ has joined #openstack-meeting-302:37
*** ivar-laz_ has quit IRC02:37
*** Networkn3rd has quit IRC02:40
*** rushiagr is now known as rushiagr_away02:40
*** ivar-lazzaro has quit IRC02:40
*** nelsnelson has joined #openstack-meeting-302:41
*** baoli has quit IRC02:49
*** puranamr has joined #openstack-meeting-302:55
*** dims__ has quit IRC02:56
*** puranamr has quit IRC02:58
*** jxstanfo_ has joined #openstack-meeting-303:14
*** jxstanf__ has joined #openstack-meeting-303:15
*** jxstanford has quit IRC03:18
*** jxstanfo_ has quit IRC03:19
*** jxstanf__ has quit IRC03:19
*** nelsnelson has quit IRC03:30
*** puranamr has joined #openstack-meeting-303:43
*** markvoelker has quit IRC03:44
*** sarob has joined #openstack-meeting-303:45
*** j^2 has joined #openstack-meeting-303:52
*** Longgeek_ has quit IRC03:53
*** Longgeek has joined #openstack-meeting-303:54
*** puranamr has quit IRC03:54
*** alexpilotti has joined #openstack-meeting-303:54
*** Aish has joined #openstack-meeting-303:55
*** Aish has left #openstack-meeting-303:55
*** Longgeek_ has joined #openstack-meeting-303:57
*** puranamr has joined #openstack-meeting-303:59
*** Longgeek has quit IRC04:00
*** Longgeek has joined #openstack-meeting-304:02
*** Longgeek_ has quit IRC04:04
*** sarob has quit IRC04:06
*** Longgeek_ has joined #openstack-meeting-304:08
*** Swami has joined #openstack-meeting-304:09
*** salv-orlando has joined #openstack-meeting-304:10
*** Longgeek has quit IRC04:10
*** nelsnelson has joined #openstack-meeting-304:11
*** Longgeek_ has quit IRC04:12
*** Swami_ has joined #openstack-meeting-304:15
*** pballand has joined #openstack-meeting-304:16
*** Swami has quit IRC04:17
*** Longgeek has joined #openstack-meeting-304:18
*** Longgeek has quit IRC04:18
*** Longgeek has joined #openstack-meeting-304:19
*** Longgeek has quit IRC04:20
*** Longgeek has joined #openstack-meeting-304:20
*** Swami_ has quit IRC04:21
*** Longgeek_ has joined #openstack-meeting-304:23
*** banix has quit IRC04:24
*** Longgee__ has joined #openstack-meeting-304:25
*** Longgeek has quit IRC04:25
*** VW has quit IRC04:26
*** Longgeek_ has quit IRC04:26
*** Longgeek has joined #openstack-meeting-304:26
*** Longgeek_ has joined #openstack-meeting-304:28
*** Longge___ has joined #openstack-meeting-304:29
*** Longgee__ has quit IRC04:30
*** coolsvap|afk is now known as coolsvap04:30
*** coolsvap is now known as coolsvap|afk04:31
*** Longgeek has quit IRC04:32
*** coolsvap|afk is now known as coolsvap04:32
*** Longgeek_ has quit IRC04:32
*** mrmartin has joined #openstack-meeting-304:33
*** Swami has joined #openstack-meeting-304:38
*** krtaylor has quit IRC04:40
*** markvoelker has joined #openstack-meeting-304:45
*** markvoelker has quit IRC04:50
*** Swami has quit IRC04:50
*** stevemar has quit IRC04:58
*** nkrinner has joined #openstack-meeting-305:03
*** pballand has quit IRC05:07
*** mrmartin has quit IRC05:17
*** yamahata has joined #openstack-meeting-305:20
*** puranamr has quit IRC05:20
*** krtaylor has joined #openstack-meeting-305:27
*** roxanaghe has quit IRC05:44
*** mrunge has joined #openstack-meeting-305:56
*** woodster_ has quit IRC06:00
*** armax has quit IRC06:01
*** puranamr has joined #openstack-meeting-306:02
*** vineetmenon has joined #openstack-meeting-306:06
*** radek_ has joined #openstack-meeting-306:07
*** sahid has joined #openstack-meeting-306:07
*** shakamunyi has joined #openstack-meeting-306:16
*** barra204 has joined #openstack-meeting-306:17
*** yamamoto has joined #openstack-meeting-306:17
*** puranamr has quit IRC06:24
*** belmoreira has joined #openstack-meeting-306:26
*** ddomingo has quit IRC06:27
*** nelsnelson has quit IRC06:30
*** mrmartin has joined #openstack-meeting-306:33
*** markvoelker has joined #openstack-meeting-306:34
*** scheuran has joined #openstack-meeting-306:34
*** Longgeek has joined #openstack-meeting-306:35
*** jtomasek has joined #openstack-meeting-306:37
*** Longge___ has quit IRC06:37
*** markvoelker has quit IRC06:38
*** mrmartin has quit IRC06:43
*** wojdev has joined #openstack-meeting-306:45
*** sahid has quit IRC07:01
*** radek_ has quit IRC07:02
*** egallen has joined #openstack-meeting-307:03
*** radek_ has joined #openstack-meeting-307:05
*** tmorin has joined #openstack-meeting-307:09
*** radek__ has joined #openstack-meeting-307:18
*** radek_ has quit IRC07:20
*** bradjones has quit IRC07:20
*** bradjones has joined #openstack-meeting-307:22
*** egallen has quit IRC07:24
*** egallen has joined #openstack-meeting-307:25
*** matrohon has joined #openstack-meeting-307:27
*** zz_ttrifonov is now known as ttrifonov07:35
*** radek_ has joined #openstack-meeting-307:35
*** radek__ has quit IRC07:37
*** coolsvap is now known as coolsvap|afk07:41
*** belmoreira has quit IRC07:42
*** jcoufal has joined #openstack-meeting-307:45
*** coolsvap|afk is now known as coolsvap07:46
*** belmoreira has joined #openstack-meeting-307:46
*** devvesa has joined #openstack-meeting-307:50
*** tobe has quit IRC07:52
*** dims_ has joined #openstack-meeting-307:58
*** rushiagr_away is now known as rushiagr08:02
*** wojdev has quit IRC08:03
*** dims_ has quit IRC08:03
*** stanzgy has quit IRC08:05
*** stanzgy__ has joined #openstack-meeting-308:05
*** JeanBriceCombebi has joined #openstack-meeting-308:05
*** JeanBriceCombebi has quit IRC08:12
*** tobe has joined #openstack-meeting-308:14
*** wojdev has joined #openstack-meeting-308:15
*** JeanBriceCombebi has joined #openstack-meeting-308:16
*** sahid has joined #openstack-meeting-308:22
*** markvoelker has joined #openstack-meeting-308:22
*** markvoelker has quit IRC08:27
*** egallen has quit IRC08:33
*** egallen has joined #openstack-meeting-308:34
*** JeanBriceCombebi has quit IRC08:35
*** stanzgy__ has quit IRC08:35
*** e0ne has joined #openstack-meeting-308:46
*** JeanBriceCombebi has joined #openstack-meeting-308:51
*** nkrinner has quit IRC08:52
*** nkrinner has joined #openstack-meeting-308:57
*** safchain has joined #openstack-meeting-308:57
*** egallen has quit IRC09:01
*** e0ne is now known as e0ne_09:01
*** e0ne_ is now known as e0ne09:01
*** egallen has joined #openstack-meeting-309:05
*** JeanBriceCombebi has quit IRC09:07
*** JeanBriceCombebi has joined #openstack-meeting-309:08
*** pavel_bondar has quit IRC09:14
*** stanzgy has joined #openstack-meeting-309:14
*** JeanBriceCombebi has quit IRC09:22
*** gcb has joined #openstack-meeting-309:27
*** pavel_bondar has joined #openstack-meeting-309:28
*** lazy_prince has joined #openstack-meeting-309:28
*** yamamoto has quit IRC09:29
*** mrmartin has joined #openstack-meeting-309:30
*** pkarikh has joined #openstack-meeting-309:47
*** tmorin has quit IRC09:49
*** e0ne is now known as e0ne_09:55
*** e0ne_ is now known as e0ne09:57
*** wojdev has quit IRC09:59
*** dims_ has joined #openstack-meeting-310:06
*** markvoelker has joined #openstack-meeting-310:11
*** JeanBriceCombebi has joined #openstack-meeting-310:14
*** markvoelker has quit IRC10:15
*** lazy_prince has quit IRC10:22
*** sahid has quit IRC10:25
*** wojdev has joined #openstack-meeting-310:25
*** mwagner_afk has quit IRC10:26
*** egallen has quit IRC10:31
*** amotoki has quit IRC10:40
*** amotoki has joined #openstack-meeting-310:44
*** amotoki has quit IRC10:48
*** stanzgy has quit IRC10:49
*** julim has joined #openstack-meeting-311:06
*** JeanBriceCombebi has quit IRC11:12
*** egallen has joined #openstack-meeting-311:19
*** rushiagr is now known as rushiagr_away11:25
*** e0ne is now known as e0ne_11:32
*** yamamoto has joined #openstack-meeting-311:32
*** wojdev has quit IRC11:38
*** markvoelker has joined #openstack-meeting-311:42
*** e0ne_ has quit IRC11:42
*** woodster_ has joined #openstack-meeting-311:44
*** markvoelker has quit IRC11:46
*** baoli has joined #openstack-meeting-311:47
*** baoli has quit IRC11:49
*** yamamoto_ has joined #openstack-meeting-311:50
*** sahid has joined #openstack-meeting-311:50
*** baoli has joined #openstack-meeting-311:50
*** yamamoto has quit IRC11:53
*** tobe has quit IRC11:56
*** irenab has quit IRC11:56
*** irenab has joined #openstack-meeting-311:57
*** tobe has joined #openstack-meeting-311:57
*** e0ne has joined #openstack-meeting-311:58
*** markvoelker has joined #openstack-meeting-312:01
*** tobe has quit IRC12:02
*** VW has joined #openstack-meeting-312:08
*** yamamoto_ has quit IRC12:09
*** yamamoto has joined #openstack-meeting-312:13
*** wojdev has joined #openstack-meeting-312:16
*** amotoki has joined #openstack-meeting-312:18
*** lblanchard has joined #openstack-meeting-312:18
*** JeanBriceCombebi has joined #openstack-meeting-312:23
*** yamamoto has quit IRC12:23
*** JeanBriceCombebi has quit IRC12:28
*** JeanBriceCombebi has joined #openstack-meeting-312:28
*** egallen has quit IRC12:33
*** yamamoto has joined #openstack-meeting-312:34
*** baoli has quit IRC12:34
*** JeanBriceCombebi has quit IRC12:42
*** JeanBriceCombebi has joined #openstack-meeting-312:45
*** vineetmenon has quit IRC12:45
*** egallen has joined #openstack-meeting-312:49
*** jcoufal has quit IRC12:52
*** bknudson has joined #openstack-meeting-312:56
*** VW has quit IRC12:59
*** yamamoto has quit IRC13:01
*** mattfarina has joined #openstack-meeting-313:04
*** yamamoto has joined #openstack-meeting-313:05
*** mattgriffin has joined #openstack-meeting-313:05
*** puranamr has joined #openstack-meeting-313:07
*** shwetaap has joined #openstack-meeting-313:11
*** shwetaap1 has joined #openstack-meeting-313:12
*** puranamr has quit IRC13:13
*** puranamr has joined #openstack-meeting-313:14
*** nkrinner has quit IRC13:15
*** shwetaap has quit IRC13:16
*** stevemar has joined #openstack-meeting-313:17
*** peristeri has joined #openstack-meeting-313:23
*** jrist has quit IRC13:26
*** yamamoto has quit IRC13:27
*** mrmartin has quit IRC13:28
*** yamamoto has joined #openstack-meeting-313:29
*** puranamr has quit IRC13:31
*** singlethink has joined #openstack-meeting-313:31
*** jcoufal has joined #openstack-meeting-313:33
*** baoli has joined #openstack-meeting-313:35
*** moshele has joined #openstack-meeting-313:36
*** puranamr has joined #openstack-meeting-313:36
*** jrist has joined #openstack-meeting-313:39
*** puranamr has quit IRC13:40
*** e0ne is now known as e0ne_13:41
*** e0ne_ is now known as e0ne13:41
*** wojdev has quit IRC13:42
*** VW has joined #openstack-meeting-313:42
*** vikram has joined #openstack-meeting-313:50
*** banix_ has joined #openstack-meeting-313:51
*** mwagner_afk has joined #openstack-meeting-313:52
*** cbouch has joined #openstack-meeting-313:53
*** nelsnelson has joined #openstack-meeting-313:53
*** yamamoto has quit IRC13:54
*** sigmavirus24_awa is now known as sigmavirus2413:54
*** Piet has quit IRC13:56
*** singleth_ has joined #openstack-meeting-313:58
*** ihrachyshka has joined #openstack-meeting-313:59
*** coolsvap is now known as coolsvap|afk14:00
ajohi :)14:00
moshelehi14:00
ihrachyshkao/14:00
sc68calo/14:00
vikramhi14:00
ajo:) ping irenab14:00
pcarverhi14:00
ajook, let's start :)14:01
ajo#startmeeting neutron_qos14:01
openstackMeeting started Wed Jun  3 14:01:23 2015 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
*** singlethink has quit IRC14:01
ajo#topic Where are we14:01
*** openstack changes topic to "Where are we (Meeting topic: neutron_qos)"14:01
irenabhi14:01
ajohi :)14:02
ajo#link https://etherpad.openstack.org/p/neutron-qos-jun-3-201514:02
*** sadasu has joined #openstack-meeting-314:02
ajowith the help of irenab , we have put an interactive agenda in etherpad14:02
ajowith some design details14:02
ajoand some points for today :)14:02
*** sicarie_ has joined #openstack-meeting-314:02
ajoplease name yourself in the top right icon of the etherpad before commenting :)14:03
*** sicarie_ has left #openstack-meeting-314:03
*** moshele has quit IRC14:03
sadasuajo: are you referring to this etherpad/ https://etherpad.openstack.org/p/neutron-qos-api-preview14:03
*** sfinucan has joined #openstack-meeting-314:03
ihrachyshkasadasu, https://etherpad.openstack.org/p/neutron-qos-jun-3-201514:03
*** yamamoto has joined #openstack-meeting-314:04
ajothanks ihrachyshka14:04
sadasuihrachyshka: thanks!14:04
ajook14:04
ajoso, we got the API / service plugin spec approved14:04
ajohttps://review.openstack.org/#/c/8859914:04
*** moshele has joined #openstack-meeting-314:04
ajoand we have a follow up addressing some final comments: https://review.openstack.org/#/c/187513/14:04
vikramgreat14:05
vhowardajo, anthony and i will be working on finishing up initial drafts for specs tomorrow around dscp and will link them for everyones review14:05
ajowe also have specs for ML2/OVS: https://review.openstack.org/#/c/182349/  and ML2/SR-IOV  https://review.openstack.org/#/c/187895/14:05
ajovhoward, great,14:05
vikramdo we need to raise RFE for new specs14:05
ajoplease note the new RFE mechanism in place14:05
ihrachyshkabeside specs, is there any code?14:05
ajoRFEs are basically to prevent you from writing a spec for nogthing14:06
ajonothing14:06
ajobut still, I believe the spec is valuable in our context14:06
ajoin some cases (like this) you could not be required even to write a spec14:06
*** yamamoto has quit IRC14:07
ajoand just a simple devref explanation of what do you want to do14:07
ajoihrachyshka: no code yet, we will get to organize that by the end of this meeting14:07
*** lazy_prince has joined #openstack-meeting-314:07
ajoihrachyshka, or was it a question to vhoward ?14:07
ajoI believe they have some code they can reuse14:07
ihrachyshkaajo, no, your response is what I looked for14:07
ajoihrachyshka ack, thanks14:07
ajo.14:07
*** armax has joined #openstack-meeting-314:08
ajoyesterday on neutron's meeting, we raised the openstack/neutron vs openstack/neutron-qos question14:08
ajohi armax ;)14:08
ajomestery suggested a feature branch, and we need to analyze work that out during this week14:08
sc68calihrachyshka: there is code for dscp marking14:08
ajo#link http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-06-02-14.01.log.html#l-29314:08
*** bknudson has left #openstack-meeting-314:09
*** JeanBriceCombebi has quit IRC14:09
sc68calone thing that may complicate the OVS work - the new reference implementation split - https://review.openstack.org/#/c/176501/14:09
*** JeanBriceCombebi has joined #openstack-meeting-314:09
irenabsc68cal: I guess it will impact SR-IOV as well14:10
ajoa feature branch, is basically a branch of /neutron where we do all the work related  to QoS, and when stable, that's finally merged to /neutron, or ... spun out (I'd definitely avoid feature branches if that's the final outcome and jump straight into separate repo)14:10
vikramajo14:10
ajobecause a later spin out may introduce all the CI overhead later in the cycle14:10
vikramajo: is it in stackforge14:10
ajovikram, starckforge first, then under neutron umbrella14:11
ajowhich means openstack/..... as far as I understood14:11
ajoihrachyshka, am I right?14:11
ajovikram, talking about out of tree plugin, right?14:11
vikramajo: yes14:12
ajosc68cal: yes14:12
ajosc68cal, that's true, OVS spin out may complicate things, but, we just need to track that14:12
ihrachyshkaajo, I guess so14:12
ajook, any question or concern about this?14:12
* sc68cal gets out his butterfly net to chase all these pieces of neturon that are flying out of the main tree14:12
ajosc68cal lol14:12
ihrachyshkasc68cal, puzzle with 1000+ pieces, yea14:13
vikramajo: so the patch i submitted for neureon-qos project will be approved?14:13
ajosc68cal, if finally we spin out ref implementation, I have proposed myself to help a bit with it, so we have better track ourselves14:13
ajovikram, no14:14
ajounless there is any change in the end...14:14
ajobut no, so far..14:14
sc68calajo: nice :)14:14
ajo#topic QoS design points14:15
*** openstack changes topic to "QoS design points (Meeting topic: neutron_qos)"14:15
ajoirenab, do you want to talk about this one? :) I can interleave...14:15
irenabajo: sure14:15
irenabso Lets start from server side14:15
irenabwe will have QoS server plugin to manage  QoS policy/rules14:16
irenabwe have QoS policy to port/ent mapping API14:16
sadasuajo: just to summarize from the previous discussion: qos api changes in a seperate feature branch (maybe) and the changes to OVS/SR-IOV refernce ML2 plugins will be in their respective stackforge repos14:16
ajosadasu, correct, as they will be spun out...14:17
*** sahid has quit IRC14:17
irenabback  to design?14:17
ajoyes :)14:17
sadasuyes irenab!14:17
irenabso for qos policy mapping lokks like there are 2 options14:18
irenab1. support in qos service plugin14:18
irenab2. ML2 extension14:18
irenabwith option 1, it looks like more consistent way14:18
irenabwith option 2, more easy way14:19
*** Networkn3rd has joined #openstack-meeting-314:19
sadasuirenab: what do you mean by more consistent way14:19
ajowith 1 we pave the way for other plugins14:19
*** davids has joined #openstack-meeting-314:19
ajoand it's more consistent with the API proposal14:19
irenaball policy UUID resolution into real attribute should be handled by the qos plugin anyway14:19
ajothat means,14:19
mosheleirenab: if we got  with 1 can the service rpc  with L2 agent  or we need to implement new agent?14:20
ajowe may extend the port information just with the qos-profile-id but no more details14:20
ajothen the plugin is responsible of talking with the qos service plugin api to fetch the policy and rule details14:20
irenabajo: right, and the question if we want to do it via Ml2 qos mapping extension driver OR qos plugin14:20
ajoI'd go for 114:21
ajoand then every plugin can do what it needs to do...14:21
irenabfor me 1 lokks more consistent as well, but maybe we need to prototype the workflow to see how to achive it14:22
vikramso we will have separate plugins for OVS/LB/SR-IOV?14:22
ajoirenab: I agree14:22
ajovikram, no,14:22
ajoall those are drivers within ML214:22
irenabwe may need some differentiation in the QoS pplugin, since capabilities may differ14:23
ajoyes,14:23
ajothat's one of the points we need to resolve14:23
irenabmy keyboard in a bad mood today :-)14:23
ajoplugin-wise it's very simple to add a mechanism for "plugins" (ML2, a, b c...) to register their available rules...14:24
ajoand then when those rules are created, we can just deny the ones not supported...14:24
ajobut14:24
ajowith ML2, we have one plugin14:24
ajoand many drivers, that can be running concurrently14:24
*** zz_jgrimm is now known as jgrimm14:25
ajolocal, ovs, lb, sr-iov...14:25
*** david-lyle has quit IRC14:25
ajonot local, sorry14:25
ajoif you see the table in the etherpad14:25
ihrachyshkaajo, maybe ml2 could find common set to report as supported14:25
irenabWhat I am stil questioning is how port-create will deal with port extension supported by service plugin14:25
ajonot all of them have the same capabilities..14:25
ajoihrachyshka, yes, that makes sense, and resolves some part14:25
ajobut still14:26
ajowe may have issues:14:26
ajo1) at port binding, if the port is bound to a sr-iov port (can we know that in advance?)14:26
irenabonce port-create is invoked with —qos-profile=UUID, port creation will be handled by ML2 plugin14:26
ajo2) at policy modification, for example, if your policy is applied to lots of ports (sr-iov, ovs..)14:27
ajobut you introduce a rule which is not compatible with all ports14:27
irenabajo: I think your quesion is much more advanced then mine14:28
ajoonce ports are bound... may be during port update, ML2 could refuse to accept the new policy...14:28
ihrachyshkaajo, you know which drivers are enabled, so the list of rules supported by all of them is predetermined. You can just check whether the new rule is among those.14:28
ajoIok,14:29
ajomay be we're trying to dig too much in advance14:29
irenabis it possible in current neutron code to support port extensions in different plugins and not in L2 plugin only?14:29
ajoand it's something we could resolve during develpment14:29
ajoirenab, what do you mean?14:29
*** VW has quit IRC14:30
irenabif we support qos-mapping port extension in qos service plugin, I am not sure if current API framework will handle it gracefully.14:30
irenabport is managed by L2 plugin (ML2)14:31
pcarverIn order to support SR-IOV we would need that support in hardware, right? There's no OvS/LinuxBridge way of applying QoS to an SR-IOV VM VF14:31
ajopcarver, correct14:31
ajoirenab, I don't see the issue, but, I guess we can solve this by jumping into a code POC14:32
pcarverSo the ML2 plugin's vendor specific hardware driver is involved14:32
irenabso for now any port extension if supported by this plugin, and then there are mixins to take care of validations and persistency14:32
ajoirenab, plugins may need to signup for the "qos extension" yet14:32
ajoeven if we don't have a mixin14:32
ajoand we do that via callback14:32
ajothat=extension14:33
ihrachyshkairenab, doesn't self.mechanism_manager.create_port_postcommit in ml2 pass all the needed info to driver?14:33
irenabajo: so from the ‘supported_extension’ perspective, qos-mapping will go into ML2?14:33
ajoirenab, we need to provide a generic mechanism for plugins, and then in ML2 we could do it as we wanted14:34
*** praveens1 has joined #openstack-meeting-314:34
ajomay be I'm missing something, can we POC and resolve this into code to see how things fit?14:34
irenabthe point I wanted to raise, that it seems that currently all ‘net’, ‘port’ extensions are supposed to be declared as supported by L2 plugin. We just need to see how to make it work.14:35
irenabwith qos service plugin14:35
ajoyes14:35
irenabwith other L2 plugins, it is the same14:35
ihrachyshkairenab, but qos will be still supported by ml2, it's just that specific rules available may depend on drivers. (or I completely misunderstand the concern)14:36
*** qwebirc74593 has joined #openstack-meeting-314:36
*** barra204 has quit IRC14:36
*** shakamunyi has quit IRC14:36
ajowe need to resolve the specific rules per driver... either we fail/warning on port bind when we discover where/to which driver the port is bound14:36
mosheleajo: also on port update14:37
ajoor... we fail on QoS rules update if there is a port not supporting such rule (we may need to find a reasonable way to do such thing without specific ML2 knowledge)14:37
ajomoshele: correct14:37
ajoif we had more port states, some kind of warning could be sent back to neutron server about the ports with unsupported rules14:38
irenabihrachyshka: it should work for ML2 with ref implementation, but be possible to leverage by other L2 plugins14:38
ajoI remember somebody was looking into that already14:38
ajoirenab: it should work for all plugins,14:39
ajoML2 included14:39
irenabajo: right14:39
*** VW has joined #openstack-meeting-314:39
ihrachyshkairenab, sure. I don't see why it won't work.14:40
irenabbut looks like with ML2 there are additional concerns, due to mixed drivers capabilities14:40
ihrachyshkayes, if we solve ml2, other plugins are even easier14:40
ajocorrect14:40
ajoas we're resolving ML2 first, the mechanism should be there for all in the end14:40
irenabso for the next design concern14:40
ajoAgent side?14:41
irenabthere are two tipes of plugins/mech drivers: agent and agent-less14:41
irenab^types14:41
irenabso we should take care of both14:41
ajoexamples of agent-less ML2 drivers?14:42
irenabagent-based will require QoS “extension driver” to deal with qos settings and reporting14:42
mosheleODL14:42
irenabajo: cisco sr-iov?14:43
ajothanks :)14:43
vikramopencontrail14:43
irenabovn14:43
irenablooks like there are more agent-less than agent-based :-)14:44
ajoyep :)14:44
ajoso, the idea of the extension driver, is that you can extend the agents in a modular way14:44
*** VW has quit IRC14:44
ajoreusing all the RPC communication, etc.14:44
irenabajo: correct14:44
*** fallenpegasus has joined #openstack-meeting-314:44
*** carl_baldwin has joined #openstack-meeting-314:44
ajoirenab: I added some notes to the etherpad, but may be is too long for this meeting14:45
ihrachyshkafor agent-less, we don't do anything specifically, right?14:45
ajoI had an idea on how to have a generic RPC mechanism for all extension drivers14:45
irenabI think both OVS and SR-IOV specs are mentioning some qos driver api that they will implement14:45
ajoand even (later in time) make security groups an extension driver too14:45
*** yamamoto has joined #openstack-meeting-314:45
*** vineetmenon has joined #openstack-meeting-314:45
vhoward+114:45
irenabthere will be a common layer above to make the information available14:45
irenabajo: can you share your idea?14:46
*** yamamoto has quit IRC14:46
ajoirenab: yes, line 61 of etherpad14:46
ajobasically14:46
ajowe could use query + subscription to fanout queues to retrieve and register for "SG RULES" "sg-id" info14:46
ajoor "QOS PROFILE" "qos-profile-id" info14:47
ajothen the extension mechanism would receive the messages, and route them to the right extension14:47
ajowhich subscribed14:47
ajoalso14:47
ajoon the rpc side, the service plugins, or extensions, could register to this common rpc mechanism, saying14:47
ajo"I  provide info for SG RULES", "I provide info for QOS profiles" , ....14:48
irenabajo: PUB/SUB14:48
ajoso when somebody subscribes, it's notified, when somebody de-suscribes, it's notified... and it sends the information as changes hapen14:48
ajohappen14:48
ajoyes14:48
*** killer_prince has joined #openstack-meeting-314:48
ajoso, we would have common bits at ML2 level for the RPC messages14:49
*** qwebirc74593 has quit IRC14:49
*** lazy_prince has quit IRC14:49
ajobut then, the service plugin would subscribe to that API saying: "I provide QOS PROFILE info"14:49
ajoeven, if we use oslo versioned objects at some point, those could be seralized over the messages...14:50
ajofrom rpc server to agents...14:50
ajodoes it sound too crazy? or even slightly reasonable? :)14:50
*** gsagie has joined #openstack-meeting-314:50
*** tholtzen has joined #openstack-meeting-314:50
gsagiesorry for being late14:50
gsagielong meeting :(14:50
ajohi gsagie  :) np, we have minutes :D14:50
irenablooks like nice infrastructure, need to reread though …14:51
vikramit's basically a consumer / provider model ...right?14:52
ajoI think it melds well with the idea of providing rpc responses from the service plugin, the extension manager, and having a common mechanism to communicate extensions info..14:52
pcarverajo: I like it. But I don't think I've fully absorbed it yet. Definitely seems like a good path.14:52
ajovikram , yes, with rpc in the middle and fanouts to optimize RPC traffic..14:52
ajopcarver, yes, I need to write a devref with more detail14:52
vikramok14:52
*** nikhil_k is now known as nikhil_k-brb14:52
ajook,14:53
*** VW has joined #openstack-meeting-314:53
ajolet's talk about the last point, and lets mature the idea to see if it really makes sense14:53
*** JeanBriceCombebi has quit IRC14:53
ajo#topic organizing work14:53
*** openstack changes topic to "organizing work (Meeting topic: neutron_qos)"14:53
*** JeanBriceCombebi has joined #openstack-meeting-314:53
ajoif you go to line 94: https://etherpad.openstack.org/p/neutron-qos-jun-3-201514:53
*** lazy_prince has joined #openstack-meeting-314:53
*** killer_prince has quit IRC14:53
sadasuajo: agree with the model the way you have explained it, but not sure if we are missing anything here..your devref would help14:53
ajosadasu, probably we're missing some detail, unexpected complexities everywhere :)14:54
ajo#action ajo to put the common RPC mechanism to a devref14:54
sadasuajo: +114:54
ajocan you put your names next to the work points where you feel you could collaborate?14:55
ajoin the etherpad14:55
ajoprobably the first step is the DB models14:55
ajoI haven't draw a dependency tree...14:56
ajobut time for liberty is tight14:56
vikramthat would be nice14:56
vikram;)14:56
ajoby the end of august, liberty-3 is closed, and feature freeze comes ;)14:56
ajowinter is coming...14:56
ajo;)14:56
irenabajo: will add later, my browser is stuck….14:57
irenabneed bulet for extension too14:57
irenabits different from DB model14:57
ajook, just signup or add any work piece I could have missed14:57
vikramhow about horizon?14:57
vikramwe need to do now?14:58
gsagiei think thats a low priority14:58
ajohorizon, right14:58
ajoit's low, but it's important14:58
vikramyes.. but need to deliver right?14:58
ajolet's add the bullet14:58
*** mrmartin has joined #openstack-meeting-314:59
ajocorrect, but some tracking with horizon when we manage to get the API in place will be good14:59
ajomy browser is getting a bit crazy :D14:59
ajook, we're at the top of the hour... :)14:59
vikramok14:59
ajoif you want to talk a few minutes more about work distribution I'll be happy #openstack-neutron15:00
irenabajo: cli?15:00
ajoirenab: that's the command line client point :)15:00
*** pballand has joined #openstack-meeting-315:00
ajo#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
irenaboh, sorry missed it15:00
openstackMeeting ended Wed Jun  3 15:00:34 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
ajothanks everybody for your incredible patience! ;D15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-06-03-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-06-03-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-06-03-14.01.log.html15:00
vikrambye15:00
moshelebye15:01
ajoah, I forgot , we can start working as WIP patches to master15:01
ajoprobably I said it ;)15:01
ajothen we can move it to the right branch/project/whatever :)15:01
ajoto "the right place(tm)"15:01
irenabajo: need to have the dependency between patches15:02
ajoirenab, yes15:02
ajowe will need to organize that15:02
ajoservice plugin <- DB <- API extension15:02
ajoI guess that's the first thing15:03
*** tholtzen has left #openstack-meeting-315:03
-amotoki- missed QoS meeting time.... this is one of meetings I (he) can join before going to bed :-)15:03
irenabI suspect some impact maybe in ML2 plugin, need to verify15:04
*** moshele has left #openstack-meeting-315:05
*** sfinucan has left #openstack-meeting-315:07
*** davids has quit IRC15:09
*** jgrimm is now known as zz_jgrimm15:10
*** asahlin_afk is now known as asahlina15:10
*** asahlina is now known as asahlin15:10
*** zz_natorious is now known as natorious15:11
ajoameade ooo ;)15:12
ajoamotoki15:12
ajosorry ameade  ;)15:12
ameadehaha15:12
ajoamotoki, we had some interesting ideas about a generic rpc path for details about ports & nets agents can consume15:13
ajolike qos-rules, or sg-rules + sg-members (if we refactor sg in such idea later in time)15:13
ajothis way we may not need to rewrite new messages for every new feature consuming port info15:13
ajoand... of course, apply the same optimizations to all :)15:14
*** natorious is now known as zz_natorious15:16
*** marun has joined #openstack-meeting-315:16
*** killer_prince has joined #openstack-meeting-315:17
*** mestery_ has joined #openstack-meeting-315:17
*** Aish has joined #openstack-meeting-315:18
*** mestery has quit IRC15:20
*** lazy_prince has quit IRC15:20
*** alexpilotti has quit IRC15:24
*** jcoufal has quit IRC15:27
*** singlethink has joined #openstack-meeting-315:28
*** tholtzen has joined #openstack-meeting-315:30
mestery_armax dougwig amotoki marun: neutron-drivers meeting (30 minutes today)15:30
armaxmestery_: ping15:30
dougwigo/15:30
*** mestery_ is now known as mestery15:30
amotokio/15:30
marun\o15:30
mestery#startmeeting neutron-drivers15:30
openstackMeeting started Wed Jun  3 15:30:47 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.15:30
maruno/15:30
armax\o/15:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:30
*** openstack changes topic to " (Meeting topic: neutron-drivers)"15:30
openstackThe meeting name has been set to 'neutron_drivers'15:30
mestery#topic Agenda15:30
*** openstack changes topic to "Agenda (Meeting topic: neutron-drivers)"15:30
* ihrachyshka lurks15:31
mesteryDisolve the drivers team and instead directly use lietenants15:31
mestery:)15:31
mesterythoughts?15:31
*** singleth_ has quit IRC15:31
marun+115:31
mesteryI mean, not dissolve, but refocus15:31
armaxwell, I think the drivers team should be made up by15:31
mesterySince we have Lts. now, they need to be involved in evaluating RFEs15:31
armaxlietenants15:31
mesteryarmax: ++15:31
mesterydougwig amotoki ihrachyshka: Thoughts?15:31
marunyeah, I was going to say. Still helpful to have a high-level group of ptl delegates15:32
mesterymarun: Exactly15:32
armaxthis in turn means that marun and I give our seats to the other folks15:32
dougwigseems reasonable, except for when the current LT silos don't cover something.15:32
mesteryarmax marun: You both will forever be in my heart ;)15:32
armaxand include the rest of the folks15:32
*** e0ne is now known as e0ne_15:32
marundougwig: the ptl is responsible for everything not delegated15:32
armaxmestery: I would personally still do the reviews etfc15:32
mestery++15:32
mesteryright15:32
mesteryI hope people keep reviewing!15:32
mesteryThey should!15:32
mesteryCode, RFEs, etc.15:32
armaxbut yesterday it occurred to me that I have not the right visibility into some of the lietenant areas for juding an approval15:33
mesteryI mean, even now, I am defering to Lts. for some of these specs/RFEs15:33
mesteryarmax: Exactly15:33
amotokithe driver team focus on the project management and mainly focuses on spec approvals.15:33
armaxamotoki: agreed15:33
marunare drivers still the only ones to merge specs then?15:33
armaxso it makes sense to let lietenants have that right15:33
mesterymarun: Yes, and that would be made up of Lts.15:33
marunI thought the lts should have that right15:33
marunah, ok15:33
armaxmarun:  by the looks of it, yes15:33
mesterymarun: But, I expect after Liberty-1 we will have a negligble amount of specs15:34
marunso lts are elevated to drivers essentially15:34
marunmakes sense15:34
amotokiwe can collaborate with lientenants and we can share our views.15:34
*** killer_prince has quit IRC15:34
mesterymarun: yes, exactly!15:34
ihrachyshkaso drivers are now lieutenants + existing drivers?15:34
mesteryamotoki: Keep in mind, you and dougwig are Lts., so there is no change for either of you15:34
mesteryihrachyshka: No, marun and armax would be out since they are not Lts.15:34
*** killer_prince has joined #openstack-meeting-315:34
amotokimestery: i know, but only dougwig and me are intersections ;-)15:35
mestery:)15:35
*** killer_prince has quit IRC15:35
mesteryamotoki: So, you are advocating for keeping a separate drivers team to do project management, etc,? That's a fair point.15:35
ihrachyshkahow come armax is not in drivers team??? :)15:35
dougwigi think it was a natural consequence, though it seems to me to be too quickly, but i don't have any objection.15:35
armaxihrachyshka: because I am not a lt15:35
*** e0ne_ is now known as e0ne15:35
mesteryihrachyshka: Personal choice :)15:35
*** zz_natorious is now known as natorious15:36
armaxrest assured that my level of involvement is not going to change15:36
armaxat least for the reasonable time being :)15:36
amotokiI don't think we should have more separate teams.15:36
marunSo long as the ptl can maintain relationships with all the lts this should be fine15:36
marunif the number grows unmanageble, middle management may be required15:36
mestery:(15:37
mesteryReasonably, 7 is about the max15:37
armaxamotoki: what separate teams are your thinking of?15:37
*** Networkn3rd has quit IRC15:37
marunlinux manages quite a deep hierarchy15:37
mesteryAlthough, I am going to start "IRC office hours" for "PTL to Lt. communication" each week15:37
marunso it is possible15:37
armaxI think mestery needed to intereact on a regular basis with lietenants15:37
dougwigan LT per tent repo is probably unmanageable already.  :)15:37
armaxthat can happen in the context of this meeting15:37
mesterydougwig: True dat.15:37
mesteryActually15:37
mesteryNow that we're discussing this15:37
mesteryI am starting to understand amotoki's points15:38
* dougwig left his tea brewing for half an hour. danger.15:38
mesterythe fact each repo in the neutron stadium has a Lt. now makes the team large already15:38
marunI'm not sure everything in the tent needs direct ptl oversight though15:38
armaxmestery: care to elaborate?15:38
armaxmarun: right15:38
mesterymarun: IT does! By coming in, they are agreeing to it, but how much time will it take? Debatable. We won't know until Liberty is done to be honest.15:38
marunI mean, the argument for ovn's inclusion was that it wouldn't add work to ptl15:38
mesteryExperimentation is #ftw15:38
marunIf that's not true, we're in trouble15:38
mesteryFor OVN, I'm already intimiately involved there, so it wasn't a problem15:39
*** david-lyle has joined #openstack-meeting-315:39
marunSo they get special treatment :/15:39
*** Sukhdev has joined #openstack-meeting-315:39
mesteryI wouldn't say special treatment15:39
armaxmestery: I think this boils down to stuff that must go in neutron proper15:39
dougwigmarun: they are meant to be mostly standalone, but the ptl is there if needed.15:39
marunHonestly, if we don't prioritize effort we'll be overworked indefinitely15:39
armaxor the interface with external parties15:39
mesteryright15:39
marunNot everything in the tent is equally deserving15:39
mesterymarun: I agree!15:39
armaxfor that we can keep an ad-hoc approach15:39
mestery++ marun15:39
*** zz_jgrimm is now known as jgrimm15:40
amotokimarun: ++15:40
dougwigthere's in the tent, and then there's in the same sleeping bag.15:40
* marun thinks dougwig missed his calling as a comedian15:40
mesteryOK15:40
marunSo wrt lts getting direct oversight from ptl...15:41
mesterySo, this is all good feedback15:41
marunShouldn't that be on a prioritized basis on how important the area of responsibility is perceived to be to the project?15:41
mesterymarun: It is, yes!15:41
armaxso, to recap: drivers team == made up of neutron lt’s15:41
mesteryarmax: I don't think everyone agreed to that yet :)15:41
*** bpokorny has joined #openstack-meeting-315:42
mesteryamotoki still had concerns about dissolving the existing drivers team in favor of Lts. being the new drivers team15:42
armaxthe tent projects lt’s as being defined by russellb patch https://review.openstack.org/#/c/187733/ will have ad hoc interaction with the neutron ptl?15:42
mesteryAlso, do we allow LTs. from stadium projects into drivers? I would say no.15:42
marunmestery: I think so long as you're comfortable directly interacting with the lts, it's fine.15:42
mesteryarmax: Yes15:42
armaxmestery: what cocnern?15:42
mesteryarmax: Correct15:42
marunmestery: If/when it becomes too much work, then we can revsiit15:42
mesterymarun: Right, agreed.15:42
dougwigi would suggest that the drivers team be "drivers + LTs", to give yourself some wiggle room for broader delegation.15:42
armaxmestery: ok, so does my summary make sense?15:43
mesterymarun: Thus, my idea of weekly IRC office hours for Lt. interaction15:43
armaxdougwig: no, I would oppose to the idea15:43
mesterymarun: This is how ttx has moved the general realease work to as well15:43
mesteryThere are no longer 1:1s between ttx and the PTLs, just office hours15:43
marundougwig: nothing stopping lts from being anybody responsible for anything15:43
dougwigarmax: i mean, you can still stop being a driver.  :)15:43
mesterydougwig: That works too15:43
armaxdougwig: but at that point if we enlarge the team so why why do we have the drivers team at all?15:43
marunmestery: cool15:43
mesteryOK, let me write something up and share it with everyone on this.15:44
mesteryDoes that sound fair?15:44
armaxdougwig: it’s either a small drivers team or no drivers teamm at all15:44
* mestery gest out his DMV clipboard15:44
marunI think this represents an expansion of driver responsibility along with increasing the membership.15:44
dougwigso maybe he can delegate all the decomposed plugins to one person.  or maybe add nobody to that half of the group.  it's his organizational call.15:44
armaxmestery: I got number 443434315:44
mesterylol15:44
marunand we're renaming it too15:44
marunit is confusing, I'll admit15:44
armaxwhat are we renaming?15:44
marunI wish we had been able to use the term 'maintainers', frankly.15:44
mesteryneutron-intent-based-lieutenant-policy-chaining? ;)15:44
amotokithough i canot follow all discussions... lts are regarded as some kind of specialists of specific areas. on the other hand drivers team review specs and priorities. the role is a bit different but the goal is similar.15:45
dougwigyou forgot flavors15:45
marundrivers -> lts15:45
mesterymarun: ++ to maintainers15:45
mesterydougwig: Nuts!15:45
marunor at least member of drivers team -> lts15:45
mestery#action mestery to sort out neutron-drivers vs. Lts. and the path forward15:45
marunor maybe amotoki's idea is drivers is lts + non-lt drivers?15:45
mesteryI gave myself a work item15:45
armaxnot sure where the disconnect is: I think that what it’s being advocated here is that members of the drivers team are selected from the LT’s pool15:46
mesteryAre people ok with me coming up with a solution here and driving consensus?15:46
amotokiI trust all drivers and lts and I have no worry about merging both.15:46
marunI don't know if the distinction of driver with area of code responsibility vs driver with area of non-code responsibility is justified.15:46
armaxas they are the ones who need to care for their area of specialization, they have intimate knowledge of what needs to get done, fixed etc15:46
*** yamamoto has joined #openstack-meeting-315:46
marunmestery: yes15:46
mesteryOK15:46
dougwigthere is an interesting dynamic to this conversation, wherein armax and marun are opposed to the drivers continuing in their current form. if you're that adamant, why are you still in the group? aren't you really saying that you want out?15:46
*** lblanchard has quit IRC15:46
mesteryWe have 13 minutes left, shall we move on?15:46
marundougwig: It doesn't make sense for me to be in the group regardless.15:47
*** david-lyle has quit IRC15:47
* mestery waits for responses to dougwig's point15:47
armaxdougwig: you’re reading it wrong, but at this point yes,15:47
armaxI want out15:47
marundougwig: I have no vested interest in any given outcome, just that it should make sense to everyone involved.15:47
armaxbecause it makes no sense for me to +A a spec whose ultimate impact should be determined by the LT15:47
armaxthat’s all I am saying15:48
dougwigso you don't see your broader knowledge of neutron than most as having additional value in spec review?  (and it's broader, and with longer history, than mine.)15:48
armaxthe drivers team main feat was the +A right15:48
armaxthat’s all15:48
*** alexpilotti has joined #openstack-meeting-315:48
mesteryarmax: Also, consistency15:48
armaxdougwig: I am not saying that I am stopping reviewing15:48
dougwigarmax: fair point.15:48
amotokimy understanding for the driver team is not to rush to approve specs. I think it is important point.15:49
armaxonly that the last say into whether something needs to be +A or not does not lie with me15:49
mesteryone of hte original goals of the small drivers team was consistency from release to release15:49
armaxdougwig: ^15:49
mesteryIf we make hte team too big, we lose that15:49
mesteryamotoki: ++15:49
mesteryLots more to discuss here I think, but this is all good! Thanks for all the feedback everyone!15:49
marunI think this bears further thought, in any case.15:49
dougwigmestery: yes, that's the thing that might get lost, although i see that as moving back onto the PTL's shoulders if this stays as simply "LTs".15:49
armaxamotoki: agreed, but the lt’ team is only 7 folks now, and we’d need a bit of extra help15:49
armaxespecially if the core team grows, then the ratio is not too bad15:50
amotokiarmax: agreed.15:50
mesteryI'll write something up to share with folks by Monday.15:50
*** nikhil_k-brb is now known as nikhil_k15:50
*** sbalukoff has joined #openstack-meeting-315:50
mesteryIn either case, we'll iterate on gerrit and see what we come up with.15:50
mesteryIdeally, we keep this meeting to 9 more minutes :)15:50
mesteryShall we look at at least a few RFEs now?15:51
armaxsounds good15:51
mestery#topic RFE review15:51
*** openstack changes topic to "RFE review (Meeting topic: neutron-drivers)"15:51
mestery#link https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe15:51
mestery#link https://bugs.launchpad.net/neutron/+bug/146017715:51
openstackLaunchpad bug 1460177 in neutron "Support metadata service with IPv6-only tenant network" [Undecided,Confirmed]15:51
mesteryLets start with this one15:51
mesteryBecause I think it's an example of a good RFE overall15:51
*** yamamoto has quit IRC15:52
mestery"metadata only works with IPv4, and we'd like it to work for tenants with IPv6 only networks."15:52
mesteryThoughts by folks?15:52
russellb+1 sane15:52
amotokiit sounds reasonable for pure IPv6 world.15:53
*** david-lyle has joined #openstack-meeting-315:53
*** devvesa has quit IRC15:53
*** vineetmenon has quit IRC15:53
mesteryOK, lets move it to triaged, which means that work can proceed on it. armax dougwig marun, good with this?15:53
*** vineetmenon has joined #openstack-meeting-315:53
marunyes15:53
armaxI am wondering how cloud-init works with IPv615:54
*** egallen has quit IRC15:54
dougwigaren't all ipv4 addresses also ipv6?15:54
russellbsays cloud-init can be configured with other URLs15:54
mesteryyes15:54
dougwigi thought it was a simple no prefix scenario.15:54
dougwigso i'm confused why that ipv4 won't work, but that's ok.15:55
*** egallen has joined #openstack-meeting-315:55
dougwigi'm too far into the weeds.15:55
*** JeanBriceCombebi has quit IRC15:55
armaxrussellb: if that’s the case, then it should be fine15:55
amotokii understand we need to identify prbolems to support preu ipv6 world, but it is worth triaged.15:55
armaxI wonder if a more elegant approach would be adopting config-drive15:55
russellbthere's no adopting needed, that already works15:55
russellbbut metadata service is pretty well known and established, seems fine to make sure it works via ipv6, as well15:56
mesteryrussellb: ++15:56
armaxrussellb: +15:56
mesteryThis one is good15:56
mesteryHow about this one: https://bugs.launchpad.net/neutron/+bug/146100015:56
openstackLaunchpad bug 1461000 in neutron "[rfe] openvswitch based firewall driver" [Undecided,Triaged] - Assigned to Jakub Libosvar (libosvar)15:56
mesteryThis was an example of a not so good RFE (we're learning, I'm not picking on the submitters)15:57
mesteryBut kuba's response is good15:57
mesterykuba's update is solid15:57
mesteryI moved this to triaged I realized before consulting in this meeting, but it's fairly obvious we want this, does anyone disagree?15:57
*** singlethink has quit IRC15:58
russellbseems obviously good to me :)15:58
marunno disagreement15:58
amotokisounds good to me.15:59
mesteryadded a note to the bug15:59
mesteryLets do one more15:59
mesteryhttps://bugs.launchpad.net/neutron/+bug/146022215:59
openstackLaunchpad bug 1460222 in neutron "Add 'labels', a list of opaque strings, to the neutron 'port' object" [Undecided,Triaged]15:59
mesteryarmax: You moved this to triaged I think?15:59
*** Aish has quit IRC16:00
*** shwetaap1 has quit IRC16:00
armaxmestery: yes16:00
mesteryI'm fine with that, just letting other folks know.16:00
*** shwetaap has joined #openstack-meeting-316:00
mesteryarmax: Any idea who this should be assigned to?16:00
russellbi think nova has a thing very similar, but they call it tags16:00
* mestery notes it shouldn't be armax16:00
russellbwould be nice to be consistent16:00
russellbbut i'm fine with the concept16:00
mesteryrussellb: Comment in the bug? :)16:00
amotokimy question is whether we should allow 'labels' for all other resources.16:00
armaxacknoledging that we starteed the discussion16:00
mesteryConsistency is good16:00
dougwigspeaking as a vendor who has wanted to stash some meta-data in the past, it was always pushed back against as "locking in".16:01
armaxI am wondering if we can achieve the use case proposed with what we got already16:01
armaxlike binding:profile16:01
*** matrohon has quit IRC16:01
mesterydougwig: In effect, that is partially the goal from the proposer here as well to be honest16:01
dougwigthat's basically adding a key=value meta store to each object.  which i agree with, but which has already been rejected before.16:01
russellbugh, it's actually proposed as info interpreted by the backend16:01
mesterydougwig: But the general concept seems ok16:01
russellbmore backend specific pass-through is harmful IMO16:01
mesteryrussellb: Right16:01
mesteryThat was my concern as well16:01
russellbi assumed it'd be just used for clients to do filtering16:01
russellbthe more vendor specific stuff added, the less valuable neutron is as an abstraction16:02
dougwigyes, this is purely an aid for vendor specifics. we should be upfront about that.16:02
mesteryrussellb: Agreed, and the harder it becomes for people to switch backends, etc.16:02
armaxrussellb: binding:profile is effectively already doing that16:02
mesteryCan you folks comment in the bug with this info too? russellb dougwig16:02
mestery:)16:02
* russellb will comment on the bug16:02
russellbarmax: right, and i think that's bad too :)16:02
marunopaque bags of data for everyone!16:02
armaxso, we sort have that ship already sailed16:02
dougwigflavors also does this, but puts the configuration control in the hands of operators.16:02
mesterymarun: lol16:03
russellbarmax: doesn't have to get worse16:03
mesteryLets be honest, this is an attempt to end-run neutron, bottom line.16:03
armaxrussellb: however that can be used for a number of other use cases, I was talking to Sukhdev  and he mentioned that he uses it for bare metal provisioning16:03
*** rushiagr_away is now known as rushiagr16:03
mesteryarmax: Not everyone will use their special powers for good :)16:03
*** eghobo has joined #openstack-meeting-316:03
dougwigif it didn't have use cases, we wouldn't have flavors being worked on.16:03
mesterydougwig: ++16:03
*** qwebirc38254 has joined #openstack-meeting-316:04
*** egallen has quit IRC16:04
armaxthere was also another proposal made in the past about tagging core resoruces16:04
mesteryyes, the yahoo one from manesh right?16:05
armaxdespite what some people think16:05
armaxmestery: yes16:05
*** egallen has joined #openstack-meeting-316:05
armaxI think that pushing back is not really a viable long-term solution16:05
marunThere are too many valid use cases to ignore16:05
marunSo long as core neutron doesn't rely on these fields,  I think it's fine.16:06
mesterymarun: to quote you, "opaque bags of data for everyone!"16:06
amotokibut we need a common way to interact with other projects. vendor specific way is not diresable.16:06
dougwigi think all of those uses cases are covered by flavors, if we can ship it.16:06
HenryGlol16:06
*** sadasu has quit IRC16:06
marunmestery: but if neutron isn't using them, I don't think it matteres16:06
mesterydougwig: We have to ship it in Liberty16:06
armaxmarun: ++16:06
russellbi think it does matter in terms of interop16:07
marunmestery: I'm more concerned with neutron itself relying on opaque data bags.16:07
*** jgrimm is now known as zz_jgrimm16:07
armaxamotoki: we give the tool, if the tool is misused is not our fault16:07
mesteryLets be honest here, there are valid use cases for this, yes. Will people use this for nefarious purposes? Absolutely! Should we care? If it harms the concept of neutron and waters it down, yes.16:07
russellbit means code written against one openstack does not work against another16:07
russellbit makes interop worse16:07
mesterymarun: We can't rely on opaque data blogs agreed16:07
marunrussellb: that's a given16:07
marunrussellb: and a reality today16:07
*** belmoreira has quit IRC16:07
armaxrussellb: that’s an academic point to be honest16:07
marunrussellb: It does beg the question of how we can deal with that reality constructively.16:07
armaxrussellb: no two openstack clouds are alike and interoperable, period.16:07
*** praveens1 has quit IRC16:07
marunrussellb: without stalling useful efforts or requiring a bunch of rework to existing stuff16:08
russellbtake each use case and define a proper abstraction that serves it16:08
mesteryrussellb: ++16:08
russellbinstead of just adding pass through data bags16:08
*** praveens has joined #openstack-meeting-316:08
marunrussellb: easier said than done in a landscape of conflicting vendor requirements16:08
russellbi do not disagree :)16:08
marun:)16:08
dougwigto level-set, flavors, as approved today, is nothing but a big table of opaque data bags associated with neutron objects, which must be enabled by operators and then can be seen by plugins/drivers. we have already approved this concept, in a way that doesn't promote lock-in, and doesn't touch the core data models.16:08
*** zz_jgrimm is now known as jgrimm16:09
mesterydougwig: ++16:09
marunI think interop is a pipe dream where specialized behavior is being provided by specialized solutions16:09
armaxdougwig: so do you think that’s another viable appraoch to solving this use case?16:09
marunat least above lowest-common-denominator capabilities16:09
armaxif so, we should capture that on the rfe bug16:09
marunGiven that, maybe we should find ways to make this clear to operators?16:09
amotokiwe allow some way for vendors, but it is better most things are common. it is one of our (neutron) important roles.16:10
dougwigarmax: yes, you could create ODL flavored ports.16:10
marunSo they can make decisions based on the long term cost/benefit of the loss of interop vs capabilities?16:10
mesteryODL flavored ports, now with less testing! :)16:10
armaxdougwig: I would love pointers16:10
dougwigarmax: well, an operator could choose to define ODL flavored ports, which would then be accessible, to be clearer.16:10
armaxso that the bug author can explore with it too16:10
dougwigi'll comment on the bug.16:10
armaxdougwig: thanks, much appreciated16:11
mesteryyes, lets comment on the bug and drive discussion there for ODL flavored ports16:11
mesterydougwig: That is too rich not to keep using :)16:11
dougwigthat sounds kinda dirty, and i almost regret hitting enter.  :)16:11
*** alexsyip has joined #openstack-meeting-316:12
dougwigand we killed all conversation.16:12
mesteryOK16:12
mesterySince we are still here16:13
mesteryAnd have 17 minutes or so left16:13
* russellb got distracted sorry :)16:13
mesteryshall we keep going?16:13
armaxI think we should be vigilant on how certain tools provided by teh systems are used to make sure that people do not shoot themselves in the foot16:13
kevinbentonso what purpose does neutron serve if we give up caring about interop...16:13
mesterykevinbenton: The point is we are not giving up on interop16:13
mesterykevinbenton: This bug will make interop worse, thus the discussion16:13
mestery:)16:13
russellbi think debating these features is very healthy fwiw16:13
mesteryrussellb: ++16:13
russellbgets at the heart of what neutron should be, and where lines are drawn16:13
russellbreally good stuff16:13
mesterycool16:14
amotokirussellb: +16:14
armaxI think we’re mixing the what we provide with how it’s being used16:14
mesteryI am firmly in the camp of "neutron is an abstraction and should be a DB/API layer"16:14
mesteryJust to be clear16:14
*** vikram has left #openstack-meeting-316:14
armaxwhen gunpowder was invented it clearly had various applications16:14
armaxwe can make pretty fireworks16:15
mesterylol16:15
armaxor kill people16:15
kevinbentoni suppose that was directed at marun16:15
*** egallen has quit IRC16:15
marunkevinbenton: The reality is that interop has only ever been lcd16:15
kevinbentonmarun: what do you think the job of neutron is if interoperability is a pipe dream?16:15
kevinbentonmarun: lcd?16:15
marunkevinbenton: and hopefully we bump lcd over time to encompass more features as they mature and become more widely distributed16:15
marunlowest common denominator16:16
russellbi read lcd as lsd ......16:16
mesterylol16:16
dougwigi don't think it's a pipe dream, and default neutron is interoperable.  but if an operator *chooses* to modify neutron to be non-interoperable, for their needs, why should we try to prevent that?16:16
mesterymarun: nothign wrong with that16:16
russellbi was so confused ... and intrigued16:16
armaxrussellb: LOOL16:16
kevinbentonwell stuff like port tags could easily lead to everyone developing a similar feature with a different data format16:16
marunWhen we see opaque bags of data becoming the norm16:16
marunand I'm looking at you, ml216:17
marunIt's pretty clear that interop is starting to fall by the wayside16:17
dougwigkevinbenton: i think port tags just got shot down.16:17
mestery++16:17
* russellb throws a data bag at dougwig 16:17
mestery"shot down! In a blaze of glory!"16:17
marunWhen we have a client that can only configure the backend with arbitrary key value pairs16:17
marunwe're not doing a good job of interop either16:17
marunI'm not saying we're doomed, but we have been falling behind.16:18
*** dims_ has quit IRC16:18
mesterymarun: Right, thus the need to take the reigns back a bit16:18
* marun digresses16:18
mesteryAnd focus on the platform16:18
*** puranamr has joined #openstack-meeting-316:18
kevinbentonnot terribly, the very basic l2 wiring doesn't rely on the data bags16:18
marunkevinbenton: right, that's lcd16:18
*** dims_ has joined #openstack-meeting-316:18
mestery"ODL flavored ports" and "data bags", only in a neutron meeting16:18
marunkevinbenton: necessary but not sufficient to run most clouds16:19
mesteryLook16:19
mesterypart of the problem with neutron is that vendors still want to differentiate16:19
mesteryAt the expense of their customers16:19
marun'part'? ;)16:19
mesteryLook at all the stuff we've let into the client for example16:19
mestery"vendors gotta vend"16:19
russellbmarun: ha16:19
marunIt's the cost of doing business, yeah16:19
mesteryOur job is to keep growing lcd16:19
armaxmestery: amen to that16:19
dougwig*cough*, some of their customers want that differentiation too.16:19
kevinbentonmarun: no, monolithic plugins skirt the provider extension and they provide l2. ml2 raises the requirements to expose the encap info16:20
mesterydougwig: Right, thus, "vendors gotta vend"16:20
russellbi think differentiation is possible without opaque data bags16:20
russellbyou can have a proper abstraction that not every backend implements16:20
mesteryrussellb: ++16:20
russellband implementations of abstractions can be superior in other ways too, performance, ease of deployment, whatever16:20
marunrussellb: just have to get people to work together to develop those common abstractions16:20
amotokiAPi should define both protocol and its behaivor. If we don't define the behavior, it means we don't provide a proper abstraction. it is from operators view.16:20
marunrussellb: we can definitely improve in that regard16:20
armaxI think we’re dereiling the conversation badly16:20
russellbmarun: totally ... and i view that as a core part of what neutron is16:20
*** dims__ has joined #openstack-meeting-316:20
armaxnot sure whetehr that was intended16:20
russellbor should be16:20
kevinbentonport tags as a service16:20
dougwigi thought we already decided against data bags.  i'm nots sure why we're still arguing.16:20
russellbare we violently agreeing?16:21
mesteryright16:21
marunyes16:21
russellbi mean, that can be fun sometimes16:21
mesterywe're agreeing16:21
mestery:)16:21
mesterydata bags are out!16:21
marundougwig: arguers gonna argue16:21
kevinbentonwe came to agreement too soon, we have argument quotas16:21
mesterylol16:21
mesteryOK, I'd say that's it for this week.16:21
dougwigthen let's talk service chaining.16:21
armaxbah16:21
armaxI am lost16:21
mesteryrofl16:21
*** barra204 has joined #openstack-meeting-316:21
kevinbentonwhat am i supposed to do with all of this indignant outrage!?!?16:21
marunservice _flavor_ chaining (ftfy)16:21
dougwigkevinbenton: go murder a puppy16:22
mesteryrofl16:22
russellbwoah16:22
russellbthat escalated quickly16:22
armaxyou guys clearly taking me for a ride16:22
*** david-lyle has quit IRC16:22
kevinbenton he's from idaho, they do things differently there16:22
mesteryarmax: You're like a 57 corvette my friend16:22
armaxbye bye now16:22
mesterylol16:22
marunheh16:22
* mestery reigns everyone back in16:22
mesteryOK16:22
mesteryfocus. FOCUS!16:22
mesteryI'm proposing the meeting is over, unless someone has another RFE they want to look at in 7 minutes?16:23
HenryGA quick one16:23
mesteryHenryG: Please16:23
HenryGBug 146072016:23
openstackbug 1460720 in neutron "Move ipv6_gateway L3 config to CLI" [Undecided,New] https://launchpad.net/bugs/1460720 - Assigned to Abishek Subramanian (absubram)16:23
HenryGThe rfe tag was removed16:23
mesteryHenryG: I think I wasn't in favor of this even being an RFE16:23
mesteryI removed the tag in fact :)16:23
HenryGBut it changes the api, just wanted to make sure16:23
*** dims_ has quit IRC16:24
mesteryHenryG: Ah, ok! In reality, the RFE wasn't written well (had too much "how"), again, not picking on the submitter, the process is new16:24
mesteryHenryG: Bottom line, I made a mistake here and I'll correct it16:24
amotokiagreed that moving something to client side sounds a big change.16:24
HenryGyes, it should say "Add API to configure v6 gateway"16:25
HenryGSo add rfe tag back?16:26
mesteryOK, thanks amotoki HenryG.16:26
mesteryI added it back16:26
mesteryrefresh16:26
amotokiHenryG: do we still have IPv6 meeting in Liberty?16:26
kevinbentonno16:26
HenryGI can update the title and description16:26
kevinbentonamotoki: sean disbanded it16:26
HenryGWe discuss v6 in the L3 meeting if needed16:26
amotokiI think it is worth discussed among IPv6 experts.16:26
mestery#action HenryG to make sure Bug 1460720 is discussed during an upcoming L3 meeting with carl_baldwin and team16:27
openstackbug 1460720 in neutron "Move ipv6_gateway L3 config to CLI" [Undecided,New] https://launchpad.net/bugs/1460720 - Assigned to Abishek Subramanian (absubram)16:27
HenryGmestery: thanks!16:27
* carl_baldwin adds it to the agenda…16:27
* mestery ^5s carl_baldwin.16:27
HenryGcarl_baldwin: thanks!16:27
mesteryOK16:27
*** singlethink has joined #openstack-meeting-316:27
dougwigwell, this has been a surreal meeting.16:27
mesteryThat's a wrap!16:27
mesterylol16:28
mesteryThanks folks!16:28
russellbthanks for letting me crash it16:28
mesteryrussellb: Anytime :)16:28
mesteryHenryG too!16:28
mestery#endmeeting16:28
*** barra204 has quit IRC16:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:28
openstackMeeting ended Wed Jun  3 16:28:19 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-06-03-15.30.html16:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-06-03-15.30.txt16:28
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-06-03-15.30.log.html16:28
*** ihrachyshka has quit IRC16:28
amotokigoing back to the beginning, HenryG and kevinbenton joined the meeting now. we can merge and already merged lts sycn and driver-team meeting :-)16:29
mesteryamotoki: Patience, working on it :)16:30
*** marun_ has joined #openstack-meeting-316:30
*** mrmartin has quit IRC16:32
*** scheuran has quit IRC16:33
*** marun has quit IRC16:33
*** vineetmenon_ has joined #openstack-meeting-316:34
*** vineetmenon has quit IRC16:34
*** vineetmenon_ has quit IRC16:34
*** marun has joined #openstack-meeting-316:34
*** marun_ has quit IRC16:35
*** vineetmenon_ has joined #openstack-meeting-316:35
*** tholtzen has quit IRC16:36
*** praveens has quit IRC16:37
*** mrmartin has joined #openstack-meeting-316:38
*** Swami has joined #openstack-meeting-316:40
*** safchain has quit IRC16:41
*** ttrifonov is now known as zz_ttrifonov16:44
*** sarob has joined #openstack-meeting-316:45
*** lblanchard has joined #openstack-meeting-316:47
*** tholtzen has joined #openstack-meeting-316:48
*** tholtzen has left #openstack-meeting-316:51
*** Longgeek has quit IRC16:55
*** belmoreira has joined #openstack-meeting-316:58
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Jun  3 17:00:29 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
alaskiAnyone around for the cells meeting?17:00
bauzas\o17:00
melwitto/17:00
belmoreirao/17:00
dansmitho/17:00
vineetmenon_o/17:00
alaskicool17:01
alaski#topic Tempest testing17:01
*** openstack changes topic to "Tempest testing (Meeting topic: nova_cells)"17:01
alaskiI'm going to put melwitt on the spot and defer to her for updates here17:01
melwitt:)17:01
melwittokay, the cells job seems in the same state as it has been, link here http://goo.gl/b7R8wq17:02
*** vineetmenon_ is now known as vineetmenon17:02
melwittso it's good there's nothing new happening. I went through the failures from yesterday and they all have to do with tests that delete a server, and I have identified a race where instances can be "undeleted" causing some tests to fail or time out17:02
melwittI have this patch up for the fix https://review.openstack.org/#/c/176518/ that fixes it sort of indirectly, details in the bug it closes17:03
*** mrmartin has quit IRC17:03
*** ivar-lazzaro has joined #openstack-meeting-317:03
alaskinice, I will review that again in a bit17:04
bauzasmelwitt: seeing a -W, can I review it ?17:04
melwittI will remove the -W today, I was running a test all night that runs one of the failure-prone tests in a loop to make sure it doesn't make any races with it worse17:04
bauzasmelwitt: ok17:04
*** puranamr has quit IRC17:04
*** puranamr has joined #openstack-meeting-317:04
melwittI finally got it to where it could run all night without failing, so I'll put up a couple of more patches for those races that came out after undelete became impossible17:04
bauzasalaski: which target do you try to reach for having the cells job voting ?17:05
melwittthe UnexpectedTaskStateError is I think unrelated, but is a trace we need to clean up17:05
bauzasalaski: considering another observation period once melwitt's patch lands, I guess ?17:05
alaskimelwitt: okay, so there's still a bit more work17:05
alaskibauzas: that's a good question17:06
melwittthere is also this bug that I *think* doesn't fail tests (I'm not sure) but is a clean up https://bugs.launchpad.net/nova/+bug/144830217:06
openstackLaunchpad bug 1448302 in OpenStack Compute (nova) "cells: intermittent KeyError when deleting instance metadata" [Low,Confirmed] - Assigned to melanie witt (melwitt)17:06
bauzasalaski: I just wonder about any benefits that we could have17:06
alaskibauzas: I would like to see us close to the overall failure rate for non cells, but I don't know that that is right now17:06
bauzasalaski: agreed, melwitt's patch is important17:07
melwittit's another race with update/delete server metadata I think but I didn't spend much time on it17:07
bauzasalaski: my only wonder is how we can prevent any tunnel effect17:07
alaskimelwitt: would it help to have someone else look into that?17:07
bauzasalaski: ie. fixing all the cells bugs17:07
melwittalaski: yeah, I think bauzas said he might want to look at it, so feel free17:07
bauzasalaski: melwitt: my brain certainly needs some recreation, so I would be pleased to help17:07
belmoreirabauzas: sorry, tunnel effect?17:07
alaskigreat17:07
bauzasmelwitt:17:08
bauzascool17:08
*** s3wong has joined #openstack-meeting-317:09
bauzasbelmoreira: sorry, something probably french17:09
melwittso, I guess what I'm thinking is watch the job after the patches land. that I expect to see very few failures after that. but you never know17:09
bauzasbelmoreira: the idea of trying to boil the ocean I guess17:09
*** amotoki has quit IRC17:09
alaskirealistically I think if we fix the list servers negative test failure and the random test failures from unexpected task state errors I think we'll be where we need to be17:09
melwittyeah, okay. I'll have all the patches ready today, now that I'm done testing it17:10
bauzascool17:10
melwittI think that's all I have about the tempest testing17:10
alaskiawesome, great work17:10
bauzasmelwitt: so you don't expect https://bugs.launchpad.net/nova/+bug/1448302 to break tests ?17:10
openstackLaunchpad bug 1448302 in OpenStack Compute (nova) "cells: intermittent KeyError when deleting instance metadata" [Low,Confirmed] - Assigned to melanie witt (melwitt)17:10
alaskithanks for the update17:11
bauzasok, let's move on17:11
melwittbauzas: honestly I don't know, I didn't spend enough time to be sure. often it doesn't fail them17:11
alaski#topic Specs17:11
*** openstack changes topic to "Specs (Meeting topic: nova_cells)"17:11
alaskiThe host mapping spec merged during the summit17:12
alaskiand https://review.openstack.org/#/c/141486/ is ready for review17:12
*** rlpple has joined #openstack-meeting-317:12
alaskiand the followup to that one, though I suspect it will need some work17:12
*** rlpple has left #openstack-meeting-317:12
*** david-lyle has joined #openstack-meeting-317:13
alaskiI have a few more to write, but have still been organizing a few things after the break last week17:13
alaskibut there is some work available if anyone is interested, in implementing the host mapping spec17:13
*** david-lyle has quit IRC17:13
alaskiand that's all I have on that, so if no comments we can move on17:14
belmoreiraalaski: we are looking into a spec to have flavor tables in the api DB17:14
*** marun has quit IRC17:14
alaskibelmoreira: ahh, excellenbt17:14
alaskibah, excellent17:14
*** david-lyle has joined #openstack-meeting-317:15
alaskiplease ping me when that's up, or add me to the review17:15
*** marun has joined #openstack-meeting-317:15
bauzasalaski: that spec seems pretty trivial to be done, probably we should propose some new contributors for it ?17:15
*** rushiagr is now known as rushiagr_away17:15
alaskiand add it to the agenda for mention, or I can do that17:16
bauzasalaski: thinking about the "mentoring" stuff you know17:16
alaskibauzas: I would love for somebody to pick up that work17:16
bauzasalaski: we know we have some quickwins that new contributors could help, and that one seems also a good opportunity17:16
belmoreiraalaski, bauzas: we can do it17:16
bauzasbelmoreira: \o/17:16
vineetmenonalaski, bauza, belmoreira one thing to be confirmed about that spec..17:16
bauzasbelmoreira: I can help you on the implementation but I don't have the bandwidth for implementing it17:17
vineetmenonwe assumed that flavor will reside in cell.. i hope it's okay17:17
*** e0ne has quit IRC17:17
bauzasbelmoreira: so you can hassle me on that one17:17
bauzasbelmoreira: to be clear, I was talking about cell-host-mapping :)17:17
alaskivineetmenon: what do you mean?  I thought we were discussing moving flavor to the api db17:18
*** shwetaap has quit IRC17:18
alaskiso out of the cell17:18
vineetmenonalaski, ooh ya.. sorry. flavors in api17:18
*** mrmartin has joined #openstack-meeting-317:18
alaskivineetmenon: yes, that's okay.  I think there's agreement that that's where they should be17:19
bauzas+117:19
belmoreiradoes anyone have the spec number... I can't find it now...17:19
bauzasbelmoreira: still happy with https://review.openstack.org/#/c/182715/2/specs/liberty/approved/cells-host-mapping.rst,cm ?17:19
alaskihttps://review.openstack.org/#/c/182715/17:19
belmoreiraalaski: thanks17:20
bauzaseh :)17:20
*** egallen has joined #openstack-meeting-317:21
bauzasbelmoreira: so, there is an API model, a migration script to write and a NovaObject to provide17:21
alaskibelmoreira: to make sure we're on the same page, you're saying that you can help with that spec?17:21
vineetmenon+117:21
belmoreiraalaski: yes17:21
alaskigreat, thanks17:21
bauzasbelmoreira: awesome17:21
*** yamahata has quit IRC17:21
alaskianything else on specs?17:22
alaski#topic Open Discussion17:22
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:22
alaskianything else to discuss generally?17:22
belmoreirawhat is blocking https://review.openstack.org/#/c/136490/ ?17:23
alaskibelmoreira: I just need to go through it again and refresh it17:24
alaskimy goal is that by the next meeting I will have refreshed all specs, and written more or at least have a list of specs I think need to be proposed17:25
alaskianything else?17:26
alaskithanks everyone!17:26
alaski#endmeeting17:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:26
bauzasthanks17:26
openstackMeeting ended Wed Jun  3 17:26:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-06-03-17.00.html17:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-06-03-17.00.txt17:26
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-06-03-17.00.log.html17:26
vineetmenoncaio.17:27
*** reed_ has joined #openstack-meeting-317:27
bauzasbelmoreira: since I'm committed to mentor some people on Nova, you can ping me if needed17:27
belmoreirabauzas: thanks17:27
vineetmenonyes.. I'll need that. :D17:27
belmoreirabauzas: vineetmenon is working with me, he also will need some help17:28
*** david-lyle has quit IRC17:28
alaskiI'm always open to pings as well, though my hours may not line up as well as bauzas17:28
bauzasvineetmenon: what I'm trying to figure out is a list of easy actionable items that new contributors can do17:28
bauzasvineetmenon: I've made the experience that low-hanging-fruit bugs are not the best entry door for Nova17:29
vineetmenonhmm.. we (belmoreira and us) have made a list as well... whcih includes both the items discussed today17:29
bauzasvineetmenon: but that's a general point, not only including the cells effort17:29
bauzasalaski: unless you move to Geneva or Grenoble :)17:30
vineetmenonbauzas: oh. k. I agree on what you said about low-hanging fruit, though17:30
alaskibauzas: heh.  I'll need to know the weather and how good the hiking is before considering that17:31
belmoreirabauzas: vinnetmenon and Deerej are working in a collaboration with CERN to help improve cells17:31
*** egallen has quit IRC17:31
*** mickeys has joined #openstack-meeting-317:31
bauzasalaski: one pic http://en.wikipedia.org/wiki/Grenoble#/media/File:Moucherotte_23_12_11_092_%282%29_final.JPG17:31
belmoreiraThey are happy to help in any related work17:31
bauzasbelmoreira: cool17:31
*** shwetaap has joined #openstack-meeting-317:31
alaskibauzas: that is very compelling17:32
vineetmenonbauzas: ack17:32
*** s3wong has quit IRC17:33
*** vikram has joined #openstack-meeting-317:34
*** Sukhdev has quit IRC17:34
*** sridhar_ram has joined #openstack-meeting-317:35
*** yamahata has joined #openstack-meeting-317:40
*** vineetmenon has quit IRC17:42
*** Networkn3rd has joined #openstack-meeting-317:44
*** praveens has joined #openstack-meeting-317:48
*** reed_ has quit IRC17:52
*** vikram has quit IRC17:54
*** s3wong has joined #openstack-meeting-318:01
*** belmoreira has quit IRC18:02
*** VW_ has joined #openstack-meeting-318:03
*** praveens1 has joined #openstack-meeting-318:03
*** egallen has joined #openstack-meeting-318:04
*** VW has quit IRC18:05
*** praveens has quit IRC18:05
*** ivar-lazzaro has quit IRC18:12
*** ivar-lazzaro has joined #openstack-meeting-318:15
*** sridhar_ram has quit IRC18:16
*** egallen has quit IRC18:17
*** eghobo_ has joined #openstack-meeting-318:18
*** sballe has quit IRC18:18
*** praveens1 has left #openstack-meeting-318:18
*** eghobo has quit IRC18:18
*** ivar-lazzaro has quit IRC18:19
*** ivar-lazzaro has joined #openstack-meeting-318:19
*** VW_ has quit IRC18:19
*** VW has joined #openstack-meeting-318:20
*** yamahata has quit IRC18:25
*** yamahata has joined #openstack-meeting-318:25
*** SridarK has joined #openstack-meeting-318:26
*** fallenpegasus has quit IRC18:26
*** madhu_ak has joined #openstack-meeting-318:27
*** jwarendt has joined #openstack-meeting-318:28
*** pc_m has joined #openstack-meeting-318:30
SridarKvishwanathj: yamahata: pc_m: Hi18:30
vishwanathjhi SridarK, hi All18:30
yamahatahello18:30
xgermanhi18:30
madhu_akhello18:30
*** jwarendt_ has joined #openstack-meeting-318:30
pc_mSridarK: hi18:30
SridarKxgerman: madhu_ak: hi18:30
SridarKSumitNaiksatam is out sick - so requested me to run the mtg18:31
SridarKwe will do a quick sync up18:31
SridarK#startmeeting Networking FWaaS18:31
openstackMeeting started Wed Jun  3 18:31:33 2015 UTC and is due to finish in 60 minutes.  The chair is SridarK. Information about MeetBot at http://wiki.debian.org/MeetBot.18:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:31
SridarKLets run thru bugs, specs and other important actions18:32
*** jwarendt has quit IRC18:32
SridarK#topic Bugs18:32
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:32
*** slaweq has joined #openstack-meeting-318:32
SridarKWe discussed last week:18:32
SridarK#link https://bugs.launchpad.net/neutron/+bug/145586318:33
openstackLaunchpad bug 1455863 in neutron "FWAAS- FW Rule editing puts FW to error state " [Undecided,Confirmed] - Assigned to vikram.choudhary (vikschw)18:33
*** badveli has joined #openstack-meeting-318:33
vishwanathjI was able to reproduce the issue as well in Kilo18:33
*** david-lyle has joined #openstack-meeting-318:33
badvelihello all18:33
SridarKThis could be an issue with Agent communication - i will sync with vikram to help18:33
slaweqhello guys18:33
SridarKbadveli: hi18:33
SridarKslaweq: hi18:33
badvelihello sridar and all18:33
SridarKthe other one:18:34
SridarK#link https://bugs.launchpad.net/horizon/+bug/145497418:34
openstackLaunchpad bug 1454974 in OpenStack Dashboard (Horizon) "FWAAS- FW rules table is asymmetric." [Undecided,New] - Assigned to Kahou Lei (kahou82)18:34
SridarKdashboard related - vishwanathj: could i request u to take a look and offer any help or suggestions18:34
vishwanathjSridarK, I will take a look after this meeting18:34
SridarKvishwanathj: thanks18:35
SridarKother than these there was nothing new or critical18:35
SridarKothers pls add if there is something i have missed18:35
SridarKok so we are good - we can move on to specs18:36
SridarK#topic Traffic direction Spec18:36
*** openstack changes topic to "Traffic direction Spec (Meeting topic: Networking FWaaS)"18:36
*** Networkn3rd has quit IRC18:37
SridarKthanks slaweq: & Vikram  for working thru this18:37
slaweqI made some changes in specs18:37
*** stevelle has left #openstack-meeting-318:37
slaweqis it what we were talking about last week SridarK?18:37
SridarKslaweq: yes i am good18:37
SridarKslaweq: u had a few other comments - have u addressed all - if not u can clean up and push another patch18:38
slaweqI was trying to answer for all and address all in new patchset18:39
SridarKslaweq: ok18:39
slaweqbut maybe I forgot about something18:39
SridarKslaweq: ok no worries - u can ping the folks with comments and if they are good u should get a +1 and then u can reach out cores18:40
SridarK* to cores18:40
slaweqok, I will try to ask them to review it again18:40
SridarKslaweq: sounds good18:40
SridarKslaweq: anything else u would like to discuss here18:40
*** tholtzen has joined #openstack-meeting-318:40
slaweqno18:41
SridarKslaweq: ok thx for the update18:41
SridarK#topic Service Objects/Group18:41
*** openstack changes topic to "Service Objects/Group (Meeting topic: Networking FWaaS)"18:41
slaweqSridarK: np18:41
SridarKbadveli: were u planning to push up a spec18:41
SridarKbadveli: i think u can fast track this18:41
badvelii already did18:42
SridarKsince it was approved for Kilo18:42
SridarKok cool - can u pls post the link18:42
*** vkmc has quit IRC18:42
badveliyes18:42
*** yanping has joined #openstack-meeting-318:42
SridarKbadveli: sorry i did not realize18:42
badvelihttps://review.openstack.org/#/c/185765/18:42
badvelino problem, i followed one of the patch that does18:43
badvelirepurpose the juno spec to kilo18:43
*** puranamr has quit IRC18:43
badvelisorry kilo-backlog to liberty18:43
SridarKi think u may need another patch here - but good now we have the coordinates to go look18:44
*** flaper87 has quit IRC18:44
SridarKbadveli: any issues u want to bring up ?18:44
SridarKor discuss18:44
badvelinothing much but i think this is the way we repurpose a spec as per one of the patch that was given as the guidelines18:45
vishwanathjbadveli, I do not see the contents, how are reviewers going to provide their comments?18:45
SridarKvishwanathj: yes - hence i requested badveli: that he may need another patch18:46
badvelivishwanthj this is only a repurpose the spec that is alreasy approved as per kilo18:46
badvelithe spec needs to be moved from kilo-backlog to liberty18:46
badvelithere is already a patch kyle had done to repurpose a spec18:47
badveliwe only move the spec18:47
vishwanathjok, thanks18:47
badvelithere is a kilo-backlog that is already there with the spec that needs to be moved18:47
SridarKbadveli: ok maybe we can sync up offline more on this to make sure we can see the contents ?18:48
badvelilet me give a link that kyle had done to repurpose a spec if i can find18:48
badveliin the meeting18:48
badveliotherwise i will send an offline message18:48
SridarKbadveli: sounds good - lets take if offline18:48
SridarK*it18:48
SridarKbadveli: anything else u want to bring up ?18:49
badveli  nothing18:49
SridarKbadveli: ok thanks18:49
badveli from my side thanks18:49
*** puranamr has joined #openstack-meeting-318:49
SridarK#topic Logging Spec18:49
*** openstack changes topic to "Logging Spec (Meeting topic: Networking FWaaS)"18:49
SridarK#link https://review.openstack.org/#/c/132133/18:49
SridarKi don't see yushiro here today18:50
SridarKthis is getting reviews, i had some discussion with yushiro at the summit as well18:50
SridarKwe can pick this up next time or on gerrit18:50
SridarK#topic SG - FWaaS alignment18:51
*** openstack changes topic to "SG - FWaaS alignment (Meeting topic: Networking FWaaS)"18:51
SridarKFrom the summit - the other important thing is that we should help on the effort to look for alignment with SG.18:51
*** puranamr has quit IRC18:51
SridarKWe should all run thru the use cases and help with the discussion in any way.18:51
*** puranamr has joined #openstack-meeting-318:51
xgerman+118:51
SridarKthere was an email from xgerman:18:51
SridarK#link https://etherpad.openstack.org/p/fwaas_use_cases18:52
xgermanyep18:52
*** baoli has quit IRC18:52
SridarKwould request all to take a look and lets get some use cases and help in any way18:52
xgermanI am still trying to invite some operators and end users to give us use cases18:52
SridarKxgerman: great and pls add anything more u would like to on this topic18:52
xgermanpeople went on vacation right after the summit :-(18:52
SridarKxgerman: i suspect most of this month is going to be like that18:53
xgermanyeah, once we have the use cases collected we can rethink the API18:53
SridarKxgerman: yes absolutely and meanwhile if there are things to look lets also discuss here18:53
xgermanyep18:53
SridarKwe can keep this is a living topic on the mtg18:54
mickeysI have a hard time figuring out what to think about the traffic direction spec without any resolution to the FWaaS alignment discussion18:54
xgermansounds good18:54
SridarKxgerman: thx18:54
SridarKmickeys: hi18:54
mickeyshi18:54
xgermanmickeys agreed18:54
SridarKmickeys: yes this is a bit of tightrope with any spec18:54
*** mordred has quit IRC18:55
*** mordred has joined #openstack-meeting-318:55
SridarKmickeys: but the direction from Kyle has been to get specs going and continue the discussion18:55
SridarKperhaps we may have a v2 API - yes these things are still TBD18:55
mickeysJust noting that some iteration may be required, depending on the progress of FWaaS alignment18:55
xgerman+118:55
SridarKbut if we have something going - it may be a question of refactor18:56
SridarKrather than start the work fresh18:56
SridarKbut i agree as well18:56
xgermanit really depends on the bandwidth and where we want to concentrate our efforts18:56
*** Networkn3rd has joined #openstack-meeting-318:56
SridarKyes we will record that for all contributors - that there will be some refactor - we should be open to that18:57
mickeysIf we are able to get any consensus on FWaaS alignment, IBM would like to pitch in18:57
SridarKmickeys: +118:57
xgerman+118:57
SridarKthat will be good - banix also mentioned this18:57
jwarendt_+118:57
*** barra204 has joined #openstack-meeting-318:57
vishwanathjin my opinion, until there is a concrete plan spelled out for the fwaas alignment, we should continue to make progress and not wait18:58
vishwanathjthat's just my opinion18:58
SridarKvishwanathj: and we are open to the fact there will be reiteration/refactor18:58
mickeysIs the association of ports with firewalls going ahead, or is that tied into the FWaaS alignment discussion?18:59
xgermanwell, as long as we keep an open mind when going into those features18:59
vishwanathjyes, we are open to re-iteration and refactor18:59
SridarKbut this may be a case by case basis18:59
SridarKmickeys: the port association will be really close to SG alignment18:59
mickeysOK, good to know18:59
SridarKmickeys: unless u are thinking only router ports19:00
*** Networkn3rd has quit IRC19:00
*** Networkn3rd has joined #openstack-meeting-319:00
mickeysI would like router ports or VM ports, so I agree to making it part of the FWaaS alignment discussion19:00
SridarKmickeys: in that case will be good to get some thoughts down on the etherpad and get some consensus19:00
SridarKmickeys: exactly19:00
mickeysI mentioned router ports, VM ports, and groups of each in the etherpad last night19:01
SridarKmickeys: great19:01
SridarKxgerman: anything else u would like to bring up ?19:01
xgermandon’t see them join here https://etherpad.openstack.org/p/fwaas_use_cases19:01
xgermanmickeys?19:01
xgermanon here19:02
mickeysI am OK for now. Waiting for the real FWaaS alignment discussion ...19:02
xgermank19:02
*** barra204 has quit IRC19:02
SridarKok sounds good19:03
SridarK#topic Open Discussion19:03
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:03
*** puranamr has quit IRC19:03
vishwanathjSridarK, who is driving the FWaaS alignment discussion19:03
vishwanathj?19:03
SridarKxgerman: has kickstarted it and i think it is open for all of us to join in19:03
xgermanyes19:04
SridarKand help out19:04
vishwanathjgood to know, thanks19:04
xgermanit’s a team effort19:04
badvelifine sridark19:04
vishwanathjSridarK, I was wondering if there are any thoughts of making this meeting bi-weekly ......19:05
SridarKvishwanathj: yes that makes sense19:05
SridarKvishwanathj: there is probab a lot of PTO going around as well now19:05
vishwanathjbecause its summer time and lot of people are going to be out on vacation with kids and stuff19:05
SridarKvishwanathj: and we can get some more traction on the alignment discussions too19:06
SridarKsounds like a good idea to me19:06
SridarKif no one has any objections we can do that - we can always change the frequency back to every week as needed19:06
xgerman+119:07
jwarendt_+119:07
SridarKok great lets do that then19:07
badveli  fine19:08
SridarKfolks can always be reached on irc or email if any discussions are needed19:08
SridarKanything else anyone wanted to bring up ?19:08
*** flaper87 has joined #openstack-meeting-319:08
vishwanathjxgerman, How do I get involved with the FWaaS alignment discussion? Thanks19:08
xgermanI started the ether pad to collect use cases19:09
xgermanand we will use this meeting to discuss progress19:09
*** flaper87 has quit IRC19:09
*** flaper87 has joined #openstack-meeting-319:09
SridarKxgerman: +119:09
jwarendt_Use cases very basic right now; did mickeys cases make the etherpad?19:09
xgerman+119:09
vishwanathjok, thanks.....is there a planned timeline and milestones? I ask that to figure out how this is going to progress19:10
madhu_ak+119:10
jwarendt_asap?19:10
mickeysjawarendt: I cannot say what I put in the etherpad goes beyond basic either19:10
xgermanwell, we are still working out the specifics but we are hoping to have everything done in Liberty19:12
SridarKok as a first step lets get some traction on the ether pad, but as xgerman: mentioned earlier we need more operator inputs here as well19:12
xgerman+119:13
jwarendt_+119:13
madhu_ak+119:13
*** e0ne has joined #openstack-meeting-319:13
SridarKok great may be we close out on this "aligned moment" on this mtg. :-)19:14
SridarKok folks all have a great rest of the week and we will meet in 2 weeks then.19:14
xgermanbye19:14
jwarendt_Thanks everyone!19:15
badveli thanks and bye19:15
madhu_akbye folks19:15
slaweqbye19:15
*** jwarendt_ has quit IRC19:15
SridarKi will update the wiki etc for frequency19:15
SridarKbye all19:15
SridarK#endmeeting19:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:15
openstackMeeting ended Wed Jun  3 19:15:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-06-03-18.31.html19:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-06-03-18.31.txt19:15
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-06-03-18.31.log.html19:15
vishwanathjbye19:15
*** slaweq has quit IRC19:15
*** pc_m has left #openstack-meeting-319:16
*** SridarK has quit IRC19:16
*** mickeys has left #openstack-meeting-319:17
*** Networkn3rd has quit IRC19:17
*** yanping has quit IRC19:18
*** puranamr has joined #openstack-meeting-319:22
*** tholtzen has left #openstack-meeting-319:22
*** egallen has joined #openstack-meeting-319:24
*** tholtzen has joined #openstack-meeting-319:26
*** jgrimm is now known as zz_jgrimm19:26
*** tholtzen has left #openstack-meeting-319:27
*** vkmc has joined #openstack-meeting-319:28
*** puranamr has quit IRC19:32
*** tholtzen has joined #openstack-meeting-319:35
*** Swami has quit IRC19:35
*** tholtzen has left #openstack-meeting-319:37
*** VW has quit IRC19:38
*** woodm19791 has joined #openstack-meeting-319:39
*** neillc has joined #openstack-meeting-319:40
*** igordcard_ has quit IRC19:40
*** jwy has joined #openstack-meeting-319:45
*** sqchen has joined #openstack-meeting-319:48
*** mrunge has quit IRC19:49
*** mattgriffin has quit IRC19:50
*** Networkn3rd has joined #openstack-meeting-319:51
*** mrunge has joined #openstack-meeting-319:52
*** armax has quit IRC19:53
*** natorious is now known as zz_natorious19:53
*** vkmc has quit IRC19:53
*** doug-fish has joined #openstack-meeting-319:55
*** ongk has joined #openstack-meeting-319:56
*** madhu_ak has left #openstack-meeting-319:56
*** egallen has quit IRC19:57
*** matt-borland has joined #openstack-meeting-319:57
*** pauloewerton has joined #openstack-meeting-319:57
*** flaper87 has quit IRC19:57
*** VW has joined #openstack-meeting-319:58
*** yanping has joined #openstack-meeting-319:58
*** barra204 has joined #openstack-meeting-319:58
*** TravT has joined #openstack-meeting-319:58
*** flaper87 has joined #openstack-meeting-319:59
*** VW_ has joined #openstack-meeting-319:59
*** lhcheng has joined #openstack-meeting-319:59
*** ducttape_ has joined #openstack-meeting-320:00
david-lyle#startmeeting Horizon20:00
openstackMeeting started Wed Jun  3 20:00:57 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** puranamr has joined #openstack-meeting-320:00
*** openstack changes topic to " (Meeting topic: Horizon)"20:01
openstackThe meeting name has been set to 'horizon'20:01
woodm19791Good afternoon!20:01
TravTo/20:01
matt-borlando/20:01
lhchengo/20:01
r1chardj0n3so/20:01
*** clu_ has joined #openstack-meeting-320:01
neillco/20:01
bpokornyHi all20:01
mrungehello there20:01
doug-fishgreetings20:01
clu_hi!20:01
ducttape_yo20:01
pauloewertonhi there20:01
*** tqtran has joined #openstack-meeting-320:01
*** hurgleburgler1 has joined #openstack-meeting-320:02
*** tqtran has quit IRC20:02
asahlinhello20:02
rhagartyhowdy20:02
*** tqtran has joined #openstack-meeting-320:03
david-lylehello everyone20:03
hurgleburgler1Hello20:03
*** VW has quit IRC20:03
tqtran0/20:03
david-lyleas the horizon turns episode 200020:03
*** barra204 has quit IRC20:03
*** flaper87 has quit IRC20:03
*** marun_ has joined #openstack-meeting-320:03
lhchenghttps://wiki.openstack.org/wiki/Meetings/Horizon20:03
asahlinlol, what season?20:03
*** marun has quit IRC20:03
david-lyleso the agenda for today can be found on the link lhcheng provided20:04
david-lylethanks lhcheng20:04
lhchengwow, we have a lot in agenda today20:04
*** sballe has joined #openstack-meeting-320:04
david-lylecrazy, right?20:04
r1chardj0n3sok, who added all that stuff to the agenda? :)20:04
*** Aish has joined #openstack-meeting-320:04
*** ajmiller has joined #openstack-meeting-320:05
lhchenglol20:05
TravTwhat's wrong with people?20:05
*** clu has joined #openstack-meeting-320:05
david-lyleI have an extra topic that I'm going to start with20:05
david-lylejust cause20:05
woodm19791#drunkwithpower20:05
r1chardj0n3sSurprise Topic!20:05
neillcNobody expects the surprise topic20:06
david-lyleOpenStack is moving from a shake the magic 8-ball approach to release planning to reporting what we did20:06
tqtranhe's holding out the anticipation20:06
hurgleburgler1darn, forgot to add my topic!!20:06
david-lylehurgleburgler1: go ahead20:07
*** mattgriffin has joined #openstack-meeting-320:07
david-lyleon the wiki20:07
tqtrandavid-lyle: what does that mean?20:07
r1chardj0n3s(oh good, it wasn't just me)20:07
mrungewe'll probably have fewer blueprints completed20:07
doug-fishso ... no planning? just reporting results?20:07
david-lyleso we used to slate all these blueprints for milestones and hope by some crazy chance it might actually land there20:07
doug-fishlol - I thought that was the old process!20:08
doug-fishoh wait20:08
* doug-fish stops laughing and reads20:08
david-lylethe success rate was quite low, not surprisingly20:08
david-lyleAt the summit we actually spent some time lining up what the priorities were20:08
*** salv-orlando has quit IRC20:09
david-lylethey were collated here #link https://etherpad.openstack.org/p/YVR-horizon-liberty-priorities20:09
*** salv-orlando has joined #openstack-meeting-320:09
david-lylewe also talked about having a page that showed review priority20:09
*** e0ne is now known as e0ne_20:09
david-lyleMy suggestion would be just to use the etherpad to track the release20:09
*** baoli has joined #openstack-meeting-320:10
david-lylerather than on a per milestone basis20:10
r1chardj0n3spile of poo here we come20:10
david-lylelink the bps and bugs on that etherpad directly20:10
david-lyleI've found two things over time20:10
david-lyle1) reviewers don't actually look at the milestone list to prioritize blueprint reviews20:11
david-lyle2) moving around random things in launchpad is not highly effective.20:11
david-lyleThoughts?20:11
doug-fishagreed20:11
TravTWell, I liked using etherpad for launch instance last release20:12
r1chardj0n3sI think it's worth a shot, perhaps we just need to remind folks occasionally20:12
doug-fishThe etherpad is probably clearer and simpler - and no reason to think it will be less effective20:12
r1chardj0n3salso, could people with testing patches please update https://etherpad.openstack.org/p/june_2015_testing_push :)20:12
matt-borlandsure thing20:12
r1chardj0n3s(that's linked from the priorities page)20:12
tqtranyeah, im fine with either approach, but having etherpad helps a bit. my only concern is when it starts to grow and becomes a tangle of mess20:12
r1chardj0n3sat least - unlike blueprints - you can have an actual conversation in an etherpad20:13
david-lyleI had the same issue with launchpad20:13
mrungeI would expect to become a mess more sooner than later20:13
*** baoli has quit IRC20:13
mrungethere is no sync back to etherpad20:13
r1chardj0n3s... or are we still expecting to use blueprints?20:13
mrunge(once patch is reviewed)20:13
r1chardj0n3smrunge: good point20:13
woodm19791mrunge's point is the biggest20:13
r1chardj0n3sit's very manual20:13
*** baoli has joined #openstack-meeting-320:13
tqtrani think a hybrid approach might make sense, have your bp in launchpad, and link it in etherpad20:13
mrungetqtran, that's double effort then20:14
*** e0ne_ is now known as e0ne20:14
bpokornyAnyone can modify the etherpad, so we'd have to watch out for who is changing/deleting things.20:14
tqtranthis way, the details and stuff is out of the way and reviewers can just focus on line items they need to knock down20:14
* david-lyle pulls back the curtain a bit20:14
david-lyleI update the bp status manually in launchpad too20:14
david-lyleit's not automated20:14
*** e0ne has quit IRC20:14
TravTWell, one thing i like about the current etherpad linked here is that we can see themes.20:14
mrungeaand, easiest way to sneak own patches to top prio ;-)20:14
bpokornyYes!20:15
TravTtrue, no governance mrunge.20:15
TravTetherpad does have a timeslider...20:15
TravThttps://etherpad.openstack.org/p/YVR-horizon-liberty-priorities/timeslider20:15
TravTbut, no way to enforce changes20:16
mrungeTravT, true, so revisions are recorded.20:16
doug-fishI like the etherpad idea - maybe we revisit if we find it's being abused/vandalized?20:16
*** flaper87 has joined #openstack-meeting-320:16
david-lyleif you all like launchpad, we can stick with that, I just waste a lot of time on managing those lists20:16
*** hurgleburgler1 is now known as hurgleburgler20:16
TravTalthough, it doesn't seem to work right (at least playing with it).20:16
david-lyleand get very little out of it20:16
TravTwait, now it is working.20:16
r1chardj0n3swoah, woah, who alleged I like launchpad?20:17
david-lyleTravT: you have to save revisions as well20:17
david-lyleI would also hazard to guess 75% of what's in the etherpad has neither a bp or bug in launchpad right now20:17
*** alexpilotti has quit IRC20:17
* david-lyle points finger of guilt around the room20:18
r1chardj0n3sthere should be more bugs linked, yes. I will do one now20:18
lhchengDoesn't hurt to try it, I think we should just go for it.20:18
lhchengIt is better than what we do now.20:18
mrungedavid-lyle, that'd be another reason not to use an etherpad20:18
* ducttape_ points a different finger back at david-lyle ;)20:18
tqtranyeah, lets try it and see how well it works out20:18
lhchengWe can revisit it after a few months if it working or not.20:18
* TravT feeling guilty20:18
david-lylethe thing is we have an idea what we want to accomplish, it's there in the etherpad, it's more about fleshing out the details20:19
TravTso, process wise, last release, we'd just use the cross out thing when something got done.20:19
mrungeI'd say: let's try and revisit next week20:19
david-lyleTravT: +120:19
mrungeTravT, but you were under 10 people20:19
TravTyep, agreed20:19
mrungeand you met each day on that pad20:20
TravTi am a little worried having all blueprints linked here will get messy.20:20
*** fallenpegasus has joined #openstack-meeting-320:20
david-lyleit's all messy20:20
TravTmaybe we should copy this etherpad to somewhere for reference.20:20
asahlin+120:20
mrungewe have a little over 240 blueprints currently20:20
*** vkmc has joined #openstack-meeting-320:20
TravTsince it is more thematic at the moment without all the details.20:21
r1chardj0n3swow20:21
david-lylemrunge: and how many of those are legit?20:21
mrungenot to speak about bugs or patchsets20:21
*** mrmartin has quit IRC20:21
mrungedavid-lyle, right. maybe 50?20:21
*** vkmc has quit IRC20:21
*** vkmc has joined #openstack-meeting-320:21
woodm19791We should clean that out then.20:21
hurgleburglerLegit as in Accepted to work on?20:21
woodm19791Switching to etherpad won't help that.  :-)20:21
mrungehurgleburgler, in the past, a not accepted blueprint was not a blocker for review20:22
mrungewe might think again about that20:22
david-lylelets take the week to consider and move on to the scheduled items20:23
mrungewe could simply drop unaccepted blueprints after... 1 month?20:23
david-lylehonestly I find none of the options overly appealing20:23
TravTif you are going to do that, there probably should be a weekly blueprint review meeting among drivers or something like that20:23
hurgleburglernot a bad idea, but more overhead for the bp reviewers20:24
mrunge+1 for discussing blueprints20:24
david-lyle+1 for more overhead20:24
david-lyleoh wait20:24
david-lyleI think it makes sense though20:24
david-lylelet's take this offline for now20:25
david-lyle#topic Angular translation, continue using tweaked Django or switch to Babel? (tqtran/r1chardj0n3s)20:25
*** openstack changes topic to "Angular translation, continue using tweaked Django or switch to Babel? (tqtran/r1chardj0n3s) (Meeting topic: Horizon)"20:25
hurgleburglerI would like it, cause I honestly never know who I need to bribe for a bp20:25
david-lylehurgleburgler: when in doubt, all20:25
r1chardj0n3sooh, translation cage match20:25
david-lyleand in this corner20:25
TravTwe all take bribes around here.20:25
r1chardj0n3soh man, I gotta get in on this bribery action20:26
* TravT digresses - let tqtran have the floor with r1chardj0n3s20:26
tqtranok next topic20:27
tqtranso basically, we have settled on 2 different ways to translate angular static html20:27
r1chardj0n3stqtran: got the bp link? I've lost it because launchpad20:27
tqtranhttps://blueprints.launchpad.net/horizon/+spec/angular-translate-makemessages20:27
tqtranits quite a long read, but it outlines my thought process20:28
tqtranand list alternatives with pros/cons20:28
tqtranright now, i think its agreed that we will go with approach 3 since its something angular-gettext supports20:28
r1chardj0n3s(for markup)20:29
tqtranyes for markup and future compatibility20:29
*** Sukhdev has joined #openstack-meeting-320:29
tqtranthe part where we need a discussion around is the translation extraction20:29
tqtranwhich is listed as options in the bp20:29
*** matrohon has joined #openstack-meeting-320:29
tqtranrichard is advocating for option 2 and using babel for extraction20:30
tqtranhis reasons are as follows:20:30
tqtran1) use angular-gettext now, not later20:30
r1chardj0n3s(except that option 2 I'm advocating is less sucky than the BP implies ;)20:30
tqtran2) use babel to extract messages from django templates and angular templates, exrtacting into the current messages catalog20:30
tqtran3) use django's translation system as we do today over the top of that messages catalog20:30
tqtran4) need to use babeldjango plugin20:30
tqtranand today, i found out that we already have babel in the requirements and are using it to some degree20:31
r1chardj0n3soh!20:31
tqtranthanks to doug-fish for pointing that out20:31
doug-fishsure, np20:31
tqtrani'm advocating for option 320:31
*** singleth_ has joined #openstack-meeting-320:32
tqtran1) use angular-gettext as well20:32
tqtran2) extend a django makemessages command20:32
tqtran3) create a temp file that we dump all static translatable html strings into20:33
tqtran4) let django do its work20:33
r1chardj0n3s(with a hack that leaves a horrid legacy for future horizon devs)20:33
tqtran5) delete file20:33
tqtranits not a hack lol20:33
r1chardj0n3s:)20:33
tqtranhttps://review.openstack.org/#/c/187321/20:33
tqtranhere is the patch for the single translation version, with interpolation and plural added in later patches20:33
r1chardj0n3sit messes with the workings of makemessage in a way that is potentially fragile and not clear to future devs20:33
tqtranit doesn't mess with makemessages, it adds a temporary file that contains all extracted strings so that django can do its thing20:34
r1chardj0n3sthat's my reasoning to use a tool that's designed to be extended and already handles django templates20:34
r1chardj0n3sit replaces makemessages command by overridding the built in class20:34
r1chardj0n3smonkeypatching, yeah :)20:34
*** puranamr has quit IRC20:35
*** singlethink has quit IRC20:35
tqtranso for me, i dont understand babel enough to know how the plugin would fit into horizon20:35
tqtranif you can put up a patch and show how it would all fit together, i will be more than happy to create a plugin for it20:36
* TravT gets some popcorn20:36
tqtranthoughts?20:36
david-lyleI'd like to see an investigation for using babel, the temp file seems "interesting"20:36
neillcI think a look at babel before writing our own tool would be a good idea20:37
r1chardj0n3sbabel plugins are just a python file that knows how to extract messages from text20:37
tqtranyeah, its a work around since we don't have access to override the makemessages class in django20:37
neillcI don't understand either option well enough yet to offer a definitive opinion20:37
TravTi'd agree at this point that seeing an alternate patch with babel would help to clarify.20:37
r1chardj0n3seg here's the existing django one http://babel.edgewall.org/browser/contrib/django/babeldjango/extract.py20:37
david-lylebut if that goes poorly we have a fallback20:37
r1chardj0n3swhich uses django's built-in parser to pull messages from its templates20:37
r1chardj0n3sall we need to do is use tqtran's regex he's already written for his tempfile approach and put it in an extract_angular function and register it with babel20:38
tqtranbut how would we use that in horizon today?20:38
r1chardj0n3sand then instead of invoking manage.py makemessages we invoke babel20:38
r1chardj0n3sthat's it, afaict20:38
r1chardj0n3sthe message catalog produced is the same as today20:39
tqtranso we invoke bable for the angular stuff and leave the js/py/templates to django?20:39
r1chardj0n3sso all the downstream is the same as today20:39
r1chardj0n3stqtran: no, babel extracts the django stuff as well using its plugin. one command20:39
tqtranso we need 2 plugins, a django one and an angular one20:39
*** puranamr has joined #openstack-meeting-320:40
TravTin either case, would the HTML markup look similar (attempt to be forward compatible with angular gettext)?20:40
david-lyleok, r1chardj0n3s can you work on a prototype for that? or someone else? we have a lot to get through today20:40
r1chardj0n3syes, the django one that already exists20:40
tqtranTravT:  yes it would be20:40
r1chardj0n3sdavid-lyle: I can work on it, but I won't get to it until later next week20:40
tqtranok cool, lets wait on the prototype, we can work on it together if you like r1chardj0n3s20:40
r1chardj0n3stqtran: ok, thanks20:41
david-lylethat would be ideal20:41
david-lylethanks!20:41
david-lyle#topic Horizon Keystone to Keystone Federation - current status and future directions (pauloewerton)20:41
*** openstack changes topic to "Horizon Keystone to Keystone Federation - current status and future directions (pauloewerton) (Meeting topic: Horizon)"20:41
stevemardavid-lyle, of course you bring this up as i'm getting ready to leave20:41
david-lyleas I planned it20:41
*** puranamr has quit IRC20:42
david-lyleshould we punt a week on this topic stevemar20:42
david-lyle?20:42
doug-fish(maybe he left?)20:43
david-lyleok, reshuffling deck, slipping K2K to the bottom20:43
pauloewertonso I know that this work is probably blocked because of that keystoneclient auth plugin dependency20:43
*** banix_ has quit IRC20:43
*** radek_ has quit IRC20:44
doug-fishit's true - it looks like they have some nice, not-yet-implemented ideas https://review.openstack.org/#/c/172155/20:44
*** puranamr has joined #openstack-meeting-320:44
stevemari trust doug-fish to know everything20:44
doug-fishstevemar: let me know how that works out for you!20:44
stevemardoug-fish, it's been working well20:44
doug-fish"Oh yeah, the keystone guys will do that"20:45
david-lyleI think this work can't make much progress until we have something concrete to build on, I know doug-fish has a patch up20:45
david-lylebut we can't do much without the dependencies merged20:45
pauloewertonI see20:45
doug-fishtrue.  Here's the patch:  https://review.openstack.org/#/c/159910/20:45
stevemarwe're trying to figure out our auth plugins story on the keystone side20:45
*** matrohon has quit IRC20:46
david-lyleWe can discuss in the horizon room as well20:46
stevemarwe're trying to put all auth plugins into a new repo (keystoneauth)20:46
stevemarand have that ready for L120:46
*** baoli has quit IRC20:46
pauloewertondoug-fish, david-lyle ok, thanks20:46
david-lyleI think there is visibility, we just need to hash out the details20:46
pauloewertonjust a question20:46
stevemar(the k2k plugin should go into that repo)20:46
pauloewertononce this work in django-openstack-auth is finished20:47
pauloewerton would we have something like a service provider selector in horizon nav-bar, for instance?20:47
david-lyleI think this is a discussion that should happen on the blueprint not in the team meeting20:48
doug-fishhttps://blueprints.launchpad.net/horizon/+spec/k2k-federation20:48
pauloewertondavid-lyle, doug-fish, sure.20:48
david-lyleI really need to get to the next two topics and time is dwindling20:49
david-lylepauloewerton: we'll work it out in the bp20:49
david-lyle#topic A Quick searchlight update (TravT)20:49
*** openstack changes topic to "A Quick searchlight update (TravT) (Meeting topic: Horizon)"20:49
TravTso, at the summit, we showed project Searchlight in a fishbowl for both Glance and Horizon.  since then, have been doing the work to get it set up as a new project separated from Glance.20:49
TravTtoday we put up for a vote to be included in the official Big Tent project list #link https://review.openstack.org/#/c/188014/20:49
TravTthe wiki is here: #link https://wiki.openstack.org/wiki/Searchlight20:49
TravThorizon is intended to be a (the?) primary consumer of the project initially, so wanted to give an update and also set some context for discussion on the mid-cycle meet-up.20:50
david-lyle#topic Midcycle meetup (david-lyle, TravT)20:50
*** openstack changes topic to "Midcycle meetup (david-lyle, TravT) (Meeting topic: Horizon)"20:50
david-lyleso a mid-cycle meetup was strongly requested at the summit20:51
david-lylewe've had several offers for hosts, thank you all20:51
*** stevemar has quit IRC20:51
david-lyleOne potential set of dates is July 8-10 in Boston, MA. This would coincide with the glance and searchlight mid-cycles as well20:52
TravTa number of Glance cores are also going to be working on searchlight, so co-locating with them helps get approval.20:52
david-lyleas there is an interest overlap that could potentially very productive20:52
david-lyleI know of at least one person these dates don't work for20:52
hurgleburglerAh doh!  That's during comiccon20:53
woodm19791:-)20:53
hurgleburglersorry, my priority will always be batman20:53
r1chardj0n3s:)20:53
david-lyleSo there are a couple of other options20:53
david-lyleJuly 20-22 or July 21-23 in Fort Collins, CO20:54
hurgleburglerif you did it in san diego, that'd be an interesting mid-cycle meet up :-D20:54
hurgleburglerthe whole city becomes mardi gras for nerds20:54
*** cbouch has quit IRC20:54
david-lyleor another undetermined data in San Jose, CA or maybe Portland, OR20:54
david-lylethoughts on people's availability?20:55
TravTwe've (including nikhil_k - Glance PTL) put together an initial spreadsheet to help bring out ideas and for voting.20:55
TravT#link https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=020:55
TravTroom idea are on top, but if you scroll down20:55
TravTyou can fill in your availability in the "Voting" section20:56
tqtrancool will fill that in20:56
david-lyleso if you can fill that in, we can close quickly20:57
david-lyleif we went with the early dates, people will need to start booking travel in the next few days20:57
*** baoli has joined #openstack-meeting-320:57
david-lyleso please fill it in20:57
* ducttape_ enjoys watching the names fill in. mesmorizing20:58
david-lylemagic20:58
*** lblanchard has quit IRC20:58
david-lylelast two topics real quick20:58
david-lyle#topic Adding events information to instance audit tab https://blueprints.launchpad.net/horizon/+spec/instance-events (peristeri)20:58
*** openstack changes topic to "Adding events information to instance audit tab https://blueprints.launchpad.net/horizon/+spec/instance-events (peristeri) (Meeting topic: Horizon)"20:58
*** marun_ has quit IRC20:58
david-lyleperisteri: wasn't able to attend20:58
david-lylebut he want to point out the bp20:58
david-lylethere's a demo video as well20:58
TravTi just watched it20:59
TravTpretty interesting.20:59
david-lyleI think it makes perfect sense, may need some tweaking, but overall I have no problem with the concept20:59
TravTand some discussion should happen in context of searchlight as well20:59
david-lyleTravT: sure20:59
TravTi don't like that it is new functionality in legacy code, but that is a detail.20:59
*** mattfarina has quit IRC20:59
*** puranamr has quit IRC21:00
david-lyleand finally21:00
tqtranlol yeah, that means more work for us when we do decide to convert21:00
david-lyle#topic Themeing Additions (hurgleburgler)21:00
*** openstack changes topic to "Themeing Additions (hurgleburgler) (Meeting topic: Horizon)"21:00
david-lyletqtran: WHEN21:00
hurgleburgleryay!21:00
*** Networkn3rd has quit IRC21:00
tqtranwhen the fat lady sings21:00
hurgleburglerI've been doing some work using the new themeing functionality and hit a few bugs as well as some things that can be improved quite a bit21:01
r1chardj0n3sI think she's sung, it's time ;)21:01
*** Networkn3rd has joined #openstack-meeting-321:01
*** Networkn3rd has quit IRC21:01
hurgleburglerif I can get some eyes on the following21:01
hurgleburglerhttps://blueprints.launchpad.net/horizon/+spec/horizon-theme-templates21:01
hurgleburglerhttps://review.openstack.org/#/c/188162/21:01
hurgleburglerhttps://blueprints.launchpad.net/horizon/+spec/bootstrap-theme-preview21:01
hurgleburglerhttps://review.openstack.org/#/c/187818/21:01
hurgleburglerhttps://bugs.launchpad.net/horizon/+bug/145718821:01
hurgleburglerhttps://review.openstack.org/#/c/187797/21:01
openstackLaunchpad bug 1457188 in OpenStack Dashboard (Horizon) "Bootstrap variables overrides should only be default values" [Medium,In progress] - Assigned to Diana Whitten (hurgleburgler)21:01
*** matt-borland has left #openstack-meeting-321:01
r1chardj0n3swoah, link!21:01
tqtrandang calm down on the links21:01
david-lylethese are patches to make the theming we based of hurgleburgler earlier work, far more useful21:02
mrungethere's no need to click them all...21:02
david-lyleplease check it out21:02
david-lyles/it/them21:02
hurgleburglerThanks!21:02
david-lyleok, we're over. followup can be in the horizon room21:02
david-lyleThanks everyone!21:02
david-lyle#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Wed Jun  3 21:02:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-06-03-20.00.html21:02
*** ducttape_ has left #openstack-meeting-321:02
mrungethanks!21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-06-03-20.00.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-06-03-20.00.log.html21:02
david-lyleand who's filling in my availability d*mn it21:03
*** clu has quit IRC21:03
*** r1chardj0n3s has left #openstack-meeting-321:03
david-lylenvmd21:03
*** yanping has left #openstack-meeting-321:04
*** doug-fish has left #openstack-meeting-321:04
*** woodm19791 has left #openstack-meeting-321:04
*** clu_ has quit IRC21:04
*** pauloewerton has quit IRC21:05
*** puranamr has joined #openstack-meeting-321:07
*** mrunge has quit IRC21:10
*** sqchen has quit IRC21:13
*** ivar-lazzaro has quit IRC21:16
*** ivar-lazzaro has joined #openstack-meeting-321:17
*** mattgriffin has quit IRC21:18
*** ongk has left #openstack-meeting-321:20
*** sqchen has joined #openstack-meeting-321:20
*** alexsyip has quit IRC21:23
*** alexsyip has joined #openstack-meeting-321:26
*** hurgleburgler1 has joined #openstack-meeting-321:27
*** hurgleburgler has quit IRC21:28
*** baoli has quit IRC21:28
*** baoli has joined #openstack-meeting-321:29
*** hurgleburgler1 is now known as hurgleburgler21:31
*** banix has joined #openstack-meeting-321:34
*** peristeri has quit IRC21:38
*** bpokorny has quit IRC21:45
*** alexpilotti has joined #openstack-meeting-321:45
*** mwagner_afk has quit IRC21:49
*** mwagner_afk has joined #openstack-meeting-321:53
*** mattgriffin has joined #openstack-meeting-321:53
*** zz_natorious is now known as natorious21:53
*** bpokorny has joined #openstack-meeting-321:55
*** qwebirc38254 has quit IRC22:03
*** armax has joined #openstack-meeting-322:03
*** hurgleburgler1 has joined #openstack-meeting-322:08
*** hurgleburgler has quit IRC22:08
*** hurgleburgler1 is now known as hurgleburgler22:09
*** mwagner_afk has quit IRC22:16
*** singlethink has joined #openstack-meeting-322:17
*** singleth_ has quit IRC22:18
*** tqtran has quit IRC22:20
*** lhcheng has quit IRC22:25
*** bpokorny has quit IRC22:27
*** bpokorny has joined #openstack-meeting-322:27
*** VW_ has quit IRC22:27
*** Sukhdev has quit IRC22:29
*** sigmavirus24 is now known as sigmavirus24_awa22:30
*** banix has quit IRC22:31
*** banix has joined #openstack-meeting-322:32
*** jwy has left #openstack-meeting-322:35
*** singlethink has quit IRC22:36
*** singlethink has joined #openstack-meeting-322:36
*** banix has quit IRC22:38
*** shwetaap has quit IRC22:40
*** shwetaap has joined #openstack-meeting-322:41
*** VW has joined #openstack-meeting-322:41
*** VW_ has joined #openstack-meeting-322:43
*** VW_ has quit IRC22:43
*** VW_ has joined #openstack-meeting-322:43
*** singlethink has quit IRC22:44
*** VW has quit IRC22:45
*** barra204 has joined #openstack-meeting-322:48
*** VW_ has quit IRC22:48
*** shwetaap has quit IRC22:48
*** barra204 has quit IRC22:53
*** shwetaap has joined #openstack-meeting-322:54
*** bpokorny has quit IRC22:57
*** Sukhdev has joined #openstack-meeting-322:59
*** mattgriffin has quit IRC23:00
*** baoli has quit IRC23:01
*** carl_baldwin has quit IRC23:05
*** tqtran has joined #openstack-meeting-323:07
*** alexsyip has quit IRC23:21
*** banix has joined #openstack-meeting-323:25
*** sballe has quit IRC23:28
*** alexsyip has joined #openstack-meeting-323:28
*** Swami has joined #openstack-meeting-323:33
*** jrist has quit IRC23:34
*** VW has joined #openstack-meeting-323:35
*** bpokorny has joined #openstack-meeting-323:40
*** yamamoto has joined #openstack-meeting-323:40
*** VW has quit IRC23:44
*** jrist has joined #openstack-meeting-323:48
*** dims_ has joined #openstack-meeting-323:51
*** Yi_ has joined #openstack-meeting-323:54
*** dims__ has quit IRC23:55
*** ajmiller has quit IRC23:58

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