Wednesday, 2016-04-20

*** piet has quit IRC00:01
*** piet has joined #openstack-meeting-300:04
*** kzaitsev_mb has quit IRC00:06
*** ddieterly[away] is now known as ddieterly00:07
*** ddieterly is now known as ddieterly[away]00:09
*** baoli has quit IRC00:13
*** banix has quit IRC00:13
*** ddieterly[away] is now known as ddieterly00:14
*** sdake has quit IRC00:21
*** piet has quit IRC00:24
*** fawadkhaliq has joined #openstack-meeting-300:25
*** sdake has joined #openstack-meeting-300:25
*** alex_xu has quit IRC00:26
*** alex_xu has joined #openstack-meeting-300:27
*** pvaneck_ has quit IRC00:28
*** jaypipes has quit IRC00:30
*** banix has joined #openstack-meeting-300:34
*** sdake has quit IRC00:38
*** sdake has joined #openstack-meeting-300:38
*** yamamot__ has joined #openstack-meeting-300:39
*** mageshgv has quit IRC00:41
*** hoangcx has joined #openstack-meeting-300:42
*** hoangcx has left #openstack-meeting-300:42
*** tellesnobrega_af is now known as tellesnobrega00:44
*** doug-fish has quit IRC00:46
*** alex_xu has quit IRC00:47
*** tellesnobrega is now known as tellesnobrega_af00:48
*** doug-fish has joined #openstack-meeting-300:49
*** alex_xu has joined #openstack-meeting-300:49
*** tellesnobrega_af is now known as tellesnobrega00:50
*** lblanchard has quit IRC00:54
*** mtanino_ has joined #openstack-meeting-300:54
*** mtanino has quit IRC00:55
*** fawadkhaliq has quit IRC00:56
*** fawadkhaliq has joined #openstack-meeting-300:57
*** mtanino_ has quit IRC00:59
*** zz_dimtruck is now known as dimtruck01:02
*** kzaitsev_mb has joined #openstack-meeting-301:02
*** zhurong has joined #openstack-meeting-301:04
*** rossella_s has quit IRC01:04
*** rossella_s has joined #openstack-meeting-301:04
*** mickeys has joined #openstack-meeting-301:07
*** bpokorny has quit IRC01:07
*** tellesnobrega is now known as tellesnobrega_af01:09
*** Sukhdev has quit IRC01:11
*** mickeys has quit IRC01:13
*** ddieterly has quit IRC01:18
*** Sukhdev has joined #openstack-meeting-301:23
*** yamahata has quit IRC01:23
*** kzaitsev_mb has quit IRC01:25
*** zhurong has quit IRC01:29
*** zhurong has joined #openstack-meeting-301:29
*** tellesnobrega_af is now known as tellesnobrega01:33
*** lblanchard has joined #openstack-meeting-301:46
*** MarkAtwood has quit IRC01:48
*** ddieterly has joined #openstack-meeting-301:50
*** ddieterly is now known as ddieterly[away]01:51
*** lblanchard has quit IRC01:51
*** s3wong has quit IRC02:03
*** iyamahat has quit IRC02:04
*** tfukushima has joined #openstack-meeting-302:07
*** yamamot__ has quit IRC02:09
*** neiljerram has joined #openstack-meeting-302:17
*** sdake_ has joined #openstack-meeting-302:20
*** kzaitsev_mb has joined #openstack-meeting-302:22
*** banix has quit IRC02:23
*** sdake has quit IRC02:23
*** ddieterly[away] is now known as ddieterly02:25
*** Sukhdev has quit IRC02:26
*** ddieterly is now known as ddieterly[away]02:26
*** kzaitsev_mb has quit IRC02:27
*** absubram has joined #openstack-meeting-302:28
*** sdake_ has quit IRC02:36
*** tfukushima has quit IRC02:40
*** tfukushima has joined #openstack-meeting-302:41
*** sekrit is now known as CIA02:44
*** iyamahat has joined #openstack-meeting-302:44
*** amotoki has joined #openstack-meeting-302:44
*** stanzgy has joined #openstack-meeting-302:46
*** sdake has joined #openstack-meeting-302:48
*** fawadkhaliq has quit IRC02:53
*** yamamot__ has joined #openstack-meeting-302:56
*** xiaohhui has quit IRC03:21
*** kzaitsev_mb has joined #openstack-meeting-303:23
*** tfukushima has quit IRC03:26
*** ddieterly[away] has quit IRC03:27
*** tfukushima has joined #openstack-meeting-303:27
*** kzaitsev_mb has quit IRC03:28
*** bpokorny has joined #openstack-meeting-303:40
*** vtech has joined #openstack-meeting-303:58
*** doug-fish has quit IRC04:01
*** armax has quit IRC04:06
*** piet has joined #openstack-meeting-304:07
*** ekarlso has quit IRC04:11
*** andreaf has quit IRC04:11
*** bpokorny has quit IRC04:16
*** kaz has joined #openstack-meeting-304:19
*** piet has quit IRC04:19
*** piet has joined #openstack-meeting-304:20
*** andreaf has joined #openstack-meeting-304:21
*** toddjohn_ has joined #openstack-meeting-304:23
*** kzaitsev_mb has joined #openstack-meeting-304:25
*** ekarlso has joined #openstack-meeting-304:25
*** toddjohn_ has quit IRC04:28
*** fawadkhaliq has joined #openstack-meeting-304:28
*** kzaitsev_mb has quit IRC04:30
*** vtech has quit IRC04:30
*** piet has quit IRC04:34
*** markvoelker has quit IRC04:34
*** markvoelker has joined #openstack-meeting-304:35
*** sdake has quit IRC04:36
*** markvoelker has quit IRC04:40
*** lpetrut has joined #openstack-meeting-304:40
*** tfukushima has quit IRC04:50
*** numan_ has joined #openstack-meeting-304:52
*** piet has joined #openstack-meeting-304:54
*** numan_ has quit IRC04:56
*** numan_ has joined #openstack-meeting-304:56
*** mrmartin has joined #openstack-meeting-304:59
*** mrmartin has quit IRC04:59
*** yamamot__ has quit IRC04:59
*** Sukhdev has joined #openstack-meeting-305:00
*** neelashah has quit IRC05:01
*** doug-fish has joined #openstack-meeting-305:02
*** sverma has joined #openstack-meeting-305:03
*** rossella_s has quit IRC05:03
*** rossella_s has joined #openstack-meeting-305:04
*** yamamot__ has joined #openstack-meeting-305:05
*** doug-fish has quit IRC05:07
*** piet has quit IRC05:10
*** yamahata has joined #openstack-meeting-305:10
*** mickeys has joined #openstack-meeting-305:15
*** pgadiya has joined #openstack-meeting-305:16
*** mickeys has quit IRC05:19
*** emagana has quit IRC05:22
*** soichi has joined #openstack-meeting-305:24
*** bpokorny has joined #openstack-meeting-305:25
*** kzaitsev_mb has joined #openstack-meeting-305:26
*** anil_rao has joined #openstack-meeting-305:27
*** xiaohhui has joined #openstack-meeting-305:29
*** tfukushima has joined #openstack-meeting-305:29
yamamot__hi05:29
anil_rao#startmeeting taas05:29
openstackMeeting started Wed Apr 20 05:29:19 2016 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.05:29
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:29
*** openstack changes topic to " (Meeting topic: taas)"05:29
openstackThe meeting name has been set to 'taas'05:29
anil_raohi05:29
soichihi05:29
*** eliqiao_ is now known as eliqiao05:29
kazhi05:29
anil_rao#topic TaaS demo session in Austin05:29
*** openstack changes topic to "TaaS demo session in Austin (Meeting topic: taas)"05:30
anil_raoWere you able to download and see the demo recording?05:30
soichiyes05:30
soichii think the demo video is very nice!05:30
soichii'm happy that the TaaS dashboard works well in the demo05:30
anil_raoThanks. The TaaS dashboard looks very nice. :-)05:30
soichithank you05:31
*** kzaitsev_mb has quit IRC05:31
anil_raosoichi: I saw an email from you about the fact that the dashboard is ready to accept the network id param removal.05:32
soichiyes05:32
soichi#link: https://review.openstack.org/#/c/300383/305:32
anil_raoThanks for the link.05:33
soichii think we are ready to merge the fix to remove network_id05:33
anil_rao+105:33
kaz+105:34
anil_raokaz: I am sorry I wasn't able to try out the new patch as yet.05:34
kazno problem05:35
anil_raoI am wondering if that problem with the installation and the missing egg-info has been taken care of.05:35
anil_raoNot sure what it was though.05:35
kazI think these are different problems.05:36
anil_raoYes, I agree05:36
*** dimtruck is now known as zz_dimtruck05:36
anil_raoFor the longer term how do we plan to address the installation?05:36
*** sdake_ has joined #openstack-meeting-305:37
kazI will try to rebase for liberty dashboard.05:38
anil_raoThat would be great.05:38
yamamot__why liberty?05:39
reediphi, sorry05:39
yamamot__rather than mitaka or master?05:39
kazyes, newer version.05:39
reedipnewton would be a better option05:39
reedipkaz ^^05:39
soichireedip: +105:40
kaz+105:41
*** vtech has joined #openstack-meeting-305:41
anil_rao+105:42
anil_rao#topic TaaS meet up in Austin05:42
*** openstack changes topic to "TaaS meet up in Austin (Meeting topic: taas)"05:42
*** ihrachys has joined #openstack-meeting-305:42
*** zz_dimtruck is now known as dimtruck05:43
soichido you have any idea about date/time/place?05:44
anil_raoOpen to suggestions...05:45
yamamot__before or after the session?05:45
*** Poornima has joined #openstack-meeting-305:45
anil_raoOur session is late in the day on Thursday. :-(05:46
reedipjust a heads up, my VISA has been approved, but I am yet to get it ( maybe by Monday ..?)05:46
anil_raoAwesome!05:46
reedipso I might just be able to join :)05:47
yamamot__great05:47
anil_raoLet's just use email and organize something during the week.05:48
reedipYup05:48
soichiokay, sure05:48
kaz+105:49
*** vtech has quit IRC05:51
reedipanything else? its pretty quiet :)05:51
anil_rao#topic Open Discussion05:51
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"05:52
anil_raoWe should try and attend the design sessions on agent extension05:53
soichianil_rao: i think so, too05:54
reedipYup, and also the meeting for Large deployers05:54
*** ihrachys has quit IRC05:54
reedipwe can get some points from the operators and deployers meeting of what can be added in the roadmap05:54
anil_raoreedip: +105:55
yamamot__urls?05:55
reedipJust a minute05:55
*** luis5tb_ has joined #openstack-meeting-305:55
reedipSearching......05:56
*** bpokorny has quit IRC05:56
reediphttps://www.openstack.org/summit/austin-2016/summit-schedule/events/9515?goback=105:56
yamamot__thank you05:57
*** stendulker has joined #openstack-meeting-305:57
anil_raoQuestion about reedip's patch regarding tap-flow create05:58
reedip?05:58
yamamot__this one might be important for us.  https://www.openstack.org/summit/austin-2016/summit-schedule/events/9097?goback=105:58
anil_raoAre you going to break it up as yamamot__ was suggesting05:59
anil_raoyamamot__: Agree05:59
reedipI just saw the comment06:00
reedipyes I agree\06:00
reedipits doing too much06:00
reedipfor a small commit message06:00
reedipI will break it for easier review06:00
anil_raoSounds good. Thanks.06:00
yamamot__agent extension things belong to this  https://www.openstack.org/summit/austin-2016/summit-schedule/events/9113?goback=106:01
yamamot__are you talking about this? https://review.openstack.org/#/c/275017/06:02
*** eliqiao has quit IRC06:02
anil_raoYes06:02
*** lpetrut has quit IRC06:03
anil_raoWithout that patch the neutron client support for TaaS is broken. So it is important to get that in.06:03
yamamot__sure06:04
reedipthen check it tomorrow morning ( tonights its pretty late ) , I will update the patch :)06:04
anil_raoreedip: Sure. :)06:04
yamamot__we can't merge it until https://bugs.launchpad.net/neutron/+bug/1571486 is fixed anyway. :-)06:05
openstackLaunchpad bug 1571486 in networking-midonet "tempest jobs timout" [Critical,In progress] - Assigned to YAMAMOTO Takashi (yamamoto)06:05
yamamot__so no hurry06:05
anil_raoNo hurry, just that we shouldn't let it linger too long.06:05
yamamot__agree06:06
yamamot__is there any progress on bug triage permission tweak?06:06
anil_raoyamamot__: I will be talking to Vinay in the morning and will bring it up again. Somehow the permission setting can only be changed by him.06:07
yamamot__ok.  are you and vinay working closely?  (geographically)06:08
anil_raoNot really. He is in Sweden. I am in California.06:08
yamamot__i see06:09
*** eliqiao has joined #openstack-meeting-306:09
reediplol06:09
soichii have no additional topic06:12
*** JeanBriceCombebi has joined #openstack-meeting-306:12
anil_raoNext week's meeting is cancelled on account of the Summit06:12
yamamot__+106:13
anil_raoLook forward to meeting those of you who will be in Austin.06:13
soichisure06:13
kaz+106:13
anil_raoreedip: Don't forget to pick up your visa. :)06:13
reedipU think????06:14
reediphalf of my work is stuck because of it :D06:14
anil_raoThat should be it for today then.06:15
anil_rao#endmeeting06:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:17
openstackMeeting ended Wed Apr 20 06:17:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-04-20-05.29.html06:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-04-20-05.29.txt06:17
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-04-20-05.29.log.html06:17
anil_raoBye06:17
soichisee you in Austin!06:17
yamamot__bye06:17
kazbye06:18
*** soichi has left #openstack-meeting-306:18
*** anil_rao has quit IRC06:18
*** kaz has quit IRC06:19
*** neiljerram has quit IRC06:19
*** lpetrut has joined #openstack-meeting-306:22
reedipo/06:22
*** nelsnelson has quit IRC06:23
*** kzaitsev_mb has joined #openstack-meeting-306:24
*** anilvenkata has joined #openstack-meeting-306:24
*** dimtruck is now known as zz_dimtruck06:24
*** jlanoux has joined #openstack-meeting-306:29
*** vtech has joined #openstack-meeting-306:29
*** janice has joined #openstack-meeting-306:30
*** JeanBriceCombebi has quit IRC06:31
*** JeanBriceCombebi has joined #openstack-meeting-306:35
*** e0ne has joined #openstack-meeting-306:38
*** vtech has quit IRC06:38
*** lpetrut has quit IRC06:40
*** nkrinner has joined #openstack-meeting-306:40
*** JeanBriceCombebi has quit IRC06:41
*** e0ne has quit IRC06:43
*** e0ne has joined #openstack-meeting-306:44
*** e0ne_ has joined #openstack-meeting-306:45
*** e0ne has quit IRC06:48
*** e0ne_ has quit IRC06:50
*** kzaitsev_mb has quit IRC06:52
*** ccamacho has joined #openstack-meeting-306:53
*** wangbo has joined #openstack-meeting-306:57
*** matrohon has joined #openstack-meeting-307:02
*** banix has joined #openstack-meeting-307:04
*** Sukhdev has quit IRC07:04
*** vtech has joined #openstack-meeting-307:06
*** vtech has quit IRC07:07
*** vtech has joined #openstack-meeting-307:07
*** dedery has joined #openstack-meeting-307:09
*** Rockyg has quit IRC07:10
*** vgridnev has joined #openstack-meeting-307:11
*** jlvillal has quit IRC07:22
*** jlvillal has joined #openstack-meeting-307:22
*** melwitt has quit IRC07:23
*** kevinbenton has quit IRC07:23
*** bharathm has quit IRC07:25
*** zz_dimtruck is now known as dimtruck07:25
*** melwitt has joined #openstack-meeting-307:25
*** melwitt is now known as Guest1703307:25
*** kevinbenton has joined #openstack-meeting-307:26
*** emagana has joined #openstack-meeting-307:34
*** dimtruck is now known as zz_dimtruck07:34
*** tfukushima has quit IRC07:35
*** tfukushima has joined #openstack-meeting-307:37
*** scheuran has joined #openstack-meeting-307:37
*** ihrachys has joined #openstack-meeting-307:38
*** emagana has quit IRC07:38
*** bharathm has joined #openstack-meeting-307:41
*** jlanoux has quit IRC07:41
*** lpetrut has joined #openstack-meeting-307:44
*** fawadkhaliq has quit IRC07:45
*** fawadkhaliq has joined #openstack-meeting-307:45
*** banix has quit IRC07:48
*** andymaier has joined #openstack-meeting-307:50
*** dedery has quit IRC07:51
*** tfukushima has quit IRC07:52
*** PaulMurray has joined #openstack-meeting-307:53
*** robcresswell has joined #openstack-meeting-307:54
*** tfukushima has joined #openstack-meeting-307:56
*** r1chardj0n3s has joined #openstack-meeting-307:57
*** mickeys has joined #openstack-meeting-307:58
*** tsufiev has joined #openstack-meeting-307:58
*** ptm_away has joined #openstack-meeting-307:58
*** aarefiev_ has joined #openstack-meeting-307:59
*** luis5tb_ has quit IRC07:59
robcresswell##startmeeting horizon08:00
robcresswell#startmeeting horizon08:00
openstackMeeting started Wed Apr 20 08:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
robcresswellderp08:00
*** openstack changes topic to " (Meeting topic: horizon)"08:00
openstackThe meeting name has been set to 'horizon'08:00
r1chardj0n3so/ derp08:00
tsufievo/08:01
robcresswellQuiet meeting :)08:01
r1chardj0n3sso, who's excited about next week? :-)08:02
*** PaulMurray has quit IRC08:02
robcresswellThe summit schedule link is in the Horizon room topic; if you haven't seen it yet then https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Horizon%3A08:02
tsufievnot me :/08:02
*** fawadkhaliq has quit IRC08:02
r1chardj0n3sah, no :-(08:02
robcresswellr1chardj0n3s: Least tactful question ever08:02
robcresswellhaha08:02
r1chardj0n3sI am the worst08:02
*** mickeys has quit IRC08:03
r1chardj0n3sso, I have a patch up to integrate upper-constraints into our tox env08:03
r1chardj0n3swhich isn't merged, but would have saved us from novaclient shenanigans08:03
*** mickeys has joined #openstack-meeting-308:03
robcresswellI saw that. Its failing tests right now iirc08:03
tsufievanyways, I´m going to use the next week to do some good things in Horizon08:03
r1chardj0n3sand ironically it's failing now because david's novaclient compat patch landed, and we're not compatible with the old, upper-constraints pinned version of novaclient any longer :-)08:04
tsufievfor example, we almost made integration tests work for Angular content08:04
tsufievmore specifically, LI wizard08:04
r1chardj0n3s(I'm pretty sure that's why it's failing)08:04
robcresswellr1chardj0n3s: So, we need to pin our tests to a version of novaclient?08:04
r1chardj0n3stsufiev: an integration test for Swift UI would be awesome, since people just broke it grrrrrr08:04
tsufievr1chardj0n3s, ack08:05
robcresswellr1chardj0n3s: Yup. The bug report for that swift issue has the guilty patch I believe08:05
r1chardj0n3srobcresswell: actually, it might be that my patch needs to include a reversion of david's patch :/08:05
r1chardj0n3sor something compatibility work anyway08:05
r1chardj0n3srobcresswell: I've already put up a patch to fix the swift ui broeken08:05
robcresswellhttps://bugs.launchpad.net/horizon/+bug/156783008:05
openstackLaunchpad bug 1567830 in OpenStack Dashboard (Horizon) "“10 $digest() iterations reached” Error occur in ng-swift" [High,Confirmed]08:05
r1chardj0n3shttps://review.openstack.org/#/c/308129/08:06
r1chardj0n3shey, where's *my* autobot link?!08:06
r1chardj0n3sgrr08:06
mrungeo/08:06
mrungeno link for r1chardj0n3s08:06
robcresswellbugs get bots, not patches08:06
mrunge:P08:06
r1chardj0n3sanyhoo, the match that caused that bug wasn't compatible with the new "link" type in action-list08:06
r1chardj0n3sit was only being used in swift ui so I put up a patch that removes it08:06
*** mbound has joined #openstack-meeting-308:07
robcresswellNice08:07
robcresswellCould you tag that bug in it too, if it fixes it?08:07
r1chardj0n3sI like it less, but it works08:07
r1chardj0n3sI did08:07
*** zz_dimtruck is now known as dimtruck08:07
r1chardj0n3soh08:07
r1chardj0n3sno, I tagged a separate bug08:07
r1chardj0n3shttps://bugs.launchpad.net/horizon/+bug/157238608:07
openstackLaunchpad bug 1572386 in OpenStack Dashboard (Horizon) "Action list "link" actions broken after patch #295605" [Undecided,In progress] - Assigned to Richard Jones (r1chardj0n3s)08:07
r1chardj0n3sI didn't realise there was an existing bug (I did search, honest)08:08
*** mickeys has quit IRC08:08
robcresswellI'm just going to point out that its one of three bugs tagged "swift"08:08
robcresswell>.<08:08
r1chardj0n3ssee previous "I am the worst" :-)08:08
robcresswellhaha08:08
*** ccamacho has quit IRC08:09
robcresswellAnyway, if you could tag the other bug too (which would rerun tests anyway) that would be helpful08:09
r1chardj0n3syup08:09
robcresswellThanks r1chardj0n3s08:09
*** JeanBriceCombebi has joined #openstack-meeting-308:10
robcresswelltsufiev: So we nearly have angular integration tests?08:10
tsufievrobcresswell, nearly - yes, I like the word :)08:10
r1chardj0n3s:-)08:10
robcresswellGreat news08:10
r1chardj0n3sI have a few folks who are chipping in on the integration test side of things, so I might encourage them in that direction...08:11
tsufievI guess, we may have a working test for NG LI by the start of the summit08:11
robcresswellOh, one thing I should mention; given the number of people leaving Horizon, our stable-maint team is extremely light right now. If you have any interest in backporting, please help review or propose patches08:12
tsufievhopefully, doug-fish will stop looking then towards JS based integration tests :)08:12
robcresswell:)08:13
robcresswellWe have an open agenda, so if there are any topics to be discussed feel free08:14
robcresswellotherwise we can just end early08:14
tsufievI would keep reminding about AVAILABLE_REGIONS renaming, but I guess that the target audience is in another TZ08:15
*** ccamacho has joined #openstack-meeting-308:16
robcresswellYeah I think you'll get more attention in the later meeting if you're around08:16
robcresswellotherwise I can bring it up08:16
tsufievrobcresswell, I´m going to attend another meeting as well08:17
tsufievah, another thing08:17
*** dimtruck is now known as zz_dimtruck08:17
tsufievin the patch https://review.openstack.org/#/c/279573/ a point was raised that we need unit-tests which pass both for py2 and py308:17
*** luis5tb_ has joined #openstack-meeting-308:18
tsufievwhich doesn´t seem entirely reasonable to me, because there is no way to run Horizon with py308:18
tsufievor there is?08:18
tsufievr1chardj0n3s, it´s about unicode and py3, in case you´re interested08:19
r1chardj0n3sah, ok08:19
robcresswellSo there's an openstack-wide effort to support py3. Given the scale of the work, its unfair for projects to suddenly regress on py3 support.08:19
robcresswellSo I don't believe it is an unfair expectation, personally08:19
r1chardj0n3swhich is actually hilarious because I'm getting poorly-encoded characters in IRC from you at the moment tsufiev ;-)08:19
r1chardj0n3s"itŽs"08:19
tsufievlol08:20
robcresswellHuh. The only weird chars I saw was from pkarikh doing copy paste, irssi was going nuts.08:20
r1chardj0n3sI'll have a look at that patch tomorrow, if that's OK?08:20
tsufievr1chardj0n3s, sure08:20
robcresswellIts a pain to work around, but we should maintain the py3 UT support so that the python 3 guys can move forward :)08:21
tsufievdid not know that the special backtick my keyboard generates is in unicode :O08:21
*** ccamacho has quit IRC08:21
tsufievrobcresswell, what if I skipped these tests explicitly if py3 env was detected :)?08:21
*** luis5tb_ has quit IRC08:21
robcresswellIf py3: pass08:22
*** jlanoux has joined #openstack-meeting-308:22
*** luis5tb_ has joined #openstack-meeting-308:22
r1chardj0n3s_ = string.upper08:22
tsufievvolkswagen lib for py3 ;)08:22
robcresswellha!08:23
robcresswellI forgot about that08:23
*** dtardivel has joined #openstack-meeting-308:23
robcresswelltsufiev: I believe the general advice from r1chardj0n3s re: unicode is to aritrarily throw in encode and decode statements until it works.08:23
robcresswelleven better if you use the oslo safe_* functions08:24
r1chardj0n3srobcresswell: you know we're going to be in the same physical space next week, right? and someone recently encouraged me to work on my right hook...08:24
robcresswellhaha08:24
*** dosaboy_ is now known as dosaboy08:24
tsufievrobcresswell, that is almost what I did... but let us wait until r1chardj0n3s says his expert ju08:24
tsufiev*makes his expert judgement on that patch08:25
r1chardj0n3sdid you see how many people agreed with my proposal to remove safe_encode and safe_decode ... on twitter?08:25
r1chardj0n3stotes makes it a solid proposal08:25
* tsufiev does not follow twitter much08:26
*** vgridnev has quit IRC08:26
robcresswellWho'd have thought the best way forward for discussion is to limit everyone to 3 lines at a time.08:26
r1chardj0n3s"best" hmmm ;-)08:27
tsufievbecase that leaves no space for objections :)08:27
robcresswellIdk, people are very good at objecting to things on twitter08:27
*** toddjohn_ has joined #openstack-meeting-308:28
robcresswellIt would be good to deprecate it though08:28
*** mickeys has joined #openstack-meeting-308:28
r1chardj0n3sindeed08:28
robcresswellRight, anything else?08:29
robcresswellRemember there will be no meetings next Wednesday due to Summit.08:29
robcresswellThanks all08:30
robcresswell#endmeeting08:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:30
openstackMeeting ended Wed Apr 20 08:30:55 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:30
r1chardj0n3so/08:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-04-20-08.00.html08:30
*** ptm_away has left #openstack-meeting-308:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-04-20-08.00.txt08:31
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-04-20-08.00.log.html08:31
*** r1chardj0n3s has left #openstack-meeting-308:31
*** tsufiev has left #openstack-meeting-308:31
*** janice has quit IRC08:32
*** toddjohn_ has quit IRC08:32
*** mickeys has quit IRC08:33
*** luis5tb_ has quit IRC08:33
*** robcresswell has left #openstack-meeting-308:37
*** neiljerram has joined #openstack-meeting-308:38
*** JeanBriceCombebi has quit IRC08:41
*** luis5tb_ has joined #openstack-meeting-308:55
*** luis5tb_ has quit IRC08:56
*** ccamacho has joined #openstack-meeting-308:57
*** janice has joined #openstack-meeting-308:59
*** david-lyle has quit IRC08:59
*** david-lyle has joined #openstack-meeting-309:00
*** alexey_weyl has joined #openstack-meeting-309:00
*** ifat_afek has joined #openstack-meeting-309:00
ifat_afek#startmeeting vitrage09:00
openstackMeeting started Wed Apr 20 09:00:50 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
alexey_weylHello09:00
*** idan_hefetz has joined #openstack-meeting-309:01
ifat_afekHi everyone :-)09:01
idan_hefetzHi09:01
janicehi09:01
*** eyalb has joined #openstack-meeting-309:01
eyalbhi09:01
*** elisha_r has joined #openstack-meeting-309:01
elisha_rhey09:01
*** yhabushi has joined #openstack-meeting-309:02
yhabushihi09:02
ifat_afekWe will have a short meeting today, and focus on the preparations for Austin09:02
ifat_afek#topic Austin preparations09:02
*** openstack changes topic to "Austin preparations (Meeting topic: vitrage)"09:02
ifat_afekLinks to Vitrage sessions in Austin:09:03
ifat_afek#link https://www.openstack.org/summit/austin-2016/summit-schedule/events/817709:03
ifat_afek#link https://www.openstack.org/summit/austin-2016/summit-schedule/events/896309:03
ifat_afekIn addition, Vitrage-Aodh integration will be discussed in Telemetry design session on Thursday at 16:10:09:03
ifat_afek#link https://www.openstack.org/summit/austin-2016/summit-schedule/events/920309:03
ifat_afekRegarding Vitrage status: we are in a code freeze, all critical bugs were fixed09:04
ifat_afektoday or tomorrow we will try to tag Vitrage first release :-)09:04
yhabushiGreat !!09:04
ifat_afekLet’s review our action items from last week:09:04
ifat_afek• elisha_r Getting Started Guide09:04
idan_hefetzAy caramba!09:05
elisha_rThe guide is in.09:05
ifat_afek• idan_hefetz aodh notifier09:05
idan_hefetzYea, the aodh notifier is already in09:06
*** eddie_lechtus has joined #openstack-meeting-309:06
ifat_afek• ifat_afek check vitrage meeting time09:06
ifat_afekI did not handle it yet. Next week there will be no meeting, and I hope to reschedule the meeting until the week after it.09:06
ifat_afek#action ifat_afek reschedule vitrage meeting09:06
idan_hefetzsince we have a stable version i'll commit a few additions after austin :)09:06
ifat_afekidan_hefetz: cool, thanks09:06
ifat_afek• ifat_afek aodh get all09:07
ifat_afekI finished coding and manually testing, still need to write some unit tests09:07
ifat_afek#action ifat_afek write aodh unit tests09:07
ifat_afek• danoffek List of default Templates + testing09:07
*** yhabushi has left #openstack-meeting-309:07
*** aviramb has joined #openstack-meeting-309:07
*** zz_dimtruck is now known as dimtruck09:08
*** Poornima has quit IRC09:08
*** danoffek has joined #openstack-meeting-309:08
danoffekUpdating about the templates :09:08
danoffekAdded locally the templates, but didn't finish testing before code freeze. Will commit after Austin on next version.09:09
ifat_afek• eddie_lechtus Aodh – Installation requirements testing + How to install without Aodh09:09
*** Poornima has joined #openstack-meeting-309:09
*** Poornima has quit IRC09:10
eddie_lechtushave tested the installation without aodh. found a bug regatds nova notifications that is currently fixed09:10
ifat_afekeddie_lechtus: thanks. anything else?09:11
ifat_afek• GuyA Entity graph, including Cinder data, changing the tabs order09:11
eddie_lechtusI want to test the ceilometer alarms but my installation failing. Eyal is taking a look. root over09:11
ifat_afekupdating on behalf of GuyA: he finished the entity graph09:12
ifat_afekeddie_lechtus: thanks again09:12
*** eddie_lechtus has quit IRC09:12
ifat_afek• aheller UI Bug fixes, improvements and auto refresh09:12
ifat_afekupdating on behalf of aheller: he finished his UI fixes09:12
*** vgridnev has joined #openstack-meeting-309:12
*** Poornima has joined #openstack-meeting-309:12
*** nbloom has joined #openstack-meeting-309:13
ifat_afek• pip install09:13
*** sambetts|afk is now known as sambetts09:14
*** ccamacho has quit IRC09:15
nbloomUnder project-config, added publish to PyPi jobs for vitrage-client, vitrage and vitrage dashboard. Registered the three in PyPi. Once we tag a release, and updated distribution should get published to PyPi which will allow for pip installing our project09:15
*** iyamahat has quit IRC09:15
ifat_afek• nbloom Run Vitrage tempest tests in the gate09:15
*** bharathm has quit IRC09:17
*** dimtruck is now known as zz_dimtruck09:17
nbloomIn progress, the vitrage tempest Jenkins job has been successfully added to the Experimental pipeline of openstack/vitrage project. I ran a check yesterday and the running of the testing script failed due to permissions. I fixed it yesterday and it has been merged, I ran check again yesterday and current situation is that the script runs and I can09:18
nbloomsee testr logs yet their empty so there's still some problem.. I will look into it as I'll have time.09:18
ifat_afeknbloom: great, thanks09:18
ifat_afek• alexey_weyl Tempest - Support more templates (RCA + Leftovers)09:18
alexey_weylHaven't got the time to handle this action, because I am busy with the Austin summit preperations09:19
ifat_afek• add blueprints for Newton09:19
ifat_afeknot done yet09:19
ifat_afek#action add blueprints for Newton09:19
ifat_afekdone with the action items :-)09:20
ifat_afekAnyone has some other updates?09:20
*** bharathm has joined #openstack-meeting-309:21
danoffekWe have 4 demo setups for the Austing summit / pre-summit. 2 are fully installed, and we're doing final training.09:22
danoffekIt seems we are pretty much set  to go :)09:22
ifat_afekdanoffek: cool!09:23
ifat_afekmoving on09:23
ifat_afek#topic Open Discussion09:23
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:23
ifat_afekAnything you would like to discuss?09:23
janicehi, i focus on vitrage in recent times, and very interested in: https://www.openstack.org/summit/austin-2016/summit-schedule/events/896309:24
janicefor this talk, are there some slides?09:25
ifat_afekHi Janice, welcome to our IRC :-)09:25
janicethank you :)09:25
*** idan_hefetz has quit IRC09:25
ifat_afekSure there will be slides, you will be able to see them later09:26
ifat_afekUntil then, you are welcome to visit vitrage wiki page, where you can find a presentation and some demos: https://wiki.openstack.org/wiki/Vitrage09:26
janicewill after the  austing submit?09:26
*** yamahata has quit IRC09:26
ifat_afekOhad is preparing the slides, I will have to discuss it with him09:27
janiceok, thank you09:27
ifat_afek(Ohad, Iris and Gerald)09:27
ifat_afekWill you be in Austin?09:28
janicesorry, this time i will not attend the submit, but i may attend to the opnfv submit09:28
ifat_afekOk. Some of us will attend OPNFV summit as well09:29
ifat_afekDo you have any other questions?09:29
janiceyes09:29
janicefor the talk:Nokia CloudBand Vitrage & OPNFV Doctor , does the test code begin?09:30
*** yamamot__ has quit IRC09:30
ifat_afekI'm not so sure what you mean by "does the test code begin"09:30
janiceoh, i'm sorry09:30
ifat_afekAnd BTW, there will also be another talk:09:31
ifat_afekhttps://www.openstack.org/summit/austin-2016/summit-schedule/events/817709:31
ifat_afekPlease explain09:31
janicethis talk: https://www.openstack.org/summit/austin-2016/summit-schedule/events/817709:31
janicesorry, this talk:https://www.openstack.org/summit/austin-2016/summit-schedule/events/896309:32
janicewhen integrate vitrage as inspector in doctor, there need some test code09:32
ifat_afekOh, I see09:32
ifat_afekI'm not sure if the talk covers the testing issue09:32
janicedoes these test code in doctor begin? or some one has do it?09:33
ifat_afekI know that Iris and Ohad plan to talk about OpenStack and Vitrage in general, and I think that Gerald plans to talk about Doctor and Inspector09:33
ifat_afekBut the integration has not began yet09:34
ifat_afekWe are mainly talking right now :-) Vitrage first version will be released next week, and then we can talk about the tests09:34
janiceok, understand, thank you very much :-)09:34
ifat_afekhappy to help09:34
ifat_afekany other questions?09:34
janicei have no :)09:35
*** idan_hefetz has joined #openstack-meeting-309:36
ifat_afekYou are very welcome to join our IRC meeting again, or to send us questions in emails09:36
ifat_afekAnyone would like to discuss anything else?09:36
*** jlanoux has quit IRC09:37
ifat_afekSo goodbye everybody. Next time we will get back to our regular agenda. Have a great week and good luck in Austin :-)09:38
elisha_rbye!09:38
eyalbbye09:38
janicebye09:38
nbloomSee you next time :)09:38
ifat_afek#endmeeting09:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:38
openstackMeeting ended Wed Apr 20 09:38:58 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-04-20-09.00.html09:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-04-20-09.00.txt09:39
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-04-20-09.00.log.html09:39
*** jlanoux has joined #openstack-meeting-309:39
*** eyalb has quit IRC09:40
*** idan_hefetz has quit IRC09:40
*** ifat_afek has left #openstack-meeting-309:47
*** mbound has quit IRC09:59
*** ccamacho has joined #openstack-meeting-310:01
*** mbound has joined #openstack-meeting-310:02
*** mbound has quit IRC10:04
*** yamamoto has joined #openstack-meeting-310:05
*** mbound has joined #openstack-meeting-310:05
*** sdague has joined #openstack-meeting-310:07
*** nelsnelson has joined #openstack-meeting-310:08
*** zz_dimtruck is now known as dimtruck10:08
*** alexey_weyl has quit IRC10:09
*** danoffek has quit IRC10:09
*** nelsnelson has quit IRC10:13
*** jlanoux has quit IRC10:15
*** danoffek has joined #openstack-meeting-310:16
*** alexey_weyl has joined #openstack-meeting-310:17
*** dimtruck is now known as zz_dimtruck10:18
*** stendulker has quit IRC10:18
*** nbloom has left #openstack-meeting-310:19
*** mbound has quit IRC10:19
*** mbound has joined #openstack-meeting-310:20
*** neiljerram has quit IRC10:22
*** mbound has quit IRC10:23
*** mbound has joined #openstack-meeting-310:25
*** doug-fish has joined #openstack-meeting-310:26
*** doug-fish has quit IRC10:31
*** neiljerram has joined #openstack-meeting-310:32
*** emagana has joined #openstack-meeting-310:34
*** emagana has quit IRC10:39
*** ccamacho is now known as ccamacho|lunch10:40
*** stanzgy has quit IRC10:44
*** itxaka has joined #openstack-meeting-310:44
*** ociuhandu has quit IRC10:51
*** jlanoux has joined #openstack-meeting-310:53
*** tellesnobrega is now known as tellesnobrega_af10:54
*** cfarquhar has quit IRC10:59
*** eliqiao_ has joined #openstack-meeting-310:59
*** cfarquhar has joined #openstack-meeting-311:00
*** cfarquhar has quit IRC11:00
*** cfarquhar has joined #openstack-meeting-311:00
*** eliqiao has quit IRC11:01
*** yamamoto has quit IRC11:02
*** elisha_r has quit IRC11:04
*** ddieterly has joined #openstack-meeting-311:06
*** zz_dimtruck is now known as dimtruck11:09
*** doug-fish has joined #openstack-meeting-311:11
*** ociuhandu has joined #openstack-meeting-311:14
*** dimtruck is now known as zz_dimtruck11:19
*** ddieterly is now known as ddieterly[away]11:25
*** yamamoto has joined #openstack-meeting-311:26
*** ddieterly[away] is now known as ddieterly11:29
*** ccamacho|lunch has quit IRC11:35
*** ccamacho has joined #openstack-meeting-311:36
*** ddieterly is now known as ddieterly[away]11:38
*** mageshgv has joined #openstack-meeting-311:39
*** nkrinner has quit IRC11:44
*** rtheis has joined #openstack-meeting-311:45
*** thatsdone has joined #openstack-meeting-311:46
*** vtech has quit IRC11:46
*** vtech has joined #openstack-meeting-311:47
*** baoli has joined #openstack-meeting-311:47
*** baoli has quit IRC11:49
*** baoli has joined #openstack-meeting-311:49
*** baoli has quit IRC11:49
*** nkrinner has joined #openstack-meeting-311:50
*** numan_ has quit IRC11:51
*** nkrinner has quit IRC11:55
*** nkrinner has joined #openstack-meeting-311:56
*** claudiub has joined #openstack-meeting-311:56
*** baoli has joined #openstack-meeting-312:04
*** baoli_ has joined #openstack-meeting-312:06
*** danoffek has quit IRC12:07
*** baoli has quit IRC12:09
*** zz_dimtruck is now known as dimtruck12:10
*** ddieterly[away] is now known as ddieterly12:18
*** ddieterly has quit IRC12:18
*** markvoelker has joined #openstack-meeting-312:18
*** piet has joined #openstack-meeting-312:18
*** eharney has quit IRC12:19
*** dimtruck is now known as zz_dimtruck12:21
*** qwebirc12661 has joined #openstack-meeting-312:30
*** Poornima has quit IRC12:30
*** tfukushima has quit IRC12:32
*** kenji-i has quit IRC12:36
*** iurygregory has joined #openstack-meeting-312:37
*** ddieterly has joined #openstack-meeting-312:46
*** atuvenie has joined #openstack-meeting-312:47
*** salv-orlando has joined #openstack-meeting-312:48
*** vtech has quit IRC12:49
*** vtech has joined #openstack-meeting-312:50
*** mfranc213 has quit IRC12:51
*** tellesnobrega_af is now known as tellesnobrega12:52
*** vtech_ has joined #openstack-meeting-312:52
*** vtech has quit IRC12:52
*** mfranc213 has joined #openstack-meeting-312:54
*** njohnston_ has joined #openstack-meeting-312:54
*** piet has quit IRC12:56
*** Poornima has joined #openstack-meeting-312:57
*** nelsnelson has joined #openstack-meeting-312:57
*** piet has joined #openstack-meeting-312:58
*** sagar_nikam has joined #openstack-meeting-312:59
atuvenieo/13:00
*** alexpilotti has joined #openstack-meeting-313:00
domi007hi all13:00
lpetrutHi13:00
alexpilotti#startmeeting hyper-v13:00
openstackMeeting started Wed Apr 20 13:00:59 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
*** slaweq_ has joined #openstack-meeting-313:01
alexpilottihi folks13:01
sagar_nikamHi13:01
atuveniehi all13:01
domi007hi13:01
*** itoader has joined #openstack-meeting-313:01
ajohmm, isn't neutron_qos meeting here at this time?13:01
*** emagana has joined #openstack-meeting-313:02
alexpilottiTo begin a quick announcement: we'll skip the meeting next week as most of us are going to be at the Austin summit13:02
*** Poornima has quit IRC13:02
slaweq_hello13:02
slaweq_ajo: I also thought that :)13:02
alexpilottiajo: looks like there's some timezone issue here :)13:02
ajoslaweq_, ours is later: http://time.is/es/UTC13:02
ajosorry :)13:02
slaweq_aha13:03
slaweq_ok13:03
ajoDST13:03
*** abalutoiu has joined #openstack-meeting-313:03
*** rossella_s has quit IRC13:03
alexpilottiajo slaweq_: the beauty of having meetings in UTC is that around this time of the year it becomes a mess :)13:03
ajohehehehe alexpilotti yes ':)13:04
*** mickeys has joined #openstack-meeting-313:04
*** rossella_s has joined #openstack-meeting-313:04
slaweq_yep13:04
slaweq_sorry for disturb You :)13:04
alexpilottislaweq_: np! :)13:05
alexpilotti#topic tpool for mixed threads / greenlets13:05
*** openstack changes topic to "tpool for mixed threads / greenlets (Meeting topic: hyper-v)"13:05
*** emagana has quit IRC13:06
*** [1]cdearborn has joined #openstack-meeting-313:06
alexpilottiWe identified some race conditions around WMI events which are handled in native threads13:06
alexpilottithere's a new patch that merged now in os-win for master and Mitaka13:06
domi007what symptoms can be observed? random WMI operation failing?13:07
lpetrutbasically, we have to avoid using eventlet primitives (or monkey patched ones, such as locks, events, etc) when running code in a different native thread13:07
alexpilottilpetrut: do you have a trace at hand or even better the link to the bug?13:07
*** zz_dimtruck is now known as dimtruck13:07
lpetrutthe event listener was dying unexpectedly with a greenlet error, complaining that it cannot switch to a different thread13:07
lpetrutsure13:07
*** mickeys has quit IRC13:08
lpetruthttps://bugs.launchpad.net/os-win/+bug/156882413:08
openstackLaunchpad bug 1568824 in os-win "Event listeners die unexpectedly" [Undecided,Fix released]13:08
domi007thanks13:08
*** lblanchard has joined #openstack-meeting-313:09
alexpilottiI just noticed that it was unprioritized, added it now13:10
alexpilottitalking about MI and WMI, it's important to note that the Hyper-V WMI v2 provider in Windows Server 2012 has some issues13:11
lpetrutjust added a trace to the bug report as well13:11
alexpilottiso for 2012 we revert to the old WMI when needed13:12
alexpilottithis means that since the old WMI is not supporting parallel operations, we limit the workers to 1 in networking-hyperv13:12
alexpilottiimportant: this DOES not apply to 2012 R2, only 201213:13
sagar_nikamalexpilotti: if using 2012, we need to use WMI instead of pyMI ?13:13
*** vhoward has joined #openstack-meeting-313:13
domi007I think this is all PyMI's internal magic, isn't it?13:13
alexpilottijust for some operations, os-win takes care of that13:13
domi007I meant os-win :)13:13
alexpilottibasically os-win selects the proper WMI module based on the OS13:14
sagar_nikamok13:14
alexpilottiwhat is annoying, is that we still need to ship pywin32 for supporting 201213:14
alexpilottias the old WMI depends on it13:15
domi007that's indeed annoying, but at least everything works everywhere13:15
alexpilottinothing critical but it's important to note it13:15
alexpilotti#topic Mitaka release13:16
*** openstack changes topic to "Mitaka release (Meeting topic: hyper-v)"13:16
*** sc68cal has quit IRC13:16
alexpilottitoday we're done with all bugs and backports13:16
*** mkovacik_ has joined #openstack-meeting-313:17
*** njohnston has quit IRC13:17
*** xiaohhui has quit IRC13:17
alexpilottia new PyMI 1.0.2 release is under test and will be released later today if nothing new shows up on the radar13:17
*** dansmith has quit IRC13:17
*** sheeprine has quit IRC13:17
*** sheeprine has joined #openstack-meeting-313:18
*** piet has quit IRC13:18
alexpilottiwhich means that final tests for our MSI will start as well immediately afterwards13:18
sagar_nikamwhat are the fixes in 1.0.2 as compared to the previous version ?13:18
*** xiaohhui has joined #openstack-meeting-313:18
domi007alexpilotti: once the MSI tests are done it is safe to say that upgrading to Mitaka should be painless?13:18
*** mkovacik has quit IRC13:19
alexpilottisagar_nikam: mostly minor things: https://github.com/cloudbase/PyMI/commits/master13:19
*** sc68cal has joined #openstack-meeting-313:19
sagar_nikamok13:19
*** njohnston has joined #openstack-meeting-313:20
*** dansmith has joined #openstack-meeting-313:20
*** dansmith is now known as Guest6476713:20
alexpilottithe main "feature" is adding a field to the previous WMI instance object during events13:20
*** pgadiya has quit IRC13:20
alexpilottithis is needed for clustering13:20
sagar_nikamok13:20
alexpilottibeside this, better error reporting when trying to retrieve a non-existing WMI instance property / method13:21
*** sverma has quit IRC13:22
*** jlanoux has quit IRC13:22
*** ccamacho has quit IRC13:22
*** reedip_ has quit IRC13:23
alexpilotticurrent version is 1.0.2.dev2, which will be a signed 1.0.2 release after tests (unless regressions show up of course)13:23
*** piet has joined #openstack-meeting-313:23
alexpilottinext13:24
alexpilotti#topic console support specs13:24
*** openstack changes topic to "console support specs (Meeting topic: hyper-v)"13:24
alexpilottiafter the millionth rebase we have been asked to add a spec for this BP13:24
*** ccamacho has joined #openstack-meeting-313:25
sagar_nikambp link ?13:25
alexpilottireason is that we are also working on objects, so it's not a so called trivial BP anymore13:25
alexpilottilpetrut: do you have a link at hand?13:25
lpetrutbasically, the serial console implementation can go in, they need a spec just for adding the the image props13:25
lpetrutsure13:25
lpetruthere's the BP: https://blueprints.launchpad.net/nova/+spec/hyperv-serial-ports13:26
lpetrutbut for the image props, we'll need a spec, which I have not submitted yet13:26
alexpilottithanks lpetrut13:27
alexpilottito be clear console support is part of compute-hyperv since ages, but since it needs to merge in nova eventually, this is the status13:27
*** rhochmuth has joined #openstack-meeting-313:27
alexpilottithose were also the first patches in the Newton review queue, so we are now bumping up the next in line13:28
*** sc68cal has quit IRC13:28
alexpilotti#topic OVS 2.513:29
*** openstack changes topic to "OVS 2.5 (Meeting topic: hyper-v)"13:29
alexpilottiwe have a release-blocker bug for 2.5, when using LACP, the switch is dropping packets in some conditions13:30
domi007oh I see13:30
alexpilottiATM this is the last blocker before release13:30
alexpilottithis can be worked around using NetLBFO13:30
*** itxaka is now known as itxaka|lunch13:31
alexpilottibut it's obviously much better if LACP can be handled directly by the vmswitch + OVS13:31
*** sc68cal has joined #openstack-meeting-313:31
alexpilottiespecially considering that the user can just apply the same openflow rules on Linux and Windows13:31
alexpilottisagar_nikam: did you guys did tests with the OVS 2.5 beta?13:32
sagar_nikami think not yet. sonu: team was planning, but as per my understanding it is not yet done13:32
sagar_nikamit is planned13:33
alexpilottiok thanks13:33
alexpilotti#topic Cinder SMB3 / iSCSI driver release13:33
*** openstack changes topic to "Cinder SMB3 / iSCSI driver release (Meeting topic: hyper-v)"13:33
*** piet has quit IRC13:33
domi007we would do testing, but without documentation we are not sure what to do...should we try to do it based on your previous write up?13:33
domi007oops, sorry, got caught up in the middle of topic change :) I'll leave my questions to the end13:34
alexpilottidomi007: good point, we're still writing the updated docs, let me ping a colleague13:34
domi007thanks :)13:34
*** vgridnev has quit IRC13:34
*** sverma has joined #openstack-meeting-313:34
*** rossella_s has quit IRC13:34
alexpilottidomi007: I'm starting an email thread13:36
*** tellesnobrega is now known as tellesnobrega_af13:36
domi007all right, looking forward to it :)13:36
alexpilottiso you dont have to wait for the public docs to be available13:37
*** sonu has joined #openstack-meeting-313:37
domi007good, I'm grateful13:37
*** rbak has joined #openstack-meeting-313:37
alexpilottiso getting back to the Cinder driver, it's aslo getting released13:37
*** obondarev_ has quit IRC13:37
*** vgridnev has joined #openstack-meeting-313:38
alexpilottinothing major to signal, there are various bug fixes but core functionality is retained from Liberty13:38
*** toddjohn_ has joined #openstack-meeting-313:38
alexpilotti#topic open discussion13:38
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:38
*** tonytan4ever has joined #openstack-meeting-313:39
*** obondarev has joined #openstack-meeting-313:39
sagar_nikamalexpilotti: have you tried Windows NLB ?13:39
alexpilottiMost topics today were clearly focused around the Mitaka release as that's where most of the focus was in the last days13:39
sagar_nikamnetwork load balancer13:39
alexpilottisagar_nikam: in what context?13:40
sagar_nikami am thinking of using it for freerdp13:40
sagar_nikamrun freerdp on 3 machines13:40
sagar_nikamhave a cluster IP using NLB13:40
alexpilottiany load balancer that can preserve client affinity and supports websockets is good13:41
sagar_nikamand then provide that Cluster IP in nova.conf13:41
domi007so we have this weird issue I already put up on ask and Alin was nice and started looking into it - basically if a network security group is applied to a VM and the group is modified the modification isn't applied to the VM somehow. I couldn't get any traces of it yet, but as far as I know the issue still exists13:41
domi007sagar_nikam: haproxy could be used maybe, we will need some kind of freeRDP clustering as well good that you mentioned this13:42
sagar_nikamalexpilotti: i had some questions on NLB, anybody from your team has knowledge on it ?13:42
alexpilottisagar_nikam: we are using haproxy as well much more than NLB13:42
sagar_nikamdomi007: haproxy for windows ? i think it is not available, hence i am thinking of using NLB13:43
domi007oh I see, I thought of it because we already have one in our system that balances openstack management apis :)13:43
*** ccamacho has quit IRC13:43
sagar_nikamalexpilotti: haproxy on windows ? how does it work13:43
alexpilottiwe use NLB as well, but not being that popular we dont use it as a load balancer in test deployments13:43
alexpilottisagar_nikam: linux13:43
alexpilottiit's just sitting in front of the Windows cluster13:44
alexpilottialso, IIS has a nice LB feature13:44
alexpilottias an alternative13:44
*** ccamacho has joined #openstack-meeting-313:44
sagar_nikamalexpilotti: since i am running freerdp on windows machines, i thought NLB was the only option13:44
alexpilottiit's called ARS13:44
*** dimtruck is now known as zz_dimtruck13:44
sagar_nikamalexpilotti: can you/your team help me with using haproxy and windows cluster13:45
alexpilottiIf you want a pure Windows deployment, NLB or ARS are the only choices13:45
alexpilottiif not, any LB frontend with the above limits can do13:46
alexpilottidomi007: abalutoiu says he tested on Mitaka and all is good, he's switching to Liberty now13:46
sagar_nikamin your environments you use haproxy on linux and it balancing windows cluster ?13:47
*** njohnston is now known as njohnston__13:47
domi007do you also have the issue of wsgate sometimes simply not working, but a restart of the service fixes it?13:47
*** njohnston__ is now known as njohnston_afk13:47
alexpilottisagar_nikam: the FreeRDP hosts, not the Windows cluster itself13:47
domi007sagar_nikam: in our env we have all linux VMs running openstack's management machines, and between them all API calls are routed through haproxy13:48
sagar_nikamalexpilotti: right i meant freerdp hosts13:48
sagar_nikamalexpilotti: and what IP is given in nova.conf for freerdp on hyperv hosts ?13:48
alexpilottidomi007: it happened for us on previous versions due to a lock, do you have a dump that we can analyze?13:49
domi007alexpilotti: by dump you mean a log file? does wsgate keep logs at all? haven't really checked this13:49
alexpilottidomi007: if not, if happens again, get in touch with cmunteanu in our team13:49
domi007oh, okay, that's good13:50
alexpilottidomi007: no, a Windows memory dump. You can generate one when the service becomes unresponsive13:50
*** sverma has quit IRC13:50
domi007oh, all right...but there is a newer version available if I understood correctly?13:50
alexpilottidomi007: Windows can generate dumps on BSODs and application crashes, but you can also dump one anytime13:51
domi007makes sense, sure13:51
alexpilottidomi007: last one was in december AFAIK13:51
domi007okay, I think our installation is newer then that, so we will cluster and dump as well13:51
domi007:)13:52
sagar_nikamalexpilotti: haproxy VIP is given in nova.conf on hyperv hosts ?13:52
*** haleyb has joined #openstack-meeting-313:53
alexpilottisagar_nikam: yes correct13:53
sagar_nikamok13:53
sagar_nikamwill try that13:53
alexpilottisince that's what horizon passes to the user13:53
domi007proxies to the user :)13:54
alexpilottithen the LB connects to the FreeRDP farm13:54
sagar_nikamok13:54
sagar_nikamand it works well ?13:54
alexpilottiand those connect to the individual Hyper-V hosts based on the Nova token13:54
alexpilottisagar_nikam: only issues we had are for websocket affinity13:55
sagar_nikamnever tried using haproxy running on linux connecting windows machines13:55
alexpilottiwe do it all the time, mostly for web apps13:55
sagar_nikamok13:55
alexpilottiit's a very simple and lightweight solution13:55
sagar_nikamalexpilotti: will mail you if i need any help13:55
domi007since HTTP is universal, haproxy simply pings based on http13:55
sagar_nikamthis seems much simpler than using NLB13:56
domi007so it should work...we will try this as well, so if you need help sagar_nikam email us13:56
alexpilottisure, but yeah as domi007 says it's just HTTP :)13:56
*** absubram has quit IRC13:56
domi007as well13:56
sagar_nikamsure domi007:13:56
*** neelashah has joined #openstack-meeting-313:56
alexpilottiNLB is not limited to HTTP only, but in this case that's all you need13:57
alexpilotti-3'13:57
sagar_nikamalexpilotti: agree13:57
alexpilottiany other topic?13:57
*** njohnston has joined #openstack-meeting-313:58
alexpilottiTiming out... :)13:58
sagar_nikamalexpilotti: 4 meetings scheduled in summit. freezer, monasca, magnum and designate, let me know if you need any help13:58
domi007Good luck in Austin guys, see you in two weeks! Hopefully Mitaka MSIs will be done with testing and out for the public :)13:58
*** vishwanathj has joined #openstack-meeting-313:58
domi007alexpilotti: till then we'll look into OVS13:59
alexpilottisagar_nikam: thanks for all your help there, we're still waiting for an answer from the Magnum TPL AFAIK, but all the rest of the meetings are planned13:59
alexpilottithanks guys!13:59
alexpilotti#endmeeting14:00
sagar_nikami think 3pm on wednesday14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Apr 20 14:00:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-04-20-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-04-20-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-04-20-13.00.log.html14:00
*** mickeys has joined #openstack-meeting-314:00
ajonow yes :)14:00
slaweq_hello then :)14:00
ajoslaweq_, ihrachys14:00
ajoirenab,14:00
ajovhoward,14:00
ajoshall we ping more?14:00
ajo#startmeeting neutron_qos14:01
openstackMeeting started Wed Apr 20 14:01:07 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
*** dslevin has left #openstack-meeting-314:02
njohnstonParticipating from my car today14:02
*** RP_ has joined #openstack-meeting-314:02
slaweq_njohnston: and You are driving now? :)14:02
ajohi njohnston14:02
RP_nope14:02
ajo:-)14:02
ajoI was letting some extra time for people to join.14:03
irenabhi14:03
ajobut it seems that the attendance is low :-),14:03
RP_hi14:03
*** MarkAtwood has joined #openstack-meeting-314:03
ajonjohnston, prepared the agenda for today, as he's stepped in to help me co-chair this meeting14:03
ajoand today, he's travelling.14:03
ajothanks njohnston14:04
ajohi RP_ , slaweq_ , irenab , njohnston , so let's begin14:04
*** sverma has joined #openstack-meeting-314:04
*** davidsha has joined #openstack-meeting-314:04
*** mickeys has quit IRC14:04
ajo#topic Summit Planning14:04
*** openstack changes topic to "Summit Planning (Meeting topic: neutron_qos)"14:04
ajoWe have two QoS talks on the schedule, for those interested:14:04
ajo#link https://www.openstack.org/summit/austin-2016/summit-schedule/events/749514:05
ajoa general one about Quality of Service, what we accomplished in Mitaka, and the future roadmap, ( slaweq_ , vhoward and me)14:05
davidsha#link https://www.openstack.org/summit/austin-2016/summit-schedule/events/7441?goback=114:05
ajoand exactly thanks davidsha14:06
ajoan specific one about DSCP14:06
ajonjohnston, amd davidsha will be on stage :)14:06
*** electrocucaracha has joined #openstack-meeting-314:06
ajoWe'd also like to announce, if that sounds right, that we'd be cancelling the meeting after the summit, on May 4th.14:07
*** mickeys has joined #openstack-meeting-314:07
njohnstonYay!14:07
ajohehe njohnston14:07
*** [1]cdearborn has quit IRC14:07
vhoward+114:07
davidsha+114:07
ajoany objections for cancelling the next meeting?  :)14:07
ajo+1 from me too14:07
vhowarddavidsha: haha14:07
irenab:-)14:08
*** baoli_ has quit IRC14:08
*** vgridnev has quit IRC14:08
*** vgridnev has joined #openstack-meeting-314:09
ajoAlso, we should use the friday time to meet, discuss and plan about QoS in person.14:09
ajosome of the friday time, :)14:09
*** itoader has quit IRC14:09
*** jmckind has joined #openstack-meeting-314:09
davidshaajo: there is also the flow management/ flow classifier meeting on Tuesday with Cathy I believe.14:09
njohnston+114:10
ajooh, great davidsha , what time's that on Tuesday exactly?14:10
irenabdavidsha: any specific time?14:10
slaweq_ajo: can it be friday morning, because I have plane at afternoon?14:10
davidsha1 sec14:10
ajoIt's an interesting morning.14:10
ajoslaweq_ +1 for the morning, most people will be flying on the afternoon I suspect14:10
slaweq_ok, great :)14:11
davidshaNo time "I am thinking about around lunch time on Tuesday or Wednesday since some of us will fly back on Friday morning/noon."14:11
ajoI booked my flight back on saturday, because the latest flight was taking off at 18:05 for me14:11
vhowardi'm in for friday14:11
davidsha-_- lunch time.14:11
slaweq_I will go this at 18:05 :)14:11
*** oanson has joined #openstack-meeting-314:11
ajodavidsha, may be we should bring a big sign for lunch, it's hard to meet anyone on purpose during summit on lunch14:12
*** cloudtrainme has joined #openstack-meeting-314:12
*** mickeys has quit IRC14:12
*** zz_dimtruck is now known as dimtruck14:12
davidshaI'll be around on Friday.14:12
ajodavidsha, or make the meeting of Tuesday more specific as we see the place on Monday, otherwise I'm afraid the meeting won't really happen14:12
ajook, let's follow up about that with Cathy on that14:13
irenabajo: can you please share some details regarding scheduler and neutron discussion you emailed few mins ago?14:13
ajoand let's talk QoS on friday morning.14:13
ajoirenab, sure, there's a point for it.14:13
ajolet's follow njohnston's prepared agenda. :)14:13
ajohttps://etherpad.openstack.org/p/neutron_qos_meeting_chair if you want to sneak peak14:14
ajo#link https://bugs.launchpad.net/neutron/+bug/156372014:14
openstackLaunchpad bug 1563720 in neutron "Bandwidth limiting for linuxbridge agent works for ingress traffic instead of egress" [High,Fix released] - Assigned to Slawek Kaplonski (slaweq)14:14
ajoslaweq_, how's that looking ?14:14
slaweq_it's fixed14:15
slaweq_we changed tc to use ingress policing instead of shaping egress traffic14:15
ajooh, true, it was merged, /me feels dumb :D14:15
ajogood work slaweq_ ,14:15
slaweq_in fact it's now in exactly same way like ovs is doing it14:15
slaweq_there is also cherry-pick to mitaka of this patch14:15
slaweq_waiting for review14:15
*** sigmavirus24_awa is now known as sigmavirus2414:15
ajoin the context of that, slaweq_ found that ovs ingress policing burst parameter set's the wrong thing14:16
ajoif you ask openvswitch to set 1Mbit burst on a port for ingress policing14:16
ajoyou get 8Mbit burst14:16
ajo(bits mixed with bytes)14:16
slaweq_yep, and ajo fixed it in ovs :)14:16
ajoI've proposed a fix for ovs,14:16
*** jaypipes has joined #openstack-meeting-314:16
ajobut the issue with that, is that next versions of ovs will behave differently to current ones,14:17
ajowe may need to add a flag to the agent, and a sanity check14:17
ajoto do the /8 division14:17
ajook14:17
ajo#14:17
ajo#link https://launchpad.net/bugs/148660714:17
openstackLaunchpad bug 1486607 in neutron "tenants seem like they were able to detach admin enforced QoS policies from ports or networks" [Medium,In progress] - Assigned to Nate Johnston (nate-johnston)14:17
slaweq_maybe we should do in ovs something like in LB agent?14:17
slaweq_to add burst value as 80% of bw_limit if it is not set?14:17
ajoslaweq_, I agree, that's right14:17
slaweq_AFAIR ovs sets always 1000kb if burst is not given14:18
ajoslaweq_, could you open a bug for it so  we don't forget ?14:18
slaweq_but we could make it more consistent for both14:18
slaweq_ok, I will14:18
ajoyes, I'd set 80% of max_rate by default, of nothing provided14:18
ajothanks slaweq_14:19
ajoabout the above bug ^14:19
ajonjohnston, is on it, he's sorting out the testing details14:19
ajobut other than that it should be good.14:19
ajoThanks njohnston!, anything to be noted about it?14:19
*** mbound has quit IRC14:20
*** electrocucaracha has left #openstack-meeting-314:20
ajook, next one :)14:20
ajo#link https://bugs.launchpad.net/neutron/+bug/156840014:20
openstackLaunchpad bug 1568400 in neutron "Pecan does not route to QoS extension" [Medium,In progress] - Assigned to Brandon Logan (brandon-logan)14:20
njohnstonJust that I need to sort out how to take admin and non-admin actions in the same test14:20
ajonjohnston, ack, exactly, the testing details, he needs to be able to do operations in the api-tempest tests as admin, and normal tenant14:21
ajoif anybody has experience with that ping njohnston, please :)14:21
ajoabout 1568400 blogan fixed that, it's an issue in the context of pecan, so thanks blogan! :)14:22
ajoI will skip " https://bugs.launchpad.net/neutron/+bug/1507654" since ihar doesn't seem around,14:22
openstackLaunchpad bug 1507654 in neutron "Use VersionedObjectSerializer for RPC push/pull interfaces" [Low,In progress] - Assigned to Artur Korzeniewski (artur-korzeniewski)14:22
*** sonu has quit IRC14:22
*** spzala has quit IRC14:22
*** spzala has joined #openstack-meeting-314:23
ajothat seems to be "In progress" but there's no link to the actual patch14:23
ajo#action iharchys  link https://bugs.launchpad.net/neutron/+bug/1507654 to the gerrit review14:23
openstackLaunchpad bug 1507654 in neutron "Use VersionedObjectSerializer for RPC push/pull interfaces" [Low,In progress] - Assigned to Artur Korzeniewski (artur-korzeniewski)14:23
ajo#link https://bugs.launchpad.net/neutron/+bug/150776114:23
openstackLaunchpad bug 1507761 in neutron "qos wrong units in max-burst-kbps option (per-second is wrong)" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)14:23
ajoslaweq_, this one is yours ^14:23
slaweq_yep14:23
ajoas far as I understood, we can't proceed until we have something like api microversioning14:24
*** vgridnev has quit IRC14:24
slaweq_and I wanted to ask about what to do with it?14:24
slaweq_exactly14:24
ajoslaweq_, probably document and wait14:24
slaweq_as You and ihrachys said in review14:24
slaweq_document on launchpad? or where?14:24
ajoslaweq_, the api guide, probably, and the adv networking guide14:24
slaweq_ah, ok14:25
slaweq_no problem, I have some experience with that already :)14:25
ajoslaweq_++14:25
ajoawesome, thanks :)14:25
njohnston+114:25
ajo#link https://bugs.launchpad.net/neutron/+bug/151556414:25
openstackLaunchpad bug 1515564 in neutron "Internal server error when running qos-bandwidth-limit-rule-update as a tenant" [Low,In progress] - Assigned to Liyingjun (liyingjun)14:25
ajo#link https://review.openstack.org/#/c/244680/  needs reviews14:26
ajoI totally missed it, adding it to my queue14:27
*** spzala has quit IRC14:27
ajoI suspect that patch will conflict with the qos_plugin refactor mfrances was working on14:27
*** vgridnev has joined #openstack-meeting-314:28
ajomfranc213, if you can ask the author to follow up on your patch, that would be the best I think14:28
ajowhich is: https://review.openstack.org/#/c/294463/14:28
*** tellesnobrega_af is now known as tellesnobrega14:29
ajonext is14:29
ajo#link https://bugs.launchpad.net/neutron/+bug/155861414:29
openstackLaunchpad bug 1558614 in neutron "The QoS notification_driver is just a service_provider, and we should look into moving to that" [Low,In progress] - Assigned to Ching Sun (ching-sun)14:29
mfranc213ajo: i'll get in touch with the author.  thanks for this.14:30
ajoI see we have a question to answer, I still don't have the exact answer14:30
ajoit's not a simple change of config name,14:30
ajowe may need to look into the service_providers thing, see how it works, and if it fits what we do with the notifications_driver14:30
ajobut it seems very similar.14:30
ajoMay be it does not 100% fit14:31
ajobecause with service providers, you can specify different providers for the same service14:31
ajoand that won't work in our case,14:31
ajoI will link that bug to this log, and discuss in there as soon as we have a clear answer14:31
*** zhurong has quit IRC14:32
ajo#link https://bugs.launchpad.net/neutron/+bug/150765614:32
openstackLaunchpad bug 1507656 in neutron "RPC callbacks push/pull mechanism should be remotable" [Wishlist,Confirmed] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)14:32
*** Sukhdev has joined #openstack-meeting-314:32
*** absubram has joined #openstack-meeting-314:32
njohnstonI wasn't sure if that was large enough to warrant an RFE14:32
ajothat one doesn't really add any new feature14:33
ajois more like a refactor of the rpc callbacks code14:33
njohnstonOk14:33
ajoI think push can't use what ihrachys proposes, but I'm sure pull could14:33
ajowe may eventually look at it when we have time. or move to Won't fix if that doesn't happen.14:34
ajo#link https://bugs.launchpad.net/neutron/+bug/155683614:34
openstackLaunchpad bug 1556836 in neutron "QOS: TestQosPlugin should receive plugin name as an input" [Wishlist,In progress] - Assigned to Adit Sarfaty (asarfaty)14:34
*** sagar_nikam has quit IRC14:34
*** tonytan4ever has quit IRC14:34
ajoah14:34
ajothat doesn't apply anymore14:35
ajobecause they did it the right way and stopped subclassing the QoS plugin14:35
*** tonytan4ever has joined #openstack-meeting-314:35
ajobugs--14:35
ajothat feels good :)14:35
ajo#link https://bugs.launchpad.net/neutron/+bug/156096314:36
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,Confirmed]14:36
ajoirenab, you were asking about this one14:36
irenabajo: I was patiently waiting14:36
ajoyou were very patient :)14:36
ajoThere's an ongoing design in the nova scheduler about this14:36
ajoThe idea is that they made some generic entities that we can fill in, to let the scheduler account resources14:36
ajoin our case14:37
*** yamahata has joined #openstack-meeting-314:37
ajowe could create pools (of traffic) attached to the hosts,14:37
*** ccamacho has quit IRC14:37
ajo(1 compute) --- (1 bandwidth pool)14:37
ajoand then, when nova had to schedule an instance with a port that requires "NIC_BW" of 1Gbit14:37
ajoit would look for the right pool (and therefore the right compute) to host it14:38
ajoand it would also count down the used traffic from the bandwidth pool attached to such compute14:38
ajoon that discussion14:38
ajowe noticed that, for that to happen, nova may need to look at the qos_policy_id and make an interpretation of a policy14:38
ajolooking for guaranteed traffic rules in the policy14:39
*** itxaka|lunch is now known as itxaka14:39
ajowhich is too coupled, since nova would have to understand the policies, the rules, which are supposed to be evolving14:39
ajoso..14:39
*** ccamacho has joined #openstack-meeting-314:39
ajothere was  suggestion from jaypipes to add an API to translate port uuids (or other objects), to scheduler constraints/scheduler resource usages14:39
ajothat's a good idea IMHO,14:40
irenabnova API?14:40
ajono, neutron api14:40
ajoyou would give that API a port id, and you would get a set of constraints/or resource usages for the scheduler14:41
irenabnica14:41
irenabnise14:41
ajo./get-scheduling-details/port/<port-uuid> ->14:41
irenabnice :-)14:41
ajo{"NIC_BW": 10000000,  blah, blah: ..}14:41
ajothe only issue we found about that, is that it would add another call from nova to neutron14:42
* njohnston has to go now... I will catch up with the transcript later. Thanks ajo!14:42
jaypipesirenab: an API that Nova (or the broken out scheduler) can call to Neutron to get information about the networking-related resource providers (like IPv4 address, etc)14:42
ajothanks njohnston !14:42
*** njohnston has quit IRC14:42
*** hosanai has joined #openstack-meeting-314:42
ajohi jaypipes :)14:42
slaweq_ajo: can't it be given in port-show call?14:42
ajoirenab, jaypipes ,14:42
slaweq_like now is policy-id14:42
ajoexactly, what slaweq_ is saying is what I was about to say14:42
*** sdake_ has quit IRC14:42
ajowe could do better14:42
slaweq_sorry :)14:42
ajoif we provide in the resource creation or show...14:42
ajothat dictionary14:42
ajoas a read only attribute of the port14:43
irenabthere is actually already port binding extension that has 2 dicts14:43
ajothat would avoid the extra API call from nova to neutron14:43
ajoirenab, aha, that's interesting, what are those dicts?14:43
irenabso maybe the vif_details or profile can be used14:43
ajoirenab, that's ml2 specific14:44
*** ajmiller has quit IRC14:44
ajowe should come up with something wide for all plugins,14:44
irenabno, this is about supporting port binding extension14:44
ajoand may be move those details from ml2 back into the generalized one14:44
*** claudiub has quit IRC14:44
ajoirenab, ok, but what I mean, is that if we put those scheduling details in the port binding extension dictionary, that's ml2 specific14:45
ajoand won't be available to other non-ml2 plugins14:45
*** ddieterly is now known as ddieterly[away]14:45
irenabso you prefer separate extension? Fair enough14:45
*** sdake_ has joined #openstack-meeting-314:45
ajoyes, and I guess we will depend in the "core extension manager" that ihrachys and I were thinking of14:45
ajoso two RFEs:14:45
ajo* core extension manager14:45
irenabbut I think the port binding is supported by others and actually maybe required by new vif lib14:46
ajo* scheduling details for nova14:46
*** tonytan_brb has joined #openstack-meeting-314:46
*** ddieterly[away] is now known as ddieterly14:46
ajoirenab, if it becomes required by vif_lib it will be an error we can't stop supporting non-ml2 plugins14:46
ajoas an example: OVN on the open side of things14:46
irenabwhy do you think its ml2 specifc?14:46
ajoirenab, may be it's not ml2 specific, and I'm mistaken :)14:47
irenabhttps://github.com/openstack/neutron/blob/master/neutron/extensions/portbindings.py14:47
slaweq_ajo: I agree with irenab, every plugin can support such extension14:47
irenabbut its implementation details anyway :-)14:47
ajoyeah, may be it makes sense14:47
ajolet's look at it, thanks irenab  :)14:48
*** watanabe_isao has joined #openstack-meeting-314:48
ajowe would have to come up with something to look up for the qos_policy details of a port and synthetize the thing into another dict there14:49
ajoor another detail in the dict14:49
* ajo is a little bit stubborn sometimes ;)14:49
ajoah14:49
ajoand about this RFE14:49
ajoI should probably split it in two14:49
ajo1) best effort14:50
ajo2) strict (with nova scheduling)14:50
*** tonytan4ever has quit IRC14:50
ajo1 would take care of the low level settings on each compute host to make it happen14:50
ajo(sriov settings, ovs settings, etc..)14:50
*** armax has joined #openstack-meeting-314:50
irenabanother question about guarantee, is it for edge only or should consider the end to end fabric?14:50
ajoI'm afraid we have 10 minutes and lots of RFEs to look at yet14:50
ajoirenab, initially only for edge, we could think of wider thing later14:51
irenabfine14:51
ajoirenab, but that would require modelling the whole underlaying network,14:51
ajoand not sure if we can keep control over all the traffic flows :)14:51
ajosounds like an interesting and very hard problem14:52
*** sverma has quit IRC14:52
irenabI would say, it would require neutron to be responsible14:52
irenabor maybe new project will come  to deal with it :-)14:52
ajolol :)14:52
*** slogan has joined #openstack-meeting-314:53
ajoI will skip some RFEs, (lack of time)14:53
ajo#14:53
ajo#link https://bugs.launchpad.net/neutron/+bug/152767114:53
openstackLaunchpad bug 1527671 in neutron "[RFE] traffic classification in Neutron QoS" [Wishlist,Incomplete]14:53
*** emagana has joined #openstack-meeting-314:53
ajodavidsha, we talked about this one ^, and there's where Cathy's meeting comes,14:54
ajoluckily on Tuesday lunch14:54
*** Sukhdev has quit IRC14:54
*** emagana has quit IRC14:54
*** armax_ has joined #openstack-meeting-314:55
*** emagana has joined #openstack-meeting-314:55
davidshaI'll be there14:55
ajoabout https://bugs.launchpad.net/neutron/+bug/1557457 , jun wei updated his description, I need to re-read it14:55
openstackLaunchpad bug 1557457 in neutron "[RFE] bandwidth rate-limit" [Wishlist,Incomplete]14:55
ajo#action ajo have another look at https://bugs.launchpad.net/neutron/+bug/155745714:55
*** oanson has quit IRC14:55
*** armax has quit IRC14:56
*** armax_ is now known as armax14:56
*** emagana has quit IRC14:56
ajo#link https://bugs.launchpad.net/neutron/+bug/153148514:56
openstackLaunchpad bug 1531485 in neutron "Available device bandwidth report by L2 agent" [Wishlist,Expired]14:56
*** ajmiller has joined #openstack-meeting-314:56
*** emagana has joined #openstack-meeting-314:56
ajothis one is expired, but it may happen in the context of https://bugs.launchpad.net/neutron/+bug/1560963   (when reporting to the nova generic resource pools)14:56
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,Confirmed]14:56
ajoand14:57
ajofinally slaweq_ is also working on these doc changes: https://review.openstack.org/#/c/30719314:57
ajoexplaining about burst values, and how should those be configured14:57
*** emagana has quit IRC14:57
ajo#topic Open discussion14:57
*** openstack changes topic to "Open discussion (Meeting topic: neutron_qos)"14:57
*** emagana has joined #openstack-meeting-314:58
ajoanything to talk about in our remaining 2 minutes? :)14:58
*** witek has joined #openstack-meeting-314:58
*** neelashah has quit IRC14:58
slaweq_I'm also working on https://bugs.launchpad.net/neutron/+bug/156096114:58
openstackLaunchpad bug 1560961 in neutron "[RFE] Allow instance-ingress bandwidth limiting" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:58
slaweq_but it's just begining now14:58
*** vgridnev has quit IRC14:58
*** Kamil has joined #openstack-meeting-314:58
ajooh, right, slaweq_ thanks about that too, you're doing an amazing job14:58
slaweq_thx :)14:59
*** Swami has joined #openstack-meeting-314:59
ajook so14:59
ajolet's endmeeting14:59
*** iyamahat has joined #openstack-meeting-314:59
ajoo/14:59
*** neelashah has joined #openstack-meeting-314:59
ajothanks everybody14:59
davidshathanks14:59
slaweq_thanks14:59
irenabthanks14:59
slaweq_see You in Austin :)14:59
ajosee you :)14:59
ajo#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Apr 20 14:59:58 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-04-20-14.01.html15:00
*** Guest64767 is now known as dansmith15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-04-20-14.01.txt15:00
*** cbellucci has joined #openstack-meeting-315:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-04-20-14.01.log.html15:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Apr 20 15:00:14 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
rhochmutho/15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
vhowardsee you in austin ;)15:00
witekhello15:00
rbako/15:00
hosanaio/15:00
*** bpokorny has joined #openstack-meeting-315:00
sloganmorning15:00
*** bklei has joined #openstack-meeting-315:00
*** davidsha has left #openstack-meeting-315:00
shinya_kwbto/15:00
cbelluccio/15:00
Kamilo/15:00
bkleio.15:00
bkleio/15:01
rhochmuthagenda has been posted15:01
rhochmuthAgenda for Wednesday April 20, 2016 (15:00 UTC)15:01
rhochmuth1. Patches15:01
rhochmuth1.1 https://review.openstack.org/#/c/298863/15:01
rhochmuth1.2 https://review.openstack.org/#/c/301355/15:01
rhochmuth1.3 https://review.openstack.org/#/c/307963/ (brad curious about status)15:01
rhochmuth1.4 https://review.openstack.org/#/c/289675 (same)15:01
rhochmuth2. Heads up on ovs plugin (router bandwidth metrics)15:01
rhochmuth 2.1 https://review.openstack.org/#/c/306621 (not fully baked)15:01
rhochmuth3. https://review.openstack.org/#/c/302660/15:01
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
rhochmuthhi everyone15:01
rhochmuthso we have a few reviews that have been asked about15:02
bkleigood morning!15:02
rhochmuthso, let's go through that list and then discuss other items15:02
rhochmuthhttps://review.openstack.org/#/c/298863/15:02
rbakThose first couple reviews are mine.15:02
rbakThat one just needs to get merged15:02
rbakIt's been sitting around for two weeks with several +115:02
rhochmuthi see, looks like there are a bunch of reviews and +1s15:03
rhochmuthi reviewed this morning, so it looks good to me15:03
rhochmuthi can merge now15:03
rbakGreat, thanks15:03
rhochmuththen there is https://review.openstack.org/#/c/301355/15:03
rbakThe next one is the more complicated patch15:03
rbakThis is the thread-pool replacement patch15:04
rhochmuthi looked at this one too15:04
rhochmuththere were some quesitons, but i'm not sure it has been resolved15:04
rbakI just wanted to talk about this one since it seems like there were some concerns15:04
rhochmuthyes15:04
rhochmuthis rbrabdt here?15:04
rhochmuthrbrandt?15:05
rhochmuthalso michael hoppal and joe keen would be good15:05
rhochmuthanyway, please ask questions15:05
rbakI'm open to making changes, I just want to keep this moving forward15:05
rhochmuthnot sure how much help i'll be15:05
*** amit213 has quit IRC15:06
rhochmuthso, i'll need to ping all those names i mentioned15:06
*** matrohon has quit IRC15:06
rbakI just need clarification on what the concerns are so I can fix them.15:06
*** irenab_ has joined #openstack-meeting-315:06
rhochmuthi'll ping them, we were super busy last week on our own releases15:06
*** tonytan_brb is now known as tonytan4ever15:06
rhochmuthso, hopefully they can take another look today15:07
rbakThat's fine.  I'll ping rbrandt later since it doesn't seem like he's on15:07
rbakWe can move on for now.15:07
*** irenab has quit IRC15:07
*** irenab_ is now known as irenab15:07
bkleithe next two patches are rbrandt's  -- and i was curious on status15:08
rhochmuthactually i did this really cool thing15:08
*** 14WAATBIX has joined #openstack-meeting-315:08
*** mhoppal has joined #openstack-meeting-315:08
rhochmuthi walked down the aisle and talked to them using my voice15:08
*** baoli has joined #openstack-meeting-315:08
*** amit213 has joined #openstack-meeting-315:08
bkleistrange -- that works?15:08
rhochmuththey are connecting in now15:08
mhoppalonly sometimes with him15:08
rhochmuthrbrandt u there15:08
bklei:)15:08
rhochmuthhoppal u there15:08
14WAATBIXI'm apparently under this name15:09
*** dimtruck is now known as zz_dimtruck15:09
mhoppalim here15:09
ddieterlyo/15:09
bkleinice name15:09
14WAATBIXno idea...15:09
rhochmuthis that you rbrandt15:09
14WAATBIXyeah15:09
rhochmuthok15:09
rhochmuthrbak is asking about https://review.openstack.org/#/c/301355/15:09
rhochmuththis is the muleiprocessing review15:09
rhochmuthhe's trying to understand next steps and the feedback he;'s received so far15:10
*** qwebirc12661 has quit IRC15:10
*** cloudtrainme has quit IRC15:10
14WAATBIXAh, yes. So the issue at the moment is the lost data if a check fails.15:10
14WAATBIXRight now, as far as I am aware, we don't lose data except for the failed check itself15:10
rbakThat's not correct15:11
*** vhoward has quit IRC15:11
14WAATBIXjkeen actually may know more of the specifics15:11
rbakRight now, worst case, the agent hangs and everything is lost.15:11
*** nkrinner has quit IRC15:11
rbakUntil the agent is restarted by hand.15:11
rbakThis patch doesn't actually change any behavior other than to allow the pool to restart as intended.15:11
bklei(and we've hit that a bunch and lost alot of data)15:12
rbakThe triggering condition and the result of the restart are still the same.15:12
rhochmuthso, with this patch, you fixed one big problem15:12
14WAATBIXjkeen was exploring the code to see what we used to do and what this new code does15:12
rhochmuthare there any other downsides15:12
rhochmuthsorry, meant downsides or side effects15:13
*** dhague_ has joined #openstack-meeting-315:13
rbakThe only new downside I'm aware of is that it's noisy.  Restarting the pool can throw a lot of errors.15:13
rhochmuthyou mean the log file15:13
*** jaypipes has quit IRC15:13
rbakYes.15:14
14WAATBIXI know when I was testing it we regularly saw failures in the checks15:14
rbakActually though, I think I finally realized what the miscommunication here is.15:14
14WAATBIXwhich is what prompted the comments15:14
rbakThere's two different ways this can be triggered, and we're talking about different conditions.15:14
*** mhoppal_ has joined #openstack-meeting-315:15
*** mhoppal has quit IRC15:15
rbakPreviously, the pool restarted cleanly and no data was lost, unless a check was truly stuck in which case it never restarted and the entire agent hung.15:15
*** cloudtrainme has joined #openstack-meeting-315:15
rbakIn that worst case this version is better.  If a check is just taking too long and the pool restarts, I suppose this does lose more data than before.15:16
*** mhoppal has joined #openstack-meeting-315:16
*** lpetrut has quit IRC15:16
rbak14WAATBIX: Why don't I talk to you after the meeting so we don't eat up too much time in the meeting.15:16
rhochmuthshould also get joe and michael15:17
14WAATBIXSure, I think we're getting synced now15:17
rhochmuthplease schedule a meeting with all three and anyone else that wants to attend15:17
rbakSure, I can do that.15:17
rhochmuththx rbak15:17
*** lpetrut has joined #openstack-meeting-315:17
rhochmuthnext review15:18
rhochmuthhttps://review.openstack.org/#/c/307963/15:18
bkleithat's 14WAATBIX's -- just wondering status15:18
bkleii'm ready to test it locally when told ot15:18
*** e0ne has joined #openstack-meeting-315:18
bkleito15:18
14WAATBIXIt should be ready for testing at the moment, I'm trying to get it set up in a large scale environment15:19
bkleiperfect -- will pull in this am and kick the tires15:19
rhochmuthit didn't pass gates15:19
rhochmuthis it really ready?15:19
*** mhoppal_ has quit IRC15:19
14WAATBIXits vertica code changes so the gate shouldn't be affected15:19
14WAATBIXthe python api tests failed in an alarm test15:20
rhochmuthmaybe just needs to be rechecked15:20
14WAATBIXnot sure why, but investigating15:20
bkleithat seems like a flaky test15:20
14WAATBIXit does, hopefully I can rewrite it15:20
bkleithx -- will give you feedback after i test your patch15:20
rhochmuththx15:20
14WAATBIXthnx15:21
rhochmuthhttps://review.openstack.org/#/c/28967515:21
bkleijust wondering if that dude is close15:21
bklei(multiple metrics)15:21
rhochmuthyup15:21
14WAATBIXIt might need to be rebased on the metric list changes15:22
rhochmuth14WAATBIX15:22
rhochmuth?15:22
rhochmuthso when metrics list merges you'll need to rebase15:22
bkleii'd guess -- poor 14WAATBIX15:22
14WAATBIXI think so, but I'm not 100% sure15:22
rhochmuthor which ever goes first15:22
rhochmuthbesides the rebase, are both reviews ready to go independently?15:23
14WAATBIXI think so15:23
rhochmuthbklei we are really interested in getting feedback on this one, namely performance analysis15:23
*** aviramb has quit IRC15:23
rhochmuthhopefully, we've significantly improved things15:23
rhochmuththis one will also impact any queries that you are doing15:24
*** zz_dimtruck is now known as dimtruck15:24
*** alexpilotti has quit IRC15:24
bkleiwe can provide feedback on perf -- but not so much pre-merge :(15:24
rhochmuthfor example, grafana will need to be enhanced to use the group_by query parameter15:24
bkleiour best perf tests are in prod15:24
bkleioh for sure15:24
bkleithat's gonna make some graphs scream15:24
rhochmuthwell, you might want to test this one before production15:24
rhochmutha few more moving parts15:25
rhochmuththe level of complexity is much higher15:25
bkleiwe can do a limited amount in the lab, but our best historic results are from prod, but we can get an indication15:25
bklei(we're talking multiple metrics -- not limit, yes?)15:25
*** spzala has joined #openstack-meeting-315:25
rhochmuthwe did test this change against the ceilosca code15:25
rhochmuthand saw a huge perf improvement15:26
*** salv-orlando has quit IRC15:26
rhochmuthbut, unfortuately no real numbers yet15:26
bkleii'm excited about this one15:26
*** numan_ has joined #openstack-meeting-315:26
rhochmuthso, after this change, i'm not sure about the "caching" solution15:26
rhochmuthmultiple metrics might actually work better than pursuing caching15:27
bkleiperhaps, things like metric-list would benefit, and that's a pig for us15:27
rhochmuthok, sounds like time to move on15:27
bkleimetric-list is 1GB of data in our 'infra' project15:27
rhochmuthbut, with start/end time you limit that down to something managable15:28
rhochmuthright15:28
bkleinot as much as it did before -- with grafana 215:28
rhochmuthalso, do you have automated cron josb to remove old data15:28
bkleiand even 'current' is huge15:28
bkleiyes15:28
bkleibut infra keeps 13mos15:28
bkleiso prune doesn't help that project much15:29
rhochmuthi see15:29
rhochmuthis there a way to control the range of data returned in grafana 215:29
rhochmuthi didn't see any15:29
bkleirbak can comment -- but i don't think so15:29
rhochmuthit should just be the current range15:29
rhochmuthright?15:30
rhochmuthlast hour15:30
rhochmuthlast day15:30
rbakI looked away for a moment.  I'm not sure I followed the conversation15:30
bkleisounds like the data source doesn't have visibility to graph range15:30
*** spzala has quit IRC15:30
bklei(providing timestamp to metric-list)15:30
rbakTemplating doesn't have access to the time-range15:30
rhochmuthso, when you are displaying metric names for example, can you limit the names that are returned to the current time range set in grafana 215:31
rbakThe graphs do.15:31
*** baoli has quit IRC15:31
rbakIt depends on how you do it.15:31
rhochmuthand templating is the part that dispays the names and dimensions?15:31
rbakIf you use templating, no15:31
rbakTemplating is the feature that queries for dimensions and lets use insert them into the graphs dynamically.15:32
rbakI'm not sure if that answers your question15:32
rhochmuthnot sure, but we can move one15:33
rhochmuthhow about, Heads up on ovs plugin (router bandwidth metrics)15:33
rhochmuthwhat is this about15:33
rhochmuthi saw the review15:33
bkleiyeah -- let's call this an advertisement15:33
bkleiit's not ready, just want to gain visibility/support15:33
bkleiour customers really want BW for virtual routers15:33
bkleiwe could do this locally, but thought others may want it too15:33
bkleipeople that use OVS/neutron15:34
rhochmuthyes, this could be very interesting15:34
*** ccamacho has quit IRC15:34
bkleiit's pretty much working needs some cleanup though15:34
rhochmuthso, syd will be interested and we're going to have a session next week with the neytron team too15:34
rhochmuthso, is this a discussion that we want to have next week in austin?15:34
bkleiok -- i'll add syd to the review -- and i'll join that discussion if you let me know when/where15:35
rhochmuththe fourth session on wednesday morning is the combined monasca/neutron/network discussion15:35
*** ajmiller_ has joined #openstack-meeting-315:35
bkleiperfect15:35
rhochmuthit will be only 40 minutes long15:35
*** ajmiller_ has quit IRC15:35
rhochmuthbut, we can also discuss more while we are there15:36
bkleisure, sounds good15:36
rhochmuthbut, i'm very interested in this development15:36
*** anilvenkata has quit IRC15:36
*** ccamacho has joined #openstack-meeting-315:36
bkleioh -- one question on my review15:36
rhochmuthso, i'll start taking a look at it15:36
rhochmuthsure go ahead15:36
bkleiis it required to add a 'detector'?15:36
bkleiwe don't use that process here15:36
*** ccamacho has quit IRC15:36
rhochmuthwhat do you mean?15:36
*** mhoppal_ has joined #openstack-meeting-315:36
bkleifor all plugins -- add a detector15:36
*** ajmiller has quit IRC15:37
rhochmuthdetection plugin15:37
bkleiright -- that15:37
*** Sukhdev has joined #openstack-meeting-315:37
rhochmuthwould be nice if it makes sense15:37
bkleiis that required for all plugins?15:37
rhochmuthnot all plugins have deteciton plugins though15:37
*** scheuran has quit IRC15:37
rhochmuthso not required15:37
rhochmuththe detection plugins configure the agent15:37
bkleiok -- i'll add it if folks request15:37
*** mhoppal has quit IRC15:38
*** 14WAATBIX has quit IRC15:38
rhochmuthand are run seperately, usually at install/deploy time15:38
rhochmuthsounds good15:38
*** rbrndt has joined #openstack-meeting-315:38
sloganI stepped away for a bit, yes, plenty to talk about Wednesday15:38
*** nikhil_k has joined #openstack-meeting-315:38
rhochmuthi'm not sure how detection woudl work in this case15:38
bkleiyeah, and we don't use that process, but can add it if folks want it15:38
*** jmckind has quit IRC15:38
bkleiyeah -- i'm not either15:38
*** ajmiller has joined #openstack-meeting-315:38
rhochmuthhi slogan, yes15:38
rhochmuthyou might want to take a look t that review if you haven't already15:39
*** ccamacho has joined #openstack-meeting-315:39
*** itxaka has quit IRC15:39
bkleihttps://review.openstack.org/#/c/30662115:39
sloganwill do15:39
*** ccamacho has quit IRC15:39
rhochmuthhre is the link, https://review.openstack.org/#/c/306621/15:39
bklei(it's not fully baked -- but close)15:40
*** nikhil has quit IRC15:40
bkleibut early comments welcome15:40
bkleiok -- i think that's it for me15:40
rhochmuthhttps://review.openstack.org/#/c/302660/15:41
rhochmuthmigrate from mysqldb to pymysql15:41
rhochmuthit looks good to me15:41
*** ccamacho has joined #openstack-meeting-315:41
rhochmuthjust need to run it once15:41
*** alexpilotti has joined #openstack-meeting-315:41
witekthere seems to be a problem with requirements15:41
*** hoppalm has joined #openstack-meeting-315:41
rhochmuthwitek: so that sounds like it isn't ready15:42
witekbut I did not investigate15:42
*** mhoppal_ has quit IRC15:42
witekthe gate job was successful previously15:42
Kamilwe are not so sure from where this error is comming15:42
witekI just changed the commit message15:42
KamilContextualVersionConflict: (Babel 2.3.3 (/home/jenkins/workspace/gate-monasca-agent-python27/.tox/py27/lib/python2.7/site-packages), Requirement.parse('Babel!=2.3.0,!=2.3.1,!=2.3.2,!=2.3.3,>=1.3'), set(['oslo.log']))15:42
rhochmuthit could be that something changes upstream15:43
rhochmuththat is impacting the agent15:43
rhochmuthnot sure15:43
hoppalmi think it is, all of our agent reviews are having that issue15:44
witekthat is also my first assumption15:44
hoppalmi was going to try to look into it sometime today if i get a chance15:44
rhochmuththat hoppalm15:44
rhochmuththx15:44
*** gema has joined #openstack-meeting-315:44
rhochmuthnot that15:44
witekwould be great, thanks michael15:45
rhochmuththat hoppalm is such a great guy15:45
witek:)15:45
bkleihotpalm :)15:45
*** iurygregory has quit IRC15:45
hoppalmmeanwhile roland is laughing as he types that15:45
bklei:)15:45
witekwe know him too much :)15:45
rhochmuthwitek: craig is reviewed tomasz's review15:46
witekgreat!15:46
rhochmuthhe sent me an email this mroning with some general questions15:46
*** alexpilotti has quit IRC15:46
rhochmuthbut he is diving in on this15:46
witekthanks a lot for that!15:46
rhochmuthi'm not sure i'll run into him here today, but i'm expecting he'll post some comments to the review soon15:47
witekthat would be best, or if longer, per email to me and Tomasz15:47
rhochmuthok15:48
rhochmuthso, are there any other reviews or questions?15:48
rhochmuthfor those in austin, i'm wondering if we should have dinner together one night15:49
*** slogan has quit IRC15:49
witekgood idea15:49
rhochmuththursday is probably the best, but i'm open to suggestions15:49
bkleithat would be great15:49
rhochmuthjust as long as bogdan doesn't pick the place15:49
*** dimtruck is now known as zz_dimtruck15:49
witekhaha15:50
rhochmuthactually, that was fun15:50
KamilOo15:50
*** cbouch has joined #openstack-meeting-315:50
rhochmuthi'll send an email out and try and coordinate15:51
*** tellesnobrega is now known as tellesnobrega_af15:51
rhochmuthshinya, you are going to be there15:51
*** baoli has joined #openstack-meeting-315:51
shinya_kwbtYes I will go to austin!15:51
rhochmuthhosanai, you are going to be there too?15:51
rhochmuthawesome15:52
shinya_kwbtI'm looking forward to seeing monasca folks.15:52
rhochmuthhave you been looking at cassandra, btw15:52
hosanaiyep15:52
rhochmuthme too15:52
*** thatsdone has quit IRC15:52
rhochmuthwitek, rbak, bklei, slogan15:52
shinya_kwbtSorry not yet, but I will15:52
rhochmuthno problem, was just checking15:52
rhochmuthalso, as i mentioned, we might want to consider ES too,15:53
rhochmuthas that is a part of the logging solution15:53
rhochmuthit would help with deploys15:53
*** tellesnobrega_af is now known as tellesnobrega15:53
rhochmuthfabiog will be there too15:53
rhochmuthif there is anyone else that is going to austin that i've missed please let me know15:54
*** slogan has joined #openstack-meeting-315:54
*** spzala has joined #openstack-meeting-315:54
witekKouji15:54
rhochmuthgreat15:54
hosanaimy colleague, daisuke15:54
rhochmuththanks hosanai15:55
*** iurygregory has joined #openstack-meeting-315:55
rhochmuthi'll get him on the email list too15:55
rhochmuthwe'll coordinate while we are there, but just in case15:55
hosanaithanks roland!15:55
rhochmuthi wanted to have the names15:55
*** spzala_ has joined #openstack-meeting-315:55
rhochmuththe MOnasca bootcamp is on MOnday15:56
rhochmuthif folks are available to help that would be great15:56
*** lcazares has joined #openstack-meeting-315:56
rhochmuthmy plan is to go thorugh an iPython notebook15:56
rhochmuthwhich will have lot's of example of using the API15:56
rhochmuthand cover other topics15:56
sloganI'll be there15:56
*** Kamil has quit IRC15:56
bkleiditto15:56
rhochmuthit is supposed to he hands-on15:56
sloganwhat kind of help do you anticipate needing?15:57
witekI'll be there15:57
rhochmuthbut given it is only 1 1/2 hour not sure that we can spend 1/2 hour just setting up VMs15:57
rhochmuththanks everyone15:57
rhochmuthi'll introduce everyone that is there15:57
*** lcazares has quit IRC15:57
rhochmuthalso, please look at the other sessions invovling monasca15:57
rhochmuthtwc, fujitsu, cisco all have sessions15:58
rhochmuthand don't forget wednesday morning15:58
*** spzala has quit IRC15:58
rhochmuththose are all the monasca working sessions15:58
*** salv-orlando has joined #openstack-meeting-315:58
rhochmuththere are also some other sessions on monasca or involving monasca in some capacity that are showing up15:59
sloganI missed the ones by fujitsu and cisco, I'll go back and look for them15:59
sloganawesome15:59
rhochmuthfujitsu is on the logging api/service15:59
*** lcazares has joined #openstack-meeting-315:59
sloganif you have a must see list you are keeping, maybe share that?15:59
rhochmuthciscso one is related to congress15:59
*** catherineD has joined #openstack-meeting-315:59
rhochmuthand policy management15:59
rhochmuththere are also some session on logging that look interesting15:59
rhochmuthok, i think that is done16:00
rhochmuthbye-bye everyone16:00
slogansee you next week16:00
rhochmuthi always cram until the end16:00
*** Rockyg has joined #openstack-meeting-316:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Apr 20 16:00:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-04-20-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-04-20-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-04-20-15.00.log.html16:00
*** cbellucci has quit IRC16:00
*** hosanai has left #openstack-meeting-316:00
shinya_kwbtbye16:01
eglute#startmeeting defcore16:01
markvoelker#startmeeting defcore16:01
openstackMeeting started Wed Apr 20 16:01:14 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: defcore)"16:01
openstackThe meeting name has been set to 'defcore'16:01
openstackmarkvoelker: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.16:01
eglute#chair markvoelker16:01
openstackCurrent chairs: eglute markvoelker16:01
gemao/  (half attending only, also in another meeting)16:01
hogepodgeo/16:01
eglutehello everyone! here is the agenda: #link https://etherpad.openstack.org/p/DefCoreRing.2016:02
docaedoo/16:02
catherineDo/16:02
hogepodgemeetbot seems to be having issues16:02
*** rbrndt has left #openstack-meeting-316:02
eglutehogepodge how so? seems to work?16:02
*** rhochmuth has left #openstack-meeting-316:02
markvoelker#topic Finalize next.json as a solid draft to present during the summit16:02
*** openstack changes topic to "Finalize next.json as a solid draft to present during the summit (Meeting topic: defcore)"16:02
markvoelkerhogepodge: I think that may have been Egle and I typing startmeeting at the same time. =)16:03
*** hoppalm has quit IRC16:03
hogepodgeah ha16:03
markvoelkerSo, we have a couple of patches left to land16:03
markvoelker#link https://review.openstack.org/#/c/290592/16:03
*** witek has left #openstack-meeting-316:03
markvoelkerhogepodge, did you want to talk about the role issue mentioned in the etherpad for this one?16:04
hogepodgeThere is a SwiftOperator role that is required for the tests, and for the ACL capabilities.16:04
*** zz_dimtruck is now known as dimtruck16:04
*** slogan has quit IRC16:04
*** ddieterly is now known as ddieterly[away]16:04
hogepodgeWe wanted some clarification of if this violated the "no admin" rule. Turns out that the SwiftOperator role is meant more as an organizational "admin" role, rather than a system "admin" role. It doesn't grant privileges beyond managing ACLs16:05
*** banix has joined #openstack-meeting-316:05
hogepodgeWhich to me, makes it non-admin in the context of defcore. We would expect a user in a public cloud being granted this role to fully take advantage of Swift's features16:06
hogepodgeI checked on this with notmyname yesterday during discussion of the update16:06
markvoelkerI'd agree (hence my +2 on the patch).  I researched a couple of public clouds just to be sure and it's expectd.16:06
*** spzala_ has quit IRC16:07
*** vtech_ has quit IRC16:07
markvoelkerAnything other discussion on this one?16:07
catherineDyes16:07
*** spzala has joined #openstack-meeting-316:07
catherineDare the tests added from tempest plugin?16:07
hogepodgecatherineD: no, those are from tempest16:08
catherineDhogepodge: thx16:08
*** spzala_ has joined #openstack-meeting-316:08
eglutesounds good to me. glad notmyname had a chance to review and provide feedback16:08
markvoelkerOk, absent any last minute objections I'll merge this today.16:08
eglutethank you markvoelker16:09
markvoelker#link https://review.openstack.org/#/c/290271/ cinder scoring16:09
hogepodgeI rebased and fixed the patch this morning16:09
eglutethanks hogepodge16:09
markvoelkerOk, cool.  I saw the new patchset go up this morning but haven't had a chance to look at it yet16:09
hogepodgeThere will be a merge conflict. I'll resolve once the first one lands.16:10
egluteit looks good to me16:10
markvoelkerNot much dissent on this one so far I think, so I'll plan on landing this too.16:11
*** ddieterly[away] is now known as ddieterly16:11
*** spzala_ has quit IRC16:11
markvoelkerOk, I think that's all for capabilities that we have remaining16:11
*** spzala_ has joined #openstack-meeting-316:12
*** ddieterly is now known as ddieterly[away]16:12
markvoelkerOne other review to point out for this Guideline: https://review.openstack.org/#/c/306229/16:12
*** spzala has quit IRC16:12
markvoelker#link https://review.openstack.org/#/c/306229/ Add cutoff_score field to next.json16:12
markvoelkerWe added a cutoff_score field in the last rev of the Guideline schema, but haven't actually added that field to next.json yet16:13
markvoelkerThis patch does that and also updates the scoring script to make use of it16:13
hogepodgeLGTM16:13
markvoelkerIt'll need a little rebase, but I'll let the other scoring patches land before doing that16:13
eglutemarkvoelker i think it also needs to be added to 2016.0116:13
markvoelkereglute: can do16:14
eglutesince it also uses 1.4 schema16:14
markvoelkerOk, moving on?16:14
eglutethank you markvoelker16:14
egluteyes16:14
markvoelker#topic Closing the coverage gap16:14
*** openstack changes topic to "Closing the coverage gap (Meeting topic: defcore)"16:14
catherineDJust content update in 2016.01 riht? no schema update?16:14
markvoelkercatherineD: correct16:14
markvoelker#link https://review.openstack.org/#/c/306229/16:14
markvoelkerAs we discussed last week, there's currently no Guideline that covers Mitaka and we have someone wanting to get a logo agreement for a Mitaka-based product16:15
catherineDRefStack uses schema to render Guideline so we are sensitive to schema change16:15
eglutecatherineD the same change would go on 2016.01.json https://review.openstack.org/#/c/306229/2/next.json16:15
*** alexpilotti has joined #openstack-meeting-316:15
eglutewe just missed that field in .json files16:15
eglutehere is the schema: #link https://github.com/openstack/defcore/blob/master/doc/source/schema/1.4.rst16:16
catherineDeglute: RefStack should be OK thax16:16
egluteglad to hear it!16:16
markvoelkerThis patch changes 2016.01 to allow it to cover Mitaka.  The Board will need to approve that change.16:17
eglutei think we have a consensus on the fomat... any objections?16:17
markvoelkerIt looks like we have rough consensus on the change from our end, so if folks could please add their final +1 or suggest any further changes they want, we'll ask the Board for approval on Sunday.16:17
eglute#link https://review.openstack.org/#/c/306614/16:18
*** RP_ has quit IRC16:18
mfranc213davidsha: pong16:18
mfranc213hello david!16:18
*** bpokorny_ has joined #openstack-meeting-316:18
hogepodgemfranc213: we're in a meeting. please use another channel16:19
markvoelkerhmmm, that link is wrong, one moment16:19
markvoelker#link https://review.openstack.org/#/c/306614/ Close coverage gap16:19
eglutewhich link?16:19
*** watanabe_isao has quit IRC16:21
markvoelkerEgle: the one in the etherpad for this topic.  It was pointing to the cutoff_score review, not the close coverage gap review.16:21
markvoelkerJust fixed it16:21
eglutethank you16:21
markvoelkerAnything further folks want to discuss on this one?16:21
eglutelooks good to me...16:21
*** bpokorny has quit IRC16:22
markvoelkerOk then, let's move on.16:22
hogepodgejust clarification on if we use future release at time of guideline approval or at release time, and codify adding that without needing to go back to the board16:22
markvoelker#topic DefCore Spec16:22
*** openstack changes topic to "DefCore Spec (Meeting topic: defcore)"16:22
markvoelkerhogepodge: my plan was to do it at approval time so we don't have to keep bugging the Board (hence the change both to 2016.01 and next.json)16:23
eglutehogepodge i think we will use future at guideline approval16:23
hogepodgethanks16:23
hogepodgecarry on  :-D16:23
markvoelker#link http://lists.openstack.org/pipermail/defcore-committee/2016-April/001085.html ML discussion16:23
markvoelker#link https://etherpad.openstack.org/p/DefCoreSpec-draft Spec draft16:24
gemawill go back to that soon, please add any ideas/comments to it :)16:24
markvoelkerSeveral folks have been adding notes to the pad, which is a good start.  I think we're probably in a good position to take some time at the Summit during the working session to see if we can come up with a firm draft and put it up in Gerrit.16:24
markvoelkerSo unless there are objections, I'll plan on adding it to the agenda.16:25
eglute+116:25
gemamarkvoelker: ok, I won't be in the summit so someone else will have to drive that one :D16:25
hogepodgegema: I can help out with that16:25
gemahogepodge: +116:25
gemathanks16:25
markvoelkergema: Bummer, we will miss you.  But yes, we'll get it covered. =)16:26
hogepodgegema: thank you, it's a great start16:26
gemamarkvoelker: cool :D I will add all I can think of beforehand then16:26
markvoelkergema: yes please16:26
markvoelker(and that goes for the rest of you lot as well =p)16:26
luzCok16:26
*** spzala_ has quit IRC16:26
markvoelker#action please make any additional comments on the etherpad ahead of the Summit so we can have a productive work session16:26
markvoelkerAnything folks want to discuss on this right now?  We have a little available time today I think.16:27
markvoelkerOk, hearing none...16:28
luzCquick question any news about heat tempest plugin priority?16:28
eglutei think it is a good start16:28
*** cbouch has quit IRC16:29
catherineDthere will be a heat work session https://www.openstack.org/summit/austin-2016/summit-schedule/events/924716:29
eglutewould it be worthwhile to discuss atomicity?16:29
egluteright now there is no definition in the spec16:29
catherineDplease note the session is now at 3:30 - 4:10 on Wednesday16:29
*** galstrom_zzz is now known as galstrom16:29
eglutesorry, there is some definition, getting ahead of myself16:30
VanLThere is a definition of sorts16:30
eglutecatherineD thank you... did not see that.16:30
eglutei will be sending calendar invite to the working group session16:30
VanLA functional test is atomic if, after excluding fixture setup and cleanup, exactly one aspect of an API is exercised.16:30
VanLAnd there is some discussion in the document about "should" vs "must"16:31
catherineDeglute: please do .. They reschedule the time so please update you calendar ... I put the new link on the DefCore etherpad16:31
*** tellesnobrega is now known as tellesnobrega_af16:31
luzCcatherineD thanks, I'll add it to my calendar too16:32
egluteVanL i like the "must" part for atomicity16:32
*** ddieterly[away] is now known as ddieterly16:33
eglutehogepodge what do you think so far of the atomicity?16:34
markvoelkerI'll just note that when considering applying something as a "must" it would probably be good to look at our existing required tests and see how many of them would meet the bar we're creating16:34
hogepodgeIt's a complicated issue. I don't want to see a huge set of tests invalidated because of the requirement.16:34
markvoelkerThat's not to say we should or shouldn't use must, just that it would be informative.16:34
hogepodgeWe also have capabilities that are group as CRUD, so I could see tests that do CRUD16:35
eglutewe could say that going forward we will aim for tests to meet the specs. and start working on non-atomic first16:35
eglutehogepodge i think those would be scenario tests, no?16:35
hogepodgeBy starting at should, we get a path to refining the guideline without massive disruption.16:35
VanLI don't think that a "CRUD" capability starts by doing all of CRUD16:35
hogepodgeOh yes, and scenario tests, most definitely not atomic.16:36
VanLIt means that we have a "create" test, a "read" test, etc16:36
VanLhogepodge: I don't think that anyone is disputing non-atomic scenario tests16:36
hogepodgePlus theres the issue of the fixtures, which seems to be addressed by the proposed definition.16:36
hogepodgeI am opposed to any definition that a) is an attempt to flag and remove a large number of existing tests without attempting to "fix" or replace them, and b) is used as a tool to "justify" a fork of tempest as our primary test suite.16:38
hogepodgeso starting with should gives us a criteria to work on with the qa team16:38
*** spzala has joined #openstack-meeting-316:39
VanLA refactoring of any functional test to be one or more atomic tests would improve the test suite for all purposes, not just for defcore16:39
eglutehogepodge i dont think the spec would be a blank permission to do either. i would propose that we grandfather existing tests and then work to improve them.16:40
markvoelkerhogepodge: Fair.  We also have the option of not enforcing the spec immediately, but rather using it as a guidepost for discussions on refactoring.16:40
eglutebut we do need to improve the tests16:40
*** ihrachys has quit IRC16:40
*** mickeys has joined #openstack-meeting-316:41
markvoelkerOk, good things to note in the pad and bring up for discussion at the Summit16:41
hogepodgeI'm not saying there's no room for improvement.16:41
markvoelker20 minutes left, so perhaps we should move on to the last couple of topics for today?16:41
catherineDSo atomic test would include fixture and setup ... does the test fail if the fixture or setup/cleanup fail?16:41
eglutecatherineD good question, it should be addressed in the spec16:41
VanLTest only fails if the test fails16:41
hogepodgeA test should only pass if it passes.16:42
catherineDbut if cleanup fail ... test may not be in a good condititon for futher testing16:42
hogepodgewe treat skips as failures16:42
VanLFixtures would be swappable. The test code itself is inviolate16:42
*** spzala has quit IRC16:43
catherineDwe havve a real life test case right now in the cinder volume mounting area16:43
eglutecatherineD can you link to it?16:43
VanLcatherineD: Explain16:44
catherineDThe volume mount test passes but the cleanup by  unmounting the volume fails16:44
eglutecatherineD do we consider that a test failure?16:44
*** spzala has joined #openstack-meeting-316:45
catherineDeglute: https://bugs.launchpad.net/nova/+bug/156585916:45
openstackLaunchpad bug 1565859 in OpenStack Compute (nova) "Can't detach SVC volume from an instance; guest detach device times out" [Undecided,Invalid]16:45
*** vtech has joined #openstack-meeting-316:45
catherineDso right  now the test count as fail... but should we?16:45
catherineDFailure is by status provided by Tempest16:45
catherineDso from tempest point of view it fails16:45
VanLSo I would characterize that as a "Pass" on the test, but it would point to a separate need for an "unmount" test and capability if we want to ensure that16:46
eglutethis is excellent point... looking at this example, test should not be considered as failed16:46
catherineDbut from DefCore atomic test feature testing point of view it should pass16:46
*** Swami has quit IRC16:46
egluteright.. i think unmount should be a separate test16:46
hogepodgethe failure still pointed out a problem with the cloud, a buggy and old driver, and the problem was fixed when the downstream error was fixed, so the test was a success in identifying a real problem16:47
VanLSo it may be a good QA test, but it is a bad defcore test16:47
hogepodgeso yes, split the tests to catch it, but it doesn't make the test immediately invalid. It served a purpose16:47
eglutebugs will happen in tests and in frameworks, so we need to see what would be easiest for someone trying to certify16:47
catherineDso from technical mechanical testing point of view  .. it is hard to define pass/fail16:47
hogepodgeno, it's not, because it would have caught an interoperability problem16:47
eglutehogepodge we cannot expect everyone trying to certify try to fix all the issues before they certify16:48
hogepodgebut yes, it can be improved.16:48
*** bklei has quit IRC16:48
catherineDhogepodge: so in that case the test should count as fail?16:48
VanLA bug is not necessarily an interop problem, it is a bug16:48
eglutei agree with VanL16:49
hogepodgecatherineD: yes, because downstream had a problem16:49
VanLQA is not the same as defcore16:49
*** spzala has quit IRC16:49
eglute+116:49
catherineDhogepodge: but the capability we are testing is mount ...16:49
hogepodgeit's a problem if features don't work for end users16:49
catherineDif the testing is unmount then I agree16:49
VanLhogepodge: And the mount worked for the end user.16:49
catherineDthis is the point about test atomic16:49
hogepodgeit's unfair to end users to flag away implementation bugs and call yourself interoperable16:49
*** atuvenie has quit IRC16:49
egluteit is unfair to the everyone to lump everything in one thing16:50
VanLNo, this is about improving the test suite and making it say what we mean16:50
catherineDif we count that test case as fail ... we vilolate what we just define as "atomic"16:50
egluteDefCore should not test the tests or the testing framework16:50
hogepodgeif you can't manage a fixture it's still a problem16:50
egluteDefCore should test interoperability16:50
VanLI think what happens is you identify the need for an unmount test16:50
*** watanabe_isao has joined #openstack-meeting-316:50
hogepodgeespecially if the capability falls under crud16:50
*** spzala has joined #openstack-meeting-316:50
VanLThen each of "CRUD" needs to be tested seperately16:51
hogepodgeyes, the correct action is to split out the tests and reassign as necessary16:51
eglutehogepodge i think that is a different case. crud and scenario tests are separate from atomic tests.16:51
hogepodgebut it's still a failure16:51
VanLA fixture failure is not a failure16:51
markvoelkerOk gang, 10 minutes. =)  I think I hear you all saying "we should find ways to improve tests" and that we have a lot of discussing to do about how to get there, which we can hopefully have some good discussion about in Austin.  Fair?16:51
hogepodgeand in that case, the failure was an implementation bug16:51
VanLIf the fixture can be swapped and the test succeeds16:51
catherineDso we are saying taht fixture/setup/cleanup failure counts as test failure?16:51
VanLcatherineD: fixture/setup/cleanup *should not* count as test failure16:52
eglutecatherineD i think that is what hogepodge is saying. I disagree with that16:52
hogepodgeand in my experience over the last year, vendors flag tests but then don't fix the tests they flag16:52
*** ddieterly is now known as ddieterly[away]16:52
catherineDeglute: +116:52
eglutehogepodge that is a separate issue we should address16:52
hogepodgeVanL: if the test isn't run to completion it's counted as a fail16:53
markvoelkerGotta call time folks.  We still have two more topics today.16:53
markvoelker#topic Austin summit16:53
*** openstack changes topic to "Austin summit (Meeting topic: defcore)"16:53
catherineDthis is an issue of how we define "atomic" test16:53
markvoelker#link https://etherpad.openstack.org/p/refstack-newton-summit Summit etherpad16:54
markvoelkerPlease make sure your topics get added to that pad.  I'll work on finalizing the working session agendas by the end of the week.16:54
eglutethat is refstack link16:54
markvoelkerwhoops16:54
markvoelker#link https://etherpad.openstack.org/p/DefCoreRing.AustinSummit201616:54
markvoelker(thanks elgute)16:54
*** spzala has quit IRC16:55
markvoelkerThere are also some other sessions that are likely to interest DefCore folks listed in today's meeting etherpad16:55
eglute(but also add topics to refstack, on refstack etherpad)16:55
*** Sukhdev has quit IRC16:55
catherineDeglute: thanks :-)16:55
markvoelkerIf you have others, feel free to stick them on there16:55
hogepodgeI've arranged a joint DefCore/QA working session, following the DefCore working session.16:56
eglutethanks hogepodge16:56
*** alexpilotti has quit IRC16:56
egluteplease be sure QA understands what defcore is16:56
markvoelkerOk, we already hit the cutoff score topic, so I'll jump straight o our last topic for the day:16:57
markvoelker#topic DefCore in Launchpad16:57
*** openstack changes topic to "DefCore in Launchpad (Meeting topic: defcore)"16:57
markvoelkerhogepodge: take it away16:57
*** andymaier has quit IRC16:57
hogepodgecompleted the action item from last week, this was in response for the need to manage blueprints16:57
*** ddieterly[away] is now known as ddieterly16:58
hogepodgewe didn't need any special support from infra or the TC, but we do have an administrators group for it on launchpad.16:58
hogepodgeI'll add egle to it, and anyone else that we feel is appropriate to add.16:58
eglutethank you hogepodge16:58
hogepodge(I don't have any issues with adding anyone who wants to be on it, but I started with co-chairs)16:58
markvoelkerhogepodge: that looks fine as a starter list.  We can discuss mechanics later.16:59
*** amotoki has quit IRC16:59
markvoelker(as we're down to our last minute)16:59
markvoelkerAny final thoughts before we switch back to #openstack-defcore?16:59
markvoelker#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Apr 20 17:00:05 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-04-20-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-04-20-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-04-20-16.01.log.html17:00
*** vhoward has joined #openstack-meeting-317:02
*** spzala has joined #openstack-meeting-317:02
*** MarkAtwood has quit IRC17:04
*** bpokorny_ has quit IRC17:06
*** mbound has joined #openstack-meeting-317:06
*** spzala has quit IRC17:07
*** bpokorny has joined #openstack-meeting-317:07
*** numan_ has quit IRC17:08
*** mickeys has quit IRC17:11
*** claudiub has joined #openstack-meeting-317:11
*** mickeys has joined #openstack-meeting-317:11
*** iyamahat has quit IRC17:12
*** mickeys has quit IRC17:12
*** mickeys has joined #openstack-meeting-317:12
*** yamahata has quit IRC17:12
*** scsnow_ has joined #openstack-meeting-317:13
*** scsnow_ has left #openstack-meeting-317:13
*** mtanino has joined #openstack-meeting-317:14
*** neelashah has quit IRC17:16
*** Guest17033 is now known as melwitt17:19
*** neelashah has joined #openstack-meeting-317:22
*** lcazares has quit IRC17:25
*** mbound has quit IRC17:26
*** lcazares has joined #openstack-meeting-317:26
*** MarkAtwood has joined #openstack-meeting-317:29
*** iyamahat has joined #openstack-meeting-317:32
*** dhague_ has quit IRC17:32
*** alexpilotti has joined #openstack-meeting-317:32
*** yamahata has joined #openstack-meeting-317:33
*** ccarmack1 has joined #openstack-meeting-317:35
*** s3wong has joined #openstack-meeting-317:35
*** spzala has joined #openstack-meeting-317:40
*** tellesnobrega_af is now known as tellesnobrega17:41
*** sdake__ has joined #openstack-meeting-317:41
*** jmckind has joined #openstack-meeting-317:42
*** dedery has joined #openstack-meeting-317:43
*** sdake__ has quit IRC17:43
*** sdake_ has quit IRC17:43
*** sdake_ has joined #openstack-meeting-317:45
*** sambetts is now known as sambetts|afk17:46
*** jmckind has quit IRC17:46
*** ccamacho has quit IRC17:51
*** jaypipes has joined #openstack-meeting-317:52
*** sdake__ has joined #openstack-meeting-317:53
*** jed56 has quit IRC17:53
*** neelashah has quit IRC17:57
*** sdake_ has quit IRC17:57
*** ddieterly is now known as ddieterly[away]17:57
*** pvaneck has joined #openstack-meeting-317:59
*** spzala has quit IRC17:59
*** spzala has joined #openstack-meeting-318:01
*** spzala has quit IRC18:06
*** alexpilotti has quit IRC18:07
*** neelashah has joined #openstack-meeting-318:07
*** lpetrut has quit IRC18:09
*** lcazares is now known as Guest7490518:11
*** luzC is now known as lcazares18:11
*** abalutoiu has quit IRC18:12
*** spzala has joined #openstack-meeting-318:13
*** sdake__ has quit IRC18:14
*** anilvenkata has joined #openstack-meeting-318:15
*** watanabe_isao has quit IRC18:15
*** MarkAtwood has quit IRC18:15
*** lcazares has quit IRC18:15
*** luzC has joined #openstack-meeting-318:16
*** spzala has quit IRC18:18
*** luzC- has joined #openstack-meeting-318:19
*** spzala has joined #openstack-meeting-318:19
*** luzC- has quit IRC18:20
*** Sukhdev has joined #openstack-meeting-318:23
*** alexpilotti has joined #openstack-meeting-318:23
*** rmoe has joined #openstack-meeting-318:23
*** rmoe_ has quit IRC18:23
*** spzala has quit IRC18:24
*** Sukhdev has quit IRC18:24
*** luzC- has joined #openstack-meeting-318:24
*** spzala has joined #openstack-meeting-318:24
*** alexpilotti has quit IRC18:25
*** alexpilotti has joined #openstack-meeting-318:25
*** luzC has quit IRC18:25
*** luzC- is now known as luzC18:25
*** Sukhdev has joined #openstack-meeting-318:28
*** lcazares has joined #openstack-meeting-318:28
*** alexpilotti has quit IRC18:29
*** yamamoto has quit IRC18:31
*** egafford has joined #openstack-meeting-318:34
*** galstrom has quit IRC18:35
*** galstrom has joined #openstack-meeting-318:35
*** woodster_ has joined #openstack-meeting-318:39
*** oanson has joined #openstack-meeting-318:42
*** ociuhandu has quit IRC18:43
*** ociuhandu has joined #openstack-meeting-318:43
*** sigmavirus24 is now known as sigmavirus24_awa18:45
*** aarefiev_ has quit IRC18:45
*** doug-fish has quit IRC18:47
*** catherineD has left #openstack-meeting-318:47
*** vishwanathj has quit IRC18:50
*** vishwanathj has joined #openstack-meeting-318:50
*** ddieterly[away] is now known as ddieterly18:54
*** e0ne has quit IRC18:55
*** sigmavirus24_awa is now known as sigmavirus2418:56
*** ociuhandu has quit IRC18:59
*** dimtruck is now known as zz_dimtruck18:59
*** galstrom has quit IRC19:00
*** tqtran has joined #openstack-meeting-319:00
*** galstrom has joined #openstack-meeting-319:00
*** salv-orlando has quit IRC19:03
*** zz_dimtruck is now known as dimtruck19:03
*** doug-fis_ has joined #openstack-meeting-319:07
*** stanzgy has joined #openstack-meeting-319:08
*** toddjohn_ has quit IRC19:09
*** lpetrut has joined #openstack-meeting-319:11
*** rocky_g has joined #openstack-meeting-319:12
*** stanzgy has quit IRC19:13
*** ihrachys has joined #openstack-meeting-319:14
*** matrohon has joined #openstack-meeting-319:17
*** ociuhandu has joined #openstack-meeting-319:18
*** ccamacho has joined #openstack-meeting-319:18
*** ihrachys_ has joined #openstack-meeting-319:18
*** alexpilotti has joined #openstack-meeting-319:21
*** ihrachys has quit IRC19:21
*** matrohon has quit IRC19:23
*** matrohon has joined #openstack-meeting-319:25
*** alexpilotti has quit IRC19:25
*** salv-orlando has joined #openstack-meeting-319:26
*** yamamoto has joined #openstack-meeting-319:31
*** e0ne has joined #openstack-meeting-319:33
*** kenji-i has joined #openstack-meeting-319:34
*** matrohon has quit IRC19:36
*** matrohon has joined #openstack-meeting-319:39
*** yamamoto has quit IRC19:39
*** toddjohn_ has joined #openstack-meeting-319:45
*** Sukhdev has quit IRC19:46
*** dtardivel has quit IRC19:48
*** toddjohn_ has quit IRC19:49
*** tyr_ has joined #openstack-meeting-319:49
*** tsufiev has joined #openstack-meeting-319:51
*** mrmartin has joined #openstack-meeting-319:52
*** ankur-gupta-f has joined #openstack-meeting-319:54
*** robcresswell has joined #openstack-meeting-319:56
*** neelashah has quit IRC19:57
*** alexpilotti has joined #openstack-meeting-319:57
*** ediardo has joined #openstack-meeting-319:58
*** dimtruck is now known as zz_dimtruck19:59
*** TravT has joined #openstack-meeting-319:59
robcresswell#startmeeting horizondrivers20:00
openstackMeeting started Wed Apr 20 20:00:16 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizondrivers)"20:00
openstackThe meeting name has been set to 'horizondrivers'20:00
david-lyleo/20:00
lcastello/20:00
ediardoo/20:00
ankur-gupta-fo/20:00
bpokornyo/20:00
tsufievo/20:00
*** jlopezgu_ has joined #openstack-meeting-320:01
robcresswellHi all20:01
tqtran[=_=]/20:01
*** ddieterly is now known as ddieterly[away]20:01
*** zz_dimtruck is now known as dimtruck20:01
robcresswellJust one notice to start20:01
jlopezgu_Hi20:01
robcresswell#topic Summit schedule20:01
*** openstack changes topic to "Summit schedule (Meeting topic: horizondrivers)"20:01
robcresswell#link https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Horizon%3A20:01
robcresswellThis is the Horizon room topic if you need to refer back, but wanted to bring it up anyway20:02
TravTo/20:02
robcresswellSo make sure you attend the sessions :D20:02
david-lylewe're tagged in a talk titled "fail." so that's promising20:02
*** matt-borland has joined #openstack-meeting-320:02
robcresswellYeah I saw that20:02
robcresswellVery encouraging20:03
david-lyleI'm sure they mean it in the best possible way20:03
*** ducttape_ has joined #openstack-meeting-320:03
robcresswellAny other notices before I move on to blueprints?20:03
kenji-io/20:04
robcresswell#topic Blueprint Review20:04
*** openstack changes topic to "Blueprint Review (Meeting topic: horizondrivers)"20:04
*** ddieterly[away] is now known as ddieterly20:04
robcresswellThere's several bps on the agenda20:04
*** hurgleburgler has joined #openstack-meeting-320:04
*** rbak has quit IRC20:04
robcresswell#link https://wiki.openstack.org/wiki/Meetings/HorizonDrivers#Agenda_for_2016-04-20_2000_UTC20:04
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/operation-history-log20:05
robcresswellkenji-i: If you want to add anything to the explanation, go ahead :)20:05
robcresswellducttape_: This sounds similar to a feature you mentioned before?20:06
kenji-irobcresswell: okay, thanks :)20:06
* ducttape_ reads up on that one20:06
* tsufiev is curios how many operators assign different accounts to different people20:07
robcresswellBasically its about logging the actions that users take within Horizon20:07
kenji-irobcreddwell: yes, this fieature to log an operation on Horizon20:08
*** lhcheng has joined #openstack-meeting-320:08
tyr_this sounds similar to an audit logging request we've been looking at. Instead of adding to our logs, it inserts Keystone WSGI middleware to log any API requests to Horizon server20:08
ducttape_that would be somewhat helpful.  I would expect larger deployments to also have something like splunk aggregating all the actions too20:08
*** egafford has left #openstack-meeting-320:08
david-lylekenji-i: this seems like something that should be outside Horizon20:09
ducttape_some of the need for that, would be for having a view into api calls made by admins - cli or within horizon20:09
david-lyleI don't want to pass the buck, but it misses all API and CLI calls20:09
tqtrandoesnt ceilometer does this to some degree?20:09
david-lyleso you only get part of the story20:10
david-lylenova has the events log which we show20:10
tyr_see also: http://docs.openstack.org/developer/keystonemiddleware/audit.html20:10
ducttape_not sure to what degree ceilometer would help here tqtran, maybe a bit20:10
kenji-iI think in some cases, there are required to log an access log.20:11
ducttape_thats the logging part, yes tyr_, but then you need to aggregate all the logs everywhere, combine them, then have a powerful ui to query them20:11
kenji-inot api call but operation by user20:11
tyr_smells like search ;)20:11
*** oanson has quit IRC20:11
ducttape_it's splunk, in a nutshell20:11
lhchengthere's more standard auditing, use pycadf20:12
lhchengwe already have audit middleware for that20:12
*** anilvenkata has quit IRC20:12
lhchengthe audit can be pushed to a queue or something for recording purposes20:12
ducttape_but that requires operators to consolidate / aggregate logs etc , right lhcheng ?20:12
lhchengyeah, up to the operator to determine what they want to do with the audit log20:13
ducttape_so, back to the bp at hand, I think it is somewhat useful, but it will be a partial solution20:13
ducttape_right ?20:14
robcresswellDepends if we want to carry a partial solution in Horizon (and even if we should carry that logic at all) ?20:14
tqtranif you want to add a panel to support this view, thats entirely possible and welcomed. but consolidating/aggregating logs is beyond what horizon can do20:14
tyr_I agree. Auditing Horizon is a good step...but only part of the problem. Often cloud actions occur outside of the UI.20:14
ducttape_right tqtran, this much is certain20:14
ducttape_I would see this more of a contrib panel, if operators use splunk  (or other alternatives)20:15
tyr_I think we should first focus on logging rest calls to the Horizon server in a way that is consistent with the REST calls to other services...before worrying too much about a UI to expose those logs.20:15
ducttape_so the other side should be logging it tyr_, not to say that horizon logging is great - there is room for improvement20:16
ducttape_but if I have to aggregate all of cinder/glance/neutron etc logs anyways, I'll just use that location20:16
david-lylethis is basically turning up the log level20:16
david-lylewe can already do that20:16
david-lylenot entirely sure where the userid fits in though, TBH20:17
ducttape_I think there is value in this type of feature, but you will need to assume a certain way to aggregate and gather all the logs20:17
*** r1chardj0n3s has joined #openstack-meeting-320:18
ducttape_also, if horizon is setup behind a load balancer, you'd need to show all the actions from all the horizon servers etc20:18
tsufievosprofiler library stores messages about API calls in mongodb (one of possible backends)20:18
ducttape_that would work tsufiev20:18
david-lyletsufiev: you're not running osprofiler in production are you?20:18
*** ccamacho has quit IRC20:18
tsufievbut it was designed with a slightly different goal in mind...20:18
david-lyleall the time20:19
tsufievdavid-lyle, not yet, and I don't know if it could be switched on _permanently_20:19
david-lylethat's a pretty faulty audit solution then :P20:19
tsufieva great amount of data, it would be20:19
robcresswellYeah we're getting off topic with osprofiler20:20
tsufievbut I'll ask rally folks if they though about that use-case20:20
ducttape_should we just say that this bp needs more info on how the data is stored / aggregated ?20:20
robcresswellYeah I've just been scanning the patch itself20:20
tyr_at a high-level, I'd like a Horizon logging solution to be consistent with other services.20:20
david-lylemy thought is if auditing isn't done outside of Horizon, it's too incomplete to be useful20:21
ducttape_+120:21
lhchengthere's already auditing solution in place, why are we re-inventing the auditing solution?20:21
ducttape_that is a partial solution lhcheng, but its the best start we have20:22
lhchengyeah, we could improve and contribute on that. but let's not start another project :)20:22
david-lylebig tent requires more projects, it's a pyramid scheme20:23
ducttape_ok, so lhcheng would like to start another project, I second this motion20:23
robcresswellGreat20:23
david-lylewe don't make money without more new projects20:23
lhchenglol20:23
*** ccamacho has joined #openstack-meeting-320:23
david-lyleexcuse me multi-level marketing20:23
robcresswellI quite liked the contrib idea. If there is some value in holding this, we could hold it in contrib and see if it can extended beyond that for a more complete solution.20:24
ducttape_ground floor level opportunities20:24
ducttape_yep robcresswell.  I think that patch is going to have issues when you have multiple horizons too20:24
* r1chardj0n3s is wondering what he's stumbled in on ;-)20:24
robcresswellducttape_: Agreed, but I'm trying to keep the bp review seperate from implementation.20:25
robcresswellOtherwise we'll be here all day.20:25
robcresswellnight20:25
*** lhcheng has quit IRC20:25
*** tonytan4ever has quit IRC20:25
robcresswellI'd say approve for now, and see where it goes. Anyone strongly against that idea?20:26
ducttape_wfm20:26
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/operation-history-log Approved, Marked Low Priority.20:27
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/django-debug-toolbar20:27
robcresswellOh, this is mine. Its a pretty common django tool. Also adds a fairly detailed template profiler for load times.20:28
ducttape_could that thing just be turned on when debug is turned on ?20:28
david-lyleI think this piece should a documented add on20:28
*** ccamacho has quit IRC20:28
ducttape_kinda like the css preview page ?20:28
david-lylethe show() method is called for every request20:28
tsufievrobcresswell, does django debug toolbar profile templates as well?20:29
david-lyle19 times when launch instance is invoked20:29
robcresswellducttape_: Right now its disabled when DEBUG is False, but also has an explicit bool control too. Called ENABLE_DEBUG_TOOLBAR iirc.20:29
tsufievit seems as there are 2 debugging/profiling features in this bp20:29
ducttape_thanks20:29
robcresswelltsufiev: Its an add on to the debug toolbar. So, they are interlinked.20:29
*** doug-fish has joined #openstack-meeting-320:30
tsufievokay, so the the toolbar is a prerequisite for template profiler20:30
tsufievlike the idea20:30
*** ccamacho has joined #openstack-meeting-320:30
*** doug-fi__ has joined #openstack-meeting-320:31
tsufievI guess the most difficult part is to push 2 new dependencies to global requirements ;)?20:31
robcresswellThe question is, as David mentioned, whether we just mention it and leave it all commented out, or provide the code and toggle it on a boolean20:31
robcresswellI'm obviously biased :)20:31
r1chardj0n3sit's pretty easy to just pip install over a venv, right?20:31
david-lyleyou have three-four logical checks each time show is called20:32
tsufievrobcresswell, what if made a switch at Developer dashboard?20:32
*** doug-f___ has joined #openstack-meeting-320:32
tsufiev*we made20:32
david-lyletsufiev: cookie driven rather than settings20:33
*** Sukhdev has joined #openstack-meeting-320:33
david-lylewell that still doesn't eliminate the overhead of checking on every request20:33
*** doug-fis_ has quit IRC20:33
tsufievdavid-lyle, ack20:33
tyr_I like that it would be easy to enable...but I wouldn't want it on by default in debug mode. Also not certain about asking deployers to include this developer only dependency.20:33
robcresswellIts disabled by default, even in debug mode.20:34
ducttape_ah good point tyr_, that extra prereq is bad20:34
david-lyleyou could even script enabling it20:34
david-lylein tools20:34
*** doug-fish has quit IRC20:34
david-lylepip install 2-packages, append onto the local settings20:34
ducttape_the problem is that people trying to run horizon in prod are going to have some python dependancy on a library they have no interest in running with20:34
*** doug-fish has joined #openstack-meeting-320:35
*** doug-fi__ has quit IRC20:35
david-lyleducttape_: I'm for not including it and just having a scripted solution to enable it20:35
robcresswellSure20:35
david-lylethat's where I was headed, if unclear20:35
ducttape_that would be ideal, or even to have some developer requirements.txt thing20:35
david-lylebut how you inject the show method I don't know yet20:35
*** toan has quit IRC20:35
tsufievwhat if we placed it into contrib/ and changed contrib/ dependencies regulations?20:36
david-lyleoh, nevermind20:36
david-lyleit's adding an app, forgot20:36
*** toan has joined #openstack-meeting-320:36
david-lyleso yeah, a contrib panel would be fine20:36
david-lyleerr, not panel, but script20:37
tsufievI mean, for example, contrib/ apps don't have to work with global requirements out of the box and may require additional deps to be installed20:37
tyr_bring it in as a FEATURE plugin?20:37
robcresswellSo as long as its conditional, the idea is fine, is the general consensus?20:37
ducttape_I think so robcresswell, make it pluggable and avoid the global requirements change20:37
robcresswellReluctant to presume with my own bp, but we should move on to the next item.20:37
*** doug-f___ has quit IRC20:37
tyr_flip Disabled=False in its enabled file and away you go.20:37
tsufiev+120:37
david-lyletyr_: something like that20:37
robcresswellGreat. So will approve and leave a comment about ensuring its optional, as are its dependencies20:38
robcresswellSound good?20:38
ducttape_+120:38
r1chardj0n3s+120:38
tyr_+120:38
tsufievack20:38
david-lyleperfect20:39
hurgleburgler+120:39
robcresswell#https://blueprints.launchpad.net/horizon/+spec/django-debug-toolbar Approved, marked Low20:39
robcresswellugh20:39
*** banix has quit IRC20:39
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/django-debug-toolbar Approved, marked Low20:39
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/horizon-use-quotas-api20:39
robcresswellducttape_: You're up20:40
ducttape_ok, so some background20:40
ducttape_horizon uses the 'limits" api for lots of stuff, mainly around the pie charts on overview pages and checking quotas20:40
ducttape_the limits api is old, but reliable20:40
ducttape_cinder has now introduced this ability to have multiple storage types20:41
r1chardj0n3sit's also incredibly slow :/20:41
ducttape_so deployment might have SSD / HDD etc20:41
ducttape_it gets worse r1chardj0n3s  ;)20:41
*** tonytan_brb has joined #openstack-meeting-320:41
tsufievducttape_, is the 'usage' feature a part of limits API or quotas API?20:42
ducttape_if I want to show users how much cinder quota they have, I need to no longer call limits api, instead I need the quotas call20:42
ducttape_the actual "you used this much" is returned in limits - but NOT in quotas call20:42
tsufievI saw some horrendous workarounds for usage in horizon code20:42
*** tonytan_brb has quit IRC20:42
tsufievI think it was exactly cinder20:42
ducttape_this all is a giant mess, indeed20:42
*** Aish has joined #openstack-meeting-320:43
robcresswellQuota management in general is something that gets mentioned a lot too20:43
david-lyleusage is fairly inaccurate too20:43
robcresswellSo it seems like it could use an improvement in many regards20:43
david-lyleor at least was20:43
ducttape_we have the need to show users "you have this much available in ssd" and "this much in hdd" etc space20:43
david-lyleI applaud ducttape_ for volunteering20:43
ducttape_but to do this, it means making quotas calls20:43
david-lylethat is code no one ever wants to touch20:43
*** tonytan_brb has joined #openstack-meeting-320:44
ducttape_and when I switch to quotas, then I need to make subsequent calls to summarize "oh - you used 500GB of SSD" etc20:44
tsufievdavid-lyle, I made one attempt some time ago and still regret that :)20:44
*** tonytan_brb is now known as tonytan4ever_20:44
ducttape_and that slowness r1chardj0n3s mentioned becomes more worser20:44
ducttape_perhaps even worserest20:44
r1chardj0n3s(just try limits with 10s of thousands of servers :/)20:45
*** neelashah has joined #openstack-meeting-320:45
hurgleburgleryikes20:45
tsufievducttape_, the proper solution to that problem is a cross-project initiative, isn't it?20:45
ducttape_so I'm stuck in my current position, I need to start making quota calls, and the work I need to do should probably be pushed back upstream20:45
*** neelashah has quit IRC20:45
david-lyletsufiev: funny you should mention that20:46
tsufievI mean, quotas have to be fixed in every affected service20:46
david-lylethere happens to be a quotas working group20:46
ducttape_but I loathe trying to make everything quotas, because that seems pretty horrid too20:46
robcresswellThe blueprint itself seems too small given the scope then; aren't we talking about an effort per-project, rather than a general "migrate API" bp?20:46
ducttape_it could be.   right now I am also asking which other projects have this aspect - to be able to have random new quotas show up20:47
david-lylewell, we migrated to limits from quotas (ducttape_ drove that), migrating back via ducttape_ seems like proper punishment20:47
ducttape_like I think glance and nova / neutron might be fixed20:47
ducttape_the irony is not lost on me20:47
ducttape_evidently I was a very bad person in my former life20:47
david-lyleI just want to highlight for the new comers :)20:48
* ducttape_ is not sure about this life, either20:48
hurgleburglerlol20:48
tsufiev:D20:48
david-lylewhat is the permission model on the quota APIs ?20:49
tsufievI'm still missing the point why come back to quotas from limits if quotas were so bad :)20:49
ducttape_so the bp is there / filed.... and I'll push what I can under review in there for more feedback, but this quotas stuff and having a quotas working group sounds like waiting on the government to fix my problems20:49
david-lylewould we have to do something like limits for non-admins and quotas for admins?20:49
* david-lyle hasn't checked20:49
robcresswellducttape_: Yeah I'm just wondering whether we can build this up to a better scope for people to contribute. The bp in its current state isnt ideal20:49
ducttape_quotas provides a richer set of features tsufiev20:50
*** neelashah has joined #openstack-meeting-320:50
*** neelashah has quit IRC20:50
*** doug-fish has quit IRC20:50
tsufievah, okay20:50
*** rbak has joined #openstack-meeting-320:50
*** matrohon has quit IRC20:50
ducttape_as an example, we have users that log into horizon, and say "I failed to create a volume, but it says I have 100GB left"20:50
ducttape_and we say "you only have 100GB of HDD storage, you are out of SSD storage"20:51
ducttape_and the customer says "why is the chart telling me this / confusing me? "20:51
*** neelashah has joined #openstack-meeting-320:51
robcresswellI think: expand the bp to detail what needs to be done, and we can use the summit to talk about the work further, since it sounds like you're not available to implement the entire thing yourself ;)20:51
*** Swami has joined #openstack-meeting-320:51
*** doug-fis_ has joined #openstack-meeting-320:52
ducttape_I'm excellent at creating bps that I can't complete.  challenge accepted20:52
ankur-gupta-f\o/20:52
david-lylelooks like quota show calls are open20:52
tsufievI would gladly implement the bp (if that's possible)20:52
*** alaski has joined #openstack-meeting-320:53
robcresswellThe trap worked!20:53
tsufievwell, I meant that pkarikh would gladly implement it :)20:53
robcresswellI mean, well volunteered tsufiev20:53
ducttape_I'll take all the help I can get :D20:53
david-lyleSCATTER20:53
tsufievsince he's interested in quotas fixing20:53
ducttape_my next bp on the list today is not as bad, I promise20:53
robcresswellducttape_: I'm gonna mark the bp as Drafting until it can be expanded further20:53
ducttape_sounds good, thanks robcresswell20:53
*** spzala has quit IRC20:54
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/horizon-use-quotas-api Needs more work, but the idea is generally approved of.20:54
robcresswell:D20:54
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/admin-neutron-l3-agent20:54
ducttape_so neutron agent lists - good times.20:54
ducttape_we have a hypervisor page, which is a good analogy of what I am after for this20:54
*** ihrachys has joined #openstack-meeting-320:54
ducttape_this lists all the places where nova is running / available to host vms20:55
*** ihrachys_ has quit IRC20:55
ducttape_well, neutron has a similar list of agents it has.   like "these are places that host dhcp servers"  "these are places that host routers"20:55
*** tonytan4ever_ is now known as tonytan4ever20:56
ducttape_as admins, we have to use the cli to navigate that right now20:56
ducttape_but it would be very helpful to show some of that info in the UI20:56
david-lylewould this be added to the table in system information?20:56
ducttape_I would see this as a new neutron panel in the admin area, if it really got flushed out20:56
ducttape_right now I have a small patch up, that just shows the location(s) where the neutron router resides20:57
ducttape_but really, this is a pretty rich environment for a lot of interesting stuff20:57
ducttape_if I was in tsufiev's shoes - this is where to volunteer20:58
*** rtheis has quit IRC20:58
ducttape_the api is pretty well know, there is a need from admins for a view into this stuff, etc20:58
tsufievthis time I abstain :)20:58
david-lyleit's not linked to the bp20:58
robcresswellLooks like a good idea, but needs filling out more so people can pick up on it ducttape_20:58
ducttape_https://review.openstack.org/#/c/306619/20:58
ducttape_#link https://review.openstack.org/#/c/306619/20:58
ducttape_ok, yep agree robcresswell20:59
david-lyleducttape_: http://pasteboard.co/kSwaEFE.png20:59
david-lyleI could see hosts listed in that table20:59
david-lylejust a thought20:59
robcresswellthanks ducttape_20:59
david-lyleor is there a lot more information you're going to add?20:59
ducttape_yep, makes sense david-lyle20:59
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/admin-neutron-l3-agent needs to be expanded21:00
ducttape_I could see the ability to drill down on those items too david-lyle21:00
robcresswellWe're at time; will add final item to next meeting21:00
robcresswellRemember, no meetings next week because of summit21:00
ducttape_like you know the l3 agent is running on daves machine - what other routers are living there???21:00
*** MarkAtwood has joined #openstack-meeting-321:00
ducttape_thanks all21:00
robcresswellLets continue in Horizon chat. Thanks all21:00
*** r1chardj0n3s has left #openstack-meeting-321:00
robcresswell#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Apr 20 21:00:56 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-04-20-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-04-20-20.00.txt21:01
kenji-iThask you ! sorry to not to be able to reply properly, I hate my cheap english skills. anyway thank you21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-04-20-20.00.log.html21:01
*** baoli has quit IRC21:01
*** mriedem has joined #openstack-meeting-321:01
alaski#startmeeting nova_cells21:01
openstackMeeting started Wed Apr 20 21:01:24 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** spzala has joined #openstack-meeting-321:01
*** openstack changes topic to " (Meeting topic: nova_cells)"21:01
openstackThe meeting name has been set to 'nova_cells'21:01
alaskianyone around today?21:01
*** tqtran has left #openstack-meeting-321:01
mriedemo/21:01
mriedemsort of21:01
melwitto/21:01
ccarmack1o/21:01
bauzas\o21:01
*** ctrath has joined #openstack-meeting-321:01
alaski#topic testing21:02
*** openstack changes topic to "testing (Meeting topic: nova_cells)"21:02
*** rlrossit has joined #openstack-meeting-321:02
alaskihaven't heard of any gate failures, so things are sailing smoothly these days21:02
alaskiccarmack1 had a thing to discuss though21:02
ccarmack1I put some thoughts about testing in https://etherpad.openstack.org/p/nova-cells-testing21:02
*** bpokorny_ has joined #openstack-meeting-321:02
*** ducttape_ has left #openstack-meeting-321:03
ccarmack1please add any comments21:03
alaskiat the bottom it looks like21:03
melwittah, my old friend that etherpad21:03
ccarmack1yea, sorry at the bottom21:03
alaskidoes anyone object to me removing the big glob in the middle?21:03
ccarmack1I was thinking we need something that approximates a real multi node cells env21:04
melwittalaski: not me. I totally forgot about this etherpad21:04
alaskimelwitt: I had repressed it as well :)21:04
melwitthaha :)21:04
alaskiccarmack1: yes, that would be ideal21:04
ccarmack1amazing what google will find21:04
*** hurgleburgler has left #openstack-meeting-321:05
ccarmack1how found that etherpad21:05
melwittimpressive21:05
bauzasorly?21:05
alaskiso the question I have for multi-node is where will cell0 live21:05
alaskiI would probably put it on the api node21:06
*** spzala has quit IRC21:06
melwittthat's what I was thinking. that would be like real life anyway, right?21:06
ccarmack1I was thinking of a devstack with api + cell121:06
alaskifor a lot of people, yeah21:06
ccarmack1and cell021:06
*** bpokorny has quit IRC21:07
alaskion one node?21:07
melwittfor multi-node I thought we would have 2 cells, no?21:07
*** mrmartin has quit IRC21:07
*** mickeys has quit IRC21:07
melwittapi + cell1 + cell221:07
ccarmack1I was concerned about a 3 host multinode21:07
*** spzala has joined #openstack-meeting-321:07
ccarmack1but yes that would be better21:07
ccarmack1does the gate support 3 hosts?21:07
*** mickeys has joined #openstack-meeting-321:08
bauzaswhy not 2 nodes with (api, cell0, cell1) and (cell2) ?21:08
*** mickeys has quit IRC21:08
ccarmack1thats where I left it21:08
bauzaslike an AIO-+121:08
alaskiccarmack1: not sure. that's probably a sdague or -infra question21:08
*** mickeys has joined #openstack-meeting-321:08
alaskiI was actually thinking (api, cell0), then cell1 separate21:08
alaskiand eventually another node for cell221:08
alaskibut we're not quite up to a cell2 yet21:09
ccarmack1thats what I have in the doc.. but I can ask infra about having 3 hosts in a multi-node test21:09
ccarmack1not quite up to cell2 ?21:09
melwittyeah, I was thinking future, I guess I assumed multi-node means multi-cell21:09
*** mickeys has quit IRC21:09
alaskiccarmack1: we don't have all the pieces in place to make that work yet21:10
*** mickeys has joined #openstack-meeting-321:10
alaskibut melwitt has a patch up right now with a big chunk of it21:10
ccarmack1I think this is planning for testing when everything is working21:10
*** jlopezgu_ has left #openstack-meeting-321:10
alaskiokay21:11
ccarmack1melwitt's patch in the rpc switching?21:11
melwittokay, so are we thinking we have one multi-node job now that has api + cell0 + cell1 and then in the future another multi-node job that has 2 cells or just amend the existing job to have 2 cells?21:11
alaskiyeah21:11
alaskimelwitt: I was thinking the latter21:11
ccarmack1and each cell has 1 host?21:12
ccarmack1aka node21:12
alaskiyes, if infra can provide that21:12
*** spzala has quit IRC21:12
ccarmack1ok, I'll ask21:12
*** lpetrut has quit IRC21:12
alaskiwe could do (api, cell0, cell1) and (cell2) as a reasonable test bed as well I think21:12
ccarmack1that's 2 hosts, if infra can't do 321:13
bauzasI'm just thinking of people using All-in-One21:13
alaskiccarmack1: yeah. a fallback21:13
bauzasgiven that, adding a new cell21:13
*** lblanchard has quit IRC21:13
*** spzala has joined #openstack-meeting-321:13
melwittwait, are we waiting until multi-cell to do multi-node or are we thinking of multi-node now with everything talking to the same db/mq?21:13
bauzashence 2 nodes, first with (api, cell0, cell1) and the other with only a cell21:13
bauzas2 MQs21:14
bauzasmelwitt: and different DBs21:14
bauzasbut within the same infra node21:14
*** kenji-i has quit IRC21:14
*** mickeys has quit IRC21:14
ccarmack1melwitt: I'm thinking of multi-cell, when its ready21:14
*** Sukhdev has quit IRC21:15
alaskiwell, I was thinking of multi-node with one cell, and then expand to two when ready21:15
alaskibut if everyone wants to wait we can do that21:15
ccarmack1alaski: would that env test anything specific to cells?21:15
*** lcastell has quit IRC21:16
*** luzC has quit IRC21:16
ccarmack1it would be a non-AIO21:16
alaskiit wouldn't21:16
alaskiso maybe it's not important now21:16
alaskiokay, so multi-node will be multi-cell21:17
alaskiand it may be a while until that works21:17
bauzasI was basically thinking that a cell DB could be close to the compute21:17
ccarmack1I was thinking waiting for multi-cell and then have a config as we are saying  — node1 has api, cell0, cell2 .. node2 has cell121:17
melwittit would be figuring out the legwork now instead of later I guess. or rather setting it up now once to be expanded instead of potentially having to redo a lot to expand?21:17
bauzasbut yeah...21:17
alaskimelwitt: yeah, that was my thinking21:18
*** spzala has quit IRC21:18
bauzasmelwitt: alaski: well, that's just config stuff right?21:18
bauzasmeaning that we cut our deployment with the manage calls we want21:18
alaskiccarmack1: that works, but it won't pass anything now so the question is are you planning to work on it now, and should it run on all reviews?21:18
bauzasnot sure changing that could be difficult21:19
*** spzala has joined #openstack-meeting-321:19
ccarmack1alaski: I was planning to do some leg work to set up the jobs, etc21:20
alaskiccarmack1: okay. that would be great, but it probably needs to start in the experimental queue21:20
ccarmack1yup21:20
*** e0ne has quit IRC21:20
alaskibauzas: you're thinking of doing two cells in AIO?21:21
ccarmack1bauzas: I was thinking of having each cell's db on the same host has compute21:21
*** janice has quit IRC21:21
*** lcastell has joined #openstack-meeting-321:21
bauzasalaski: nope21:21
*** neiljerram has quit IRC21:21
bauzasalaski: one cell in AIO21:21
bauzasalaski: and one other cell in a separate node with another compute21:21
*** luzC has joined #openstack-meeting-321:21
alaskibauzas: gotcha21:21
bauzasalaski: but that means a cell DB could be close to the compute node21:21
alaskiyeah, that's fine though21:22
bauzaswhich could be a bit sad for performance... but we use AIO too :)21:22
alaskiyep21:22
bauzasso, maybe later a large-ops one21:22
alaskiyeah21:23
alaskiokay, I think we're all on the same page now21:23
ccarmack1could you all comment in the etherpad21:23
ccarmack1so I can chew on this later?21:24
ccarmack1also, I'm not sure about the grenade stuff21:24
alaski#action all comment on https://etherpad.openstack.org/p/nova-cells-testing21:24
ccarmack1alaski: is multi-tier cells in the future?21:24
bauzaserh21:25
ccarmack1or not for newton?21:25
alaskiI think the only upgrade thing different between cells and non for grenade is testing the update from non cells to cells21:25
*** spzala has quit IRC21:25
alaskiccarmack1: not planned at all21:25
bauzasI think we agreed to only have one parent/child21:25
bauzashorizontally, not vertically21:25
ccarmack1alaski: and a cellsv1 to cellsv2 upgrade?21:25
alaskiyeah, multi-tier would be cellsv3, or v2.5 or something. not being considered for this effort21:25
ccarmack1ok21:26
*** spzala has joined #openstack-meeting-321:26
melwittmulti-tier means nested, right?21:26
alaskiccarmack1: yes, and we don't really have c1->v2 sorted yet21:26
ccarmack1yes melwitt21:26
alaskiccarmack1: we kind of need multi-cell support first21:26
melwittokay. yeah, nested cells hasn't been a thing so far and maybe never will21:26
ccarmack1ok21:26
alaskiany more on testing?21:27
ccarmack1I'm done21:27
alaskicool21:27
alaski#topic Open Reviews21:27
bauzasccarmack1: cellv1 to cellv2 path is clear now21:27
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"21:27
alaskihttps://etherpad.openstack.org/p/newton-nova-priorities-tracking21:27
ccarmack1bauza: yes I saw your doc update21:28
ccarmack1I think you did that…21:28
*** sdake_ has joined #openstack-meeting-321:28
bauzasmulti cellsv1 can be only one cellv2 by default21:28
*** tonytan4ever has quit IRC21:28
alaskifor reviews just check out the etherpad21:28
alaski#topic Open Discussion21:28
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"21:28
alaskiyeah, we have a plan for v1->v2, but without multicell support no one is realistically going to upgrade21:29
alaskiand we can't fully test it21:29
ccarmack1we can't it fully be tested?21:29
ccarmack1why,,,21:30
bauzasalaski: yup, agreed21:30
alaskijust that we can't migrate two v1 cells to v2, which is really what we want to check21:30
*** spzala has quit IRC21:30
*** reedip_ has joined #openstack-meeting-321:30
melwittI was wondering how are we doing on the 'boot an instance' with a single cell v2. are all of the patches up for that or is there anything else still needed?21:31
alaskithere's a few things still needed21:31
*** spzala has joined #openstack-meeting-321:32
alaskiI have a local WIP which moves instance creation to the conductor, that's the last big piece21:32
*** Aish has left #openstack-meeting-321:32
alaskithere's also handling listing instances from a BuildRequest21:32
alaskiwhich has no work on it yet21:32
melwittokay, cool. just wanted to make sure is it a matter of just reviews or if there's more to come21:32
*** ihrachys has quit IRC21:32
alaskimostly those two things I think21:32
rlrossitaren't there still API DB migrations needed too?21:33
*** ihrachys has joined #openstack-meeting-321:33
*** neelashah has quit IRC21:33
alaskiI consider those more of the multi-cell story21:33
*** dedery has quit IRC21:33
alaskibut yes, plenty of those still needed21:33
rlrossityeah I figured those weren't done yet :)21:34
alaskiheh, not even close21:34
melwittwhat else for multi-cell? API DB migrations, is there anything more with the scheduling interaction or is that covered under the single cell work?21:34
alaskidoffm did get some specs up though21:34
rlrossitYep and they've come up on my objects reviews dashboard, but I've been ignoring them21:35
alaskimelwitt: that should be covered under the single cell work, unless there's something being overlooked21:35
melwittalaski: great21:35
melwittalaski: well, I suppose it will be a matter of putting target_cell in the right place for the switching too21:36
alaskiright21:36
melwittalaski: in my local testing I put it in conductor21:36
*** spzala has quit IRC21:36
alaskiusing switching for db and rpc and db migrations. I think that's mostly what's left after current WIP is done21:36
melwittcool21:36
*** neelashah has joined #openstack-meeting-321:37
alaskiand testing, and upgrade path for v121:37
*** ddieterly is now known as ddieterly[away]21:37
melwitt*nod*21:37
alaskiit probably goes without saying, but I will not be running this meeting next week21:38
*** ddieterly[away] is now known as ddieterly21:38
*** Sukhdev has joined #openstack-meeting-321:38
alaskiif you want to talk cells come find me in Austin :)21:38
*** spzala has joined #openstack-meeting-321:38
melwittyeah, I assumed no meetings next week21:38
alaskialso, hopefully everyone knows by now that I am not a locquacious person, so please come ready to help with the cells summit sessions21:39
melwittI'm not either but I will try :)21:39
* rlrossit googles locquacious21:40
alaskidangit, spelled it wrong21:40
alaskimelwitt: between the two of us we're almost a talkative person21:40
melwittalaski: lol, so true21:40
alaskithat's all I have for this week21:41
alaskianyone have a topic?21:41
ccarmack1nooope21:41
rlrossitsee y'all in austin21:41
rlrossitgetting my accent ready21:41
*** e0ne has joined #openstack-meeting-321:41
alaskigreat! see y'all there21:41
melwittgreat!21:41
alaski:)21:41
melwitto/21:41
alaski#endmeeting21:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:41
openstackMeeting ended Wed Apr 20 21:41:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-04-20-21.01.html21:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-04-20-21.01.txt21:41
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-04-20-21.01.log.html21:41
*** rlrossit has left #openstack-meeting-321:42
*** ccarmack1 has left #openstack-meeting-321:42
*** spzala has quit IRC21:43
*** Sukhdev has quit IRC21:43
*** ihrachys has quit IRC21:44
*** spzala has joined #openstack-meeting-321:45
*** sdake_ has quit IRC21:45
*** sdake_ has joined #openstack-meeting-321:47
*** Sukhdev has joined #openstack-meeting-321:47
*** alaski has left #openstack-meeting-321:48
*** e0ne has quit IRC21:51
*** vgridnev_ has joined #openstack-meeting-321:55
*** salv-orl_ has joined #openstack-meeting-321:56
*** spzala has quit IRC21:57
*** mriedem has left #openstack-meeting-321:57
*** piet has joined #openstack-meeting-321:57
*** nikhil_k is now known as nikhil21:58
*** salv-orlando has quit IRC21:59
*** Sukhdev has quit IRC21:59
*** vgridnev_ has quit IRC22:00
*** spzala has joined #openstack-meeting-322:00
*** matt-borland has quit IRC22:02
*** ddieterly is now known as ddieterly[away]22:02
*** ctrath has quit IRC22:03
*** ccamacho has quit IRC22:04
*** Sukhdev has joined #openstack-meeting-322:05
*** fitoduarte has joined #openstack-meeting-322:07
*** ccamacho has joined #openstack-meeting-322:07
*** ctrath has joined #openstack-meeting-322:07
*** lblanchard has joined #openstack-meeting-322:08
*** vhoward has quit IRC22:09
*** rocky_g has quit IRC22:12
*** ccamacho has quit IRC22:13
*** ccamacho has joined #openstack-meeting-322:15
*** sigmavirus24 is now known as sigmavirus24_awa22:15
*** neelashah has quit IRC22:17
*** doug-fis_ has quit IRC22:17
*** dimtruck is now known as zz_dimtruck22:20
*** ddieterly[away] is now known as ddieterly22:25
*** rossella_s has joined #openstack-meeting-322:26
*** toddjohn_ has joined #openstack-meeting-322:27
*** toddjohn_ has quit IRC22:27
*** Adri2000 has quit IRC22:27
*** toddjohn_ has joined #openstack-meeting-322:28
*** galstrom is now known as galstrom_zzz22:36
*** spzala has quit IRC22:37
*** mickeys has joined #openstack-meeting-322:39
*** mickeys_ has joined #openstack-meeting-322:41
*** mickeys_ has quit IRC22:42
*** mickeys_ has joined #openstack-meeting-322:42
*** mickeys has quit IRC22:43
*** mickeys_ has quit IRC22:43
*** mickeys has joined #openstack-meeting-322:43
*** ddieterly has quit IRC22:43
*** yamahata has quit IRC22:49
*** lblanchard has quit IRC22:52
*** claudiub has quit IRC22:56
*** krotscheck is now known as krotscheck_dcm22:57
*** emagana has quit IRC22:57
*** piet has quit IRC23:03
*** cloudtrainme has quit IRC23:03
*** tyr_ has quit IRC23:06
*** ctrath has quit IRC23:06
*** Adri2000 has joined #openstack-meeting-323:10
*** sdague has quit IRC23:12
*** ddieterly has joined #openstack-meeting-323:15
*** vtech has quit IRC23:17
*** spzala has joined #openstack-meeting-323:18
*** Sukhdev has quit IRC23:22
*** mickeys has quit IRC23:23
*** spzala has quit IRC23:23
*** ddieterly is now known as ddieterly[away]23:23
*** mickeys has joined #openstack-meeting-323:24
*** bpokorny_ has quit IRC23:25
*** salv-orl_ has quit IRC23:26
*** bpokorny has joined #openstack-meeting-323:26
*** mickeys has quit IRC23:28
*** jaypipes has quit IRC23:29
*** emagana has joined #openstack-meeting-323:32
*** kenji-i has joined #openstack-meeting-323:38
*** Sukhdev has joined #openstack-meeting-323:41
*** neelashah has joined #openstack-meeting-323:42
*** fitoduarte has quit IRC23:46
*** Sukhdev has quit IRC23:48
*** mageshgv has quit IRC23:57
*** sdake__ has joined #openstack-meeting-323:58

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