Wednesday, 2015-07-15

*** barra204 has quit IRC00:03
*** mickeys has quit IRC00:12
*** FallenPegasus has quit IRC00:12
*** woodster_ has quit IRC00:21
*** sridhar_ram1 is now known as sridhar_ram00:22
*** david-lyle has quit IRC00:25
*** sdake_ has joined #openstack-meeting-300:28
*** Swami has quit IRC00:28
*** sdake has quit IRC00:31
*** bitblt has quit IRC00:44
*** watanabe_isao has quit IRC00:45
*** baoli has joined #openstack-meeting-300:45
*** ivar-lazzaro has quit IRC00:50
*** ivar-lazzaro has joined #openstack-meeting-300:51
*** dims__ has quit IRC00:54
*** fitoduarte has quit IRC00:55
*** alexsyip has quit IRC01:03
*** sridhar_ram has quit IRC01:06
*** bpokorny has quit IRC01:16
*** puranamr has quit IRC01:18
*** puranamr has joined #openstack-meeting-301:20
*** jwang_ has quit IRC01:21
*** FallenPegasus has joined #openstack-meeting-301:23
*** bradjones has quit IRC01:26
*** dims_ has joined #openstack-meeting-301:28
*** bradjones has joined #openstack-meeting-301:30
*** bradjones has quit IRC01:30
*** bradjones has joined #openstack-meeting-301:30
*** puranamr has quit IRC01:30
*** puranamr has joined #openstack-meeting-301:30
*** puranamr has quit IRC01:30
*** puranamr has joined #openstack-meeting-301:31
*** stanzgy has joined #openstack-meeting-301:33
*** puranamr has quit IRC01:39
*** puranamr has joined #openstack-meeting-301:41
*** geoffarnold has quit IRC01:50
*** s3wong has quit IRC01:53
*** markvoelker has quit IRC01:54
*** geoffarnold has joined #openstack-meeting-301:54
*** markvoelker has joined #openstack-meeting-302:00
*** ivar-lazzaro has quit IRC02:01
*** zhenguo has joined #openstack-meeting-302:09
*** coolsvap|away has quit IRC02:10
*** yamahata has quit IRC02:10
*** kebray has joined #openstack-meeting-302:11
*** coolsvap|away has joined #openstack-meeting-302:12
*** david-lyle has joined #openstack-meeting-302:12
*** dims_ has quit IRC02:17
*** markvoelker has quit IRC02:18
*** puranamr has quit IRC02:18
*** yamamoto has joined #openstack-meeting-302:18
*** mmasaki has quit IRC02:26
*** mmasaki has joined #openstack-meeting-302:26
*** sdake_ is now known as sdake02:34
*** geoffarnold has quit IRC02:34
*** david-lyle has quit IRC02:35
*** sdake_ has joined #openstack-meeting-302:43
*** coolsvap has quit IRC02:45
*** sdake has quit IRC02:46
*** sdake__ has joined #openstack-meeting-302:46
*** baoli has quit IRC02:49
*** sdake_ has quit IRC02:50
*** Yi has joined #openstack-meeting-302:51
*** baoli has joined #openstack-meeting-302:52
*** sdake__ is now known as sdake02:58
*** dims_ has joined #openstack-meeting-303:19
*** Yi_ has joined #openstack-meeting-303:20
*** Yi has quit IRC03:23
*** dims_ has quit IRC03:23
*** Yi_ has quit IRC03:32
*** markvoelker has joined #openstack-meeting-303:35
*** stevemar has joined #openstack-meeting-303:36
*** mmasaki has quit IRC03:36
*** mmasaki has joined #openstack-meeting-303:37
*** david-lyle has joined #openstack-meeting-303:38
*** markvoelker_ has joined #openstack-meeting-303:38
*** Yi has joined #openstack-meeting-303:39
*** markvoelker has quit IRC03:40
*** Yi has quit IRC03:46
*** Poornima has joined #openstack-meeting-303:54
*** kebray has quit IRC03:59
*** kumar has joined #openstack-meeting-304:00
*** markvoelker has joined #openstack-meeting-304:04
*** puranamr has joined #openstack-meeting-304:07
*** markvoelker_ has quit IRC04:07
*** markvoelker_ has joined #openstack-meeting-304:08
*** markvoelker has quit IRC04:09
*** carl_baldwin has quit IRC04:10
*** puranamr_ has joined #openstack-meeting-304:11
*** puranamr has quit IRC04:13
*** mmasaki has quit IRC04:20
*** coolsvap|away is now known as coolsvap04:20
*** mmasaki has joined #openstack-meeting-304:21
*** sridhar_ram has joined #openstack-meeting-304:24
*** fifieldt has joined #openstack-meeting-304:28
*** Aish has joined #openstack-meeting-304:32
*** lazy_prince has joined #openstack-meeting-304:34
*** ajo has quit IRC04:35
*** ajo has joined #openstack-meeting-304:37
*** baoli has quit IRC04:39
*** baoli_ has joined #openstack-meeting-304:41
*** baoli_ has quit IRC04:44
*** puranamr_ has quit IRC04:47
*** Aish has quit IRC04:51
*** fitoduarte has joined #openstack-meeting-304:51
*** stevemar has quit IRC04:52
*** mrmartin has joined #openstack-meeting-304:55
*** Adri2000 has joined #openstack-meeting-305:00
*** yuikotakada has joined #openstack-meeting-305:04
*** markvoelker has joined #openstack-meeting-305:06
*** markvoelker_ has quit IRC05:06
*** sridhar_ram1 has joined #openstack-meeting-305:07
*** sridhar_ram has quit IRC05:08
*** markvoelker_ has joined #openstack-meeting-305:08
*** sridhar_ram2 has joined #openstack-meeting-305:09
*** sridhar_ram1 has quit IRC05:11
*** markvoelker has quit IRC05:11
*** adduarte has joined #openstack-meeting-305:13
*** FallenPegasus has quit IRC05:14
*** fitoduarte has quit IRC05:16
*** irenab has joined #openstack-meeting-305:24
*** Longgeek has joined #openstack-meeting-305:28
*** puranamr has joined #openstack-meeting-305:30
*** puranamr_ has joined #openstack-meeting-305:32
*** vineetmenon has joined #openstack-meeting-305:34
*** puranamr has quit IRC05:34
*** Sukhdev has joined #openstack-meeting-305:38
*** kebray has joined #openstack-meeting-305:41
*** kebray has quit IRC05:41
*** kebray has joined #openstack-meeting-305:42
*** kumar has quit IRC05:52
*** vineetmenon has quit IRC05:56
*** sridhar_ram2 has quit IRC05:56
*** Caleb-- has quit IRC06:19
*** belmoreira has joined #openstack-meeting-306:21
*** tobe has joined #openstack-meeting-306:28
*** mrunge has joined #openstack-meeting-306:28
*** mrunge has quit IRC06:28
*** puranamr_ has quit IRC06:30
*** Caleb-- has joined #openstack-meeting-306:30
*** sahid has joined #openstack-meeting-306:32
*** Poornima has quit IRC06:34
*** mrunge has joined #openstack-meeting-306:34
*** nkrinner_afk is now known as nkrinner06:35
*** mrunge has quit IRC06:40
*** mrunge has joined #openstack-meeting-306:45
*** adduarte has quit IRC06:58
*** Poornima has joined #openstack-meeting-307:00
*** yamamoto has quit IRC07:03
*** evgenyf has joined #openstack-meeting-307:03
*** stevemar has joined #openstack-meeting-307:03
*** sdake has quit IRC07:07
*** stevemar has quit IRC07:08
*** bouthors has joined #openstack-meeting-307:08
*** yamamoto has joined #openstack-meeting-307:09
*** bouthors has quit IRC07:13
*** mrmartin has quit IRC07:16
*** dims_ has joined #openstack-meeting-307:20
*** Longgeek has quit IRC07:23
*** zigo has quit IRC07:24
*** zigo has joined #openstack-meeting-307:25
*** dims_ has quit IRC07:26
*** wim_dc has joined #openstack-meeting-307:31
*** lazy_prince has quit IRC07:34
*** lazy_prince has joined #openstack-meeting-307:34
*** Sukhdev has quit IRC07:37
*** e0ne has joined #openstack-meeting-307:39
*** yushiro has joined #openstack-meeting-307:41
*** safchain has joined #openstack-meeting-307:49
*** kebray has quit IRC07:59
*** Longgeek has joined #openstack-meeting-308:00
*** yamamoto has quit IRC08:01
*** yushiro has quit IRC08:14
*** e0ne is now known as e0ne_08:16
*** yamamoto has joined #openstack-meeting-308:20
*** stendulker has joined #openstack-meeting-308:21
*** markvoelker_ has quit IRC08:21
*** e0ne_ is now known as e0ne08:22
*** egallen has joined #openstack-meeting-308:30
*** markvoelker has joined #openstack-meeting-308:36
*** markvoelker has quit IRC08:45
*** mickeys has joined #openstack-meeting-308:46
*** JeanBriceCombebi has joined #openstack-meeting-308:49
*** markvoelker has joined #openstack-meeting-308:51
*** markvoelker has quit IRC08:56
*** mickeys has quit IRC09:01
*** markvoelker has joined #openstack-meeting-309:06
*** btully has quit IRC09:08
*** markvoelker has quit IRC09:10
*** yamahata has joined #openstack-meeting-309:15
*** e0ne is now known as e0ne_09:15
*** e0ne_ is now known as e0ne09:16
*** yamahata has quit IRC09:20
*** markvoelker has joined #openstack-meeting-309:20
*** e0ne has quit IRC09:22
*** markvoelker has quit IRC09:25
*** markvoelker has joined #openstack-meeting-309:35
*** JeanBriceCombebi has quit IRC09:37
*** JeanBriceCombebi has joined #openstack-meeting-309:37
*** markvoelker has quit IRC09:40
*** JeanBriceCombebi has quit IRC09:42
*** JeanBriceCombebi has joined #openstack-meeting-309:44
*** markvoelker has joined #openstack-meeting-309:49
*** amotoki has quit IRC09:50
*** tobe has quit IRC09:54
*** markvoelker has quit IRC09:54
*** dims_ has joined #openstack-meeting-310:03
*** markvoelker has joined #openstack-meeting-310:04
*** dims_ has quit IRC10:05
*** markvoelker has quit IRC10:08
*** e0ne has joined #openstack-meeting-310:12
*** tobe has joined #openstack-meeting-310:17
*** yamamoto has quit IRC10:18
*** markvoelker has joined #openstack-meeting-310:19
*** mrmartin has joined #openstack-meeting-310:21
*** markvoelker has quit IRC10:23
*** e0ne is now known as e0ne_10:32
*** markvoelker has joined #openstack-meeting-310:33
*** markvoelker has quit IRC10:38
*** stendulker has quit IRC10:38
*** e0ne_ is now known as e0ne10:39
*** coolsvap is now known as coolsvap|away10:41
*** Yi has joined #openstack-meeting-310:43
*** e0ne has quit IRC10:46
*** markvoelker has joined #openstack-meeting-310:48
*** tobe has quit IRC10:48
*** e0ne has joined #openstack-meeting-310:50
*** stanzgy has quit IRC10:52
*** markvoelker has quit IRC10:54
*** robcresswell has joined #openstack-meeting-310:58
*** e0ne has quit IRC11:00
*** markvoelker has joined #openstack-meeting-311:02
*** e0ne has joined #openstack-meeting-311:04
*** egallen has quit IRC11:05
*** Yi_ has joined #openstack-meeting-311:06
*** markvoelker has quit IRC11:07
*** Yi__ has joined #openstack-meeting-311:07
*** Yi has quit IRC11:09
*** Yi_ has quit IRC11:10
*** Yi has joined #openstack-meeting-311:10
*** Yi__ has quit IRC11:11
*** e0ne has quit IRC11:13
*** yuikotakada has quit IRC11:15
*** Yi has quit IRC11:16
*** markvoelker has joined #openstack-meeting-311:17
*** baoli has joined #openstack-meeting-311:17
*** e0ne has joined #openstack-meeting-311:18
*** Yi has joined #openstack-meeting-311:21
*** markvoelker has quit IRC11:21
*** markvoelker has joined #openstack-meeting-311:24
*** openstack has joined #openstack-meeting-311:36
*** markvoelker has quit IRC11:37
*** e0ne is now known as e0ne_11:37
*** bradjones_ has joined #openstack-meeting-311:37
*** bradjones_ has quit IRC11:37
*** bradjones_ has joined #openstack-meeting-311:37
*** alex_xu_ has joined #openstack-meeting-311:37
*** Yi has quit IRC11:37
*** melwitt_ has joined #openstack-meeting-311:37
*** bradjones_ is now known as bradjones11:37
*** ChanServ sets mode: +o openstack11:37
*** alex_xu_ has quit IRC11:37
*** alex_xu_ has joined #openstack-meeting-311:37
*** openstackstatus has joined #openstack-meeting-311:38
*** ChanServ sets mode: +v openstackstatus11:38
*** markvoelker has joined #openstack-meeting-311:39
*** Yi has joined #openstack-meeting-311:39
*** e0ne_ is now known as e0ne11:39
*** markvoelker has quit IRC11:44
*** Yi has quit IRC11:44
*** dims_ has joined #openstack-meeting-311:47
*** masco__ has joined #openstack-meeting-311:49
*** markvoelker has joined #openstack-meeting-311:54
*** ramitsurana has joined #openstack-meeting-311:54
*** Yi has joined #openstack-meeting-311:55
*** Yi has quit IRC11:55
*** egallen has joined #openstack-meeting-311:56
*** yamamoto has joined #openstack-meeting-311:58
*** markvoelker has quit IRC11:58
*** puranamr has joined #openstack-meeting-311:58
*** qwebirc6184 has joined #openstack-meeting-311:59
*** yamamoto has quit IRC12:02
*** markvoelker has joined #openstack-meeting-312:08
*** puranamr has quit IRC12:11
*** JeanBriceCombebi has quit IRC12:11
*** markvoelker has quit IRC12:13
*** JeanBriceCombebi has joined #openstack-meeting-312:14
*** qwebirc34032 has joined #openstack-meeting-312:15
*** qwebirc6184 has quit IRC12:15
*** tobe has joined #openstack-meeting-312:15
*** tobe has quit IRC12:18
*** stevemar has joined #openstack-meeting-312:18
*** tobe has joined #openstack-meeting-312:19
*** bouthors has joined #openstack-meeting-312:21
*** markvoelker has joined #openstack-meeting-312:23
*** stevemar has quit IRC12:23
*** tobe has quit IRC12:24
*** Poornima has quit IRC12:26
*** markvoelker has quit IRC12:28
*** woodster_ has joined #openstack-meeting-312:30
*** markvoelker has joined #openstack-meeting-312:37
*** qwebirc34032 has quit IRC12:41
*** dims_ has quit IRC12:41
*** JeanBriceCombebi has quit IRC12:41
*** JeanBriceCombebi has joined #openstack-meeting-312:41
*** markvoelker has quit IRC12:42
*** Yi has joined #openstack-meeting-312:44
*** masco_ has joined #openstack-meeting-312:48
*** Yi has quit IRC12:50
*** masco__ has quit IRC12:51
*** JeanBriceCombebi has quit IRC12:51
*** markvoelker has joined #openstack-meeting-312:52
*** neelashah has joined #openstack-meeting-312:54
*** markvoelker has quit IRC12:56
*** Yi has joined #openstack-meeting-312:58
*** yamamoto has joined #openstack-meeting-312:59
*** jaypipes has joined #openstack-meeting-312:59
*** Aish has joined #openstack-meeting-313:00
*** julim has joined #openstack-meeting-313:00
*** markvoelker has joined #openstack-meeting-313:01
*** yamamoto has quit IRC13:03
*** Aish has quit IRC13:05
*** dims_ has joined #openstack-meeting-313:06
*** markvoelker has quit IRC13:09
*** markvoelker has joined #openstack-meeting-313:09
*** markvoelker_ has joined #openstack-meeting-313:10
*** JeanBriceCombebi has joined #openstack-meeting-313:14
*** markvoelker has quit IRC13:14
*** krtaylor has joined #openstack-meeting-313:16
*** baoli has quit IRC13:20
*** peristeri has joined #openstack-meeting-313:22
*** Yi has quit IRC13:22
*** peristeri has quit IRC13:27
*** shwetaap has joined #openstack-meeting-313:27
*** peristeri has joined #openstack-meeting-313:28
*** ttrifonov is now known as zz_ttrifonov13:31
*** lblanchard has joined #openstack-meeting-313:34
*** Piet has quit IRC13:38
*** jpomero has joined #openstack-meeting-313:43
*** btully has joined #openstack-meeting-313:44
*** bknudson has joined #openstack-meeting-313:44
*** terrylhowe has joined #openstack-meeting-313:45
*** stevemar has joined #openstack-meeting-313:52
*** vikram has joined #openstack-meeting-313:56
*** moshele has joined #openstack-meeting-313:56
*** Ramanjaneya has joined #openstack-meeting-313:57
*** mohankumar has joined #openstack-meeting-313:58
*** jckasper has quit IRC13:59
*** jckasper has joined #openstack-meeting-313:59
*** daniel_ has joined #openstack-meeting-314:00
*** Piet has joined #openstack-meeting-314:00
*** gcossu has joined #openstack-meeting-314:00
*** ihrachyshka has joined #openstack-meeting-314:00
*** njohnston has joined #openstack-meeting-314:01
ajoping vikram , irenab , ihrachyshka ,14:01
irenabajo: hey14:02
ajoshall we have meeting today, or do we stay in-code?14:02
vikramajo:hi14:02
moshelehi14:02
RamanjaneyaHi14:02
ajoI was so depth in reviews and code that I forgot14:02
gcossuhi14:02
ajoI know you had an etherpad14:02
*** njohnston has quit IRC14:02
mohankumarHi all14:02
ajomoshele,14:02
irenabajo: short status update will be helpful14:02
*** egallen has quit IRC14:02
ihrachyshkao/14:02
*** egallen has joined #openstack-meeting-314:02
*** njohnston has joined #openstack-meeting-314:03
ihrachyshkaI'm for status update at least14:03
ihrachyshkaand anything people have to discuss/ask outside of their trenches14:03
ajook14:03
*** gsagie has joined #openstack-meeting-314:03
ajo#startmeeting neutron_qos14:03
openstackMeeting started Wed Jul 15 14:03:30 2015 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:03
openstackThe meeting name has been set to 'neutron_qos'14:03
ajo#topic status update from the trenches14:03
*** openstack changes topic to "status update from the trenches (Meeting topic: neutron_qos)"14:03
*** Vichoward has joined #openstack-meeting-314:04
ajoSo, we're advancing a bit slow, but it's nice to see more testing coming from all directions14:04
ajoand more patched merged.14:04
ajoStill, the important ones are taking more time than expected,14:04
ihrachyshkayeah, I shout "service plugin!!"14:05
ihrachyshkabut hopefully, we'll get it today. I'll do everything for that14:05
ajoand we just found that using the callbacks to extend introduced a DBDeadlock, we're partly lucky that it was triggered twice in a row14:05
ajodigging into mixinless core-resource extension14:06
ajowe also found that relying directly on callbacks is a messy mechanism14:06
mosheleajo: this is the etherpad for qos sync https://etherpad.openstack.org/p/qos-sync I think echo one should add his tasks so we can keep track on everything14:06
ajoand we must provide a better interface, similar to ml2 extension drivers, but more for the general neutron, I talked with mkolesni about it... not to be fully done for neutron now, that needs broader discussion,14:06
*** jckasper has quit IRC14:07
ajobut he will do something in the middle, which can be consumed by the ML2 extension drivers (with an adaptor) and by other plugins14:07
irenabajo: can you clarify this one?14:07
ihrachyshkamoshele, ok, I'll update the etherpad. I didn't know about that one14:07
ajo#link https://etherpad.openstack.org/p/qos-sync14:07
ajosure irenab ,14:07
ajolet me explain the thing14:07
*** adityav has joined #openstack-meeting-314:08
mosheleihrachyshka: thanks14:08
ajoextending a core resource, doing it with louse coupling, requires "something" to handle a few things14:08
*** peristeri has quit IRC14:08
ajo1) extending the core resource attributes (what we already do with AFTER_READ)14:08
irenabsometing  = plugin that handles the esource extenision, right14:09
irenabresource14:09
ajo2) tracking core resource updates to keep track of such extended atrtibutes in DB14:09
ajoin this case , the bindings to policies of networks and ports14:09
ajoyes, in this case14:09
ajoresource = networks / ports14:09
ajoand something (right now) is the service plugin14:09
ajoafter looking at...14:10
ajothe ml2 extension drivers, let me link to int14:10
ajoint->it14:10
*** jlibosva has joined #openstack-meeting-314:11
ajo#link https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/driver_api.py#L89314:11
ajoafter looking to that,14:11
ajoan example is this:14:11
ajohttps://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/extensions/port_security.py14:11
ajothey're basically doing that, but only within ml214:11
gcossunice link14:11
irenabajo: what I am missing is what is not already handled by current implementation14:12
ajobasically, they came to almost the same interface we're finally exposing in the service, via callbacks14:12
irenabWe skip ML2 extension, since resource is extended by qos plugin14:12
*** sigmavirus24_awa is now known as sigmavirus2414:12
irenabajo: so what you want is to add Resource extension interface?14:13
irenabto be implemented by QoS plugin?14:13
ajomkolesni is thinking about generalizing the resource extension, and decouple that from the plugin14:13
ajofor now, he's going to provide that in the same file,14:13
ajoand make it available to all plugins14:13
ajoso you have a common class to call from your plugin14:13
ajoto update_network/port create_network/port14:13
ajoand get the bindings done/undone14:13
ajoand also, put the dict extension in that class14:14
irenabajo: the rational to eanble ML2 to call QoS plugin via this interface?14:14
ajoirenab: create a ml2 extension which will call this class14:14
ajoand other plugins, can call this class14:14
ajoat a later time, in neutron14:15
ajowe will need to find the right way for plugins not needing to do such thing14:15
ajo(manually)14:15
ajojust say "I support this resource extension", yey...14:15
irenabajo: I think you jump into technical details before explaining what you want to solve :-)14:15
ajoirenab, it's mike idea's actually, I was refusing to listen this morning, but he's so convincing...14:16
ajoand I believe he's right14:16
mosheleI feel we need another code sprint :)14:16
ihrachyshkaajo, why isn't he on the meeting?14:16
irenabWhat is missing with current callback AFTER_READ?14:16
ihrachyshkahe should have convinced all of us!14:16
ajohe just wants to move all the resource extension/extension tracking out of the class14:16
ajointo a separate one14:16
ajoI think that's neat, and ends in a cleaner plugin14:17
ajoand it's something we can reuse neutron wide later14:17
irenabajo: the change that was done for ML2Plugin is absolutly no-go14:17
ajobut one step at a time14:17
ajoirenab: correct14:17
irenabso I assumed we trying to resolve this14:17
ajocorrect14:17
ajothis, and more :)14:17
ajoas we solve this, we want to clean up the way we extend resources14:18
ihrachyshkaajo, can we take more of this and less of more?14:18
irenablso to resolve this (without more) what is missing?14:18
ihrachyshkairenab, I like your 'result first' approach14:18
irenabihrachyshka: :-)14:18
*** yamahata has joined #openstack-meeting-314:18
irenabmore of: lets keep focused14:18
ihrachyshkaI'm fine with good design as long as we stick to schedule (that we don't have, and I blame our Lord Miguel for not guiding us!)14:19
ajoI agree, I couldn't convince mkolesni to do less of more, but I convinced him to do something very thin14:19
irenabajo: ca you share the plan, I still do not understand what was missing so it required to “polute” ML2 plugin14:19
ajoirenab, you will see it in next patch.14:20
ihrachyshkayes, please make communication explicit. you talk via phone, you have chats in redhat irc...14:20
ajobasically it's putting the relevant parts of the ml2 extension driver available in qos_plugin14:20
ihrachyshkaand then it's not clear what's going on14:20
ajohe's just going to move functions, not reinvent the world14:20
irenabajo: can you still explain the problem,  will see the solution in the patch :-)14:20
ajothe problem is, we planned to use callbacks for all this,14:21
ajoand callbacks are not suitable for this as they are today14:21
ajoonly the AFTER_READ part is ok14:21
ajoand still we will move that in a separate interface14:21
ajotracking the resources via AFTER_UPDATE AFTER_CREATE for ports14:21
ajodoes not work, because it's too tied to ml2 (those callbacks are only called from ml2)14:22
ajowell14:22
ajosome of them, some other don't exist14:22
ajosince14:22
*** Yi_ has joined #openstack-meeting-314:22
ajothe plan was to use callbacks temporarily, until we had the definitive solution from armax to "resource extension"14:22
irenabajo: initially we discussed that qos extension has two parts : policy management and port/net association.14:22
*** peristeri has joined #openstack-meeting-314:23
ajocorrect14:23
ajois the port/net association14:23
*** sdake has joined #openstack-meeting-314:23
ajoand dissociation14:23
ajothe pain point14:23
irenabif we split this in two extensions and make ML2 extension for second, this will be the ML2 way14:23
ajoirenab: I don't follow14:24
ajowe want something that works for all , not ml2 only14:24
gsagieso the call backs are called from the db layer?14:25
irenabajo: I agree, but this looks like complicating the flow14:25
ajoit's harder to discuss than to implement14:25
*** jreeves has joined #openstack-meeting-314:25
ajobasically it's the same we have scinded to a separate class14:25
ihrachyshkairenab, ok, the problem seems to be clear; let's now give them one day to see the solution14:26
ajojust a few methods moved out to another class, not inside the plugin itself all together14:26
ihrachyshkaajo, will it be up for review tomorrow?14:26
ajoyeah, I will push mkolesni to show us his work by tomorrow14:26
ihrachyshkagood, push is the right word14:26
irenabihrachyshka: +1, we can always fallback for ML2 Extension of net/port qos association to call into Qo plugin14:26
ihrachyshkairenab, yeah, as long as we don't start to fallback one day before merge :)14:27
ajoihrachyshka, that's my point14:27
ihrachyshkathat's why we need to move quickly and get solution up tomorrow14:27
ajoI don't want to change directions14:27
ihrachyshkaajo, when do you leave for PTO?14:27
ajonext week I'm out, but I'll dedicate 30m-1h daily14:27
ajofor mail, and reviews14:28
irenabajo: sometimes better change than keep digging :-)14:28
ajoand probably irc14:28
ihrachyshkaajo, good. we'll try to limit pings14:28
ajoirenab, I have limited the dig depth, if I left mkolesni alone he'd rewrite the whole callbacks :D :P :)14:28
*** markvoelker has joined #openstack-meeting-314:28
ihrachyshkaajo++ for staying online on PTO for emergencies14:28
ihrachyshkaajo, yeah, those Java guys...14:29
ajoirenab, if we find it getting too complicated for some other reasons, I agree, falling back to a simple ml2 extension would be good14:29
ajoand then next cycle can be used for doing something more general14:29
gsagieits important to see how a plugin adds this support14:29
*** absubram has joined #openstack-meeting-314:29
irenabajo: fine, this mwill require spliiting qos extension into two, but generally simple14:29
ajoirenab, splitting in two?14:30
ajogsagie, yes we will need to document that14:30
irenabextensions/qos.py to split14:30
ajoirenab: I don't follow :)14:30
irenabajo: we can take it offline in case will be needed14:30
*** absubram has quit IRC14:31
ihrachyshkacan we move forward with the topic? I think we are stuck on that Mike's patch, and we have ETA and plan for it already. And yeah, the way we will rewrite stuff when in master.14:31
*** markvoel_ has joined #openstack-meeting-314:31
*** markvoelker has quit IRC14:31
irenabI just mentioned the code change that will be required to make ML2 extension fallback14:31
*** absubram has joined #openstack-meeting-314:31
ihrachyshkairenab, you can try to describe the idea in email maybe. I also don't follow.14:31
irenabihrachyshka: fine, will do it14:32
*** markvoelker_ has quit IRC14:32
ihrachyshkaany other high prio patches?14:32
ihrachyshkaif not, I vote for rules inside policies one from me: https://review.openstack.org/20060814:32
ihrachyshkaajo, eagarly waiting for review ;)14:32
irenabajo: want to update on cli apprach?14:32
ihrachyshkaajo, once we will have +2 from you, it should be easier to get another one14:33
ajoyes, that patch is important14:33
ajoplease review14:33
* ajo <- please, review!14:33
*** markvoel_ has quit IRC14:33
ajoabout CLI14:33
ajowe found a stopper for using a common qos-create-rule / qos-update-rule14:34
ajoif we provide <type> after that,14:34
*** masco_ has quit IRC14:34
ajowe have not found a sane way to provide different arguments per rule in neutron-client14:34
ajoso14:34
ajothe call is to have a separate create/update per rule14:34
ajoso we may have14:34
ajoqos-create-bandwidth-limit-rule14:34
ajoqos-update-bandwidth-limit-rule14:34
ihrachyshkaajo, is it just for help message sake?14:35
ajoqos-{create, update}-<type>-rule for every rule type14:35
ajoihrachyshka, also for argument parsing14:35
ihrachyshkaajo, because afaik passing random --options should still work14:35
ajowe don't want to accept a ton of optional arguments, where some are not really optional for some rule types14:35
gcossuihrachyshka: I'll try to review https://review.openstack.org/20060814:35
ihrachyshkagcossu, thanks14:36
*** masco_ has joined #openstack-meeting-314:36
ihrachyshkafor cli, I'm fine and don't mind. any new rule type will require a patch for neutronclient anyway.14:36
ajoyes14:36
ajothat's correct14:36
ihrachyshkaand if the approach simplifies things, I'm good14:36
ajoand every rule type has a different URL path14:36
ajoit will be weird, btw, that...14:37
ajoqos-rule-delete, qos-rule-show, will need to specify rule type14:37
Vichowardif it simplifies i'm okay with it also14:37
ihrachyshkaajo, ouch, that's a bit weird indeed14:37
irenabajo: no, no need for rule type14:37
ihrachyshkaideally, id is enough14:37
ajoirenab, how then do you point it to the right api url?14:38
ajoqos/policy/<policy-uid>/<rule-type>/<rule-uuid> ?14:38
irenabajo: hope vikram can clarify14:38
*** sadasu has joined #openstack-meeting-314:38
irenabmaybe you right, lets see14:38
ajoI've seen that other services (lbaasv2) solves that by exposing "rules" at a lower level14:39
ajothey have that in monitor or heartbeats or something like that14:39
ajoso you can just do14:39
ajoqos/rule/<uuid> for some operations14:39
ajobut...14:40
ihrachyshkayeah, that simplifies cli but makes API inconsistent a bit14:40
ajocorrect14:40
ajowe can just do a first version, and refine over time14:40
ajowe're experimental14:40
ajoso it should be ok14:40
ajoonce done, we may make the odds exposed and discussed IMHO14:40
ihrachyshkaok, let's do the simple form even if it requires --type14:41
*** mickeys has joined #openstack-meeting-314:41
ajoif having a less beautiful API makes CLI people happier, I'm ok with that14:41
ajoother option, could be ... being able to discover the rule type14:41
ajoby looking at the policy14:41
ajoso we , in two calls, read the policy, ... find what's the category of the rule, then... kill the rule14:42
ajoor then show the rule14:42
ajoand then we don't need to provide type14:42
ajowe already do a lookup when somebody passes the policy name, instead of the policy id14:42
ajoirenab, vikram , thoughts?14:42
ajod14:42
ajodevil is in the details..14:43
gcossu:)14:43
*** masco_ has left #openstack-meeting-314:43
ihrachyshkalet's have simple thing first. then go into UX14:43
ajo+114:43
irenabfor me it looks doable, but I have very limited knowledge on cli implementation14:43
ajoI'd then just stick to providing the type for now, may be later we can make it optional by auto-discovert14:44
ajodiscovery14:44
ihrachyshkathere is another thing that is overdue: devref that we said before will be somehow ready for Wed: https://review.openstack.org/201536 and followups14:44
ihrachyshkaajo, what's the plan here?14:44
* ajo plans to duplicate himself :)14:45
ihrachyshkaI know it seems like it's not a big deal since it's not code, but I believe it's a must for merge-back, and the earlier we start to document stuff, the better14:45
ajoyes14:45
ihrachyshkaajo2 = copy.copy(ajo)14:45
ajoit's a very expensive operation14:45
ihrachyshkaajo, do you need any help with that?14:45
ajolast two copies still taking too many resources, instead of producing14:45
ihrachyshkaajo, you're not that huge14:46
ajo':D14:46
ihrachyshkaso, any help?14:46
ihrachyshkaI think I'm better in writing than coding, so14:46
ajoif you can address current comments, and join to your other patch14:46
ajoI think gsagie was doing something too14:47
ajoI'd really thank you14:47
ajowhile I keep tackling the plugin towards merge...14:47
ihrachyshkaok14:47
ajothanks -as usual-14:47
ihrachyshkaany more critical pieces?14:47
ajogsagie, did you have time to look into the devref of your pieces?14:47
*** adityav has quit IRC14:48
ajoihrachyshka, I will respond to comments14:48
ajoso you can update the parts I'm more aware correctly14:48
*** sinval has quit IRC14:48
*** absubram has quit IRC14:48
* ajo looks again for the list of patches..14:48
*** jasondotstar has joined #openstack-meeting-314:49
mosheleajo: for full flow with ovs agent we need this 2 to merge https://review.openstack.org/#/c/201975/ https://review.openstack.org/#/c/201583/14:49
gsagieajo: not yet14:49
ajoahm nice, I wil check your update moshele , thanks14:49
*** sbalukoff has quit IRC14:49
*** terrylhowe has left #openstack-meeting-314:49
ihrachyshkamoshele, I see the 1st one -1's on jenkins14:49
mosheleajo: my patch is failing becuase a bug in the ovs driver which gsagie fixed https://review.openstack.org/#/c/201583/14:50
ihrachyshkaah, there is order involved14:50
*** JeanBriceCombebi has quit IRC14:50
ajoah, ok14:50
ajolet's make a comment on the other14:50
ihrachyshkamoshele, can you rebase on gsagie's?14:50
ihrachyshkamoshele, I've sent it to gate, but it will buy us several hours14:51
ajomoshele, I can rebase it if you want14:51
mosheleajo: yes please14:51
ajoack, I will14:51
ihrachyshkaajo, make sure not to rebase the Gal's one :)14:51
ajoyep14:51
ajook, any more critical pieces ?14:52
ihrachyshkaajo, we may also +A https://review.openstack.org/#/c/202119/14:52
ihrachyshkabut that's not critical :)14:52
ihrachyshkathough I will be more happy to see less patches in the queue :)14:53
*** markvoelker has joined #openstack-meeting-314:53
ajodone14:53
ajoihrachyshka, should we wait for jenkins before +A ?14:53
ihrachyshkaok, I think we can go back to trenches?14:53
ihrachyshkaajo, I think no14:53
ajook, I never got the logic of that14:53
ihrachyshkaajo, at least that's what I see from what zuul does14:53
mosheleajo: get_info rpc will return version object or dict in  the current implementation (I know it should be object at the end)?14:53
*** FallenPegasus has joined #openstack-meeting-314:53
ajoihrachyshka, may be it was necessary back in time14:54
ajomoshele, it should be object in the end, but the current dict usage may work14:54
ajoihrachyshka, we made them dict-compatible for now, right?14:54
*** markvoelker_ has joined #openstack-meeting-314:54
ihrachyshkaajo, well... they are similar, but not identical to dict. you can call .to_dict() to get the real one14:55
ihrachyshkathough I'm not sure where we are in terms of serialization14:55
mosheleajo: for know for the server-> agent flow to work we need dict14:55
*** JeanBriceCombebi has joined #openstack-meeting-314:56
mosheleknow -.> flow14:56
mosheleihrachyshka: I think we need to convert to dict in registry.get_info14:57
mosheleihrachyshka: just for now to make it work14:57
ihrachyshkamoshele, I'm fine either way. we'll get objects later.14:58
*** markvoelker has quit IRC14:58
mosheleok14:58
ihrachyshkado whatever you need to integrate agent side :)14:58
ajomoshele, you can access the objects as dicts14:58
ajothey will work14:58
ajojust for sending over wire you may need to use the functions I pointed this morning14:58
*** vineetmenon has joined #openstack-meeting-314:58
ajook https://review.openstack.org/#/c/201975/ rebased14:59
ajo#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Jul 15 14:59:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-07-15-14.03.html14:59
ihrachyshkao/14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-07-15-14.03.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-07-15-14.03.log.html14:59
ihrachyshkakeep up!14:59
*** jckasper has joined #openstack-meeting-314:59
ajoyeah14:59
irenabbye14:59
gcossubye15:00
*** moshele has left #openstack-meeting-315:00
*** yamahata has quit IRC15:02
*** galstrom_zzz is now known as galstrom15:02
*** yamahata has joined #openstack-meeting-315:03
*** JeanBriceCombebi has quit IRC15:05
*** sarkarsu has joined #openstack-meeting-315:06
*** sarkarsu has quit IRC15:07
*** jlibosva has left #openstack-meeting-315:07
*** gsagie has left #openstack-meeting-315:09
*** bpokorny has joined #openstack-meeting-315:12
*** yamahata has quit IRC15:12
*** yamahata has joined #openstack-meeting-315:12
*** lsmola has quit IRC15:13
*** carl_baldwin has joined #openstack-meeting-315:17
*** zhenguo has quit IRC15:23
*** vineetmenon has quit IRC15:25
*** vineetmenon has joined #openstack-meeting-315:25
*** iben has joined #openstack-meeting-315:27
*** puranamr has joined #openstack-meeting-315:30
*** peristeri has quit IRC15:31
*** sdake has quit IRC15:32
*** sdake has joined #openstack-meeting-315:32
*** e0ne is now known as e0ne_15:36
*** iben has quit IRC15:37
*** ig0r__ has quit IRC15:39
*** ig0r_ has joined #openstack-meeting-315:40
*** ajmiller has joined #openstack-meeting-315:40
*** sridhar_ram has joined #openstack-meeting-315:43
*** daniel_ has quit IRC15:44
*** zz_natorious is now known as natorious15:44
*** e0ne_ is now known as e0ne15:45
*** peristeri has joined #openstack-meeting-315:46
*** vikram has quit IRC15:46
*** natorious is now known as zz_natorious15:46
*** belmoreira has quit IRC15:48
*** Poornima has joined #openstack-meeting-315:49
*** galstrom is now known as galstrom_zzz15:51
*** ajmiller has quit IRC15:52
*** ajmiller has joined #openstack-meeting-315:52
*** Aish has joined #openstack-meeting-315:53
*** armax has joined #openstack-meeting-315:56
*** lazy_prince has quit IRC15:57
*** jaypipes has quit IRC15:58
*** salv-orl_ has joined #openstack-meeting-316:01
*** amotoki has joined #openstack-meeting-316:02
*** robcresswell has left #openstack-meeting-316:02
*** vineetmenon has quit IRC16:03
*** Sukhdev has joined #openstack-meeting-316:03
*** ajmiller has quit IRC16:03
*** salv-orlando has quit IRC16:05
*** sdake has quit IRC16:08
*** evgenyf has quit IRC16:09
*** egallen has quit IRC16:10
*** sdake has joined #openstack-meeting-316:11
*** gcossu has left #openstack-meeting-316:13
*** krtaylor has quit IRC16:15
*** ramit_surana has joined #openstack-meeting-316:17
*** ramitsurana has quit IRC16:17
*** tpatil has joined #openstack-meeting-316:18
*** bradjones has quit IRC16:20
*** mrda-away has quit IRC16:20
*** bradjones has joined #openstack-meeting-316:20
*** bradjones has quit IRC16:20
*** bradjones has joined #openstack-meeting-316:20
*** mrda-away has joined #openstack-meeting-316:20
*** puranamr has quit IRC16:21
*** stevemar has quit IRC16:22
*** stevemar has joined #openstack-meeting-316:23
*** puranamr has joined #openstack-meeting-316:24
*** vineetmenon has joined #openstack-meeting-316:25
*** Poornima has quit IRC16:25
*** stevemar has quit IRC16:27
*** krtaylor has joined #openstack-meeting-316:28
*** sahid has quit IRC16:34
*** jckasper has quit IRC16:36
*** markvoelker_ has quit IRC16:40
*** markvoelker has joined #openstack-meeting-316:42
*** s3wong has joined #openstack-meeting-316:45
*** melwitt_ is now known as melwitt16:49
*** amotoki has quit IRC16:50
*** sbalukoff has joined #openstack-meeting-316:51
*** JeanBriceCombebi has joined #openstack-meeting-316:51
*** hichihara has joined #openstack-meeting-316:52
*** ajmiller has joined #openstack-meeting-316:53
*** ajmiller_ has joined #openstack-meeting-316:54
*** ajmiller__ has joined #openstack-meeting-316:55
*** ramit_surana has quit IRC16:55
*** jreeves has quit IRC16:56
*** yamahata has quit IRC16:57
*** ajmiller__ has quit IRC16:57
*** ajmiller__ has joined #openstack-meeting-316:57
*** yamahata has joined #openstack-meeting-316:58
*** ajmiller_ has quit IRC16:59
*** ajmiller has quit IRC16:59
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Jul 15 17:00:15 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 today?17:00
melwitto/17:00
alaskiheh, going to be quick today17:01
alaski#topic Tempest testing17:01
*** openstack changes topic to "Tempest testing (Meeting topic: nova_cells)"17:01
dansmitho/17:01
alaskimelwitt: anything newsworthy on testing?17:01
melwittalaski: nope. things are in the same state goo.gl/b7R8wq (stable) except for the gate issues yesterday17:02
alaskigreat17:02
*** vineetmenon has quit IRC17:02
alaskimelwitt: you mean the issue that was reverted, right?17:02
*** bouthors_ has joined #openstack-meeting-317:03
melwittalaski: yes, I think so17:03
alaskiokay17:03
alaskiif you aren't aware of anything specific that's different we'll assume it's that17:04
alaski#topic Specs17:04
*** openstack changes topic to "Specs (Meeting topic: nova_cells)"17:04
alaskinothing here except to say that at this point it's probably too late to open more17:04
alaskibut there is still work to be done on open specs17:04
alaski#topic open discussion17:05
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"17:05
*** vineetmenon has joined #openstack-meeting-317:05
alaskiI'm going to recommend that we skip this meeting next week17:05
dansmithum, yeah17:05
alaskiif someone objects and wants to run the meeting that's fine, otherwise we'll skip17:05
melwittI'm +1 on skipping17:06
alaskicool17:06
alaskiI've been sidetracked for a bit on internal work but am finally starting to get back to some coding for cells17:07
alaskiit's quite unfortunate that it's this late and I'm just getting back to it17:07
vineetmenon+117:07
vineetmenonjust one comment..17:07
*** hichihara has quit IRC17:07
*** ihrachyshka has quit IRC17:07
vineetmenonbelmiro has uploaded first patch for flavors bp17:07
vineetmenonbelmoreira, ^17:08
alaski#link https://review.openstack.org/#/c/201606/217:08
alaskiI saw that go up, but haven't looked closely at it yet17:08
vineetmenonthanks alaski17:08
melwittyeah, I'm not sure what I can do right now. the db connection switching bp was approved recently and I'll refresh Dheeraj's patch on that and add to it. other than that, I don't know17:08
vineetmenonfor the link17:08
*** yamahata has quit IRC17:09
alaskimelwitt: a lot of the work was going to be around scheduling and the instance boot flow, but that's been stuck behind request spec object work17:09
*** ajmiller__ is now known as ajmiller17:10
*** sigmavirus24 is now known as sigmavirus24_awa17:10
alaskiI'm working on the persistence side of that now, but the object is still up for review17:10
alaskithis series https://review.openstack.org/#/c/145528/17:10
*** sballe has joined #openstack-meeting-317:10
melwittalaski: right. I should review that. what about the cells conductor, is that considered part of scheduling?17:11
alaskisort of17:11
alaskithe work can be done independently, but assumes the object is there17:11
melwittokay17:11
alaskiso it will be harder to test, but could be coded17:11
*** s3wong has quit IRC17:12
alaskimelwitt: do you want to get started on that?17:12
alaskianything else anyone wants to discuss today?17:14
melwittalaski: oh, I was just asking to get more idea of how things fit together. since nothing is existing yet. I'd be interested but to be honest not sure I'd know what to do about it yet17:14
alaskimelwitt: okay, let me see where I can get to this week on the spec object and we can talk next week17:15
melwittalaski: okay, cool17:15
*** shwetaap1 has joined #openstack-meeting-317:15
alaskiseems like there's nothing else17:15
alaskithanks everyone17:15
alaski#endmeeting17:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:16
openstackMeeting ended Wed Jul 15 17:15:59 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-07-15-17.00.html17:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-07-15-17.00.txt17:16
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-07-15-17.00.log.html17:16
vineetmenonciao17:16
*** vineetmenon has quit IRC17:16
*** tsandall has quit IRC17:16
*** Yi_ has quit IRC17:16
*** shwetaap has quit IRC17:16
*** banix has joined #openstack-meeting-317:18
*** Aish has quit IRC17:18
*** rockyg has joined #openstack-meeting-317:18
*** rockyg has left #openstack-meeting-317:21
*** stevemar has joined #openstack-meeting-317:23
*** ajmiller_ has joined #openstack-meeting-317:25
*** ajmiller__ has joined #openstack-meeting-317:26
*** ajmiller has quit IRC17:26
*** stevemar has quit IRC17:28
*** Yi has joined #openstack-meeting-317:28
*** ajmiller_ has quit IRC17:29
*** kebray has joined #openstack-meeting-317:33
*** yamahata has joined #openstack-meeting-317:33
*** JeanBriceCombebi has quit IRC17:34
*** jaypipes has joined #openstack-meeting-317:35
*** ivar-lazzaro has joined #openstack-meeting-317:40
*** bouthors_ has quit IRC17:42
*** bouthors has quit IRC17:43
*** ivar-laz_ has joined #openstack-meeting-317:44
*** sridhar_ram has left #openstack-meeting-317:44
*** bauzas has quit IRC17:46
*** ivar-lazzaro has quit IRC17:47
*** ajmiller__ is now known as ajmiller17:49
*** bauzas has joined #openstack-meeting-317:50
*** salv-orl_ has quit IRC17:50
*** kebray has quit IRC17:54
*** sridhar_ram1 has joined #openstack-meeting-317:54
*** bouthors_ has joined #openstack-meeting-317:54
*** bouthors has joined #openstack-meeting-317:54
*** puranamr has quit IRC17:56
*** bouthors__ has joined #openstack-meeting-317:56
*** Swami has joined #openstack-meeting-317:58
*** egallen has joined #openstack-meeting-317:58
*** jwarendt has joined #openstack-meeting-317:59
*** stevemar has joined #openstack-meeting-317:59
*** bpokorny_ has joined #openstack-meeting-318:01
*** mickeys has quit IRC18:01
*** puranamr has joined #openstack-meeting-318:02
*** bouthors__ has quit IRC18:03
*** Sukhdev has quit IRC18:03
*** bouthors has quit IRC18:04
*** bpokorny has quit IRC18:04
*** bouthors_ has quit IRC18:04
*** nkrinner is now known as nkrinner_afk18:05
*** sigmavirus24_awa is now known as sigmavirus2418:06
*** mickeys has joined #openstack-meeting-318:07
*** hoangcx has joined #openstack-meeting-318:09
*** alexsyip has joined #openstack-meeting-318:10
*** puranamr_ has joined #openstack-meeting-318:14
*** puranamr has quit IRC18:14
*** puranamr has joined #openstack-meeting-318:15
*** puranamr_ has quit IRC18:16
*** puranamr has quit IRC18:16
*** puranamr has joined #openstack-meeting-318:16
*** jwarendt has quit IRC18:17
*** jckasper has joined #openstack-meeting-318:18
*** FallenPegasus has quit IRC18:18
*** SridarK has joined #openstack-meeting-318:19
*** puranamr has quit IRC18:22
*** sridhar_ram1 has left #openstack-meeting-318:22
*** DJLoky06 has joined #openstack-meeting-318:25
*** yushiro has joined #openstack-meeting-318:25
*** ajmiller_ has joined #openstack-meeting-318:25
*** ajmiller_ has quit IRC18:25
*** vishwanathj has joined #openstack-meeting-318:25
*** egallen has quit IRC18:26
*** belmoreira has joined #openstack-meeting-318:28
*** ivar-laz_ has quit IRC18:29
*** ivar-lazzaro has joined #openstack-meeting-318:29
*** pc_m has joined #openstack-meeting-318:30
*** annp has joined #openstack-meeting-318:31
*** ivar-lazzaro has quit IRC18:31
*** badveli has joined #openstack-meeting-318:31
SridarKhi18:31
*** galstrom_zzz is now known as galstrom18:32
pc_mSridarK: hi18:32
badvelihello sridark18:32
hoangcxHi SridarK and all18:32
annphi18:32
mickeysHi18:32
badvelihello pc_m18:32
yushiroSridarK, Hi,  :-)18:32
SridarKhi all18:32
SridarKlets get started18:32
badvelihello all18:32
*** ivar-lazzaro has joined #openstack-meeting-318:32
vishwanathjhi18:32
SridarK#startmeeting Networking FWaaS18:32
openstackMeeting started Wed Jul 15 18:32:38 2015 UTC and is due to finish in 60 minutes.  The chair is SridarK. Information about MeetBot at http://wiki.debian.org/MeetBot.18:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:32
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:32
openstackThe meeting name has been set to 'networking_fwaas'18:32
*** FallenPegasus has joined #openstack-meeting-318:32
SridarKsorry abt connectivity issues last mtg and thanks all for helping18:33
SridarK#topic Bugs18:33
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:33
*** sadasu has quit IRC18:33
SridarK#link https://bugs.launchpad.net/neutron/+bug/147427918:34
openstackLaunchpad bug 1474279 in neutron "FWaaS let connection opened if delete allow rule, beacuse of conntrack" [Undecided,New] - Assigned to Elena Ezhova (eezhova)18:34
SridarKnew one i see and it just get picked up by Elena18:34
SridarKany others that folks are aware of causing some concerns18:34
SridarK?18:34
*** FallenPegasus has quit IRC18:35
SridarKok lets move on18:35
SridarK#topic Service Objects/Group18:35
*** openstack changes topic to "Service Objects/Group (Meeting topic: Networking FWaaS)"18:35
SridarKbadveli: all yours18:35
badvelii am working on a wip patch18:36
badvelinot yet there18:36
*** jwarendt has joined #openstack-meeting-318:36
*** bouthors has joined #openstack-meeting-318:36
*** bouthors_ has joined #openstack-meeting-318:36
SridarKbadveli: ok, can u pls share the link18:36
badvelii could spend little time on neutron patch and scenario tests18:37
SridarKbadveli: so we will have one on neutron and another patch on neutron_fwaas ?18:37
SridarKbadveli: ok18:37
badveliyes scenario tests for neutron-fwaas18:38
badvelithe patch is only scenario tests in neutron-fwaas18:38
SridarKbadveli: ok there will be a backend on fwaas as well eventually ?18:38
badvelishould be as the reference model18:39
SridarKbadveli: ok perfect, anything else to add or discuss ?18:39
badvelibut initially to make progress i am concentrating on neutron patch and use the service objects in scenario tests18:40
SridarKbadveli: yes that definitely makes sense18:40
*** Yi has quit IRC18:40
badvelibut i need pc_m help18:40
badvelito set up the scenario tests18:41
* pc_m ears perk18:41
*** belmoreira has quit IRC18:41
SridarK:-)18:41
badvelihe asked me to add a job18:41
badveli i am not there yet,18:42
SridarKbadveli: ok, do u want to discuss now with pc_m or take it up offline ?18:42
*** puranamr has joined #openstack-meeting-318:42
pc_mSridarK: whatever works is OK with me18:43
*** puranamr has quit IRC18:43
badvelii would like to discuss, since we have not yet have a similar model as vpnaas18:43
*** puranamr has joined #openstack-meeting-318:43
badvelii can take it up offline18:44
SridarKbadveli: ok cool18:44
SridarKlets move on then18:44
SridarK#topic Logging Spec18:44
pc_mbadveli: Just ping me, when you need help.18:44
*** openstack changes topic to "Logging Spec (Meeting topic: Networking FWaaS)"18:44
SridarKyushiro: hoangcx: all yours18:44
yushirohi, SridarK long time no see :-)18:45
badvelithanks pc_m18:45
SridarKyushiro: yes good to c u18:45
SridarK:-)18:45
yushirocurrently,  we've already implemented new logging API patch.18:45
yushiroSo,  I'd like to update my spec and WIP.18:46
SridarKyushiro: great18:46
yushiroRFE - Packet logging API for Neutron. https://bugs.launchpad.net/neutron/+bug/146836618:46
openstackLaunchpad bug 1468366 in neutron "RFE - Packet logging API for Neutron" [Undecided,Confirmed] - Assigned to Yushiro FURUKAWA (y-furukawa-2)18:46
yushiroAnd, I'd like pc_m 's help...18:46
vishwanathjI vote for cloning pc_m :)18:47
SridarKpc_m: is a great help all the time :-)18:47
SridarKvishwanathj: +118:47
SridarK:-)18:47
pc_m:)18:47
yushiropc_m, I'd like to ask your review in my RFE :-)18:47
* pc_m needs a clone already.18:47
pc_myushiro: Sure will add to my list.18:48
yushiroSridarK, pc_m  Our target is 'Liberty' to implement logging feature.18:48
SridarKyushiro: yes understood18:49
*** puranamr has quit IRC18:49
SridarKyushiro: anything else u would like to bring up ?18:49
yushiroSridarK, It's OK.  I'll update my fwaas spec and WIP :-)18:50
SridarKyushiro: ok thanks18:50
*** puranamr has joined #openstack-meeting-318:50
SridarK#topic SG - FWaaS alignment (FWaaS Usecases)18:51
*** openstack changes topic to "SG - FWaaS alignment (FWaaS Usecases) (Meeting topic: Networking FWaaS)"18:51
SridarK#link https://etherpad.openstack.org/p/fwaas_use_cases18:51
SridarKxgerman: over to u18:51
SridarKthanks to all for adding more inputs here, i tried to summarize into buckets (broadly) around L#13118:52
mickeysThere is a lot of stuff there. Do we need to prioritize requirements? How?18:52
SridarKmickeys: yes hence a first stab at putting it into broader buckets18:53
SridarKthen we can start prioritizing18:53
SridarKNot sure if xgerman: is away, we can continue the discussion18:54
mickeysI guess he is at the mid-cycle summit. Does not seem like FWaaS will have quorum there.18:54
jwarendtxgerman is at mid-cycle meetup18:54
SridarKok - lets continue with discussion and this is probab going to take some amount of iterations and we can pick it up with xgerman next time18:55
*** puranamr has quit IRC18:55
jwarendtThe usecase document is open for input though18:55
SridarKjwarendt: yes18:56
mickeysIn Vancouver, it seemed like many key Neutron developers had strong opinions on SG - FWaaS alignment, but we have not heard from the in a while. Any idea how to include them so there are no surprises just as we think we are getting consensus?18:56
SridarKAs i saw it one set of requirements focussed on the point of insertion of the FW18:56
sc68calI was actually writing up a spec to address this18:56
sc68calhttps://etherpad.openstack.org/p/fwaas-api-evolution-spec18:56
SridarKVM ports, routers, router interfaces ...18:56
SridarKsc68cal: hi18:56
jwarendtWill try to get midcycle input into that doc.18:56
SridarKsc68cal: great this is a good place to capture the results of the discussion18:57
SridarKmickeys: yes, point taken - i am hoping that requirements that folks come up will drive that decision18:58
sc68calI basically had strong opinions about the SG api (no changes to it), and how the FwaaS API is where everyhting should go, so I am writing a spec to collect my thoughts and document what I've been saying at the midcycle18:58
*** flwang has quit IRC18:58
*** markvoelker has quit IRC18:58
SridarKsc68cal: +118:58
jwarendt+118:59
SridarKthe use case etherpad has mostly focussed on fwaas requirements18:59
hoangcx+118:59
yushirosc68cal, great.  I'd like to attend midcycle :-)18:59
mickeysI put in some requirements from the point of view of both security groups and fwaas18:59
*** FallenPegasus has joined #openstack-meeting-319:00
*** shwetaap has joined #openstack-meeting-319:00
SridarKmickeys: and i think u made a point that u had no religion on this19:00
sc68calyushiro: We actually have a hangout open, for remote attendees19:00
sc68calit's on the etherpad https://etherpad.openstack.org/p/LBaaS-FWaaS-VPNaaS_Summer_Midcycle_meetup19:00
SridarKsc68cal: thanks19:01
mickeysSridar: Yes, as long as there is a path for future extensions to security group functionality19:01
SridarKsc68cal: perhaps with ur spec if manage to capture the sentiment at the mid cycle that will be good input19:02
jwarendtThe use case IMHO is what customer needs - whether done in SG or FWaaS is really a detail, do not want to limit meeting customer needs just by OpenStack internal boundaries.19:02
SridarKin addition to the requirements19:02
sc68calSridarK: agreed - I plan on doing that and sharing with the community to see if there is consensus in the wider community for whatever conensus we build at the midcycle19:02
SridarKjwarendt: yes coming at it from use cases would be right thing19:03
SridarKsc68cal: great thanks19:03
*** shwetaap1 has quit IRC19:03
xgermanwe will keep him honest :-)19:03
SridarKxgerman: hi :-)19:03
xgermanhi19:04
SridarKxgerman: we got the ball rolling on the use cases19:04
SridarKpls chime in19:04
xgermanyep19:04
xgermanI think we are ready for the next step so we will weight in on the spec19:05
badveli jwarendt but using security groups for advanced use case will it be feasible19:05
*** e0ne has quit IRC19:05
SridarKxgerman: perhaps a bit more time is needed for folks to digest the contents and then we can start a prioritized list19:06
SridarKat least on the use cases19:06
SridarKthe SG - FWaaS API is a bit more complicated, but hopefully the use cases can drive the discussion there19:06
xgermanyeah, we will definitely keep an eye on it and adjust as we go19:06
SridarKand sc68cal: 's spec19:07
*** Longgeek has quit IRC19:08
sc68calbtw the spec is just as an etherpad so if you have thoughts chip in :)19:09
xgerman+119:09
SridarKsc68cal: surely19:09
badvelithanks sc68cal19:09
*** fifieldt_ has joined #openstack-meeting-319:09
jwarendt+1 on usecases driving discussion <Sridark>19:09
mickeysThe other thing we should discuss is the flow classifier proposal: https://etherpad.openstack.org/p/flow-classifier19:11
*** fitoduarte has joined #openstack-meeting-319:11
SridarKPerhaps we can start the exercise of collating all inputs to some buckets ( i took a very prelim stab at it - pls feel free to edit) so we can get rid of duplicates for each persons inputs and start building out a list19:11
mickeysThey mention FWaaS and Security Groups explicitly.19:11
SridarKthen we can prioritize19:12
mickeys+119:12
jwarendt+119:12
*** fifieldt has quit IRC19:13
*** belmoreira has joined #openstack-meeting-319:13
SridarKok good lets try to do that then but we can preserve the contents from the folks who put their inputs and we can build this out towards the bottom19:14
badvelimickeys, jwarendt to me it looked like we should atleast check the feasabiltiy of the use cases implementation19:14
badveliwe cannot say the use cases can be done in either security groups or fwaas19:14
SridarKbadveli: at least once we have the use cases, the next round in addition to prioritization we can do the feasibility19:15
mickeysbadveli: Not sure how to capture feasibility. Hopefully people take that into account during prioritization.19:15
SridarKor at least call it out in terms of SG/FWaaS19:16
badvelithanks19:16
badveliyes i think that makes more sense19:17
SridarKok so perhaps we can run thru this exercise over the next couple of days so we can target to have a list for discussion by the next meeting19:17
jwarendt+119:17
SridarKcool we can possibly discuss this forever, so unless there is something else very critical, lets move on19:18
SridarK:-)19:19
*** Vichoward has quit IRC19:19
SridarKwe hope that xgerman: & sc68cal: would have all the answers for us, solved world hunger, gotten us to world peace etc etc when they are back from the mid cycle :-)19:20
jwarendt+100019:20
SridarKon that note of optimism lets move on19:20
SridarK#topic Open Discussion19:21
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:21
SridarKpc_m: pls go ahead19:21
SridarKand others as well19:21
pc_mSridarK: I have a few things to mention to the team, in case you folks are not aware of them...19:21
pc_m1) Grenade job has been modified to disable services, so no service based migrations are tested.19:21
SridarKi am just catching up after PTO so every thing is news to me :-)19:21
pc_mThis implies that in the future we should have service based Grenade jobs.19:22
SridarKok and we will need to get them set up19:22
pc_m2) Should also do a Grenade plugin for service19:22
pc_m3) Should do a DevStack plugin too.19:23
pc_mI did one for VPNaaS and it has some dependencies on FW plugin (config file). It has been approved and will upstream as soon as we fix breakage19:23
SridarKok19:24
pc_m4) Migration is being modified to support live-migration in Neutron. The services will be updated too. VPN will be guinea pig19:24
vishwanathjpc_m, do you mind sharing the patchset link for the VPANaas.Thanks19:24
pc_m5) Related to migration, for VPN, we had a check-migration test under PEP8. It is now broken due to the migration changes.19:25
SridarKSo on (4) we have to wait till VPNaaS settles in ?19:25
pc_mI have a patch that disables that check for VPN.19:25
pc_mSridarK: Yeah, they have to do neutron and then each of the services. Requires directory structure change.19:25
SridarKpc_m: ok thx19:26
pc_mI hit issues with Grenade, and found that it is broken for services. Hence #1.19:26
SridarKok thx pc_m: for the info19:27
pc_mSo, if you do any change with db migration, it'll need manual checking.19:27
pc_mSridarK: sure, np/19:27
*** sridhar_ram1 has joined #openstack-meeting-319:27
SridarKAny one else have other things to bring up as we are near to closing19:29
mickeysFlow classifier19:29
pc_mall set19:29
*** tonyd has joined #openstack-meeting-319:29
badveli      pc_m could you please clarify if we add a upgrade(for example in my case service group does change the db migration by addding a new file)19:29
badveliwhat do you mean by manual checking19:29
pc_mbadveli: So, grenade disabled FW, so it won't be tested now (at all). You'll need to manually test.19:30
pc_mUntil you create a FW grenade job, and that will be delayed, until all this migration change is done.19:30
badveliok thanks pc_m19:30
mickeysFlow classifier: For Security Groups, I think it is a clear no go due to backwards compatibility and alignment with Amazon19:30
mickeysFor FWaaS, I personally don't have a strong opinion, but I suspect many of you want backwards compatibility, so you might want to speak up and say it is too late to change the FWaaS model to a common classifier19:31
SridarKmickeys: and other issues on the compat that sc68cal: brought up at YVR as well19:31
mickeysIf FWaaS did go with a common classifier, then service object/group would need to move there19:31
vishwanathjFriendly reminder: we are past the hour19:31
SridarKvishwanathj: yes19:31
SridarKmickeys: sorry lets close out now19:32
pc_mbye!19:32
SridarKmickeys: add it to the etherpad19:32
yushirobye bye :-)19:32
SridarK#endmeeting19:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:32
hoangcxBye19:32
openstackMeeting ended Wed Jul 15 19:32:27 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:32
SridarKbye19:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-07-15-18.32.html19:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-07-15-18.32.txt19:32
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-07-15-18.32.log.html19:32
SridarKbye all19:32
yushirovishwanathj,  Nice time keeper !!19:32
badvelithanks mickeys , bye all19:32
jwarendtthanks19:32
vishwanathj:)19:32
annpbye19:32
yushirogood night, all :-)19:33
*** annp has quit IRC19:33
*** pc_m has left #openstack-meeting-319:33
*** yushiro has quit IRC19:33
*** hoangcx has quit IRC19:33
*** choco_ has joined #openstack-meeting-319:34
*** SridarK has quit IRC19:34
*** choco_ has quit IRC19:38
*** puranamr has joined #openstack-meeting-319:39
*** sdake_ has joined #openstack-meeting-319:41
*** belmoreira has quit IRC19:43
*** markvoelker has joined #openstack-meeting-319:43
*** bouthors_ has quit IRC19:43
*** bouthors has quit IRC19:43
*** kzaitsev_mb has joined #openstack-meeting-319:43
*** mickeys has quit IRC19:45
*** sdake has quit IRC19:45
*** markvoelker has quit IRC19:45
*** markvoelker has joined #openstack-meeting-319:46
*** crobertsrh has joined #openstack-meeting-319:47
*** neillc has joined #openstack-meeting-319:47
*** egallen has joined #openstack-meeting-319:49
*** robcresswell has joined #openstack-meeting-319:49
*** nkrinner_afk is now known as nkrinner19:51
*** salv-orlando has joined #openstack-meeting-319:51
*** sdake_ has quit IRC19:52
*** hurgleburgler has joined #openstack-meeting-319:54
*** doug-fish has joined #openstack-meeting-319:54
*** tsandall has joined #openstack-meeting-319:54
*** bpokorny has joined #openstack-meeting-319:56
*** salv-orlando has quit IRC19:57
*** ducttape_ has joined #openstack-meeting-319:57
*** sdake has joined #openstack-meeting-320:00
*** bpokorny_ has quit IRC20:00
*** pauloewerton has joined #openstack-meeting-320:00
*** tqtran has joined #openstack-meeting-320:00
*** esp has joined #openstack-meeting-320:00
*** tonyd has quit IRC20:01
*** r1chardj0n3s has joined #openstack-meeting-320:01
tqtranhello hello20:02
r1chardj0n3sohai20:02
neillchello20:02
hurgleburgler(◠‿◠✿)ノ20:02
espo/20:02
pauloewertono/20:02
ducttape_o/20:02
rhagarty_o/20:02
mrungeo/20:02
kzaitsev_mbhas the meeting started? =)20:02
mrungenope, we're here by coincidence20:03
tqtrannot yet, david's around though20:03
david-lyle#startmeeting Horizon20:03
openstackMeeting started Wed Jul 15 20:03:18 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:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: Horizon)"20:03
openstackThe meeting name has been set to 'horizon'20:03
btully%/20:03
kzaitsev_mbo/20:03
peristerio/20:03
crobertsrhhello/20:03
doug-fishhi20:03
bpokornyHi20:04
*** lhcheng has joined #openstack-meeting-320:04
*** tonyd has joined #openstack-meeting-320:04
david-lylethe gangs all here20:05
r1chardj0n3syep20:05
david-lyleThe only general lead in I have is that the midcycle is next week20:06
david-lylewe are working on a video conf solution for remote participants20:06
david-lyleand by we, I mean someone else ;)20:07
*** mwhagedorn has joined #openstack-meeting-320:07
kzaitsev_mb(=20:07
r1chardj0n3sI've been told that vidyo should support >10 participants20:07
robcresswell\o/20:08
david-lyleThere was a question around the weekly meeting next week. It will be at 6am Fort Collins time, so I can still run it if desired20:08
robcresswellYeah if there's some type of video, that would be great20:08
r1chardj0n3sgetting a camera/mic is up to someone else, as I tried the one I have and it didn't work :)20:08
*** Longgeek has joined #openstack-meeting-320:08
*** shwetaap has quit IRC20:08
espI think hp myrooms suports 25020:08
robcresswellMe or Matthias could run it, if thats easier. It was more if it should still be held with all the cores busy?20:08
david-lyleother than r1chardj0n3s and doug-fish I don't think anyone that usually attends will be here20:09
david-lylerather than home20:09
david-lyleprobably asking the wrong group20:09
david-lyle:)20:09
*** ameybhide has joined #openstack-meeting-320:10
mrungeyeah, maybe20:10
david-lyleI'll just hold it20:10
robcresswellSure20:10
*** ameybhide has left #openstack-meeting-320:10
david-lyleif we quit early, so be it20:10
*** egallen has quit IRC20:10
david-lyleThere is a UX project proposal up, from Piet to add UX to openstack20:10
david-lylewhich may be of interest to some20:11
PietTerrible idea!  -1!20:11
robcresswellWho even is that piet guy20:11
robcresswell:)20:11
david-lyle#link https://review.openstack.org/19976820:11
Pietmouth breather20:11
david-lyledon't get me started20:11
david-lyleseemed to be generally supported, some minor concerns from the TC20:12
*** shwetaap has joined #openstack-meeting-320:12
david-lylelast general thing, I posted some review criteria, to explicitly spell out expectations20:13
david-lyle#link https://wiki.openstack.org/wiki/Horizon/Reviews20:13
*** egallen has joined #openstack-meeting-320:13
*** Longgeek has quit IRC20:13
*** Yi has joined #openstack-meeting-320:14
david-lyleIMO we've been getting a little lax and I'd like to see that corrected20:14
ducttape_do we need more rules, or better adoption of those listed?20:14
r1chardj0n3s+1 guidelines20:14
*** jwarendt has quit IRC20:14
mrungebetter adoption, I think the rules are clear20:14
david-lyleducttape_: in the past the guidelines were tribal knowledge, this just documents them20:14
*** tonyd has quit IRC20:15
*** puranamr has quit IRC20:15
david-lyletribal knowledge doesn't share as easily20:15
ducttape_should we have listed that each +2 should be from a different company?20:15
robcresswellOne nitpick to tag on, when you approve patches, can you please also make sure the bug is targeted/ prioritised and the patch is attached properly (sometimes auto-infra doesnt work)20:15
*** puranamr has joined #openstack-meeting-320:15
doug-fishlisting them in a wiki is a great idea20:15
mrungerobcresswell +120:16
mrungeit's a wiki, that should be added20:16
doug-fishducttape_: is that true? (each +2 from a different company) I thought as long as the submitter and both approvers were not from the same company all was good20:16
ducttape_not sure, I have heard different versions of the "lets get broad adoption for merging" rule20:16
doug-fishI don't see it in the wiki20:16
david-lyleducttape_: the rule I've been advocating is of the author, and two core reviewers one of the three needed to be from a different company20:16
doug-fishdavid-lyle: maybe you could capture that in the wiki?20:17
david-lylesure20:17
doug-fishthx20:17
david-lyleI'll add it post meeting20:17
mrungeand please add to check, bug is targeted correctly, prioritized20:17
mrungeas robcresswell mentioned20:18
*** matt-borland has joined #openstack-meeting-320:18
robcresswellYeah, and listed against the bug, recently infra keeps saying Fix Commited without linking the patch so I end up chasing them down.20:18
*** badveli has quit IRC20:18
david-lyleif there are concerns that the 1 of 3 rule is causing problems please raise it privately or publicly20:18
*** sqchen has joined #openstack-meeting-320:19
*** ongk has joined #openstack-meeting-320:19
david-lyleI also cleaned up the d-o-a project in launchpad today, will try to tackle horizon in the next few20:19
* david-lyle knows that will go much slower20:19
david-lyleso you can target bugs in d-o-a to a milestone as well20:20
*** jwy has joined #openstack-meeting-320:20
*** Yi_ has joined #openstack-meeting-320:20
* ducttape_ looks forward to doa and django 1.8 20:20
david-lyleToday's agenda can be found at:20:20
david-lyle#link https://wiki.openstack.org/wiki/Meetings/Horizon20:20
mrungeif there's a milestone missing, it seems I am able to create tags, versions etc. in launchpad. too20:20
*** alexsyip has quit IRC20:21
lhchengmy concern is although 1 of 3 is followed, but all three have the same motive. It kinda work around the rule.20:21
kzaitsev_mbdavid-lyle: seems like I added the only item to the agenda =)20:21
david-lylelhcheng: if that goal of the motive is outside the scope of the project, then we have a problem20:21
david-lyleif the goal is correct and the means to get there are a problem, we should discuss that20:22
david-lylelet's table that for just a minute and hear kzaitsev_mb20:22
*** Yi__ has joined #openstack-meeting-320:22
*** Yi_ has quit IRC20:22
ducttape_lhcheng  - I think the spirit of the rule is "the change should try to gather broad input, and see reasonable effort made so that anyone interested can review"20:23
*** Yi has quit IRC20:23
david-lyle#topic Choosing a CPL (https://wiki.openstack.org/wiki/CrossProjectLiaisons) for OSLO20:23
*** openstack changes topic to "Choosing a CPL (https://wiki.openstack.org/wiki/CrossProjectLiaisons) for OSLO (Meeting topic: Horizon)"20:23
lhchengdavid-lyle: sure20:23
david-lyleso kzaitsev_mb you're volunteering, is that correct?20:23
kzaitsev_mbwell, the topic actually says it all. I've been contacted by dims_ earlier this week, and he asked if I'd like to volounteer for that position20:24
*** tonyd has joined #openstack-meeting-320:24
kzaitsev_mbdavid-lyle: yep, I pretty much would like to )20:24
david-lylethere's a lot of competition ;)20:24
kzaitsev_mbif that's ok with everyone )20:24
kzaitsev_mbI'll try to do my best (=20:24
david-lyleI have no issue with it, anyone else?20:25
lhcheng++ for me20:25
mrunge1+ from me20:25
doug-fishno concern here - thanks for volunterring kzaitsev_mb!20:25
mrungeand if he doesn't behave, we'll kick him out again?20:25
mrungethank you for stepping up kzaitsev_mb !20:25
david-lylekzaitsev_mb: please add yourself to the wiki, and thanks for stepping up20:25
*** DJLoky06 has quit IRC20:25
kzaitsev_mbok, will do =)20:25
lhchengthanks kzaitsev_mb20:25
david-lyleagenda complete!20:26
kzaitsev_mb"And now my watch begins" or something (=20:26
david-lyle#topic Open Discussion20:26
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"20:26
david-lylego ahead lhcheng20:26
*** alexsyip has joined #openstack-meeting-320:26
david-lylesorry to cut you off before20:26
lhchengno worries, I guess the reason we have the 1 of 3 rule is so that we can control code getting pushed without broader review20:27
doug-fishlhcheng: are you thinking patches get approved too quickly and there is no chance for review?20:28
doug-fish*some patches, not all20:28
mrungeiirc, that was to prevent code rushed in, which was dominated by just a single company20:28
lhchengdoug-fish: approved too quickly20:28
doug-fishlhcheng: maybe we should have some minimum age/time we generally let the patches sit before they get merged?20:29
tqtranisn't that the point of having many cores? to get eyes on things. usually it takes a day or two to merge, is that not enough time?20:30
ducttape_right, what would be reasonable review time?20:30
*** rajatvig has joined #openstack-meeting-320:30
david-lyleOk, the historical reason was when I started 2 companies were the most active contributors and had different motivations, but worked well together. My original concern was getting two major currents going in horizon that wouldn't necessarily line up20:30
david-lyleit seems we may have those two currents now and the split is no longer at company boundaries20:31
david-lyleso the rule is too simple20:31
ducttape_+120:31
david-lylethere is a strong push to change and change rapidly20:32
lhchengdoug-fish: at least get the patch pass gate first even before approving20:32
doug-fishdavid-lyle: : just to make those 2 current clear to those of us who lack social sensitivity can you spell out the 2 currents you see?20:32
david-lyleand there is a strong push by those deploying horizon and actively use it, to do so more sanely20:32
doug-fishlhcheng: yeah, that's probably a good idea!20:32
*** FallenPegasus has quit IRC20:32
*** FallenPegasus has joined #openstack-meeting-320:33
david-lyleand developers in those two camps don't necessarily understand the implications of changes for the other20:33
ducttape_doug-fish - this is an oversimplification, but new code right away vs the need to be able to have horizon in a good working state 100%20:33
doug-fishyeah ok, I got it now.20:33
* david-lyle thinks he said something like that20:34
tqtrani agree, but isnt majority of new code disabled by default?20:34
*** jwy has quit IRC20:34
david-lyletqtran: only the end features of it20:34
ducttape_I think that's missing the point20:34
*** DJLoky06 has joined #openstack-meeting-320:34
mrungeyupp20:34
tqtranthere are a few infra changes that did get through, i agree those should have been more strict20:34
ducttape_if you can check in whatever you like, so long as it is disabled.... thats not correct20:35
david-lyleand building iteratively is ok, as long as code is not the only thing being created20:35
lhchenghmm even if its disabled code, it should still be working code20:35
lhchengwith test too20:35
mrungeand it should be checked on the gate properly20:35
tqtrannothing merges without getting checked at gate?20:35
david-lyletests and docs are not a tax, they protect the developer too20:35
mrungeif you don't write tests, it's not checked20:36
david-lyleotherwise the next partial piece comes along and breaks the change you just made20:36
tqtrani agree some of the patches didn't include tests, but i would say most of the newer patches do contain them, in fact more so than previously20:36
*** jasondotstar has quit IRC20:37
*** Yi__ has quit IRC20:37
tqtranif you guys took a look at them, you would notice that a majority of the time, the spec files are bigger than the code20:37
david-lylethe lack of tests is not just a angular vs django thing either20:37
mrungeit's not fingerpointing at anyone, we just need to make sure, code is production ready, not ready to be tested by other developers20:37
tqtrani agree, some infra stuff did get in w/o proper tests20:38
tqtranbut theres only one that i can think of off the top of my head20:38
tqtranmrunge: understood, i agree that going forward, tests and docs should be prioritize20:38
ducttape_tqtran:  this change was +2 within a 3 min window - https://review.openstack.org/#/c/200324/20:39
ducttape_and I didn't see any tests20:39
lhchengmrunge: agree, we want to agree to some guideline on quality of code20:39
david-lyleFor the me the goal here is make clear the expectations and do a bit of a reset20:39
tqtranducttape_: how would you test that?20:39
*** jwy has joined #openstack-meeting-320:40
david-lyleotherwise we will all be paying down the road20:40
*** krtaylor has quit IRC20:40
tqtransure thats fair20:40
doug-fishdavid-lyle: yeah that's a good approach.20:40
*** nkrinner is now known as nkrinner_afk20:40
ducttape_tqtran - thats the question a core should be asking ;)20:40
david-lyletqtran: load the panel and test that it renders, much like any of the index views20:40
doug-fishI've been contributing here and there to other projects - they are much more strict about testing that we have been in Horizon20:40
tqtranas in manual testing?20:40
david-lyletqtran: we have the ability to write selenium tests if need be20:41
lhchengdoug-fish: true, no tests/doc is immediately -120:41
tqtranso, do we normally tests new panels/dashboards via selenium?20:41
lhchengdoug-fish: at least for keystone20:41
tqtranim just trying to setup a consensus and norm20:41
david-lyletqtran: with django we didn't need selenium to do that20:41
doug-fisheven heat requires unit tests!20:41
ducttape_we usually use django's test runner20:41
mrungetqtran, in the past, we didn't need selenium20:42
david-lylebecause the page was rendered server side20:42
*** FallenPegasus has quit IRC20:42
mrungenow, we need some rendering engine20:42
tqtranso my question is simple, for new panels/dashboards, do we have existing tests for them? and if not, are we expecting programmatic tests for them?20:42
david-lylebut we did use selenium to validate some Javascript code20:42
david-lylethat has been the case yes20:43
mrungetqtran, for django based panels: as david said. and yes, we're expecting programmatic tests20:43
tqtrani have a feeling that many more panels are going to get angularize going forward, so this is something i would be interested to know20:43
*** bryan_att has quit IRC20:43
tqtrani think david-lyle is referring to just manual testing, so we'd have to come up with a programmatic way to test it then. sounds about right?20:44
david-lyletqtran: no programmatic20:44
ducttape_this would be something to be done with the first commit....  "this is how you test ng stuff"20:44
mrungetqtran, manual testing should be an exception20:44
mrungewe need automatic testing20:45
tqtranok, you guys are telling me two different things here20:45
david-lyletqtran: I don't think we are20:45
tqtranducttape_: most of the patches include testing messages in the commit body20:45
david-lyleok, that is different20:45
david-lylebut yes that is necessary too20:45
ducttape_I mean automated tests, not in a commit message20:46
mrungehow can we exclude regressions, if features are not tested at each commit?20:46
ducttape_I mean as you guys blaze that trail, to have a solid example for others to follow20:46
tqtranwould someone like to volunteer on creating this automated test for new panel/dashboard?20:46
mwhagedornmost of the new angular stuff seems to have jasmine tests.. what am I missing?20:46
*** jasondotstar has joined #openstack-meeting-320:46
tqtranif that is something you guys want, someone should step up to the plate, i sure got mine full :P20:47
david-lylehuh20:47
lhchengmwhagedorn: that only test the client side, how the data is passed from rest to client is not.20:47
doug-fishlhcheng: are you talking about integration tests?20:48
mwhagedornlike end to end testing/selenium20:48
mwhagedorn?20:48
tqtranlhcheng:  you mean like integration tests? or https://github.com/openstack/horizon/blob/master/openstack_dashboard/test/api_tests/keystone_rest_tests.py ?20:48
ducttape_https://i.imgflip.com/o91iz.jpg20:48
mrungetqtran, integration tests would be ideal20:49
lhchengdoug-fish: not integration test20:49
mwhagedornducttape_: moce20:49
mwhagedornnice20:49
mwhagedorn:)20:49
mrungebut, that's probably too much20:49
lhchengintegration tests means horizon is tested with other services20:49
tqtranso just unit rest tests?20:49
tqtranwe have those....20:49
david-lylemost horizon tests to this point have been a hybrid20:49
david-lylethey're not really unit tests20:50
david-lylebecause we're not testing one method at a time20:50
mwhagedorndo we need to set expectations in the docs for what a good test looks like then?20:50
*** rajatvig has quit IRC20:50
david-lylewe're testing that methods work in association with the pages that are rendered20:50
tqtrandavid-lyle: for legacy code? or the newer code?20:50
david-lyletesting get_context_data while mocking the data source is worthless20:51
david-lyletqtran: django based code20:51
*** rajatvig has joined #openstack-meeting-320:52
david-lyleso the goal of a core reviewer is ultimately a stable and functioning project20:52
*** krtaylor has joined #openstack-meeting-320:53
david-lylechange is done with respect to that stability and continued functionality20:53
david-lyleif something needs to change drastically, it needs to be documented20:53
david-lyleso that people can consume it20:53
david-lylewithout ripping out their hair for days on end20:53
david-lyleI'm not saying we've been perfect at that20:54
david-lyleit is the goal20:54
mrungeyes!20:54
mwhagedornI am still a little in the dark then what qualifies as a good test from the core perspective20:55
mwhagedornwhats lacking20:55
mwhagedornwhats needed to get things more in line with larger goals20:55
ducttape_mwhagedorn - I think there are patterns for old school horizon changes20:55
ducttape_and the new stuff is all over the map on how much it does or does not have for tests, and which type20:55
ducttape_we are struggling to reach consensus on what is correct20:56
mwhagedornducttape_ : sure but wouldnt you agree that its hard to tell what the legacy tests actually test sometimes?20:56
mrungeoh, mwhagedorn that's easy20:56
hurgleburglerThere is some old stuff that isn't currently being tested at all as well20:56
ducttape_I'm strange, I understand the old tests very well.  you should ask a normal person20:56
*** FallenPegasus has joined #openstack-meeting-320:56
hurgleburglerdo we know what kind of coverage we currently have?20:56
tqtranducttape_: i think thats an unfair statement, most of the angular patches come with spec files (there were exceptions in kilo).20:56
david-lylemwhagedorn: depends on if you understand how mox and django work20:56
mwhagedornmox is pretty much user-viscious imho20:57
tqtranbut test for the patches in kilo have since been added20:57
david-lyletqtran: again, to me this is not a clean cut case of angular vs django20:57
ducttape_tqtran - would you agree we are trying to reach consensus on what is appropriate for ng style testing, when you are adding a new feature?20:57
peristericode coverage can help the reviewer see what has not been tested. It is not bullet proof but better then nothing20:57
tqtranright, thats what karma is there for20:58
hurgleburglerthat's just js thought, right?20:58
hurgleburglerthough*20:58
tqtrancorrect, just js part20:58
mrungetqtran, for example, new launch instance couldn't create a volume during launching an instance20:58
david-lylecoverage can be run on any horizon build20:58
mrungethat would have been caught very early20:59
mwhagedornyou can get coverage on the django stuff hurgleburgler....20:59
mrungeif there was a test for it20:59
david-lylelooks like time is up.21:00
tqtranok, so what im hearing is, more tests and docs. but going back to mwhagedorn, what are expections/standards for them?21:00
mwhagedornyes21:00
mwhagedornsomeone help me :)21:00
* robcresswell is following all this, btw, but also eating dinner :)21:01
tqtranand popcorn21:01
*** mickeys has joined #openstack-meeting-321:01
tqtranhahaha21:01
* esp just finished some nachos and a coke21:01
* ducttape_ always brings a cold beverage to these things21:01
robcresswellThe drama here is better than tv :)21:01
hurgleburglerGood Times ಠ◡ಠ21:02
mrungeyou can switch off tv and don't need to care about it any more21:02
hurgleburglerI'll have to bring pop corn to the mid cycle21:02
* david-lyle bites tongue21:02
robcresswellI'm happy to help out with docs stuff. Me and bradjones are working on a formal doc for angular panels/dashboards and adding external plugins etc21:02
david-lyle#nedmeeting21:02
r1chardj0n3sned meeting who?21:02
hurgleburglerstark??21:02
* r1chardj0n3s ducks21:02
david-lyle#action david-lyle document testing21:03
david-lyle#endmeeting21:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:03
openstackMeeting ended Wed Jul 15 21:03:12 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-07-15-20.03.html21:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-07-15-20.03.txt21:03
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-07-15-20.03.log.html21:03
*** r1chardj0n3s has left #openstack-meeting-321:03
*** hurgleburgler has left #openstack-meeting-321:03
neillcbye all21:03
*** puranamr_ has joined #openstack-meeting-321:03
*** neillc has left #openstack-meeting-321:03
*** mickeys has quit IRC21:03
*** tonyd has quit IRC21:04
*** mickeys has joined #openstack-meeting-321:04
*** Piet has quit IRC21:04
*** tqtran has left #openstack-meeting-321:04
*** pauloewerton has left #openstack-meeting-321:04
*** FallenPegasus has quit IRC21:05
*** puranamr has quit IRC21:05
*** FallenPegasus has joined #openstack-meeting-321:05
espthx david-lyle21:06
*** bknudson has quit IRC21:06
*** lhcheng has left #openstack-meeting-321:06
*** dims_ has quit IRC21:07
*** lblanchard has quit IRC21:07
*** jasondotstar has quit IRC21:09
*** rajatvig has quit IRC21:09
*** crobertsrh is now known as _crobertsrh21:10
*** ongk has left #openstack-meeting-321:10
*** stevemar has quit IRC21:10
*** julim has quit IRC21:10
*** matt-borland has left #openstack-meeting-321:10
*** rajatvig has joined #openstack-meeting-321:15
*** safchain has quit IRC21:15
*** jwy has left #openstack-meeting-321:18
*** stevemar has joined #openstack-meeting-321:20
*** mrmartin has quit IRC21:22
*** peristeri has quit IRC21:23
*** stevemar_ has joined #openstack-meeting-321:25
*** stevemar has quit IRC21:25
*** rajatvig has quit IRC21:25
*** FallenPegasus has quit IRC21:26
*** FallenPegasus has joined #openstack-meeting-321:26
*** mrunge has quit IRC21:26
*** egallen has quit IRC21:28
*** stevemar_ has quit IRC21:29
*** robcresswell has left #openstack-meeting-321:29
*** rajatvig has joined #openstack-meeting-321:30
*** sdake_ has joined #openstack-meeting-321:30
*** sdake_ has quit IRC21:30
*** Sukhdev has joined #openstack-meeting-321:30
*** sdake_ has joined #openstack-meeting-321:30
*** FallenPegasus has quit IRC21:31
*** FallenPegasus has joined #openstack-meeting-321:32
*** FallenPegasus has quit IRC21:32
*** sdake has quit IRC21:33
*** Piet has joined #openstack-meeting-321:33
*** FallenPegasus has joined #openstack-meeting-321:34
*** salv-orlando has joined #openstack-meeting-321:36
*** alexsyip has quit IRC21:36
*** Swami has quit IRC21:37
*** DJLoky06 has quit IRC21:40
*** rajatvig has quit IRC21:40
*** FallenPe_ has joined #openstack-meeting-321:40
*** FallenPegasus has quit IRC21:40
*** rajatvig has joined #openstack-meeting-321:41
*** rajatvig has quit IRC21:41
*** DJLoky06 has joined #openstack-meeting-321:42
*** tsandall has quit IRC21:42
*** sdake has joined #openstack-meeting-321:43
*** neelashah has quit IRC21:43
*** alexsyip has joined #openstack-meeting-321:43
*** tsandall has joined #openstack-meeting-321:44
*** rajatvig has joined #openstack-meeting-321:45
*** sdake_ has quit IRC21:46
*** Swami has joined #openstack-meeting-321:52
*** puranamr_ has quit IRC21:54
*** puranamr has joined #openstack-meeting-321:57
*** jaypipes has quit IRC21:57
*** Longgeek has joined #openstack-meeting-321:57
*** krtaylor has quit IRC22:03
*** shwetaap1 has joined #openstack-meeting-322:04
*** shwetaap has quit IRC22:08
*** puranamr has quit IRC22:12
*** banix has quit IRC22:15
*** Longgeek has quit IRC22:16
*** krtaylor has joined #openstack-meeting-322:16
*** FallenPe_ has quit IRC22:24
*** ivar-laz_ has joined #openstack-meeting-322:30
*** igordcard_ has quit IRC22:30
*** doug-fish has left #openstack-meeting-322:30
*** shwetaap1 has quit IRC22:33
*** ivar-lazzaro has quit IRC22:33
*** Yi has joined #openstack-meeting-322:36
*** Yi_ has joined #openstack-meeting-322:37
*** Yi has quit IRC22:40
*** galstrom is now known as galstrom_zzz22:41
*** sqchen has quit IRC22:41
*** yamahata has quit IRC22:42
*** shwetaap has joined #openstack-meeting-322:43
*** tsandall has quit IRC22:46
*** mickeys has quit IRC22:46
*** mickeys has joined #openstack-meeting-322:46
*** tsandall has joined #openstack-meeting-322:47
*** dims_ has joined #openstack-meeting-322:51
*** sigmavirus24 is now known as sigmavirus24_awa22:51
*** mestery_ has joined #openstack-meeting-323:00
*** esp has left #openstack-meeting-323:01
*** sqchen has joined #openstack-meeting-323:02
*** FallenPegasus has joined #openstack-meeting-323:03
*** mestery has quit IRC23:03
*** jasondotstar has joined #openstack-meeting-323:07
*** devlaps has joined #openstack-meeting-323:08
*** puranamr has joined #openstack-meeting-323:09
*** jasondotstar has quit IRC23:10
*** puranamr has quit IRC23:11
*** Yi_ has quit IRC23:11
*** mickeys has quit IRC23:12
*** fitoduarte has quit IRC23:18
*** carl_baldwin has quit IRC23:20
*** zhenguo has joined #openstack-meeting-323:27
*** Yi has joined #openstack-meeting-323:27
*** Sukhdev has quit IRC23:30
*** ducttape_ has quit IRC23:30
*** kzaitsev_mb has quit IRC23:32
*** DJLoky06 has quit IRC23:36
*** Yi has quit IRC23:44
*** shwetaap has quit IRC23:47
*** kzaitsev_mb has joined #openstack-meeting-323:47
*** bpokorny has quit IRC23:58
*** bpokorny has joined #openstack-meeting-323:58
*** Sukhdev has joined #openstack-meeting-323:59

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