Wednesday, 2016-10-05

*** ivar-laz_ has quit IRC00:11
*** ivar-lazzaro has joined #openstack-meeting-300:13
*** sdake_ has quit IRC00:16
*** galstrom is now known as galstrom_zzz00:22
*** mtanino has quit IRC00:32
*** kzaitsev_mb has quit IRC00:34
*** ivar-lazzaro has quit IRC00:35
*** hj-hpe has quit IRC00:37
*** ivar-lazzaro has joined #openstack-meeting-300:43
*** ivar-lazzaro has quit IRC00:44
*** hoangcx has joined #openstack-meeting-300:48
*** ivar-lazzaro has joined #openstack-meeting-300:48
*** Poornima has quit IRC00:49
*** ivar-lazzaro has quit IRC00:50
*** david-lyle has quit IRC00:52
*** sdake has joined #openstack-meeting-300:53
*** tqtran has quit IRC00:56
*** spzala has joined #openstack-meeting-300:59
*** gouthamr has quit IRC00:59
*** margaret has quit IRC01:00
*** Poornima has joined #openstack-meeting-301:02
*** tonytan4ever has quit IRC01:03
*** spzala has quit IRC01:03
*** spzala has joined #openstack-meeting-301:03
*** Sukhdev has quit IRC01:04
*** xgerman has quit IRC01:04
*** abalutoiu has quit IRC01:05
*** toddjohn has quit IRC01:06
*** toddjohn has joined #openstack-meeting-301:06
*** baoli has quit IRC01:09
*** toddjohn has quit IRC01:11
*** Poornima has quit IRC01:11
*** pvaneck has quit IRC01:12
*** margaret has joined #openstack-meeting-301:15
*** xgerman has joined #openstack-meeting-301:17
*** baoli has joined #openstack-meeting-301:20
*** tuanluong has joined #openstack-meeting-301:21
*** baoli has quit IRC01:27
*** woodster_ has quit IRC01:50
*** tellesnobrega has quit IRC01:59
*** tellesnobrega has joined #openstack-meeting-302:01
*** mtanino has joined #openstack-meeting-302:01
*** sdake has quit IRC02:18
*** amotoki has joined #openstack-meeting-302:19
*** mickeys has quit IRC02:20
*** mickeys has joined #openstack-meeting-302:20
*** sdake has joined #openstack-meeting-302:20
*** amotoki has quit IRC02:31
*** amotoki has joined #openstack-meeting-302:43
*** haleyb_ has quit IRC02:44
*** yamahata has quit IRC02:45
*** iyamahat has quit IRC02:45
*** amotoki_ has joined #openstack-meeting-303:04
*** amotoki has quit IRC03:07
*** toddjohn has joined #openstack-meeting-303:08
*** Sukhdev has joined #openstack-meeting-303:09
*** Sukhdev has quit IRC03:13
*** toddjohn has quit IRC03:13
*** spzala has quit IRC03:20
*** VW has joined #openstack-meeting-303:26
*** amotoki has joined #openstack-meeting-303:35
*** amotoki has quit IRC03:36
*** amotoki_ has quit IRC03:36
*** tongli has quit IRC03:38
*** mickeys has quit IRC03:39
*** sdake has quit IRC03:43
*** sdake has joined #openstack-meeting-303:43
*** haleyb_ has joined #openstack-meeting-303:44
*** markvoelker has quit IRC03:48
*** vishwanathj has quit IRC03:50
*** SarathMekala has joined #openstack-meeting-303:50
*** tqtran has joined #openstack-meeting-303:55
*** chandanc_ has joined #openstack-meeting-303:56
*** tqtran has quit IRC03:59
njohnston#startmeeting fwaas04:00
openstackMeeting started Wed Oct  5 04:00:15 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** SridarK has joined #openstack-meeting-304:00
*** openstack changes topic to " (Meeting topic: fwaas)"04:00
openstackThe meeting name has been set to 'fwaas'04:00
SridarKHi All04:00
njohnstonHello everybody04:00
chandanc_Hello All04:00
SarathMekalaHi all O/04:00
SridarKshall we get started04:01
njohnstonby all means :-)04:01
SridarK#topic FWaaS v204:01
SridarKnjohnston: can u pls add me to chair04:02
njohnstonoops forgot04:02
njohnston#chair SridarK04:02
openstackCurrent chairs: SridarK njohnston04:02
SridarKno worries thx04:02
njohnston#chair yushiro xgerman04:02
openstackWarning: Nick not in channel: yushiro04:02
openstackCurrent chairs: SridarK njohnston xgerman yushiro04:02
SridarK#topic FWaaS v204:02
*** openstack changes topic to "FWaaS v2 (Meeting topic: fwaas)"04:02
SridarKI think yushiro is out today04:03
SridarKand we are done with the CLI discussion, now it is just a matter of getting the review moving when he is back04:04
SridarKso lets move on to L204:04
SridarKpadkrish may join in late04:04
SridarKbut he has been working the L2 Agent side of things and has good progress on that04:05
SridarKso lets move to the driver04:05
SridarKchandanc_: SarathMekala: pls go ahead all yours04:05
chandanc_We have been working on the UT for conntrack and l2 driver04:05
chandanc_the Conntrack still has 2 more UT breaks but the ideas provided by Nate and Margaret helped04:06
SridarKgreat04:06
njohnstonYou both were working hard - I saw a blizzard of patchsets come in - nice work!04:06
chandanc_On the Iptables driver side we had some 100 + UT breakage04:06
SridarKouch04:06
chandanc_we could bring it down to 307 now04:06
*** amotoki has joined #openstack-meeting-304:06
chandanc_37 *04:06
chandanc_sorry04:06
SridarK:-)04:07
chandanc_should be able to close the iptable UTs quite soon04:07
chandanc_but the contrack one seems a hardnut04:07
*** spzala has joined #openstack-meeting-304:07
SridarKexcellent - then u can push for core attention on the iptables patch04:07
*** spzala has quit IRC04:07
chandanc_even with the threading lock we are not able to fix the last 2 UTs04:08
chandanc_yes I think now I will ask for Core attention04:08
njohnstonI can take a look at those 2 last UTs; I am humble but perhaps I can help.04:08
*** toddjohn has joined #openstack-meeting-304:08
chandanc_sure njohnston04:09
chandanc_I can use some help04:09
*** SridarK_ has joined #openstack-meeting-304:09
chandanc_I will be pinging Kevin this week04:10
SridarK_sorry got bounced, chandanc_: if think it will help we can all get together in a mtg tomorrow to do some debugging04:10
chandanc_sure that will be helpful04:11
SarathMekala+104:11
SridarK_chandanc_: pls send out an email to all of us, to coordinate on a time04:11
*** SridarK has quit IRC04:12
njohnston+104:12
chandanc_I will send a mail to the team with the meeting time04:12
SridarK_we can get some context as well on this to think thru04:12
chandanc_BTW what will be a good time for you guys04:12
SridarK_great thx chandanc_:04:12
chandanc_yes04:12
SridarK_I have a mtg at 9am to 9:30am Pacific time - after that i am fine04:13
njohnstonchandan: for me sometime between 1300 UTC and 2100 UTC04:14
njohnstonis optimal04:14
*** toddjohn has quit IRC04:14
SarathMekala1400 UTC then04:15
SridarK_sure i can make that work too04:15
SridarK_a bit early for me but should be ok04:15
njohnstonsounds good04:15
SridarK_ok lets carry that fwd to the mtg, meanwhile just send out an email with some context and i can set up a conf call04:16
chandanc_Sure04:16
chandanc_Will send a mail04:16
SridarK_we can get to the fwaas piece after the neutron pieces are getting some review traction04:17
SarathMekalameeting for today right?04:17
SridarK_this is definitely not the long pole04:17
SridarK_SarathMekala: yes so that would be 7:30pm for u guys (i think)04:17
chandanc_yes04:18
njohnstonwe appreciate you staying late04:18
chandanc_7:30 is not late :)04:18
njohnstonmy wife would have strong opinions if I stayed until 7:30 ;-)04:19
*** haleyb_ has quit IRC04:19
SridarK_ok other things on the L2 driver side of things that u would like to discuss ?04:19
chandanc_:)04:19
SridarK_:-)04:19
SarathMekala:)04:19
SarathMekalaSridarK_, we are ok till 9 pm if its clashing with your meeting04:19
SridarK_no this is fine04:19
*** amotoki_ has joined #openstack-meeting-304:19
*** VW has quit IRC04:20
SridarK_i have to convince someone to take the dog out - thats all :-)04:20
SridarK_good lets move on, i will send out conf call details04:20
SarathMekala:) my dog takes me out around this time04:20
SridarK_:-)04:20
njohnston:-)04:20
SridarK_other things on v2 - i started looking at tempest, but had to take care of some other things at work so been slow04:21
njohnstonok, sounds like we can move on04:21
SridarK_will get back on track on this - so we can get some basic coverage in04:21
njohnstonecellent!  The tempest change looks like it just needs neutron infra +1 and it will merge04:22
njohnston#link https://review.openstack.org/#/c/371749/ tempest change04:22
SridarK_njohnston: great, so we can just hook our v2 tests to this04:23
SridarK_once i get some done04:23
*** amotoki has quit IRC04:23
njohnstonyes, for every change we will get v1 and v2 test results - both non-voting, but still we'll be able to make sure our changes are working on both sides04:23
SridarK_njohnston: great04:24
SridarK_ok thats about all i had on v204:24
SridarK_njohnston: anything else to cover ?04:24
*** sdake has quit IRC04:25
njohnstonnothing on v204:25
*** anilvenkata has joined #openstack-meeting-304:25
SridarK_ok we can move on then04:25
SridarK_njohnston: i think my alias got morphed, so can u pls drive04:25
njohnstonsure thing04:25
SridarK_this was the main set of things i wanted to discuss mainly04:26
njohnstonAll right, I have a few other items04:26
njohnston#topic Ocata04:26
SridarK_njohnston: pls go ahead04:26
*** openstack changes topic to "Ocata (Meeting topic: fwaas)"04:26
njohnstonI don't know how many people we are going to have in Barcelona04:26
njohnstonSo I am unsure if we should talk about Ocata priorities in one of these meetings, or in person at the summit04:27
chandanc_Sorry we will not be able to make it this time :(04:27
njohnston#link https://etherpad.openstack.org/p/fwaas-ocata fwaas ocata etherpad04:27
njohnstonchandanc_: I will regret not seeing you04:27
SridarK_chandanc_: sigh - i was hoping both of u will make it04:28
hoangcxnjohnston, I will be at the summit and looking forward to discuss in person as last Austin summit.04:28
chandanc_Ya, but we seem to have budget constrain :(04:28
SridarK_hoangcx: ok will yushiro be there too ?04:28
SridarK_chandanc_: yes i understand04:28
hoangcxSridarK_, Yes. He will be there too04:28
SridarK_ok04:29
njohnstonlooking forward to seeing you again, hoangcx!04:29
njohnstonI have already been pursuing one of the items on the Ocata list, which is an integration with Congress.  I think it is very interesting, and I'll be chatting with the Congress people in one of their work sessions.04:29
njohnston#link https://blueprints.launchpad.net/congress/+spec/congress-fwaas Congress integration with FWaaS04:29
SridarK_njohnston: cool04:30
njohnstonIt's quite exciting, I have been emailing with Tim Hinrichs on the Congress side04:31
SridarK_njohnston: u can give us an outline either at the summit or we can discuss before04:32
njohnstonSridarK_: definitely04:32
SridarK_since all folks will not make it, perhaps we can have a sync mtg with the team to focus on priorities and some level of input for planning and priorities folks would like to see addressed in Ocata04:33
njohnstonI think that would be very good04:33
SridarK_we can do this in this forum or also as separate meeting (even as a conf call if folks so desire)04:34
chandanc_+104:34
njohnstonAnd to prep for that, make sure your ideas and info are in the etherpad04:34
SarathMekala+104:34
SridarK_+104:34
SridarK_ok we can plan to discuss this next week either here or towards the end of the week if we need more time04:35
njohnstonsounds good04:35
njohnston#topic Other changes04:36
*** openstack changes topic to "Other changes (Meeting topic: fwaas)"04:36
njohnstonThere are a few changes flying about that I wanted to mention04:36
njohnstonA fix to the periodic job that makes sure fwaas works with the master branch of neutron-lib (stadium prerequisite): https://review.openstack.org/#/c/380648/04:36
njohnstonYushiro put in a bug fix for an argument issue: https://review.openstack.org/#/c/373964/04:37
njohnstonthose two just need reviews04:37
njohnstonand if people are interested in looking at documentation04:37
SarathMekalaI will review them04:37
*** ivar-lazzaro has joined #openstack-meeting-304:37
njohnstonplease feel free to contribute to an embryonic install guide https://review.openstack.org/37570604:38
SridarK_on the reviews04:38
njohnstonand/or migration of the fwaas docs from the admin guide to the networking guide, per Sam-I-Am's directions https://review.openstack.org/36633104:38
njohnstonI haven't had much time for the documentation, but I think the things that have been on my plate will start to get completed soon04:39
njohnstonDoes anyone else have changes in-flight that we haven't talked about, that they'd like reviews on?04:40
*** annp has joined #openstack-meeting-304:40
*** salv-orlando has joined #openstack-meeting-304:41
njohnston#topic Bugs04:42
*** openstack changes topic to "Bugs (Meeting topic: fwaas)"04:42
njohnstonWe haven't talked about bugs much in this meeting04:42
njohnstonBut to draw attention to the list:04:42
njohnston#link http://tinyurl.com/fwaas-bugs04:42
njohnstonone of those is from late September, bug 162246004:43
openstackbug 1622460 in neutron "neutron-server report 'FirewallNotFound' when delete firewall under l3_ha mode" [Low,Confirmed] https://launchpad.net/bugs/162246004:43
njohnstonBut we have bugs going back as far back as 2013 (gasp)04:44
SridarK_many of these may just require clean up04:44
njohnstonSo I am hoping that we can take a periodic look at bugs, especially as adoption increases we will start seeing a greater flow04:44
*** coolsvap has joined #openstack-meeting-304:45
SridarK_+104:45
njohnstonand nuke bugs that date to a havana/icehouse timeframe04:45
SarathMekalaI have one observation to discuss on the bug area04:45
njohnstonPlease go ahead, SarathMekala04:45
SarathMekalawhen VPNaaS is installed using devstack it fails to start as it cant locate /etc/neutron/fwaas_driver.ini04:46
SridarK_Hmm04:46
njohnstonWhy is VPNaaS looking for the FWaaS config file?04:46
SarathMekalaI took a cursory glance at their installation script and there seems to be some linkage to FwaaS04:47
njohnstonI think they tried to create some hokey workaround so that FWaaS and VPNaaS could coexist04:47
SarathMekala1 min will share the paste link04:47
SridarK_SarathMekala: the linkage is again embedded in the inheritance hierachy issues on L3Agent04:47
SarathMekalahttp://paste.openstack.org/show/584360/04:47
SridarK_VPN inherits from L3Agent class04:47
*** markvoelker has joined #openstack-meeting-304:49
njohnstonwas VPN's inheritance snipped the same way FWaaS's was?  I realize our inheritance was more sordid, with L3NATAgent inheriting from firewall_l3_agent.FWaaSL3AgentRpcCallback04:49
njohnstonBut I would have thought they would have been given the shove a bit04:49
SridarK_now how the ini file comes into play needs some thought - i dont recall why we see this04:49
SridarK_i dont believe VPN made any fixes04:50
SridarK_earlier, if VPN was configured - L3Agent would run as VPNAgent04:50
njohnstonhttps://github.com/openstack/neutron-vpnaas/blob/e9d8afa2d7c778b4c4ba7325b989953726700b0c/devstack/settings#L30-L3204:50
*** sdake has joined #openstack-meeting-304:51
SridarK_yes exactly if FWaaS is also enabled04:51
*** armax has quit IRC04:51
njohnstonexactly https://github.com/openstack/neutron-vpnaas/blob/e9d8afa2d7c778b4c4ba7325b989953726700b0c/devstack/plugin.sh#L57-L5904:51
SridarK_then that too runs in the context of VPNagent04:51
*** HenryG has quit IRC04:51
njohnstonI think that we can propose to them that these bits be excised04:52
*** HenryG has joined #openstack-meeting-304:52
SridarK_i think if i heard correctly, vpn did not want to make any changes04:52
SridarK_i will ask Paul M04:52
*** pgadiya has joined #openstack-meeting-304:53
njohnston#topic Open Discussion04:53
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:53
SridarK_SarathMekala: were u interested to get VPN up ?04:53
njohnstonAnything else, anyone?04:53
*** ivar-lazzaro has quit IRC04:54
SarathMekalaYes Sridar04:54
*** markvoelker has quit IRC04:54
SarathMekalaon the Horizon UI front I will start working from next week04:54
SridarK_SarathMekala: ok on VPN - there might not much traction in the community - i will ask and let u know04:55
SridarK_one of the cores works with me04:55
*** mickeys has joined #openstack-meeting-304:55
SarathMekalasure SridarK_.. thanks04:56
SridarK_great on the horizon - it will be nice to get that in place, close on the heels of CLI04:56
njohnstonAs far as VPNaaS, I threw up a quick patch to remove the FWaaS-specific bits from their devstack plugin04:56
njohnston#link https://review.openstack.org/382141 Disentangle VPNaaS from FWaaS04:56
njohnstonSo we can see how that is received04:56
SridarK_sounds good04:57
SarathMekalanjohnston, you amaze me :O04:57
SridarK_+104:57
* njohnston blushes04:57
njohnstonOK, I think that sounds like everything.  Last call?04:57
SridarK_i am good04:58
SarathMekalanothing on my side04:58
njohnstonexcellent.  Thank you so much everyone.04:58
SridarK_Thanks all04:58
njohnston#endmeeting04:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"04:58
openstackMeeting ended Wed Oct  5 04:58:29 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-10-05-04.00.html04:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-10-05-04.00.txt04:58
openstackLog:            http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-10-05-04.00.log.html04:58
SridarK_Bye everyone04:58
SarathMekalabye all O/04:58
*** ivar-lazzaro has joined #openstack-meeting-304:59
njohnstonbye!04:59
*** amotoki_ has quit IRC04:59
*** mickeys has quit IRC05:01
*** ociuhandu has joined #openstack-meeting-305:05
*** Poornima has joined #openstack-meeting-305:13
*** psachin has joined #openstack-meeting-305:13
*** psachin has quit IRC05:13
*** psachin has joined #openstack-meeting-305:14
*** itxaka has joined #openstack-meeting-305:17
*** donghao has joined #openstack-meeting-305:17
*** clarkb has quit IRC05:18
*** prateek has joined #openstack-meeting-305:20
*** egallen has quit IRC05:23
*** soichi has joined #openstack-meeting-305:23
*** kaz has joined #openstack-meeting-305:29
*** vnyyad has joined #openstack-meeting-305:29
soichihi05:30
kazhi05:30
vnyyadHi05:31
soichi#startmeeting taas05:31
openstackMeeting started Wed Oct  5 05:31:30 2016 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:31
*** openstack changes topic to " (Meeting topic: taas)"05:31
openstackThe meeting name has been set to 'taas'05:31
soichi#link https://wiki.openstack.org/wiki/Meetings/taas05:31
soichi#topic Inclusion in Governance and Neutron Stadium05:32
*** openstack changes topic to "Inclusion in Governance and Neutron Stadium (Meeting topic: taas)"05:32
soichivnyyad, kaz: would you please share the status if you have any update05:32
kazsorry, i have no update.05:33
vnyyadvnyyad: none either05:33
soichiokay, let's go on the next topic05:34
soichi#topic Adding TaaS to Ocata Design Summit Ideas?05:34
*** openstack changes topic to "Adding TaaS to Ocata Design Summit Ideas? (Meeting topic: taas)"05:34
soichi#link https://etherpad.openstack.org/p/ocata-neutron-summit-ideas05:34
soichias a reference, Etehrpad for ideas in Austin/Newton design summit:05:35
-soichi- #link https://etherpad.openstack.org/p/newton-neutron-summit-ideas05:35
soichiMy idea is submitting the same agenda again, that is05:35
soichi"Tap-as-a-Service session to talk about next steps for the project: enhancements, governance, ..."05:35
soichiplease let me know if you have much better idea05:36
vnyyadadding filtering capability while mirroring would be good as i have been hearing05:36
vnyyadi can add that to etherpad if  not already there05:36
soichi+105:36
kazvnyyad: +105:37
vnyyadi guess you guys should also add the flow based approach to improve preformance to that list05:37
soichii agree with you05:38
vnyyadits is a viable approach when we have spare nics  on the server05:38
soichiyes05:38
vnyyadbut yes first things the Governance issue05:39
soichisure, i think so too05:40
vnyyadwhen is the design session due for05:40
*** bks has joined #openstack-meeting-305:40
soichiI'm not sure. I think it is not announced yet.05:41
vnyyadha ok05:41
vnyyadwould it be possible to attend it over skype or other means in case i cannot make it05:42
soichiI guess contributors meet up will be held on 28th Friday.05:42
vnyyadha ok.... since it is in CET time zone i can dial in or come over skype and join it05:42
*** amotoki has joined #openstack-meeting-305:43
soichithank you05:43
soichiI will add two topics to the Etherpad 1) Governance and 2) Add the flow based approach.05:44
vnyyadi will add the filtering05:44
soichithank you05:44
soichi#topic Daylight Saving Time will end. Do we need to change IRC time slot from Nov.?05:46
*** openstack changes topic to "Daylight Saving Time will end. Do we need to change IRC time slot from Nov.? (Meeting topic: taas)"05:46
soichithe summer time period ends at Oct 30th in EU and at Nov 6th in US.05:47
kazi think we do not need to change IRC time.05:48
vnyyad+105:49
*** SarathMekala has quit IRC05:49
*** markvoelker has joined #openstack-meeting-305:50
soichivnyyad, kaz: i see, but I'd like to discuss it again on next week because Anil is not available today.05:50
kazsoichi: sure05:50
vnyyadyes05:51
*** lpetrut has joined #openstack-meeting-305:51
soichi#topic Open Discussion05:51
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"05:51
soichido you have any topic?05:54
vnyyadnothing from me05:54
kazme too05:55
*** markvoelker has quit IRC05:55
soichivnyyad: I'm looking forwad to see the presenation: "Tapping in NFV cloud : A real world showcase by Swisscom, Ericsson and IXIA"05:55
vnyyadsure :)05:55
vnyyadi am still working out how to attend the summit05:55
vnyyadbut i will try my best to make it there or be there virtually there05:56
soichii hope you can attend and we have a chance to meet05:56
vnyyadyes05:56
kaz+105:56
*** amotoki has quit IRC05:57
soichiokay, I'd like to close today's meeting05:58
soichisee you next week05:58
vnyyadthanks, see you next week05:58
kazbye05:59
soichi#endmeeting05:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:59
openstackMeeting ended Wed Oct  5 05:59:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-10-05-05.31.html05:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-10-05-05.31.txt05:59
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-10-05-05.31.log.html05:59
soichibye05:59
vnyyadbye05:59
*** kaz has quit IRC05:59
*** vnyyad has quit IRC05:59
*** soichi has left #openstack-meeting-305:59
*** salv-orlando has quit IRC06:01
*** chandanc_ has quit IRC06:07
*** david-lyle has joined #openstack-meeting-306:08
*** chandanc_ has joined #openstack-meeting-306:09
*** toddjohn has joined #openstack-meeting-306:10
*** paul-carlton2 has joined #openstack-meeting-306:12
*** toddjohn has quit IRC06:15
*** haleyb_ has joined #openstack-meeting-306:16
*** nkrinner_afk is now known as nkrinner06:19
*** VW has joined #openstack-meeting-306:20
*** haleyb_ has quit IRC06:21
*** itxaka_ has joined #openstack-meeting-306:22
*** VW has quit IRC06:25
*** itxaka has quit IRC06:26
*** itxaka__ has joined #openstack-meeting-306:28
*** itxaka_ has quit IRC06:29
*** andreas_s has joined #openstack-meeting-306:33
*** rossella_s has quit IRC06:34
*** rossella_s has joined #openstack-meeting-306:35
*** salv-orlando has joined #openstack-meeting-306:36
*** jtomasek_ has joined #openstack-meeting-306:36
*** itxaka_ has joined #openstack-meeting-306:38
*** salv-orlando has quit IRC06:40
*** itxaka__ has quit IRC06:41
*** lpetrut has quit IRC06:43
*** pcaruana has joined #openstack-meeting-306:46
*** jtomasek_ has quit IRC06:50
*** markvoelker has joined #openstack-meeting-306:51
*** Rockyg has joined #openstack-meeting-306:52
*** markvoelker has quit IRC06:56
*** salv-orlando has joined #openstack-meeting-306:56
*** yamahata has joined #openstack-meeting-306:58
*** tqtran has joined #openstack-meeting-307:00
*** david-lyle has quit IRC07:02
*** tqtran has quit IRC07:05
*** matrohon has joined #openstack-meeting-307:09
*** numans has joined #openstack-meeting-307:13
*** amotoki has joined #openstack-meeting-307:20
*** hogepodge has quit IRC07:21
*** amotoki has quit IRC07:32
*** abalutoiu has joined #openstack-meeting-307:41
*** chandanc_ has quit IRC07:41
*** amotoki has joined #openstack-meeting-307:43
*** ivar-lazzaro has quit IRC07:49
*** mickeys has joined #openstack-meeting-307:50
*** markvoelker has joined #openstack-meeting-307:51
*** mickeys has quit IRC07:52
*** mickeys has joined #openstack-meeting-307:53
*** tuanluong has quit IRC07:54
*** salv-orl_ has joined #openstack-meeting-307:54
*** markvoelker has quit IRC07:56
*** amotoki has quit IRC07:56
*** salv-orlando has quit IRC07:57
*** mickeys has quit IRC07:58
*** paul-carlton2 has quit IRC08:02
*** eyalb has joined #openstack-meeting-308:04
eyalbhi08:04
*** eyalb has left #openstack-meeting-308:05
*** chandanc_ has joined #openstack-meeting-308:06
*** alineb has left #openstack-meeting-308:07
*** hogepodge has joined #openstack-meeting-308:11
*** toddjohn has joined #openstack-meeting-308:11
*** toddjohn has quit IRC08:16
*** ccamacho has joined #openstack-meeting-308:16
*** amotoki has joined #openstack-meeting-308:17
*** paul-carlton2 has joined #openstack-meeting-308:24
*** kzaitsev_mb has joined #openstack-meeting-308:25
*** salv-orl_ has quit IRC08:48
*** markvoelker has joined #openstack-meeting-308:52
*** mickeys has joined #openstack-meeting-308:54
*** markvoelker has quit IRC08:57
*** mickeys has quit IRC08:58
*** sdake has quit IRC08:59
*** amotoki has quit IRC09:00
*** lpetrut has joined #openstack-meeting-309:00
*** lpetrut has quit IRC09:01
*** lpetrut has joined #openstack-meeting-309:03
*** Poornima has quit IRC09:03
*** toddjohn has joined #openstack-meeting-309:13
*** kzaitsev_mb has quit IRC09:16
*** toddjohn has quit IRC09:17
*** VW has joined #openstack-meeting-309:21
*** VW has quit IRC09:25
*** amotoki has joined #openstack-meeting-309:31
*** amotoki has quit IRC09:31
*** amotoki has joined #openstack-meeting-309:31
*** ivar-lazzaro has joined #openstack-meeting-309:37
*** ivar-lazzaro has quit IRC09:42
*** pgadiya has quit IRC09:49
*** markvoelker has joined #openstack-meeting-309:53
*** markvoelker has quit IRC09:58
*** annp has quit IRC10:01
*** pgadiya has joined #openstack-meeting-310:01
*** tqtran has joined #openstack-meeting-310:02
*** tqtran has quit IRC10:06
*** sdague has joined #openstack-meeting-310:15
*** rstarmer has joined #openstack-meeting-310:17
*** salv-orlando has joined #openstack-meeting-310:19
*** ociuhandu has quit IRC10:20
*** sambetts|afk is now known as sambetts10:21
*** salv-orlando has quit IRC10:25
*** hoangcx has quit IRC10:31
*** kzaitsev_mb has joined #openstack-meeting-310:31
*** rossella_s has quit IRC10:34
*** rossella_s has joined #openstack-meeting-310:35
*** abalutoiu has quit IRC10:41
*** rtheis has joined #openstack-meeting-310:54
*** markvoelker has joined #openstack-meeting-310:54
*** zhurong has joined #openstack-meeting-310:56
*** markvoelker has quit IRC10:59
*** rstarmer has quit IRC11:01
*** rstarmer has joined #openstack-meeting-311:02
*** abalutoiu has joined #openstack-meeting-311:02
*** chandanc_ has quit IRC11:03
*** ccamacho is now known as ccamacho|lunch11:15
*** salv-orlando has joined #openstack-meeting-311:21
*** yamamoto has joined #openstack-meeting-311:22
*** salv-orlando has quit IRC11:26
*** alexismonville has joined #openstack-meeting-311:29
*** salv-orlando has joined #openstack-meeting-311:30
*** coolsvap is now known as coolsvap_11:30
*** pgadiya has quit IRC11:51
*** markvoelker has joined #openstack-meeting-311:54
*** jlanoux has joined #openstack-meeting-311:58
*** markvoelker has quit IRC11:59
*** anilvenkata has quit IRC12:02
*** pgadiya has joined #openstack-meeting-312:08
*** ociuhandu has joined #openstack-meeting-312:09
*** haleyb_ has joined #openstack-meeting-312:11
*** coolsvap_ is now known as coolsvap12:13
*** pgadiya has quit IRC12:14
*** gouthamr has joined #openstack-meeting-312:16
*** sdake has joined #openstack-meeting-312:19
*** ccamacho|lunch is now known as ccamacho12:24
*** jdwald has joined #openstack-meeting-312:27
*** pgadiya has joined #openstack-meeting-312:28
*** krtaylor has quit IRC12:30
*** cleong has joined #openstack-meeting-312:38
*** atuvenie has joined #openstack-meeting-312:42
*** claudiub has joined #openstack-meeting-312:44
*** markvoelker has joined #openstack-meeting-312:44
*** VW has joined #openstack-meeting-312:44
*** abalutoiu has quit IRC12:44
*** baoli has joined #openstack-meeting-312:44
*** VW has quit IRC12:45
*** rstarmer has quit IRC12:54
*** MarkBaker has quit IRC12:56
*** abalutoiu has joined #openstack-meeting-312:59
*** pgadiya has quit IRC12:59
*** kzaitsev_mb has quit IRC13:00
*** bks has quit IRC13:00
*** kzaitsev_mb has joined #openstack-meeting-313:00
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Oct  5 13:00:31 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
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
claudiubhellou13:00
claudiubgonna wait a bit for people to join13:01
*** MarkBaker has joined #openstack-meeting-313:01
*** sagar_nikam has joined #openstack-meeting-313:01
sagar_nikamHi13:01
claudiubhello :)13:02
claudiubsagar_nikam: anyone else joining?13:02
*** prateek has quit IRC13:03
atuveniehi all13:03
claudiubhello :)13:03
sagar_nikamno13:03
sagar_nikamwe can start13:04
claudiubcool13:04
claudiub#topic nova patches13:04
*** openstack changes topic to "nova patches (Meeting topic: hyper-v)"13:04
claudiubsooo, just fyi, we already merged 2 blueprints in ocata in nova13:04
sagar_nikamnice !!!13:05
sagar_nikamwhich ones ?13:05
*** baoli_ has joined #openstack-meeting-313:05
claudiubthose are the Hyper-V UEFI one, and the storage QoS one.13:05
claudiub#link Hyper-V storage QoS support patch: https://review.openstack.org/#/c/175479/13:05
claudiub#link Hyper-V UEFI Secure Boot https://review.openstack.org/#/c/209581/13:05
claudiubthere have been a couple of python3 related patches that merged too13:05
lpetruthey guys13:06
sagar_nikamany progress on FC ?13:06
sagar_nikamin ocata13:06
claudiuband I can say that nova-compute on Hyper-V works well with python 313:06
sagar_nikamany perf improvement after moving to python 313:06
sagar_nikam?13:06
*** donghao has quit IRC13:07
claudiubthe os-brick in nova patch is still pending.13:07
claudiub#link os-brick in nova patch: https://review.openstack.org/#/c/273504/13:07
claudiubthe blueprint is approved, and it got some core review on it13:07
claudiubsoo, yeah13:07
sagar_nikamok13:08
*** reedip has joined #openstack-meeting-313:08
*** baoli has quit IRC13:08
*** GheRivero has joined #openstack-meeting-313:08
claudiubalso, for the Hyper-V OVS vif driver, the blueprint is approved, and the patch no longer has a -2. still waiting reviews13:08
claudiubas for the python 3 performance impact: we didn't do rally tests against it yet13:08
claudiubbut python 3 is typically slower than python 2.713:08
lpetruton the other hand, WS 2016 seems to bring some considerable performance improvements13:09
sagar_nikamlpetrut: that is irrespective of python 3 ?13:09
lpetrutyep13:09
claudiubyeah, so it can potentially balance it out. :)13:09
claudiubas for blueprints, we still have the shielded vms spec up for review.13:10
claudiubdidn't get much attention13:10
sagar_nikamok13:11
claudiubquestions?13:11
sagar_nikamno13:11
sagar_nikamnot much as of now13:11
claudiubmoving on13:11
claudiub#topic PyMI release13:11
*** openstack changes topic to "PyMI release (Meeting topic: hyper-v)"13:11
claudiubsoo, PyMI 1.0.4 was released.13:12
claudiub#topic PyMI release: https://pypi.python.org/pypi/PyMI13:12
*** openstack changes topic to "PyMI release: https://pypi.python.org/pypi/PyMI (Meeting topic: hyper-v)"13:12
*** lblanchard has joined #openstack-meeting-313:12
claudiubfeel free to grab it13:12
claudiubas mentioned in the previous meetings, it boasts better performance. :)13:12
sagar_nikamok.. we will check it13:13
claudiub#topic monasca status13:13
*** openstack changes topic to "monasca status (Meeting topic: hyper-v)"13:13
claudiubehm, I have to rebase pretty much everything again :)13:14
claudiubalso got some comments. will have to check them out.13:14
sagar_nikamwhy ? the last time they were almost fine and just wanted some documentation13:14
claudiubdon't know if I've mentioned this previously, but I've also sent a patch adding documentaion13:15
claudiubyeah, will have to check the comments. it probably won't be anyting big anyways13:16
sagar_nikamthe last time we discussed this... you attended a meeting with monasca team and they were fine with the code except docs13:16
claudiubyep13:16
*** ccamacho has quit IRC13:16
*** tonytan4ever has joined #openstack-meeting-313:17
sagar_nikamso new code comments again ?13:17
claudiubyep. anyways, will sort it as soon as i can13:17
sagar_nikamok13:17
sagar_nikamthanks13:17
claudiubnp :)13:17
claudiub#topic open discussion13:18
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:18
claudiubhm, so there are a couple of things that I want to mention here13:19
claudiubfirst of all, on your hyper-v compute nodes, you should change the neutron_hyperv_agent.conf's firewall_driver to hyperv.neutron.security_groups_driver.HyperVSecurityGroupsDriver13:20
claudiubstarting with ocata, the old value will no longer work13:20
sagar_nikamok ...13:21
sagar_nikamso this is for ocata only ?13:21
claudiub#info The neutron_hyperv_agent.conf firewall_driver config value must be changed to hyperv.neutron.security_groups_driver.HyperVSecurityGroupsDriver when upgrading to Ocata13:22
claudiubthe old value has been deprecated since mitaka13:22
claudiubstill works, but in ocata it won't work anymore13:22
claudiubfor more info, see patch:13:23
sagar_nikamok got it. will mention it to sonu13:23
claudiub# Removes remaining Hyper-V plugin in neutron: https://review.openstack.org/#/c/378299/113:23
claudiub#link Removes remaining Hyper-V plugin in neutron: https://review.openstack.org/#/c/378299/113:23
claudiubthe docs have been updated as well.13:23
claudiubsecondly, there has been a bug affecting python 3 on hyper-v, on python-swiftclient, which has been fixed and merged13:24
claudiub#link https://bugs.launchpad.net/python-swiftclient/+bug/162810713:25
openstackLaunchpad bug 1628107 in python-swiftclient "Futures package should not be installed for python 3" [Undecided,Fix released] - Assigned to Claudiu Belu (cbelu)13:25
claudiubbasically, python-swiftclient was installing the futures library in python3, and it shouldn't have, as, ironically, futures is not python 3 compatible13:26
claudiubpython 3 comes with a native futures library anyways13:26
sagar_nikamwhy is this affecting hyperv ? nova's requirements.txt has it and hence it gets installed on nova compute for hyperv ?13:26
claudiubit does, but if you check the requirement, it says that it will only be installed on python 2.6 or python 2.713:27
claudiubfutures>=3.0;python_version=='2.7' or python_version=='2.6' # BSD13:28
claudiubthat line basically means that futures>=3.0 will be installed if the python version is 2.7 or 2.613:28
*** tongli has joined #openstack-meeting-313:28
sagar_nikamok13:28
*** SridarK_ has quit IRC13:30
claudiubalso, currently working on solving some of the tests that are failing on the ci13:30
claudiubseems i'll have to send a patch up, most probably oslo.messaging13:30
claudiubanyways, that's about it from me13:31
claudiubsagar_nikam: any news from your side?13:31
sagar_nikamone point from me13:31
sagar_nikami am planning to start off on kubernetus13:31
sagar_nikamhow is it going ?13:31
sagar_nikamanything that i can try13:31
claudiubatuvenie: hi13:32
atuvenieheya, what are your plans there sagar?13:32
*** zhenguo has joined #openstack-meeting-313:32
atuveniethe aprenda folks have a WIP pull request that is on the K8 repo13:32
atuvenieI'm helping in the review process with that13:33
sagar_nikamfirst of all.... kubernetus is new to me13:33
sagar_nikami will start some initial learning and trying out basic things13:33
sagar_nikamand then if something is ready for windows, i can try that13:33
sagar_nikamand provide you feedback13:34
atuvenieon the other side, I'm still playing with OVN to setup a overlay network like k8 needs, but it's kinda slow13:34
*** ccamacho has joined #openstack-meeting-313:34
*** aa___ has joined #openstack-meeting-313:34
*** rstarmer has joined #openstack-meeting-313:34
*** aa___ has quit IRC13:34
sagar_nikamso as of now, basic k8s tests with windows also not a good option ?13:34
*** rbak has joined #openstack-meeting-313:35
sagar_nikami am starting on k8s may be in a week or 10 days.. and will try for few weeks13:35
sagar_nikamand then i can try with windows13:35
atuveniewell, you can use the pull request that is currently under review13:35
sagar_nikamso may be a month from now, i can try k8s for windows13:35
atuvenieusing that, I can create pods but networking is still a issue for me13:35
sagar_nikamany docs available13:36
sagar_nikamon how to use it ?13:36
sagar_nikamand containers are windows containers ?13:36
*** rstarmer has quit IRC13:36
*** rstarmer has joined #openstack-meeting-313:37
*** toddjohn_ has joined #openstack-meeting-313:37
atuveniecontainers are indeed windows containers13:38
atuveniehave not tried with hyper-v containers13:38
sagar_nikamok13:38
sagar_nikamso let me try k8s on linux first13:38
sagar_nikamjust basic hands on13:38
sagar_nikamto get familar13:38
sagar_nikamand then may be i will reach out to you to try on windows13:38
sagar_nikamis that fine ?13:39
atuveniesure13:39
*** rstarmer has quit IRC13:39
sagar_nikamok thanks13:39
sagar_nikamnext question13:40
sagar_nikamclaudiub: any plans on monasca-log ?13:40
claudiubsagar_nikam: didn't look at it yet13:40
sagar_nikamok13:41
sagar_nikamis that planned ?13:41
sagar_nikamdid the monasca team mention anything sbout it13:41
sagar_nikamabout it13:41
claudiubno they haven't. it is a bit low on my priority list, to be honest13:41
claudiubmy main concern is nova and work on it. when I don't have anything to do there, and i have some free time, I can take a look13:42
claudiubsagar_nikam: any news from the testing lab?13:42
sagar_nikamok sure got it13:43
sagar_nikamno... getting slot has been difficult13:43
sagar_nikammay be pushed by some more time13:43
claudiuback13:43
sagar_nikamwill let you know as and when we start it13:43
sagar_nikamwe plan to test it on mitaka13:43
claudiubsounds good13:44
sagar_nikami was told by sonu that some neutron-agent code may not scale13:44
sagar_nikamwe are not sure though13:44
sagar_nikamthe last time, sonu's team picked some code from mitaka and put it in liberty13:44
sagar_nikamand found sclability issues13:45
sagar_nikamwe reverted it back to liberty13:45
sagar_nikamand we achieved good performance13:45
sagar_nikammay be it just a backport issue13:45
*** iyamahat has joined #openstack-meeting-313:45
*** abalutoiu has quit IRC13:45
sagar_nikamcant confirm13:45
claudiubthere shouldn't have been any performance regressions from liberty to mitaka13:45
claudiubfrom our tests, mitaka was performing significantly better than liberty13:46
sagar_nikami think we would have taken only some pieces of code13:46
claudiubwe presented those results a few months ago13:46
sagar_nikamwe will try with full mitaka13:46
sagar_nikamrather than just some code backported13:46
*** yamamoto has quit IRC13:47
claudiubok13:47
claudiubwell, that's about it from me13:47
claudiubany other questions from you, sagar_nikam?13:47
sagar_nikamno not as of now13:47
claudiubwell then, we can end the meeting soon. :)13:48
sagar_nikamhow is the summit plans going ?13:48
claudiubwell, we're currently working on demo's and other cool booth setups13:48
claudiubhopefully it will be an enjoyable summit. :)13:49
claudiubbecause after this, the summits won't be the same13:49
claudiubas the summit will split into 213:49
sagar_nikamwhy ?13:49
sagar_nikamoh ... what is that13:49
sagar_nikamdont know about it13:49
claudiubinto the general public / marketplace summit, and the design summit13:49
sagar_nikamok13:50
claudiubwhich will be in 2 separate locations, in 2 separate dates13:50
claudiubi don't really know the reason13:50
sagar_nikamok13:50
*** haleyb_ has quit IRC13:50
sagar_nikami am done with all topics... thanks13:51
claudiubwell then, thanks folks for joining, see you next week!13:51
claudiub#endmeeting13:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:51
openstackMeeting ended Wed Oct  5 13:51:33 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-10-05-13.00.html13:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-10-05-13.00.txt13:51
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-10-05-13.00.log.html13:51
*** chandanc_ has joined #openstack-meeting-313:53
*** salv-orl_ has joined #openstack-meeting-313:54
*** eliqiao has quit IRC13:55
*** MarkBaker has quit IRC13:55
*** yamahata has quit IRC13:55
*** MarkBaker has joined #openstack-meeting-313:55
*** alex_xu has quit IRC13:55
*** yamahata has joined #openstack-meeting-313:55
*** sagar_nikam has quit IRC13:56
*** salv-orlando has quit IRC13:57
*** chandanc_ is now known as chandanc13:57
*** SarathMekala has joined #openstack-meeting-314:01
ajo_#startmeeting neutron_qos14:01
openstackMeeting started Wed Oct  5 14:01:51 2016 UTC and is due to finish in 60 minutes.  The chair is ajo_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
ajo_let's leave some time for people to join14:02
njohnstonHi!  I am lurking today.14:02
ajo_#chair njohnston14:02
openstackCurrent chairs: ajo_ njohnston14:02
*** alex_xu has joined #openstack-meeting-314:02
ajo_ack njohnston  :)14:02
*** rnoriega has joined #openstack-meeting-314:03
ajo_I see a few missing people, please say hi, whoever is around for this meeting :-)14:03
rnoriegahi14:03
ajo_hi rnoriega  ;)14:03
ltomasbohi14:03
ajo_hi ltomasbo !! :)14:03
ajo_I heard that some people from Ericsson R&D would be joined because they're interested in contributing ;)14:04
ajo_I miss slaweq, ralonso, and others hmmm14:05
ajo_I wonder if it's worth having the meeting or if a email status update will be enough14:06
ajo_rnoriega, ltomasbo thoughts? , shall we proceed, email, or wait?14:06
*** _SarathMekala_ has joined #openstack-meeting-314:06
* ajo_ got everyone bored of QoS :P14:07
* njohnston is still here!14:07
ajo_hi njohnston  :=)14:07
ajo_this was more or less the agenda I had ready:14:07
ajo_#link https://etherpad.openstack.org/p/qos-meeting14:07
*** galstrom_zzz is now known as galstrom14:07
*** yamamoto has joined #openstack-meeting-314:08
*** absubram has quit IRC14:08
*** davidsha has joined #openstack-meeting-314:09
ajo_ok, 10 minutes is enough, I'm going to summarize the status,14:09
*** SarathMekala has quit IRC14:09
ajo_and wrap up this quickly14:09
rnoriegaajo_, good!14:10
ajo_so14:10
davidshahey, sorry for being late!14:10
ajo_#topic RFEs-approved14:10
*** openstack changes topic to "RFEs-approved (Meeting topic: neutron_qos)"14:10
ajo_hi davidsha  :)14:10
ajo_#links https://bugs.launchpad.net/neutron/+bugs?field.tag=qos+rfe-approved+&field.tags_combinator=ALL14:10
ajo_one is missing on that link, let me fix it14:10
rnoriegaso we have three RFEs that have been approved, right?14:11
*** dims has quit IRC14:11
rnoriegaajo_, it's fixed...thanks14:12
ajo_Yeah, I've toggled strict min bw to rfe-approved (from rfe-postponed)14:12
ajo_but I'm unsure I have the right to do that, I have commented it, and said that we should start by spec there.14:13
ajo_#link https://bugs.launchpad.net/neutron/+bug/1586056  (extended validation)14:13
openstackLaunchpad bug 1586056 in neutron "[RFE] Improved validation mechanism for QoS rules with port types" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:13
ajo_that one is about fixing some technical debt we have,14:13
ajo_to make sure any changes to policies are validated with the plugin or mechanism drivers,14:13
ajo_or changes to ports or networks (attached policy changes)14:14
ajo_since dataplane capabilities for QoS are quite heterogeneous14:14
ajo_that depends on more tech-debt14:14
ajo_#link https://review.openstack.org/#/c/351858/  (qos notification-driver  to  "driver")14:15
rnoriegaok14:15
ajo_Some refactor over the current "qos driver" to make it more consistent and be able to do the improved validation properly14:15
*** eliqiao has joined #openstack-meeting-314:16
ajo_#link https://bugs.launchpad.net/neutron/+bug/1560961  (instance ingress bw limit)14:16
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:16
ajo_this one depends on the two above ;)14:16
ajo_this is like a train, sorry ;)14:16
ajo_it does not physically depend on the others, but it's a constraint neutron-drivers has imposed on it, to make sure we fix the technical debt first,14:17
ajo_which, makes sense IMHO14:17
*** dims has joined #openstack-meeting-314:17
ajo_#link https://bugs.launchpad.net/neutron/+bug/1560963 (minimum bw egress -non-strict-)14:17
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,Fix released] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:17
ajo_that one is being worked out by Rodolfo Alonso14:18
ajo_partly merged for newton (SR-IOV support)14:18
ajo_and OVS & LB efforts are being developed to be merged in Ocata14:18
ajo_let me look for the links,14:18
ajo_I know ltomasbo is interested in this :)14:18
rnoriegaajo_, this last one is not strict bw support14:18
ltomasboyep, I was about to ask..14:19
rnoriegaright?14:19
ajo_rnoriega, non-strict, right14:19
rnoriegaok14:19
ltomasbonon-stric in the sense that it is not "nova-aware"?14:20
ajo_correct14:20
ajo_non scheduling aware14:20
ltomasbook14:20
ajo_#link https://review.openstack.org/318531  QoS minimum egress for ovs-agent14:20
ajo_#link https://review.openstack.org/357865 QoS minimum egress for LinuxBridge14:20
ajo_buy the great Rodolfo Alonso Hernandez!, we should get him on some hall of fame (/me blinks eye on njohnston )14:21
ajo_buy -> by :)14:21
rnoriegaajo_, lol! I wanted to buy a Rodolfo for me as well14:21
ajo_he's awesome14:22
njohnston:-)14:22
ajo_and now, the hot topic14:22
davidsha+114:22
ajo_#link https://bugs.launchpad.net/neutron/+bug/1578989 minimum bandwidth egress strict (scheduling aware)14:22
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,Confirmed]14:22
ajo_this feature builds on the other14:22
ajo_and it's necessary to make sure no hypervisor is scheduled more "minimum bandwidth" than the specific nics can handle in total14:23
ltomasboso, it will be enforce at host level, right?14:23
ajo_so, effectively enforcing SUM(port[i].min_bw) for port in hypervisor   <= hypervisor.bw14:24
ajo_more or less14:24
ltomasboif the bottleneck is at another point in the network, it will not be enforced, right14:24
ajo_that's a simplified equation, as we need to consider the network over which the packets travel, and the direction too14:24
rnoriegaajo_, sorry for my ignorant question. But is there anything that could be done in parallel to accelerate the development of the strict min bw support?14:24
rnoriegalike writing a spec14:24
rnoriegahelping with some patches on the previous work14:25
ajo_rnoriega, yes, let me get into that :)14:25
rnoriegaajo_, ok, thanks!14:25
*** rhochmuth has joined #openstack-meeting-314:25
*** eliqiao has quit IRC14:25
ajo_I will summarize now the steps to get there14:25
ajo_ltomasbo, you're right14:25
ajo_ltomasbo, we have no capability now to see how the network architecture physically is14:25
ajo_I wonder if we could model that on a later step14:26
ajo_and let the scheduler consume from there14:26
ajo_for example, we have the switches dataplane capacity, etc...14:26
ajo_interconnections between switches14:26
ajo_that's a harder stone to chew14:26
ltomasboajo_, any plans to tackle that? Perhaps in a VNF chain (as a first step)14:26
ajo_IP connectivity /& routes for tunnels14:26
ajo_ltomasbo, thinking of that problem causes me heartburn literally ;D14:27
ltomasbo:D14:27
ajo_ltomasbo, I'd be very happy if anybody wants to look at it14:27
ajo_but we should build the foundations first :)14:27
ltomasbocould be related to the EU project, but it will depend on the previous patches too14:28
*** hj-hpe has joined #openstack-meeting-314:28
*** psachin has quit IRC14:28
ajo_ltomasbo, is on a fancy NFV related project ;)14:28
ajo_sorry, no comma :)14:28
*** eliqiao has joined #openstack-meeting-314:28
ajo_so14:29
ajo_steps to get this RFE done (eventually)14:29
ajo_I'd say it's an ocata & beyond effort, specially since Ocata cycle is shorter14:29
*** toddjohn_ has quit IRC14:29
ajo_and since we have dependencies on some extra work for nova14:29
ajo_so14:30
ajo_0) Writing a neutron spec including all the next steps in detail14:30
ajo_I plan on tackling that, but I'm super happy if anybody wants to step in to write the barebones, and have me as Co-Author14:30
ajo_since I must first kill the technical debt we have or drivers will kill me :)14:31
ajo_such spec could contain some of the next steps:14:31
ajo_1) Neutron collecting physnet/tunneling available bandwidth on every compute, with the option to override via config.14:31
ajo_2) Neutron reporting such available bandwidth to the new nova placement API   inventories in the form of NIC_BW_<physnet>_{ingress,egress}14:31
ajo_that'd mean that neutron tells nova "this hypervisor has  10Gb total of NIC_BW_tenant_egress , 10Gb total of NIC_BW_tenant_ingress" as an example14:32
ajo_for every hypervisor14:32
ajo_also for external networks attached to compute nodes, etc..14:32
ajo_We'd make use of the new nova placement API: #link  http://specs.openstack.org/openstack/nova-specs/specs/newton/approved/generic-resource-pools.html14:33
ajo_but we'd be missing a key feature from nova14:33
*** kzaitsev_mb has quit IRC14:33
ajo_#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/custom-resource-classes14:33
ajo_which is being worked out14:33
ajo_Jaypipes++14:34
ajo_that is14:34
ajo_3) Nova accepting custom resource types (NIC_BW_.....) now compute nodes report via this http api the CPU, DISK, RAM.14:34
*** ibmko has joined #openstack-meeting-314:34
ajo_4) Changes in how Nova handles ports, by creating/fetching them before doing any scheduling. (this seems to be planned for Cellsv2)14:34
*** baoli_ has quit IRC14:35
ajo_that way, nova can know the requirements of the port (in form of bandwidth) before trying to schedule the instance14:35
ltomasboajo_, why neutron needs to tell nova about static information (total NIC_BW)?14:35
ltomasboor with total you meant total_in_use?14:35
ajo_ltomasbo, the alternative would be14:35
*** spzala has joined #openstack-meeting-314:35
ajo_nova find the qos_policy_id on port, as it's now14:35
ajo_but then has to fetch the policy, and rules, and make an interpretation of such rules14:36
ajo_which could be complex as they grow14:36
*** hosanai has joined #openstack-meeting-314:36
ajo_so after discussing with the nova team, it seems that the more reasonable option was to give a chewed output for nova (when nova creates, or fetches a port)14:36
ltomasboso, if there is no QoS policy, there will be no information about the bandwidth of the hosts, right?14:37
ajo_ltomasbo, I'm talking about the ports14:37
ajo_when nova does a GET or POST of a port to neutron14:37
ajo_we'd provide the breakdowns of NIC_BW per net/direction14:38
ajo_and that'd be empty if there is no qos policy attached to the port14:38
*** hj-hpe has quit IRC14:38
*** cleong has quit IRC14:38
*** rossella_s has quit IRC14:38
*** hogepodge has quit IRC14:38
*** itxaka_ has quit IRC14:38
*** margaret has quit IRC14:38
*** jed56 has quit IRC14:38
*** davidlenwell has quit IRC14:38
*** mugsie has quit IRC14:38
ltomasboahh, ok, I thought you were talking about host_bw14:38
*** mugsie has joined #openstack-meeting-314:39
*** rossella_s has joined #openstack-meeting-314:39
*** itxaka_ has joined #openstack-meeting-314:39
*** hj-hpe has joined #openstack-meeting-314:39
*** hogepodge has joined #openstack-meeting-314:39
ajo_ah, no no :), that's on step 2, when neutron reports to nova placement API,14:39
ajo_such reporting is static (not changing as we add or remove ports, it's the total available)14:39
*** mickeys has joined #openstack-meeting-314:40
*** davidlenwell has joined #openstack-meeting-314:40
ajo_nova will be responsible for counting down/up available traffic for this guarantee14:40
ajo_and that's all14:40
ltomasbook, now it is clear!14:40
ajo_rnoriega, any question about all this? :)14:41
rnoriegaajo_, not really! it was a very clear explanation of the current state...14:41
rnoriegaajo_, thanks!!!14:41
*** DuncanT has quit IRC14:41
rnoriegaajo_++14:41
ajo_ltomasbo, rnoriega , anyone, you're welcome to throw in an initial spec for this based on the steps :)14:41
*** cleong has joined #openstack-meeting-314:42
rnoriegaajo_, cool! let's see what we can do!14:42
ltomasbook14:42
ajo_#topic other RFEs14:43
*** openstack changes topic to "other RFEs (Meeting topic: neutron_qos)"14:43
ajo_https://bugs.launchpad.net/neutron/+bugs?field.tag=qos+rfe+&field.tags_combinator=ALL14:43
ajo_we had this one too:14:43
ajo_https://bugs.launchpad.net/neutron/+bug/161472814:43
openstackLaunchpad bug 1614728 in neutron "REF: qos: rule list in policy is too difficult to use" [Undecided,Won't fix]14:43
*** jed56 has joined #openstack-meeting-314:43
ajo_which I have moved to won't fix by now, since we can't make changes to the API, unless we get microversioning (one day)14:44
ajo_I'm moving this other one to Won't fix for the same reason:14:44
ajo_https://bugs.launchpad.net/neutron/+bug/158014914:44
openstackLaunchpad bug 1580149 in neutron "[RFE] Rename API options related to QoS bandwidth limit rule" [Wishlist,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:44
*** david-lyle has joined #openstack-meeting-314:45
*** kzaitsev_mb has joined #openstack-meeting-314:45
*** mickeys has quit IRC14:45
*** emagana has joined #openstack-meeting-314:45
ajo_and, there's ECN which needs more maturing14:46
*** zhurong has quit IRC14:46
ajo_I've heard non formal requests to provide pps limits, right rnoriega  ?14:46
rnoriegaajo_, yep14:46
*** Fdaisuke has joined #openstack-meeting-314:46
ajo_and also requests about, providing warnings on bandwidth usage14:47
rnoriegaajo_, right too14:47
ajo_but that's more likely to fit in https://bugs.launchpad.net/neutron/+bug/159291814:47
openstackLaunchpad bug 1592918 in neutron "[RFE] Adding Port Statistics to Neutron Metering Agent" [Wishlist,In progress] - Assigned to Sana Khan (sana.khan)14:47
*** haleyb_ has joined #openstack-meeting-314:47
*** DuncanT has joined #openstack-meeting-314:47
ajo_we can look at it when we don't have so much on our shoulders14:47
rnoriegaajo_, agreed. Thanks14:47
ajo_#topic bugs14:48
*** openstack changes topic to "bugs (Meeting topic: neutron_qos)"14:48
ajo_#link http://bit.ly/1WhXlzm BUGS14:48
ajo_let's see if we have anything there to be tackled14:48
*** Swami has joined #openstack-meeting-314:48
ajo_#link https://bugs.launchpad.net/neutron/+bug/1627749 qos driver api can have better error handling14:48
openstackLaunchpad bug 1627749 in neutron "qos driver api can have better error handling" [Medium,Confirmed]14:48
ajo_I agree, this one has been filled by yamamoto14:48
ajo_basically, we could have other backends, like midonet in this case14:49
ajo_which could fail when we ask to modify a policy14:49
ajo_and we need to handle that properly14:49
*** yamahata has quit IRC14:49
ajo_now the opreation is just stopped14:49
*** yamamoto has quit IRC14:49
*** yamahata has joined #openstack-meeting-314:50
*** margaret has joined #openstack-meeting-314:51
ajo_#link https://bugs.launchpad.net/python-neutronclient/+bug/158729114:51
openstackLaunchpad bug 1587291 in python-neutronclient "Specifying '-F' or '--field' parameter in the qos related commands, returns abnormal result" [Low,In progress] - Assigned to Yan Songming (songmingyan)14:51
ajo_this one is in progress, probably needs reviews14:51
*** VW has joined #openstack-meeting-314:51
ajo_#link https://review.openstack.org/#/c/326902/14:51
ajo_ohh, it's merged14:51
*** haleyb_ has quit IRC14:52
*** pratid has joined #openstack-meeting-314:52
*** haad1 has joined #openstack-meeting-314:52
ajo_#link https://bugs.launchpad.net/neutron/+bug/1625570 testing DSCP in fullstack via packet inspection14:53
openstackLaunchpad bug 1625570 in neutron "fullstack : should add test of ensure traffic is using DSCP marks outbound " [Wishlist,New]14:53
ajo_that one is wishlist, but important too, because now we only make sure rules are set properly, etc,14:53
ajo_but we never check the outgoing traffic for DSCP marks14:53
njohnstonso in that case we're really testing ovs flows14:53
ajo_njohnston, ^:)14:53
*** itxaka_ has quit IRC14:53
*** bklei has joined #openstack-meeting-314:53
njohnstonnot testing the neutron code14:53
ajo_yes, we have some proposals to use pcap / tcpdump to check the real packets coming out the VM14:53
ajo_yes, but since those are our flows, we may want to test them14:54
ajo_they can become broken14:54
*** david-lyle has quit IRC14:54
ajo_(incompatibilities to ovs-fw, or the new L2 flow pipeline (eventually))14:54
ajo_the intent is... avoiding the feature from being silently broken14:54
njohnstonUnderstood.  Is there any other packet capture code in fullstack?14:54
ajo_njohnston, we have some experiments with tcpdump14:55
ajo_and I discussed some options with jlibosva but not sure what's the status14:55
njohnstonSounds fun!  And it frightens me to my core.14:55
ajo_nah, it shall just be fun14:55
ajo_1) setup rules14:55
ajo_2) ssh to the VM to send packets to tempest controller14:55
ajo_sorry14:55
ajo_not even that, no VM :)14:55
*** lpetrut has quit IRC14:55
ajo_just send packets from the first port to the 2nd14:56
ajo_(this is fullstack, no tempest14:56
*** VW has quit IRC14:56
ajo_3) capture packets on the other side with a filter for the dscp flag14:56
ajo_no packets -> rules don't work14:56
ajo_packets -> rule works14:56
*** Kamil__ has joined #openstack-meeting-314:56
ajo_and14:57
ajo_I guess we can wrap up the meeting for today, .... wasn't it going to be short? ':]14:58
njohnston:-D14:58
ltomasbo:D14:58
*** dkehn has quit IRC14:58
ajo_njohnston, ltomasbo , davidsha , njohnston , see u around14:58
*** koji has joined #openstack-meeting-314:58
njohnstonthanks ajo_14:58
davidshaThanks! see ya!14:58
ajo_thank you sirs!14:58
ltomasboThanks! See you!14:58
ajo_#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Oct  5 14:59:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-10-05-14.01.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-10-05-14.01.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-10-05-14.01.log.html14:59
*** davidsha has left #openstack-meeting-314:59
*** diga has joined #openstack-meeting-314:59
*** david-lyle has joined #openstack-meeting-315:00
*** witek has joined #openstack-meeting-315:00
rnoriegathanks ajo_ ! byee15:00
*** toddjohn has joined #openstack-meeting-315:00
*** cbellucci has joined #openstack-meeting-315:00
*** Trpger has joined #openstack-meeting-315:01
*** vhoward has joined #openstack-meeting-315:01
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Oct  5 15:01:30 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
rhochmutho/15:01
haad1hey15:01
Kamil__o/15:01
rbako/15:01
pratidhi15:01
cbelluccio/15:01
witekhi15:01
shinya_kwbto/15:01
kojio/15:01
rhochmuthi just tried starting the meeting in the moansca room15:02
bkleio/15:02
rhochmuthand no one was there15:02
hosanaio/15:02
rhochmuthhello everyone15:02
rhochmutho/15:02
Trpgerwhat's up15:02
haad1so let's start :)15:02
Fdaisukeo/15:02
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:02
rhochmuthAgenda for Wednesday October 5, 2016 (15:00 UTC)15:02
rhochmuth1.monasca-statsd (stable) and monasca-agent out of sync15:02
rhochmuth1.https://github.com/openstack/monasca-statsd/commit/c4bbfa665df15e57b73381b2467e214c4e04a70a15:02
rhochmuth2.https://github.com/openstack/monasca-agent/commit/feb0a83bd9011bac4d7c6e85afef59d0f1fdb7f515:02
rhochmuth3.2016-09-26 08:40:13 GMT-2 | WARNING | statsd | monasca_agent.statsd.udp(udp.py:111) | metric type ms not supported.15:02
rhochmuth2.Status of openstack-ansible-os_monasca  role and merging fixes15:02
rhochmuth3.Reviews15:02
rhochmuth1.https://review.openstack.org/#/c/379585/15:02
*** claudiub has quit IRC15:03
rhochmuthso, we have a little bit of an agenda today15:03
rhochmuthi guess we shoudl cover that first and then open it up15:03
rhochmuth#topic monasca-statsd (stable) and monasca-agent out of sync15:03
*** openstack changes topic to "monasca-statsd (stable) and monasca-agent out of sync (Meeting topic: monasca)"15:03
witekthat me15:04
witekwe see cited warnings when monitoring log-api15:04
*** ddieterly has joined #openstack-meeting-315:05
*** jlanoux has quit IRC15:05
witekthe commit in statsd is not in stable, and as far as I understand it can be difficult to merge it into stable15:05
ddieterlyo/15:05
rhochmuthi think we'll be allowed to do the merge in a couple of days15:06
rhochmuthso, we can cherry pick into the newton branch the relevant commit15:06
Trpger!get mirc15:06
rhochmuthand then update the tafs on the newton branch15:06
openstackTrpger: Error: "get" is not a valid command.15:06
rhochmuthwill that resolve the problem?15:07
witekif that will be possible, then it shouldn't be a problem15:07
witekyes, that should resolve the problem15:08
*** qwebirc90830 has joined #openstack-meeting-315:08
rhochmuthwitek: can you do the cherry pick to the newton branch?15:08
*** qwebirc90830 has quit IRC15:08
witekyes, should I wait until freeze is lifted?15:08
*** Trpger has quit IRC15:09
*** rnoriega has left #openstack-meeting-315:09
rhochmuthi think so15:09
witekok15:09
rhochmuthnote, this review for updating tags is also in progres, https://review.openstack.org/#/c/374361/15:09
rhochmuthfor monasca-statsd15:09
rhochmuthi think they will merge that review relatively soon15:10
rhochmuthafter that merge goes through then we can cherry-pick to monasca-statsd and update the tags15:10
rhochmuth:-)15:11
*** dkehn has joined #openstack-meeting-315:11
rhochmuthdoes that cover that topic?15:12
witekyes, thanks15:12
witekI just hope it works :)15:12
rhochmuthme too15:12
*** pcaruana has quit IRC15:13
rhochmuth#topic Status of openstack-ansible-os_monasca  role and merging fixes15:13
*** openstack changes topic to "Status of openstack-ansible-os_monasca  role and merging fixes (Meeting topic: monasca)"15:13
rhochmuthis someone here avaialble to discuss this topic?15:13
haad1yeah15:13
rhochmuthhi haad115:13
haad1so for me there are couple questions here15:13
haad1hi15:13
rhochmuthare you working on this?15:14
rhochmuthor just have questions15:14
rhochmuthi'm not involved in this effort15:14
haad1yeah I would like to as I have to deploy monasca with ansible anyway15:14
*** salv-orl_ has quit IRC15:15
rhochmuthhhad1: you have the floor15:15
rhochmuthhaad1: sorry, got your name wrong15:15
haad1so what do we want to do with this role15:15
haad1install + configure whole monasca + backend15:15
rhochmuththat would be nice15:16
*** tonytan4ever has quit IRC15:16
haad1my suggestion would be to split it into multiple roles15:16
haad1as that would be much more usable15:16
rhochmuthare you working on a single node depoly or multiple nodes15:16
rhochmuthclustered or non-clustered15:17
*** tonytan4ever has joined #openstack-meeting-315:17
haad1we are doploying it on multiple nodes15:17
*** armax has joined #openstack-meeting-315:17
haad1api/notification/thresh on couple + backend on other15:17
rhochmuthok, so what we've done in the past is create a role for every component15:17
rhochmuthmysql, influxdb, zk, kafka, storm15:18
rhochmuththose are the based shared services15:18
rhochmuthyou already have roles for mysql i'm sure15:18
rhochmuthbut probably not the others15:18
rhochmuththen i would create roles for monasca-api, monasca-persister, ...15:18
haad1so what I did in my pull request is that I have added support for deploying backend services with this role15:18
haad1and would add api services in other one15:19
rhochmuthi'm not an ansible expert15:19
haad1ok and how I would make them available to community as monasca roles for deployment ?15:20
haad1My plan wat to change existing openstack roles to help others15:20
rhochmuthi tend to think of each compnent as a micro-service that can be deployed independently15:21
rhochmutheach component with it's own role15:21
haad1yeah that's why I think current approach is not optimal at all15:21
haad1http://docs.openstack.org/developer/openstack-ansible-os_monasca/15:21
haad1using one mega role is not good15:21
haad1it should be per service15:21
rhochmuthwell, i don't think it is a terrible idea to have a single role15:22
rhochmutheither15:22
rhochmuthit depends on a lot of things15:22
*** ddieterly is now known as ddieterly[away]15:22
rhochmuthwe have written a lot of ansible roles a while ago, https://github.com/search?utf8=%E2%9C%93&q=ansible-monasca15:22
rhochmuthand had created a role for each component15:22
rhochmuththe down side is lot's of repos, roles, …15:22
rhochmuthbut, i still think a separate role for each repo/component is the optimal approach15:23
*** toddjohn has quit IRC15:23
haad1you can still have one wrapper role which will wrap all api services15:23
rhochmuthor better approach15:23
haad1to one role and then do the same for backend15:23
rhochmuthyes, that might be a good approach15:23
haad1ok so I can create those roles for newton branch as I have to update our deployment to newton anyway15:24
haad1but how can I get them under opentstack15:24
rhochmuthi'm not sure i understand the question15:25
*** david-lyle has quit IRC15:26
haad1how we can make them offical monasca roles under openstack15:26
*** ddieterly[away] is now known as ddieterly15:26
*** andreas_s has quit IRC15:27
rhochmuthunfortunately, i don't have much engagemnt with the openstack ansible project15:28
rhochmuthhave you submitted blueprints and reivewed/discussed with that project?15:28
*** dkehn has quit IRC15:28
haad1that would be my mistake I thought that this role is under monasca project15:29
haad1I will ping them tomorrow on their meeting15:29
haad1and see what happens15:29
rhochmuthok, so I was thinking that you were involved with that project already15:29
haad1ok thanks15:29
rhochmuththat explains the problem15:29
rhochmuthso the openstack ansible project is run by another team15:29
rhochmuthi'm hoping that they will want a monasca role15:30
rhochmuthi can't see why they wouldn't15:30
rhochmuthso, i think for guidance and process questions it will be best to follow-up with them15:30
*** _SarathMekala_ has quit IRC15:30
rhochmuthi will be glad to help15:30
rhochmuthalthough, when it comes to ansible/deployment i'm not the right guy to ask15:30
rhochmuthbut there are others invovled with monasca that do know a lot in this area15:31
*** galstrom is now known as galstrom_zzz15:31
rhochmuthso, they could help with reviews on the roles that you are creating15:31
*** vishwanathj has joined #openstack-meeting-315:31
rhochmuthso, should we move on?15:31
rhochmuthto the next topic?15:31
*** david-lyle has joined #openstack-meeting-315:32
pratidplease proceed15:32
rhochmuthalso, if the ansible openstack project needs or wants our involvmenet, then we can help15:32
rhochmuththx pratid15:32
rhochmuth#topic reviews15:33
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:33
rhochmuth#topic Reviews15:33
*** openstack changes topic to "Reviews (Meeting topic: monasca)"15:33
rhochmuth#topic https://review.openstack.org/#/c/379585/15:33
*** openstack changes topic to "https://review.openstack.org/#/c/379585/ (Meeting topic: monasca)"15:33
rhochmuthi'm waiting for gates to pass, then i'll check with craig, but it looks like this one is ready15:33
*** kashyap has left #openstack-meeting-315:34
rhochmuthrbak: u there?15:34
rbakThanks.  I was just trying to get eyes on that.15:34
rbakI don't have anything to add15:35
rhochmuthunless craig has any issues, looks like a merge15:35
rhochmuthawaiting any additional comments15:35
rhochmuthalso, as gates were down for a few days, didn't look at this15:35
*** numans has quit IRC15:36
rhochmuth#topic open floor15:36
*** openstack changes topic to "open floor (Meeting topic: monasca)"15:36
rhochmuthi think that completes the formal agenda15:36
rhochmuthif anyone has any additional topics that they would like to discuss, then the floor is open15:37
rhochmuthwe have about 20 minutes15:37
pratidi'd like to include15:37
pratidthis review for next meeting15:37
pratidhttps://review.openstack.org/#/c/374204/15:37
pratidabout but https://bugs.launchpad.net/monasca/+bug/162557315:37
openstackLaunchpad bug 1625573 in Monasca "monasca-setup does not support service_type & endpoint_type for Keystone Catalog" [Undecided,Fix committed] - Assigned to Pablo Rodriguez (pratid)15:37
*** jlanoux has joined #openstack-meeting-315:37
rhochmuthpratid: sounds good, please add to the agenda15:38
*** gouthamr has quit IRC15:38
pratidcould I15:38
pratidcould I?15:38
rhochmuthalso, i'll try and review over the next few days15:38
rhochmuthpratid: the agenda is posted at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda, and is open for anyone to add too15:38
pratidgood, i'll do15:38
pratiddidn't know about the procedure, sorry15:39
rhochmuthnp15:39
rhochmuthi've just added a spot for next week15:39
*** baoli has joined #openstack-meeting-315:39
pratidthx15:39
rhochmuthI just added your review15:40
rhochmuthso you shoudl be all set for next week15:40
rhochmuthalso, if we get enough review comments this might be addressed by next week15:40
pratidperfect15:41
rhochmuthit looks like joe keen had some comments on that review15:41
*** chandanc has quit IRC15:41
pratidyes, and i added some comments in reply15:41
pratidi'd like to revisit this issue15:42
*** paul-carlton2 has quit IRC15:42
rhochmuthok, i'll take a look15:42
rhochmuthand ping joe15:42
*** jlanoux_ has joined #openstack-meeting-315:42
*** mhoppal has joined #openstack-meeting-315:42
*** zhenguo has quit IRC15:43
pratidnothing else from my side15:43
rhochmuthpratid: thx15:43
rhochmuthare there other topics to discuss15:43
rhochmuthi should mention i'm trying to put the monasca agenda together for the summit15:44
rhochmuthbut it mainly some of the areas that we've discussed/mentioned already15:44
*** haad1 has left #openstack-meeting-315:44
rhochmuthi should mention that there is a backlog of reviews15:45
rhochmuthrbak: if we merged the changes for the names, dimensions names and dimension values15:45
*** gouthamr has joined #openstack-meeting-315:45
*** jlanoux has quit IRC15:45
rhochmuthdo you think you could complete the grafana changes15:45
*** salv-orlando has joined #openstack-meeting-315:45
rhochmuthor, the other way to look at this, can you complete all the grafana work first15:45
rhochmuththen give us a thumbs up15:45
rhochmuththen we can merge the api changes and your grafana changes more or less at the same time15:46
rhochmuthi'm just worried about downtime15:46
rbakI can do the grafana changes any time15:46
rbakThey shouldn't be difficult15:46
rhochmuthcool15:46
rhochmuthi think it is ready15:46
rhochmuthwe've been holding off with final reviewes and merges due to newton release15:46
rhochmuthill check with kaiyan and others, but i think it is good to go15:47
rhochmuthso, if you complete grafana work, then we can merge, and hopefully very little downtime15:47
*** Swami has quit IRC15:47
rhochmuthi think we can start merging to master after oct 6th15:48
rhochmuthassuming the origianl schedule holds15:48
*** caboucha has joined #openstack-meeting-315:49
witek7th15:49
rhochmuththx witek15:49
*** catherine_d|1 has joined #openstack-meeting-315:49
rhochmuthalso, i tried out xenial again this morning15:49
rhochmuthit is going further than the last time i tried15:49
rhochmuthso the big issue i beleive has been resolved in merged in the virtual box image15:50
rhochmuthbut, it didn't complete15:50
rhochmuthi think i ran into problems with openjdk715:50
rhochmuthbut, i didnt' get a thorough look15:50
rhochmuthhad to run15:50
rhochmuthonce xenial support merged, that will open up several other reviews to merge15:51
rhochmuth.15:53
*** yamamoto has joined #openstack-meeting-315:53
shinya_kwbt big issue i beleive has been resolved in merged in the virtual box image that is good15:53
rhochmuthother topics/updates/requests15:53
*** gouthamr has quit IRC15:53
*** david-lyle has quit IRC15:53
rhochmuththx shinya_kwbt15:53
rhochmuthyes, it went further15:53
rhochmuthbut still some problems, that i wasn't sure about15:54
*** gouthamr has joined #openstack-meeting-315:54
shinya_kwbtI also want to try but I cant do that now sorry. I'm in business trip.15:54
*** matrohon has quit IRC15:54
rhochmuthare you in barcelona already?15:54
shinya_kwbtOh no. I'm not rich haha15:55
shinya_kwbtI'm in tokyo now.15:55
rhochmuthhopefully, i'll get another look later today at xenial15:55
witekI think Tokyo is more expensive :)15:55
rhochmuthmaybe i'll even be able to figure it out15:55
rhochmuthok, sounds like we are wrapping-up for today15:56
shinya_kwbtwitek: Yes. hotel is very small and expensive!15:56
rhochmuthi'm going to end the meeting15:56
*** brunssen has joined #openstack-meeting-315:56
pratidbye15:56
rhochmuthbye15:56
*** cbellucci has quit IRC15:57
witekthanks, bye15:57
Kamil__bye15:57
shinya_kwbtthx bye15:57
kojithanks15:57
*** koji has quit IRC15:57
*** Kamil__ has quit IRC15:57
*** vhoward has quit IRC15:57
*** pratid has quit IRC15:57
rhochmuth#endmeeting15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Wed Oct  5 15:57:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
*** shamail has joined #openstack-meeting-315:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-10-05-15.01.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-10-05-15.01.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-10-05-15.01.log.html15:57
*** hosanai has quit IRC15:57
*** Fdaisuke has quit IRC15:58
*** Sukhdev_ has joined #openstack-meeting-315:59
*** tonytan4ever has quit IRC15:59
*** tonytan4ever has joined #openstack-meeting-316:00
*** gema has joined #openstack-meeting-316:00
*** claudiub has joined #openstack-meeting-316:00
markvoelker#startmeeting defcore16:00
openstackMeeting started Wed Oct  5 16:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
eglute_so/16:00
openstackThe meeting name has been set to 'defcore'16:00
catherine_d|1o/16:00
markvoelker#link https://etherpad.openstack.org/p/DefCoreLunar.21 Today's Agenda16:00
*** mhoppal has quit IRC16:01
shamailHi everyone16:01
markvoelker#chair eglute_s hogepodge16:01
*** witek has left #openstack-meeting-316:01
openstackCurrent chairs: eglute_s hogepodge markvoelker16:01
hogepodgeo/16:01
brunsseno/16:01
GheRiveroo/16:01
*** yamamoto has quit IRC16:01
Rockygo/16:01
*** rhochmuth has left #openstack-meeting-316:01
markvoelkerHi everyone.  Just a few weeks until Barcelona left!  Let's get to it...16:02
eglute_sshould we be in 20 not 21?16:02
*** bklei has quit IRC16:02
gemao/16:02
markvoelkereglute: 20 was last week, no?16:02
eglute_si thought it was 19 last week16:02
markvoelkerHeh...both pads show the same date16:02
*** bklei has joined #openstack-meeting-316:03
eglute_si created 20 yesterday but didnt change the date16:03
eglute_smy bad16:03
markvoelkerAh, ok then.16:03
markvoelker#link https://etherpad.openstack.org/p/DefCoreLunar.20 Today's Agenda (for real this time)16:03
markvoelker#topic 2017.01 Guideline16:04
*** openstack changes topic to "2017.01 Guideline (Meeting topic: defcore)"16:04
markvoelkerIf folks could take a quick moment to update their status on the etherpad there please...16:04
eglute_sdone...16:04
eglute_sI would like to talk about Ceilometer!16:05
*** ccamacho is now known as ccamacho|willbeb16:05
markvoelkereglute_s: the floor is yours16:05
*** VW has joined #openstack-meeting-316:05
*** ccamacho|willbeb is now known as ccamacho|willbbc16:05
eglute_sI talked to the PTL of telemetry, and as my notes indicate, there are a couple issues16:05
*** ccamacho|willbbc is now known as ccamacho|wllbbck16:05
*** VW has quit IRC16:05
eglute_sthe major one is that they are deprecating Ceilometer API16:05
*** atuvenie has quit IRC16:05
*** Sukhdev_ has quit IRC16:06
eglute_s#link http://lists.openstack.org/pipermail/openstack-dev/2016-October/105042.html16:06
*** baoli has quit IRC16:06
Rockygyup.  That's why it's interesting16:06
markvoelkereglute_s: has that been decided?  I lost the thread yesterday in a barage of meetings and haven't caught up yet.16:06
eglute_sif there is no API for it, I don't think we can include it in defcore16:06
*** VW has joined #openstack-meeting-316:06
eglute_sthe PTL sounded pretty sure that it has been decided16:06
eglute_sbut, reading the email, seems like it might be still up for discussion16:07
*** bklei has quit IRC16:07
markvoelkerOk.  The basic idea there was that Ceilometer had basically been decomopsed into Aodh/Panko/Gnocchi.  Those are currently not tc-approved-release.16:08
Rockygthey've been talking abour it for a while16:08
markvoelkerWas the PTL aware that we can't consider projects that aren't tc-approved-release?  Are they interested in getting the decomposed projects tagged?16:08
eglute_si told him we cant consider it if there are no APIs16:09
*** rbak has quit IRC16:09
eglute_she didnt seem to be interested in defcore, though he was very helpful16:09
catherine_d|1Even with the new APIs ... we still need to wait for adoption and tests to mature?16:10
shamailMy take was that it is still up for discussion after heat auto-scaling was brought up16:10
eglute_sadditionally, ceilometer's tests are in tempest plugin16:10
eglute_sshamail i do hope it will be discussed more16:10
RockygI think they are more focused on getting everything lined up and in good shape without ceilometer16:10
eglute_sthough at this point, since it's future is uncertain, i do not think we should push it forward with scoring16:11
hogepodgeI'm not so worried about plugins, as we can work on moving tests over if they're good candidates.16:11
catherine_d|1don't think it is a good candidate for interop if the project itself does not seem to be stable16:11
Rockyggood to wait until at least next cycle16:11
eglute_scatherine_d|1, Rockyg i agree16:11
Rockygthey are doing good and importannt work, but it's still midflight16:12
markvoelkereglute_s: Agreed, but I think we should start evaluating a future path.  E.g. does it make sense to ask for tc-approved-release on some or all of the decomp projects, can tests for them be moved to tempest, etc.16:12
eglute_shogepodge PTL was willing to work on moving the tests, so not too much of an issue16:12
*** diga has quit IRC16:12
markvoelkerThe answer to all of those might be "no", but we should start that discussion sooner rather than later. =)16:12
eglute_smarkvoelker i think we should wait for the projects to settle. right now there is too much change going on there in my opinion...16:13
* markvoelker is also curious if heat autoscaling is going to eventually move to senlin, but that's another topic16:13
eglute_sfor the decomp projects, i think we need to wait to see how the adoption goes16:14
markvoelkerAre Aodh/Gnocchi/Panko listed in the user survey this time around?16:14
eglute_sand what the deprecated API will be replaced with, if it is in fact, deprecated.16:14
RockygAt last gnocchi and aodh are getting good adoption with other opnstack projcts16:15
markvoelkerSo, I think there's a couple of things here then.16:16
Rockygyup.16:17
markvoelkerFirst, let's see if we can talk to the user survey folks about making sure Aodh/Gnocchi/Panko get listed (so we can guage adoption down the line)16:17
eglute_si am looking at the survey now and only see Ceilometer16:17
markvoelkerSecond, obviously let's follow the decision around the old Ceilometer API16:17
*** rajinir has joined #openstack-meeting-316:17
markvoelkerThird, once that decision has been reached we should think about future potential paths for Ceilometer.16:18
Rockyganything on telemetry?16:19
eglute_sRockyg no telemetry either.16:19
markvoelkerE.g. it'd be a shame if they decide next week that Ceilometer goes away and Gnocchi/Aodh/Panko are the future, but nobody even starts work on porting tests or whatnot for six more months16:19
markvoelkerMake sense?16:19
Rockyg++16:20
eglute_smarkvoelker yes16:20
* gema sneaks out for dinner, will read logs later o/16:20
hogepodgeWhat would be nice is a telemetry api and all the projects could plug in to that. Would make our jobs easier.16:20
eglute_shogepodge ++16:20
eglute_sagree16:20
markvoelkerOk.  So eglute_s would you be able to handle those AI's for the moment?16:20
eglute_smarkvoelker yes, i don't think anything is immediate though16:21
markvoelkereglute_s: sure, mostly keeping abreast of things at the moment16:21
eglute_si guess user survey is more immediate. i will send some emails :)16:22
markvoelkerSounds good.  Thanks!16:22
markvoelker#action eglute_s to follow up with user survey folks about telemetry projects16:22
*** tonytan4ever has quit IRC16:22
hogepodge(speaking of user survey, newest data was just released)16:22
*** shamail_ has joined #openstack-meeting-316:22
markvoelker#action eglute_s will keep abreast of the Ceilometer API deprecation discussion16:23
markvoelkerOk, further discussion on Ceilometer?  Or shall we move on?16:23
eglute_shogepodge do you have a link?16:23
eglute_smove on!16:23
markvoelkershamail: around?16:24
shamail_Here!16:24
markvoelkerAnything to discuss on Cinder?16:24
shamail_Not much yet, I got guidance from yourself and hodgepodge on how to start with scoring... I will be reviewing third party sources tonight.  I have a meeting scheduled for Friday with the PTL16:25
markvoelkerOk, thanks16:25
shamail_I think I bit off more than I can chew for the first time helping but I'll get through it :)16:25
markvoelkerFor those not aware, Cinder may be a little interesting too...they revved the CURRENT API from v2 to v3 in Mitaka.16:26
*** woodster_ has joined #openstack-meeting-316:26
markvoelker(functionally the same, but with microversions...but v3 was completely undocumented until a few weeks ago, so adoption possibly not great right now...)16:26
markvoelkerAnything else on Cinder?16:27
*** ddieterly is now known as ddieterly[away]16:27
shamail_Not at the moment16:27
*** nkrinner is now known as nkrinner_afk16:27
markvoelkerOk, next up: Glance16:27
catherine_d|1markvoelker: the current Cinder tests in DefCore guideline is based on v2 right?16:28
hogepodgecatherine_d|1: right16:28
markvoelkerI've spoken with the PTL and should have a patch up today-ish.  Got delayed last week by a ridiculous pile of pre-summit stuff that's piling up.16:28
hogepodgeif it's just a microversion with guaranteed backwards compatibility, it may not be a problem16:28
*** shamail_ has quit IRC16:28
markvoelkerBarring objections I'll probably also be submitting a governance patch to add glance_store as tc-approved-release16:28
catherine_d|1I would imagine there will be a conf parameter to set v2 vs v3 just like Keystone in tempest.conf16:28
markvoelkerAnd then consider adding the non-driver bits of it as designated sections16:29
*** shamail_ has joined #openstack-meeting-316:29
Rockygsame for cindr except for possible additions16:29
* markvoelker switches back to Cinder for a moment since it seems I moved on too quickly16:29
*** mickeys has joined #openstack-meeting-316:29
*** ddieterly[away] is now known as ddieterly16:30
markvoelkerSo, one thing to bear in mind with Cinder is that 2017.01 will include Liberty (in whcih v3 didn't exist)16:30
catherine_d|1it tool us a cycle or two to drop v2 Keystone tests from the must-pass list .. I guess we will do the same for Cinder?16:30
catherine_d|1tool --> took16:30
*** yamamoto has joined #openstack-meeting-316:31
markvoelkerSo basically we'll need to consider how that transition will work and when/if we switch guidelines to v316:31
* catherine_d|1 API version change really does not help Interop16:31
* markvoelker sees he and catherine_d|1 are thinking along similar lines here16:31
Rockygyup.  api revs are bears16:32
markvoelkerAlso worth noting: there's nothing that says both API's can't be required in the same Guideline, so it's not like there has to be an either/or.  v2 is not DEPRECATED, it's SUPPORTED16:32
Rockygexactly16:33
markvoelkerBut I'll leave it to our Cinder point folks (hi shamail_ !) to come up with proposals to discuss.16:33
*** ociuhandu has quit IRC16:33
RockygI'm not sur we've even managd the nova tests for that all that wll.16:33
*** shamail_ has quit IRC16:33
*** shamail_ has joined #openstack-meeting-316:33
markvoelkerOK, anything else on Cinder?16:34
RockygWe've just let th nova team gnerate the tests as they see fit16:34
* markvoelker pauses a little longer this time16:34
hogepodgeit appears that v3 will be backwards compatible with v2 because microversions16:34
hogepodge(confirmed with cinder devs)16:34
shamail_I'll confirm when I meet16:34
shamail_Ah ok16:34
hogepodgeso this should not be a major issue for us. v3 should just work with interop tests16:34
catherine_d|1hogepodge: that is good news ..16:34
hogepodge(that's assuming the host api supports an early enough microversion, but that's the case with all microversion apis)16:35
markvoelkerMove on?16:36
hogepodgeyes16:36
Rockygyeah16:36
markvoelkerOk, back to Glance: see above.  Any questions there?16:37
*** sergio_nubeliu has joined #openstack-meeting-316:37
eglute_slooks good to me16:38
markvoelkerHearing none, let's move on to Heat.16:38
markvoelkercatherine_d|1: what's the word? =)16:38
catherine_d|1I added a summit session request to the Heat team after contact the PTL16:38
markvoelkerSounds like we're mostly in the same boat as last time where we don't have good tests in Tempest?16:38
*** jdwald has quit IRC16:38
*** MarkBaker has quit IRC16:39
catherine_d|1yes16:39
catherine_d|1basically need the Heat team to put priority to move the tests to Tempest16:39
*** yamamoto has quit IRC16:39
*** jlanoux_ has quit IRC16:39
catherine_d|1that all for Heat ..16:41
markvoelkerOk.  We may also want to discuss/think through whether the API alone is all we want to define capabilities for down the road.16:41
catherine_d|1Heat summit eitherpad https://etherpad.openstack.org/p/ocata-heat-sessions16:41
markvoelkerHeat's a little different than some projects in that we might want to define capabilities that test support for various resources in templates, for example.16:41
hogepodgeheat is kind of a funny case because the api doesn't do a whole lot, most of the action is in the templates with is heavily deployment dependent.16:41
markvoelkerhogepodge: exactly.16:42
markvoelkerI'll defer to catherine_d|1 on figuring out a proposal around how to deal with that though, since she's playing point and I have way too much on my hands as it is. =)16:43
catherine_d|1resources may not be capabilities that should be scope for interop ... but those ae discussion we can bring up16:43
*** iyamahat has quit IRC16:43
markvoelkerOk, anything else on Heat?16:43
hogepodgeit's the case for scenario testing16:43
hogepodgenothing more from me16:44
*** yamahata has quit IRC16:44
catherine_d|1that is it from me16:44
markvoelkerOk, moving on then16:44
markvoelkerNext up is Keystone16:44
markvoelkerLast week hogepodge asked for some help here, and I've sent an email to the PTL and started (barely) digging in to look for capabilities16:44
markvoelkerNot a lot to report here this week I guess, unless hogepodge has any updates16:45
markvoelkerAny questions/comments on Keystone?16:45
hogepodgeI don't, I can begin to look again next week. My backlog and lingering illness has buried me for the short term16:46
* markvoelker hopes hogepodge feels better soon and will continue to work on this too16:46
markvoelkerOk, time's short...let's move on to nova16:46
markvoelkershamail_: that's you again16:46
*** claudiub has quit IRC16:47
markvoelkeror shamail: whichever of you is actually Shamail today. =)16:47
markvoelkerLooks like you're meeting with the PTL tomorrow?16:47
*** bklei has joined #openstack-meeting-316:48
shamail_Hi, Nova is same status as Cinder.  I have a meeting scheduled with the PTL tomorrow.16:48
markvoelkerOk, thanks.  Anything else?16:48
shamail_I am going to be looking at sources tonight16:48
shamail_Yes, that's the plan (and hopefully go in prepared)16:48
markvoelkerOk.  If nothing further, let's move on to Neutron16:49
markvoelkerwhich is me again16:49
markvoelkerI spoke with the PTL and did some looking myself too.  The TC approved adding neutron-lib to tc-approved-release16:50
markvoelkerI have a scoring patch up here:16:50
markvoelker#link https://review.openstack.org/#/c/381393/ Neutron scoring patch16:50
markvoelkerThere's one additional capability I'm still looking at that's a bit more recent16:50
markvoelkerBut the existing patch there is pretty simple.16:50
*** MarkBaker has joined #openstack-meeting-316:51
markvoelkerHave a look and feel free to start discussing anytime16:51
*** ibmko has quit IRC16:51
markvoelkerQuestions/comments on Neutron right now?16:51
shamail_Not at the moment16:51
eglute_snot right now...16:51
markvoelkerOk then, on to Swift.  eglute_s: that's you!16:51
eglute_smarkvoelker should we wait to review your patch on neutron?16:51
notmynameoh hai16:51
markvoelkereglute_s: nah, go ahead and start commenting.16:52
eglute_snotmyname did a lot of work on swift!16:52
eglute_s#link https://gist.github.com/notmyname/102e4aba7084598638f47cee47f62bb116:52
*** ivar-lazzaro has joined #openstack-meeting-316:52
eglute_si have not had a chance to review it.16:52
*** shamail_ has quit IRC16:52
eglute_sonce I do, i will start scoring16:52
*** david-lyle has joined #openstack-meeting-316:52
eglute_si am sure i will need help with scoring16:52
notmynameplease work with me as you go through that. I'm happy to help clarify my intent, etc16:53
notmynamethere's some new things, yeah, but also som renames and better classifications for existing stuff16:53
eglute_snotmyname i will! and really appreciate your help16:53
markvoelkerCool.  Sounds like you and notmyname are making good progress.16:53
eglute_smostly notmyname yes, :)16:53
markvoelkerWhen do you think we can expect to see a patch up?16:53
eglute_shopefully by friday. I am swamped by some other things, so not sure how much time i will have today16:54
notmynameso, as an asside, something that the defcore team could produce that would be *super* helpful would be a script that lists current capabilites and tests (i wrote my own) and then correlates that with what's available in tempest (I did that part by hand)16:54
markvoelkerOk, I'll keep an eye out.  Remember, first rev doesn't need to be perfect, just needs to be enough to kickstart discussion in gerrit16:54
eglute_snotmyname can you share the scripts with us?16:55
markvoelkerI think catherined|2 did something like that a while back maybe?16:55
catherine_d|1yea I did that a few cycle ago ... strictly by name ... not very accurate ...16:56
notmynamethis is all I have https://gist.github.com/notmyname/586fab93aab607d36b2bc6861b638afb16:56
eglute_sthank you notmyname16:56
notmynamethe .sh is run from inside a tempest directory16:56
markvoelkerOk gang, down to the last couple of minutes unfortunately16:57
notmynamegives every test name found, what file it's in, and its idempotent id16:57
eglute_snotmyname that looks good!16:57
notmynamethen I used some nice features of sublime text to clean it up16:57
*** bklei has quit IRC16:58
notmynamethus resulting in the original gist i sent you (or that's what i used to do the capabilities correlation)16:58
markvoelkerCertainly worth looking over for folks who are still test hunting16:58
markvoelkerTwo quick notes before we have to close for today16:58
hogepodgenotmyname: I write that script all the time  :-D16:58
*** ddieterly is now known as ddieterly[away]16:58
markvoelker#topic Summit Planing16:58
*** openstack changes topic to "Summit Planing (Meeting topic: defcore)"16:58
*** galstrom_zzz is now known as galstrom16:58
markvoelker#link https://etherpad.openstack.org/p/DefCoreBarcelona Summit Planning pad16:58
markvoelkerIf you have any other topics, get them on that pad today.  We'll start hammering out the agenda shortly.16:59
markvoelkerAnd lastly16:59
markvoelker#topic RefStack Updates16:59
*** openstack changes topic to "RefStack Updates (Meeting topic: defcore)"16:59
markvoelker#link https://etherpad.openstack.org/p/refstack-ocata-summit RefStack Planning pad16:59
markvoelkerPlease take note of the RefStack pad and add topics if necessary17:00
markvoelkerAnd with that, we're all out of time17:00
markvoelkerOver to #openstack-defcore17:00
markvoelkerThanks!17:00
markvoelker#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
eglute_sthanks!17:00
openstackMeeting ended Wed Oct  5 17:00:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-10-05-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-10-05-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-10-05-16.00.log.html17:00
catherine_d|1could we discuss about the second item on #openstack-defcore?17:00
*** mjturek has joined #openstack-meeting-317:00
*** iyamahat has joined #openstack-meeting-317:01
*** bklei has joined #openstack-meeting-317:03
*** ddieterly[away] is now known as ddieterly17:03
*** jed56 has quit IRC17:05
*** kzaitsev_mb has quit IRC17:07
*** yamamoto has joined #openstack-meeting-317:08
*** paul-carlton2 has joined #openstack-meeting-317:09
*** tqtran has joined #openstack-meeting-317:10
*** VW has quit IRC17:11
*** jdwald has joined #openstack-meeting-317:12
*** sambetts is now known as sambetts|afk17:14
*** ddieterly is now known as ddieterly[away]17:15
*** baoli has joined #openstack-meeting-317:18
*** yamamoto has quit IRC17:18
*** anilvenkata has joined #openstack-meeting-317:18
*** catherine_d|1 has quit IRC17:18
*** shamail has quit IRC17:20
*** amotoki has quit IRC17:21
*** bklei has quit IRC17:21
*** yamahata has joined #openstack-meeting-317:22
*** VW has joined #openstack-meeting-317:23
*** ccamacho|wllbbck is now known as ccamacho17:23
*** cleong has quit IRC17:27
*** claudiub has joined #openstack-meeting-317:27
*** VW has quit IRC17:28
*** VW has joined #openstack-meeting-317:29
*** Swami has joined #openstack-meeting-317:30
*** bklei has joined #openstack-meeting-317:30
*** yamahata has quit IRC17:34
*** VW has quit IRC17:37
*** lpetrut has joined #openstack-meeting-317:37
*** gouthamr has quit IRC17:41
*** ociuhandu has joined #openstack-meeting-317:42
*** caboucha_ has joined #openstack-meeting-317:42
*** haleyb_ has joined #openstack-meeting-317:43
*** haleyb__ has joined #openstack-meeting-317:44
*** caboucha has quit IRC17:45
*** lpetrut has quit IRC17:46
*** yamamoto has joined #openstack-meeting-317:47
*** bklei has quit IRC17:47
*** VW has joined #openstack-meeting-317:51
*** vhoward has joined #openstack-meeting-317:55
*** spzala has quit IRC17:56
*** yamamoto has quit IRC17:56
*** VW has quit IRC17:57
*** lpetrut has joined #openstack-meeting-318:01
*** anilvenkata has quit IRC18:03
*** yamahata has joined #openstack-meeting-318:04
*** mtanino has quit IRC18:04
*** gouthamr has joined #openstack-meeting-318:06
*** ivar-laz_ has joined #openstack-meeting-318:07
*** ivar-lazzaro has quit IRC18:10
*** VW has joined #openstack-meeting-318:13
*** tqtran has quit IRC18:13
*** haleyb__ has left #openstack-meeting-318:14
*** ddieterly[away] has quit IRC18:15
*** sergio_nubeliu has quit IRC18:16
*** VW has quit IRC18:17
*** salv-orlando has quit IRC18:22
*** rossella_s has quit IRC18:22
*** bklei has joined #openstack-meeting-318:23
*** spzala has joined #openstack-meeting-318:24
*** caboucha_ has quit IRC18:24
*** david-lyle has quit IRC18:25
*** yamamoto has joined #openstack-meeting-318:25
*** VW has joined #openstack-meeting-318:26
*** haleyb_ has quit IRC18:30
*** ddieterly has joined #openstack-meeting-318:33
*** ivar-laz_ has quit IRC18:35
*** ivar-lazzaro has joined #openstack-meeting-318:35
*** yamamoto has quit IRC18:36
*** haleyb_ has joined #openstack-meeting-318:40
*** rbak has joined #openstack-meeting-318:40
*** bklei has quit IRC18:42
*** claudiub has quit IRC18:45
*** anilvenkata has joined #openstack-meeting-318:49
*** bklei has joined #openstack-meeting-318:49
*** Sukhdev has joined #openstack-meeting-318:51
*** bklei has quit IRC18:57
*** bklei has joined #openstack-meeting-318:58
*** VW has quit IRC18:58
*** haleyb_ has quit IRC19:02
*** matrohon has joined #openstack-meeting-319:02
*** galstrom is now known as galstrom_zzz19:02
*** bklei has quit IRC19:03
*** galstrom_zzz is now known as galstrom19:03
*** yamamoto has joined #openstack-meeting-319:04
*** marst has joined #openstack-meeting-319:04
*** tqtran has joined #openstack-meeting-319:09
*** VW has joined #openstack-meeting-319:10
*** vhoward has quit IRC19:12
*** yamamoto has quit IRC19:14
*** VW has quit IRC19:18
*** Sunkara has joined #openstack-meeting-319:20
*** ddieterly is now known as ddieterly[away]19:23
*** david-lyle has joined #openstack-meeting-319:23
*** VW has joined #openstack-meeting-319:26
*** ddieterly[away] is now known as ddieterly19:26
*** paul-carlton2 has quit IRC19:28
*** VW has quit IRC19:31
*** VW has joined #openstack-meeting-319:35
*** persia has quit IRC19:37
*** lazy_prince has quit IRC19:37
*** persia has joined #openstack-meeting-319:37
*** claudiub has joined #openstack-meeting-319:37
*** lazy_prince has joined #openstack-meeting-319:39
*** yamamoto has joined #openstack-meeting-319:44
*** Sunkara has quit IRC19:44
*** sdake has quit IRC19:45
*** ramya has joined #openstack-meeting-319:45
*** sdake has joined #openstack-meeting-319:46
*** kzaitsev_mb has joined #openstack-meeting-319:46
*** sunkara has joined #openstack-meeting-319:46
*** salv-orlando has joined #openstack-meeting-319:53
*** alexismonville has quit IRC19:53
*** alexismonville has joined #openstack-meeting-319:53
*** salv-orl_ has joined #openstack-meeting-319:54
*** yamamoto has quit IRC19:54
*** rdopiera has joined #openstack-meeting-319:54
*** tsufiev has joined #openstack-meeting-319:56
*** salv-orlando has quit IRC19:58
*** ddieterly is now known as ddieterly[away]19:58
*** ddieterly[away] is now known as ddieterly19:59
*** qwebirc41501 has joined #openstack-meeting-320:00
*** r1chardj0n3s has joined #openstack-meeting-320:00
r1chardj0n3s#startmeeting horizon20:01
openstackMeeting started Wed Oct  5 20:01:04 2016 UTC and is due to finish in 60 minutes.  The chair is r1chardj0n3s. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: horizon)"20:01
openstackThe meeting name has been set to 'horizon'20:01
david-lyleo/20:01
r1chardj0n3sHello all20:01
tsufievo/20:01
david-lylestop shoving20:02
r1chardj0n3sWell, I'd like to thank Dave and Timur for coming :-)20:02
r1chardj0n3s#topic Notices20:02
*** openstack changes topic to "Notices (Meeting topic: horizon)"20:02
rdopierahi20:02
qwebirc41501hello20:02
*** qwebirc41501 has quit IRC20:02
r1chardj0n3s#link https://etherpad.openstack.org/p/horizon-ocata-summit now has a schedule20:02
tsufiev:)))20:03
r1chardj0n3sI've grouped things into sessions that seem to make sense. Feedback is welcome, of course. And ordering can change, though I'd like to keep it stable within reasonable time before the summit.20:03
r1chardj0n3sHmm, I should note the times of each of the sessions on that pad too.20:04
*** galstrom is now known as galstrom_zzz20:05
r1chardj0n3s#action r1chardj0n3s to add time, location and session-specific etherpad links to the summit overview etherpad page20:05
r1chardj0n3s(let's see if I got that right ;-)20:05
r1chardj0n3sok... next thing I have is Project Teams Gathering20:06
r1chardj0n3s#link http://www.openstack.org/ptg is intended to replace mid-cycles - are we going to participate?20:06
r1chardj0n3sI need to know whether Horizon folks are happy to do that thing rather than have an independent mid-cycle20:06
david-lyleI think we should try it20:07
tsufievseems like a proper thing to do20:07
rdopieracan we skip the summits then?20:08
david-lylerdopiera, for most, that's the idea20:08
* tsufiev thinking is if Atlanta a 'cost-effective transportation hub'20:08
*** ociuhandu has quit IRC20:09
david-lylerdopiera, this summit is still design related, but starting with Boston, it will not have the design component20:09
rdopieradavid-lyle: I know that's the plan, but I'm a bit afraid that we will start going to both20:10
david-lyleso devs should go if they want to talk to users/customers/other devs who have come to talk to users/customers20:10
david-lylerdopiera, we already go to both20:10
r1chardj0n3sI concur with y'all - let's see how the PTG goes. I'll feed that back to the Foundation.20:10
*** lcastell_ has joined #openstack-meeting-320:10
rdopieradavid-lyle: I thought ptg is a new thing20:10
*** matrohon has quit IRC20:11
david-lylebut this is an attempt to reduce the need for most to go to both20:11
rdopieramakes sense20:12
r1chardj0n3sYeah, it'll be interesting to see how it goes.20:12
*** mickeys has quit IRC20:12
*** anilvenkata has quit IRC20:13
r1chardj0n3sThey're reducing our face-to-face time for planning and discussion to once per cycle. We'll have to come up with alternative methods of planning to fill that void, and I'm not sure what that'll look like.20:13
r1chardj0n3sOK, so the only other thing I have is to mention that RC3 is out and we’re looking to get 10.0.0 released this week from it.20:14
tsufievr1chardj0n3s, how is that different from what was before? IIRC, midcycle meetups were not organized by foundation...20:14
*** ibmko has joined #openstack-meeting-320:14
david-lyle10.0.1 right?20:14
*** ramya has quit IRC20:14
r1chardj0n3sdavid-lyle: no, 10.0.0 unless I'm horribly confused... 10.0.0 hasn't been released20:15
*** sunkara has quit IRC20:15
*** robcresswell has joined #openstack-meeting-320:15
r1chardj0n3sthe patch for newton final is https://review.openstack.org/#/c/380478/20:15
david-lyletsufiev, the midcycle weren't official, but a large number projects were using them20:15
*** lpetrut has quit IRC20:16
r1chardj0n3stsufiev: yes, we'll have to see how many projects end up having a "planning" meetup independently20:16
david-lyler1chardj0n3s, I'm jumping the gun20:16
tsufievdavid-lyle, I mean, the foundation isn't going to forbid us to hold midcycles, are they :)?20:16
robcresswelltsufiev: More that nobody will get approval to travel 6 times a year :)20:16
*** mickeys has joined #openstack-meeting-320:16
robcresswell(also hi, sorry for lateness)20:16
david-lyletsufiev, no, there are a few reasons for the reorg20:16
david-lyleallowing key devs to actually use the summit to interface with people other than devs20:17
david-lylereduce the overall travel burden on most devs20:17
robcresswellWe can also use the forum for mid-cycle style meetups. Thats even in the Forum description.20:17
david-lylebetter align releases and downstream consumers around summits20:17
r1chardj0n3sthe mid-cycle timing we used to have lines up with when the summit will run, so that's going to be difficult for some to manage20:17
robcresswellAs key people will all be there anyway.20:18
robcresswellJust read scrollback, I'm a +1 for PTG too.20:19
r1chardj0n3sthanks robcresswell20:19
tsufievwell, the future is going to come despite all our concerns, I think...20:19
david-lyletsufiev, what are the concerns?20:20
r1chardj0n3sI look forward to mid-cycling with y'all in Boston :-)20:20
tsufievdavid-lyle, that there might be not enough time for our interaction - as r1chardj0n3s mentioned20:21
r1chardj0n3swe've still not been told the exact format of the summit-located mid-cycles (I recall some folks indicating that they would be held "away" from the summit to reduce cost)20:22
robcresswellYeah, we can chat at the summit anyway. Its not banned, just wont be dedicated rooms for it. But the cores/ptls will hopefully be around, which is what the midcycles most consist of anyway.20:22
r1chardj0n3swe'll just have to see20:22
david-lyleI think PTG will the primary meeting for devs20:22
robcresswelldavid-lyle: yup20:22
r1chardj0n3sso the last thing I wanted to talk about was the low attendance at these meetings20:24
*** yamamoto has joined #openstack-meeting-320:24
ediardoo/20:24
rdopieraI have to admit that I often forget about them :(20:24
tsufievediardo, that was a proper timing ;) ^^20:24
r1chardj0n3sI'm going to send out a reminder email to the dev list20:24
r1chardj0n3s#action r1chardj0n3s to email openstack-dev reminding folks about the weekly IRC meeting20:24
r1chardj0n3swe'll see if that has any impact20:25
robcresswellr1chardj0n3s: You could try a courtesy reminder type thing like searchlight and others do20:26
ediardordopiera ;)20:26
r1chardj0n3sI think the timing of the meeting will mean that the large number of contributors we have in China won't be making it along (it's very much in the AM there)20:26
tsufievr1chardj0n3s, maybe the main reason is that people don't know what to expect from these meetings? I mean, if before people were coming to a meeting to push their feature, now they generally don't do it (maybe that just didn't work for them and they stopped trying)20:26
rdopieraI wonder if we could make the bot announce the meeting on the #openstack-horizon channel20:26
rdopierawhen it's starting20:26
* david-lyle recalls an APAC friendly time that was even less attended20:26
robcresswellSomething like this, to remind people: https://etherpad.openstack.org/p/search-team-meeting-agenda( about line 6)20:26
r1chardj0n3srobcresswell: I'm not familiar with the searchlight timing thing?20:27
robcresswellugh, misplaced '(' might break that link20:27
r1chardj0n3stsufiev: that's a good point20:27
david-lyler1chardj0n3s, same as TC meeting start20:27
david-lylejust a list of nics copied into room20:27
r1chardj0n3sdavid-lyle: yep, the APAC meeting time was a dud indeed20:27
ediardoLet's do an iOS app that reminds us wehave a meeting to attend20:27
david-lylesearchlight does in their team room too20:28
ediardoconnected to keystone20:28
tsufievo_O20:28
robcresswelltsufiev: Right, the old blueprint system and asking for approval in meetings seems to have died20:28
*** ociuhandu has joined #openstack-meeting-320:28
ediardok jk20:28
robcresswellone sec just moving, internet might fall over20:28
david-lyleTIL robcresswell routes the entire internet20:29
r1chardj0n3srobcresswell: ok, I'll see about finding out how that meeting reminder thing works20:29
ediardolol20:29
tsufievthen, dropping the integrated/incubated statuses (and a requirement to have a Horizon dashboard in a Horizon repo to be an integrated project) has certainly contributed to the downfall of interest to Horizon meetings20:30
* tsufiev thinks about Sahara20:30
r1chardj0n3s(though to be honest, I have a calendar on my desktop and the meeting is in it and I get reminders, it's not difficult...)20:30
david-lyletsufiev, I think there larger influences on that decreased interest20:30
*** zerick has joined #openstack-meeting-320:30
*** galstrom_zzz is now known as galstrom20:31
robcresswelldavid-lyle: Looks like the internet survived without me20:31
r1chardj0n3shttp://www.thewebsiteofdoom.com/new/wp-content/uploads/2012/12/internet.jpg20:32
tsufievdavid-lyle, like the containers thing :)?20:32
david-lyletsufiev, I'm happy to have a larger discussion, but not sure out meeting time is the best place to cover openstack macrotrends20:33
tsufievsure, not going to continue with off-topic discussion right now20:34
*** ddieterly is now known as ddieterly[away]20:34
*** yamamoto has quit IRC20:34
david-lyleI guess the point is, smaller meetings may become the norm20:34
robcresswellWe generally just use the meeting for announcements now20:34
robcresswellPreviously it was for bug/bp discussion20:35
*** brunssen has quit IRC20:35
robcresswellI think if we used bp approval then it might get more attention, but thats somewhat ignored now. People just throw up features and ping for reviews :)20:35
david-lylethe volume into the funnel has fallen20:36
david-lylewe've solved it20:36
r1chardj0n3swe're also in the end-of-cycle dead spot at the moment where we're kind of on pause getting the release out and before the summit when priorities are agreed to20:37
r1chardj0n3sso these few weeks are a bit weird anyway20:38
robcresswellYeah its normally quiet while people prep Ocata features and demos20:38
r1chardj0n3sso they can surprise us with theirthrowing up features and pinging for reviews, yes :-)20:39
* tsufiev grabs the microphone and promotes the Profiler commits :D20:39
*** ivar-laz_ has joined #openstack-meeting-320:39
r1chardj0n3stsufiev: yes! um, I had questions about that, which I forgot (because vacation)20:39
r1chardj0n3stsufiev: I'm a little hazy on the actual setup of the profiler - do I need to be running a MongoDB or something somewhere to make it work?20:40
tsufievunfortunately, yes20:40
tsufievotherwise you'll have to face the Ceilometer poor performance20:40
r1chardj0n3sit might be helpful to have some (hopefully simple) setup instructions for devs to follow to get that right20:41
tsufievosprofiler team might fix the ceilometer drivers in some distant future... but I won't bet a large sum on that20:41
robcresswellWe need to axe that panel20:41
robcresswellShould've done it last cycle20:41
tsufievhttps://review.openstack.org/#/q/status:open+project:openstack/horizon+branch:master+topic:bp/openstack-profiler-at-developer-dashboard20:42
robcresswell(the ceilometer panel I mean)20:42
tsufievinstructions are in the second patch, https://review.openstack.org/#/c/303514/20:42
tsufievr1chardj0n3s, ^^20:42
*** ddieterly[away] is now known as ddieterly20:42
r1chardj0n3sOK, so the issue then becomes how to test the first patch20:43
tsufievwe even made some preparations for profiling API calls made from Angular pages20:43
*** devananda is now known as devananda|afk20:43
*** ivar-lazzaro has quit IRC20:43
tsufievr1chardj0n3s, I may merge them if that makes things easier20:44
tsufiev1st + 2nd20:44
tsufievalways a tradeoff between the ease of reviewing vs. providing a fully demoable feature20:45
* tsufiev puts back the microphone20:46
r1chardj0n3sabsolutely, but I think it makes sense to be able to exercise the code before merging it, and we can't sensibly exercise the code in the 1st patch I think20:46
tsufievyep, that's true20:46
robcresswellOn the summit etherpad, are we starting with priorities?20:47
r1chardj0n3srobcresswell: that's the ordering at the moment, but it doesn't really make sense so that session will probably be the fourth.20:47
r1chardj0n3sWell, the priorities bit20:47
robcresswellcool20:47
robcresswellWait who +1'd rotten fruit20:48
david-lyle;)20:48
robcresswellI should've known...20:48
david-lyleyou should have20:48
r1chardj0n3sok, I think this meeting may have run its course. thanks all for coming!20:48
robcresswelloh20:49
robcresswello/20:49
r1chardj0n3s#endmeeting20:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:49
openstackMeeting ended Wed Oct  5 20:49:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-10-05-20.01.html20:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-10-05-20.01.txt20:49
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-10-05-20.01.log.html20:49
*** tsufiev has left #openstack-meeting-320:49
*** robcresswell has left #openstack-meeting-320:49
*** haleyb_ has joined #openstack-meeting-320:49
*** rtheis has quit IRC20:51
*** lblanchard has quit IRC20:53
*** rdopiera has left #openstack-meeting-320:54
*** haleyb_ has quit IRC20:55
*** ddieterly is now known as ddieterly[away]20:56
*** r1chardj0n3s has left #openstack-meeting-320:57
*** yamamoto has joined #openstack-meeting-321:02
*** ociuhandu has quit IRC21:04
*** ociuhandu has joined #openstack-meeting-321:13
*** yamamoto has quit IRC21:14
*** lpetrut has joined #openstack-meeting-321:21
*** ociuhandu has quit IRC21:22
*** ddieterly[away] is now known as ddieterly21:25
*** alexismonville has quit IRC21:25
*** marst has quit IRC21:28
*** yamamoto has joined #openstack-meeting-321:42
*** mtanino has joined #openstack-meeting-321:46
*** ddieterly is now known as ddieterly[away]21:47
*** marst has joined #openstack-meeting-321:48
*** yamamoto has quit IRC21:52
*** VW_ has joined #openstack-meeting-321:55
*** spzala has quit IRC21:57
*** lpetrut has quit IRC21:57
*** ddieterly[away] is now known as ddieterly21:58
*** VW has quit IRC21:59
*** VW_ has quit IRC22:00
*** alexismonville has joined #openstack-meeting-322:06
*** alexismonville has quit IRC22:12
*** warrenwang has joined #openstack-meeting-322:13
*** vishwanathj has quit IRC22:18
*** yamamoto has joined #openstack-meeting-322:21
*** rbak has quit IRC22:25
*** ivar-laz_ has quit IRC22:25
*** ivar-lazzaro has joined #openstack-meeting-322:25
*** spzala has joined #openstack-meeting-322:27
*** ddieterly has quit IRC22:29
*** yamamoto has quit IRC22:30
*** spzala has quit IRC22:32
*** hj-hpe has quit IRC22:33
*** warrenwang has quit IRC22:38
*** gouthamr has quit IRC22:41
*** kzaitsev_mb has quit IRC22:45
*** tellesnobrega has quit IRC22:54
*** yamahata has quit IRC22:57
*** lcastell_ has quit IRC22:59
*** yamamoto has joined #openstack-meeting-322:59
*** yamamoto has quit IRC23:02
*** yamamoto has joined #openstack-meeting-323:02
*** galstrom is now known as galstrom_zzz23:03
*** yamahata has joined #openstack-meeting-323:05
*** salv-orl_ has quit IRC23:07
*** ddieterly has joined #openstack-meeting-323:09
*** ddieterly has quit IRC23:09
*** sdague has quit IRC23:17
*** Sukhdev has quit IRC23:17
*** Sukhdev has joined #openstack-meeting-323:19
*** yamamoto has quit IRC23:20
*** markvoelker has quit IRC23:22
*** logan- has quit IRC23:28
*** kenji-i has joined #openstack-meeting-323:32
*** tellesnobrega has joined #openstack-meeting-323:34
*** logan- has joined #openstack-meeting-323:37
*** Swami has quit IRC23:46
*** david-lyle has quit IRC23:47
*** sdake has quit IRC23:48
*** megm_ has quit IRC23:51
*** megm has joined #openstack-meeting-323:54
*** gouthamr has joined #openstack-meeting-323:57

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