Wednesday, 2016-05-11

*** toddjohn has quit IRC00:01
*** toddjohn has joined #openstack-meeting-300:01
*** julim has joined #openstack-meeting-300:02
*** Poornima has joined #openstack-meeting-300:06
*** spzala has quit IRC00:07
*** mickeys has quit IRC00:08
*** mickeys has joined #openstack-meeting-300:08
*** mickeys_ has joined #openstack-meeting-300:11
*** kzaitsev_mb has joined #openstack-meeting-300:11
*** toddjohn has quit IRC00:12
*** toddjohn has joined #openstack-meeting-300:13
*** mickeys has quit IRC00:13
*** emagana has quit IRC00:15
*** mickeys_ has quit IRC00:15
*** ddieterly has joined #openstack-meeting-300:16
*** kzaitsev_mb has quit IRC00:17
*** ivar-lazzaro has joined #openstack-meeting-300:19
*** agateaaa has quit IRC00:27
*** salv-orlando has joined #openstack-meeting-300:28
*** Swami has quit IRC00:29
*** salv-orlando has quit IRC00:33
*** reedip__ has joined #openstack-meeting-300:35
*** Poornima has quit IRC00:41
*** Poornima has joined #openstack-meeting-300:42
*** mbound has quit IRC00:45
*** mtanino has quit IRC00:48
*** bpokorny_ has joined #openstack-meeting-300:56
*** Poornima has quit IRC00:57
*** mickeys has joined #openstack-meeting-300:57
*** bpokorny has quit IRC01:00
*** bpokorny_ has quit IRC01:01
*** yamamot__ has joined #openstack-meeting-301:04
*** crinkle has joined #openstack-meeting-301:04
*** hoangcx has joined #openstack-meeting-301:06
*** hoangcx has left #openstack-meeting-301:06
*** spzala has joined #openstack-meeting-301:08
*** zhurong has joined #openstack-meeting-301:11
*** pvaneck has quit IRC01:11
*** kzaitsev_mb has joined #openstack-meeting-301:12
*** spzala has quit IRC01:13
*** mickeys has quit IRC01:16
*** mickeys has joined #openstack-meeting-301:17
*** kzaitsev_mb has quit IRC01:18
*** mickeys has quit IRC01:21
*** dedery has quit IRC01:28
*** piet has joined #openstack-meeting-301:28
*** amotoki has quit IRC01:30
*** reedip__ has quit IRC01:30
*** mickeys has joined #openstack-meeting-301:31
*** emagana has joined #openstack-meeting-301:36
*** yamamot__ has quit IRC01:40
*** emagana has quit IRC01:40
*** ivar-lazzaro has quit IRC01:41
*** amotoki has joined #openstack-meeting-301:41
*** yamamot__ has joined #openstack-meeting-301:41
*** mbound has joined #openstack-meeting-301:46
*** vishwanathj has quit IRC01:48
*** yamahata has quit IRC01:49
*** iyamahat has quit IRC01:49
*** amotoki has quit IRC01:50
*** mbound has quit IRC01:51
*** piet has quit IRC01:54
*** amotoki has joined #openstack-meeting-301:56
*** spzala has joined #openstack-meeting-301:57
*** salv-orlando has joined #openstack-meeting-301:58
*** xiaohhui has joined #openstack-meeting-302:03
*** salv-orlando has quit IRC02:05
*** mickeys has quit IRC02:12
*** mickeys has joined #openstack-meeting-302:12
*** kzaitsev_mb has joined #openstack-meeting-302:14
*** ddieterly is now known as ddieterly[away]02:15
*** mickeys has quit IRC02:17
*** amotoki has quit IRC02:19
*** kzaitsev_mb has quit IRC02:20
*** fitoduarte has quit IRC02:26
*** yamahata has joined #openstack-meeting-302:29
*** absubram has joined #openstack-meeting-302:29
*** absubram_ has joined #openstack-meeting-302:30
*** amotoki has joined #openstack-meeting-302:32
*** absubram has quit IRC02:34
*** absubram_ is now known as absubram02:34
*** zhurong has quit IRC02:36
*** hoangcx has joined #openstack-meeting-302:36
*** hoangcx has left #openstack-meeting-302:36
*** zhurong has joined #openstack-meeting-302:36
*** baoli has joined #openstack-meeting-302:38
*** sankarshan_away is now known as sankarshan02:38
*** yamamot__ has quit IRC02:38
*** piet has joined #openstack-meeting-302:45
*** ccamacho has quit IRC03:04
*** absubram has quit IRC03:05
*** ccamacho has joined #openstack-meeting-303:05
*** dimtruck is now known as zz_dimtruck03:06
*** zz_dimtruck is now known as dimtruck03:06
*** piet has quit IRC03:07
*** absubram has joined #openstack-meeting-303:08
*** spzala has quit IRC03:12
*** spzala has joined #openstack-meeting-303:12
*** ddieterly[away] has quit IRC03:15
*** kzaitsev_mb has joined #openstack-meeting-303:17
*** spzala has quit IRC03:17
*** yamamot__ has joined #openstack-meeting-303:19
*** yamamot__ has quit IRC03:22
*** kzaitsev_mb has quit IRC03:23
*** yamamot__ has joined #openstack-meeting-303:23
*** salv-orlando has joined #openstack-meeting-303:24
*** yamamot__ has quit IRC03:25
*** armax has quit IRC03:27
*** yamamot__ has joined #openstack-meeting-303:27
*** iyamahat has joined #openstack-meeting-303:30
*** mbound has joined #openstack-meeting-303:30
*** salv-orlando has quit IRC03:30
*** mbound has quit IRC03:35
*** vishwanathj has joined #openstack-meeting-303:36
*** salv-orlando has joined #openstack-meeting-303:36
*** salv-orlando has quit IRC03:41
*** vishwanathj has quit IRC03:54
*** reedip__ has joined #openstack-meeting-303:58
*** baoli has quit IRC04:01
*** pcaruana has joined #openstack-meeting-304:02
*** stendulker has joined #openstack-meeting-304:09
*** spzala has joined #openstack-meeting-304:13
*** mickeys has joined #openstack-meeting-304:14
*** kaz has joined #openstack-meeting-304:17
*** spzala has quit IRC04:18
*** reedip__ has quit IRC04:19
*** mickeys has quit IRC04:19
*** kzaitsev_mb has joined #openstack-meeting-304:20
*** kzaitsev_mb has quit IRC04:26
*** lpetrut has joined #openstack-meeting-304:26
*** reedip__ has joined #openstack-meeting-304:31
*** pgadiya has joined #openstack-meeting-304:40
*** Poornima has joined #openstack-meeting-304:42
*** amotoki_ has joined #openstack-meeting-304:46
*** mrunge has quit IRC04:46
*** salv-orlando has joined #openstack-meeting-304:47
*** amotoki has quit IRC04:48
*** markvoelker_ has joined #openstack-meeting-304:50
*** salv-orlando has quit IRC04:52
*** dimtruck is now known as zz_dimtruck04:57
*** zz_dimtruck is now known as dimtruck04:57
*** spzala has joined #openstack-meeting-305:02
*** fawadkhaliq has joined #openstack-meeting-305:05
*** spzala has quit IRC05:07
*** dimtruck is now known as zz_dimtruck05:07
*** lpetrut has quit IRC05:07
*** yamamot__ has quit IRC05:08
*** sverma has joined #openstack-meeting-305:08
*** sdake has quit IRC05:08
*** yamamot__ has joined #openstack-meeting-305:09
*** kzaitsev_mb has joined #openstack-meeting-305:09
*** coolsvap has joined #openstack-meeting-305:10
*** yamamot__ has quit IRC05:12
*** yamamot__ has joined #openstack-meeting-305:13
*** kzaitsev_mb has quit IRC05:14
*** fitoduarte has joined #openstack-meeting-305:14
*** anil_rao has joined #openstack-meeting-305:24
*** soichi has joined #openstack-meeting-305:25
*** emagana has joined #openstack-meeting-305:27
*** salv-orlando has joined #openstack-meeting-305:28
anil_rao#startmeeting taas05:30
openstackMeeting started Wed May 11 05:30:09 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:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:30
*** openstack changes topic to " (Meeting topic: taas)"05:30
openstackThe meeting name has been set to 'taas'05:30
yamamot__hi05:30
kazhi05:30
soichihi05:30
anil_raoHi05:30
anil_raoHope everyone who attended the summit had a safe trip back.05:31
*** emagana has quit IRC05:32
soichithank you for meet up in the summit05:32
anil_raoThe only item in today's agenda is the gate blocking bug.05:33
yamamot__#link https://wiki.openstack.org/wiki/Meetings/taas05:33
anil_raoI complete the review shortly.05:34
yamamot__#link https://review.openstack.org/#/c/306390/05:34
anil_raoAny other items folks want to discuss?05:35
yamamot__any update on lp permission tweak?05:35
anil_raoNot yet. Waiting for Vinay on this. Not sure what is going on05:36
anil_raowe had talked in Austin about me putting up the TaaS Driver detailed design doc.05:37
anil_raoWhere is a good place to park such a document?05:38
yamamot__doc/ in the repo05:38
yamamot__incase it's inappropriate for some reason, maybe put on wiki and have a link there.05:39
anil_raoOk.05:39
*** absubram has quit IRC05:40
yamamot__common flow classifier meeting will start on may 1705:40
yamamot__#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/094538.html05:40
anil_raoThanks for the reminder.05:40
*** absubram has joined #openstack-meeting-305:41
yamamot__and neutron stadium05:41
yamamot__#link https://review.openstack.org/#/c/312199/05:41
*** fitoduarte has quit IRC05:42
anil_raoLooks like lots of activity in the Neutron Statdium Evolution review05:43
anil_raoI'll look into adding some error handling code in the TaaS driver.05:45
*** sanghai has joined #openstack-meeting-305:45
anil_raoWe will also need to design the status field for some of the TaaS API calls.05:46
soichianil_rao: agree (to support async API)05:47
anil_raosoichi: Yes.05:47
*** yamamot__ has quit IRC05:50
kazI can try to this.05:51
anil_raokaz: Sure.05:52
*** yamamot__ has joined #openstack-meeting-305:52
anil_raokaz: The first step would be to just add the status field in the API and just set it to success by default.05:52
anil_raoWhen the driver error handling is completed we can properly update the status field.05:53
kazi see05:53
*** mickeys has joined #openstack-meeting-305:53
soichianil_rao: +105:53
anil_raoI am headed back to Texas (Dallas) next week for a couple of days. When I get back I'll set up a h/w based DevStack environment and collect some performance data for TaaS.05:56
anil_raoWill share the results on the mailing list.05:56
*** amotoki_ has quit IRC05:56
*** sankarshan is now known as sankarshan_away05:57
*** zz_dimtruck is now known as dimtruck05:57
soichianil_rao: that's sounds great. we really need performance data.05:58
*** mickeys has quit IRC05:58
kazanil_rao: +105:58
soichiin our experiment, we found that the virt-io running on a host can be a bottleneck06:01
*** anil_rao has quit IRC06:02
*** spzala has joined #openstack-meeting-306:03
*** anil_rao has joined #openstack-meeting-306:05
anil_raoSorry, compute problem06:06
anil_raosoichi: virt-io?06:06
*** hdaniel_ has joined #openstack-meeting-306:07
*** numans has joined #openstack-meeting-306:07
soichivirt io process running on a host seems to comsume CPU 100%06:08
*** spzala has quit IRC06:09
soichicomsume -> consume06:09
anil_raosoichi: I see.06:09
anil_raosoichi: What kind of load were you putting on the VM being monitored.06:10
yamamot__soichi: it isn't taas-specific, right?06:10
soichiyamamotot_: you are right. it isn't taas-specific.06:12
anil_raoI am still wondering what kind of load was resulting in virt-io consuming 100% cpu06:13
soichianil_rao: we put load by using iperf06:13
yamamot__small frames i guess06:14
anil_raosoichi: I guess iperf is measuring the max speed so it will push the system until it maxes out.06:14
anil_raosoichi: Was this on hardware based DevStack? Multi-node?06:15
kazi guess so.06:15
*** piet has joined #openstack-meeting-306:16
kazanil_rao: yes06:16
anil_raokaz: Thanks.06:16
soichianil_rao: we would like to share our result on next week06:18
anil_raosoichi: That would be nice.06:18
anil_raoHowever, I will have to skip next week's meeting since I am going to Texax on a business trip.06:18
anil_raoI can read up on the meeting minutes.06:18
*** abhishek has left #openstack-meeting-306:19
soichiokay06:19
soichii have no additional topic for today.06:21
anil_raoAnyone else has any updates?06:21
yamamot__nothing from me06:21
kazme too06:21
anil_raoOk, I think we can end for today then.06:21
*** yushiro has joined #openstack-meeting-306:22
*** yushiro has left #openstack-meeting-306:22
*** david-lyle has quit IRC06:23
anil_rao#endmeeting06:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:23
openstackMeeting ended Wed May 11 06:23:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-05-11-05.30.html06:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-05-11-05.30.txt06:23
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-05-11-05.30.log.html06:23
anil_raoBye06:23
soichibye06:23
kazbye06:23
*** anil_rao has quit IRC06:23
yamamot__bye06:24
*** dimtruck is now known as zz_dimtruck06:24
*** soichi has left #openstack-meeting-306:24
*** kaz has quit IRC06:24
*** piet has quit IRC06:25
*** david-lyle has joined #openstack-meeting-306:26
*** zz_dimtruck is now known as dimtruck06:30
*** anilvenkata has joined #openstack-meeting-306:36
*** woodster_ has quit IRC06:38
*** fawadkhaliq has quit IRC06:44
*** fawadkhaliq has joined #openstack-meeting-306:44
*** dimtruck is now known as zz_dimtruck06:49
*** vgridnev has quit IRC06:54
*** vgridnev has joined #openstack-meeting-306:56
*** andreas_s has joined #openstack-meeting-306:57
*** zz_dimtruck is now known as dimtruck07:01
*** salv-orlando has quit IRC07:02
*** sanghai has quit IRC07:03
*** amotoki has joined #openstack-meeting-307:04
*** matrohon has joined #openstack-meeting-307:04
*** spzala has joined #openstack-meeting-307:04
*** spzala has quit IRC07:09
*** belmoreira has joined #openstack-meeting-307:11
*** amotoki has quit IRC07:18
*** nkrinner_afk is now known as nkrinner07:19
*** dimtruck is now known as zz_dimtruck07:21
*** amotoki has joined #openstack-meeting-307:25
*** kzaitsev_mb has joined #openstack-meeting-307:26
*** gabriel-bezerra has joined #openstack-meeting-307:26
*** markvoelker_ has quit IRC07:30
*** iyamahat has quit IRC07:36
*** jlanoux has joined #openstack-meeting-307:40
*** itxaka has joined #openstack-meeting-307:45
*** kzaitsev_mb has quit IRC07:46
*** iyamahat has joined #openstack-meeting-307:52
*** amotoki has quit IRC07:54
*** robcresswell has joined #openstack-meeting-307:54
*** milan has quit IRC07:54
*** mickeys has joined #openstack-meeting-307:54
*** emagana has joined #openstack-meeting-307:55
*** amotoki has joined #openstack-meeting-307:55
*** iyamahat has quit IRC07:57
*** tsufiev has joined #openstack-meeting-307:57
*** emagana has quit IRC07:59
*** mickeys has quit IRC07:59
robcresswell#startmeeting horizondrivers08:00
openstackMeeting started Wed May 11 08:00:19 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
*** openstack changes topic to " (Meeting topic: horizondrivers)"08:00
openstackThe meeting name has been set to 'horizondrivers'08:00
tsufievo/08:00
robcresswello/08:00
itxakao/08:00
itxakafull room08:01
itxaka:)08:01
robcresswellAlways quieter in this tz08:01
robcresswellLets run through a couple of notices08:01
robcresswell#topic Notices08:01
*** openstack changes topic to "Notices (Meeting topic: horizondrivers)"08:01
robcresswell#info Weekly bug report updated08:02
robcresswell#link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport08:02
robcresswellIf you only get time to do a handful of reviews each week, make sure its on these patches.08:02
robcresswellWe've about 3 weeks until N-1, and a number of issues I'd like to address before then.08:03
robcresswellWith the slightly earlier FF, all the more reason to get the bps merged early08:03
*** r1chardj0n3s_afk has joined #openstack-meeting-308:04
*** r1chardj0n3s_afk is now known as r1chardj0n3s08:04
*** amotoki has quit IRC08:04
r1chardj0n3so/08:04
betherlyo/08:04
*** dedery has joined #openstack-meeting-308:05
r1chardj0n3s(I'm guessing: quiet meeting ;-)08:05
robcresswellMoving on. I've put up a short poll to get an idea of when people would prefer a midcycle. Got a few internal meetings this week, should have something in stone by next meeting08:05
robcresswell#info Midcycle dates poll08:05
robcresswell#link http://doodle.com/poll/xvchsbbs4qz9tzr708:05
*** spzala has joined #openstack-meeting-308:05
robcresswellIf people could fill that out promptly it'll help me get a good sense of date and numbers/08:06
robcresswellIt's also on the mailer and Horizon IRC room topic if you need to refer back.08:06
tsufievwill do by the end of this week08:07
r1chardj0n3sthanks toan08:07
r1chardj0n3ser08:07
r1chardj0n3sthanks robcresswell08:07
robcresswelllol08:07
robcresswellAny questions on those items?08:08
robcresswell#topic Blueprint Review08:09
*** openstack changes topic to "Blueprint Review (Meeting topic: horizondrivers)"08:09
betherlyawesome will do that today08:09
*** pavel_bondar has quit IRC08:10
*** spzala has quit IRC08:10
*** pavel_bondar has joined #openstack-meeting-308:11
robcresswellNothing on the agenda for this meeting. If anyone has any blueprints they'd like reviewed, feel free to link, otherwise we can pick a few at random08:11
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/manage-volume-instance-views08:11
robcresswellThis seems quite straightforward to me. Its just improving the UI for managing attachments08:12
*** zz_dimtruck is now known as dimtruck08:12
itxaka+108:13
tsufievso basically it's about attaching volume not only from volumes page, but also from instances page, right?08:13
robcresswellYes08:13
tsufiev+1 from my side08:14
r1chardj0n3s+108:14
*** fawadkhaliq has quit IRC08:14
*** fawadkhaliq has joined #openstack-meeting-308:15
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/manage-volume-instance-views Approved08:15
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/horizon-vendor-split08:16
*** mickeys has joined #openstack-meeting-308:16
robcresswellThis is one thats lingered from a while back. One of my coworkers thought it'd be nice to assign me :)08:17
r1chardj0n3sseems fair08:17
robcresswellThere's still a few pieces of vendor specific code/settings we should remove, so the bp is still viable.08:17
itxakaseems logical to me08:17
itxaka+108:17
tsufiev+108:18
robcresswellWe have our own repo, so I should just finish ripping that code out and be done with it.08:18
robcresswellAnd check for others too... I think BigSwitch have some router code iirc.08:18
*** salv-orl_ has joined #openstack-meeting-308:19
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/horizon-vendor-split Approved08:19
*** r1chardj0n3s has left #openstack-meeting-308:19
robcresswellNot a great deal of active bps that havent been accepted08:21
*** amotoki has joined #openstack-meeting-308:21
*** mickeys has quit IRC08:22
robcresswellIf there aren't any suggestions, we can end early :)08:22
*** amotoki has quit IRC08:22
*** mickeys has joined #openstack-meeting-308:22
*** vgridnev has quit IRC08:22
*** wangbo has joined #openstack-meeting-308:23
robcresswellThanks all!08:23
robcresswell#endmeeting08:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:23
openstackMeeting ended Wed May 11 08:23:54 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-05-11-08.00.html08:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-05-11-08.00.txt08:23
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-05-11-08.00.log.html08:24
*** vgridnev has joined #openstack-meeting-308:24
itxakao/ o/08:24
*** robcresswell has left #openstack-meeting-308:24
*** fawadkhaliq has quit IRC08:25
*** fawadkhaliq has joined #openstack-meeting-308:25
*** amotoki has joined #openstack-meeting-308:26
*** mickeys has quit IRC08:27
*** yamahata has quit IRC08:29
*** kenji-i has joined #openstack-meeting-308:31
*** dimtruck is now known as zz_dimtruck08:31
*** wangbo has quit IRC08:36
*** vgridnev has quit IRC08:39
*** sambetts|afk is now known as sambetts08:39
*** c64cosmin has joined #openstack-meeting-308:39
*** abalutoiu has joined #openstack-meeting-308:40
*** cartik has joined #openstack-meeting-308:40
*** rossella_s has joined #openstack-meeting-308:44
*** neiljerram has joined #openstack-meeting-308:46
*** markvoelker has joined #openstack-meeting-308:48
*** amotoki has quit IRC08:49
*** amotoki has joined #openstack-meeting-308:50
*** markvoelker has quit IRC08:55
*** Rajen_liyuanzhen has joined #openstack-meeting-309:01
*** milan has joined #openstack-meeting-309:02
*** Rajen_liyuanzhen has quit IRC09:03
*** spzala has joined #openstack-meeting-309:07
*** andreas_s has quit IRC09:07
*** spzala has quit IRC09:11
*** markvoelker has joined #openstack-meeting-309:16
*** markvoelker has quit IRC09:20
*** JeanBriceCombebi has joined #openstack-meeting-309:21
*** andreas_s has joined #openstack-meeting-309:21
*** zz_dimtruck is now known as dimtruck09:23
*** c64cosmin_ has joined #openstack-meeting-309:28
*** c64cosmin_ has quit IRC09:29
*** c64cosmin_ has joined #openstack-meeting-309:29
*** c64cosmin has quit IRC09:29
*** stanzgy has quit IRC09:31
*** fawadkhaliq has quit IRC09:32
*** fawadkhaliq has joined #openstack-meeting-309:32
*** dimtruck is now known as zz_dimtruck09:33
*** c64cosmin_ has quit IRC09:35
*** amotoki has quit IRC09:35
*** c64cosmin has joined #openstack-meeting-309:35
*** JeanBriceCombebi has quit IRC09:36
*** reedip__ has quit IRC09:44
*** yamamot__ has quit IRC09:54
*** yamamot__ has joined #openstack-meeting-309:55
*** cartik has quit IRC09:56
*** reedip__ has joined #openstack-meeting-309:57
*** coolsvap_ has joined #openstack-meeting-310:01
*** zhurong has quit IRC10:04
*** coolsvap has quit IRC10:04
*** sdague has joined #openstack-meeting-310:05
*** sdague has quit IRC10:05
*** sdague has joined #openstack-meeting-310:05
*** spzala has joined #openstack-meeting-310:08
*** markvoelker has joined #openstack-meeting-310:10
*** stevemar has quit IRC10:13
*** spzala has quit IRC10:13
*** markvoelker has quit IRC10:15
*** stevemar has joined #openstack-meeting-310:15
*** andreas_s has quit IRC10:16
*** zz_dimtruck is now known as dimtruck10:24
*** pgadiya has quit IRC10:30
*** pgadiya has joined #openstack-meeting-310:30
*** andreas_s has joined #openstack-meeting-310:32
*** emagana has joined #openstack-meeting-310:37
*** kmartin has quit IRC10:38
*** dimtruck is now known as zz_dimtruck10:39
*** emagana has quit IRC10:42
*** jed56 has quit IRC10:44
*** yamamot__ has quit IRC10:53
*** yamamot__ has joined #openstack-meeting-310:53
*** coolsvap_ has quit IRC10:57
*** ccamacho has quit IRC11:00
*** markvoelker has joined #openstack-meeting-311:04
*** stendulker has quit IRC11:06
*** reedip__ has quit IRC11:06
*** amotoki has joined #openstack-meeting-311:07
*** ccamacho has joined #openstack-meeting-311:08
*** tellesnobrega is now known as tellesnobrega_af11:08
*** spzala has joined #openstack-meeting-311:09
*** markvoelker has quit IRC11:09
*** baoli has joined #openstack-meeting-311:10
*** kenji-i has quit IRC11:11
*** pgadiya has quit IRC11:11
*** baoli_ has joined #openstack-meeting-311:12
*** pgadiya has joined #openstack-meeting-311:12
*** spzala has quit IRC11:14
*** jlanoux_ has joined #openstack-meeting-311:14
*** baoli has quit IRC11:16
*** jlanoux has quit IRC11:18
*** mrunge has joined #openstack-meeting-311:20
*** baoli_ has quit IRC11:21
*** baoli has joined #openstack-meeting-311:22
*** baoli has quit IRC11:25
*** baoli has joined #openstack-meeting-311:25
*** belmoreira has quit IRC11:31
*** Poornima has quit IRC11:34
*** rtheis has joined #openstack-meeting-311:42
*** salv-orl_ has quit IRC11:43
*** ccamacho is now known as ccamacho|lunch11:43
*** fawadkhaliq has quit IRC11:46
*** fawadkhaliq has joined #openstack-meeting-311:47
*** ociuhandu has joined #openstack-meeting-311:49
*** JeanBriceCombebi has joined #openstack-meeting-311:55
*** yamamot__ has quit IRC11:56
*** yamamot__ has joined #openstack-meeting-311:56
*** markvoelker has joined #openstack-meeting-311:58
*** ducttape_ has joined #openstack-meeting-311:59
*** yamamot__ has quit IRC12:01
*** yamamot__ has joined #openstack-meeting-312:01
*** yamamot__ has quit IRC12:01
*** salv-orlando has joined #openstack-meeting-312:01
*** yamamot__ has joined #openstack-meeting-312:02
*** markvoelker has quit IRC12:03
*** ddieterly has joined #openstack-meeting-312:10
*** spzala has joined #openstack-meeting-312:10
*** itxaka is now known as itxaka|out12:12
*** spzala has quit IRC12:15
*** ddieterly is now known as ddieterly[away]12:21
*** ducttape_ has quit IRC12:22
*** ccamacho|lunch is now known as ccamacho12:28
*** zz_dimtruck is now known as dimtruck12:31
*** yamamot__ has quit IRC12:40
*** yamamoto has joined #openstack-meeting-312:40
*** dimtruck is now known as zz_dimtruck12:41
*** ddieterly[away] is now known as ddieterly12:44
*** atuvenie_ has joined #openstack-meeting-312:45
*** belmoreira has joined #openstack-meeting-312:46
*** claudiub has joined #openstack-meeting-312:47
*** markvoelker has joined #openstack-meeting-312:52
*** sdake has joined #openstack-meeting-312:55
*** sverma has quit IRC12:56
*** markvoelker has quit IRC12:57
*** sdake_ has joined #openstack-meeting-312:58
*** sagar_nikam has joined #openstack-meeting-312:59
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed May 11 13:00:17 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
openstackThe meeting name has been set to 'hyper_v'13:00
*** milan_ has joined #openstack-meeting-313:00
claudiubhellou OpenStack people. :)13:00
abalutoiuhello13:00
sagar_nikamHello13:00
c64cosminHello all13:00
atuvenie_Hi all13:01
atuvenie_o/13:01
claudiubSoo.. let's try to keep this meeting short. :)13:01
*** dtardivel has joined #openstack-meeting-313:01
claudiub#topic Newton workitems13:02
*** ddieterly has quit IRC13:02
*** openstack changes topic to "Newton workitems (Meeting topic: hyper-v)"13:02
*** sdake has quit IRC13:02
*** sverma has joined #openstack-meeting-313:02
*** banix has joined #openstack-meeting-313:02
claudiubSo, as you well know, we will bring the Windows / Hyper-V world to different projects in the OpenStack ecosystem.13:02
claudiube.g. freezer, monasca, magnum13:03
*** seanmurphy has joined #openstack-meeting-313:03
claudiuband designate13:03
*** milan has quit IRC13:03
sagar_nikamclaudiub:nice13:03
claudiubfor monasca I've already started, the 1st patch should be fine, but I still have to create a proper environment and test it.13:03
sagar_nikamthe windows agent for monasca does not work13:04
sagar_nikamcould you get it working ?13:04
sagar_nikamwhen you submitted the first patch ?13:04
sagar_nikami mean start agent does not work13:04
claudiubsagar_nikam: yep, that's another thing I'll have to do.13:04
*** itxaka|out is now known as itxaka13:05
claudiubas I've mentioned, I don't have a monasca environment yet, so I'll be able to make the agent work when I get my env ready. :)13:05
sagar_nikamok13:05
claudiubsagar_nikam: the first patch I've sent right after the summit.13:05
claudiubthere is also another wmi_checker module in the monasca-agent project that I'll have to take a look into13:05
sagar_nikamok13:06
sagar_nikamclaudiub: can you please give me the link of that patch13:06
claudiubalso, I've looked around in the code. they seem to have a module which acts very similarly with futures.thread_pool, that we use in networking_hyperv as well.13:06
claudiubI'll probably try to replace that module with futures.thread_pool.13:07
claudiub#link https://review.openstack.org/#/c/311925/13:07
claudiubbasically, this patch is almost identical to the patch I've made in ceilometer, when we wanted to replace the in-tree utils with os-win.13:08
*** Sonu has joined #openstack-meeting-313:08
sagar_nikamok13:08
*** amotoki has quit IRC13:08
sagar_nikamshall i add the required team members of monasca for review ?13:08
claudiubanyways. another thing that seemed interesting to me, was the monasca-logging agent. I'll take a look at is as well, see that it will work on WIndows as well.13:08
sagar_nikamis it ready to be reviewed ?13:08
claudiubsagar_nikam: I've marked it as WIP for the time being. I'll remove it after I see everything working properly. :)13:09
sagar_nikamsure13:09
SonuI would like to review. Link?13:10
sagar_nikamhttps://review.openstack.org/#/c/311925/13:10
SonuThanks.I would like to review the metric lists that we can support.13:10
claudiubalso, for monasca-logging agent, it might be interesting for it to also fetch Hyper-V events. Will investigate further.13:10
*** andymaier has joined #openstack-meeting-313:10
sagar_nikamthat would be nice to send HyperV events13:11
sagar_nikami think we should not send all events13:11
sagar_nikammay be just the relevant ones13:11
*** spzala has joined #openstack-meeting-313:11
claudiubSonu: sagar_nikam: just a heads-up, the monasca inspectors and the ceilometer inspectors are the same, or at least the HyperVInspectors are.13:11
sagar_nikamceilometer was for metering and monasca for monitoring13:11
sagar_nikamjust wondering how they are same, can you please provide more details13:12
claudiubsagar_nikam: yeah, from what I understood, monasca-polling is also able to separate logging / events per tenant, which could be trickier to pull off with hyper-v events.13:12
*** lblanchard has joined #openstack-meeting-313:13
claudiubsagar_nikam: sure. there are a few differences between them. first of all, monasca boasts a much better response time when doing queries13:13
claudiubsince ceilometer uses mongodb, after a few thousands or more metrics, the response times can get a bit crazy.13:14
sagar_nikamok13:14
claudiubmonasca uses another database type, I'm forgetting which one at the moment, but it works better with large ammounts of data13:15
sagar_nikammy question was on how the same/similar code in hyperv can be used in both monasca and ceilometer13:15
Sonuinfluxdb13:15
claudiubSonu: yep, that's the one.13:15
Sonuthey have vertica integration as well...but for enterprise13:15
*** spzala has quit IRC13:16
claudiubanyways, it can handle a lot more data, which is very important, since monasca polls metrics every 30 seconds by default, while ceilometer does it every 600 seconds.13:16
claudiubalternatively, we can use the ceilometer-polling agent with the monasca backend. this the so-called ceilasca. :)13:17
*** milan_ has quit IRC13:17
sagar_nikamclaudiub: so which approach is planned for hyperv ? monasca or ceilasca ?13:18
claudiub+ monasca-agent seems to be polling / monitoring other metrics as well. (e.g. services status)13:18
*** milan_ has joined #openstack-meeting-313:18
claudiubsagar_nikam: ceilometer-polling is already working on hyper-v, so ceilasca should already work. but we should also have monasca-agent working as well.13:19
*** banix has quit IRC13:19
claudiubso, users can choose their favorite toys. :)13:19
sagar_nikamclaudiub: agree... i think the first priority should be monasca agent13:19
*** mkovacik__ has joined #openstack-meeting-313:19
claudiubanyways. I'll have my env ready by next week hopefully. won't take long to have everything working after that.13:20
*** spzala has joined #openstack-meeting-313:20
*** Shivakumar has joined #openstack-meeting-313:20
sagar_nikamclaudiub:as of today does ceilsca work ? for hyperv13:20
sagar_nikamsince we already have ceilometer agent for hyperv13:21
claudiubplus, the monasca core are pretty cool with deadlines and deadlines, which is neat. :)13:21
claudiubsagar_nikam: I've mentioned before: it should work, but I haven't tested it yet. will try it.13:21
sagar_nikamok13:22
*** vhoward has joined #openstack-meeting-313:22
claudiubok.. so... for other projects, abalutoiu has been designated to lead the effort for the project named designate. :)13:22
*** milan_ has quit IRC13:22
ShivakumarHi, with native thread patch applied, hyperv agent hangs sometimes.13:23
claudiublpetrut is freezing with enthusiasm over the prospect of working on freezer. :)13:23
claudiubShivakumar: ok, will tackle that as soon as we change the topic.13:24
*** mkovacik__ is now known as milan13:24
sagar_nikamclaudiub: nice to see some progress on monasca, designate and freezer13:24
claudiubok, so I guess that's it for this topic.13:25
claudiub#topic networking-hyperv13:25
*** openstack changes topic to "networking-hyperv (Meeting topic: hyper-v)"13:25
claudiubok, so, first of all, just a small announcement, a little while ago, networking-hyperv has been removed from neutron's governance, as it was calling the Hyper-V APIs, which is not "open-source".13:26
claudiubthis happened because the neutron core decided that they can't vouch for some networking agents / plugins in their governance, if not everything is opensource.13:27
claudiubso, networking-hyperv is not the only one in this situation, there were quite a few that were removed from governance because of this.13:27
claudiubbuut, since today, networking-hyperv is under winstackers governance, so yeay. :)13:28
*** ddieterly has joined #openstack-meeting-313:28
claudiubthat means we have a little bit more liberty and control with the project.13:28
claudiubShivakumar: ok, so you're saying you have issues with native threads? what branch? are you using pymi?13:29
claudiubwhat os-win version?13:29
Shivakumaractually, we are using pymi with stable liberty hyperv code13:29
claudiubbecause this hasn't happened in the Hyper-V CI since it was originally merged in Mitaka, like 2-3 months ago I think.13:29
Shivakumarwe backported native thread and enhanced rpc patches, able to get good scale results upto 1000VMs13:30
sagar_nikamclaudiub: we hit 2 issues in scale tests, will mention once we are done with the networking topic13:31
claudiubShivakumar: ah, I see. I suppose that it hangs during agent's startup?13:31
Shivakumarbut, sometimes hyperv agent hangs while making an rpc call, and fails to report again13:31
Shivakumarsince we have introduced threading for processing new ports, is it due to Logger  ?13:32
Shivakumaryes, cladiub ..during agent startup13:33
*** zz_dimtruck is now known as dimtruck13:33
Shivakumarwhen there are no VM ports to be processed, but if an update comes from other HyperV hypervisor13:33
claudiubShivakumar: yeah, it feels like you're missing something.13:33
claudiubShivakumar: I think that the main thread is locked. I don't know exactly what you've backported.13:34
Shivakumari have backported native thread and enhanced rpc only13:35
claudiubShivakumar: I suppose you've also backported the patch with the vNIC event listeners, right?13:35
Shivakumarno, we left that13:35
Shivakumarhave a doubt13:36
Shivakumardo we need to add this content https://github.com/openstack/networking-hyperv/blob/master/hyperv/neutron/__init__.py13:36
Shivakumarmeans, add  monkey patch ?13:36
*** JeanBriceCombebi has quit IRC13:36
claudiubhonestly, some logs could be useful, as well as a list of cherry-pick you've done. otherwise I'm just doing guess work.13:37
Shivakumarhttps://review.openstack.org/#/c/263865/13:37
Shivakumarhttps://review.openstack.org/#/c/264235/13:37
*** jed56 has joined #openstack-meeting-313:38
claudiubShivakumar: hm, in liberty, the neutron-hyperv-agent was still being loaded from neutron13:38
Shivakumarok,13:38
claudiubShivakumar: so, monkey patching was already being done there.13:38
*** tonytan4ever has joined #openstack-meeting-313:38
Shivakumari think here also we have a separate repo for hyperv13:39
Shivakumarso, if hyperv is separate, does it mean we need monkey patching ?13:40
Shivakumarseparately ?13:40
claudiubShivakumar: what do you mean?13:41
claudiubShivakumar: also, logs pls. :)13:41
Shivakumarsure,13:41
Shivakumar2016-05-06 18:16:23.986 1780 INFO neutron.agent.securitygroups_rpc [req-6f83c39f-7370-43bb-af2b-3c3c0d9f2ff1 - - - - -] Provider rule updated 2016-05-06 18:16:23.986 1780 INFO neutron.agent.securitygroups_rpc [req-6f83c39f-7370-43bb-af2b-3c3c0d9f2ff1 - - - - -] Refresh firewall rules 2016-05-06 18:16:23.986 1780 DEBUG neutron.api.rpc.handlers.securitygroups_rpc [req-6f83c39f-7370-43bb-af2b-3c3c0d9f2ff1 - - - - -] Get13:41
claudiubput them here: http://paste.openstack.org/13:42
claudiuband post a link.13:42
Shivakumarhttp://paste.openstack.org/show/496733/13:42
claudiubcan you put the entire log?13:43
*** dedery_ has joined #openstack-meeting-313:43
claudiubor at least from when the agent starts?13:43
*** ddieterly is now known as ddieterly[away]13:45
*** absubram has quit IRC13:45
*** jmckind has joined #openstack-meeting-313:46
*** dedery has quit IRC13:46
*** markvoelker has joined #openstack-meeting-313:46
claudiubShivakumar: also, there's another patch that could be useful: https://review.openstack.org/#/c/297773/13:46
*** dedery_ has quit IRC13:47
claudiubanyways... since we have a few other things to discuss...13:47
claudiub#topic open discussion13:47
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:47
sagar_nikamclaudiub: 2 bugs we found in our scale tests13:48
Shivakumari have pasted complete log http://paste.openstack.org/show/496736/13:48
sagar_nikamhttps://bugs.launchpad.net/nova/+bug/147329113:48
openstackLaunchpad bug 1473291 in OpenStack Compute (nova) "nova compute on hyperv don't wait for vif plugged event from neutron" [Medium,Confirmed]13:48
sagar_nikamhttps://bugs.launchpad.net/nova/+bug/158016113:48
openstackLaunchpad bug 1580161 in OpenStack Compute (nova) "hyper-v nova compute go down with error Error writing vm console log file from serial console pipe. Error: [Errno 2] No such file or directory" [Undecided,Confirmed]13:48
sagar_nikamfix for bug 1580161, lpetrut: already provided13:49
sagar_nikamwe will use it13:49
claudiubsagar_nikam: cool, for the second one, lpetrut already sent up a patch.13:49
claudiub#link https://review.openstack.org/#/c/314590/13:49
sagar_nikamany plans for the first bug ?13:49
claudiubcurrently the gate is down, so I'll +2 it when it's ok.13:49
sagar_nikamwe had hit that bug in juno and now in liberty13:49
claudiubas for the 1st one, we've already fixed it compute_hyperv in mitaka.13:49
claudiubsagar_nikam: it is marked as bp though.13:50
*** hdaniel_ has quit IRC13:50
claudiub#link https://blueprints.launchpad.net/nova/+spec/hyper-v-spawn-on-neutron-event13:50
*** fawadkhaliq has quit IRC13:50
*** fawadkhaliq has joined #openstack-meeting-313:50
sagar_nikamclaudiub: plans to upstream it in newton ?13:50
claudiubsagar_nikam: yup. there are going to be a few changes to it though.. there is some duplicate code related to this sort of mechanism in all drivers. I want to refactor it.13:51
sagar_nikamok13:51
sagar_nikamit would be good if it gets merged in newton, we have seen that issue since juno13:52
*** jmckind_ has joined #openstack-meeting-313:52
claudiubhere's the link to the implementation in compute_hyperv:13:52
claudiub#link https://review.openstack.org/#/c/292615/13:52
sagar_nikamregarding the first bug for which lpetrut: submitted a patch in stable/liberty13:52
sagar_nikamyou will +2 it ?13:53
claudiubsagar_nikam: this issue doesn't exist anymore in mitaka, since port binding is being done a lot faster13:53
claudiubeven without this bp.13:53
claudiubsagar_nikam: will do as soon as Jenkins gives its +1. Hyper-V CI already passed on the patch, which was needed, so it's good.13:53
sagar_nikamclaudiub: should i wait for it to be merged in stable/liberty13:53
sagar_nikamclaudiub: ok thanks13:54
claudiubsagar_nikam: yeah, you can.13:54
sagar_nikamclaudiub: alexpilotti: not in meeting?13:55
sagar_nikamhad some updates on freerdp13:55
*** ddieterly[away] is now known as ddieterly13:55
*** jmckind has quit IRC13:55
claudiubor you can cherry-pick it in your downstream repos, if you have any. :)  but it probably won't take long to be merged.13:55
claudiubalex is currently away on some bussiness trip13:55
*** markvoelker has quit IRC13:55
claudiubc64cosmin: ^13:56
c64cosminI'm here for any RDP info though13:56
sagar_nikamclaudiub: since it will not take long to merge, i will probably wait13:56
claudiubc64cosmin: welcome. :)13:56
*** rbak has joined #openstack-meeting-313:56
sagar_nikamc64cosmin: sometimes the freerdp service hangs13:56
claudiubc64cosmin: ?????????13:56
*** dimtruck is now known as zz_dimtruck13:56
*** auggy has joined #openstack-meeting-313:56
sagar_nikamand restart also hangs... only way to recover is kill wsgate.exe13:57
*** Sonu has quit IRC13:57
*** atuvenie_ has quit IRC13:57
*** spzala has quit IRC13:57
c64cosminsagar_nikam: that happens with the installed version right?13:57
*** atuvenie_ has joined #openstack-meeting-313:57
*** spzala has joined #openstack-meeting-313:57
sagar_nikamc64cosmin: yes, installer taken from cloudbase13:58
c64cosminsagar_nikam: we also have a beta version, the fact that the service hangs if well known and had been taken care of13:58
c64cosminthough, the beta version is also unstable13:59
sagar_nikamc64cosmin: i used the stable version, if the issue is fixed in beta... when will come in stable ?13:59
c64cosminsagar_nikam: cannot approximate for sure, but that is main priority right now on this project14:00
sagar_nikamsure... will wait14:00
sagar_nikamlet me know when you have a good stable build14:00
*** sigmavirus24_awa is now known as sigmavirus2414:01
sagar_nikamwe are almost out of time... we will discuss in detail in next meeting14:01
c64cosminsagar_nikam: I sure will :)14:01
*** spzala has quit IRC14:02
claudiubwell... this was a.. short meeting. :)14:02
claudiubthanks all for attending. :)14:02
sagar_nikamthanks all14:02
claudiubsee you next time!14:02
claudiub#endmeeting14:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:02
openstackMeeting ended Wed May 11 14:02:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-05-11-13.00.html14:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-05-11-13.00.txt14:02
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-05-11-13.00.log.html14:02
c64cosminthank you all14:02
*** auggy has left #openstack-meeting-314:03
*** salv-orl_ has joined #openstack-meeting-314:04
*** jed56 has quit IRC14:04
*** jed56 has joined #openstack-meeting-314:05
*** pgadiya has quit IRC14:05
*** sverma has quit IRC14:05
*** salv-orlando has quit IRC14:06
*** jed56 has quit IRC14:07
*** jed56 has joined #openstack-meeting-314:07
*** jed56 has quit IRC14:08
*** jed56 has joined #openstack-meeting-314:09
*** fawadkhaliq has quit IRC14:10
*** fawadkhaliq has joined #openstack-meeting-314:10
*** zz_dimtruck is now known as dimtruck14:14
*** jed56 has quit IRC14:15
*** jed56 has joined #openstack-meeting-314:15
*** fawadkhaliq has quit IRC14:15
*** Swami has joined #openstack-meeting-314:17
*** jed56 has quit IRC14:18
*** jed56 has joined #openstack-meeting-314:18
*** rbrndt has joined #openstack-meeting-314:20
*** rossella_s has quit IRC14:25
*** Shivakumar has quit IRC14:27
*** sdake_ has quit IRC14:28
*** sdake has joined #openstack-meeting-314:29
*** spzala has joined #openstack-meeting-314:29
*** rbrndt has left #openstack-meeting-314:29
*** amotoki has joined #openstack-meeting-314:30
*** jed56 has quit IRC14:31
*** jed56 has joined #openstack-meeting-314:32
*** dand has joined #openstack-meeting-314:34
*** rhochmuth has joined #openstack-meeting-314:34
*** dand has quit IRC14:35
*** sdake has quit IRC14:35
*** JeanBriceCombebi has joined #openstack-meeting-314:36
*** ddyer has joined #openstack-meeting-314:36
*** ajmiller has quit IRC14:36
*** iyamahat has joined #openstack-meeting-314:37
*** yamahata has joined #openstack-meeting-314:38
*** bklei has joined #openstack-meeting-314:38
*** JeanBriceCombebi has quit IRC14:40
*** ajmiller has joined #openstack-meeting-314:42
*** jed56 has quit IRC14:47
*** jed56 has joined #openstack-meeting-314:47
*** jayahn has joined #openstack-meeting-314:48
*** woodster_ has joined #openstack-meeting-314:50
*** spzala has quit IRC14:53
*** spzala has joined #openstack-meeting-314:53
*** emagana has joined #openstack-meeting-314:53
*** witek has joined #openstack-meeting-314:57
*** anilvenkata has quit IRC14:57
*** mtanino has joined #openstack-meeting-314:58
*** koji has joined #openstack-meeting-314:58
*** ashwin has joined #openstack-meeting-314:58
*** ddieterly has quit IRC14:58
*** flintHP has quit IRC14:58
*** claudiub has quit IRC14:59
*** flintHP has joined #openstack-meeting-314:59
*** kamil_ has joined #openstack-meeting-314:59
*** thatsdone has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed May 11 15:00:19 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
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmutho/15:00
rbako/15:00
witekhello15:00
bkleio/15:00
kojihi15:00
jayahnhi15:00
kamil_hey15:00
flintHPhi15:00
rhochmuthhi flintHP15:01
ddyero/15:01
*** ddieterly has joined #openstack-meeting-315:01
thatsdonehi15:01
rhochmuthhi ddyer15:01
ashwinhi good morning15:01
*** s-kawabata_ has joined #openstack-meeting-315:01
rhochmuthhi thatsdone15:01
rhochmuthhi ashwin15:01
ddieterlyhi everybody!15:01
rhochmuthhi everyone else15:01
ddieterlythat covers it15:01
rhochmuththe agenda is at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:02
*** tgraichen has joined #openstack-meeting-315:02
rhochmuthAgenda for Wednesday May 11, 2016 (15:00 UTC)15:02
rhochmuth1.monasca-transform15:02
rhochmuth1.https://wiki.openstack.org/wiki/Monasca/Transform15:02
rhochmuth2.Reviews15:02
rhochmuth1.https://review.openstack.org/#/c/307963/15:02
rhochmuth2.https://review.openstack.org/#/c/289675/15:02
rhochmuth3.https://review.openstack.org/#/c/306621/15:02
rhochmuth4.https://review.openstack.org/#/c/286281/15:02
rhochmuth5.https://review.openstack.org/#/q/topic:sporadic_metric15:02
rhochmuth6.https://review.openstack.org/#/c/310511/15:02
rhochmuthWhat I woudl like to cover first is monasca-transform15:02
s-kawabata_o/15:02
rhochmuthwe have a few folks form hpe that are here today15:02
rhochmuthashwin, ddyer and flinHP15:02
*** absubram has joined #openstack-meeting-315:03
rhochmuthflintHP15:03
*** s-kawabata_ is now known as shinya_kwbt_15:03
rhochmuthso, if we could cover that in the first half hour that woudl be good15:03
rhochmuththen we can look at some fo the reviews that have been posted15:03
bklei+115:03
rhochmuth#topic monasca-transform15:03
*** openstack changes topic to "monasca-transform (Meeting topic: monasca)"15:03
*** sdake has joined #openstack-meeting-315:03
rhochmuthso, i'll let ashwin and team introduce you to the project and what is being done15:03
rhochmuthand then open up for questions15:04
rhochmuthashwin u have the floor15:04
ashwinhi all15:04
rhochmuthhi ashwin15:04
ashwinwe will do a walkthrough new project monasca-transform15:04
ashwinBlueprint is at https://blueprints.launchpad.net/monasca/+spec/monasca-transform15:04
ashwinMore detailed design is on the wiki at : https://wiki.openstack.org/wiki/Monasca/Transform15:05
ashwinThe main purpose of this project is to aggregate and transform metrics published to monasca's metrics topic in Kafka15:06
*** bmotz_ has joined #openstack-meeting-315:06
ashwinand publish new aggregated metrics back to metrics topic in Kafka.15:07
ddieterlywhat use cases does it cover that can't be covered by the alarm definition language?15:07
ashwinThere are several use cases which we can address e.g. aggregate individual metrics, combine multiple metrics to derive a new metric, find say a rate at which metric changes over a time interval etc15:08
*** slogan has joined #openstack-meeting-315:08
witekdo you want to write back to the same topic?15:09
*** sagar_nikam has quit IRC15:10
*** c64cosmin has quit IRC15:10
ddieterlyaggregrate individual metrics and combine multiple metrics to derive a new metric seem like functionality that already exists in monasca from the users point of view using existing tools/queries15:10
*** tomasztrebski has joined #openstack-meeting-315:10
ashwinyes the idea is aggregated metric is just like any other monasca metrics so you can set alarms etc on the aggregated metric15:10
*** matrohon has quit IRC15:10
ddieterlyfind the rate and deriving metrics seem like new functionality15:10
ddieterlywhy was apache spark chosen instead of using storm?15:12
ashwinDeriving metrics using complex business logic For example consider the periodic heart beat metrics which come from a VM indicating what state the VM was in. One might have to look at how the state of  VM changed over the target time interval and then use some business logic come up with a new metric which would indicate the amount of time that the VM was in a usable state15:13
*** mrhillsman has joined #openstack-meeting-315:14
mrhillsmano/15:14
bkleiwill this all be project-scoped/multi-tenant?15:15
bkleilike for operators, as well as cloud customers?15:15
*** numans has quit IRC15:15
rhochmuthaggregations can be defined based on any parameters15:15
rhochmuththe project/tenant aggregations will be the normal one15:16
rhochmuthfor exampel calculating the number of swift bytes in/out per tenant15:16
rhochmuthfor metering/billing purposes15:16
bkleiand operators can aggregate across all projects?15:17
rhochmuthyes, i believe so15:17
bkleithat would be good15:17
rhochmuthi don't think that was the intended usage15:17
*** yamamoto has quit IRC15:17
rhochmuthbut it is just code15:17
*** salv-orl_ has quit IRC15:17
tomasztrebskiwould I be able to compose mem.used_md with cpu.user_perc somehow with this ?15:17
tomasztrebskiit that the case ?15:18
*** yamamoto has joined #openstack-meeting-315:18
ashwinyes our initial use cases involve aggregating metrics over entire cloud, by all hosts, by each host, by all projects etc15:18
rhochmuthnot sure that was a target, but i'm not sure what you mean by that15:18
rhochmuthtomasz ^^^15:18
bkleinice ashwin15:19
*** abalutoiu has quit IRC15:19
*** slogan has quit IRC15:19
ashwinyes you could for example get mem.total_mb metrics which are per host metrics and aggregate to get total available memory across all hosts15:19
tomasztrebskicomposite alarms - that's the name that at least read somewhere, the case is to compose two distinct metrics to say: trigger ALARM if cpu exceeds 50% and in the sime memory consumption goes above 70%15:19
*** ericksonsantos has joined #openstack-meeting-315:19
rhochmuthtomasz: that isn't the intended usage15:20
tomasztrebskimhm, thx15:20
ericksonsantoshello everyone o/15:20
*** slogan has joined #openstack-meeting-315:21
*** salv-orlando has joined #openstack-meeting-315:21
tomasztrebskihmm...my reviewer from sporadic metrics :D, hello there :-)15:21
iurygregoryhi people  =) we are late sorry15:21
ericksonsantostomasztrebski, haha15:21
*** milan has quit IRC15:21
rhochmuthhi, we are in theprocess of reviewing the monasca-transform engine15:21
rhochmuthlet's stay focused for another 10 minutes15:21
*** fawadkhaliq has joined #openstack-meeting-315:22
iurygregorytks for the update rhochmuth15:22
*** claudiub has joined #openstack-meeting-315:22
rhochmuththen do intros and reivews15:22
ashwinWe are planning on using Spark, Spark streaming on collecting set of metrics and use generic transformation components to run series of aggregation operations over a time interval and publish the metrics back to Kafka.15:22
ashwinall the components are written in python15:23
*** JOlsen has joined #openstack-meeting-315:23
*** rbrndt has joined #openstack-meeting-315:23
ashwinAll transformations will be data driven, and it should be possible to add new aggregation routines by configuration changes.15:23
ashwinGeneric transformation components will be re-usable and easy to change, add new ones or make changes to existing ones15:24
ashwinShould be possible to write python unit tests  to test each transformation, also series of transformations (transformation pipeline) can be tested.15:24
ddieterlywas an evaluation done between spark and storm? monasca uses storm and the team has expertise in it. why was spark a better alternative to storm?15:24
*** galstrom_zzz is now known as galstrom15:24
sloganCan I build the transform engine from code as well as from config?15:25
*** galstrom is now known as galstrom_zzz15:25
ddyerspark was chosen for a couple of reasons:15:25
sloganEr, pipeline15:25
*** galstrom_zzz is now known as galstrom15:26
ddyer1. python support15:26
*** kmartin has joined #openstack-meeting-315:26
kamil_and monasca-ui will be extended to set/configure "new aggregations" ?15:26
rhochmuthkamil_: there isn't an API at this time15:26
ddyer2. we had previous experience with hadoop and spark supported a lot of the same mechanisms15:26
ddyer3. it has a lot of momentum in terms of development and we wanted something others would be willing to invest in15:27
witekhow much of the code is ready? the repo is empty15:28
ddieterlyddyer it would be good to update the wiki with those reasons so that people know why spark was chosen15:28
ddyergood idea15:28
rhochmuthkamil_: so you can deploy the service and specify the transform via configuration and new metrics will be created15:28
flintHPwe are in the process of preparing the code for submittal/review15:28
*** tonytan_brb has joined #openstack-meeting-315:28
rhochmuthwitek: should be published soon15:28
ashwinwe found the ability to write unit tests in python to test components really useful (vs hadoop where this was impossible)15:28
rhochmuthso, we are kinda getting to the end of a 1/2 hour15:29
rhochmuthshould probably talk next stpes15:29
rhochmuthsteps15:29
rhochmuthfollow-up15:29
rhochmuththe code will be submited for review15:29
rhochmuthand then folks can start using it15:30
rhochmuthand reviewing it15:30
tomasztrebskisweet :D15:30
rhochmuthso, does anyone have any major issues with this code being submitted for review15:31
rhochmuthand proceeding15:31
rhochmuthwould anyone like another session after reviewing the wiki15:31
witekplease squash the commits :)15:31
rhochmuthlol15:31
ddieterlywe need to see it before we can make that determination15:31
*** tonytan4ever has quit IRC15:31
slogan:-)15:31
rhochmuthso the code will end-up in the monasca-transform repo15:31
*** armax has joined #openstack-meeting-315:32
rhochmuthas a single new review15:32
ddieterlywe eagerly await your review for submission ;-)15:32
rhochmuthso, do we want to discuss again next week any issues?15:32
rhochmuthwe can use gerrit for comments and other questions15:33
rhochmuthso, i think that would be preferred right now15:33
*** divya_ has joined #openstack-meeting-315:33
tomasztrebski+1 gerrit15:33
flintHPwow, we already have a +1 (grin)15:34
ashwinthank you everyone!15:34
*** belmoreira has quit IRC15:34
rhochmuthok, so ashwin and team please submit, and then we can review and discuss any subsequent follow-up15:34
rhochmuth"submit the review" that is15:34
*** vishwanathj has joined #openstack-meeting-315:34
ashwinsounds good thanks roland!15:35
rhochmuththanks ashwin et al15:35
*** hosanai has joined #openstack-meeting-315:35
ddieterlyroland is speaking latin again15:35
rhochmuththe other topic listed on the agenda is reviews15:35
rhochmuth#topic reviews15:36
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:36
rhochmuthhttps://review.openstack.org/#/c/307963/15:36
bkleithat's me asking for status15:36
bkleifix metric-list limits15:36
bkleiplease to merge :)15:36
rhochmuthyes, i think it is ready15:36
bkleithis is a blocker for us at twc15:37
rhochmuththe problem from last week was that there were several performance issues identified15:37
rhochmuthrbarndt did a huge amount of testing and performance analysis last week15:37
rhochmuthbut i think it is ready to go now15:38
bkleilast i heard from ryan brandt that he was ok now?15:38
rhochmuthcorrect15:38
rbrndtyup15:38
rhochmuthhttps://review.openstack.org/#/c/289675/15:38
rhochmuththis one is also ready, jsut waiting on some more testing15:39
*** bpokorny has joined #openstack-meeting-315:39
rhochmuthactually I =2'd that one, but the merge didnt' go through15:39
bkleiok, rbak is excited to pull that in and make grafana changes15:39
rbrndtthat one is based off the metrics-list fix15:39
rbrndtso need that first15:39
rhochmuthright15:40
*** armax has quit IRC15:40
rhochmuthi'll discuss after doen here, and possibly merge both15:40
bkleisweet15:40
rhochmuthhttps://review.openstack.org/#/c/306621/15:40
bkleithat's me15:41
bkleii think it's ready -- no oustanding comments15:41
bkleiovs plugin15:41
*** dwalleck has joined #openstack-meeting-315:41
rhochmuthcan this be used in devstack15:41
bkleii need to stand up devstack again -- does it use ovs?15:42
rhochmuthi don't know15:42
bkleii'll get the answer to that15:42
*** bpokorny has quit IRC15:43
rhochmuthhas anyone else tested your plugin15:43
rhochmuthall i can do at this point is a cursory review of code, ...15:43
bkleitested i'm not sure -- i have been getting comments from folks that seem like neutron people15:43
*** bpokorny has joined #openstack-meeting-315:43
bkleiwe've tested it at twc in the labe with and without HA routers15:44
bkleis/labe/lab15:44
rhochmuthwell, i'll take another look15:44
bkleicool15:44
rhochmuthi asked some folks in hpe india that are looking at vswitch metrics15:44
rhochmuthsome of them left comments15:44
bkleiaah, cool, that must be sonu and selvakumar15:45
rhochmuthsonu yes15:45
rhochmuthlet's move on next review15:45
shinya_kwbt_Openstak default is linuxbridge. I don't know devstack uses ovs.15:45
rhochmuthhttps://review.openstack.org/#/c/286281/15:45
bkleithx shinya -- so this won't help devstack if that's the default15:46
*** divya_ has quit IRC15:46
bkleioh -- that kv hint is mine too15:47
rbrndtI mentioned it in my comment, but I didn't see any differences in my testing of the hint15:47
rbrndtAnd exploring the queries we use it seems like vertica is already satisfying everything locally15:48
rbrndtIt doesn't hurt anything though15:48
bkleiyeah -- i think it'll free vertica resource/bandwidth up more than anything15:48
bkleiaccording to artem at vertica -- the hint eliminates node chatter15:48
sloganDevstack supports ovs, I think the default networking is ovs15:49
*** seanmurphy has left #openstack-meeting-315:49
shinya_kwbt_http://docs.openstack.org/developer/devstack/guides/neutron.html?highlight=openvswitch15:49
clarkbslogan: default is still nova network which does not use ovs, but if you enable neutron then the default for neutron is ovs15:49
sloganJust enable the q services, I might be able to help with a local.conf if needed15:49
rhochmuththanks shinya15:49
sloganRight clarkb15:50
*** andymaier has quit IRC15:50
sloganNovas net ID something I've never used so to me neutron iscalways on :-)15:50
rhochmuthso let's move on15:51
rhochmuthhttps://review.openstack.org/#/q/topic:sporadic_metric15:51
rhochmuthtomasz, witek15:51
*** dwalleck has quit IRC15:51
witekTomasz has moved the newest code to deterministic_alarm topic15:52
*** galstrom is now known as galstrom_zzz15:52
rhochmuthi didn't get to review the latest round of changes15:52
rhochmuthinternet was out last night15:52
rhochmuthbut i heard that craig added comments15:52
*** galstrom_zzz is now known as galstrom15:52
*** armax has joined #openstack-meeting-315:53
witekin sporadic_metric we have the additional sporadic field for metric, which can be persisted15:53
witekso we can see, what kind of metric we are getting15:53
witekis that functionality still useful after implementing deterministic_alarms?15:54
rhochmuthit isn't required15:54
rhochmuthas the deterministic_alarms are independent of sporadic metrics15:54
tomasztrebskiroland, I forgot to add you as reviewer to the newest changes, that's fixed right now15:54
*** Sukhdev has joined #openstack-meeting-315:54
rhochmuthyou can apply a deterministic_alarm to either a periodic or sproadic metric15:55
rhochmuthand it is done independently15:55
rhochmuththe only use that the sproadic metrics have at this point are to supply additional information about metrics15:55
witekexactly15:55
rhochmuthso it is still useful, but not required15:56
tomasztrebskiwell, not exactly, we could "propose" user to use non-deterministic alarm for sporadic metrics15:56
tomasztrebskidirectly in ui15:56
tomasztrebskiobviously the checkox would be mutable, so user could proceed as he wishes15:56
rhochmuthso, i t hink the question is whether we shoudl keep sporadic metrics too15:56
*** catherineD has joined #openstack-meeting-315:57
tomasztrebskiI think we should with having the case above in my head15:57
rhochmuthi see15:57
rhochmuthi was assuming it woudl be removed just to simplify15:57
*** armax has quit IRC15:57
ericksonsantostomasztrebski, +115:57
*** fitoduarte has joined #openstack-meeting-315:57
rhochmuthok, let me think about that some more15:57
witekok, thanks Roland15:57
rhochmuthi'll discuss with craig15:57
*** igorn has joined #openstack-meeting-315:58
tomasztrebskithat'd be up to the user to decide if he want to accept "the proposition" - so the checkbox (or something, I haven't decided yet) would be mutable in monasca-ui15:58
*** mickeys has joined #openstack-meeting-315:58
tomasztrebskiok, thx15:58
rhochmuthtomasz: are you planning on python changes too15:58
tomasztrebskiright now I am in middle of checking if I need to do anything for deterministic alarms15:58
rhochmuthtomasz: also agree with last statements15:58
tomasztrebskitill now I found one "bug" in monasca-api documentation :D15:59
rhochmuthso, i think we've run out of time again15:59
rhochmuththis is happenign a lot15:59
rhochmuthdo we need a longer time-slot or two meetings15:59
tomasztrebskia lot of interest in monasca :)15:59
rhochmuthyup15:59
rhochmuththat's good15:59
rhochmuthi hate rushing through and skipping over stuff16:00
rhochmuthwe have a few folks that showed up today that we didnt' even get introduced16:00
*** tgraichen has quit IRC16:00
rhochmuthok, i need to close the meeting down16:00
*** cjvolzka has joined #openstack-meeting-316:00
rhochmuthsorry foks16:00
*** nkrinner is now known as nkrinner_afk16:00
rhochmuthtoo much to discuss today16:00
*** dwalleck has joined #openstack-meeting-316:00
iurygregorynps ^^16:00
ericksonsantosno problem, we can introduce ourselves in the next meeting. :)16:00
witekbye16:00
rhochmuthi'll be in the openstack-monasca room16:01
rhochmuth#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Wed May 11 16:01:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-05-11-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-05-11-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-05-11-15.00.log.html16:01
*** bklei has quit IRC16:01
shinya_kwbt_bye16:01
tomasztrebskicya16:01
hogepodge#startmeeting defcore16:01
openstackMeeting started Wed May 11 16:01:31 2016 UTC and is due to finish in 60 minutes.  The chair is hogepodge. 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
hogepodge#topic roll call16:01
*** openstack changes topic to "roll call (Meeting topic: defcore)"16:01
*** jlanoux_ has quit IRC16:01
dwallecko/16:01
catherineDo/16:01
luzCo/16:01
*** iurygregory has left #openstack-meeting-316:01
nikhilo/16:02
*** rbrndt has left #openstack-meeting-316:02
docaedoo/16:02
*** koji has left #openstack-meeting-316:02
*** ametts has joined #openstack-meeting-316:02
* docaedo can be here for the first half at least :)16:02
amettso/16:02
*** fawadkhaliq has quit IRC16:02
hogepodgeThis week and the next our esteemed co-chairs, eglute and  markvoelker16:03
hogepodgewon't be here16:03
*** gema has joined #openstack-meeting-316:03
*** witek has left #openstack-meeting-316:03
hogepodgeOk, let's start16:03
hogepodge#topic cycle naming16:03
*** openstack changes topic to "cycle naming (Meeting topic: defcore)"16:03
*** tomasztrebski has quit IRC16:03
hogepodgeLunar won by one vote in our polling16:04
*** hosanai has quit IRC16:04
*** kamil_ has quit IRC16:04
*** shinya_kwbt_ has quit IRC16:04
hogepodgeThanks for everyone's suggestions and votes.16:04
dwalleckI finally won something! :)16:04
hogepodge#link results https://www.surveymonkey.com/results/SM-7JQKSYLR/16:04
docaedosounds like a good opportunity to volunteer them for many tasks?16:04
hogepodgedocaedo: definitely, they have a lot of +2's piling up :-D16:05
hogepodgedwalleck: \o/16:05
catherineDInteresting I also vote for Lunar... How come there is only one vote?16:05
hogepodgecatherineD: Hm, I'm wondering if it's a cache issue.16:06
*** ddieterly is now known as ddieterly[away]16:06
gemalunar has 8 votes, no?16:06
*** shamail has joined #openstack-meeting-316:06
catherineDnvm16:06
gemaat least on my screen16:06
catherineDoh won by 1 vote16:06
hogepodgecatherineD: I think it caches the results if you've voted.16:06
catherineDnot only one vote  my mistake16:06
hogepodgecatherineD: ah, ok.16:06
*** GheRivero has joined #openstack-meeting-316:07
hogepodgemoving on16:07
hogepodge#topic Interoperability, APIs, Branding, and Beyond.16:07
*** openstack changes topic to "Interoperability, APIs, Branding, and Beyond. (Meeting topic: defcore)"16:07
hogepodgenikhil: this was your topic16:07
nikhilo/16:07
shamailSorry for being late.16:07
nikhilThere are some services that are using internal only APIs (meant for admin) to manipulate image data.16:07
nikhilThis results in loosely coupling of the image information with the image data.16:08
nikhilquestions:16:08
nikhil1) How can we come up with definition of an Image in openstack?16:08
nikhil2) Do I need to invest time to research what all projects comsuming glance are not assuming incorrect constructs and possibly improve documentation?16:08
nikhilinterop if our #1 priority so I want to ensure we do all the right things16:08
* nikhil done16:08
nikhilor do I need to start a ML thread on this?16:10
VanLnikhil: I think the docs should be clear on what is the "correct" way to deal with an image, especially if there are multiple ways to do so16:10
hogepodgeIt seems like 1 should be easy. An image is a set of files (in the case where kernel and ramdisk are provided seperately) that can successfully boot on a given hypervisor. Naturally, an image that can boot in one cloud may not be able to boot in another given implementation details.16:10
hogepodgeSo, it would be nice for that information to be discoverable.16:11
nikhilVanL: noted16:12
nikhilhogepodge: hmm, I think there are a few gotchas to it.16:12
nikhilfor example, a full template like vmware instance template or ovf may not be an image if we think in terms of glance16:12
*** vhoward has quit IRC16:12
dwalleckSince image files have a type, could that be used to determine if an image works for a given cloud?16:12
nikhilfor but industry standards it should be to support say some sort of certification16:13
*** flintHP has quit IRC16:13
nikhildwalleck: we want to support that as pluggable way in the import mechanism so that more info can be given to a user16:13
nikhilbut there are some cases when the volumes (stored as images) in glance are16:13
hogepodgea pluggable import mechanism needs to be discoverable16:14
VanLI wonder if we are getting ahead of ourselves here. I'm not sure we want to be so heavyweight at the moment.16:14
dwalleckNikhil: ++ to the idea of discoverability16:14
nikhilstored as meta information and sometimes the flatenning happesn behind the scenes as there are assumptions on how the glance_store utility driver is supported16:14
hogepodgemore so, plugins needs to pass the defined test suite16:15
nikhilhogepodge: the API will be fine16:15
VanLRIght now, I think the first course would be to look at the APIs and their usage (both by projects, by implementations, and how you consider to be "correct" going forward) and try to come up with a clear way of communicating about what is expected by clients.16:15
nikhilhogepodge: what you get out of an image may or may not be. I may need to do more research on this.16:15
hogepodgeIt's not ok to let plugins be defined to do whatever they want with arbitrarily defined inputs and outputs. That works directly against api interoperability.16:15
*** GheRivero has left #openstack-meeting-316:16
nikhilhogepodge: the plugins would be simplistic and will not impact the API.16:16
hogepodgeWe face an uphill battle with differences in image formats16:16
VanLI think any discussions around images should be driven by identified differences and how they affect the API (VIO/Xen/KVM differences)16:16
hogepodgenikhil: it will if the plugins can be arbitrary.16:16
nikhilVanL: I need to evaluate right now if we need to work hard on supporting a API for services like Nova so that they can use the right way of doing things.16:17
*** slogan has quit IRC16:17
hogepodgenikhil: using cinder as an example, the user-facing api doesn't change when the driver plugin changes16:17
nikhil(or wait another 3 years to get that support added)16:17
*** ddieterly[away] is now known as ddieterly16:17
nikhilhogepodge: no, the API won16:17
nikhilwon't*16:17
nikhilhogepodge: I can go over the import spec on why not later if needed.16:18
catherineDFron interop point of view, image should be something that customers can bring to an OpenStack cloud.  Which may be a package like ovf a a file in different format ... more important is what does OpenStack core APIs support16:18
dwalleckhodgepodge: As long as every backend supports every API facing action, then that's true16:18
hogepodgenikhil: to be honest, I'd like for us to stop using the nova proxy api, and we're in a place where we can start moving in that direction by requiring the direct apis and deprecating the compute-image apis (of which a large number are flagged because of proxy issues)16:18
catherineDhogepodge: ++16:19
nikhilhogepodge: This discussion is separate from the Nova proxy API which are read only (user facing). Write (snapshots) are handled at the virt level.16:19
nikhilI am talking about the right way the different virt drivers use to upload data to glance -- which is drastically different for each driver.16:19
catherineDnikhil: different way means different APIs?16:20
nikhilcatherineD: glance cannot support ovf completely today. (Technical limitations)16:20
nikhilcatherineD: for example:16:20
hogepodgenikhil: isn't it in the scope of glance and the cross project work to make sure the backends work? I'm confused about what you're asking for16:20
nikhilsome drivers are using location_add to "directly set" a location on an image16:21
*** armax has joined #openstack-meeting-316:21
catherineDnikhil: understand that ovf is not support .. we need to concentrate on the format that OpenStack supports today16:21
catherineDas our concentration is trailing ...16:21
hogepodgenikhil: who writes the drivers?16:22
nikhilhogepodge: at the summit a issue of "0 sized" images came up; this means that the location magic is used to make the copy on write work for volume snapshots.16:22
nikhilcatherineD: ok, thanks for that clarification.16:22
nikhilhogepodge: the virt drivers are in Nova.16:22
hogepodgeSo it's a cross project issue?16:23
*** claudiub has quit IRC16:23
nikhilhogepodge: on 0 sized images, I need more research on what a end user will get back when they do image-download. We have to rely on individual drivers to do the right thing.16:23
hogepodgenikhil: can you write up a summary of these issues and how they impact the api and interoperability and sent it to the mailing list? It seems like this is going to be a deeper discussion than we might have time for.16:23
nikhilhogepodge: if a image is uploaded through nova virt driver in a way it becomes unusable to end user and there are assumptions on it being usable to just internal deployment, I need to do more research on it. Personally, I DO NOT want this to be GLance16:24
catherineDTo me volume snapshot won;t be a enduser support unless it can be downloaded ... and upload to a different OpenStack clouds.16:24
nikhilGLance's responsibility.16:24
nikhilhogepodge: ok, thanks. So, I take it we need initial research.16:25
nikhil(meaning we do care about interop beyond the APIs)16:25
*** thatsdone has quit IRC16:25
hogepodgenikhil: so it the upshot that snapshot shouldn't be required as a capability?16:25
*** Poornima has joined #openstack-meeting-316:25
nikhilhogepodge: I am just asking for standardizing/documenting best practices and something that won't make glance responsible (as it may appear so).16:26
nikhil(snapshot seems like a important capability)16:26
catherineDsnapshot should be a required feature but the image of the image of the snapshot maynot be16:27
hogepodgestandardizing/documenting best practices for what?16:27
nikhilsnapshot16:27
*** ashwin has quit IRC16:27
VanLnikhil: Regardless of it being important, is it sufficiently widely supported, necessary, etc to be *required* at all times in all OpenStack clouds?16:27
catherineDthat means a particular env should support snapshot but the image of the snapshot may not  be transfered to a diff environment16:27
VanLThat is the question that needs to be answered.16:28
hogepodgethat's very much a technical issue. If snapshot isn't available as a working and interoperable feature, that's guidance we need to use in determining the capabilities16:28
hogepodgecatherineD: that's ok, because OpenStack will never have what I would call binary compatibility16:28
gemahogepodge: but then people wont' be able to literally "move their workloads"16:29
nikhilI can take more of this offline.16:29
catherineDhogepodge: we need to test that an env can create and boot the created snapshot on same env16:29
catherineDgema: workload is something predefine but snapshot is the capturing of something at the moment ...16:30
hogepodgegema: we lost that when we allowed for choice of hypervisor. Your application code should still be portable, but the images you boot aren't. Now, it's not as bad as you might think. Infra is using dib to create one image then transform it into the expected formats for different clouds16:30
gemahogepodge, catherineD: ok, sounds reasonable16:30
catherineDit would be nice to support transferable snapshot but that would be a more advance feature and shoud not be core16:31
hogepodgecatherineD: +116:31
gemayep16:31
*** markvan has joined #openstack-meeting-316:31
hogepodgenikhil: can I give you an action item to write a summary for the mailing list?16:32
*** neiljerram has quit IRC16:32
nikhilhogepodge: please do16:32
hogepodge#action nikhil write glance issues summary for defcore mailing list16:33
hogepodgeAnything else on this topic?16:33
nikhilnone, I do have a bit of overlap in the next topic16:33
nikhilbut that can be no-op from the defcore team16:33
hogepodgesure, I kind of merged the two topics together, so we can move on to your next section16:34
nikhilok, thanks16:34
nikhilI will ask next set of questions then16:34
nikhil3. Do we need to account for all the internal usage of glance in services as interop is meant for end users?16:34
nikhil4. As per Mark’s blog we _could_ have more than one API for same operation so for nova we want to keep the old API for POST + PUT that streams data to glance nodes and is not as complicated as newer import API16:35
* nikhil done16:35
nikhilSo, I can chat a bit more on these things:16:37
nikhili) the RefStack testing will expect the interoperable API to exist in clouds. We can be clear on communicating that.16:37
hogepodgeOn 3, defcore is concerned with public facing, non-admin apis. One would hope the public-facing apis are durable to internal implementation details. If that durability isn't there it's a problem for choosing those apis for interoperability16:37
catherineDTo me , APIs that are end user facing should be accounted for interop  ... anything internal should be cloud configuration options16:37
nikhilhogepodge: are _all_ APIs expected to be so. (I'm assuming yes)16:39
VanL+1 catherineD -- and *should not be used* in any tests required for interop16:39
nikhil?16:39
catherineDThat mean we need to carefully choose the must-pass tests to matches the internal and external API used16:39
catherineDVanL: yea16:39
hogepodgeTo 4, having more than one API is problematic, because if you offer n apis you'll have n choices. My opinion is that, under guidance from the TC, project leaders, and deployers, we pick APIs that we would expect every cloud to have. that creates an environment where app and sdk developers have guidance as to which API they can expect16:39
nikhilhogepodge: what if it's a technical limitation (or something too complex)?16:40
hogepodgenikhil: what is the technical limitation?16:40
*** tellesnobrega_af is now known as tellesnobrega16:41
hogepodgeVanL: the internal choice of a hypervisor bleeds through. You have to provide a bootable image, which is a config detail. Are you suggesting that DefCore just give up on image api completely?16:41
nikhilhogepodge: it may take a few mins to discuss that. if we want to discuss it I can arrange for a more high bandwidth communication channel?16:41
catherineDnikhil: would the technical limitation applied due to a certion configuration options?16:41
*** ivar-lazzaro has joined #openstack-meeting-316:41
hogepodgenikhil: it is also a good candidate for the mailing list. We're at 15 minutes remaining and I wanted to make sure we had time for the next topic since we didn't get to it last week.16:42
nikhilcatherineD: It will be hard to type it all here without creating more confusion.16:42
nikhilhogepodge: ok, thanks. I may take a week to get that done if it's ok?16:42
nikhil(too much churn happening in glance atm)16:42
VanLhogepodge: If the end result would be "All clouds must be KVM" then that is not workable.16:43
hogepodgenikhil: sure, we want to make sure we have a thorough understanding of the issues16:43
nikhilhogepodge: ok, thanks.16:43
*** JOlsen has quit IRC16:43
hogepodgeVanL: that isn't the case right now. the test fixtures are configurable to take that into account16:43
catherineDnikhil: thx for bringing up the topics here ...16:43
nikhilanytime!16:44
hogepodgenikhil: thank you. We really appreciate it.16:44
nikhil(I'm just planning the cycle milestones & mine)16:44
nikhilhogepodge: right back at ya.16:44
hogepodgeOk, are we ok to move on to the next topic and take the larger discussion to the mailing list?16:44
nikhilyes, thx16:45
hogepodge#topic Test spec16:45
*** openstack changes topic to "Test spec (Meeting topic: defcore)"16:45
hogepodgegema: you've been the lead on this16:45
gemaI am working on a commit that I plan to submit on Friday and I have a couple of questions16:45
gemadwalleck: do you have any extra input from your analysis that you'd like me to consider?16:46
*** shamail has quit IRC16:46
dwalleckgema: Not at the moment. I think a lot of points ended up getting discussed in the etherpad over the atomicity point16:47
* dwalleck deletes atomicity from his vocabulary16:47
gemadwalleck: ok, sounds good16:47
gemais the spec supposed to cover API design guidelines?16:47
gemabecause some of the discussion in the etherpad seems to point towards that16:47
gema#link https://etherpad.openstack.org/p/DefCoreSpec-draft16:48
gemathings like: Prefer Basic REST CRUD operations: Create, Read, Update, Delete?16:48
dwalleckgema: There is an API working group who puts out standards for OpenStack APIs16:48
gemado we need to point that out on a test spec?16:48
gemadwalleck: so we don't need to cover that16:49
catherineDgema: I think the discussion is about API testing guidelines not API design16:49
gemacatherineD: cool, because I was about to leave that part blank, I don't feel qualified to write it :)16:49
gemaok, I have all I need then16:49
gemahogepodge: thanks16:49
hogepodgeOn this topic, does anyone want to add anything else?16:50
dwalleckgema: I think the functionality of many of the APIs kind of looks like CRUD, but there's often more16:50
*** claudiub has joined #openstack-meeting-316:50
*** Swami has quit IRC16:50
gemadwalleck: yeah, I figured as much that is why I didn't want to get into that16:51
gemaon a test spec16:51
dwalleckgotcha16:51
* dwalleck didn't sleep so is a bit out of it16:51
hogepodgeOk, we'll move on. Please update the etherpad if you have more comments.16:51
hogepodgegema: thanks for working on this, and let us know if you need anything else to help out16:52
gemahogepodge: will do, thanks16:52
hogepodge#topic TC Resolutions16:52
*** openstack changes topic to "TC Resolutions (Meeting topic: defcore)"16:52
*** amotoki has quit IRC16:52
hogepodgeThere's been quite a bit of good discussion on the mailing list regarding the resolutions.16:52
*** fawadkhaliq has joined #openstack-meeting-316:53
hogepodgeThe TC will be voting on them no earlier than the May 24 meeting.16:53
hogepodgerelevant links16:53
hogepodge#link https://review.openstack.org/#/c/312718/16:53
hogepodge#link https://review.openstack.org/#/c/312719/16:53
hogepodge#link Discussion http://lists.openstack.org/pipermail/defcore-committee/2016-May/001095.html16:54
hogepodgeAny comments or feedback?16:54
hogepodgeMoving on16:54
hogepodge#topic Interoperability Issues Report16:55
*** openstack changes topic to "Interoperability Issues Report (Meeting topic: defcore)"16:55
hogepodge#link https://etherpad.openstack.org/p/DefCoreInteropReport16:55
hogepodgeReminder to vote on issues, contribute thoughts, or add new issues.16:55
hogepodgeMark and Egle are looking to winnow that list down to 5.16:56
hogepodge#topic Work Items16:56
*** openstack changes topic to "Work Items (Meeting topic: defcore)"16:56
hogepodgeThe remainder of the agenda is largely work items from the previous meeting and Austin summit.16:56
*** jmckind_ has quit IRC16:57
hogepodgeIn the remaining minutes, if anyone has updates please feel free to let us know.16:57
*** claudiub has quit IRC16:57
*** alaski has joined #openstack-meeting-316:57
dwalleckI've been buried since I came back from the summit, just starting to dig back out16:58
*** andreas_s has quit IRC16:58
*** belmoreira has joined #openstack-meeting-316:58
hogepodgeI had burst of work, then also got delayed with other things. Turning my attention back to a number of items though, so expect new patches.16:58
hogepodgeOk, let's call it a meeting.16:58
hogepodgeThanks everyone!16:59
dwalleckthanks!16:59
gemathanks!16:59
*** dwalleck has quit IRC16:59
hogepodge#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Wed May 11 16:59:24 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-05-11-16.01.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-05-11-16.01.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-05-11-16.01.log.html16:59
catherineDthank! bye!16:59
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed May 11 17:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
melwitto/17:00
belmoreirao/17:00
doffmo/17:00
alaskibauzas: ping17:00
alaskicool, let's get going17:00
*** gema has left #openstack-meeting-317:01
alaski#topic Testing17:01
*** openstack changes topic to "Testing (Meeting topic: nova_cells)"17:01
*** mriedem has joined #openstack-meeting-317:01
mriedemo/17:01
alaskino breaks on v1 that I can see17:01
alaskiand the cell job caught something dansmith tried to sneak by which would break it17:01
alaskiso huzzah17:01
mriedemhe's so sneaky17:01
melwittnice17:01
dansmithheh17:01
alaskiI don't see ctrath so we'll skip talking about v2 testing17:02
* bauzas lurks17:02
mriedemccarmack you mean17:02
alaskiwoops17:02
mriedembut yeah17:02
alaskiyeah17:02
alaski#topic Open Reviews17:02
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"17:02
alaskihttps://etherpad.openstack.org/p/newton-nova-priorities-tracking17:02
*** auggy has joined #openstack-meeting-317:02
alaskiplenty of things to look at17:03
alaskiI think most of us here have series up, we should take a moment to look at someone elses17:03
alaski#topic Open Discussion17:03
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:03
mriedemshould probably add the keypair stuff to that17:03
alaskimriedem: yes17:03
bauzasYup please17:03
*** ivar-lazzaro has quit IRC17:04
alaski#action alaski add keypair patches to review priorities if someone doesn't beat me to it17:04
mriedemyou slackers are all supposed to be reivewing api-ref stuff today too17:04
mriedemshame!17:04
dansmithI have to add a fake test for mriedem first17:04
alaskiok17:04
dansmiththe bottom patch is already +W17:05
dansmithbut give me a bit after this meeting and I'll have it ready17:05
alaskiI don't have any items on the agenda for open discussion, but I do have some questions for folks17:05
alaskidansmith: you and jay had a pow wow on migrating stuff to the cell db17:05
alaskican you share the gist of the plan?17:05
dansmithwell,17:06
bauzasPow wow ?17:06
alaskiby stuff I mean inventory and resource type things17:06
dansmithhe pasted some of it into the channel, I just came up with a few steps,17:06
alaskibauzas: they sat around a campfire and discussed, metaphorically17:06
dansmithbut the thing I had that was more concerning is that .. if we move inventory to the api,17:06
dansmiththen we've got the cells making an upcall to the api db to write that information,17:06
dansmithwhich I don't like17:06
dansmithlonger term we'll be making a REST call to the api to manage those things, which is better17:06
alaskiyea17:07
bauzasI agree it's a sad thing17:07
alaskibut that longer term is actually getting approachable right?17:07
dansmithyes17:07
doffmThe upcall is short lived. hopefully.17:07
dansmithso we'll have to do it in the short term of course17:07
dansmithI just want to make sure we don't let it go longer than we need17:07
alaskiokay17:08
doffmdansmith: What about instance groups? I presume we just move all of those up in to the API as well?17:08
bauzasBecause it's the compute manager save thing ?17:08
doffmI don't think there is an upcall there.17:08
dansmithdoffm: actually I want to move those into the fire, but...17:08
bauzasI mean the RT17:08
alaskidansmith: that basically ties scheduler work into cellsv2 a bit, so I may divert my energy in that direction to help out if needed17:08
alaskidoffm: my understanding was that anything that's purely for scheduling would move to the api db17:09
alaskiwhich is actually a lot of what Nova keeps in the db17:10
dansmithalaski: yeah, we're definitely getting into the intersection area at this point17:10
*** spzala has quit IRC17:10
bauzasthat's because the compute nodes need to update somehow the DB for the scheduler, right17:10
bauzasso, if we have an scheduler DB, then...17:10
doffmThere was some discussion from johnthetubaguy about leaving some of the instance groups in the cell. (InstanceGroupHostMappingThing). But i'll presume its all going to api.17:10
doffmFor now.17:11
bauzaswithout really needing yet a REST API call17:11
bauzasso, my thoughts are17:11
bauzas1/ do an upcall for Newton17:11
alaskidoffm: +1 for presuming17:11
bauzas2/ discuss on any need for a sched DB in Ocata17:11
bauzas3/ implement if so, or wait for the REST call17:11
dansmithbauzas: no, it's really 1. do the upcall now, 2. get a REST call very soon, 3. the rest17:12
*** fawadkhaliq has quit IRC17:12
alaski4/ think of a new db to split out next17:12
dansmiththe split and db stuff can come later, we should have the rest call ASAP so that we're decoupled regardless17:12
alaski+117:12
bauzasdansmith: well, it needs a placement client first, right? plus the fact we need to have old n-1 computes having that17:12
bauzasdansmith: which means the upcall is N+O right?17:12
dansmithit needs some isolation17:12
alaskipart of the REST work would be a client17:12
dansmithI think we might get the REST bit done in newton, which would mean we could split or do other things in O17:13
bauzasI assume the compute services using that placement client if so17:13
alaskiand computes don't call the scheduler17:13
alaskinvm, you may be talking about updates17:13
bauzasthey actually call "a scheduler client"17:13
bauzasso the problem is really with upgrades17:13
bauzasbecause we already have that facade17:14
*** jed56 has quit IRC17:14
*** spzala has joined #openstack-meeting-317:14
*** mickeys has quit IRC17:15
*** anilvenkata has joined #openstack-meeting-317:15
alaskiif we get a new API and computes using a new client in N, the scheduler keeps supporting current mechanisms in N, then in O we can drop all of that right?17:15
*** mickeys has joined #openstack-meeting-317:15
dansmithyar17:15
bauzasalaski: yeah, but that means 1.5 milestones for both implementing the REST API and the client :)17:15
bauzas(and approving the spec)17:16
mriedembauzas: you better get to work then17:16
mriedemit's definitely a stretch17:16
bauzasmriedem: heh, that's the exact reason why I threw off my api-ref duty17:16
bauzasin order to make my non-prio BPs done first before helping17:17
alaskibauzas: you're more up to date on scheduling plans, are there dependencies that have to happen before working on the REST stuff?17:17
mriedemwe have to get this spec approved for one https://review.openstack.org/#/c/300176/17:17
alaskior anyone who knows17:17
mriedemi haven't reviewed the updates since monday17:17
mriedembut i'm told jay and chris are on the same page17:17
bauzasalaski: the generic-resource-pools spec is kinda not needing deps17:17
dansmithshall we move on?17:18
alaskiokay17:18
dansmithI'm hangry and looking for this to move along :)17:18
alaskialright17:18
alaskifrom my end I'm finishing up docs for my policy changes, and then I'm done with that except for review feedback17:18
bauzasalaski: apart the tables move to the API DB and the policy stuff you volunteered17:18
dansmithalaski: are you working on quota migration?17:19
alaskidoffm: are you pretty set on the direction of your specs or are there things to discuss here?17:19
alaskidansmith: I am not17:19
doffmalaski: Pretty set.17:19
*** spzala has quit IRC17:19
dansmithalaski: why for/17:19
alaskidansmith: does that need someone?17:19
dansmithalaski: it doesn't need someone, it needs _you_17:19
alaskiheh17:19
*** mickeys has quit IRC17:20
melwittwas that supposed to be a question mark again17:20
dansmithmelwitt: yeah17:20
*** TravT has joined #openstack-meeting-317:20
alaskiI'm still pushing on reworking scheduling for cells, but I'll look at quotas as well17:20
doffmActually.... I'll ask about the quota spec.17:20
doffmmriedem and alaski gave me some feedback on how quotas should be migrated.17:20
doffmBy putting the migration code in the quota db driver.17:21
doffmIs that how we want to do things this cycle? Quick and dirty. :)17:21
doffmFix things in this code later.17:21
mriedemyes17:21
alaskiyeah, we can't wait on fixing quotas17:21
doffmOk, will update spec with that feedback this afternoon.17:21
*** mickeys has joined #openstack-meeting-317:21
mriedemalso, fyi, i'm overly full of pizza right now17:22
doffmMe too.17:22
doffmAnd mountain dew.17:22
mriedemand oreos17:22
bauzasoh man17:22
*** ddieterly is now known as ddieterly[away]17:22
alaskiyou're going to make dansmith jealous17:22
*** jayahn has quit IRC17:23
dansmithso .. hungry17:23
mriedemthat's the idea17:23
alaskiI don't have anything else though, so if nobody has a topic17:23
bauzasfortunately, I already ate17:23
mriedemi've heard that snickers really satisfies17:23
alaskime too17:23
alaskialright, thanks everyone17:23
alaski#endmeeting17:23
bauzas++17:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:23
openstackMeeting ended Wed May 11 17:23:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-05-11-17.00.html17:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-05-11-17.00.txt17:23
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-05-11-17.00.log.html17:23
*** mriedem has left #openstack-meeting-317:23
*** atuvenie_ has quit IRC17:24
*** auggy has left #openstack-meeting-317:25
*** bpokorny has quit IRC17:26
*** bpokorny has joined #openstack-meeting-317:27
*** egallen has joined #openstack-meeting-317:27
*** ociuhandu has quit IRC17:27
*** Swami has joined #openstack-meeting-317:28
*** mickeys has quit IRC17:33
*** mickeys has joined #openstack-meeting-317:33
*** claudiub has joined #openstack-meeting-317:34
*** milan has joined #openstack-meeting-317:36
*** fitoduarte has quit IRC17:37
*** mickeys has quit IRC17:38
*** spzala has joined #openstack-meeting-317:43
*** ccamacho is now known as ccamacho|away17:46
*** ociuhandu has joined #openstack-meeting-317:51
*** ivar-lazzaro has joined #openstack-meeting-317:53
*** belmoreira has quit IRC17:54
*** anilvenkata has quit IRC17:56
*** ivar-lazzaro has quit IRC17:57
*** mickeys has joined #openstack-meeting-317:57
*** ivar-lazzaro has joined #openstack-meeting-317:57
*** panzrwagn has joined #openstack-meeting-317:59
*** chandanc_ has joined #openstack-meeting-318:01
*** numans has joined #openstack-meeting-318:03
*** ivar-lazzaro has quit IRC18:06
*** kmartin has quit IRC18:06
*** chandanc_ has quit IRC18:09
*** mickeys has quit IRC18:09
*** panzrwagn has quit IRC18:10
*** mickeys has joined #openstack-meeting-318:10
*** abalutoiu has joined #openstack-meeting-318:19
*** mickeys has quit IRC18:20
*** mickeys has joined #openstack-meeting-318:21
*** mickeys has quit IRC18:22
*** mickeys has joined #openstack-meeting-318:22
*** ddieterly[away] has quit IRC18:22
*** abalutoiu_ has joined #openstack-meeting-318:25
*** madhu_ak has joined #openstack-meeting-318:25
*** ivar-lazzaro has joined #openstack-meeting-318:26
*** evgenyf has joined #openstack-meeting-318:27
*** abalutoiu has quit IRC18:28
*** Poornima has quit IRC18:29
*** Sukhdev has quit IRC18:29
*** krotscheck_ has joined #openstack-meeting-318:30
*** Sukhdev has joined #openstack-meeting-318:31
*** krotscheck has quit IRC18:31
*** ddieterly has joined #openstack-meeting-318:32
*** krotscheck_ is now known as krotscheck18:33
*** mickeys has quit IRC18:33
*** mickeys has joined #openstack-meeting-318:33
*** catherineD has left #openstack-meeting-318:34
*** belmoreira has joined #openstack-meeting-318:34
*** Poornima has joined #openstack-meeting-318:34
*** tonytan_brb has quit IRC18:36
*** Poornima has quit IRC18:36
*** mickeys has quit IRC18:38
*** mickeys has joined #openstack-meeting-318:39
*** fitoduarte has joined #openstack-meeting-318:39
*** egallen has left #openstack-meeting-318:39
*** ddieterly is now known as ddieterly[away]18:40
*** ddieterly[away] is now known as ddieterly18:47
*** sdake has quit IRC18:48
*** mickeys has quit IRC18:49
*** mickeys has joined #openstack-meeting-318:50
*** pt_15 has joined #openstack-meeting-318:51
*** vgridnev_ has joined #openstack-meeting-318:57
*** vgridnev_ has quit IRC18:57
*** numans has quit IRC18:59
*** tonytan4ever has joined #openstack-meeting-318:59
*** vgridnev_ has joined #openstack-meeting-319:00
*** itxaka has quit IRC19:00
*** sambetts is now known as sambetts|afk19:04
*** ddyer has quit IRC19:05
*** carolbarrett has joined #openstack-meeting-319:05
*** dtardivel has quit IRC19:09
*** lpetrut has joined #openstack-meeting-319:12
*** jmckind has joined #openstack-meeting-319:13
*** ddieterly is now known as ddieterly[away]19:13
*** ddieterly[away] is now known as ddieterly19:14
*** mickeys has quit IRC19:14
*** pvaneck has joined #openstack-meeting-319:15
*** mickeys has joined #openstack-meeting-319:15
*** vhoward has joined #openstack-meeting-319:16
*** DevonBoatwright has joined #openstack-meeting-319:16
*** DevonBoatwright has left #openstack-meeting-319:16
*** ddieterly is now known as ddieterly[away]19:17
*** ivar-lazzaro has quit IRC19:17
*** vgridnev_ has quit IRC19:19
*** mickeys has quit IRC19:19
*** carolbarrett has quit IRC19:23
*** ducttape_ has joined #openstack-meeting-319:26
*** lpetrut has quit IRC19:32
*** dcwangmit01 has joined #openstack-meeting-319:38
*** ddieterly[away] is now known as ddieterly19:38
*** dcwangmit01 has quit IRC19:39
*** matrohon has joined #openstack-meeting-319:39
*** dcwangmit01 has joined #openstack-meeting-319:39
*** milan_ has joined #openstack-meeting-319:43
*** milan has quit IRC19:44
*** ccamacho|away has quit IRC19:58
*** yohoffman has joined #openstack-meeting-319:59
*** ccamacho has joined #openstack-meeting-319:59
*** itxaka has joined #openstack-meeting-319:59
david-lyle#startmeeting Horizon20:00
openstackMeeting started Wed May 11 20:00:04 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. 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: Horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
itxakao/20:00
*** iyamahat has quit IRC20:00
david-lylerobcresswell had other engagements so you're stuck with me20:00
*** hurgleburgler has joined #openstack-meeting-320:00
tsufievo/20:01
hurgleburgler(◠‿◠✿)ノ20:01
*** yamahata has quit IRC20:01
david-lyleanother large crowd ;)20:01
bpokornyo/20:02
*** tyr_ has joined #openstack-meeting-320:02
david-lyleand two look familiar from 12 hours ago20:02
david-lylelet's get started20:02
*** peristeri has joined #openstack-meeting-320:02
david-lyleThe agenda for today can be found at20:02
david-lyle#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_2016-05-11_2000_UTC20:03
david-lylethere are a couple of notices20:03
david-lyleone the bug report is updated20:03
*** salv-orl_ has joined #openstack-meeting-320:03
david-lyle#link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport20:03
david-lylewith some bugs and bps currently targeted20:04
david-lyleso take a look and prioritize appropriately20:04
david-lyle2nd notice is about the midcycle20:04
david-lylea poll for dates is:20:04
david-lyle#link http://doodle.com/poll/xvchsbbs4qz9tzr720:05
*** sdake has joined #openstack-meeting-320:05
david-lyleif you plan on attending please vote with your availability20:05
david-lyleI'm not entirely sure the where20:05
*** alaski has left #openstack-meeting-320:06
hurgleburglerthe where might dictate the ability to attend20:06
david-lyleright20:06
david-lyleit was not in the email to the ML either20:06
david-lylejust checked20:06
*** salv-orlando has quit IRC20:06
david-lyle#action robcresswell tells us where we're going for midcycle20:06
tsufievrobcreswell mentioned that it may be San Francisco20:06
david-lyleok20:07
david-lylethat's it for notices and agenda20:07
david-lyle#topic Open Discussion20:07
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"20:08
bpokornyDoes anyone know what's going on with the integration tests lately?20:08
tsufievhopefully once https://review.openstack.org/#/c/315050/ is merged we should get much fewer failures20:08
bpokornyGreat. Thanks, tsufiev.20:09
tsufievbut if it's not, here is an etherpad we're going to update to keep track of actual failures: https://etherpad.openstack.org/p/horizon-integration-tests-failures20:09
tsufievI find it easier to use than kibana20:09
tsufievcategorize failures, see how frequent they are etc20:10
bpokornyok, good to know.20:10
david-lyletsufiev: what about elastic recheck?20:10
tsufievcurrent form is not final, may adjust it to our needs20:10
tsufievdavid-lyle, what's the usual workflow with elastic recheck that may help us in navigating in different failures?20:11
david-lyleif you put those signatures in elastic recheck, you would get a count on the failure numbers and the notice when it fails on the patch in gerrit20:11
tsufievI mean I'm not very familiar with ER facilities that really help finding out root causes...20:11
david-lyleand an entry on here http://status.openstack.org//elastic-recheck/20:12
*** vgridnev has joined #openstack-meeting-320:12
tsufievokay, I'll try it :)20:12
*** vgridnev has quit IRC20:12
david-lyleit's more about quantifying the failures and assess if they actually went away20:12
david-lylejust something for the future20:13
tsufievthanks, I have to eventually get used to these big data helpers20:13
tsufievmy first impression with kibana wasn't very... friendly20:14
david-lylethe second thing to check is http://status.openstack.org//openstack-health/#/g/project/openstack~2Fhorizon?groupKey=project&resolutionKey=hour&end=2016-05-11T20:13:19.115Z20:14
david-lylebut for some reason the failures are not showing up for integration jobs20:14
tsufievhehe20:15
tsufievyou see, the job is fine :)20:15
david-lyleso that might be worth checking into20:15
clarkbkibana is a giant blobof js, I hear horizonay know how to workwith that >_>20:15
david-lyleit's all an illusion clarkb20:16
tsufievbeing a developer doesn't mean we all know how to fix an electric kettle :)20:16
clarkbkibana 3 is all client side and kibana 4 is node.js20:16
david-lylefrom bad to worse20:16
david-lyle:)20:16
itxakalool20:16
clarkbwe currently run 320:17
tsufievso the integration job fix just merged20:17
tsufievif you still encounter any failures in check job, just rebase your work onto latest master20:17
david-lyletsufiev: was it only failing in check?20:18
* tsufiev crosses fingers20:18
david-lylethat would explain health not showing failures20:18
hurgleburglerthanks tsufiev20:18
david-lylebut seems odd20:18
tsufievdavid-lyle, AFAIK, gate job always runs against latest master, but check is run for topic branches which may not be up to date20:18
tsufievno, failures were in both pipelines20:19
david-lyleok, that makes more sense20:19
david-lyleyour phrasing confused me20:19
david-lylebut I started in that direction ;)20:19
tsufievyeah, I fancy being cryptic sometimes :)20:19
david-lylesince we don't have a blueprint for this, as blueprints don't really track CP stuff20:20
david-lyleI have created a tempest plugin for horizon20:20
david-lyleit's merged and there is a new test job that runs on check which isn't voting20:20
tsufievbtw, I've noticed that there were some tempest failures as well20:20
tsufievcannot give a specific link though20:21
david-lyleI'm finalizing the job setup, once that's ready and passing, we can run that on gate as well20:21
david-lyleand remove our test from integrated tempest20:21
david-lylethen we can move forward with upper-constraints and new xstatic packages20:22
tsufievdavid-lyle, or the thing you're speaking about is not related to dsvm-tempest job?20:22
david-lyletsufiev: no20:22
tsufiev:o20:22
david-lylewell, gate-horizon-dsvm-tempest-plugin20:22
david-lylejob20:23
david-lyleis that what you're referring to?20:23
david-lylethe job isn't doing much yet, I have another patch up that I am testing out20:24
david-lylehttps://review.openstack.org/#/c/314795/20:24
david-lyleanyway, just a status report20:24
tsufievI think yes20:24
tsufievwell, never mind, if it wasn't voting yet, then I most likely confused it with something else20:25
tsufievas that thing was voting20:25
david-lyleok20:25
tsufievwhen you look into many failures, they start looking into you :/20:26
itxakaumm talking about failures and gate20:26
itxakadid someone saw michael's email referring to npm mirrors?20:26
itxakahttp://lists.openstack.org/pipermail/openstack-dev/2016-May/094719.html20:26
itxakaproject I guess?20:27
itxakaagh, cut phrase20:27
tsufievnow I did :)20:27
itxakawe are supposed to add the nam mirrors to the project I guess20:27
*** iyamahat has joined #openstack-meeting-320:27
david-lyleI tried it locally20:28
tsufievcould we just change npm job builders?20:28
itxakaahh, now I am reading it properly lmao20:29
itxakaits just to test it locally and report any errors, nothing to do with touching the project20:29
itxakasorry for the noise20:29
* itxaka retreats20:29
*** ivar-lazzaro has joined #openstack-meeting-320:30
david-lyleany other items?20:31
ducttape_so we get to ignore all test jobs, then?  great.  let's move forward  ;)20:31
*** ediardo has joined #openstack-meeting-320:32
tsufievwat :)?20:32
ducttape_just trolling / kidding20:32
* david-lyle thinks ducttape_ misread something20:32
TravTdavid-lyle what's the net result of all this?20:32
david-lyleTravT: this?20:33
TravT^^^20:33
TravTlast 15 mins20:33
david-lylestatus update20:33
ducttape_that there are a lot of test jobs failing / getting fixed.  it's getting better very soon20:33
david-lyleintegration tests should be working better20:33
david-lyleplans for xstatic upgrades moving forward20:34
* TravT will send thank you card to david-lyle20:34
*** ddieterly is now known as ddieterly[away]20:34
david-lylethere is an npm mirror that will reduce failures and fragility in npm dependent tests20:34
tsufievone more reason to come by the end of meeting :)20:35
*** galstrom is now known as galstrom_zzz20:35
david-lyleany other items?20:36
david-lyleany hasty decisions to make?20:37
david-lylegoing twice20:37
*** ddieterly[away] is now known as ddieterly20:37
* TravT sold20:37
david-lyleHave a banner week folks. Keep slinging that cloud.20:37
david-lyle#endmeeting20:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:37
openstackMeeting ended Wed May 11 20:37:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-05-11-20.00.html20:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-05-11-20.00.txt20:37
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-05-11-20.00.log.html20:37
bpokornyThanks, david-lyle.20:37
*** ducttape_ has left #openstack-meeting-320:37
*** tsufiev has left #openstack-meeting-320:38
*** TravT has left #openstack-meeting-320:38
*** absubram has quit IRC20:38
itxakao/20:40
*** itxaka has quit IRC20:40
*** kzaitsev_mb has joined #openstack-meeting-320:42
*** dimtruck is now known as zz_dimtruck20:42
*** pcaruana has quit IRC20:42
*** yohoffman has quit IRC20:45
*** dedery has joined #openstack-meeting-320:45
*** ashwin has joined #openstack-meeting-320:46
*** flintHP has joined #openstack-meeting-320:46
*** dedery_ has joined #openstack-meeting-320:47
*** flintHP has quit IRC20:47
*** ashwin has quit IRC20:47
*** dedery_ has quit IRC20:49
*** yamahata has joined #openstack-meeting-320:50
*** dedery has quit IRC20:51
*** mickeys has joined #openstack-meeting-320:53
*** mickeys has quit IRC20:54
*** mickeys has joined #openstack-meeting-320:54
*** robcresswell has joined #openstack-meeting-320:55
*** robcresswell has left #openstack-meeting-320:56
*** hurgleburgler has left #openstack-meeting-320:59
*** revon has joined #openstack-meeting-321:01
*** evgenyf has quit IRC21:02
*** lblanchard has quit IRC21:06
*** lpetrut has joined #openstack-meeting-321:08
*** rtheis has quit IRC21:09
*** tonytan4ever has quit IRC21:10
*** ekarlso has quit IRC21:11
*** ekarlso has joined #openstack-meeting-321:15
*** vhoward has quit IRC21:19
*** matrohon has quit IRC21:20
*** abalutoiu_ has quit IRC21:23
*** lpetrut has quit IRC21:28
*** mickeys has quit IRC21:28
*** mickeys has joined #openstack-meeting-321:29
*** zz_dimtruck is now known as dimtruck21:29
*** belmoreira has quit IRC21:30
*** baoli has quit IRC21:31
*** mickeys has quit IRC21:33
*** Sukhdev has quit IRC21:38
*** jmckind_ has joined #openstack-meeting-321:39
*** mickeys has joined #openstack-meeting-321:41
*** jmckind has quit IRC21:43
*** ddieterly is now known as ddieterly[away]21:45
*** kzaitsev_mb has quit IRC21:45
*** s3wong has joined #openstack-meeting-321:46
*** julim has quit IRC21:47
*** ddieterly[away] is now known as ddieterly21:48
*** mickeys has quit IRC21:48
*** kzaitsev_mb has joined #openstack-meeting-321:48
*** tyr_ has quit IRC21:49
*** mickeys has joined #openstack-meeting-321:49
*** claudiub has quit IRC21:50
*** Swami has quit IRC21:57
*** njohnston is now known as njohnston_afk22:00
*** njohnston_afk is now known as njohnston__22:00
*** jmckind_ has quit IRC22:02
*** ddieterly is now known as ddieterly[away]22:04
*** claudiub has joined #openstack-meeting-322:10
*** cloudtrainme has joined #openstack-meeting-322:10
*** dimtruck is now known as zz_dimtruck22:16
*** sigmavirus24 is now known as sigmavirus24_awa22:19
*** yamamoto has quit IRC22:28
*** yamamoto has joined #openstack-meeting-322:28
*** zz_dimtruck has quit IRC22:28
*** zz_dimtruck has joined #openstack-meeting-322:31
*** zz_dimtruck is now known as dimtruck22:31
*** ddieterly[away] is now known as ddieterly22:32
*** ddieterly has quit IRC22:36
*** egallen has joined #openstack-meeting-322:40
*** Swami has joined #openstack-meeting-322:41
*** mbound has joined #openstack-meeting-322:41
*** kzaitsev_mb has quit IRC23:00
*** chandanc has joined #openstack-meeting-323:01
*** rbak has quit IRC23:03
*** mickeys has quit IRC23:05
*** mickeys has joined #openstack-meeting-323:06
*** kmartin has joined #openstack-meeting-323:10
*** sdague has quit IRC23:12
*** sambetts|afk has quit IRC23:13
*** sreshetnyak has quit IRC23:14
*** zigo has quit IRC23:14
*** mikal has quit IRC23:15
*** Daviey has quit IRC23:15
*** mikal has joined #openstack-meeting-323:15
*** Daviey has joined #openstack-meeting-323:15
*** zigo has joined #openstack-meeting-323:15
*** sambetts has joined #openstack-meeting-323:15
*** peristeri has quit IRC23:27
*** salv-orl_ has quit IRC23:32
*** Sukhdev has joined #openstack-meeting-323:32
*** rhochmuth has quit IRC23:32
*** yamahata has quit IRC23:34
*** iyamahat has quit IRC23:37
*** revon has quit IRC23:39
*** yushiro has joined #openstack-meeting-323:40
*** yushiro has left #openstack-meeting-323:40
*** mdbooth has quit IRC23:44
*** ajo has quit IRC23:45
*** mdbooth has joined #openstack-meeting-323:45
*** ivar-laz_ has joined #openstack-meeting-323:48
*** ajo has joined #openstack-meeting-323:49
*** ivar-lazzaro has quit IRC23:52
*** njohnsto_ has joined #openstack-meeting-323:52
*** egallen has quit IRC23:55

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