Wednesday, 2016-06-15

*** piet_ has quit IRC00:00
*** mbound has quit IRC00:00
*** kzaitsev_mb has quit IRC00:01
*** kzaitsev_mb has joined #openstack-meeting-300:03
*** hoangcx_ has joined #openstack-meeting-300:07
*** zz_dimtruck is now known as dimtruck00:07
*** hoangcx_ is now known as hoangcx00:10
*** iyamahat has quit IRC00:14
*** yamahata has quit IRC00:14
*** uxdanielle has quit IRC00:16
*** ddieterly has joined #openstack-meeting-300:17
*** sdake has quit IRC00:18
*** sarob has quit IRC00:30
*** david-lyle has quit IRC00:32
*** tqtran has quit IRC00:33
*** ddieterly has quit IRC00:35
*** revon has quit IRC00:39
*** dimtruck is now known as zz_dimtruck00:41
*** mtanino has quit IRC00:41
*** banix has joined #openstack-meeting-300:42
*** Sukhdev has joined #openstack-meeting-300:44
*** Sukhdev has quit IRC00:45
*** ivar-lazzaro has joined #openstack-meeting-300:47
*** ivar-laz_ has joined #openstack-meeting-300:48
*** ivar-lazzaro has quit IRC00:52
*** numans has joined #openstack-meeting-300:56
*** bpokorny_ has joined #openstack-meeting-300:57
*** ddieterly has joined #openstack-meeting-300:59
*** bpokorny has quit IRC01:00
*** mbound has joined #openstack-meeting-301:01
*** bpokorny_ has quit IRC01:01
*** zhurong has joined #openstack-meeting-301:06
*** mbound has quit IRC01:06
*** pvaneck has quit IRC01:08
*** ddieterly has quit IRC01:15
*** kzaitsev_mb has quit IRC01:16
*** ivar-laz_ has quit IRC01:17
*** mickeys has quit IRC01:21
*** mickeys has joined #openstack-meeting-301:22
*** mickeys has quit IRC01:27
*** sdake has joined #openstack-meeting-301:28
*** tqtran has joined #openstack-meeting-301:30
*** sdake has quit IRC01:32
*** tqtran has quit IRC01:34
*** primeministerp has joined #openstack-meeting-301:38
*** baoli has joined #openstack-meeting-301:41
*** stanzgy has joined #openstack-meeting-301:46
*** toddjohn has joined #openstack-meeting-301:53
*** jrist has quit IRC01:56
*** ddieterly has joined #openstack-meeting-301:57
*** ddieterly is now known as ddieterly[away]01:57
*** ddieterly[away] is now known as ddieterly01:57
*** toddjohn has quit IRC01:58
*** jrist has joined #openstack-meeting-302:02
*** s3wong has quit IRC02:09
*** ddieterly has quit IRC02:12
*** zz_dimtruck is now known as dimtruck02:17
*** coolsvap has joined #openstack-meeting-302:18
*** ddieterly has joined #openstack-meeting-302:20
*** baoli has quit IRC02:32
*** ddieterly has quit IRC02:35
*** ddieterly has joined #openstack-meeting-302:35
*** ddieterly has quit IRC02:35
*** VW has joined #openstack-meeting-302:37
*** julim has joined #openstack-meeting-302:38
*** lblanchard has quit IRC02:38
*** iyamahat has joined #openstack-meeting-302:38
*** kzaitsev_mb has joined #openstack-meeting-302:41
*** VW has quit IRC02:42
*** chandanc has joined #openstack-meeting-302:46
*** zhurong has quit IRC02:56
*** zhurong has joined #openstack-meeting-302:56
*** iyamahat has quit IRC03:01
*** kzaitsev_mb has quit IRC03:24
*** tfukushima has joined #openstack-meeting-303:27
*** sarob has joined #openstack-meeting-303:28
*** tqtran has joined #openstack-meeting-303:31
*** sarob has quit IRC03:35
*** tqtran has quit IRC03:36
*** VW has joined #openstack-meeting-303:45
*** banix has quit IRC03:46
*** Sukhdev has joined #openstack-meeting-303:50
*** SridarK has joined #openstack-meeting-303:52
*** anilvenkata has joined #openstack-meeting-303:56
*** yushiro has joined #openstack-meeting-303:57
*** VW has quit IRC03:59
*** njohnston|afk is now known as njohnston03:59
*** VW has joined #openstack-meeting-303:59
njohnston#startmeeting fwaas04:00
openstackMeeting started Wed Jun 15 04:00:04 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: fwaas)"04:00
openstackThe meeting name has been set to 'fwaas'04:00
*** dimtruck is now known as zz_dimtruck04:00
njohnstonHello all!04:00
yushirohello :)04:00
njohnston#chair SridarK xgerman04:00
openstackCurrent chairs: SridarK njohnston xgerman04:00
SridarKHi All04:00
SridarKshall we get started04:01
chandancHello all04:01
SridarKpadkrish is out on PTO so most likely will not join04:01
yushiroSridarK, OK. Thanks you.04:02
SridarK#topic FWaaS v204:02
*** openstack changes topic to "FWaaS v2 (Meeting topic: fwaas)"04:02
*** SarathMekala has joined #openstack-meeting-304:02
SridarKnjohnston: thanks for the db patch - i am working thru the integration04:02
njohnstonExcellent, I am glad we are starting to see some real velocity here04:03
SridarKas expected - i am going thru some initial teething issues04:03
SridarKnothing major04:03
*** shwetaap has joined #openstack-meeting-304:03
SridarKi am creating the new tables manually - i hope by end of day tomorrow -  i will atleast have gotten rid of some of the tracebacks04:03
SridarKso will continue with that04:04
*** julim has quit IRC04:04
SridarKyushiro: on the agent front - how are things04:05
SridarKthings u would like to discuss04:05
yushiroSridarK, last week, we discussed with paddu and decided some A.I.04:05
yushiroSridarK, My A.I is asking ajo and Ihar about adding L2 extension patch into neutron.04:06
SridarKyushiro: ok04:06
*** david-lyle has joined #openstack-meeting-304:06
yushiroSridarK, But I'm sorry. I couldn't reach out ajo/Ihar last week. (No timing on IRC..)04:06
SridarKyushiro: ok no worries - perhaps this week u can close on that04:07
njohnstonyushiro: Let me know if there is anything I/we can do to help04:07
*** ppouliot has joined #openstack-meeting-304:07
yushiroSridarK, Thanks. I'll send e-mail them again and try to reach out on IRC.04:07
SridarKyushiro: ok perfect04:08
yushironjohnston, Yes.  I'll do that.  Thanks for your help :)04:08
SridarKMoving to the driver, I dont see mickeys online. chandanc: SarathMekala: things u would like to bring up or discuss ?04:09
chandancI have had a look at the conntrack side04:10
SridarKi know u were in discussion with mickeys on getting a bug opened to clean things up on neutron amongst other things04:10
*** primeministerp has quit IRC04:11
chandancYa, i cond not proceed beyond the initial discussion about conntrack04:11
SridarKi think mickeys is getting busy with some other things - but he mentioned that he is available for any discussions04:11
SarathMekalaI had a closure on the discussion with Mickey.. will send across an etherpad on it04:11
chandancok will ping him and start proceeding on the driver patch04:12
SridarKchandanc: SarathMekala: ok great. yes pls feel free to reach him via email or IRC04:12
njohnstonSarathMekala and chandanc: Did either of you get an idea about the neutron change to relocate the ACCEPT?04:12
chandancDid you guys had a look at the singleton patch ? do you have any feedback ?04:12
SridarKchandanc: can u pls point to the patch04:13
njohnstonchandanc: I did not, apologies.  Can you send the URL?04:13
chandancNo i have not looked at the exact iptables rules, i can give an update this week though04:13
njohnstonchandanc: Thanks!04:13
njohnston#action multiple folks to review
* njohnston notes shwetaap pushed a new patchset for the rest API change, and it has a lot more in the way of tests:
SridarKok sounds good04:15
SridarKchandanc: any thing else to discuss ?04:15
chandancnothing more for now04:15
shwetaapthanks njohnston, yea i just pushed it out. I may have a few more tests to add. Will add to the patch04:16
SridarKshwetaap: circling back - thx for the update04:16
SridarKshwetaap: i have started with the original patch for my integration - i will update04:16
shwetaapSridarK: sounds good.04:17
SridarKxgerman: njohnston: other things to cover on v2 ?04:17
xgermanno I think w are good04:18
njohnstonI have my v2 work on hold while I work on the l3 agent extension04:18
SridarKnjohnston: yes understood - u have given me enough to go on04:18
SridarKnjohnston: i will let u know if i hit issues04:18
njohnstonSridarK: Sounds like a good plan04:19
SridarK#topic L3Agent extension04:19
*** openstack changes topic to "L3Agent extension (Meeting topic: fwaas)"04:19
SridarKnjohnston: pls go ahead04:19
njohnstonFirst implementation patch for the l3 agent extension is up: "Move agent extension mechanism out of L2 agent"04:19
njohnstonI figure that si the first bit, then I will proceed with the more intrusive agent changes.04:19
njohnstonNote that patch is super-WIP, I haven't really attended to the breakage in the tests yet - that is tomorrow04:20
SridarKnjohnston: great - i took a quick look at this - i think getting out of L2 was a good first step04:20
*** iyamahat has joined #openstack-meeting-304:20
SridarKnjohnston: so the extensions manager bit can be pretty much commonized without any issues ?04:21
njohnstonAs far as the server side, the notification driver, it's a little stickier extricating out the l2 agent specific code form the general notification logic, and I have a question out to ajo, since he wrote that code04:21
*** kzaitsev_mb has joined #openstack-meeting-304:21
njohnstonSridarK: I believe that part is highly generic, so yes, I am optimistic it can be generalized with very few issues04:21
SridarKnjohnston: ok that would be nice04:21
njohnstonthat is the lowest of the low hanging fruit in this endeavor04:21
njohnstonSo that divides the work into more achieveable sections04:23
njohnstonand I will proceed delivering them seriatim04:23
SridarKSounds good04:23
njohnstonThat is it for me04:24
SridarKi am quite familiar with the FWaaS L3 Agent pieces - so i can definitely help bolt that in04:24
SridarKnjohnston: nice work on the spec - i think most issues are covered04:24
njohnstonwhat rpc messages does l3 fwaas need to be sensitive to?04:24
SridarKonce Ihar acks ur last rev - we shd be good04:24
SridarKnjohnston: these would be for the FWaaS resources04:25
SridarKwhen we create a Firewall Group04:25
SridarKor if we update a rule or a policy in a Firewall Group04:25
SridarKIIRC, we use one topic to push these from the plugin to the agent04:26
njohnstonyes, but it would also need to be sensitive to, say, a port delete, so it would clean up any rules specific to that port's firewalling, yes?04:26
SridarKand we had a reverse for things the agent reported back to the plugin (like if something failed)04:26
SridarKnjohnston: yes exactly as we introduce the port attribute04:26
SridarKnjohnston: previously we had an update out if the router that the FW was installed on changes04:27
*** vishwanathj has joined #openstack-meeting-304:27
njohnstoncould you send me a ppinter to where that logic is when you get a chance?04:28
SridarKnjohnston: although will need to look at parallels with the L2 case where u had mentioned that we shared the rpc04:28
njohnston(doesnt need to be right now)04:28
SridarKnjohnston: surely04:28
SridarKnjohnston: essentially all the CRUD methods will trigger a push to the agent (if there is a Firewall Group)04:29
* xgerman finished another call and can now pay full attention04:29
xgermanSridarK +104:29
SridarKxgerman: totally understand04:30
xgermanand then the agent will figure out if the change affects the ports it manages and ask for the info — or in v 0.5 always asks for the info04:30
SridarKxgerman: +1 - i need to go thru that logic a bit more for the new implementation model04:31
SridarKnjohnston: other things u would like to discuss here04:31
njohnstonnot in the l3 topic, no04:31
SridarK#topic Devstack plugin for FWaaS04:32
*** openstack changes topic to "Devstack plugin for FWaaS (Meeting topic: fwaas)"04:32
SridarKnjohnston: thx for confirming - clearly i dont see the db migration script running thru04:32
njohnstonIt sounds to me like migrations are only getting partially executed04:32
SridarKthe router association table is not getting created, so when we do a firewall-create - we fail with the table being absent04:33
chandancquestion: do you guys not see the association table created ?04:33
njohnstonI need to bone up a bit on how migrations get executed I guess, since I can't make heads or tails of this issue yet04:33
SridarKchandanc: i did not see it04:33
chandancoh, i just re stacked, and was able to create a router04:34
SridarKand i asked njohnston: to confirm - just to be sure that i did not get something messed up on my setup04:34
SridarKchandanc: ok i have a router too04:34
SridarKchandanc: but are u able to create a firewall ?04:34
SridarKi can create rules and policies04:35
xgerman know they changed migrations around a bit04:35
SridarKchandanc: ok so i may have a red herring ?04:35
xgermanbut forgot the deails04:35
chandancok , will recheck and let you know by mail04:35
SridarKxgerman: yes that is correct04:35
njohnstonchandanc: Did you try with the devstack plugin patch?04:35
chandancya i did04:36
*** vishwanathj has quit IRC04:36
njohnstonok, I will restack tomorrow with a freshly created VM and see what happens04:36
chandancplease go on, will let you know once my stack is redone04:36
SridarKchandanc: u are using enable_service fwaas ?04:36
chandancyes, will also share my local.conf04:37
njohnston#action njohnston to restack with a fresh VM and see if migrations happened04:37
njohnstonchandanc: +1 thanks!04:37
SridarKchandanc: ok great04:37
xgermanwe should put a sample local.conf in our project04:37
SridarKlets carry on the conversation in email04:37
SridarKxgerman: +1 lets do that right after this patch merges04:37
xgermanwe can also use our shiny new channel04:37
chandancxgerman: i think we can update the README in the devstack plugin04:38
xgermanthar, too04:38
SridarKactually the README does have this04:38
chandancok, sorry for the confusion04:39
SridarKchandanc: ok thx - we can sync over email04:39
njohnstondevstack readme in the patch:
SarathMekalawas about to mention that04:39
xgermanwell, I know we added a sample local.conf in LBaaSand that helped a lot… some project even have vagrant files...04:39
SridarK#action SridarK to clean up some of the setup documentation04:39
xgermansample local.conf is far more tune-key ;-)04:39
SridarKok i think we have beaten this to death :-)04:41
SridarKhopefully by tomorrow we can all be on the same page04:41
SridarK#topic Open Discussion04:42
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:42
njohnstonThe bot should be on #openstack-fwaas probably tomorrow, thanks to infra liason intervention by dougwig.  Thanks dougwig!04:43
SridarKnjohnston: thanks for initiating this04:43
njohnstonIt seemed like the logical next step04:44
*** primeministerp has joined #openstack-meeting-304:44
chandancquestion: had a quick look at the l3 patch, do you think the agent_extension interface will change to support l3 extensions or we are going to handle updates at the port level ?04:44
*** ppouliot has quit IRC04:45
SridarKchandanc: we will have to handle the L3 port thru the L3 agent ext i/f04:45
*** kaz has joined #openstack-meeting-304:46
chandancSridarK: i mean the methods of the #link
njohnstonchandanc: The l3 agent extensions manager will load the fwaas extension, and the fwaas extension will register for port updates directly04:47
*** p0n has quit IRC04:47
njohnstonThe updates don't need to pass through the extension manager on the agent side.04:48
njohnstonrpc updates04:48
chandancok, so the l3 extension will be called for each port created ?04:48
chandancor only the l3 ports ?04:48
SridarKThere will port updates and then FW resource updates binding to a specific port04:49
*** mrmartin has joined #openstack-meeting-304:49
SridarKchandanc: we will need to do this if there is a FW bound to that port04:49
xgermanwe will have calls through the L3 extension and then our CRUD calls -port, FW Rule, etc.04:49
xgermanso practically the L3 extension will be called for each port created on the router and each L2 port relevant to us04:50
chandancok suer, will go through the patch and come back04:50
SridarKother things any one would like to bring up ?04:51
njohnstonchandanc: And understand that is still super WIP - it's hours old, and I am working out the kinks. :-)04:52
yushironjohnston, If your patch will be merged, I don't need to register some resources on L2 side?04:52
njohnstonyushiro: This shouldn't change anything for the L2 side, since the L2 agent will still need to implement rules on VM ports.04:53
yushironjohnston, Ah, I see. I understand your patch effects only L3 side. Thanks.04:54
xgermanwe hope to share some code between L2 and L3 eventually04:54
*** kzaitsev_mb has quit IRC04:54
*** salv-orl_ has quit IRC04:54
njohnstonIt seems unnatural for this part of the code not to be shared.04:54
*** salv-orlando has joined #openstack-meeting-304:54
SridarKnjohnston: i think we can commonize some of the FW - port binding stuff on the agent04:55
njohnstonSridarK: +104:55
SridarKnjohnston: once we have some things working04:55
SridarKok if nothing else - we can close out04:56
yushiroThank you all!04:57
SridarKok thanks all and we can exchg emails as needed04:57
xgermanThanks a lot! I will hammer out some reviews :-)04:57
* SarathMekala says bye bye o/04:58
*** openstack changes topic to "OpenStack Meetings ||"04:58
openstackMeeting ended Wed Jun 15 04:58:07 2016 UTC.  Information about MeetBot at . (v 0.1.4)04:58
openstackMinutes (text):
*** yushiro has quit IRC04:58
*** njohnston is now known as njohnston|sleep04:59
*** lpetrut has joined #openstack-meeting-304:59
*** yamamot__ has joined #openstack-meeting-305:01
*** kazu_ has joined #openstack-meeting-305:02
*** primeministerp has quit IRC05:12
*** salv-orlando has quit IRC05:17
*** salv-orlando has joined #openstack-meeting-305:17
*** shwetaap has quit IRC05:20
*** mrmartin has quit IRC05:21
*** salv-orl_ has joined #openstack-meeting-305:29
*** muawiakhan has joined #openstack-meeting-305:31
*** sarob has joined #openstack-meeting-305:31
*** salv-orlando has quit IRC05:32
yamamot__#startmeeting taas05:33
openstackMeeting started Wed Jun 15 05:33:05 2016 UTC and is due to finish in 60 minutes.  The chair is yamamot__. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:33
*** openstack changes topic to " (Meeting topic: taas)"05:33
openstackThe meeting name has been set to 'taas'05:33
yamamot__#topic agenda05:33
*** openstack changes topic to "agenda (Meeting topic: taas)"05:33
yamamot__#topic do we still aim to make a release compatible with mitaka?05:34
*** openstack changes topic to "do we still aim to make a release compatible with mitaka? (Meeting topic: taas)"05:34
yamamot__it has been postponed in the last meeting because of the lack of quorum05:35
yamamot__but it seems we have even fewer this week :-(05:35
yamamot__let's bring it on ml05:35
*** sarob has quit IRC05:36
yamamot__#action yamamoto raise the release topic on ml05:36
yamamot__#topic gate blocker
*** openstack changes topic to "gate blocker (Meeting topic: taas)"05:36
yamamot__this is a fix for the gate blocking issue05:37
yamamot__please review.05:37
yamamot__#topic Open Discussion05:37
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"05:37
yamamot__anyone has any topic?05:37
kazyamamoto_: thank you for your comment for my patchset.05:38
kazwhat do you mean "populate" ?05:38
yamamot__i meant that, if there are existing rows, their status somehow need to be set.05:39
*** SarathMekala has quit IRC05:39
kazi see05:39
kazi will update it.05:40
yamamot__i think ADD COLUMN can specify the default value.  i don't know how it can be specified via sqlalchemy though.05:40
*** tfukushima has quit IRC05:40
*** tfukushima has joined #openstack-meeting-305:41
yamamot__i guess there are good examples in neutron migration scripts05:41
kazthanks, i will see that05:41
yamamot__muawiakhan: hi, can you remind me who are you?  my memory is dim.05:43
yamamot__fawad's coworker?05:45
muawiakhan@yamamot__ :) I think we haven't met before or talked directly. I work with Fawad.05:45
muawiakhanyamamot__: you got that right ;-)05:45
yamamot__ok, google is great :-)05:45
*** pgadiya has joined #openstack-meeting-305:46
yamamot__muawiakhan: what's your interest wrt taas? plumgrid support?05:47
*** iyamahat has quit IRC05:48
muawiakhan@yamamot__ yes, and to follow up on the latest and the greatest.05:49
yamamot__in that case, i guess you are interested in this patch05:49
muawiakhanI can also take some action items if need be.05:50
yamamot__it was necessary for midonet, but should be useful for other vendor drivers05:50
*** kzaitsev_mb has joined #openstack-meeting-305:50
muawiakhanwill take a look. thanks05:50
*** tfukushima has quit IRC05:51
*** nkrinner_afk is now known as nkrinner05:51
yamamot__there are a lot of todos.  currently we are trying to concentrate to fix the functionality we already have, rather than adding new features.05:51
yamamot__a few important bugs are:05:52
openstackLaunchpad bug 1501792 in tap-as-a-service "lack of automated tests" [Undecided,In progress] - Assigned to YAMAMOTO Takashi (yamamoto)05:52
openstackLaunchpad bug 1535993 in tap-as-a-service "Convert TaaS to a Neutron L2 extension" [Undecided,New] - Assigned to Reedip (reedip-banerjee)05:52
*** yamahata has joined #openstack-meeting-305:53
openstackLaunchpad bug 1565622 in tap-as-a-service "OSC support" [Undecided,New] - Assigned to Reedip (reedip-banerjee)05:53
yamamot__it's great if you can take some of them05:54
muawiakhani will take a look.05:55
*** kzaitsev_mb has quit IRC05:55
*** mbound has joined #openstack-meeting-305:55
yamamot__i guess the poor coverage of automatic tests is the most important issue for vendors who want to implement their own.05:55
kazi will consider.05:55
yamamot__reedip: hi!05:55
muawiakhanwill need to catch up on some stuff. but will update.05:55
reedipsorry I was busy with other tasks05:56
reedipnow I have a bit of bandwidth available05:56
*** coolsvap has quit IRC05:57
yamamot__kaz: thank you05:57
yamamot__reedip: do you have any update on l2 agent extension?05:57
*** sarob has joined #openstack-meeting-305:57
reedipyamamot__ : no, sorry05:57
*** numans has quit IRC06:00
*** mbound has quit IRC06:00
yamamot__reedip: alright.  do you still want to work on it?06:01
*** sarob has quit IRC06:02
*** stanzgy has quit IRC06:02
reedipyamamot__ : I need some help, the arch is not clear to me06:04
*** irenab has quit IRC06:05
*** irenab has joined #openstack-meeting-306:05
yamamot__which part of arch?06:07
reedipHow to implement it as an extension06:08
reedipdavidsa helped but it was still not clear06:08
*** Niham has joined #openstack-meeting-306:10
*** coolsvap has joined #openstack-meeting-306:10
reedipI will checkout the ovs implementation again06:11
yamamot__have you looked at qos extension?06:12
reedipI didnt check it out completely06:14
reedipI will try to complete it today and ping you if I have any doubts06:14
yamamot__it comsumes rpcs and handles port events. these are necessary for taas as well i guess.06:15
reedipCan you resend the link if possible ?06:15
reedip ??06:17
yamamot__it's better to look at the code in master though06:18
reedipumm, I was thinking this would explain what chages they did06:19
reedipbut ok06:19
*** reedip_ has joined #openstack-meeting-306:19
yamamot__neutron/plugins/ml2/drivers/openvswitch/agent/extension_drivers/ and neutron/agent/l2/extensions/ are important files for our purpose06:20
*** andreas_s has joined #openstack-meeting-306:20
yamamot__8 mins left.  does anyone have any other topics?06:22
kazI have no more topics.06:23
*** numans has joined #openstack-meeting-306:24
*** salv-orlando has joined #openstack-meeting-306:24
yamamot__it seems we've done06:25
yamamot__thank you for attending!06:25
*** openstack changes topic to "OpenStack Meetings ||"06:25
openstackMeeting ended Wed Jun 15 06:25:30 2016 UTC.  Information about MeetBot at . (v 0.1.4)06:25
openstackMinutes (text):
kazthank you, bye06:25
*** kaz has quit IRC06:27
*** salv-orl_ has quit IRC06:28
*** irenab has quit IRC06:28
*** salv-orlando has quit IRC06:29
*** lpetrut has quit IRC06:29
*** reedip_ has quit IRC06:30
*** toddjohn has joined #openstack-meeting-306:31
*** tfukushima has joined #openstack-meeting-306:34
*** toddjohn has quit IRC06:36
*** abalutoiu has joined #openstack-meeting-306:40
*** VW has quit IRC06:41
*** lpetrut has joined #openstack-meeting-306:42
*** jschwarz has joined #openstack-meeting-306:42
*** muawiakhan has quit IRC06:43
*** vtech has quit IRC06:44
*** irenab has joined #openstack-meeting-306:44
*** jschwarz has quit IRC06:50
*** Poornima has joined #openstack-meeting-306:50
*** kzaitsev_mb has joined #openstack-meeting-306:51
*** belmoreira has joined #openstack-meeting-306:51
*** kzaitsev_mb has quit IRC06:56
*** zhurong has quit IRC06:58
*** toddjohn has joined #openstack-meeting-306:59
*** rossella_s has joined #openstack-meeting-307:02
*** Niham has quit IRC07:02
*** toddjohn has quit IRC07:04
*** vtech has joined #openstack-meeting-307:05
*** lpetrut has quit IRC07:07
*** oshidoshi has joined #openstack-meeting-307:09
*** matrohon has joined #openstack-meeting-307:10
*** zhurong has joined #openstack-meeting-307:11
*** Niham has joined #openstack-meeting-307:12
*** Niham has quit IRC07:13
*** dtardivel has joined #openstack-meeting-307:14
*** Niham has joined #openstack-meeting-307:14
*** paul-carlton2 has joined #openstack-meeting-307:16
*** lpetrut has joined #openstack-meeting-307:18
*** egallen has joined #openstack-meeting-307:19
*** dhellmann has quit IRC07:20
*** dhellmann has joined #openstack-meeting-307:20
*** jlanoux has joined #openstack-meeting-307:25
*** lpetrut has quit IRC07:26
*** Niham has quit IRC07:26
*** Niham has joined #openstack-meeting-307:26
*** Sukhdev has quit IRC07:29
*** amotoki has joined #openstack-meeting-307:37
*** paul-carlton2 has quit IRC07:39
*** pgadiya is now known as pgadiya|lunch07:40
*** salv-orlando has joined #openstack-meeting-307:41
*** kzaitsev_mb has joined #openstack-meeting-307:52
*** jtomasek_ has joined #openstack-meeting-307:53
*** azemlyanov has joined #openstack-meeting-307:56
*** azemlyanov has quit IRC07:56
*** ccamacho has joined #openstack-meeting-307:56
*** azemlyanov has joined #openstack-meeting-307:56
*** kzaitsev_mb has quit IRC07:57
*** sarob has joined #openstack-meeting-307:58
*** paul-carlton2 has joined #openstack-meeting-307:59
*** sarob has quit IRC08:02
*** wangbo has joined #openstack-meeting-308:05
*** jtomasek_ has quit IRC08:10
*** kzaitsev_mb has joined #openstack-meeting-308:13
*** mickeys has joined #openstack-meeting-308:23
*** rdopiera has joined #openstack-meeting-308:25
*** paul-carlton2 has quit IRC08:25
*** mickeys has quit IRC08:27
*** stendulker has joined #openstack-meeting-308:28
*** toddjohn has joined #openstack-meeting-308:32
*** xiaohhui has quit IRC08:40
*** tqtran has joined #openstack-meeting-308:45
*** stanzgy has joined #openstack-meeting-308:47
*** tqtran has quit IRC08:50
*** jaesang has joined #openstack-meeting-308:51
*** ihrachys has joined #openstack-meeting-308:51
*** mbound has joined #openstack-meeting-308:52
*** mickeys has joined #openstack-meeting-308:56
*** itxaka has joined #openstack-meeting-308:59
*** pgadiya|lunch has quit IRC09:06
*** mickeys has quit IRC09:07
*** mickeys has joined #openstack-meeting-309:07
*** jtomasek_ has joined #openstack-meeting-309:08
*** mickeys has quit IRC09:11
*** jtomasek_ has quit IRC09:13
*** jaesang has quit IRC09:14
*** toddjohn has quit IRC09:16
*** sambetts|afk is now known as sambetts09:16
*** hdaniel has joined #openstack-meeting-309:19
*** pgadiya|lunch has joined #openstack-meeting-309:27
*** ostroverkhov has joined #openstack-meeting-309:27
*** lpetrut has joined #openstack-meeting-309:28
*** ostroverkhov has quit IRC09:28
*** kzaitsev_mb has quit IRC09:33
*** Niham has quit IRC09:36
*** tfukushima has quit IRC09:37
*** tfukushima has joined #openstack-meeting-309:38
*** hdaniel has quit IRC09:39
*** Niham has joined #openstack-meeting-309:41
*** ociuhandu has quit IRC09:42
*** salv-orlando has quit IRC09:47
*** salv-orlando has joined #openstack-meeting-309:48
*** cinerama has quit IRC09:51
*** cinerama has joined #openstack-meeting-309:55
*** sarob has joined #openstack-meeting-309:59
*** zhurong has quit IRC10:00
*** ajmiller_ has quit IRC10:02
*** ajmiller has joined #openstack-meeting-310:02
*** pavel_bondar has quit IRC10:02
*** sarob has quit IRC10:03
*** ajmiller_ has joined #openstack-meeting-310:04
*** ajmiller has quit IRC10:04
*** pgadiya|lunch has quit IRC10:13
*** tfukushima has quit IRC10:18
*** hoangcx has quit IRC10:24
*** pgadiya|lunch has joined #openstack-meeting-310:26
*** kzaitsev_mb has joined #openstack-meeting-310:27
*** pavel_bondar has joined #openstack-meeting-310:29
*** primeministerp has joined #openstack-meeting-310:33
*** ociuhandu has joined #openstack-meeting-310:36
*** Niham has quit IRC10:44
*** hdaniel has joined #openstack-meeting-310:51
*** sdague has joined #openstack-meeting-310:52
*** stanzgy has quit IRC10:56
*** salv-orlando has quit IRC10:56
*** salv-orlando has joined #openstack-meeting-310:57
*** chandanc has quit IRC10:59
*** egallen has quit IRC11:01
*** baoli has joined #openstack-meeting-311:05
*** salv-orlando has quit IRC11:06
*** baoli has quit IRC11:06
*** yamamot__ has quit IRC11:10
*** diana_clarke has quit IRC11:14
*** ccamacho is now known as ccamacho|lunch11:16
*** stendulker has quit IRC11:16
*** pgadiya|lunch is now known as pgadiya11:20
*** ppouliot has joined #openstack-meeting-311:28
*** rtheis has joined #openstack-meeting-311:29
*** diana_clarke has joined #openstack-meeting-311:30
*** primeministerp has quit IRC11:31
*** primeministerp has joined #openstack-meeting-311:31
*** ppouliot has quit IRC11:33
*** belmoreira has quit IRC11:33
*** Niham has joined #openstack-meeting-311:33
*** ppouliot has joined #openstack-meeting-311:45
*** ddieterly has joined #openstack-meeting-311:45
*** zhurong has joined #openstack-meeting-311:46
*** primeministerp has quit IRC11:48
*** yamamoto has joined #openstack-meeting-311:48
*** banix has joined #openstack-meeting-311:56
*** sarob has joined #openstack-meeting-312:00
*** banix has quit IRC12:00
*** sarob has quit IRC12:04
*** ddieterly is now known as ddieterly[away]12:08
*** zhurong has quit IRC12:09
*** ccamacho|lunch is now known as ccamacho12:10
*** zhurong has joined #openstack-meeting-312:10
*** claudiub has joined #openstack-meeting-312:11
*** lpetrut has quit IRC12:11
*** mbound has quit IRC12:15
*** mbound has joined #openstack-meeting-312:15
*** c64cosmin has joined #openstack-meeting-312:15
*** lpetrut has joined #openstack-meeting-312:15
*** baoli has joined #openstack-meeting-312:19
*** baoli has quit IRC12:20
*** baoli has joined #openstack-meeting-312:20
*** baoli_ has joined #openstack-meeting-312:22
*** egallen has joined #openstack-meeting-312:24
*** baoli has quit IRC12:25
*** c64cosmin has quit IRC12:26
*** ddieterly[away] is now known as ddieterly12:27
*** ppouliot has quit IRC12:27
*** ionutbalutoiu has joined #openstack-meeting-312:31
*** sarob has joined #openstack-meeting-312:32
*** ddieterly has quit IRC12:35
*** sarob has quit IRC12:36
*** c64cosmin has joined #openstack-meeting-312:38
*** mbound has quit IRC12:40
*** uxdanielle has joined #openstack-meeting-312:43
*** tqtran has joined #openstack-meeting-312:47
*** uxdanielle has quit IRC12:47
*** tqtran has quit IRC12:51
*** iuliat has joined #openstack-meeting-312:53
*** sagar_nikam has joined #openstack-meeting-312:55
*** salv-orlando has joined #openstack-meeting-312:56
*** salv-orlando has quit IRC12:56
*** salv-orlando has joined #openstack-meeting-312:56
*** yujunz has joined #openstack-meeting-312:58
*** julim has joined #openstack-meeting-312:59
*** kvinod has joined #openstack-meeting-313:00
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Jun 15 13:00:50 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
openstackThe meeting name has been set to 'hyper_v'13:00
domi007hi all :)13:01
kvinodhi all13:01
sagar_nikamHi All13:01
claudiub#topic designate status13:01
*** openstack changes topic to "designate status (Meeting topic: hyper-v)"13:01
*** yujunz has quit IRC13:01
*** woodster_ has joined #openstack-meeting-313:02
claudiubsooo... abalutoiu is at the testing phase of the designate stuff13:02
claudiubhe has already submitted a patch on os-win, and the one on designate is going to be submitted when it's fully reliable.13:02
claudiubabalutoiu: links?13:03
claudiubincluding the launchpad blueprint.13:03
abalutoiuthat is the os-win patch which adds support for DNS server operations13:03
abalutoiublueprint on designate for msdns:
claudiubthanks. :)13:04
sagar_nikamclaudiub: we saw a mail from designate PTL last week, i saw your reply as well, can we post the os-win changes to him13:04
sagar_nikamthis will let the designate team know that work is in progress13:05
claudiubsagar_nikam: I think we should email him when abalutoiu says it's ready and the patch has been submitted13:05
claudiubsagar_nikam: I agree.13:05
abalutoiusagar_nikam I already talked today with Graham about this13:05
sagar_nikamabaluntoiu: thanks13:05
sagar_nikamthat should be fine13:05
claudiubso, until then, we should review the os-win patch.13:06
claudiub#action review the os-win dnsutils patch:
claudiub#monasca status13:07
claudiub#topic monasca status13:07
*** openstack changes topic to "monasca status (Meeting topic: hyper-v)"13:07
claudiubsoo, no news here, just replying to comments mostly. fixing merge conflicts and so on.13:07
claudiub#topic nova patches13:08
*** openstack changes topic to "nova patches (Meeting topic: hyper-v)"13:08
claudiubit seems nothing really merged recently. :)13:08
claudiubapparently, it was a miracle so many patches merged a few weeks. ago.13:09
claudiubbut as far as nova goes, I've been taking a look at the OVS Hyper-V vif plugin driver on nova.13:09
sagar_nikamclaudiub: do we have a list of recently merged patches, we can check them13:09
claudiubThe plan is to use os-vif to create the OVS ports, if necessary.13:10
domi007hm, you are doing that to enable later security groups based on ovs flows?13:10
claudiubsagar_nikam: hm, not at the top of my head. I'll try to create one.13:10
sagar_nikamclaudiub: thanks13:10
*** diana_clarke has quit IRC13:11
claudiubdomi007: the security groups is a neutron-ovs-agent specific job. the VIF Drivers should just create the OVS ports.13:11
sagar_nikamkvinod: have you seen claudiub13:11
sagar_nikampatch ?13:11
sagar_nikamon OVS vif plugin13:11
domi007claudiub: I understand, but I'm not sure I understand why you are looking at this since creating OVS ports currently works fine :) sry13:11
claudiub#link Hyper-V OVS VIF driver:
claudiub^ this is the patch.13:12
kvinodsagar_nikam: no13:12
kvinodwill see it13:12
sagar_nikamkvinod: can you check please13:12
claudiubstill not fully functional. There are some linux specific issues in the current os-vif... I have to find a solution for them.13:13
claudiubsolved a few, but not all of them.13:13
domi007oh okay, I understand13:13
claudiubanyways. This VIF Driver was already merged in compute-hyperv since liberty13:13
claudiubor even Kilo, if I'm not mistaken.13:14
claudiuband that works well.13:14
claudiubbut as far as nova goes, we have to use os-vif for this, that's how all the VIF drivers are going to be used in nova.13:14
claudiubdomi007: to answer your question: at the moment, you cannot bind OVS ports on Hyper-V, unless you are using compute-hyperv. :)13:15
*** ddieterly has joined #openstack-meeting-313:16
claudiubmoving on.13:16
claudiub#topic networking-hyperv status13:16
*** openstack changes topic to "networking-hyperv status (Meeting topic: hyper-v)"13:16
claudiubso, first of all, I found a bug13:17
*** lblanchard has joined #openstack-meeting-313:17
openstackLaunchpad bug 1592777 in networking-hyperv "neutron-hyperv-agent shouldn't run if the OVS extension if active" [Medium,Confirmed]13:17
claudiubbasically, you cannot run neutron-ovs-agent and neutron-hyperv-agent on the vSwitches.13:17
claudiubit's not imediately obvious, you just see failures and exception traces in the neutron-hyperv-agent.log file.13:18
claudiubso, this is also a warning, in case you've been using both. :)13:18
kvinodclaudiub: you mean at a time it should be any one13:19
claudiubif you want to disable the OVS switch extension, run in powershell: Disable-VMSwitchExtension -VMSwitchName switch_name -Name "Open vSwitch Extension"13:19
domi007claudiub: I'm sure that they need to run at the same time to have security groups working, atuvenie worked on this recently13:19
claudiubto enable: Enable-VMSwitchExtension -VMSwitchName switch_name -Name "Open vSwitch Extension"13:19
claudiubkvinod: hm, don't really know why you'd want to run both agents at the same time. But if you do, they shouldn't be configured to use the same switches.13:21
*** primeministerp has joined #openstack-meeting-313:21
kvinodclaudiub: agreed13:21
domi007I can confirm this bug btw as well if you run them simultenously, but it's no surprise13:21
claudiubdomi007: for security groups, you only need the neutron.plugins.hyperv.agent.security_groups_driver.HyperVSecurityGroupsDriver13:21
domi007claudiub: wait, so if I config this in neutron_ovs.conf it will work?13:22
claudiubdomi007: you only need the security groups driver, not the whole agent, as far as I understood from atuvenie.13:22
domi007in that case of course there is no need to run them together13:22
domi007would make a lot of sense13:22
claudiubdomi007: to my understanding, yes.13:22
domi007of course in liberty it doesn't work yet, but atuvenie is working on backporting mitaka patches13:23
claudiubfair warning: HyperVSecurityGroupsDriver on liberty doesn't have the enhanced_rpc implemented, so it won't work.13:23
sagar_nikamclaudiub: how will upgrade cases be handled ? if a customer has older version with neutron-hyperv-agent and wants to move to ovs13:23
*** xavierr-afk is now known as xavierr13:23
claudiubdomi007: but you should be able to use the HyperVSecurityGroupsDriver on mitaka.13:23
domi007so basically we can fully forget the neutron-hyperv-agent, all of its functionality can be done using ovs13:23
domi007claudiub: that's why atuvenie is creating a new liberty installer with cherry-picked backported patches from mitaka to make it work if I'm correct13:24
domi007I was about to apply the patches she sent me, but it seemed like a cumbersome job so I decided to wait for the installer13:25
*** yamamoto has quit IRC13:25
claudiubsagar_nikam: I'm afraid that's a whole other story. it involves neutron network migrations. Basically, if you are using neutron-hyperv-agent, the neutron ports will be bound on the neutron-hyperv-agent, of course.13:25
sagar_nikamclaudiub: so we cant support this kind of upgrades ?13:26
*** jmckind has joined #openstack-meeting-313:27
domi007sagar_nikam: we are planning to do this kind of upgrade, but we are using only VLAN-based networks, so they should be easily transformed into OVS networks/ports (hopefully)...although current live machines might need to be rebooted I'm not sure13:27
claudiubsagar_nikam: I wouldn't say it's imposible. From what I can think of, you just have to change the port's owner, or rebind the ports to the ovs-agent.13:28
*** yamamoto has joined #openstack-meeting-313:28
kvinodclaudiub: but that will have data part hit, i mean migration from hyperv to ovs13:28
kvinodsorry data path13:28
sagar_nikamclaudiub: i think this support should be added in future13:28
claudiubdomi007: I think it should work without rebooting them.13:29
claudiubdomi007: But I do think that in order to work, you will have to disable the neutron ports first, migrate them, then enable them.13:29
*** sdake has joined #openstack-meeting-313:29
claudiubdomi007: when you disable a neutron port, it will also be deleted from the agents.13:29
domi007claudiub: that's what I thought, it's like removing and adding a port to a machine which if I'm right requires the machine to be turned off13:29
sagar_nikamlot of hyperv customers who are using hyper-agent would like to move to ovs ... and they will need this as a supported usecase13:29
claudiubdomi007: anyways, let us know how it goes. :)13:29
domi007sure thing :)13:30
claudiubdomi007: ports, no. Only vNICs or other devices.13:30
domi007oh cool, I learned something new today :)13:30
claudiubdomi007: if you are using generation 2 VMs, you can even hot-plug vNICs and other devices.13:30
claudiubkvinod: I agree. there are some network downtimes on this.13:31
*** jmckind_ has joined #openstack-meeting-313:31
domi007gen2 is a whole different story, not really wishing to go down that road yet :)13:31
claudiubI wouldn't expect them to be long.13:31
claudiubdomi007: what do you mean? :)13:31
*** yamamoto has quit IRC13:32
*** yamamoto has joined #openstack-meeting-313:32
claudiubsagar_nikam: Indeed. It would be interesting to investigate what is the best way to migrate those ports from one agent to another.13:33
*** jlanoux has quit IRC13:33
domi007claudiub: is gen2 code even ready and working in compute-hyperv? I just remember that for example UEFI makes them a lot harder to work with13:33
*** davidsha has joined #openstack-meeting-313:33
claudiubgen2 support was added since Kilo. :)13:33
*** jmckind has quit IRC13:34
claudiubdomi007: hm, by default, uefi is disabled, unless you request it via image metadata property or flavor extra_spec.13:34
sagar_nikamclaudiub: let us know how your investigation goes on it13:34
claudiubimage property os_secure_boot=required or flavor extra_spec os:secure_boot=required13:35
claudiubsagar_nikam: sure. :)13:35
sagar_nikamclaudiub: thanks13:35
claudiubdomi007: we've disabled it by default because not all linux guests support uefi.13:35
sagar_nikamas usual, whenever you have working, we can pick up and verify13:35
sagar_nikamand let you know our results13:36
domi007claudiub: I thought all gen2 machines need to be UEFI, but you can turn off signature verification...but it's prossible that I'm wrong :)13:36
domi007but I'll dig into that then13:36
claudiubso, gen2 VMs rely on EFI boot, instead of a generic BIOS.13:36
domi007indeed, that's what I'm saying. So you can disable signature verification = secure boot, but still will be using EFI...and I'm not sure how well that plays with guests13:37
claudiubhaving UEFI turned on, basically assures that the EFI boot section has not been altered.13:37
domi007ok, I think we are on the same page with this :)13:38
*** coolsvap has quit IRC13:39
*** ddieterly is now known as ddieterly[away]13:39
claudiubdomi007: :)13:39
claudiubanyways. moving on.13:39
openstackLaunchpad bug 1586354 in networking-hyperv "Intermittent Issue seen --Associating a vm from one security group (having tcp rule) to another security group(not having tcp rule) does not stop ssh from happening" [Medium,Confirmed]13:39
*** oshidoshi has quit IRC13:40
claudiubI've confirmed this bug. it should be a big commit for this.13:40
kvinodi see its confirmed13:40
domi007so it wasn't about windows firewall not being on by default13:40
kvinodso do we know what is causing the issue13:41
claudiubbasically, when the port's security group changes, the security groups driver's update_port_filter method is not called. prepare_port_filter is called instead, which just adds new rules.13:41
*** mbound has joined #openstack-meeting-313:41
claudiubupdate_port_filter actually checks what rules are to be added, what rules are to be deleted.13:41
*** sdake_ has joined #openstack-meeting-313:42
kvinodso fix implementation started?13:42
domi007I think this issue surfaced in our deployment as well, the symptoms are really similar13:42
claudiubanyways. I am currently working on it. Now the rules are deleted / added properly. Will send it up for review when it's ready and also wrote some unit tests.13:42
kvinodwhen is the fix expected13:43
kvinodgreat, thanks13:43
claudiubETA: 1-2 days.13:44
domi007claudiub: is this networking-hyperv code or inside the FW driver?13:44
kvinodany idea by when review will be posted13:44
claudiubbut it depends if there are any other urgent matters appearing13:44
claudiubdomi007: networking-hyperv code13:44
claudiubanyways. moving on.13:44
claudiub#topic os-brick status13:45
*** openstack changes topic to "os-brick status (Meeting topic: hyper-v)"13:45
*** sdake has quit IRC13:45
kvinodone more bug is there13:45
*** chandanc has joined #openstack-meeting-313:45
claudiubwell, we've mostly been asked for CI results. They've been posted for each connector: iSCSI, Fibre Channel, SMB.13:45
claudiubwaiting reviews.13:45
openstackLaunchpad bug 1591114 in networking-hyperv "Few Vm's not getting IP due to missing security group rules in scale scenarios" [Undecided,In progress] - Assigned to Krishna Kanth (krishna-kanth-mallela)13:45
*** mbound has quit IRC13:46
*** ddieterly[away] is now known as ddieterly13:46
kvinodi donot see its confirmed13:46
*** yamamoto has quit IRC13:46
sagar_nikamclaudiub: nice, so hopefully we will have os-brick patches merged soon ?13:46
sagar_nikamclaudiub: nice, so hopefully we will have os-brick patches merged soon ?13:46
claudiubsagar_nikam: I really do hope so.13:47
domi007kvinod: #link
sagar_nikamclaudiub: lpetrut: once we have os-brick, can we push for nova patches merged as well13:47
claudiubbut getting the reviews, that's the hard part, IMO. :)13:48
claudiubsagar_nikam: ofc.13:48
sagar_nikamFC support for hyperv is something we have been trying for sometime now13:48
claudiubkvinod: will discuss it at the next topic.13:48
claudiubsagar_nikam: well, until then, there's compute-hyperv. :)13:48
*** yamamoto has joined #openstack-meeting-313:48
domi007claudiub: which we all love :)13:49
claudiub#topic open discussion13:49
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:49
sagar_nikamclaudiub: is it easy to port this to mitaka ? we are on mitaka now, we can try backporting if it is feasible ?13:49
sagar_nikamclaudiub: one topic from me, could you check the BP of my team mate Paul Murray, does it have any impact on FreeRDP ?13:50
claudiubkvinod: sorry for missing that. So, for that, it's harder to confirm / replicate. Which is why I haven't done it yet. I see you've sent some patches up. Will take a look.13:51
domi007sagar_nikam: good thing you raised FreeRDP, we have been testing the new beta from c64cosmin and it works so far fine13:51
*** pgadiya has quit IRC13:51
domi007I just finished haproxy config as well13:51
claudiubkvinod: but for this:  I don't really see how it solves the issue, as it only removes the sleep.13:51
domi007and it looks stable so far13:51
c64cosminSagar_nikam: you mean the one with console objects?13:51
claudiubsagar_nikam: sorry, I didn't understand, port what exactly?13:52
kvinodI will talk to krishna the committer and update the bug13:52
sagar_nikamc64cosmin: yes, last time i gave the BP link13:52
c64cosminI've read the bp shouldn't be a problem13:52
*** yamamoto has quit IRC13:53
c64cosminDomi007: thanks for the info13:53
*** yamamoto has joined #openstack-meeting-313:53
sagar_nikamc64cosmin: claudiub: this is the BP
sagar_nikamdoes it have any impact on freerdp13:53
sagar_nikamdomi007: nice to hear that the new FreeRDP works for you. Does keystrokes work ?13:54
sagar_nikamdomi007: we are yet to pick up the new MSI, Our QA is planning to test it soon13:54
claudiubkvinod: thanks. :) Also, I do remember that that code in was added in order to yield to other threads before adding the rules. This way the neutron-hyperv-agent didn't miss reporting its alive state.13:54
c64cosminDomi, sagar : I have a pull on waiting, this will introduce a plugin system that will allow to change the query parameters13:54
sagar_nikamdomi007: c64cosmin: i will be very keen to see how keystrokes work with this new MSI13:55
domi007sagar_nikam: we never had the keystroke issue, so can't really report on it13:55
domi007but we'll keep at it13:55
domi007and see how it performs13:55
c64cosminAlso will reduce the CPU consumption13:55
c64cosmin, drastically13:55
claudiubkvinod: anyways. I don't sleeping is necessary anymore, since we have native threads, which run independently from the main thread.13:55
*** njohnston|sleep is now known as njohnston13:55
*** vtech has quit IRC13:55
*** amotoki has quit IRC13:55
claudiubkvinod: so, we can go forward with that patch.13:56
c64cosminSagar_nikam: please keep me posted on that13:56
domi007c64cosmin: indeed I was able to see that as well, although it never was eating too much CPU, but it improved indeed13:56
sagar_nikamc64cosmin: sure, will let you know how it works13:56
kvinodIts not possible to type all context behind the fix, probably I will update the bug report with the details.13:57
sagar_nikamdomi007: for me the keystroke was a big issue, let me check with new MSI13:57
c64cosminSagar_nikam: thanks :)13:57
*** MeganR has joined #openstack-meeting-313:57
sagar_nikamc64cosmin: another usal question.... what about debian ?13:57
*** ralonsoh has joined #openstack-meeting-313:58
c64cosminOn it's way13:58
sagar_nikamc64cosmin: thanks13:58
c64cosminAlmost forgot, I will also  implement v3 for keystone api13:58
domi007great! good meeting today guys, thanks!13:58
c64cosminI need a merge first13:59
sagar_nikamc64cosmin: that would be very nice, keystone v313:59
sagar_nikamis it planned soon ?13:59
sagar_nikamor will it take some time13:59
c64cosminIt's the next step to take14:00
kvinodthanks, today it was actually good meeting from neutron front also14:00
kvinodthanks all14:00
c64cosminGood day all14:00
claudiubwell, time's up. :)14:00
sagar_nikami would prefer debian rather than v3, that would be my personal priority... how ever i am fine with the order in which you work14:00
claudiubthanks all for joining. :)14:00
*** shwetaap has joined #openstack-meeting-314:00
claudiubsee you next week!14:00
sagar_nikamfor these features14:00
*** openstack changes topic to "OpenStack Meetings ||"14:00
openstackMeeting ended Wed Jun 15 14:00:56 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:00
openstackMinutes (text):
*** jed56 has quit IRC14:01
njohnston#startmeeting neutron_qos14:01
openstackMeeting started Wed Jun 15 14:01:08 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
*** jed56 has joined #openstack-meeting-314:01
openstackThe meeting name has been set to 'neutron_qos'14:01
njohnston#chair ajo14:01
openstackCurrent chairs: ajo njohnston14:01
ajohello o/14:01
*** shwetaap has quit IRC14:01
ajohi ralonsoh , mr. njohnston14:01
njohnstonGood day all!14:01
*** zhurong_ has joined #openstack-meeting-314:01
njohnstonLet's dive in.14:01
njohnston#topic announcements14:01
*** openstack changes topic to "announcements (Meeting topic: neutron_qos)"14:01
njohnstonLess than a month to N-2!
*** vtech has joined #openstack-meeting-314:02
njohnstonAlso, as a general note, we should keep an eye on QoS commands for the OSC transition:
*** zhurong has quit IRC14:02
njohnston#topic Merged changes14:03
*** openstack changes topic to "Merged changes (Meeting topic: neutron_qos)"14:03
njohnstonThere have been some things that came up since the last meeting.  I just wanted to note them to celebrate the great progress being made, and to keep everyone in the loop.14:03
*** kvinod has quit IRC14:03
*** shwetaap has joined #openstack-meeting-314:03
*** VW has joined #openstack-meeting-314:04
ajowow, nice njohnston thanks for putting that together14:04
njohnstonthat is to add an API test for shared policy, Iztik knocked that one out14:04
ajoI mean :)14:04
*** vtech has quit IRC14:04
*** c64cosmin has quit IRC14:04
njohnstonajo: Oh, I can't claim that, I just made sure the QoS commands were listed :-=)14:04
*** vtech has joined #openstack-meeting-314:05
*** vtech has quit IRC14:05
njohnstonWe also closed a couple of bugs, the "VersionsCallbackNotFound exception when using QoS" was fixed by ajo and "qos-policy update without specify --shared causing it change to default False" was fixed by slaweq14:06
*** iuliat has quit IRC14:06
*** vtech has joined #openstack-meeting-314:06
ajoslawek++ :)14:06
njohnstongood job all!14:06
*** mtanino has joined #openstack-meeting-314:06
njohnston#topic Approved RFEs14:07
*** openstack changes topic to "Approved RFEs (Meeting topic: neutron_qos)"14:07
*** vtech has quit IRC14:07
njohnstonDSCP fullstack: I think this is good now, it just needs an additional +2.14:07
openstackLaunchpad bug 1468353 in neutron "[RFE] QoS DSCP marking rule support" [Wishlist,Fix committed] - Assigned to David Shaughnessy (david-shaughnessy)14:07
njohnstonChange is:
njohnstonthat's the last of DSCP14:07
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:08
njohnstonlast I heard, slaweq has stopped working on this pending  (extended validation)14:08
openstackLaunchpad bug 1586056 in neutron "[RFE] Improved validation mechanism for QoS rules with port types" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:08
ajoyes, we need to bring attention to the DSCP fullstack one14:08
njohnstonI was hoping to catch jschwartz for the dscp fullstack one14:08
ajoyes, improved validation blocks a bit our ability to finish the other ones,14:08
njohnstonbut I think I missed him14:08
*** rbak has joined #openstack-meeting-314:09
ajonjohnston, we need another +2,14:09
ajomay be garyk, let me ping him14:09
njohnstonok great14:09
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:10
*** mickeys has joined #openstack-meeting-314:10
ajosame about rule validation14:10
ajoI need to probably raise that topic on the ML14:10
ralonsohNot working very well14:10
ajowith the RFE14:10
ralonsohI sent a mail this morning14:10
ajoralonsoh, go ahead, tell us,14:10
ajowhat's the topic, I missed it14:10
ralonsohNo problem, maybe it's better by mail14:11
ralonsohToo long14:11
*** ddieterly is now known as ddieterly[away]14:11
ajoralonsoh, what's the topic of the email you sent ?14:11
ajojust to link it here14:11
ajothanks :)14:11
davidshano prob :)14:11
ralonsohEgress qos in ovs is not working14:11
ralonsohfor min bw14:11
ajoralonsoh, I will check, bit it's working for me14:12
ajoI tested it, may be theres some detail that needs polishing on your implementation,14:12
njohnstonoh sorry yopu already got the link ajo14:12
davidshanjohnston: that one looks nicer :P14:12
*** vhoward has joined #openstack-meeting-314:13
ajoralonsoh, how did you arrange the queues/etc ?14:13
ralonsohYes, qos and queues14:13
ralonsohand ovs flows14:13
ajoralonsoh, I mean, how did you arrange them14:13
ajoI'll probably better look at your patch14:13
ajoand review it :)14:13
ralonsohi need to upload it14:13
ajoplease upload it as soon as you could, and ping me (IRC / email)14:14
ralonsohajo: ok14:14
ajoovs / kernel is very nitpickg about how it works14:14
ajoit has to be hierarchical14:14
ajoand all queues on the outgoing interface14:14
*** moshele has joined #openstack-meeting-314:14
ajoor , in a veth from br-int to br-XXXX14:14
*** chandanc has quit IRC14:14
ajotop queue has the "max" set to the link speed we know about14:14
ajoand the queues under it, have min: set as per flow14:15
*** mickeys has quit IRC14:15
ralonsohajo: I know14:15
ajoralonsoh, so did you set them on a veth? or the external interface?14:15
ralonsohajo: on the external interface14:15
ajomay be it's just better to try your code locally and see what's wrong14:15
ralonsohbut in the ovs port14:15
ajoralonsoh, in the ovs port?14:16
ralonsohajo: yes14:16
ajowhat do you mean by the ovs port?14:16
ralonsohin the port connected to the external interface14:17
ralonsohto shape egress traffic14:17
*** zz_dimtruck is now known as dimtruck14:17
ajodo you mean14:17
ajoeth0<--->br-ex1 ?14:17
ajoeth0 for example ?14:17
ajook, yes, that was the suggested approach from ovn14:17
*** vtech has joined #openstack-meeting-314:17
ajobut I didn't understand how to match the queue ID at the ovs side to the queue at that interface14:18
ajoto do that, I believe you have to set the set_queue flow in the br-ex114:18
ajonot br-int14:18
*** mickeys has joined #openstack-meeting-314:18
ralonsohajo: ok14:18
*** sigmavirus24_awa is now known as sigmavirus2414:18
*** chandanc has joined #openstack-meeting-314:18
*** ddieterly[away] is now known as ddieterly14:19
njohnstonanything else before we move on?14:19
ralonsohno, thanks14:19
ajoralonsoh, ping me when your code is around, I'll try to test it and help, and thanks a lot for tackling this hard stone :D14:19
ajonjohnston, no, thanks :)14:19
ralonsohajo: ok14:19
njohnston#topic Not Yet Approved RFEs14:19
*** openstack changes topic to "Not Yet Approved RFEs (Meeting topic: neutron_qos)"14:19
openstackLaunchpad bug 1586056 in neutron "[RFE] Improved validation mechanism for QoS rules with port types" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:20
njohnstonNeutron Drivers did not get to it last time14:20
njohnstonSlaweq has a change up:
*** vtech has quit IRC14:20
ajo#action ajo publish ML thread about "[RFE] Improved validation mechanism for QoS rules with port types"14:20
ajowe need to bring attention to that one14:21
njohnstonit will be an interesting discussion14:21
ajoit will ':)14:21
openstackLaunchpad bug 1580149 in neutron "[RFE] Rename API options related to QoS bandwidth limit rule" [Wishlist,Confirmed] - Assigned to Slawek Kaplonski (slaweq)14:21
*** Siri_ has joined #openstack-meeting-314:21
njohnstonThe way I read the last comment on this, Slaweq thinks this might not be necessary?14:21
*** galstrom_zzz is now known as galstrom14:22
*** Poornima has quit IRC14:22
ajonjohnston, correct, with improved validation, we can forget that one14:22
*** sagar_nikam has quit IRC14:22
*** ericksonsantos has joined #openstack-meeting-314:22
*** mickeys has quit IRC14:22
njohnstonshould it have a status change to reflect that?14:22
*** moshele has quit IRC14:22
njohnstonor wait until validation susses out a bit?14:22
ajonjohnston, I guess wait for validation, I don't know :)14:23
*** moshele has joined #openstack-meeting-314:23
njohnstonand lastly14:23
openstackLaunchpad bug 1505631 in neutron "[RFE] QoS VLAN 802.1p Support" [Wishlist,Confirmed] - Assigned to Reedip (reedip-banerjee)14:23
njohnstonno activity on that one14:23
*** vtech has joined #openstack-meeting-314:23
ajoabout DSCP fullstack: "<garyk> ajo: done"14:23
*** jrist has quit IRC14:23
njohnstonYep, it's in gate now :-)14:23
njohnston#topic Bugs14:23
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:23
ajonjohnston, yes, I guess QoS VLAN seems low prio RFE unless we have more interest or push14:24
*** Shiriul has joined #openstack-meeting-314:24
openstackLaunchpad bug 1587291 in neutron "Specifying '-F' or '--filed' parameter in the qos related commands, returns abnormal result" [Undecided,In progress] - Assigned to dongwenshuai (dong-wenshuai)14:24
*** moshele has quit IRC14:24
njohnstonthis is a newish one, filed end of May14:24
njohnstonThere are three changes to fix this:
*** vtech has quit IRC14:25
njohnstonI wanted to mention them here so folks could go take a look14:25
ajooh nice14:25
ajoI wasn't aware of it14:25
*** Shiriul has quit IRC14:26
openstackLaunchpad bug 1566514 in neutron "Enable sorting and pagination by default" [Wishlist,In progress] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)14:26
njohnstonThis has 9 changes, 2 of which are QoS related:
njohnstonihrachys is working on these14:26
ihrachysreviews welcome14:26
openstackLaunchpad bug 1515564 in neutron "Internal server error when running qos-bandwidth-limit-rule-update as a tenant" [Low,In progress] - Assigned to Liyingjun (liyingjun)14:27
njohnstonlooks like that needs reviews14:27
*** vtech has joined #openstack-meeting-314:28
*** VW has quit IRC14:28
*** pt_15 has joined #openstack-meeting-314:28
njohnstonwe also have one new change that does not have a corresponding bug14:28
*** yujunz has joined #openstack-meeting-314:29
ajoHmm, I thought I had reviewed this today, I'll do14:29
ajoah, no I started, but I didn't submit :)14:29
njohnstonthat is for adding a tempest scenario test for QoS; iztik is working on it.14:29
njohnstonajo: excellent14:29
njohnston#topic Open Discussion14:31
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"14:31
njohnstonoverall there was a lot of great work done the last 2 weeks14:31
njohnstonso kudos to the team14:31
ajoyes, awesome folks14:31
davidshaquick open, who is going to the mid cycle?14:31
ralonsohyes, good question14:32
*** rhagarty has quit IRC14:32
ajoif you have time, also review: & specs (I had already some help there, thanks davidsha & slawek)14:32
njohnstonmy request for travel was declined14:32
ajoI think ihrachys requested14:32
*** Siri_ has quit IRC14:32
ajoand I can't (too much pressure on family)14:32
ihrachysajo: there is no approval yet, we are waiting14:33
ajoJust as a note, also14:34
ajoI will probably be on PTO from Aug 19th to +2 weeks, awful time in terms of feature freeze / RC,14:34
ajoI will be reviewing nightly,14:34
ajobut I want to sort out things as soon as possible (before) so I don't block or put any extra stress on anybody14:35
ajoas it happened previous year (sorry ihrachys  & jlibosva)14:35
*** yujunz has quit IRC14:35
njohnstonthanks ajo14:35
ajoI tried to arrange different dates but it's the only time that works with my wife's job :/14:36
njohnstonSo from a high level it looks like the highest priority work in QoS land is the validation patch, yes?
*** jrist has joined #openstack-meeting-314:36
njohnstonSo if folks could give particular attention to reviews on that, there are a number of things that getting it done will unblock.14:37
ajonjohnston, first, agreement on that such way is desired and reasonable from the neutron API point of view14:37
ajothen the patch could be finally polished and merged14:37
*** rhagarty has joined #openstack-meeting-314:37
ajoif that doesn't work, option B is separate rules per direction (egress/ingress), but ... again we will have the same problem the day we want to add classifier field to the rules14:38
njohnstonOK, so perhaps we can have that discussion in the drivers meeting.  ajo will you be able to make the next drivers meeting?14:38
ajonjohnston, I can try it, but it's 12am/1am here if I don't remember wrong, let me check14:38
njohnstonI know you had mentioned an ML thread as well, I just don't want it to drag on too long14:39
ajonjohnston, agreed14:39
ajono, I have to mention it on ML14:39
*** VW has joined #openstack-meeting-314:39
njohnstonok, I will try to represent if it comes up in drivers14:39
ajoyes Thu 00:00 am to 1am14:40
ajoI will try to be present as much as I can14:40
njohnstonok, anything else anyone wants to bring up?14:40
njohnstonHearing nothing, I'll give 18 minuted back.  Good day all!14:42
*** openstack changes topic to "OpenStack Meetings ||"14:42
openstackMeeting ended Wed Jun 15 14:42:18 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:42
openstackMinutes (text):
davidshathanks, cya14:42
ajoThank you njohnston !!!14:42
*** VW has quit IRC14:44
*** cjvolzka has joined #openstack-meeting-314:44
*** hdaniel has quit IRC14:46
*** yamamoto has quit IRC14:46
*** rhochmuth has joined #openstack-meeting-314:47
*** hosanai has joined #openstack-meeting-314:49
*** Shiriul has joined #openstack-meeting-314:52
*** vtech has quit IRC14:53
*** Niham has quit IRC14:53
*** zhurong_ has quit IRC14:54
*** Niham has joined #openstack-meeting-314:54
*** Siri_ has joined #openstack-meeting-314:55
*** vtech has joined #openstack-meeting-314:55
*** numans has quit IRC14:55
*** Niham has quit IRC14:55
*** jayahn has joined #openstack-meeting-314:56
*** Niham has joined #openstack-meeting-314:56
*** Kamil_ has joined #openstack-meeting-314:57
*** Niham has quit IRC14:57
*** Niham has joined #openstack-meeting-314:58
*** tonytan4ever has joined #openstack-meeting-314:58
*** Niham has quit IRC14:59
*** vtech has quit IRC14:59
*** yamahata has quit IRC14:59
*** Niham has joined #openstack-meeting-314:59
*** koji has joined #openstack-meeting-314:59
*** cbellucci has joined #openstack-meeting-314:59
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jun 15 15:00:00 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
*** yamahata has joined #openstack-meeting-315:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmuthagenda is at,
rhochmuthAgenda for Wednesday June 15, 2016 (15:00 UTC)15:00
rhochmuth1.Mid-cycle plan15:00
rhochmuth2.Summit plans15:00
rhochmuth4. 15:00
rhochmuth4.Any plans/updates on dimensions resource?15:00
*** Niham has quit IRC15:00
rhochmuthhi everyone15:00
rhochmuthlooks like a light agenda for today15:01
*** Niham has joined #openstack-meeting-315:01
*** bklei has joined #openstack-meeting-315:01
rhochmuthso, that will leave time for misc discussions/topics15:01
rhochmuthFirst up, is the mid-cycle15:01
*** slogan has joined #openstack-meeting-315:01
rhochmuth#topic mid-cycle15:01
*** openstack changes topic to "mid-cycle (Meeting topic: monasca)"15:01
*** iyamahat has joined #openstack-meeting-315:01
*** sc has joined #openstack-meeting-315:01
*** VW has joined #openstack-meeting-315:02
rhochmuthWe are on for July 19th and 20th, 8:00 AM MST to 1:00 PM MST15:02
rhochmuthVia a remote webex session15:02
*** tgraichen has joined #openstack-meeting-315:02
*** Niham has quit IRC15:02
*** witek has joined #openstack-meeting-315:02
rhochmuthfabiog: has the webex in15:02
*** Niham has joined #openstack-meeting-315:03
rhochmuthi'll start putting together an evernote this coming week where we can start to track agenda, and other logistics15:03
rhochmuthdoes that sound good for everyone?15:03
bkleiworks for me15:03
*** Siri_ has quit IRC15:04
slogansounds good15:04
*** tsv_ has joined #openstack-meeting-315:04
rhochmuthso moving on15:04
rhochmuth#topic summit15:04
*** openstack changes topic to "summit (Meeting topic: monasca)"15:04
rhochmuthjust a reminder that CFP is open15:04
*** ezpz has joined #openstack-meeting-315:04
rhochmuthdeadline is July 13th15:04
*** toddjohn has joined #openstack-meeting-315:04
rhochmuthit is earlier this time around I believe15:04
rhochmuthat least it feels that way15:05
rhochmutha couple of sessions that i think makes sense for monasca at a more global level15:05
*** Niham has quit IRC15:05
rhochmuth1. Update on Monasca15:05
rhochmuth2. Tutorials/bootcamps15:05
sloganI got the impression that 2. was needed in Austin15:06
sloganso good :-)15:06
rhochmuthI think a presentation supplying an update on the overall Monasca project woudl be good15:06
rhochmuthall the features, deploys, connections to other projects, …, might be good to review15:06
witeki agree15:07
rhochmuthso, i think getting some authors on that would be good15:08
rhochmuthi'm assuming you are interested witek15:08
witeki won't say no ;)15:08
rhochmuthi don't know if there is a limit on authors, but would like to cover a potpourri of all the stuff that is going on15:08
*** sdake_ has quit IRC15:08
rhochmuthi hope i used that word potpourri correctly15:09
rhochmuthmayeb smorgasboard is better15:09
jayahnusually, program committee does not like more than three authors per presentation.15:09
rhochmuthanyway something along those lines15:09
*** numans has joined #openstack-meeting-315:09
*** toddjohn has quit IRC15:09
sloganunless it is sold as a panel discussion15:09
rhochmuthhmmm, i haven't heard that before15:10
*** sdake has joined #openstack-meeting-315:10
rhochmuthi don't think a panel session makes sense15:10
rhochmuththe other idea is more bootcamps/tutorials15:10
jayahnthey think a presentation with many authors are "free riders" for summit pass.15:10
sloganunless it were people talking about their experiences and where they see it going15:10
rhochmuthi think another session like we did in austin would be good15:10
rhochmuthbut, i'm wondering if a session on deploying monasca makes sense too15:10
rhochmuthjayahn: yeah, i can see that15:11
sloganaka twc?15:11
*** jayahn has quit IRC15:11
*** sdake has quit IRC15:11
sloganthey have an interesting enough use case15:11
witekthe interest for the bootcamp in austin was big15:11
rhochmuthyeah, that room had several hundred attendees15:12
*** yamamoto has joined #openstack-meeting-315:12
rhochmuthso, that makes be think that a session or two in barcelona would be good15:12
sloganproblem was I think people were looking for something more intimate and hands on15:12
rhochmuthanyway, please let me know if you are interested15:12
rhochmuthi dont' want to monopolize all this15:13
rhochmuthslogan: i agree15:13
bkleislogan, so soft music and mood lighting?15:13
rhochmuthalthough, i don't think anyone wants to get intimate with me15:13
*** jayahn has joined #openstack-meeting-315:14
rhochmuthaccepts for u bklei15:14
bkleiroger that15:14
rhochmuthis anyone interested in submitting a tutorial/bootcamp?15:15
rhochmuthi think we could do two submissions this time15:15
rhochmuthbuilding on austin15:15
jayahnprobably not as a bootcamp, but we are willing to provide "real use case" stroy if it is valuable15:15
witeki think we could join it15:15
jayahnas a part of any presentation if it helps15:16
*** Kuckkuck has joined #openstack-meeting-315:16
rhochmuthjayahn: that might make more sense for a general monasca session15:16
rhochmuthok, so i just wanted to get the ideas flowing, and gauge interest15:17
rhochmuthlet's close on this for now, and sync up next week again15:17
*** dimtruck is now known as zz_dimtruck15:17
rhochmuthwe still have 4 weeks for submissions15:17
*** kzaitsev_mb has quit IRC15:17
*** banix has joined #openstack-meeting-315:18
rhochmuth#topic reviews15:18
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:18
*** zz_dimtruck is now known as dimtruck15:18
sloganI somewhat interested in some kind of "up and running in 5 minutes" sort of thing, showing how my 10 mines of python write switch data to Monasca, and how it can be visualized in grafana, but not sure I could talk in much detail about monasca itself the way others can15:18
*** jobrs has joined #openstack-meeting-315:19
rhochmuthslogan: sounds like a good talk name: "Monasca: Up and running in 5 minutes"15:19
*** anilvenkata has quit IRC15:19
ericksonsantosslogan, +115:19
sloganthen later in the week there is a deeper dive15:20
slogancan we get 3 others to talk about their depolys?15:20
sloganer, derploys15:20
rhochmuthSo, we've got this review for adding support for sessions in the Python Keystone client15:20
rhochmuthsorry, handling 2 discussion at once,15:21
sloganmy bad15:21
rhochmuthit is ok with me15:21
rhochmuthI'm just wondering if we can get some more reviews on,
rhochmuthI've reviewed, abd looks good to me15:22
rhochmuthThere are a lot of +1's, but most of them are all buddies, so i don't trust them15:22
witekI'll take a look15:22
rhochmuthactually, i do trust them, but looking for some reviews outside of that group15:23
rhochmuththanks witek15:23
rhochmuthif you +1, i'll merge15:23
rhochmuthor please feel free to merge too15:23
rhochmuthyou have +2 prics15:23
rhochmuthI just want to point out this review,
*** tonytan4ever has quit IRC15:24
rhochmuthThere have been a lot of new metrics added recently15:24
rhochmuththis review allows you to disable them15:24
rhochmuthor enable them15:24
rhochmuthwhichever way15:25
rhochmuthi just think everyone needs to understand that all these new metrics that are being introduced put a lot of load on Monasca15:25
rhochmuthWe'll be doing a lot more scale testing over the next couple of months15:25
jayahnwe needed that disabling feature. :) great to see this.15:26
bkleii love the ability to turn them off via config -- that's great15:26
rhochmuthbut this review is for disabling/enabling them if you don't need them and don't like the load being added15:26
bklei+1 jayahn15:26
sloganthat was an easy one to review :-)15:26
*** andreas_s has quit IRC15:26
rhochmuthwe briefly discussed making a general solution for enabling/disbling things rather than approaching this piece meal15:26
rhochmuthbut we're not doing that right now15:26
rhochmuthso, sometime in the future maybe we'll get back to addressing this in a more general and architected/designed way15:27
rhochmuthfor now, this is the best we can do15:27
*** qwebirc10220 has joined #openstack-meeting-315:27
rhochmuthalso, there is a reivew for controlling the rate at which disk metrics are collected15:27
rhochmuthIt is a similar theme15:28
*** tellesnobrega is now known as tellesnobrega_af15:28
rhochmuthThis review allows you to collect the disk metrics, but at a slower rate15:28
rhochmuthjayahn and bklei, thanks15:29
rhochmuthso, anyway i think folks should keep an eye on the agent15:29
rhochmuthmost of it should be ok, but there have been quite a few added metrics and changes15:30
rhochmuthso, just good to watch, and hopefully we have enough controls in-place that we dont' add a huge amount of metrics if not required15:30
rhochmuth 15:30
bkleithat's me -- not a big change15:31
bkleijust an optimization15:31
*** coolsvap has joined #openstack-meeting-315:31
rhochmuthso, what does it do15:31
bkleiprevents hammering nova if we have more than one 'ghost' vm15:31
bkleia vm known to virsh/libvirt but not nova15:31
bkleiin our lab env, we have up to 10 per compute node, and poor nova gets hammered each time the agent wakes up15:32
bkleirefreshing the cache multiple times doesn't help15:32
*** VW has quit IRC15:32
bklei(the real problem is the ghost vms -- and we're addressing this -- but the plugin could be smarter)15:32
rhochmuthok, sounds good, i'll review and merge15:33
rhochmuthafter a few more +1's15:33
*** VW has joined #openstack-meeting-315:33
bkleigracias -- it's the same change we added to the ovs plugin that's merged, it's what made me think to do it in libvirt15:33
rhochmuthok, sounds good15:33
rhochmuth#topic dimensions resource15:34
*** openstack changes topic to "dimensions resource (Meeting topic: monasca)"15:34
rhochmuthAny plans/updates on dimensions resource?15:34
jayahni do have a quick question on monasca-agent plugins. if it is okay15:34
rhochmuthsure jayahn15:34
rhochmuthdidn't mean to rush through15:34
jayahnwe would like to add capability to check ping rsp time & success rate. I was thinking to add these to existing "host alive" checks. but, then think it is not about checking if host is alive. in that sense, might be better to have separate ping plugin.15:34
jayahni need your advise. :)15:34
rhochmuthi think it is a great idea15:35
*** oshidoshi has joined #openstack-meeting-315:35
rhochmuthnot sure if host alive makes sense or not15:35
*** moshele has joined #openstack-meeting-315:35
rhochmuthi think for the http status check we report both up/down and latency15:36
*** yamamoto has quit IRC15:36
*** yamamoto has joined #openstack-meeting-315:36
rhochmuthhowever, pinging the systems multiple times, once for aliveness and once for latency sounds inneficient15:36
bklei'ping' gets more complicated -- to be done right you really also have to look at security groups -- is ping allowed, etc15:36
*** oshidoshi1 has joined #openstack-meeting-315:37
jayahnbklei that is true.15:37
rhochmuthwe have ping for VMs and ping for infrastructure15:37
rhochmuthThere is this for physical hosts,
rhochmuthand this for libvirt VMs at,
*** ddieterly is now known as ddieterly[away]15:39
*** kzaitsev_mb has joined #openstack-meeting-315:39
rhochmuthjayahn: are you referring to the host_alive check?15:39
jayahni was looking into ping for infrastructure.15:40
jayahnbut, host_alive15:40
*** oshidoshi has quit IRC15:40
jayahnyeap. host_alive15:40
*** yamamoto has quit IRC15:40
*** chandanc has quit IRC15:41
rhochmuthi'm regretting calling that plugin host_alive15:41
*** chandanc has joined #openstack-meeting-315:41
*** tgraichen has quit IRC15:41
rhochmuthmaybe, host_status would have been better15:41
jayahnyeap. a word "host_alive" has very specific and narrow meaning.15:41
rhochmuthi think it would be preferable to have a single plugin do both simultaneousely15:41
rhochmuththat check is one of the harder checks we do15:42
rhochmuthit has to be multi-threaded to complete in a reasonable amount of time15:42
rhochmuthi hate to have to basically run the same pings to then get latency15:43
rhochmuthso, i think should add the latency to host_alive15:44
*** Kuckkuck has quit IRC15:44
rhochmuthbut I'm not sure about renaming15:44
rhochmuthanyway, that is idea number 115:45
rhochmuthmaybe it is a bad one15:45
*** dwalleck has joined #openstack-meeting-315:45
jayahnhost_status would be more suitable name, as you said. but, i will go ahead to write blueprint to add the latency to host_alive check for now.15:46
rhochmuththanks jayahn15:46
rhochmuth#topic dimensions resource15:47
*** openstack changes topic to "dimensions resource (Meeting topic: monasca)"15:47
*** catherineD has joined #openstack-meeting-315:47
rhochmuthAny plans/updates on dimensions resource?15:47
rhochmuthI don't have any immediate plans15:48
rhochmuthnot sure who asked that question15:48
*** yamamoto has joined #openstack-meeting-315:48
rbakI'm pretty sure bklei added it.15:48
bkleithat's me15:48
bkleiat the summit you mentioned HPE was working it -- true?15:48
rhochmuthwe were planning on it, but it didn't materialize15:49
*** ddieterly[away] is now known as ddieterly15:49
bkleiso no plans to pick it up?  we may if that's the case15:49
rhochmuthare you seeing where this is going to be real helpful15:49
bkleirbak would really like it to make grafana templating more effecient15:49
rhochmuthahhh, yeah, it makes complete sense15:50
rhochmuthif you want to pick it up that would be great15:50
witekso it would be listing all dimensions stored in influx/vertica?15:50
*** pcaruana has quit IRC15:50
rhochmuthi'm guessing we won't get to it over the next month or two or three15:50
bkleiok -- i probably will, will confirm with resource allocaters15:50
*** ewang12 has joined #openstack-meeting-315:50
rhochmuthwitek: the idea is that once you know a metric name, that you want to then list the dimensions for that name15:51
*** mfedosin has joined #openstack-meeting-315:51
rbakActually that's not quite right15:51
rhochmuthsonce you select a dimenion name, you then want to know all the valaues for that dimension name15:51
rbakWhat we need is given a specific dimension key, list all dimension values.15:51
*** nkrinner has quit IRC15:51
bkleilike 'hostname'15:52
*** jrist has quit IRC15:52
rbakTempting isn't tied to a specific metric unfortunately.15:52
rbakIf you want to get the dimensions for a specific metric at the moment you can do a metric-list with --name, so that's mostly covered already.15:53
rhochmuthso, can we review next week?15:53
*** Sukhdev has joined #openstack-meeting-315:53
bklei:) i'll start soon15:53
bkleia bit of a rats-nest -- java/python/vertica/influxdb15:54
bkleithat's why i wanted u to do it :)15:54
rhochmuthwell, i personally fell like this is a job for rbrandt15:55
rhochmuthhe's been in that code the most15:55
rhochmuthjust not sure i can get him15:55
rhochmuthi'll check15:55
bkleik -- i'll include him in the reviews if i start it -- but will wait to hear from you/him15:55
rhochmuthit is hard diving into that code just adding a new feature15:56
bkleihe's alot smarter than me anyway15:56
rhochmuthbut you are better looking15:56
bkleisays u15:56
*** tonytan4ever has joined #openstack-meeting-315:56
rhochmuthwe've got 3 minutes15:57
rhochmuthanyone have anythign in closing15:57
rhochmuthshoudl we tee upo something for next week?15:57
rhochmuthanything urgent?15:57
*** Rockyg has joined #openstack-meeting-315:58
rhochmuthok, i guess that is it15:58
rhochmuthended early for once15:59
rhochmuthbye everyone15:59
bkleithx roland15:59
*** toddjohn has joined #openstack-meeting-315:59
*** bklei has quit IRC15:59
*** ezpz has quit IRC15:59
*** koji has quit IRC15:59
*** cbellucci has quit IRC15:59
*** openstack changes topic to "OpenStack Meetings ||"15:59
openstackMeeting ended Wed Jun 15 15:59:41 2016 UTC.  Information about MeetBot at . (v 0.1.4)15:59
openstackMinutes (text):
*** hosanai has quit IRC15:59
*** slogan has quit IRC15:59
*** qwebirc10220 has quit IRC15:59
markvoelker#startmeeting defcore16:00
openstackMeeting started Wed Jun 15 16:00:03 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at
*** Kamil_ has quit IRC16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** Shiriul has quit IRC16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
markvoelker#chair hogepodge16:00
openstackCurrent chairs: hogepodge markvoelker16:00
*** witek has left #openstack-meeting-316:00
markvoelker#link today's agenda16:00
*** cbouch has joined #openstack-meeting-316:01
*** gema has joined #openstack-meeting-316:01
markvoelkerSo, lots to talk about today I think folks.  I want to make sure we get through at least the first three items on the agenda as they're a bit time-sensitive.16:01
markvoelkerLet's dive right in.16:02
markvoelker#topic Additional properties on API responses16:02
*** openstack changes topic to "Additional properties on API responses (Meeting topic: defcore)"16:02
*** shamail has joined #openstack-meeting-316:02
markvoelker#link Thread on the -dev ML16:02
hogepodgeHas everyone had a chance to read that thread?16:02
dwalleckI read through early yesterday evening. Seems to be a hot topic16:03
*** shamail has quit IRC16:03
* markvoelker has, and has replied to it a few times16:03
hogepodgeSome vendors have been caught with putting additional properties into Nova API responses.16:03
RockygJust wanted to say that if you read through the comments on the review that turned off the ability, there was concern then of an incompatible change that was ignored16:03
*** shamail has joined #openstack-meeting-316:03
RockygI will be replying later today.16:03
*** tsv_ has quit IRC16:03
hogepodgeI'd like to give them more time to either a) remove the extra properties or b) work with upstream to get those properties (or something like it) microversioned16:03
*** toddjohn has quit IRC16:04
*** brunssen has joined #openstack-meeting-316:04
* shamail sneaks in16:04
RockygAlso, some additiional properties were grandfathered in, but unless you put in a ptch for yours, they weren't considered16:04
catherineDIMO,  the tests serves the purpose of bring out interops issues.  We should not change the test.  From Powered Logo point of view, I think we should flag the tests until 2017.0116:04
*** itxaka has quit IRC16:04
hogepodgeIdeally, this would be accepted by upstream qa as a temporary feature to tempest, and by this working group as an acceptable practice.16:04
VanLI think there is a fundamental misunderstanding at play in that thread: None of what Tempest does, or what Nova does, or what the TC does, defines what defcore is. The specific implementation may involve a change to tempest, but tempest devs *do not* get a veto (or fiat) on how defcore-required tests evolve.16:04
catherineDthat is the purpose of RefStack that we want to collect data... if we change the tests the data really does not mean much16:05
dwalleckcatherineD: My sticking point still is that we're not changing the test. If there was a test for API contracts, that would make sense. That's not what happened though16:05
*** sdake has joined #openstack-meeting-316:05
RockygVanL, ++16:05
VanLTrenish's comments about "This is the way we do it, so screw it" is fundamentally wrongheaded16:05
Rockygdwalleck, ++16:05
dwalleckIf there were actual tests for API response contracts, we could be talking about flagging or making those tests advisory16:05
catherineDdwalleck: the proposal is to comment out the response checking that is changing the test to me16:05
hogepodgecatherineD: we would flag a whole wealth of compute tests, making the guideline meaningless. This is a syntax vs functional change16:05
catherineDhogepodge: so be it16:05
*** chandanc has quit IRC16:06
VanL+1 catherineD16:06
RockygAlso, Matt's comment of "I'd never consider Juno"  when that's where the problem is16:06
catherineDthe the same thing as mask out checking the fundamental of API response compliant16:06
hogepodgethere's still meaning behind saying "this api performs this action"16:06
catherineDthat is the #1 enemy of interops16:06
VanLI also think that this is essentially an undeclared capability16:06
dwalleckcatherineD: Not necessarily. This is all the work I had to do to fix my issues, which was 3 changes
*** numans has quit IRC16:07
RockygcatherineD, they changed the original test to encforce the checking16:07
RockygAt the start of Kilo cycle16:07
hogepodgedwalleck: that fixes everything?16:07
VanLThere was a defined capability "Add stuff to the API" that was, for obvious reasons, not tested16:07
hogepodgedwalleck: that's really useful to know16:07
dwalleckhogepodge: for Rackspace for extra properties? Yes16:07
VanLThis was acceptable and encouraged - just until it was not16:07
catherineDI would agree if we add a test to specificly test for the response16:07
catherineDto hightlight the issue areas16:08
VanLWhat I would do is propose a new test that tests *only* strict API checking16:08
VanLAdd that test as an independent test of an independent capability16:08
catherineDRockyg: so the change is to correct the test that is why I think we should flag the tests16:08
catherineDVanL: ++++16:09
VanLAnd then turn off that capability for all defcorish tests16:09
catherineDVanL: +++16:09
RockygAlso, catherineD, the checking is in the code itself starting in either Kilo or sometime later.  So, it's code enforced, not test enforced16:09
*** krotscheck is now known as krotscheck_dcm16:09
catherineDRockyg: my thinking is we should not mask out the issue that we discover ....16:10
dwalleckcatherineD: The problem is that since the property checking isn't it's own test, you would have to flag every test. To me it's a separation of concerns issue, but I know that's not the opinion of the QA folks16:10
RockygNot mask, but not fail.16:10
VanLI also think that we need to make another decision - probably a discussion for midcycle - as to whether defcore's purpose is to put a ceiling on functionality or a floor16:10
catherineDI agree with VanL: 's proposal that we should still the the response behavior16:10
*** shamail has quit IRC16:10
VanLI think that in general, defcore should present a floor - a base layer of agreed-upon capability16:11
RockygIf you look to Sean's email, it*will* be handled in code for Newton.  But our tests are generally used for older releases16:11
catherineDMasking out the issue is not why we want to spend all our time and energy for interop test16:11
VanLAnd I think that should be strictly enforced16:11
VanLbut I think that we should, as defcore, allow vendors to add stuff to the API, or to responses.16:11
hogepodgeUpstream has been very clear that additional responses and extensions that aren't upstream are out. I feel obligated to fall in line with that eventually. I'm asking for extra time for vendors to either remove the extra attributes or work with upstream to release new microversions16:11
cjvolzkaVanL: +16:11
RockygI think we all think of DefCore here as "floor"16:11
VanLMaybe there is a namespacing issue - vendor-specific stuff under /vendor/16:12
dwalleckhogepodge: ++16:12
hogepodgeAlso, I've been told by python-openstack client that strict response checking is on the feature list for their client, so this is going to be the norm in the future rather than the exception16:12
Rockyghogepodge, ++16:12
catherineDhogepodge: by not testing the response we won't know which vendors still have the issue16:12
hogepodgeMy goal here is to raise the issue transparently to the community and buy time.16:12
VanLhogepodge: As soon as there is an upstream way for vendors to fix issues and add capabilities.16:13
hogepodgecatherineD: we will know exactly with calls are returning extra data, my proposal makes it a requirement to report it16:13
VanLI fundamentally do not agree with "the fastest any vendor can go is at the speed of the community"16:13
dwalleckIf this is the norm going forward and we don't change Tempest, is there a way we could make the DefCore guideline specifically saying that API response checking is a required thing?16:13
catherineDhogepodge: who will report and how?16:13
Rockyghogepodge, until the enforcement is in the code, I don't think we can fail the vendors who take advantage of the laxness16:13
VanLI *do* agree that any vendor-specific functionality should be explicitly marked, so as to not affect interop16:13
*** tonytan4ever has quit IRC16:14
hogepodgeVanL: this is why, at a minimum, I also thing we need to start using a branch of Tempest and back-porting changes, so we have a known working instance at time of guideline approval16:14
Rockyghogepodge, ++16:14
dwalleckI'd just like to make sure the requirement is captured in some way that can be referenced, since you can't currently point to a test right now that defines that requirement16:14
hogepodgecatherineD: vendors will report to the foundation at time of applying for the trademark, and the APIs that vary will be listed in their marketplace entry16:15
VanLhogepodge: +1, at a minimum. We will need to fork sooner or later. Friendly fork, but fork16:15
*** lpetrut has quit IRC16:15
RockygDefCore does not work from trunk, it works on releases that *aren't* changing so neither should he test/test frameworks16:15
*** shamail has joined #openstack-meeting-316:15
*** ddieterly is now known as ddieterly[away]16:16
VanLdwalleck, hogepodge: What about adding a new "adheres to strict API checking" test, and adding that as advisory?16:16
catherineDVanL: ++16:16
VanLAnd turning it off in all other tests (per dwalleck's changes)?16:16
docaedoI wouldn't think a fork would be required if you can find a tempest tag or release the stick with16:16
Rockygdwalleck, it's in a design spec.  Change in code functionality.  They changed the tests first to prevent regression in new code being added16:16
* docaedo forgot to say hi earlier16:16
*** piet has joined #openstack-meeting-316:17
Rockygdocaedo, problem is, if you go for a tag, you don't get any of the new tests or bugfixes16:17
catherineDRockyg: as a interop testing group.  Arer't we glad that they change the tests to expose this?16:17
hogepodgeVanL: I really don't know. I don't disagree with the response being checked inline, I just want more time to let that be optional.16:17
VanLdocaedo: The difference is in the purpose for testing. Gate testing (avoid regression) is fundamentally different from defcore testing (assure baseline interop)16:17
*** jayahn has quit IRC16:18
RockygcatherineD, yes, but not without fixing the code, too.16:18
dwalleckVanL and hogepodge: By hogepodge's original email, if we could make those "additionalProperties" fields configurable, which shouldn't be difficult, then we could really handle this problem without impacting Tempest further16:18
VanLhogepodge: /me waves back at old "atomic" discussions16:19
catherineDRockyg: fixing the code means do not allow extension?16:19
docaedoVanL and Rockyg understood, and I assume "fork tempest" does not intend to diverge long term from tempest - but please continue, did not mean to distract from the conversation at hand16:19
*** tonytan4ever has joined #openstack-meeting-316:19
RockygThe issue is that dev )QA dev) thinks that all of vendors, no matter what release they put out there or when, should meet all new test standrds16:19
Rockygno problem, docaedo ;-)  We like developers to know our pain and help solve it16:20
dwalleckWe could write tests specifically for API compat and require those, while still using the rest of Tempest without the need to go our own route16:20
VanLQuestion for this group: Is there anyone *here in defcore* that thinks we should have strict API checking *right now*?16:20
hogepodgeRockyg: well, if we assume tempest works at guideline release, we should branch it at guideline release then cherry pick bug fixes. Then for a given guideline we know that we won't be caught by changes16:20
VanLdwalleck: +116:20
hogepodgeVanL: In six months, yes.16:21
*** ddieterly[away] is now known as ddieterly16:21
Rockyghogepodge, ++  Like in the old days :-)16:21
dwalleckWith the added benefit that folks not totally API compliant would be able to use Tempest at all for functional testing16:21
VanLI see that there are different thoughts about its applicability later16:21
catherineDVanL: I believe in strict API testing for interop purpose and we should enforce or expose those who do not ... but does not have to fail them for trademark purpose16:21
RockygVanL, when it's in the code, and only for those releases that have it and going forward16:21
docaedocatherineD: +116:22
hogepodgemarkvoelker: in interest of time, do you have any suggestions on how we should proceed?16:22
catherineDRockyg: that is why we should not fail them for trademark purpose16:22
hogepodgewe're not going to reach consensus this week16:22
hogepodge(if ever ;-P )16:23
markvoelkerhogepodge: agreed.  So, a couple of things:16:23
VanLhogepodge: I can accept strict API checking when/iff there is an allowed extension mechanism that doesn't gum up interop.16:23
markvoelker1.) There are a lot of opinions being expressed here that I don't think have made it out to the bigger audience on the ML's yet, so I'd encourage you to chime in there.16:24
markvoelkerThis is an important topic for the entire ecosystem.16:24
*** kmartin has joined #openstack-meeting-316:24
RockygcatherineD, I agee we need to know.  I also think that we need to somehow get devs to understand that the change in contract going forward (strict checking) is a now and forward conract that can't be applied (but can be exposed) for artifacts that existed before the contract change16:24
*** oshidoshi1 has quit IRC16:24
gemamarkvoelker: ++16:24
Rockygmarkvoelker, ++16:25
*** moshele has left #openstack-meeting-316:25
markvoelker2.) hogepodge, I think we need to create formal proposal of some sort that folks can vote on and that lays out where changes would be made (in tempest, refstack, or elsewhere)16:25
VanLmarkvoelker: "folks can vote on" - which folks?16:25
catherineDRockyg: ++ ... that is the reason why we have the RefStack to collect data for statistical purpose eventually16:26
*** tonytan4ever has quit IRC16:26
markvoelkerVanL: DefCore needs to decide if we're going to flag tests or not, and if we're going to add additional separate capabilties in the future or not16:26
VanLThat is one important point: We listen to and take input from other groups, but they don't get a vote16:26
markvoelkerVanL: As always, I'm interested in hearing feedback from others.16:26
Rockygoh, and markvoelker, could you change you nick so I don' have to type 2/3 of your name before I get a unique match on IRC?)16:26
markvoelker3.) I imagine this is the sort of thing the Board is going to be interested in since we are ultimately a Board body.16:27
markvoelkerThere is a Board meeting coming up later this month, and I think we should put in an agenda item to raise awareness even if we don't have a clear plan of action yet.16:27
Rockyg++  and I think that is what hogepodge said in the original post.16:28
hogepodgemarkvoelker: for 2) I will write up a proposal, which will include some alternatives based on what happens in this group and upstream16:28
VanLmarkvoelker: I think that this is the sort of thing that should go in the defcore test spec that gema has been working on - we could propose that to the board and get guidance16:28
shamailmarkvoelker and hogepodge: does it make sense to hold off on the voting until after midcycle?  This topic seems perfect for discussion at the event.16:28
RockygVanL, ++16:28
VanLAnd that could be *defcore16:28
VanL's guidance16:28
shamailVanL: ++16:28
markvoelkershamail: I think we should get a proposal put together sooner rather than later.  When it lands is going to depend on the discussion.16:29
*** sarob has joined #openstack-meeting-316:30
RockygAlso, expext discussion in TC this week or next16:30
shamailSounds good, thanks.16:30
hogepodgeshamail: keep in mind that this is time sensitive, we have vendors looking to renew or get a new trademark now or soon16:30
*** numans has joined #openstack-meeting-316:30
hogepodgeshamail: too long may be too late, but we also can't rush it.16:30
catherineDhogepodge: how many tests are we talking about?16:30
hogepodgeshamail: basically, a whole lot of no fun16:31
hogepodgecatherineD: from dwalleck's patch, three16:31
hogepodgecatherineD: no, not tests, APIs16:31
hogepodgecatherineD: I don't know how many tests16:31
catherineDhogepodge: thx16:31
*** sarob has quit IRC16:31
hogepodgecatherineD: dwalleck and Rockyg would have better data than I do16:31
dwalleckhogepodge: I can give you some more stats if that would be helpful16:32
hogepodgedwalleck: yes please16:32
VanLRockyg: Could you take a look at dwalleck's patch - does that work for Huawei?16:32
Rockygplease.  I don't get stats from our team, just confused whining16:32
*** piet has quit IRC16:32
RockygOops.  did I say that in my IRC voice?16:32
*** sarob has joined #openstack-meeting-316:32
*** matrohon has quit IRC16:33
*** piet has joined #openstack-meeting-316:33
catherineDI would be interesting to know whether those vendors are in fact interop with others at the "core" level16:33
RockygI'll pass it by our guys and request a quick response.  Should be able to get it for tomorrow.16:33
shamailHeh :) I like the idea of having a proposal to review... The discussion could carry over if necessary to midcycle (maybe even a short-term versus long-term position discussion if we resolve this actual topic)16:33
Rockygdwalleck, is that patch everything my team might need?16:33
dwalleckRockyg: That depends on where your extra properties are. This squashes checking on servers, flavors, and quotas responses16:34
*** ihrachys has quit IRC16:34
hogepodgecatherineD: I'm working under the presumption that the additional properties would not impact any applications, and can be safely ignored. I wouldn't be advocating for this if I thought otherwise16:34
RockygcatherineD, my understanding is our team added the extra response to handle network stuff they neede that didn't exist in Neutron16:34
dwalleckYours are probably different, but if you send me a gist with what your responses look like, I might be able to point you in the right direction16:35
Rockygdwalleck, Thanks.  My guys are pretty good.  I should be able to get the list of non-pass from them, too.16:35
*** sarob has quit IRC16:35
hogepodgeRockyg: I'm also working under the assumption that these additional properties will be removed or integrated upstream16:35
VanLcatherineD: If you use the common rule (from other similar standards) to "Ignore what you don't understand," then, yes, interop works16:35
hogepodge(in future product releases)16:35
*** sarob has joined #openstack-meeting-316:36
hogepodgeCan we call time on this to hit the other topics? We ok with that?16:36
*** piet has quit IRC16:36
RockygThey know their stuff, just not community process,  and hogepodge so am I.  Move to next OpenStack release for them will solve lots of problems and reduce where they neede to do extra stuff.16:37
markvoelkerIt may perhaps be a good idea to prove that point out a bit...personally I haven't found a lot of commonly used toolkits that barf on extra attributes, but it may be worth putting some time into testing ones we know are widely used.16:37
*** piet has joined #openstack-meeting-316:37
markvoelker(the user survey has some data on popular sdk's and such)16:37
dwalleckmarkvoelker: That would actually be a very helpful thing we could point to16:37
*** marst has joined #openstack-meeting-316:37
Rockyg++ to more dat and to moving on16:38
markvoelkerOk, 20 minutes to go and we really need to hit a couple of the other agenda items today.16:38
*** davidsha has left #openstack-meeting-316:38
*** davidsha has quit IRC16:38
markvoelker#topic Midcycle planning16:39
*** openstack changes topic to "Midcycle planning (Meeting topic: defcore)"16:39
catherineDVanL: markvoelker: so the common rule (best practice) is for vendors to " ignore what you don't understand" for interop puprpose16:39
VanLcatherineD: Yes, although the real target of that advice is clients16:39
markvoelker#link Midcycle planning etherpad16:39
markvoelkerSo from the preliminary info we got there, it looks like the week of August 1 works well for most folks16:40
markvoelkerWe also have 4 volunteers to host.  2 in Silicon Valley, 1 in Texas, 1 in the UK.16:41
*** SridarK has quit IRC16:42
*** sdake has quit IRC16:42
markvoelkerWe need to firm this up, and the sooner the better.  I think the -2/-1/+1/+2 format we used for dates actually worked pretty well...should we do that for locations too?16:42
markvoelkerOr would folks prefer I send out a Doodle poll?  Or...?16:43
*** mbound has joined #openstack-meeting-316:43
RockygI'm not saying this, but I'm just saying, our guys haven't figured out sponsoring meetings yet, so it could take me some time to make it happen.  I'd like to go through the steps with them so they understand the requirements, especially planning and costs, but likely can't act quickly enough.16:43
markvoelkerRockyg: so, we may need to withdraw Huawei as a possible site then?16:43
hogepodgeif vmware is an option, the valley would be covered anyway16:44
markvoelkerhogepodge: True.  And I can confirm VMware is definitely an option.16:44
*** jlanoux has joined #openstack-meeting-316:44
VanLWe have a couple venues at our campus here, depending on how many people we have (size is not a problem, just different room sets fit different sizes)16:45
Rockygmarkvoelker, I'd say, it would be best to this round.  We made the gesture, now I have to get them to understand both the cost of doing it aand the cost of lost opportunity for not.16:45
markvoelkerRockyg: ok.  Thanks for the interest, and for clarifying.16:45
RockygYeah.  It's an education process.16:45
markvoelkerOk, with that in mind I'll send out mail this week asking folks to fill in -2/-1/+1/+2 on the pad and we'll finalize at next week's meeting.  Sound good?16:46
*** jobrs has quit IRC16:46
RockygThanks all for understanding.  Hopeuflly ready for either next cycle or next time valley is an option16:46
markvoelkerGreat.  Ok, there's also a topic list on the pad there, so let's try to make sure we get all prospective topics listed too16:47
RockygCan you leave us on, but grayed out or something?  I want them to see the process with us in it, but not winning.16:47
markvoelker(I'll add that to the note)16:47
*** bpokorny has joined #openstack-meeting-316:47
RockygActually, most of the folks here voting for something else would do it.16:47
gemaRockyg: so you want us to -1 you?16:47
*** bpokorny has quit IRC16:47
*** ddieterly is now known as ddieterly[away]16:47
RockygPlus VMware has a *much* nicer campus and better food.16:48
markvoelker#action markvoelker will send email to ML this week to finalize dates/places on the etherpad16:48
Rockyggema, yup.16:48
gemaRockyg: you got it :)16:48
*** bpokorny has joined #openstack-meeting-316:48
markvoelkerAnything else on midcycle planning we need to hit today?16:48
markvoelkerMoving on...16:49
markvoelker#topic Upcoming Board Meeting16:49
*** openstack changes topic to "Upcoming Board Meeting (Meeting topic: defcore)"16:49
markvoelkerThere's a BoD meeting at the end of the month.  I put a couple items in the pad that we may want to bring up.  Anything else?16:49
VanLThe spec16:50
*** jlanoux has quit IRC16:50
Rockyglooks good.16:51
markvoelkerVanL: noted.16:51
RockygUh, is there a report on how many and types of vendors that have passe, and which guidelines, etc?16:51
*** mickeys has joined #openstack-meeting-316:51
*** cbouch has quit IRC16:52
RockygIt would be great to start getting some numbers into the minutes16:52
markvoelkerRockyg: no, although that data is available in the marketplace and I think we've occasionally provided a rollup in the past.16:52
RockygI think we should schedule a numbers report to the for a specific time in our cycle16:53
Rockygto the boar.16:54
markvoelkerRockyg: reasonable.  Maybe part of the major issues report?16:54
RockygBut not part of this agenda, so future item16:54
*** mtanin___ has joined #openstack-meeting-316:54
Rockygmarkvoelker, ++16:54
markvoelkerOk, moving on if nothing further for the Board...16:54
markvoelker#topic Documentation generation update16:54
*** openstack changes topic to "Documentation generation update (Meeting topic: defcore)"16:54
markvoelkerhogepodge: take it away16:54
*** iyamahat has quit IRC16:55
catherineDRockyg: markvoelker:  When RefStack finishes vendor/product registation .. this data would be obtained  easily16:55
hogepodgeCan everyone look at the documentation updates? It's a work in progress, but I want to get those published to openstack docs16:55
*** mtanino has quit IRC16:55
hogepodgeThe first step is cleaning things up16:55
dwalleckcan do16:55
hogepodgeThe second is adding a post-gate job that publishes16:56
markvoelkercatherineD: duly noted16:56
hogepodgeI want to add the lexicon, clean things up, but that's a start16:56
markvoelkerhogepodge: thanks for this.  I'll take a look.16:56
hogepodgeplus, if I'm missing anything, please let me know16:56
*** yamahata has quit IRC16:56
markvoelker#action everyone please review
markvoelkerAnything else on this?  We're down to a couple of minutes16:57
Rockygdoing that now...16:57
catherineDhogepodge: now that we move schema to JSON format ... we seem like loosing the comments16:57
catherineDThe comments has been very helpful ... should we still keep the rst file for comments16:58
hogepodgecatherineD: I added an rst file, so we can annotate there16:58
hogepodgecatherineD: change log and imports the schema, we can do an unofficial mock up with comments too
*** woodster_ has quit IRC16:59
*** NobodyCam has quit IRC16:59
markvoelkerOk, I think we're out of time.  Thanks folks--and again, I'd love to see some of you chime in on the broader ML discussion.  See you soon!16:59
*** openstack changes topic to "OpenStack Meetings ||"17:00
openstackMeeting ended Wed Jun 15 17:00:04 2016 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
*** brunssen has quit IRC17:00
*** NobodyCam has joined #openstack-meeting-317:00
*** woodster_ has joined #openstack-meeting-317:00
*** carl_baldwin has quit IRC17:01
*** carl_baldwin has joined #openstack-meeting-317:01
*** mtanino has joined #openstack-meeting-317:01
*** catherineD has left #openstack-meeting-317:02
*** primeministerp has quit IRC17:02
*** mtanin___ has quit IRC17:03
*** shamail has quit IRC17:04
*** lpetrut has joined #openstack-meeting-317:05
*** lpetrut has quit IRC17:05
*** lpetrut has joined #openstack-meeting-317:06
*** dwalleck has left #openstack-meeting-317:06
*** Rockyg has quit IRC17:07
*** ddieterly[away] is now known as ddieterly17:08
*** ralonsoh has quit IRC17:10
*** coolsvap has quit IRC17:11
*** iyamahat has joined #openstack-meeting-317:12
*** numans has quit IRC17:13
*** bswartz has quit IRC17:13
*** rossella_s has quit IRC17:13
*** yamahata has joined #openstack-meeting-317:15
*** tonytan4ever has joined #openstack-meeting-317:17
*** pcaruana has joined #openstack-meeting-317:21
*** VW has quit IRC17:23
*** cjvolzka has left #openstack-meeting-317:25
*** Sukhdev has quit IRC17:26
*** piet has quit IRC17:29
*** tqtran has joined #openstack-meeting-317:31
*** ivar-lazzaro has joined #openstack-meeting-317:31
*** kzaitsev_mb has quit IRC17:35
*** tqtran has quit IRC17:35
*** kzaitsev_mb has joined #openstack-meeting-317:37
*** tellesnobrega_af is now known as tellesnobrega17:37
*** anilvenkata has joined #openstack-meeting-317:41
*** ddieterly is now known as ddieterly[away]17:41
*** kzaitsev_mb has quit IRC17:42
*** kzaitsev_mb has joined #openstack-meeting-317:42
*** mtanino has quit IRC17:48
*** galstrom is now known as galstrom_zzz17:50
*** kzaitsev_mb has quit IRC17:50
*** chandanc has joined #openstack-meeting-317:51
*** galstrom_zzz is now known as galstrom17:55
*** s3wong has joined #openstack-meeting-317:59
*** egallen has quit IRC18:00
*** pvaneck has joined #openstack-meeting-318:02
*** mtanino has joined #openstack-meeting-318:02
*** bswartz has joined #openstack-meeting-318:04
*** banix has quit IRC18:04
*** tonytan4ever has quit IRC18:04
*** mbound has quit IRC18:06
*** ccamacho is now known as ccamacho|out18:08
*** banix has joined #openstack-meeting-318:09
*** egallen has joined #openstack-meeting-318:10
*** pvaneck has quit IRC18:10
*** ajmiller_ is now known as ajmiller18:11
*** tqtran has joined #openstack-meeting-318:13
*** oshidoshi has joined #openstack-meeting-318:15
*** VW has joined #openstack-meeting-318:15
*** tonytan4ever has joined #openstack-meeting-318:16
*** vhoward has quit IRC18:19
*** tonytan4ever has quit IRC18:19
*** vhoward has joined #openstack-meeting-318:19
*** sarob_ has joined #openstack-meeting-318:20
*** sarob has quit IRC18:23
*** oshidoshi has quit IRC18:25
*** abalutoiu has quit IRC18:26
*** sambetts is now known as sambetts|afk18:32
*** sarob_ has quit IRC18:34
*** oshidoshi has joined #openstack-meeting-318:34
*** sdague has quit IRC18:34
*** songole has joined #openstack-meeting-318:35
*** songole has quit IRC18:35
*** pt_15 has quit IRC18:36
*** aimeeu has quit IRC18:39
*** toddjohn has joined #openstack-meeting-318:41
*** sdague has joined #openstack-meeting-318:41
*** aimeeu has joined #openstack-meeting-318:43
*** salv-orlando has quit IRC18:43
*** ddieterly[away] has quit IRC18:43
*** ddieterly has joined #openstack-meeting-318:44
*** salv-orlando has joined #openstack-meeting-318:44
*** jed56 has quit IRC18:45
*** ihrachys has joined #openstack-meeting-318:45
*** toddjohn has quit IRC18:46
*** abalutoiu has joined #openstack-meeting-318:48
*** dimtruck is now known as zz_dimtruck18:51
*** sarob has joined #openstack-meeting-318:53
*** salv-orl_ has joined #openstack-meeting-318:55
*** ivar-lazzaro has quit IRC18:56
*** salv-orlando has quit IRC18:58
*** sarob has quit IRC19:01
*** lpetrut has quit IRC19:02
*** Sukhdev has joined #openstack-meeting-319:02
*** piet has joined #openstack-meeting-319:05
*** sarob has joined #openstack-meeting-319:05
*** mbound has joined #openstack-meeting-319:06
*** tonytan4ever has joined #openstack-meeting-319:09
*** pvaneck has joined #openstack-meeting-319:10
*** sarob has quit IRC19:10
*** mbound has quit IRC19:11
*** zz_dimtruck is now known as dimtruck19:12
*** sarob has joined #openstack-meeting-319:12
*** ihrachys has quit IRC19:14
*** dimtruck is now known as zz_dimtruck19:14
*** tonytan4ever has quit IRC19:14
*** dtardivel has quit IRC19:17
*** sarob has quit IRC19:18
*** oshidoshi has quit IRC19:20
*** chandanc has quit IRC19:21
*** piet has quit IRC19:25
*** piet has joined #openstack-meeting-319:26
*** lpetrut has joined #openstack-meeting-319:30
*** ddieterly has quit IRC19:31
*** piet has quit IRC19:33
*** sdake has joined #openstack-meeting-319:36
*** sarob has joined #openstack-meeting-319:37
*** ALUVial has joined #openstack-meeting-319:37
*** sdake_ has joined #openstack-meeting-319:40
*** sarob has quit IRC19:41
*** ALUVial has quit IRC19:42
*** sdake has quit IRC19:42
*** ociuhandu has quit IRC19:44
*** salv-orl_ has quit IRC19:45
*** salv-orlando has joined #openstack-meeting-319:45
*** r1chardj0n3s has joined #openstack-meeting-319:55
*** ivar-lazzaro has joined #openstack-meeting-319:56
*** hurgleburgler has joined #openstack-meeting-319:58
*** tsufiev has joined #openstack-meeting-320:00
*** krotscheck_dcm is now known as krotscheck20:00
*** ihrachys has joined #openstack-meeting-320:00
*** tyr__ has joined #openstack-meeting-320:00
david-lyle#startmeeting HorizonDrivers20:00
openstackMeeting started Wed Jun 15 20:00:48 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at
hurgleburgler( ಠ‿ಠ)┘20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: HorizonDrivers)"20:00
openstackThe meeting name has been set to 'horizondrivers'20:00
*** TravT has joined #openstack-meeting-320:00
david-lyleRob is off holidaying, so I'm here for your entertainment20:01
*** ivar-lazzaro has quit IRC20:01
*** galstrom is now known as galstrom_zzz20:01
david-lyleThe agenda is not set, and the morning Horizon meeting was cancelled20:01
david-lyleCouple of reminders20:02
david-lyleThe midcycle is coming up quickly20:02
*** Sukhdev has quit IRC20:02
*** sarob has joined #openstack-meeting-320:02
david-lyleplease register if you plan to attend20:03
david-lylenewer users of the wiki are not able to get accounts to edit20:03
TravTi'm surprised clu isn't on there.20:03
*** VW_ has joined #openstack-meeting-320:03
david-lyleso if you want to register but can't, please read the instructions on the page for alternative methods20:04
*** flwang1 has quit IRC20:04
david-lylethe etherpad for topics is linked from there as well20:04
david-lyleTravT, that's clu_ to you20:04
*** VW__ has joined #openstack-meeting-320:05
david-lyleNot sure of other general items other than npm_run_test continues to plague us20:05
*** ihrachys_ has joined #openstack-meeting-320:06
*** zz_dimtruck is now known as dimtruck20:06
*** VW has quit IRC20:06
david-lyleThere have not been many new blueprints proposed, does anyone have one they want/need reviewed?20:06
TravTi do have a question20:07
*** sdake_ has quit IRC20:07
*** sarob has quit IRC20:07
* david-lyle will fake an answer20:07
TravTwhere are we on library upgrades and all the xstatic fun?20:07
*** sdake has joined #openstack-meeting-320:07
david-lyleour gate is now all separate from integrated tempest20:07
*** VW_ has quit IRC20:08
david-lyleand we're relying on upper-constraints, so are we ready to roll r1chardj0n3s ?20:08
*** galstrom_zzz is now known as galstrom20:08
r1chardj0n3sI need to review where we're up to in the "plan" and see what the next step is20:09
*** ihrachys has quit IRC20:09
david-lyleI think we're at the break things part20:09
david-lylewait, that's where we're always at20:09
r1chardj0n3sI was about to give a longer answer but I think david-lyle summarises well ;-)20:09
david-lylewell, it's easy to find20:09
*** VW__ has quit IRC20:09
*** egallen has quit IRC20:09
r1chardj0n3syeah, we should be able to attempt an automated release20:09
hurgleburglerhow exciting ]o/20:09
hurgleburgler\o/ too20:10
r1chardj0n3sI will work with my infra / releases folks to try to make that happen20:10
TravTokay, just was thinking that we'd want to have library upgrades all done before newton 320:10
david-lyleyes, sooner is better20:10
*** mfedosin has quit IRC20:10
*** sarob has joined #openstack-meeting-320:10
r1chardj0n3sthat's now #1 on my horizon priorities20:10
david-lylethe tempest part was ready a couple of weeks ago, so I'm not sure what we're stuck on20:10
r1chardj0n3sI think we're stuck on me20:11
david-lylemaybe rob's vacationing brain knows20:11
*** sdake_ has joined #openstack-meeting-320:11
r1chardj0n3sI got distracted after the tempest change went through, sorry.20:11
david-lyleno worries20:11
david-lyleso library soup is on the menu for the next few weeks20:12
tsufievdo we plan to roll angular 1.4 in newton?20:12
*** VW has joined #openstack-meeting-320:12
tsufievjust curious20:12
TravTtsufiev, yes20:12
david-lyleI'm going to be that guy20:12
*** sdake has quit IRC20:12
tsufievnice :)20:12
TravTrobcresswell already did some work on that20:12
david-lylewe need to make sure that the supported distros are going to line up20:13
*** VW has quit IRC20:13
david-lyleor we deliverable unrunnable code20:13
david-lyle16.04 should have shiny new versions20:13
*** VW has joined #openstack-meeting-320:13
TravTand david-lyle's scripts nixed his review fixing a few things20:14
david-lylebut we should pull mrunge in at some point to consult20:14
mrungesorry, in a meeting right now20:14
david-lylemrunge, we'll need you another day, just reminding people to talk to you about library versions20:15
david-lylemrunge, go about your business20:15
*** sarob has quit IRC20:15
david-lyleTravT, I aim to nix things20:16
*** matrohon has joined #openstack-meeting-320:16
david-lyleI started going through the abandons of blocked, but figure people would undo those20:16
r1chardj0n3sso what's the version of red hat we should be checking for our library versions20:16
*** ihrachys_ has quit IRC20:16
david-lyler1chardj0n3s, I honestly don't know any more20:16
david-lylewe should just consult with matthias another time20:17
r1chardj0n3sI guess I'll just try to figure out what the latest release is ;-)20:17
r1chardj0n3syeah maybe20:17
*** vhoward has quit IRC20:17
david-lyleany other topics?20:19
david-lyleI can always dig into the stale bp list if people are wanting20:21
* tsufiev again reminds everybody to look into dsvm-integration job failure videos20:21
TravTlink tufiev?20:21
david-lylenow there's a fun date night20:21
tsufievit's fun and very educating20:21
david-lyleTravT, they are part of the review logs20:22
david-lyleso depends on the failed review20:22
tsufievTravT, inside test_report dir for every failed dsvm job20:22
david-lyles/review/job failure/20:22
TravTokay, cool. thanks for that. i saw some chatter on that, but didn't digest it20:22
tsufievso far I've managed to see that most of failures are caused by dropdowns somehow not showing up when clicked20:23
hurgleburgleruh oh20:23
david-lylebecause they're themed?!?!?!20:23
*** galstrom is now known as galstrom_zzz20:24
*** toddjohn has joined #openstack-meeting-320:24
hurgleburgler*runs away* ε=┌( >_<)┘20:24
*** MeganR has quit IRC20:24
tsufievmy primary 'suspect' is that some delayed JS initialization is done on page at the same moment when test clicks the dropdown20:24
tsufievand it interferes with showing the dropdown content20:24
david-lylefixes everything20:24
TravTi usually prefer nap(15)20:25
tsufievdavid-lyle, that's the EVIL way20:25
tsufievwe're Jedi, not the Sith20:25
tsufievalthough there only ~2 people with integration tests knowledge, which aligns with Sith lore :/20:26
TravTtsufiev, don't resist the power of the dark side20:26
* tsufiev hums Imperial March20:27
*** sdake_ has quit IRC20:27
david-lyleother fun and excitement? or should we let tsufiev sleep and r1chardj0n3s wake up?20:28
tsufievany ideas why npm-run-test still bothering us, by the way?20:28
r1chardj0n3sdon't wanna20:28
r1chardj0n3sI thought we had an npm mirror now20:28
r1chardj0n3sbut we're still seeing bizarro network issues in install part of tests20:29
tsufievand 40 mins timeouts as well20:29
r1chardj0n3syeah, like the test runner just decides to not exit20:29
david-lylekrotscheck, around?20:29
krotscheckOnly if you're willing to fill out a Turing-test survey afterwards :)20:30
david-lylenpm-run-test question20:30
*** dimtruck is now known as zz_dimtruck20:30
* krotscheck reads scrollback20:30
david-lylewhy does it not work? explained to melike I'm a horizon developer20:30
krotscheck"I don't know"20:31
david-lyleI already had that answer on my own :)20:31
krotscheckWe've observed it hanging at the end of both test runs, and the only thing that happens there is the generation of the coverage report.20:31
tsufievshould we disable coverage reports temporarily?20:31
krotscheckOf course, there's a lot of things happening during that, including (I believe) releasing the karma ports.20:32
krotscheckReleasing the browsers, etc.20:32
krotscheckOur original hypothesis whas that the system's # of open files is a problem.20:32
krotscheckBut we landed that patch, and it didn't do anything.20:32
krotscheck(The reason we came up with that hypothesis is because it was stuck on popen_wait20:33
david-lylewhat can we do to help that won't get in your way?20:34
*** matrohon has quit IRC20:34
krotscheckdavid-lyle: Well, I let matt-borland know monday that I can't really continue investigating it, as I've got 2 weeks to go before a 2 week vacation, and all this App Eco WG and JavaScript SDK work is sucking down my time.20:35
krotscheckdavid-lyle: So, having someone take over would be nice.20:35
david-lyleok, so we won't step on your toes flailing at it for a bit20:35
krotscheckThis post will go a long way towards getting a test environment set up:
krotscheckWhich is what I used to simulate the issue, but there's the unfortunate bug that vagrant doesn't play well with xenial yet.20:36
krotscheckNo you wont.20:36
david-lyleok, thanks for your efforts and the link20:37
*** julim has quit IRC20:39
david-lyleanyone else, or should we wrap up?20:39
*** FallenPegasus has joined #openstack-meeting-320:39
*** FallenPegasus has quit IRC20:39
david-lylesounds like we're done. Thanks everyone.20:40
*** openstack changes topic to "OpenStack Meetings ||"20:40
*** TravT has left #openstack-meeting-320:40
openstackMeeting ended Wed Jun 15 20:40:41 2016 UTC.  Information about MeetBot at . (v 0.1.4)20:40
openstackMinutes (text):
*** hurgleburgler has left #openstack-meeting-320:41
*** r1chardj0n3s has left #openstack-meeting-320:41
*** tsufiev has left #openstack-meeting-320:42
*** mtanino has quit IRC20:43
*** kzaitsev_mb has joined #openstack-meeting-320:45
*** zz_dimtruck is now known as dimtruck20:50
*** ociuhandu has joined #openstack-meeting-320:52
*** bpokorny has quit IRC20:57
*** ivar-lazzaro has joined #openstack-meeting-320:57
*** ivar-lazzaro has quit IRC21:02
*** ivar-lazzaro has joined #openstack-meeting-321:03
*** anilvenkata has quit IRC21:03
*** toddjohn has quit IRC21:03
*** marst has quit IRC21:04
*** toddjohn has joined #openstack-meeting-321:04
*** ivar-lazzaro has quit IRC21:05
*** ociuhandu has quit IRC21:06
*** ociuhandu_ has joined #openstack-meeting-321:06
*** ociuhandu_ is now known as ociuhandu21:06
*** egallen has joined #openstack-meeting-321:06
*** FallenPegasus has joined #openstack-meeting-321:07
*** ivar-lazzaro has joined #openstack-meeting-321:08
*** toddjohn has quit IRC21:09
*** marst has joined #openstack-meeting-321:09
*** ewang12 has quit IRC21:11
*** rtheis has quit IRC21:12
*** bpokorny has joined #openstack-meeting-321:14
*** mickeys has quit IRC21:15
*** ivar-lazzaro has quit IRC21:16
*** ivar-lazzaro has joined #openstack-meeting-321:16
*** rockyg has joined #openstack-meeting-321:19
*** Sukhdev has joined #openstack-meeting-321:22
*** sarob has joined #openstack-meeting-321:26
*** lblanchard has quit IRC21:28
*** bpokorny has quit IRC21:28
*** bpokorny has joined #openstack-meeting-321:29
*** banix has quit IRC21:29
*** bpokorny_ has joined #openstack-meeting-321:31
*** sarob has quit IRC21:32
*** Sukhdev has quit IRC21:32
*** lpetrut has quit IRC21:32
*** ccamacho|out has quit IRC21:33
*** Sukhdev has joined #openstack-meeting-321:33
*** bpokorny has quit IRC21:34
*** VW has quit IRC21:35
*** flwang1 has joined #openstack-meeting-321:36
*** rossella_s has joined #openstack-meeting-321:36
*** Sukhdev has quit IRC21:36
*** VW has joined #openstack-meeting-321:37
*** bpokorny_ has quit IRC21:39
*** mickeys has joined #openstack-meeting-321:39
*** bpokorny has joined #openstack-meeting-321:40
*** bauzas has quit IRC21:47
*** bauzas has joined #openstack-meeting-321:51
*** egallen has quit IRC21:58
*** yamahata has quit IRC22:04
*** rhochmuth has quit IRC22:06
*** Sukhdev has joined #openstack-meeting-322:09
*** Sukhdev has quit IRC22:09
*** Sukhdev has joined #openstack-meeting-322:10
*** mbound has joined #openstack-meeting-322:10
*** Sukhdev has quit IRC22:15
*** shwetaap has quit IRC22:22
*** marst has quit IRC22:23
*** VW_ has joined #openstack-meeting-322:23
*** salv-orlando has quit IRC22:25
*** VW has quit IRC22:26
*** salv-orlando has joined #openstack-meeting-322:26
*** VW_ has quit IRC22:27
*** yamahata has joined #openstack-meeting-322:27
*** VW has joined #openstack-meeting-322:40
*** VW has quit IRC22:41
*** VW has joined #openstack-meeting-322:41
*** Sukhdev has joined #openstack-meeting-322:42
*** toddjohn has joined #openstack-meeting-322:43
*** ivar-lazzaro has quit IRC22:43
*** rossella_s has quit IRC22:44
*** Sukhdev has quit IRC22:44
*** banix has joined #openstack-meeting-322:44
*** Sukhdev has joined #openstack-meeting-322:46
*** toddjohn has quit IRC22:47
*** FallenPegasus has quit IRC22:49
*** rockyg has quit IRC22:52
*** dimtruck is now known as zz_dimtruck22:53
*** Sukhdev has quit IRC22:53
*** ivar-lazzaro has joined #openstack-meeting-322:59
*** mickeys has quit IRC23:00
*** ivar-lazzaro has quit IRC23:00

Generated by 2.14.0 by Marius Gedminas - find it at!