Tuesday, 2015-04-21

*** banix has quit IRC00:00
*** bknudson has joined #openstack-meeting-300:05
*** banix has joined #openstack-meeting-300:05
*** alexsyip has quit IRC00:07
*** yamamoto has quit IRC00:08
*** carl_baldwin has quit IRC00:10
*** melwitt has joined #openstack-meeting-300:10
*** seizadi has quit IRC00:17
*** openstack has joined #openstack-meeting-300:35
*** ChanServ sets mode: +o openstack00:35
*** banix has quit IRC00:39
*** Poornima has joined #openstack-meeting-300:50
*** banix has joined #openstack-meeting-300:50
*** banix has quit IRC00:52
*** emagana has quit IRC00:54
*** Poornima has quit IRC01:00
*** Swami has quit IRC01:00
*** yamamoto has joined #openstack-meeting-301:00
*** seizadi has joined #openstack-meeting-301:06
*** igordcard has quit IRC01:08
*** wojdev has quit IRC01:08
*** shwetaap has joined #openstack-meeting-301:10
*** clu_ has quit IRC01:13
*** eghobo has quit IRC01:16
*** seizadi has quit IRC01:19
*** zhenguo has joined #openstack-meeting-301:21
*** banix has joined #openstack-meeting-301:35
*** sankarshan_away is now known as sankarshan_01:35
*** mwagner_lap has joined #openstack-meeting-301:37
*** banix has quit IRC01:40
*** sankarshan_ is now known as sankarshan_away01:40
*** sankarshan_away is now known as sankarshan_01:44
*** banix has joined #openstack-meeting-301:45
*** banix has quit IRC01:45
*** banix has joined #openstack-meeting-301:47
*** stanzgy has joined #openstack-meeting-301:50
*** melwitt has quit IRC01:51
*** bpokorny_ has quit IRC01:52
*** baoli has quit IRC01:52
*** baoli has joined #openstack-meeting-301:52
*** sbalukoff has quit IRC01:54
*** VW_ has joined #openstack-meeting-302:05
*** Poornima has joined #openstack-meeting-302:16
*** seizadi has joined #openstack-meeting-302:18
*** banix has quit IRC02:18
*** mattgriffin has joined #openstack-meeting-302:18
*** shwetaap has quit IRC02:21
*** mwang2 has quit IRC02:31
*** ivar-laz_ has joined #openstack-meeting-302:34
*** VW_ has quit IRC02:36
*** ivar-lazzaro has quit IRC02:37
*** ivar-laz_ has quit IRC02:38
*** stevemar has joined #openstack-meeting-302:39
*** VW_ has joined #openstack-meeting-302:39
*** bpokorny has joined #openstack-meeting-302:46
*** seizadi has quit IRC02:46
*** bpokorny has quit IRC02:46
*** bpokorny has joined #openstack-meeting-302:47
*** xuhanp has joined #openstack-meeting-303:02
*** xuhanp_ has joined #openstack-meeting-303:02
*** sbalukoff has joined #openstack-meeting-303:11
*** mattgriffin has quit IRC03:23
*** Yingxin1 has quit IRC03:29
*** bpokorny has quit IRC03:43
*** eghobo has joined #openstack-meeting-304:03
*** Swami has joined #openstack-meeting-304:06
*** mattgriffin has joined #openstack-meeting-304:15
*** Swami has quit IRC04:17
*** baoli has quit IRC04:18
*** VW_ has quit IRC04:21
*** amotoki has joined #openstack-meeting-304:24
*** sbalukoff has quit IRC04:25
*** Sukhdev has joined #openstack-meeting-304:44
*** Yingxin has joined #openstack-meeting-304:44
*** Longgeek has joined #openstack-meeting-304:52
*** ramineni2 has joined #openstack-meeting-304:57
*** zhenguo has quit IRC04:57
*** ramineni2 has left #openstack-meeting-304:57
*** flaper87 has quit IRC05:01
*** emagana has joined #openstack-meeting-305:02
*** flaper87 has joined #openstack-meeting-305:04
*** emagana has quit IRC05:16
*** mrmartin has joined #openstack-meeting-305:16
*** emagana has joined #openstack-meeting-305:17
*** mrmartin has quit IRC05:17
*** emagana has quit IRC05:21
*** nkrinner has joined #openstack-meeting-305:21
*** jcoufal has joined #openstack-meeting-305:31
*** sbalukoff has joined #openstack-meeting-306:02
*** armax_ has quit IRC06:06
*** armax has joined #openstack-meeting-306:07
*** armax has quit IRC06:07
*** armax has joined #openstack-meeting-306:08
*** armax has left #openstack-meeting-306:08
*** armax has joined #openstack-meeting-306:08
*** scheuran has joined #openstack-meeting-306:09
*** armax has quit IRC06:10
*** armax has joined #openstack-meeting-306:10
*** armax has quit IRC06:10
*** mrunge has joined #openstack-meeting-306:12
*** buchi has joined #openstack-meeting-306:23
*** salv-orlando has quit IRC06:29
*** mrmartin has joined #openstack-meeting-306:31
*** MaxV has joined #openstack-meeting-306:39
*** Sukhdev has quit IRC06:44
*** sahid has joined #openstack-meeting-306:45
*** MaxV has quit IRC06:48
*** eghobo has quit IRC07:02
*** mestery has quit IRC07:03
*** jtomasek has joined #openstack-meeting-307:06
*** zhenguo has joined #openstack-meeting-307:10
*** egallen has joined #openstack-meeting-307:19
*** hichihara has quit IRC07:20
*** flaper87 has quit IRC07:23
*** flaper87 has joined #openstack-meeting-307:23
*** hichihara has joined #openstack-meeting-307:27
*** wojdev has joined #openstack-meeting-307:28
*** xuhanp_ has quit IRC07:28
*** xuhanp has quit IRC07:28
*** iovadia has joined #openstack-meeting-307:30
*** jtomasek has quit IRC07:34
*** iovadia has quit IRC07:34
*** MaxV has joined #openstack-meeting-307:44
*** mestery has joined #openstack-meeting-307:46
*** stevemar has quit IRC07:49
*** iovadia has joined #openstack-meeting-307:50
*** sarob has joined #openstack-meeting-307:54
*** safchain has joined #openstack-meeting-307:58
*** sarob has quit IRC07:59
*** mattgriffin has quit IRC08:03
*** zz_ttrifonov is now known as ttrifonov08:07
*** zz_johnthetubagu is now known as johnthetubaguy08:08
*** yamamoto has quit IRC08:15
*** johnthetubaguy is now known as zz_johnthetubagu08:15
*** zz_johnthetubagu is now known as johnthetubaguy08:20
*** wojdev has quit IRC08:23
*** wojdev has joined #openstack-meeting-308:24
*** egallen has quit IRC08:27
*** e0ne has joined #openstack-meeting-308:34
*** Longgeek has quit IRC08:42
*** coolsvap|afk is now known as coolsvap08:45
*** vdrok_afk is now known as vdrok08:46
*** coolsvap is now known as coolsvap|afk08:46
*** sarob has joined #openstack-meeting-308:58
*** sarob has quit IRC09:03
*** yamamoto has joined #openstack-meeting-309:04
*** Longgeek has joined #openstack-meeting-309:14
*** matrohon has joined #openstack-meeting-309:27
*** yamamoto has quit IRC09:34
*** yamamoto has joined #openstack-meeting-309:36
*** alexpilotti has quit IRC09:37
*** Poornima has quit IRC09:40
*** salv-orlando has joined #openstack-meeting-309:42
*** yamamoto has quit IRC09:50
*** e0ne is now known as e0ne_10:02
*** e0ne_ is now known as e0ne10:04
*** etoews has quit IRC10:06
*** egallen has joined #openstack-meeting-310:07
*** etoews has joined #openstack-meeting-310:08
*** wojdev has quit IRC10:11
*** yamahata has quit IRC10:12
*** moshele has joined #openstack-meeting-310:23
*** egallen has quit IRC10:30
*** e0ne is now known as e0ne_10:33
*** e0ne_ is now known as e0ne10:34
*** vishwanathj has joined #openstack-meeting-310:41
*** wojdev has joined #openstack-meeting-310:44
*** sahid has quit IRC10:46
*** sarob has joined #openstack-meeting-310:48
*** stanzgy has quit IRC10:51
*** sarob has quit IRC10:52
*** sahid has joined #openstack-meeting-310:54
*** sahid has quit IRC10:54
*** sahid has joined #openstack-meeting-310:55
*** mrunge has quit IRC10:58
*** jtomasek has joined #openstack-meeting-311:13
*** sergef has joined #openstack-meeting-311:38
*** mwagner_lap has quit IRC11:38
*** alexpilotti has joined #openstack-meeting-311:41
*** mrunge has joined #openstack-meeting-311:41
*** jcoufal_ has joined #openstack-meeting-311:47
*** sergef has quit IRC11:49
*** jcoufal has quit IRC11:50
*** banix has joined #openstack-meeting-311:53
*** yamamoto has joined #openstack-meeting-311:53
*** banix has quit IRC11:55
*** buchi has quit IRC11:57
*** wojdev has quit IRC12:00
*** markvoelker has joined #openstack-meeting-312:02
*** markvoelker_ has joined #openstack-meeting-312:03
*** markvoelker_ has quit IRC12:04
*** markvoelker_ has joined #openstack-meeting-312:05
*** wojdev has joined #openstack-meeting-312:06
*** markvoelker has quit IRC12:07
*** thangp has joined #openstack-meeting-312:09
*** yamamoto has quit IRC12:12
*** sahid has quit IRC12:16
*** lblanchard has joined #openstack-meeting-312:17
*** salv-orlando has quit IRC12:18
*** mwagner_lap has joined #openstack-meeting-312:19
*** sergef has joined #openstack-meeting-312:20
*** salv-orlando has joined #openstack-meeting-312:21
*** lblanchard has quit IRC12:22
*** yamamoto has joined #openstack-meeting-312:23
*** baoli has joined #openstack-meeting-312:23
*** jckasper has quit IRC12:26
*** jckasper has joined #openstack-meeting-312:26
*** banix has joined #openstack-meeting-312:27
*** yamamoto has quit IRC12:30
*** wojdev has quit IRC12:33
*** sarob has joined #openstack-meeting-312:33
*** sarob has quit IRC12:38
*** thangp has quit IRC12:38
*** yamamoto has joined #openstack-meeting-312:44
*** wojdev has joined #openstack-meeting-312:44
*** amotoki has quit IRC12:48
*** cbouch has joined #openstack-meeting-312:49
*** VW_ has joined #openstack-meeting-312:50
*** yamamoto has quit IRC12:52
*** bknudson has quit IRC12:53
*** sarob has joined #openstack-meeting-312:54
*** mrunge has quit IRC12:58
*** baoli has quit IRC13:00
*** yamamoto has joined #openstack-meeting-313:01
*** baoli has joined #openstack-meeting-313:02
*** e0ne is now known as e0ne_13:04
*** yamamoto has quit IRC13:05
*** Longgeek has quit IRC13:05
*** e0ne_ is now known as e0ne13:06
*** salv-orlando has quit IRC13:06
*** shwetaap has joined #openstack-meeting-313:07
*** VW_ has quit IRC13:11
*** aveiga has joined #openstack-meeting-313:13
*** e0ne is now known as e0ne_13:16
*** bknudson has joined #openstack-meeting-313:16
*** yamamoto has joined #openstack-meeting-313:17
*** yamamoto has quit IRC13:17
*** yamamoto has joined #openstack-meeting-313:17
*** zhenguo has quit IRC13:17
*** yamamoto has quit IRC13:19
*** e0ne_ is now known as e0ne13:21
*** shwetaap has quit IRC13:22
*** absubram has joined #openstack-meeting-313:24
*** Longgeek has joined #openstack-meeting-313:24
*** jckasper has quit IRC13:24
*** egallen has joined #openstack-meeting-313:24
*** absubram has quit IRC13:24
*** Longgeek has quit IRC13:24
*** absubram has joined #openstack-meeting-313:25
*** Longgeek has joined #openstack-meeting-313:25
*** e0ne is now known as e0ne_13:26
*** e0ne_ is now known as e0ne13:26
*** peristeri has joined #openstack-meeting-313:27
*** ttrifonov is now known as zz_ttrifonov13:28
*** mattgriffin has joined #openstack-meeting-313:34
*** wojdev has quit IRC13:37
*** iben_ has joined #openstack-meeting-313:38
*** irenab has joined #openstack-meeting-313:38
*** vhoward- has joined #openstack-meeting-313:39
*** baoli has quit IRC13:44
*** baoli_ has joined #openstack-meeting-313:45
*** seizadi has joined #openstack-meeting-313:45
*** emagana has joined #openstack-meeting-313:48
*** zz_jgrimm is now known as jgrimm13:49
*** lblanchard has joined #openstack-meeting-313:49
*** cbits has joined #openstack-meeting-313:50
*** Piet has quit IRC13:51
*** armax_ has joined #openstack-meeting-313:51
*** emagana_ has joined #openstack-meeting-313:51
*** salv-orlando has joined #openstack-meeting-313:52
*** seizadi has quit IRC13:52
*** yamahata has joined #openstack-meeting-313:52
*** emagana has quit IRC13:52
*** armax_ has quit IRC13:52
*** julim has joined #openstack-meeting-313:52
*** armax_ has joined #openstack-meeting-313:52
*** amotoki has joined #openstack-meeting-313:54
*** salv-orlando has quit IRC13:54
*** VW_ has joined #openstack-meeting-313:54
*** yamamoto has joined #openstack-meeting-313:55
*** iben_ has quit IRC13:56
*** wojdev has joined #openstack-meeting-313:57
*** Sukhdev has joined #openstack-meeting-313:57
*** banix has quit IRC13:57
*** salv-orlando has joined #openstack-meeting-314:00
*** ajo has joined #openstack-meeting-314:00
ajohi :)14:00
ajoping irenab, aveiga , matrohon14:00
ajoping sc68cal14:00
vhoward-hey14:00
aveigahello14:01
matrohonhi14:01
cbitsHi14:01
*** sarob has quit IRC14:01
ajoaround for the QoS meeting?14:01
cbouchhi14:01
aveigaabsolutely14:01
ajogreat :)14:01
vhoward-yeah ajo14:02
vhoward-;)14:02
*** egallen has quit IRC14:02
moshelehi14:02
ajoI'll wait 1 more minute to see if irenab is able to join14:02
ajoI wanted some feedback from her regarding design :)14:02
*** bryan_att has joined #openstack-meeting-314:02
ajook, I guess we can start, and I'll leave the specific design topics for the ends14:03
ajoend14:03
ajo#startmeeting neutron_qos14:03
openstackMeeting started Tue Apr 21 14:03:34 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
*** erikmwilson has joined #openstack-meeting-314:03
mosheleajo: I can send ireanb sms14:03
ajomoshele, thanks :)14:03
ajo#topic Announcements14:04
*** openstack changes topic to "Announcements (Meeting topic: neutron_qos)"14:04
sc68calajo: pong14:04
ajohi sc68cal  :)14:04
ajo#link #link https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint14:04
ajowoops :) double link :)14:04
ajo#link https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint14:04
*** sigmavirus24_awa is now known as sigmavirus2414:04
ajoI guess most of you are already aware of the qos code sprint Red Hat is proposing, feel free to signup if you believe you can come, or collaborate remotely.14:05
*** rmschn has joined #openstack-meeting-314:05
*** rmschn has quit IRC14:05
*** egallen has joined #openstack-meeting-314:05
ajobut, we have specs to get merged, and a lot to agree before a code sprint can happen :)14:05
ajoany question about it? :)14:06
ajook, let's move on14:06
mosheleajo: irenab will join shortly14:06
irenabhi14:06
ajohi irenab !! :)14:06
irenabsorry for being late14:07
ajonp :)14:07
ajojust in time14:07
ajo#topic updated spec14:07
*** openstack changes topic to "updated spec (Meeting topic: neutron_qos)"14:07
ajo#link https://review.openstack.org/#/c/88599/14:07
ajoI have updated sc68cal spec, with a few ideas about splitting the initially proposed model14:07
ajointo QoSProfiles, composed of QoSPolicies14:08
*** emagana_ has quit IRC14:08
*** rmschn has joined #openstack-meeting-314:08
*** emagana has joined #openstack-meeting-314:08
*** carl_baldwin has joined #openstack-meeting-314:08
ajofor ratecontrol/bandwidth limiting, may be it's too much, but I wanted to make the models/api to grow without big changes, or breaking backward compatibility of the API ends in the future.14:08
*** jcoufal_ has quit IRC14:08
aveigaajo: what's the problem you're attempting to solve with that setup?14:08
*** armax_ has quit IRC14:08
ajoaveiga, for example, there were concerns in previous models about applying several profiles to one port/network14:09
*** armax has joined #openstack-meeting-314:09
ajoaveiga, for example, you could like to mark packets + bandwidth limit them...14:09
ajoor you may want (in the future), to be able to write QoSPolicy rules which target traffic selectively14:09
sc68calajo: cbits and vhoward- from Comcast are also from Comcast and interested in the QoS work14:10
ajofor example... tcp.port=8014:10
ajoaveiga, does it sound reasonable?14:10
aveigaajo: I see where you want to go with this14:10
ajoaveiga, something like security groups, but for applying QoS policies to different types of traffic14:10
aveigayou can have a slective overload of that setup, where ports on tenant x by default have forced ratelimiting, but maybe they also want to add a mark for some traffic14:11
irenabajo: on same neutron port, right?14:11
ajoirenab correct,14:11
aveigathe fun part is the collapsing logic, because if they're doing different things it's fine, but some things are one property only or may be mutually exclusive14:11
ajoexactly14:11
aveigaI suppose that's an implementation detail though14:11
aveigawe need a way to provide the feedback on failure, though14:12
ajoI was going to get into that, we may need some sort of logic to check we can add an extra rule that works with previous ones in the profile14:12
irenabaviega: agree, and this may sometimes depend on QoS backend implementation14:12
aveigait would be a poor UX to allow them to try setting two DSCP marks against the same port withotu a way to tell them why it won't work or which one was actually applied14:12
ajoaveiga, but for a first iteration, it seems only ratecontrol/bandwidth limiting is getting accepted by neutron-drivers (to control how we design/grow the feature),14:13
*** TalA_ has joined #openstack-meeting-314:13
aveiga:(14:13
ajoaveiga, anyway, I'm all for it, if we finish the first steps,14:13
aveigaok14:13
ajolet's go ahead and start developing the U/S dscp part14:13
irenabajo: what is your intention regarding ref implementation?14:13
ajoit's probably not going to be too complicated with comcast code + the bare bones in place14:13
aveigaas long as we can get the api nailed down, we can port our stuff over and merge later14:14
ajoaveiga, sounds good, may be, if you want you can work in a follow up spec to the current one, to extend with dscp, so we know how it looks14:14
vhoward-yes data model and api would like to see that solidified in spec, we can help14:15
irenabI think if API will open enough, different plugins may have various options to support, sometimes richer than ref implementation14:15
ajoirenab, about ref implementaion, I have another point in the meeting, give me 1 min :)14:15
ajoirenab, I agree14:15
vhoward-+1 irenab14:15
ajothat comes to another question,14:15
ajowe're defining the bandwidth limiting fields,14:16
ajobut do you believe we should accept, other fields?14:16
irenabajo: at API level?14:16
ajoI guess, accepting different fields without control could lead to non interoperable policy rules14:17
ajoirenab, talking about the parameters dict: https://review.openstack.org/#/c/88599/7/specs/liberty/qos-api-extension.rst14:17
ajoline 12514:17
ajoI have defined as much as I can think of, but for example, max_latency_ms can't be applied to ovs (AFAIK) but it was proposed on previous versions of the spec.14:18
ajosc68cal, do you recall why?14:18
irenabajo: In my opinion there is a difference if we require this at API level or at the implementation/db level14:19
*** wojdev has quit IRC14:20
ajoirenab, what do you mean14:20
ajo?14:20
*** marun has joined #openstack-meeting-314:20
sc68calajo: That was proposed in the spec for the linux bridge implementation for rate limiting14:20
ajoah, ok API / vs impl14:20
sc68calsince it was using tc as the driver14:20
aveigait might be a good idea to abstract out the api calls as high as we can14:20
*** wojdev has joined #openstack-meeting-314:20
ajoaha, sc68cal , so tc supports latency settings14:20
sc68calajo: yes14:21
irenabThere are validations that can be done at API level, so from API perspective, I think there should be ‘key’, ‘val’  pairs14:21
sc68calaveiga: the problem with making this all abstact is how do we validate14:21
*** wojdev has quit IRC14:21
aveigayup14:21
ajoI agree with aveiga , we may abstract the parameters as much as we can, but...14:21
irenabbut where the implementation is involved , we can check the supported ‘keys’ only14:21
ajoevery implementation is a bit different14:21
ajoirenab, that makes sense,14:21
ajomay be we can check the default keys, and leave room for non-default ones14:22
matrohonbackend should report what fields they support?14:22
ajoso every vendor could leverage extra capabilities14:22
irenabin my opinion we should not close API for only current known list14:22
irenabmatrohon: +114:22
ajoirenab, ok, we may need to check that with neutron core/drivers to see if it's ok, are we doing such thing in other places?14:22
ajomatrohon, or we can pass parameters to backend for checking14:23
irenabI gues extra_dhcp_opts are similar in this sense14:23
matrohonit looks like extension suppport for plugins14:23
ajoaha14:23
ajo#action ajo allow extra settings in the parameters dictionary to be checked by the plugin/specific implementation.14:24
matrohonajo : calling a backend during a transaction should be avoided14:24
ajomatrohon, true14:24
ajoin that case, we can check available parameters with backend at start14:25
aveigaextensions could be interesting, is it possible to pass an object as the value in a k/v pair? That way you might be able to provide, say, min and max bandwidth and min/max latency in the "bandwidth" key14:25
ajobut ok, I guess this is all implementation detail we can discuss over the spec.14:25
matrohonajo : +114:26
ajois it ok to discuss the details over the spec?14:26
ajothanks matrohon14:26
cbitsajo +1 on flexable and letting the backend define the validation.14:26
ajo#topic reference implementation14:26
*** openstack changes topic to "reference implementation (Meeting topic: neutron_qos)"14:26
ajo(irenab, I had another point later for the service-plugin vs mechanism-driver or other ways...)14:27
irenabajo: ok :-)14:27
ajoabout reference implementation, I guess it should go in ml2-ovs, I know irenab you were interested in ml2-sriov, not sure if it's yet the case14:27
*** shwetaap has joined #openstack-meeting-314:28
ajosc68cal, in the previous spec, there was somebody proposing ml2-linuxbridge which I guess makes sense too if we have people willing to do it14:28
irenabajo: I think SR-IOV is  in moshele hands now14:28
ajomoshele +114:28
ajo:)14:28
sc68calajo: yes, so we would have a ml2-lb and ml2-ovs implementation ready for revival14:28
vhoward-we were interested in ml2-ovs also14:28
vhoward-the mech driver14:29
sc68calI think there was also a ml2-ovs rate limit impl. floating around too14:29
mosheleajo: I will do the ml2-sriov14:29
irenabwaht QoS functionality is going to be implemented? only rate limit?14:29
ajoirenab, I recall your design where a few parts could be reused across several ml2-agents, if I didn't get it wrong14:29
irenabajo: right. The idea was to extend existing l2 agents in a reusable way14:30
ajoat least ratelimit, yes14:30
ajothat's the recommendation from neutron drivers14:30
ajoand PTL14:30
ajoif we put testing in place, + a good design, we have a good amount of work ahead,14:30
ajobut I'm all for writing more policy types if we finish early14:31
vhoward-irenab: no we are looking to mark traffic not just rate limit14:31
matrohonirenab, ajo : are speaking about a modular agent revival?14:31
irenabmatrohon: related to this, right14:32
cbitsWe are also looking to filter traffice based on DSCP marking14:32
*** jckasper has joined #openstack-meeting-314:32
*** mrunge has joined #openstack-meeting-314:32
*** Networkn3rd has quit IRC14:32
mosheleajo: for the ml2  extension_manager we will need this https://review.openstack.org/#/c/162648/ change as well14:32
vhoward-we are looking to blueprint ml2-ovs mech driver for qos so we will keep you all in the loop on that to what cbits said14:32
irenabcbits: with upstream OVS impementation?14:32
*** Networkn3rd has joined #openstack-meeting-314:32
cbitsyes14:33
ajomoshele, It looks like it eventually get merged as it's fixing a bug, right?14:33
ajoit will14:33
irenabfrom the API perspective, it makes ense to have all these options (and maybe more) available from the beginning, while only subset can be implemented in the first iteration14:34
*** shwetaap1 has joined #openstack-meeting-314:34
ajoirenab, which options?14:34
mosheleajo: yes it was freezed because of kilo, but we will push it now14:34
irenabmentioned by cbit14:34
ajocbits, ack :)14:35
irenabDCSP marking,..14:35
ajoI missed cbit commit about DSCP filtering14:35
sc68calcbits: that's out of scope14:35
aveigafiltering is an SG change, not a QoS change14:35
ajoit's related, looks more like a security group change, correct14:35
aveigaor rather, port security14:35
sc68calthat's an extension that you guys to the sec group API, that you're going to have to carry14:35
cbitscool14:36
ajothey could propose an extension to the security groups API to have a dscp field U/S14:36
ajo#topic access control / ACLs14:36
cbitsajo +114:36
*** openstack changes topic to "access control / ACLs (Meeting topic: neutron_qos)"14:36
ajoin previous "pre-meeting" we discussed about access control to QoS profiles14:37
sc68calajo: extension of an extension. yaaay. :)14:37
ajosc68cal or just update the extension :)14:37
*** shwetaap has quit IRC14:37
irenabajo: kevin updated the RBAC  spec https://review.openstack.org/#/c/132661/ to be generic14:37
ajowe believe in the feature we could leverage the design of RBAC to control QoS profiles access by tenants14:37
ajo#link https://review.openstack.org/#/c/13266114:37
ajoyeah, I saw it, great news :)14:38
ajoI need to read it through, I didn't have time yet14:38
sc68calI think that's very good news, but let's not stretch ourselves too much for first iteration14:38
*** Networkn3rd has quit IRC14:38
ajobut, for this cycle, there was a genera agreement, that having the admin controling the policies/rules setting to ports/networks itself14:38
irenabajo: It looks suitable for managing QoS profiles14:38
ajoand disallow it on tenants for now14:38
sc68calajo: admin/owner?14:39
*** Networkn3rd has joined #openstack-meeting-314:39
ajoI'd say admin only for now, but it's just a matter of configuring the policies14:39
ajofor example, you don't want tenants randomly making bandwidth changes to modify a setting done by admin14:39
sc68calajo: true, but we can do checks for if the network is shared14:40
ajobut, if anybody needs a change on that, they only need to modify /etc/neutron/policy.json14:40
sc68calthen disallow14:40
sc68calajo: good point.14:40
ajosc68cal, we can think of probably common defaults, but everybody is going to make different uses, I guess14:41
ajosome operators may not want to rely on admin to set profiles14:41
sc68calajo: true, but you make a good point, policy.json is easy to change14:41
ajoand some operators may not want tenants to modify / set new profiles, I guess14:41
sc68calajo: and hey, it's actually getting some documentation, finally!14:41
ajosc68cal, we could provide instructions on how to do it14:41
ajosc68cal, really? :D :-)14:41
ajothat's good14:41
ajook14:42
ajoa tiny topic before we jump into a bigger one14:42
ajo#topic ratelimiting vs ratecontrol14:42
*** openstack changes topic to "ratelimiting vs ratecontrol (Meeting topic: neutron_qos)"14:42
ajoI was thinking that ratecontrol "type" could be used for both min/max rate if I'm not missing anything14:42
ajonot sure if we need separate types to define traffic guarantees14:43
ajoor just have a "min" field, specifying what's the minimum bandwidth we're providing on a port14:44
ajodoes it sounds reasonable/unreasonable?14:44
sc68callittle fuzzy on difference14:44
sc68calcare to educate?14:44
ajofrom the ovs/linux-htb point of view, having it together, makes the "min" parameter meaningful, and we can control priorities over ports/bandwidth..14:45
ajook, I see no -1's at least :-), I will change it on the spec, but feel free to complain or ask me to change it back14:46
*** thomasem has quit IRC14:46
ajolet's move on14:46
ajo#topic service-plugin, or simple mechanism driver14:46
*** openstack changes topic to "service-plugin, or simple mechanism driver (Meeting topic: neutron_qos)"14:46
ajoirenab, do you want to lead this one?14:46
irenabajo: ok14:46
ajothank you :)14:47
irenabthe question is if the QoS profile/policy management should get its own service or be part of the Core plugin14:47
irenabI tend to see it belongs to service plugin, potentially with different providers14:48
sc68calNot sure if this is relevant, but I'd say we should get the API extension into core then have our own repo to rapidly iterate14:48
sc68calsimilar to all the *aaS repos14:48
irenabsc68cal: thats what I had in mind14:49
sc68calok, so guess I'm in the service plugin camp14:49
ajoWell, I'm not 100% convinced we need a separate repo here, at least for the start14:49
irenabthe extension definition can be hosted in the same repo as well14:49
ajoI'm happy about the design advantages that come with making it a service plugin,14:50
*** mattfarina has joined #openstack-meeting-314:50
ajoand it's tightly coupled to the reference implementation of the ovs-agent which lives on tree14:50
sc68calirenab: are you sure? last I checked the core repo still had the extensions for all the *aas stuff14:50
sc68calor was that just a procedural thing, where they hadn't split them out yet14:50
irenabsc68cal: not for new introduced ‘services’, like l2gw14:50
matrohonsince it apply to core resources, I feel it's more in the scope of Core plugin extension14:51
ajomatrohon, that's my feeling too14:51
irenabI guess its just easier to maintain both api and impementation together, but do not have strong opinion where to put it.14:51
ajoirenab, sc68cal , could you enumerate advantages of making it a service plugin instead?14:51
sc68calajo: Ideally it'd allow us to iterate in our own repo, have our own cores and such14:52
ajowe're basically setting parameters of the networks and ports14:52
sc68calajo: the trouble is - as you pointed out, the agents14:52
*** rmschn has quit IRC14:52
ajosc68cal, yes, but I believe it's going to become an important feature for many telcos/operators, and it modifies parameters of basic resources like ports,14:53
*** marun_ has joined #openstack-meeting-314:53
irenabajo: I think mostof the advanced services eventually apply to core resources14:53
ajoI'm not sure if that fits on the category of an advanced service living on a seperate repository14:53
ajoirenab, well, they make use of them...14:54
ajobut do they modify them?14:54
ajomay be FwAAs modifies routers,14:54
*** marun has quit IRC14:54
irenabbut all the policies/profiles management is quite stand alone logic14:54
*** marun_ is now known as marun14:54
sc68calLet'14:54
*** egallen has quit IRC14:54
sc68calWorst case we can do a little research on the service plugin14:54
irenabwe eventually map port to some profile UUID14:54
sc68calright now most of the existing code ties right into the core14:55
ajoirenab, sc68cal , matrohon , what do you think about looping in cores in next neutron meeting, and see how they think about it14:55
ajo?14:55
sc68calajo: good idea14:55
sc68calor a ML thread14:55
ajoML should work too14:55
sc68calml thread might be better14:55
ajoprobably better14:55
ajosc68cal +114:55
irenabI would vote for service plugin for clean separation of concerns, quicker iterations14:55
matrohonyou'll have to have a dedicated MD for the service plugin to be aware of any changes on a port/networks?14:56
irenabthe recent spirit to spin every possible part out :-)14:56
matrohonarmax introduced a registry mechanism that can be reused too14:56
ajoyes14:56
irenabmatrohon: callback?14:56
ajomatrohon, the callbacks, right?14:56
ajo:D14:56
sc68calirenab: agreed - we just have to figure out how to get the agents to work with the qos service with no code changes to core14:57
matrohonyep14:57
ajosc68cal, fwaaS extends the l3-agent, reight?14:57
matrohonsc68al :  this is the scope of the module agent work in progress...14:57
irenabwe tried to solve it in some AgentExtension way14:57
ajobut I believe that way is not very sustainable14:57
ajowe may need extending the agents in a more dynamic way14:57
sc68calajo: I'd have to check how they do that14:57
*** stevemar has joined #openstack-meeting-314:58
matrohoncurrently, there is no way to extend agent (LB or OVS)14:58
sc68cali know vpnaas just runs a whole new agent that inherits from the l3 agent14:58
sc68calit14:58
sc68calis nasty14:58
ajoyes, matrohon , correct14:58
matrohonthe l3agent is easily extensible since kilo14:58
ajook14:58
matrohonbut not the l2agent14:58
ajolet's talk about it in the mail thread14:58
ajo1 min left :)14:58
irenabmatrohon: sounds about the right time to make a change :-)14:58
matrohonirenab : +100014:59
ajomy opinion is more on keeping it to the core, but I'll make an impartial thread start, so we can discuss freely14:59
ajook14:59
matrohonrosellab has been very active on the agent, but none of her improvment has merge in kilo14:59
sc68calcore is tough, they're splitting reference from neutron14:59
ajoI also had a request from salv-orlando , to share our proposed API with operators and telcos14:59
ajoto get feedback14:59
sc68calfor the neutron-lib work14:59
ajosince people complains generally about neutron API usability14:59
irenabajo: souds great, the earlier the better15:00
* sc68cal trying to get as many words in 60 seconds15:00
ajo:D :D15:00
salv-orlandoit's not a strict requirement. but it is to avoid previous mistakes15:00
salv-orlandolike the one we made with load balancing apis15:00
ajosalv-orlando +115:00
sc68cal++15:00
* sc68cal pokes aveiga 15:00
*** MarkAtwood has joined #openstack-meeting-315:00
irenabajo: any work items for next week?15:00
ajook, I believe we shall free the channel15:00
aveigasorry, catching up post power outage15:00
sc68calaveiga: you're our telco guinea pig15:01
ajolet's discuss over #openstack-neutron-qos15:01
ajo#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Tue Apr 21 15:01:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-21-14.03.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-21-14.03.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-04-21-14.03.log.html15:01
ajosorry, I didn't want to take over the meeting channel15:01
vhoward-thanks for running15:01
cbitscheers!15:02
ajoif you have some time we can think of next work items on the -qos channel15:02
*** cbits has left #openstack-meeting-315:02
*** sfinucan has joined #openstack-meeting-315:02
ajothankss everybody! ;)15:02
*** cbits has joined #openstack-meeting-315:02
*** aveiga has left #openstack-meeting-315:03
*** TalA_ has left #openstack-meeting-315:03
*** edleafe is now known as not_edleafe15:05
*** not_edleafe is now known as edleafe15:05
*** cbader has joined #openstack-meeting-315:05
*** egallen has joined #openstack-meeting-315:05
*** cbits has left #openstack-meeting-315:08
*** moshele has left #openstack-meeting-315:09
*** hichihara has quit IRC15:10
*** jaypipes has quit IRC15:11
*** mestery has quit IRC15:11
*** mestery has joined #openstack-meeting-315:12
*** rmschn has joined #openstack-meeting-315:12
*** rmschn has quit IRC15:13
*** baoli_ has quit IRC15:15
*** yamahata has quit IRC15:16
*** julim has quit IRC15:16
*** baoli has joined #openstack-meeting-315:17
*** julim has joined #openstack-meeting-315:18
*** hallyn_ has joined #openstack-meeting-315:23
*** hallyn_ has left #openstack-meeting-315:23
*** hallyn_ has joined #openstack-meeting-315:23
*** iovadia has quit IRC15:24
*** gsagie_ has joined #openstack-meeting-315:26
*** egallen has quit IRC15:30
*** Sukhdev has quit IRC15:31
*** Swami has joined #openstack-meeting-315:32
*** david-lyle has quit IRC15:36
*** amotoki has quit IRC15:41
*** sfinucan has left #openstack-meeting-315:41
*** amotoki has joined #openstack-meeting-315:43
*** amotoki has quit IRC15:43
*** bpokorny has joined #openstack-meeting-315:46
*** baoli has quit IRC15:47
*** baoli has joined #openstack-meeting-315:49
*** scheuran has quit IRC15:50
*** matrohon has quit IRC15:51
*** baoli has quit IRC15:52
*** mattgriffin has quit IRC15:52
*** cbouch has quit IRC15:52
*** baoli_ has joined #openstack-meeting-315:53
*** mattgriffin has joined #openstack-meeting-315:54
*** hallyn_ has left #openstack-meeting-315:58
*** armax has left #openstack-meeting-315:58
*** Sukhdev has joined #openstack-meeting-315:58
*** armax has joined #openstack-meeting-316:00
*** sarob has joined #openstack-meeting-316:00
*** aduarte has joined #openstack-meeting-316:00
*** eghobo has joined #openstack-meeting-316:01
*** armax has left #openstack-meeting-316:01
*** armax has joined #openstack-meeting-316:02
*** david-lyle has joined #openstack-meeting-316:02
*** baoli_ has quit IRC16:02
*** baoli has joined #openstack-meeting-316:04
*** mrunge_ has joined #openstack-meeting-316:04
*** sahid has joined #openstack-meeting-316:05
*** mrunge has quit IRC16:06
*** natorious has quit IRC16:08
*** vishwanathj has quit IRC16:14
*** vishwanathj has joined #openstack-meeting-316:15
*** egallen has joined #openstack-meeting-316:17
*** safchain has quit IRC16:18
*** vishwanathj has quit IRC16:19
*** Sukhdev has quit IRC16:22
*** yamamoto has quit IRC16:22
*** rhagarty_ has quit IRC16:25
*** rhagarty has quit IRC16:25
*** iben_ has joined #openstack-meeting-316:27
*** mwang2 has joined #openstack-meeting-316:28
*** jaypipes has joined #openstack-meeting-316:30
*** jlvillal has quit IRC16:30
*** jlvillal has joined #openstack-meeting-316:30
*** gsagie_ has quit IRC16:34
*** absubram has left #openstack-meeting-316:34
*** vishwanathj has joined #openstack-meeting-316:39
*** mrunge_ has quit IRC16:39
*** egallen has quit IRC16:42
*** e0ne has quit IRC16:45
*** jtomasek has quit IRC16:47
*** seizadi has joined #openstack-meeting-316:52
*** vishwanathj has quit IRC16:52
*** Piet has joined #openstack-meeting-316:52
*** vishwanathj has joined #openstack-meeting-316:54
*** vishwanathj has quit IRC16:58
*** jwy has joined #openstack-meeting-317:00
*** mwang2 has quit IRC17:01
*** julim has quit IRC17:01
*** sarob has quit IRC17:02
*** thinrichs has joined #openstack-meeting-317:02
thinrichsHi all17:02
thinrichs#startmeeting CongressTeamMeeting17:02
openstackMeeting started Tue Apr 21 17:02:27 2015 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:02
openstackThe meeting name has been set to 'congressteammeeting'17:02
thinrichsWalking to another room….17:03
*** vishwanathj has joined #openstack-meeting-317:03
*** shivharis has joined #openstack-meeting-317:03
*** julim has joined #openstack-meeting-317:04
*** ivar-lazzaro has joined #openstack-meeting-317:04
thinrichsAnyone here?17:04
jwyhi17:05
thinrichsjwy: hi17:05
*** Sukhdev has joined #openstack-meeting-317:05
thinrichsLet's do some status updates and hope others join us.17:05
thinrichs#topic status17:05
*** openstack changes topic to "status (Meeting topic: CongressTeamMeeting)"17:05
thinrichsjwy: want to go first?17:06
*** vishwanathj has quit IRC17:06
*** vishwanathj has joined #openstack-meeting-317:06
jwypolicy creation ui has been merged. everyone - please try it out and open bugs if you find any, and let me know if you have any other feedback/suggestions17:07
*** seizadi1 has joined #openstack-meeting-317:08
*** seizadi has quit IRC17:08
jwyRajdeep's data sources status table has also been merged17:08
*** vishwanathj has quit IRC17:08
jwyshows up on the data sources page17:08
*** david-lyle has quit IRC17:08
*** vishwanathj has joined #openstack-meeting-317:08
thinrichsjwy: any progress on writing tests for the rule-creation code?  Actually—are there usually tests for horizon code?17:09
jwythinrichs: there are usually tests for the horizon code. writing those next thing17:10
thinrichsGreat.17:10
thinrichsIt's good that we have solid coverage of the API in Horizon now.17:10
thinrichsConsumption is really important for policy.17:11
jwyand Yali's func spec is about done (#link: https://review.openstack.org/#/c/168539/)17:11
jwyfor policy abstraction17:11
jwythat sums it up for the ui stuff17:11
thinrichsjwy: Yali has been working on that for a while.  Think she'd be interested in presenting the idea during the design session at the summit?17:11
thinrichsI'm thinking a 5 minute preso.17:11
jwythinrichs: she won't be able to make it to the summit, unfortunately. she said one of her colleagues who is familiar with the idea will be there. i can ask if he can talk about it17:12
jwyooh one more thing -17:12
thinrichsI think that's a good idea.17:12
*** Sukhdev has quit IRC17:12
jwyi talked with someone from murano-dashboard about what they're doing with the code now that they're officially part of openstack17:13
jwyhe said they're not sure, but he proposed the topic for the horizon design summit17:13
thinrichsThat's a good thought—what do we do with devstack/horizon/etc. contributions now?17:14
jwyright17:14
thinrichsLet's make sure we look into that, esp. at the summit.17:14
jwythere was brief discussions in one of the horizon irc meetings about keeping the horizon code for new projects in separate repos still and having both horizon and project reviews required for patches17:14
*** MaxV has quit IRC17:14
jwynothing decided yet17:14
jwyok i'm done now17:15
thinrichsThanks!17:15
thinrichsA few things from me then.17:15
thinrichsWe'll tag kilo-3 today with Janet's UI commit.  It's the right time-frame, and we haven't found any major bugs.17:16
thinrichsAnd then at the end of the month we'll do our official release.17:16
thinrichsWe're still in feature freeze, but soon I expect us to branch and start letting features into master again.17:17
thinrichsOnce we branch, bugfixes will need to go both into master and into the branch.17:17
thinrichsI'll send out details on the ML once that happens.17:17
thinrichsI think that's mainly it for me.17:19
thinrichsAnyone else have a status update?17:19
*** sarob has joined #openstack-meeting-317:20
thinrichsI know ayip has been fixing a bug or two and working on the HA feature.17:20
thinrichsstevenldt has been continuing to work on action-execution.17:20
thinrichsWe also have an early contributor working on the Heat datasource driver.17:21
thinrichshttps://review.openstack.org/#/c/175182/17:21
thinrichsZhenzan is working on a bug in the policy engine:17:21
thinrichshttps://review.openstack.org/#/c/175695/17:22
thinrichsJohn Strassner is continuing to improve the grammar for the datalog policy language.17:22
thinrichshttps://review.openstack.org/#/c/174476/17:22
thinrichsWe're iterating through arosen's datasource notification patch as well (to enable on-demand datasource driver polling).17:23
thinrichshttps://review.openstack.org/#/c/169526/17:23
thinrichsAll told, good stuff here at the end.17:23
thinrichsOkay, it seems that people are busy this week, so we'll end here.17:24
thinrichsMy one request: use the extra 30 minutes to test.  :)17:24
thinrichsjwy: anything else?17:24
jwythinrichs: nope17:25
thinrichsThanks all!  See you next week.17:25
thinrichs#endmeeting17:25
*** seizadi has joined #openstack-meeting-317:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:26
openstackMeeting ended Tue Apr 21 17:25:58 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-04-21-17.02.html17:26
*** seizadi1 has quit IRC17:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-04-21-17.02.txt17:26
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2015/congressteammeeting.2015-04-21-17.02.log.html17:26
*** stevenldt has joined #openstack-meeting-317:27
*** jwy has left #openstack-meeting-317:28
*** stevenldt has left #openstack-meeting-317:32
*** VW_ has quit IRC17:32
*** e0ne has joined #openstack-meeting-317:33
*** e0ne is now known as e0ne_17:33
*** VW_ has joined #openstack-meeting-317:34
*** nkrinner has quit IRC17:34
*** VW_ has quit IRC17:34
*** e0ne_ is now known as e0ne17:34
*** VW_ has joined #openstack-meeting-317:35
*** sarob has quit IRC17:35
*** thinrichs has left #openstack-meeting-317:39
*** e0ne is now known as e0ne_17:44
*** e0ne_ is now known as e0ne17:45
*** ivar-laz_ has joined #openstack-meeting-317:46
*** ivar-laz_ has quit IRC17:46
*** mwang2 has joined #openstack-meeting-317:47
*** ivar-laz_ has joined #openstack-meeting-317:48
*** ivar-lazzaro has quit IRC17:49
*** e0ne is now known as e0ne_17:51
*** sarob has joined #openstack-meeting-317:54
*** sergef has quit IRC17:54
*** mwang2 has quit IRC17:56
*** e0ne_ has quit IRC17:56
*** iben_ has quit IRC17:57
*** mwang2 has joined #openstack-meeting-317:57
*** vishwanathj has quit IRC17:58
*** vishwanathj has joined #openstack-meeting-317:59
*** melwitt has joined #openstack-meeting-318:00
*** btully has quit IRC18:02
*** btully has joined #openstack-meeting-318:03
*** vishwanathj has quit IRC18:03
*** iben_ has joined #openstack-meeting-318:07
*** roxanaghe has joined #openstack-meeting-318:08
*** seizadi has quit IRC18:09
*** seizadi has joined #openstack-meeting-318:10
*** e0ne has joined #openstack-meeting-318:10
*** yamamoto has joined #openstack-meeting-318:10
*** sahid has quit IRC18:14
*** VW_ has quit IRC18:15
*** yamamoto has quit IRC18:15
*** notmyname has quit IRC18:16
*** johnthetubaguy is now known as zz_johnthetubagu18:16
*** notmyname has joined #openstack-meeting-318:17
*** VW_ has joined #openstack-meeting-318:21
*** sergef has joined #openstack-meeting-318:21
*** seizadi has quit IRC18:29
*** seizadi has joined #openstack-meeting-318:29
*** alexsyip has joined #openstack-meeting-318:32
*** sarob has quit IRC18:37
*** david-lyle has joined #openstack-meeting-318:39
*** sarob has joined #openstack-meeting-318:41
*** baffle has joined #openstack-meeting-318:43
*** dtroyer has joined #openstack-meeting-318:44
*** Piet has quit IRC18:45
*** david-ly_ has joined #openstack-meeting-318:46
*** david-lyle has quit IRC18:46
*** sarob_ has joined #openstack-meeting-318:46
*** sarob has quit IRC18:50
*** wuhg has quit IRC18:59
*** stevelle has joined #openstack-meeting-319:00
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Apr 21 19:00:25 2015 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
*** jamielennox has joined #openstack-meeting-319:00
briancurtinif you're around for the SDK meeting, say hi19:00
sigmavirus24o/19:00
sigmavirus24erm "hi"19:00
briancurtin(or if i got timezones wrong, shame me...i'm in CA today)19:00
etoewso/19:01
dtroyero/19:01
briancurtintwo things on the agenda to discuss and then whatever comes up after that: https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2015-04-21_1900_UTC19:01
stevelleo/19:01
*** terrylhowe has joined #openstack-meeting-319:02
terrylhoweo/19:02
briancurtin#topic wait_for_status19:02
*** openstack changes topic to "wait_for_status (Meeting topic: python-openstacksdk)"19:02
*** vishwanathj has joined #openstack-meeting-319:02
*** eghobo has quit IRC19:02
briancurtin#link https://review.openstack.org/#/c/174980/19:02
etoewsterrylhowe: did you have a chance to read my answers to your comments?19:02
terrylhoweno19:02
*** vishwanathj has quit IRC19:03
terrylhowesorry, lots of meetings lately19:03
etoewsi understand ;)19:03
etoewswanna take a minute now?19:03
baffleo/19:03
*** melwitt has quit IRC19:03
*** vishwanathj has joined #openstack-meeting-319:03
terrylhoweyeh19:03
briancurtinetoews: fwiw i dont like server_ -- i think value is the best we're going to get to not shadow and not do other weird-ish things19:03
etoewsya. server_ kind of seemed like an abuse of trailing underscore.19:04
*** melwitt has joined #openstack-meeting-319:04
dtroyerjust looking at it for the first time here, 'value' is not too jarring, especially once you see it as a pattern everywhere.19:05
briancurtini dont really love value, but after applying a lot of stuff around the services, having a consistent name reads pretty well19:05
briancurtinyep19:05
* dhellmann lurks while continuing to try to send release notes19:05
*** erikmwilson has quit IRC19:06
*** erikmwilson has joined #openstack-meeting-319:06
terrylhoweThe ‘value’ thing is so generic, but I don’t have a better suggestion atm not a big deal19:06
terrylhoweanyway, none of those comments are huge, more topics of discussion just like doing a wait_for method vs wait_for_status19:07
*** carl_baldwin has quit IRC19:07
*** carl_baldwin has joined #openstack-meeting-319:07
*** carl_baldwin_ has joined #openstack-meeting-319:08
briancurtini'd love to call it resource, but then we run into shadowing potential again (merely potential, since calls into the resource module are moving out of the proxy classes and into the proxy base)19:08
*** vishwanathj has quit IRC19:08
etoewsbut we'll go with value for now19:09
briancurtinit just wouldn't work immediately. if it turns out to be something we want to change, that's probably fine. value for now seems like the best bet19:09
etoewswhat does everyone think of resource.Resource._wait_for_status()19:09
briancurtinwhy would it be private?19:10
etoewsread #link https://review.openstack.org/#/c/174980/4/openstack/resource.py19:10
* briancurtin reading19:10
etoewsmy Apr 20 5:07 PM comment19:10
dtroyerFWIW, we're planning to sketch out a top-level OSC command that will do exactly this so writing status loops in shell is no longer a thing, so I'd love to be able to eventually use this method19:11
terrylhowemakeing wait_for a method of Resource makes a lot of sense if we made it generic, not so stuck on the status attribute19:11
terrylhoweI think I’m fine leaving it out of the class if we are going to have it associated with the attribute status19:12
briancurtinetoews: i think i said something earlier about it being a function, which I think handles this purpose better than it does to make it private19:12
etoewsterrylhowe: did you read my last comment on resource.py19:12
terrylhoweyeh19:12
terrylhoweoh, I thought you were talking about something else, hold on19:13
briancurtiniirc libcloud has it as a method but it's on compute-specific classes, not in the base. waiting on status is too specific to be in the base imo19:14
briancurtin(two abbreviations in one message, everyone takes a drink)19:14
terrylhoweyeh, I’m for leaving it out of the class19:14
etoewsokay19:15
*** Rockyg has joined #openstack-meeting-319:15
etoews#agreed resource.wait_for_status()19:15
etoewsterrylhowe: did you still want to discuss a generic wait_for() ?19:16
terrylhowenope19:17
etoewsokay. we'll just go with resource.wait_for_status() then.19:17
briancurtin#topic common get method19:17
*** openstack changes topic to "common get method (Meeting topic: python-openstacksdk)"19:17
*** eghobo has joined #openstack-meeting-319:18
briancurtinso now that the deletes are through, there's an implementation of get at #link https://review.openstack.org/#/c/164351/19:18
etoewsterrylhowe: i also wanted to ask you about your comment on https://review.openstack.org/#/c/174980/4/openstack/tests/unit/test_resource.py but that can wait until after or in #openstack-sdks19:18
briancurtincan talk about that now if you want, i jumped the gun19:18
*** david-ly_ has quit IRC19:18
etoewsterrylhowe: can you give me a quick idea of what you had in mind?19:19
terrylhoweI was just thinking make some FakeResource in the test file so the test isn’t pulling in stuff it doesn’t need /that might change19:19
briancurtinyeah, i think test_resource should probably not involve other actual resources and just build on the FakeResource that is already there, or something else like that19:21
terrylhowenot a big deal to me, but seems like it might be safer to not have a dependency on v2.server in test_resource19:21
etoewsokay. i'll look into that. thx.19:21
*** roxanaghe has quit IRC19:22
etoewsonto the common get method19:22
briancurtinback to the common get -- perhaps i should break out that change into one or more other changes because that review creates a path that would remove the need to have find at all by leveraging kwargs passed into a  list method, and sending in the appropriate query name/value to do the find19:23
terrylhoweOn the base get method, I really want a get method that does an HTTP get19:23
briancurtinterrylhowe: and it does that, but it handles the resource-specific logic for finding what you've sent as well. if you give it something that does exist, it just does a get and gets it. if you give it some ID or name that you want to find, it'll find it (or fail to find it) -- having to do two different methods to attempt to retreieve one thing doesn't feel19:25
briancurtintoo nice, since you then have to do a try/except dance19:25
dtroyerI think there is value in having simplified methods for simple things and a fallback to the generalized methond (find*) when required.19:25
dtroyerso a simple get() in parallel with a flexible find() seems good to me19:25
dtroyereven though they are both GET requests under the hood19:26
briancurtindtroyer: as in get uses find, or that get only gets (or fails to get) a singular resource?19:26
*** egallen has joined #openstack-meeting-319:26
dtroyerI wouldn't have get() use find(), I'd make them peers19:26
briancurtini guess i'll have to look back into how to do that. we can't really make a generic find because every resource does something very different, between query params and filters, but i'll restructure the proposal to handle it with both being separate19:28
etoewswhat's the use case for find? to find by name?19:28
etoewsit's a bit weird to me that the docs say "Find a resource by its name or id."19:29
dtroyerthat's one, also finding substring/regex matches (where possible, or done locally from list return)19:29
etoewsif i have the id, i'm going to do a get19:29
terrylhowefind was modeled after the find in OSC19:29
briancurtini dont really know the find case other than that it has existed in the past in other places, which is why i tried to handle it in get because you want to get a resource that may or may not exist19:29
terrylhoweit does a find by name_or_id that was the original intention at least19:29
dtroyerfind() is generally more complicated, with possibly multiple server requests doe to name->id lookups in some cases19:30
dtroyerget() is (in my mind) basically requests.get() + auth and what else Transport adds19:30
briancurtinyeah, there's often no way to do a find without retrieving everything and filtering locally on the response, especially if you want to do substring/regex when it's not supported (which it mostly isnt from what i can tell)19:31
*** VW_ has quit IRC19:31
dtroyerbriancurtin: right, and we are strting to do that in OSC more and more19:31
briancurtinfind is the method i think i've written and thrown away and rewritten 20 times in the last few months19:31
terrylhoweyes19:31
briancurtinif we concede that having to fall back to "get everything and filter locally" is sometimes acceptable, it gets a little easier19:32
etoewswith those use cases for find it makes more sense to me as separate method too.19:32
dtroyermy gut says there are probably three variations on find() needed across the OpenStack APIs, and we shouldn't get hung up too much on the differences.  Just docuemnt those differences well to make it easy to choose19:32
terrylhowedefinitely need that briancurtin19:32
terrylhoweIt seems like we should provide the filters and if there are dups, we filter19:33
*** VW_ has joined #openstack-meeting-319:33
*** jcoufal has joined #openstack-meeting-319:33
briancurtinyeah, there's too many places where there is zero filtering capability server side. i guess maybe i'll try to tackle a better find again and look at a cleaner get19:33
terrylhowewould it help if get returned None on 404?19:34
dtroyerat a high level API, maybe.  at the lowest levels I'd probably want to see the error code19:34
briancurtinterrylhowe: i think that depends on how find works and how they work together. on delete you can reasonably ignore a 404, but if you're expecting to get a flavor or a server or a container, you can't reasonably continue without those things since you're probably building on them or otherwise communicating with them19:35
*** alexpilotti has quit IRC19:36
briancurtinso it is an exceptional case to not be returned what you were asking for there19:36
terrylhoweI like it throwing a 40419:36
etoewsto me, if i'm doing a get with a specific id i'm fully expecting it to be there, otherwise it's an exception19:36
briancurtinthat's my stance as well19:36
etoewswe have NotFoundException19:37
briancurtinfind, on the other hand, would be a place that none could be returned19:37
etoewswe also have ResourceNotFound19:37
briancurtinetoews: that's what it would be raised as (RNF)19:37
etoews+1 None is a valid return on find19:37
*** sergef has quit IRC19:37
etoewswhat's supposed to be the diff between ResourceNotFound and NotFoundException19:38
* briancurtin was just typing that19:38
*** iben_ has quit IRC19:38
briancurtinetoews: id have to dig in, but i think the one i recently added was ResourceNotFound and it's raised when we get a 404 out of like session.get. i seem to remember NotFoundException comes from other places and is more generally for 404s not related to actually trying to work with resources (like trying to get a service catalog or something?)19:39
briancurtinthat's not really a great justification, we should look into that and confirm we need both19:40
etoewsoh wait. ResourceNotFound(NotFoundException) :P19:40
etoewsi guess it's supposed to be a more specific class of NFE19:40
etoewsthat's not particularly intuitive to me19:41
etoewsmy preference would be for just one19:41
dtroyerI would expect to see NotFoundException if I hit a URL that is invalid, ResourceNotFound if the URL is correct but there is no resource by the requested id?19:41
briancurtini think that was the intent (i have a terrible memory, looking it up now)19:42
dtroyerThe first is more likely when a client is mis-matched with the server for some reason and doesn't know it and is issuing incorrect requests19:42
etoewsdtroyer: but would the sdk necessarily know which case you're in?19:43
dtroyeretoews: in my mind it does ;)  but maybe not.  I'm not certain if the server response is different19:45
*** egallen has quit IRC19:45
briancurtinok, from transport if we get a 404, it's a NotFoundException. if the something like get_server receives catches a NotFoundException, it re-raises as ResourceNotFound19:46
etoewsi guess the question boils down to, is there value to the client code to have both?19:47
briancurtinso it's just turning a generic 404 into something with a bit more information about the request. teh exc message is "No %s found for %s" % (resource_type.__name__, value)19:47
dtroyerso the difference is just that's its specifically a resource request that returned 404.  If there is additional info in the message I'd say it is worth it19:48
dtroyerwell, you can add that anyway…19:48
* dtroyer goes back to counting release emails19:48
briancurtinthe only real difference between the two is the name of the exception class and that we put the resoruce type you're trying to get into the message. we could technically just reraise NotFoundException with that exception message19:49
etoewsright. RNF doesn't add a lot of value. (although i like the name more)19:49
briancurtin(i like ResourceNotFound as a name at that point, though...not married to it yet)19:50
briancurtinyep19:50
etoewssomething to noodle on.19:50
etoewsi'd like to bring up one more thing before we break.19:50
briancurtingo for it19:50
etoewsi'd like to see the sdk get a bit more visibility19:51
etoewsin openstack overall19:51
briancurtinoh yeah, i submitted a cross-project...uh, thing...blanking on the name of19:51
etoewssession19:51
briancurtinworking group or meetup or something for at the summit19:51
etoews#link form https://docs.google.com/forms/d/1LJZxdxE8P2F0WoULZEsRCXeqZP_VgH5nWUdZlbcA68M/viewform?c=0&w=119:52
etoewsoops19:52
etoewsform #link https://docs.google.com/forms/d/1LJZxdxE8P2F0WoULZEsRCXeqZP_VgH5nWUdZlbcA68M/viewform?c=0&w=119:52
etoewsproposals #link https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit#gid=82750341819:52
briancurtinetoews: how do you want to go about more visibility. ive wanted this for a long time but i dont know when is too early (or too late), and being in the middle of stabilizing APIs feels like a time people probably don't want to toy with it19:52
etoewslooks like the sdk is row 1419:52
etoewsbriancurtin: but we're getting close to stabilizing it19:53
etoewsi dunno. maybe i'm just being impatient.19:54
briancurtinyep, and building up examples and sharing them and writing about them and all of that is stuff we'll have to do. terry and i have a talk on buildng applications on the SDK19:54
etoewsbut participating in the cross-project meeting might help (when the time is right)19:55
terrylhowelooks good.  I’d really like to get these proxy changes done soon19:55
etoews+119:55
etoewswhat's the goal for a "1.0" release?19:56
briancurtinsame. i need to go back to the create one as well since i have work to do there as well. update is sort of similar so what we'll have discussed in create will mostly apply there19:56
etoewsor roadmap is maybe what i mean.19:57
briancurtinetoews: i think once we get these APIs stabilized and then applied, we do a release but just bump it up one from where we're at ( so 0.4 or 0.5?) -- after getting mileage and feedback and talk around more of openstack, ironing things out of that seems like the way to 1.0. i dont really think it's all that far away19:57
terrylhowewe need to get some sort of alpha/beta trial before 1.019:57
etoewsit would be nice to have a "1.0" before the summit so we can go into session and try to get some traction.19:58
terrylhoweTokyo maybe19:58
etoewsi'm talking vancouver19:58
stevelleI'm glad I wasn't the only one thinking Vancouver would be too soon19:58
briancurtinif we do a 1.0 early then we're stuck with those APIs until we do a 2.0. i want to move quick on this so maybe that's not a bad thing, but i do think we need to settle down slightly after we get the APIs baked in over the next few weeks/months19:58
etoewsalright. well expect me to continue to push. frankly i'm excited to really get this out there and get people using it.20:00
briancurtinsame. haven't worked on it for like a year for nothin'20:00
*** vishwanathj has joined #openstack-meeting-320:00
briancurtinand that's time. i have to head out to other things for a bit but i'll keep an eye on -sdks and be back later20:01
briancurtin#endmeeting20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
briancurtinthanks all20:01
openstackMeeting ended Tue Apr 21 20:01:07 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-04-21-19.00.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-04-21-19.00.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2015/python_openstacksdk.2015-04-21-19.00.log.html20:01
etoewsthanks20:01
*** jamielennox has left #openstack-meeting-320:03
*** stevelle has left #openstack-meeting-320:03
*** vishwana_ has joined #openstack-meeting-320:04
*** vishwanathj has quit IRC20:04
*** baoli has quit IRC20:05
*** dtroyer has left #openstack-meeting-320:05
*** erikmwilson has quit IRC20:11
*** erikmwilson has joined #openstack-meeting-320:11
*** jcoufal has quit IRC20:15
*** erikmwilson has quit IRC20:17
*** erikmwilson has joined #openstack-meeting-320:17
*** e0ne is now known as e0ne_20:17
*** matrohon has joined #openstack-meeting-320:20
*** david-lyle has joined #openstack-meeting-320:21
*** VW_ has quit IRC20:24
*** igordcard has joined #openstack-meeting-320:29
*** Sukhdev has joined #openstack-meeting-320:31
*** matrohon has quit IRC20:34
*** Piet has joined #openstack-meeting-320:37
*** sarob_ is now known as sarob20:40
*** baoli has joined #openstack-meeting-320:42
*** wojdev has joined #openstack-meeting-320:45
*** emagana has quit IRC20:46
*** erikmwilson has quit IRC20:47
*** alexpilotti has joined #openstack-meeting-320:51
*** julim has quit IRC20:57
*** mrmartin has quit IRC20:58
*** VW_ has joined #openstack-meeting-321:00
*** VW_ has quit IRC21:01
*** stevemar2 has joined #openstack-meeting-321:01
*** stevemar has quit IRC21:01
*** absubram has joined #openstack-meeting-321:01
*** eghobo_ has joined #openstack-meeting-321:01
*** VW_ has joined #openstack-meeting-321:02
*** clu_ has joined #openstack-meeting-321:02
*** eghobo_ has quit IRC21:02
*** stevemar2 has quit IRC21:02
*** stevemar has joined #openstack-meeting-321:04
*** zz_johnthetubagu is now known as johnthetubaguy21:04
*** eghobo has quit IRC21:04
*** absubram has quit IRC21:05
*** absubram has joined #openstack-meeting-321:06
*** wojdev has quit IRC21:10
*** lblanchard has quit IRC21:12
*** marun has quit IRC21:14
*** wojdev has joined #openstack-meeting-321:14
*** MaxV has joined #openstack-meeting-321:20
*** jgrimm is now known as zz_jgrimm21:20
*** mattfarina has quit IRC21:26
*** e0ne_ has quit IRC21:31
*** emagana has joined #openstack-meeting-321:32
*** vishwana_ has quit IRC21:32
*** peristeri has quit IRC21:34
*** sigmavirus24 is now known as sigmavirus24_awa21:35
*** sigmavirus24_awa is now known as sigmavirus2421:35
*** sarob has quit IRC21:35
*** sarob has joined #openstack-meeting-321:36
*** zz_jgrimm is now known as jgrimm21:40
*** sarob has quit IRC21:41
*** thomasem has joined #openstack-meeting-321:42
*** VW_ has quit IRC21:45
*** mwagner_lap has quit IRC21:47
*** carl_baldwin_ has quit IRC21:50
*** jckasper has quit IRC21:51
*** carl_baldwin has quit IRC21:52
*** emagana has quit IRC21:53
*** emagana has joined #openstack-meeting-321:54
*** MaxV has quit IRC21:54
*** johnthetubaguy is now known as zz_johnthetubagu21:58
*** yamahata has joined #openstack-meeting-321:58
*** emagana has quit IRC21:59
*** wojdev has quit IRC21:59
*** stevemar has quit IRC22:00
*** baoli has quit IRC22:03
*** VW_ has joined #openstack-meeting-322:03
*** Swami has quit IRC22:07
*** ivar-laz_ has quit IRC22:07
*** ivar-lazzaro has joined #openstack-meeting-322:07
*** wojdev has joined #openstack-meeting-322:08
*** ivar-lazzaro has quit IRC22:09
*** emagana has joined #openstack-meeting-322:10
*** ivar-lazzaro has joined #openstack-meeting-322:10
*** yamahata has quit IRC22:13
*** wojdev has quit IRC22:18
*** vishwanathj has joined #openstack-meeting-322:20
*** VW_ has quit IRC22:24
*** Rockyg has quit IRC22:26
*** marun has joined #openstack-meeting-322:26
*** mwang2 has quit IRC22:28
*** Sukhdev has quit IRC22:31
*** mwagner_lap has joined #openstack-meeting-322:32
*** shwetaap has joined #openstack-meeting-322:34
*** bryan_att has quit IRC22:34
*** shwetaap1 has quit IRC22:36
*** irenab has quit IRC22:41
*** bknudson has quit IRC22:41
*** irenab has joined #openstack-meeting-322:42
*** sigmavirus24 is now known as sigmavirus24_awa22:46
*** Swami has joined #openstack-meeting-322:53
*** Longgeek has quit IRC22:54
*** vishwanathj has quit IRC23:08
*** yamamoto has joined #openstack-meeting-323:11
*** markvoelker_ has quit IRC23:16
*** yamamoto has quit IRC23:21
*** vishwanathj has joined #openstack-meeting-323:24
*** aduarte has quit IRC23:29
*** bpokorny has quit IRC23:30
*** erikmwilson has joined #openstack-meeting-323:35
*** sarob has joined #openstack-meeting-323:35
*** sarob has quit IRC23:35
*** erikmwilson has quit IRC23:35
*** vishwanathj has quit IRC23:41
*** vishwanathj has joined #openstack-meeting-323:41
*** vishwana_ has joined #openstack-meeting-323:45
*** vishwanathj has quit IRC23:46
*** zhenguo has joined #openstack-meeting-323:47
*** rhagarty has joined #openstack-meeting-323:51
*** rhagarty_ has joined #openstack-meeting-323:51
*** bknudson has joined #openstack-meeting-323:54
*** melwitt has quit IRC23:56
*** yamamoto has joined #openstack-meeting-323:57

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