Wednesday, 2016-11-30

*** Swami_ has quit IRC00:00
*** Patifa has quit IRC00:02
*** galstrom_zzz is now known as galstrom00:05
*** sambetts|afk has quit IRC00:08
*** sambetts_ has joined #openstack-meeting-300:09
*** spotz is now known as spotz_zzz00:13
*** kzaitsev_mb has joined #openstack-meeting-300:20
*** VW has joined #openstack-meeting-300:25
*** VW has quit IRC00:30
*** Swami has joined #openstack-meeting-300:32
*** lblanchard has joined #openstack-meeting-300:32
*** matjazp has quit IRC00:35
*** haleyb__ has joined #openstack-meeting-300:36
*** edleafe- has joined #openstack-meeting-300:36
*** edleafe has quit IRC00:36
*** numans has quit IRC00:37
*** haleyb__ has quit IRC00:41
*** dimtruck is now known as zz_dimtruck00:43
*** pvaneck has quit IRC00:53
*** hoangcx has joined #openstack-meeting-300:55
*** bpokorny has quit IRC00:59
*** mtanino has quit IRC00:59
*** reedip_ has joined #openstack-meeting-301:12
*** m1dev has quit IRC01:13
*** zhurong has joined #openstack-meeting-301:14
*** rajinir has quit IRC01:16
*** tovin07_ has quit IRC01:16
*** baoli has joined #openstack-meeting-301:18
*** baoli has quit IRC01:19
*** baoli has joined #openstack-meeting-301:19
*** Swami_ has joined #openstack-meeting-301:22
*** Swami has quit IRC01:22
*** galstrom is now known as galstrom_zzz01:24
*** spzala has quit IRC01:27
*** stanzgy has joined #openstack-meeting-301:32
*** haleyb__ has joined #openstack-meeting-301:37
*** bobmel has joined #openstack-meeting-301:38
*** Swami_ has quit IRC01:40
*** haleyb__ has quit IRC01:42
*** bobmel has quit IRC01:42
*** bpokorny has joined #openstack-meeting-301:51
*** bpokorny has quit IRC01:51
*** bpokorny has joined #openstack-meeting-301:52
*** ccamacho has quit IRC01:57
*** bpokorny has quit IRC01:58
*** bpokorny has joined #openstack-meeting-302:02
*** ccamacho has joined #openstack-meeting-302:02
*** huanxuan has joined #openstack-meeting-302:15
*** bpokorny_ has joined #openstack-meeting-302:15
*** tovin07 has joined #openstack-meeting-302:16
*** tovin07_ has joined #openstack-meeting-302:18
*** rbak has quit IRC02:18
*** bpokorny has quit IRC02:18
*** bpokorny_ has quit IRC02:20
*** lblanchard has quit IRC02:22
*** stevemar__ has joined #openstack-meeting-302:29
*** shu-mutou has joined #openstack-meeting-302:29
*** tuanluong has joined #openstack-meeting-302:31
*** haleyb__ has joined #openstack-meeting-302:38
*** baoli has quit IRC02:41
*** haleyb__ has quit IRC02:42
*** VW has joined #openstack-meeting-302:43
*** topol has quit IRC02:46
*** VW has quit IRC02:51
*** VW has joined #openstack-meeting-302:52
*** reedip_ has quit IRC02:52
*** zz_dimtruck is now known as dimtruck02:53
*** zhurong_ has joined #openstack-meeting-302:53
*** bobmel has joined #openstack-meeting-302:53
*** zhurong has quit IRC02:55
*** s3wong has quit IRC02:56
*** bobmel has quit IRC02:58
*** topol has joined #openstack-meeting-303:14
*** haleyb__ has joined #openstack-meeting-303:39
*** huanxuan has quit IRC03:42
*** huanxuan has joined #openstack-meeting-303:42
*** haleyb__ has quit IRC03:43
*** calbers has quit IRC03:44
*** bks has joined #openstack-meeting-303:52
*** calbers has joined #openstack-meeting-303:56
*** psachin has joined #openstack-meeting-304:01
*** numans has joined #openstack-meeting-304:06
*** Marcellin__ has quit IRC04:08
*** stevemar__ has quit IRC04:19
*** stevemar__ has joined #openstack-meeting-304:19
*** stevemar__ has quit IRC04:24
*** yamamoto_ has quit IRC04:24
*** prateek has joined #openstack-meeting-304:31
*** baoli has joined #openstack-meeting-304:32
*** hoangcx has quit IRC04:35
*** yamahata has quit IRC04:35
*** hoangcx has joined #openstack-meeting-304:35
*** dimtruck is now known as zz_dimtruck04:47
*** zz_dimtruck is now known as dimtruck04:47
*** prateek has quit IRC04:53
*** prateek has joined #openstack-meeting-304:54
*** bobmel has joined #openstack-meeting-304:54
*** bobmel has quit IRC04:59
*** dimtruck is now known as zz_dimtruck05:01
*** yamamoto_ has joined #openstack-meeting-305:08
*** VW has quit IRC05:15
*** soichi has joined #openstack-meeting-305:22
*** kazu has joined #openstack-meeting-305:28
*** vnyyad has joined #openstack-meeting-305:30
soichihi05:30
yamamoto_hi05:30
kazuhi05:30
vnyyadhi05:30
soichi#startmeeting taas05:30
openstackMeeting started Wed Nov 30 05:30:54 2016 UTC and is due to finish in 60 minutes.  The chair is soichi. 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
soichi#link https://wiki.openstack.org/wiki/Meetings/taas05:31
soichi#topic L2 Extension Migration for TaaS : Status = in progress  : Review =05:31
*** openstack changes topic to "L2 Extension Migration for TaaS : Status = in progress : Review = (Meeting topic: taas)"05:31
soichi#link https://review.openstack.org/40125805:31
*** anilvenkata has joined #openstack-meeting-305:33
soichiI'd like to skip this one because reedip is not available today05:34
reedipwooah wait wait05:34
reedipi am here05:34
soichireedip: h05:34
reedip:)05:34
soichi:)05:35
reedipsorry, was fixing a bug in OSC05:35
reedipyeah, the ML2 is still under progress... needs a lot of rework05:35
soichii see05:35
soichi#topic OSC Support for TaaS: Status = in progress: Review =05:35
*** openstack changes topic to "OSC Support for TaaS: Status = in progress: Review = (Meeting topic: taas)"05:35
reedipI am trying to understand the ml2 plugin of FWaaS , SFC and QoS to implement it properly05:35
soichi#link https://review.openstack.org/39876705:36
reedipOSC has almost been implemented. yamamoto_ wanted the bulk delete operation to be in place05:36
reedipso some test cases are still failing but I will put it up by today EOD05:36
reedipI also need to write the doc for OSC for TaaS, I will do that by today as well05:36
reedipWIP atleast for ^^05:37
yamamoto_i have a question.  how long do we want to keep the old cli support?05:38
yamamoto_reedip: do you know any policy about it?05:39
reedipyamamoto_ Umm, neutronclient support can be removed as we do not have an official release of TaaS yet05:39
reedipneutronclient will be deprecated05:40
reedipbut only at the CLI level05:40
reedipnot at the Library level05:40
yamamoto_sure. but we probably want to create newton branch05:40
reedipoh yeah05:40
yamamoto_is the osc stuff compatible with newton?05:40
reedipyamamoto_ : should be05:41
*** haleyb__ has joined #openstack-meeting-305:41
reedipbut as neutronclient's migration to OSC was not yet complete in newton, so I would like to avoid introducing OSC in newton05:41
soichi+105:41
yamamoto_ok, good to know05:43
soichi#topic Horizon Support for TaaS: Status = in progress: Review =05:44
*** openstack changes topic to "Horizon Support for TaaS: Status = in progress: Review = (Meeting topic: taas)"05:44
soichihttps://review.openstack.org/39602205:44
kazuyamamoto_: thank you for your comments, but i have a question.05:44
kazuwhat does your comment: "these "patches" horizon.networktopology.js etc?" means?05:44
yamamoto_actually i don't remember what i meant :-)05:46
*** haleyb__ has quit IRC05:46
reediphehehe :)05:46
yamamoto_i guess "does this modify the data structure defined there?" or something like that?05:46
yamamoto_just a dumb question from a js beginner. :-)05:47
kazui see. :)05:47
yamamoto_how many of us are familiar with horizon and js?05:47
soichii'm a beginner :)05:48
yamamoto_i guess it's better to ask someone more familiar with horizon review.  amotoki?05:48
soichikaz: what do you say to add Motoki san as a reviwer?05:49
reedipamotoki san can be conferred for this. Let us add him as a reviewer to ask for his opinion. But he seems to be unwell05:49
kazuok, i would like to add him as a reviewer.05:49
reedipso maybe we can add other horizon reviewers as well, or better send an email to Horizon team for their idea05:50
kazui see.05:50
soichi#topic Migration to neutron-lib05:51
*** openstack changes topic to "Migration to neutron-lib (Meeting topic: taas)"05:51
soichi#link https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service+branch:master+topic:bp/neutron-lib05:51
yamamoto_is it anything to discuss about the topic?  or it's just a heads-up?05:57
soichii guess latter05:58
soichi#topic do we want to create stable/newton branch?05:58
*** openstack changes topic to "do we want to create stable/newton branch? (Meeting topic: taas)"05:58
soichi#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107892.html05:59
yamamoto_i think at this point it's a good idea to create the branch.05:59
vnyyad+105:59
yamamoto_and maybe a release.05:59
soichi+105:59
kazu+105:59
yamamoto_i volunteer to work on it, except LP bits which i don't have permission.06:00
vnyyadLP is launchpad i ss06:02
vnyyadassume06:02
yamamoto_yes06:02
vnyyadi did add anil into itt06:02
*** revon has quit IRC06:02
vnyyadlet me see if i can add you as well to it...06:02
yamamoto_thank you06:03
soichi#topic Open Discussion06:04
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"06:04
vnyyadappologies for being absent for the last two meetings... the DST change means meeting starts at 6:30 here06:05
vnyyadwill discuss with anil and start action points on us06:05
vnyyadsoon06:05
*** gouthamr has joined #openstack-meeting-306:06
soichiokay, thank you06:06
yamamoto_i always feel lucky that i live in a country w/o dst.06:07
vnyyad:)06:07
kazu+106:07
soichiAre you planning to attend PTG at Atlanta on Feb. 2017 ?06:08
soichiIf we will have a TaaS meetup and discussions with neutron team, I and Kaz will try to attend.06:08
yamamoto_i plan to attend ptg06:08
soichiokay, thank you06:10
soichido you have any topics?06:10
yamamoto_#link http://www.openstack.org/ptg#tab_faq06:11
yamamoto_i guess " Q: We are a small team. We don’t do mid-cycles currently. Now we’ll have to travel to four events per year instead of two?"06:12
yamamoto_fits taas06:12
yamamoto_i have a few too old patches06:13
soichii agree06:13
vnyyadyes06:13
yamamoto_#link https://review.openstack.org/#/c/256210/06:13
yamamoto_#link https://review.openstack.org/#/c/301841/06:13
soichiyamamoto_: i already put +2 for 256210 and i will put +2 (again) for 30184106:15
yamamoto_thank you06:15
yamamoto_no hurry.  just a reminder.06:16
yamamoto_no more topic from me06:17
soichiokay, i'd like to close today's meeting.06:19
soichi#endmeeting06:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:19
openstackMeeting ended Wed Nov 30 06:19:51 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:19
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-11-30-05.30.html06:19
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-11-30-05.30.txt06:19
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-11-30-05.30.log.html06:19
yamamoto_bye06:19
kazubye06:19
vnyyadbye06:20
soichithank you, bye06:20
*** vnyyad has quit IRC06:20
*** soichi has left #openstack-meeting-306:20
*** kazu has quit IRC06:20
*** yamahata has joined #openstack-meeting-306:26
*** armax has quit IRC06:27
*** stevemar__ has joined #openstack-meeting-306:29
*** stevemar__ has quit IRC06:33
*** anilvenkata has quit IRC06:39
*** tuanluong has quit IRC06:42
*** haleyb__ has joined #openstack-meeting-306:42
*** psachin_ has joined #openstack-meeting-306:42
*** psachin has quit IRC06:45
*** haleyb__ has quit IRC06:47
*** kzaitsev_mb has quit IRC06:58
*** megm has quit IRC07:00
*** megm has joined #openstack-meeting-307:01
*** irenab has joined #openstack-meeting-307:20
*** andreas_s has joined #openstack-meeting-307:36
*** haleyb__ has joined #openstack-meeting-307:43
*** haleyb__ has quit IRC07:48
*** matjazp has joined #openstack-meeting-307:50
*** matrohon has joined #openstack-meeting-307:50
*** matjazp_ has joined #openstack-meeting-307:50
*** iyamahat has joined #openstack-meeting-307:52
*** matjazp has quit IRC07:54
*** MarkBaker has quit IRC08:01
*** iyamahat has quit IRC08:03
*** zhurong_ has quit IRC08:04
*** zhurong has joined #openstack-meeting-308:04
*** amotoki has joined #openstack-meeting-308:08
*** amotoki has quit IRC08:08
*** mickeys has quit IRC08:15
*** ralonsoh has joined #openstack-meeting-308:19
*** pgadiya has joined #openstack-meeting-308:19
*** stevemar__ has joined #openstack-meeting-308:30
*** makowals_ has joined #openstack-meeting-308:30
*** makowals_ has quit IRC08:31
*** makowals has quit IRC08:33
*** stevemar__ has quit IRC08:34
*** haleyb__ has joined #openstack-meeting-308:44
*** makowals has joined #openstack-meeting-308:44
*** numans has quit IRC08:47
*** haleyb__ has quit IRC08:49
*** bobmel has joined #openstack-meeting-308:56
*** rossella_s has joined #openstack-meeting-308:56
*** numans has joined #openstack-meeting-309:00
*** bobmel has quit IRC09:00
*** matjazp_ has quit IRC09:02
*** numans has quit IRC09:04
*** rossella_s has quit IRC09:05
*** paul-carlton2 has joined #openstack-meeting-309:06
*** yamahata has quit IRC09:09
*** lpetrut has joined #openstack-meeting-309:10
*** MarkBaker has joined #openstack-meeting-309:29
*** baoli_ has joined #openstack-meeting-309:31
*** baoli has quit IRC09:33
*** notmyname has quit IRC09:38
*** notmyname has joined #openstack-meeting-309:40
*** kzaitsev_mb has joined #openstack-meeting-309:43
*** lpetrut has quit IRC09:55
*** mickeys has joined #openstack-meeting-309:59
*** derekjhyang has joined #openstack-meeting-309:59
*** tovin07_ has quit IRC10:02
*** zhurong has quit IRC10:02
*** lpetrut has joined #openstack-meeting-310:03
*** mickeys has quit IRC10:03
*** baoli has joined #openstack-meeting-310:16
*** andreaf has quit IRC10:17
*** xhku_ has joined #openstack-meeting-310:17
*** andreaf has joined #openstack-meeting-310:18
*** xhku has quit IRC10:19
*** negronjl has quit IRC10:19
*** D9 has quit IRC10:19
*** anteaya has quit IRC10:19
*** notmyname has quit IRC10:19
*** baoli_ has quit IRC10:19
*** betherly has quit IRC10:19
*** zz_dimtruck has quit IRC10:19
*** natorious has quit IRC10:19
*** sambetts_ has quit IRC10:19
*** briancurtin has quit IRC10:19
*** Adri2000 has quit IRC10:19
*** DinaBelova has quit IRC10:19
*** JayF has quit IRC10:19
*** leifz has quit IRC10:19
*** darrenc has quit IRC10:19
*** jschwarz has quit IRC10:19
*** bswartz has quit IRC10:19
*** dhellmann has quit IRC10:19
*** lpetrut has quit IRC10:20
*** darrenc has joined #openstack-meeting-310:20
*** JayF has joined #openstack-meeting-310:20
*** DinaBelova has joined #openstack-meeting-310:21
*** dhellmann has joined #openstack-meeting-310:23
*** D9 has joined #openstack-meeting-310:24
*** briancurtin has joined #openstack-meeting-310:24
*** alanmeadows_ has joined #openstack-meeting-310:25
*** leifz has joined #openstack-meeting-310:25
*** natorious has joined #openstack-meeting-310:25
*** zz_dimtruck has joined #openstack-meeting-310:25
*** markmcclain has quit IRC10:25
*** alanmeadows has quit IRC10:25
*** vkmc has quit IRC10:25
*** Daviey has quit IRC10:25
*** spotz_zzz has quit IRC10:25
*** sgordon has quit IRC10:25
*** alex_xu has quit IRC10:25
*** makowals has quit IRC10:25
*** sambetts_ has joined #openstack-meeting-310:25
*** notmyname has joined #openstack-meeting-310:25
*** hoangcx has quit IRC10:25
*** zz_dimtruck is now known as dimtruck10:25
*** alanmeadows_ is now known as alanmeadows10:26
*** spotz_zzz has joined #openstack-meeting-310:26
*** makowals has joined #openstack-meeting-310:26
*** markmcclain has joined #openstack-meeting-310:26
*** sambetts_ is now known as sambetts10:26
*** sgordon has joined #openstack-meeting-310:26
*** jschwarz has joined #openstack-meeting-310:26
*** MarkBaker has quit IRC10:27
*** alex_xu has joined #openstack-meeting-310:27
*** vkmc has joined #openstack-meeting-310:27
*** Adri2000 has joined #openstack-meeting-310:28
*** negronjl has joined #openstack-meeting-310:29
*** anteaya has joined #openstack-meeting-310:31
*** pcaruana has joined #openstack-meeting-310:35
*** Daviey has joined #openstack-meeting-310:36
*** betherly has joined #openstack-meeting-310:36
*** betherly has quit IRC10:36
*** betherly has joined #openstack-meeting-310:36
*** psachin_ has quit IRC10:40
*** psachin has joined #openstack-meeting-310:40
*** haleyb__ has joined #openstack-meeting-310:46
*** psachin_ has joined #openstack-meeting-310:47
*** psachin has quit IRC10:48
*** haleyb__ has quit IRC10:51
*** lpetrut has joined #openstack-meeting-310:55
*** irenab has quit IRC10:58
*** mickeys has joined #openstack-meeting-311:00
*** lpetrut has quit IRC11:01
*** donghao has joined #openstack-meeting-311:01
*** mickeys has quit IRC11:06
*** rossella_s has joined #openstack-meeting-311:06
*** stanzgy has quit IRC11:08
*** bobmel has joined #openstack-meeting-311:15
*** shu-mutou has quit IRC11:18
*** bobmel has quit IRC11:20
*** bobmel has joined #openstack-meeting-311:20
*** sdague has joined #openstack-meeting-311:27
*** scsnow has quit IRC11:29
*** MarkBaker has joined #openstack-meeting-311:33
*** irenab has joined #openstack-meeting-311:35
*** donghao has quit IRC11:38
*** psachin_ has quit IRC11:39
*** scsnow has joined #openstack-meeting-311:42
*** bobmel has quit IRC11:42
*** bobmel has joined #openstack-meeting-311:43
*** psachin has joined #openstack-meeting-311:43
*** haleyb__ has joined #openstack-meeting-311:47
*** bks has quit IRC11:47
*** rtheis has joined #openstack-meeting-311:49
*** haleyb__ has quit IRC11:52
*** sankarshan_away is now known as sankarshan11:58
*** mickeys has joined #openstack-meeting-312:02
*** mickeys has quit IRC12:06
*** jtomasek has joined #openstack-meeting-312:07
*** tellesnobrega has quit IRC12:09
*** tellesnobrega has joined #openstack-meeting-312:12
*** jtomasek has quit IRC12:19
*** baoli_ has joined #openstack-meeting-312:20
*** baoli has quit IRC12:22
*** prateek has quit IRC12:28
*** alexismonville has quit IRC12:29
*** makowals_ has joined #openstack-meeting-312:31
*** makowals has quit IRC12:34
*** jtomasek has joined #openstack-meeting-312:35
*** jrist has joined #openstack-meeting-312:37
*** makowals has joined #openstack-meeting-312:43
*** makowals_ has quit IRC12:45
*** haleyb__ has joined #openstack-meeting-312:48
*** srobert has joined #openstack-meeting-312:48
*** srobert has quit IRC12:49
*** srobert has joined #openstack-meeting-312:49
*** haleyb__ has quit IRC12:53
*** sankarshan is now known as sankarshan_away12:53
*** ociuhandu has quit IRC12:55
*** matjazp has joined #openstack-meeting-312:55
*** claudiub|2 has joined #openstack-meeting-312:56
*** yamamoto_ has quit IRC12:59
*** ociuhandu has joined #openstack-meeting-313:00
*** matjazp has quit IRC13:00
*** sagar_nikam has joined #openstack-meeting-313:00
sagar_nikamHi13:01
claudiub|2hello13:01
*** claudiub|2 is now known as claudiub13:01
claudiub#startmeeting hyper-v13:01
openstackMeeting started Wed Nov 30 13:01:25 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
claudiubhello13:01
claudiubanyone else joining us?13:01
sagar_nikamno... we can start13:01
claudiubcool.13:02
claudiub#topic OVS13:02
*** openstack changes topic to "OVS (Meeting topic: hyper-v)"13:02
*** mickeys has joined #openstack-meeting-313:03
claudiubso, first things first13:03
claudiub#link OVS 2.6 announcement: https://twitter.com/cloudbaseit/status/80357509200534732813:03
claudiubOVS 2.6 has been released13:03
claudiubjust fyi13:03
sagar_nikamchecking13:04
claudiubin case you want to try it out :)13:04
*** matjazp has joined #openstack-meeting-313:04
*** bobmel has quit IRC13:04
sagar_nikamyes.. sure... need to discuss with kvinod and somu13:04
sagar_nikamsonu13:04
claudiubit should improve network throughput13:05
*** bobmel has joined #openstack-meeting-313:05
claudiubso, it's worth checking out13:05
sagar_nikamok13:05
claudiubsecondly, I've been working on the nova hyper-v + ovs ci13:05
claudiuball of the configs are in place, the setup is fine13:06
claudiubthere are a few things i'm testing out at the moment13:06
sagar_nikamwill OVS2.6 work with mitaka ?13:06
claudiubi've noticed that neutron-ovs-agent freezes after ~10 hours or so13:07
*** ociuhandu has quit IRC13:07
claudiuband I'll have to see why and how to address this13:07
*** alexismonville has joined #openstack-meeting-313:07
claudiubsagar_nikam: yep. it is independent from openstack releases13:07
*** mickeys has quit IRC13:07
sagar_nikamok13:07
claudiubsagar_nikam: did you try neutron-ovs-agent?13:07
claudiubdid you have any issues like this?13:07
sagar_nikamfreezing after 10 hours ... at what scale ? high number of VMs and networks causes it ?13:08
claudiubnot sure yet13:08
claudiubit's not an easy case to reproduce13:08
claudiubit is not deterministic13:08
sagar_nikami think sonu's team was planning it since we wanted VxLAN support. I will mail them about the new release13:09
*** MarkBaker has quit IRC13:09
claudiubbut, from what i can see, the neutron-ovs-agent still sends its heartbeat and it processes rpc calls, but the main thread is frozen13:09
claudiubmeaning that it won't bind ports anymore13:09
sagar_nikamOK13:10
claudiubso yeah. that's what i'm currently working on.13:11
claudiubany questions?13:11
*** jtomasek has quit IRC13:12
sagar_nikamno... i have mailed the networking team about it13:12
sagar_nikamwill check with them tomorrow13:12
*** bobmel has quit IRC13:12
claudiubcool13:13
claudiub#topic open discussion13:13
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:13
*** bobmel has joined #openstack-meeting-313:13
claudiubso, no new updates on any nova patches13:13
sagar_nikamok13:13
sagar_nikamhave you considered supporting scvmm ?13:14
claudiubwe're currently trying out the windows server 2016 networking, and planning to integrate it in networking-hyperv13:14
sagar_nikamok13:14
claudiubit will be able to support vxlan network types13:14
claudiubsagar_nikam: we don't see any benefits from supporting scvmm. it's basically hyper-v + clustering13:15
sagar_nikamok13:15
claudiubwhich we already have in openstack13:15
sagar_nikamyou mean using the cluster driver ?13:15
claudiubyep13:16
sagar_nikamok13:16
claudiubsagar_nikam: anyways. I still haven't received any email from sonu13:16
sagar_nikamthe reason i asked... scvmm instances can be bursted to azure13:16
sagar_nikamwas thinking if coudbase has thought of this usecase13:17
sagar_nikam*cloudbase13:17
*** gouthamr has quit IRC13:17
claudiubsagar_nikam: not particularly familiar with hybrid cloud solutions, but from my point of view, it can be a tricky subject, as you don't have a lot of control on what vms are bursted to azure13:20
claudiubas it has its own internal ha13:20
sagar_nikamok13:20
sagar_nikami was thinking of user triggered busting... not automated13:20
claudiuband it could break some affinity rules that nova has been configured with13:20
sagar_nikamthe user provisions a VM using Openstack+SCVMM13:21
sagar_nikamand then if required.. using some other component... burst to azure13:21
sagar_nikami mean some other python component13:21
claudiubyou mean like coriolis?13:21
sagar_nikamoutside of openstack13:21
sagar_nikamyes.. possible13:21
sagar_nikamany idea if pyMI supports SCVMM ... or should i say can MI be used for SCVMM ?13:22
claudiubwell, in this case, i think coriolis might work better, as it also handles the tooling / bootstraping the instances when migration to a public / private cloud, or to a particular hypervisor13:23
sagar_nikamcoriolis.. supports SCVMM to azure ?13:24
claudiubsagar_nikam: theoretically, yes, as long as there is a WMI interface for SCVMM objects and so on, like almost anything else on Windows, including Hyper-V objects, Cluster objects, system objects, etc.13:24
claudiubyou can even manipulate excel tables through WMI objects13:25
sagar_nikamok13:25
*** pgadiya has quit IRC13:25
claudiubsagar_nikam: scvmm is basically hyper-v, and hyper-v instances can be migrated to azure13:26
sagar_nikamok13:26
sagar_nikami was thinking... how do we create VMs in SCVMM programatically .. hopefully it is possible using MI13:27
sagar_nikamand hence pyMI13:27
sagar_nikamyour opinion ?13:27
claudiubas a rule of thumb, if there's a powershell cmdlet for it, it can be done programatically13:28
claudiuband most probably with pymi as well.13:28
sagar_nikamyes ... but using python and trigger powershell cmdlet to create VMs may be the best solution13:29
sagar_nikamanyhow.... will read more13:29
sagar_nikamthanks for this info13:29
claudiubno problem. but still, from my point of view, there aren't any advantages to adding support for scvmm in openstack. :)13:30
sagar_nikamok13:30
sagar_nikamagree13:30
*** rossella_s has quit IRC13:31
claudiubany updates from your side?13:31
*** rossella_s has joined #openstack-meeting-313:31
sagar_nikamnot as of now.. we are slowing trying to move to Mitaka13:32
sagar_nikamwork is starting this week13:32
sagar_nikambut it may take time as we have some issues in getting mitaka in our downstream branch13:32
sagar_nikamas of now mostly planning stage13:33
claudiubare you doing some changes to the upsteam branches?13:33
sagar_nikamwe had done a POC to check with Mitaka few months back13:33
sagar_nikamand it had worked13:33
sagar_nikambut that was just a POC... manually checking out mitaka13:33
sagar_nikamno changes to upstream branch... atleast on nova.. it is quite stable13:34
claudiubwhy not run some tempest tests, in order to make sure it all works fine?13:34
sagar_nikamwe have not found any issues in nova... so no changes to be submitted upstream13:34
claudiubyeah, mitaka is currently in phase 2 support, which means that only high / critical importance bugfixes are backported13:35
sagar_nikamyes... we will run temptes13:35
sagar_nikambut first we need to get mitaka in our downstream bacnh13:35
sagar_nikambranch13:35
sagar_nikamsome work to be done by ops team13:35
sagar_nikamwe have requested... it will be done... but no time frame yet13:36
claudiubok :)13:36
*** MarkBaker has joined #openstack-meeting-313:36
sagar_nikamwhat we are starting is manually cloning nova and start tetsing13:36
sagar_nikambut that is more from developer perspective13:36
sagar_nikamnot much for the product itself13:36
sagar_nikamso no scale tests...13:37
sagar_nikamwhich will only happen when we get the downstream repo sorted out13:37
*** stevemar__ has joined #openstack-meeting-313:37
sagar_nikamwe will also need os-win in our downstream repo13:37
sagar_nikamsome process trying to get it13:37
sagar_nikammight take time13:37
claudiubwell, it should work out of the box13:38
sagar_nikamcorrect.. that is what i am thinking13:38
claudiubwe haven't done any backwards-incompatible to os-win, as far as I know13:38
sagar_nikamhence just my developer testing should be good enough13:38
claudiubplus, os-win has a mitaka branch as well13:38
sagar_nikamis what i feel13:38
sagar_nikamwe will use os-win in mitaka13:39
sagar_nikambranch13:39
*** lblanchard has joined #openstack-meeting-313:39
sagar_nikamso we should be fine13:39
claudiubcool. well, i hope it goes as smoothly as possible. :)13:39
sagar_nikamyes ... even i hope so13:39
sagar_nikamit is mostly the process which take time13:40
sagar_nikamcode wise i think we will be fine13:40
sagar_nikami have asked my team mate who will be working on hyperv to also try the cluster driver13:40
sagar_nikamwhen we tried it few months back13:40
sagar_nikamit all worked perfectly13:40
sagar_nikammanually cloning mitaka13:41
*** matjazp has quit IRC13:41
sagar_nikamand applied your patch13:41
sagar_nikami think the same will work now as well13:41
claudiubi think we merged the cluster driver in compute-hyperv in mitaka13:41
claudiubif i remember correctly13:41
sagar_nikamok13:41
claudiubanyways, one more thing. i propose we don't have a hyper-v meeting next week, and have it next-next week instead. the thing is that I probably won't have many updates next week, as today and tomorrow are public holidays in romania, which means that we won't do a lot in these days. :)13:43
claudiubif there's something, you can email me13:43
claudiubis that ok with you?13:43
sagar_nikamsure no problem13:43
sagar_nikamsame from my end as well13:43
claudiubcool :)13:44
sagar_nikamwe will be busy trying to get unto mitaka13:44
sagar_nikamand it will take some time13:44
sagar_nikamso not a issue13:44
sagar_nikami dont expect to hit too many issues13:44
sagar_nikamwe can do it 2 weeks from now13:44
claudiubgreat, thanks. :)13:44
claudiubwell then, that's it from me13:44
sagar_nikamthanks13:45
sagar_nikamwe can close the meeting13:45
claudiubthanks for joining, see you in 2 weeks!13:45
claudiub#endmeeting13:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:45
openstackMeeting ended Wed Nov 30 13:45:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-11-30-13.01.html13:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-11-30-13.01.txt13:45
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-11-30-13.01.log.html13:45
*** yamamoto has joined #openstack-meeting-313:45
*** slaweq has joined #openstack-meeting-313:46
*** jtomasek has joined #openstack-meeting-313:47
*** baoli has joined #openstack-meeting-313:48
*** haleyb__ has joined #openstack-meeting-313:49
*** baoli_ has quit IRC13:50
*** julim has joined #openstack-meeting-313:53
*** haleyb__ has quit IRC13:54
*** baoli_ has joined #openstack-meeting-313:54
*** julim has quit IRC13:54
*** baoli has quit IRC13:56
*** hichihara has joined #openstack-meeting-314:00
*** numans has joined #openstack-meeting-314:00
slaweq#startmeeting neutron_qos14:00
openstackMeeting started Wed Nov 30 14:00:58 2016 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
slaweqhello14:01
ralonsohHi14:01
*** julim has joined #openstack-meeting-314:01
slaweqI hope there will be more people in few minutes :)14:01
ralonsohno problem14:02
ralonsohBTW, the etherpad is https://etherpad.openstack.org/p/neutron_qos_meeting_chair?14:02
slaweqno, I was preparing it today's agenda on https://etherpad.openstack.org/p/qos-meeting14:03
*** sagar_nikam has quit IRC14:03
ralonsohok14:03
ralonsohone sec14:03
*** huanxuan has quit IRC14:03
*** mickeys has joined #openstack-meeting-314:03
slaweqok14:04
ralonsohI updated the etherpad for today14:04
slaweqthx14:04
ralonsohbut, if there is no qorum, it's useless14:04
slaweqyep :/14:04
slaweqbtw ralonsoh: can You review https://review.openstack.org/#/c/401458/ if You will have a while?14:05
*** davidsha has joined #openstack-meeting-314:05
ralonsohI'll review this today14:05
slaweqthx14:05
slaweqdavidsha, njohnston, reedip: are You there?14:06
davidshahi, just joined14:06
slaweqhello14:06
davidshaThis is the LB-dscp is it?14:07
ralonsohyes14:07
slaweqdavidsha: yes14:07
slaweqplease review if You will have time - You are dscp master :)14:07
*** tongli has joined #openstack-meeting-314:07
*** mickeys has quit IRC14:07
davidshaack,  I have very little knowledge of LB but I'll try to review it.14:08
slaweqok, so maybe we will start and do it quick, what You think?14:08
ralonsohperfect14:08
slaweq#topic RFEs-approved14:08
*** openstack changes topic to "RFEs-approved (Meeting topic: neutron_qos)"14:08
slaweqthere is no too many rfe-approved for QoS14:08
slaweq#link https://bugs.launchpad.net/neutron/+bug/157898914:08
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:08
slaweqralonsoh: how it's going?14:09
ralonsohThe first part, which is the BW manager, goes fine14:09
ralonsohone sec14:09
ralonsohBW manager, OVS: https://review.openstack.org/#/c/404343/14:09
ralonsohBW manager, LB: https://review.openstack.org/#/c/402121/14:09
ralonsohBW manager, SR-IOV: https://review.openstack.org/#/c/401254/14:09
ralonsohBW manager, config options: https://review.openstack.org/#/c/404647/14:09
ralonsohto review...14:09
ralonsohThe frist three I want to someone to see the architecture14:10
ralonsohThat's all14:10
davidshakk, I added myself to the reviews14:10
ralonsohThanks!14:11
slaweq#action slawek review ralonsoh patches with BW manager14:11
hichihararalonsoh: I'll review it14:11
slaweqok, I will also have a look on it14:11
ralonsohhichihara: thanks!14:11
ralonsohnext RFE, I think14:11
*** rhochmuth has joined #openstack-meeting-314:11
slaweqother rfe-approved bugs are same as last time (extended validation and instance ingress) and nothing changes there on my side14:12
slaweqmaybe ajo will have something to update on his patch https://review.openstack.org/#/c/351858/14:12
slaweqbut as I checked it today, there was no too many changes there14:12
slaweqso14:12
slaweq#topic RFEs14:12
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"14:12
*** alexismonville has quit IRC14:12
slaweq#link https://bugs.launchpad.net/neutron/+bug/164436914:13
openstackLaunchpad bug 1644369 in neutron "Support for DSCP marking in Linuxbridge L2 agent" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:13
slaweqI made it last week, patch is ready for review (IMHO) so please take a look on it14:13
ralonsohSur14:13
ralonsohSure14:13
slaweqI made it with iptables rule to mark packets with dscp14:13
slaweqany questions to this one?14:13
*** ianychoi has quit IRC14:14
slaweqok, so maybe next one14:14
slaweq#link https://bugs.launchpad.net/neutron/+bug/163479814:14
openstackLaunchpad bug 1634798 in neutron "[RFE] Qos DSCP to vlan priority mapping" [Wishlist,Confirmed]14:14
slaweqthis one is new IMO and is not assigned yet14:15
ralonsohI need to take a look to this one14:15
ralonsohI'll try to reply in launchpad14:15
slaweqok, thx ralonsoh14:15
davidshaslaweq: There was a Vlan pcp rfe a while back but it went obsolete, would that be needed before this?14:16
*** MarkBaker has quit IRC14:16
slaweqdavidsha: I don't know14:16
slaweqit's something to check14:16
slaweqdavidsha: do You have link to it?14:17
*** MarkBaker has joined #openstack-meeting-314:17
ralonsohdavidsha is right14:17
ralonsoh#link https://review.openstack.org/#/c/392023/14:17
davidshavikram said he was going to wait for dscp to merge before he started work on it I think, give me one sec and I'll find it14:17
davidshaOh, it's the bug linked in that spec: https://bugs.launchpad.net/neutron/+bug/150563114:18
openstackLaunchpad bug 1505631 in neutron "[RFE] QoS VLAN 802.1p Support" [Wishlist,Confirmed] - Assigned to Kannan Raman (kannanrc20)14:18
*** rhochmuth has quit IRC14:18
*** stevejims has joined #openstack-meeting-314:18
davidshathanks ralonsoh!14:19
slaweqbut this one is postponed currently14:19
ralonsohThe spec is now approved14:19
ralonsohNo14:20
*** bswartz has joined #openstack-meeting-314:20
ralonsohnot yet14:20
slaweqyes, but in https://bugs.launchpad.net/neutron/+bug/1634798 ajo asked what author means there so maybe we should wait for answear there?14:21
openstackLaunchpad bug 1634798 in neutron "[RFE] Qos DSCP to vlan priority mapping" [Wishlist,Confirmed]14:21
ralonsohYes, we should wait for the previous one14:21
slaweqok, so going forward14:21
slaweq#link https://bugs.launchpad.net/neutron/+bug/150562714:21
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Incomplete] - Assigned to Reedip (reedip-banerjee)14:21
slaweqthis one is quite old14:21
slaweqso I don't think we should talk about it again now14:22
slaweqwhat You think?14:22
ralonsohvikram or reedip should ask this question14:22
slaweqbut it seems that they are not here14:23
ralonsohnext time then14:23
slaweqok14:23
slaweq#topic Bugs14:23
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:23
slaweq#link https://bugs.launchpad.net/neutron/+bug/164075714:24
openstackLaunchpad bug 1640757 in neutron "Parameter validation for string type parameters" [Undecided,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:24
slaweqI was checking it14:24
slaweqand I described everything in comments14:24
slaweqIMHO there is no bug there but maybe You have something to add14:24
ralonsohI agree with your comments14:24
ralonsohThis could be also a problem in other objects14:25
ralonsohBut it's not14:25
slaweqso should we close this bug?14:25
ralonsohI think so14:25
*** tonytan4ever has joined #openstack-meeting-314:25
slaweqok, I will close it14:25
slaweq#action slaweq close https://bugs.launchpad.net/neutron/+bug/164075714:25
openstackLaunchpad bug 1640757 in neutron "Parameter validation for string type parameters" [Undecided,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:25
slaweqhttps://bugs.launchpad.net/neutron/+bug/164076214:26
openstackLaunchpad bug 1640762 in neutron "when I update a Qos policy, value of shared can not be changed to false from true" [Undecided,Incomplete] - Assigned to Slawek Kaplonski (slaweq)14:26
slaweqI also checked it and IMHO there is also no issue there14:26
slaweqthere is flag to set shared/not shared qos policy14:26
ralonsohWith OSC?14:26
ralonsohI need to check that14:26
slaweqyep, I checked in OSC14:26
ralonsohI did this patch14:27
slaweqin neutron client I added such flag even14:27
slaweqin OSC it is also but name is littlebit different14:27
slaweqI pasted there my test with OSC14:27
ralonsohI see14:27
ralonsohI'll ask in the bug:14:28
slaweqok14:28
ralonsohwhich version of OSC14:28
ralonsohand how to reproduce it14:28
slaweqhttps://bugs.launchpad.net/neutron/+bug/161654714:28
openstackLaunchpad bug 1616547 in neutron "qos: rule api definition shouldn't include tenant_id" [Low,Incomplete]14:28
slaweqabout this one I have note that ralonsoh wanted to check it last time14:29
slaweqdo You have any info about it?14:29
ralonsohrule doesn't include tenant_id14:29
davidshawas this not changed from tenant_id to project_id?14:29
*** srobert has quit IRC14:30
ralonsohOk14:30
ralonsohYes, it has14:30
ralonsohAnd it was changed to project_id14:30
slaweqI'm not sure but I think that there was something like that reported some time ago and it was not provided "accidentally"14:31
ralonsoh"rule" is a neutronobject14:31
ralonsohso it has project_id14:31
ralonsohShould be in the api definition14:32
slaweqso ralonsoh can You update it in this bug report?14:32
ralonsohok14:32
slaweqthx14:32
slaweqnext https://bugs.launchpad.net/neutron/+bug/161641114:32
openstackLaunchpad bug 1616411 in neutron "the result is not expected from the command "neutron qos-policy-show policy -F id"" [Undecided,New] - Assigned to QunyingRan (ran-qunying)14:32
slaweqI don't know if author of this one is here14:33
davidshadoesn't seem like it, not on #openstack-neutron either14:34
slaweqdo You have anything to add for this one?14:34
hichiharaIt looks like a bug of neutronclient14:34
slaweqyep14:34
slaweqthere is also one more for neutronclient: #link https://bugs.launchpad.net/neutron/+bug/164384914:35
openstackLaunchpad bug 1643849 in python-neutronclient "The result of 'qos-minimum-bandwidth-rule-list' is wrong" [High,In progress] - Assigned to QunyingRan (ran-qunying)14:35
slaweqanything to add here?14:36
*** kashyap has left #openstack-meeting-314:36
ralonsohIt's under review: https://review.openstack.org/#/c/401824/14:36
ralonsohI'll take a look at this14:36
slaweqok14:36
* ajo appears ':)14:37
slaweqshouldn't we check also OSC if it is valid for it also?14:37
slaweqhello ajo :)14:37
ralonsohOSC patch is still under review.... for 3 months14:37
ralonsohOSC is still not ready for this14:38
slaweqok, so OSC is not impacted by this bug :)14:38
ralonsohno14:38
slaweqnext one #link https://bugs.launchpad.net/neutron/+bug/164409714:38
openstackLaunchpad bug 1644097 in neutron "qos tempest tests should not try to use unsupported rule types" [Low,Triaged]14:38
slaweqI can look on this one later14:38
ajooh, that makes sense, right. Otherwise plugins not suporting DSCP will go red.14:39
slaweqbut in tempest there are only tests for LB and OVS agents, right?14:40
slaweqor SR-IOV also?14:40
*** irenab has quit IRC14:40
slaweqand what is tested in tempest in fact? are there tests which really check if packets are marked with DSCP?14:40
ajohmmm14:41
ajotempest should be plugin agnosti14:41
ajoagnostic14:41
ajoit's just a a tool to validate your cloud14:41
ajo(afaik)14:41
hichiharaRight14:41
*** VW has joined #openstack-meeting-314:41
slaweqyes, but if tests are only checking if rule is applied on api level then it will not be red for any plugin/agent14:41
slaweqat least as long as we don't do "improved validation" :)14:42
ajohmm14:42
ajofor bandwidth I think there were some tests that checked bandwidth14:42
slaweqbut I agree that it should be fixed14:42
ajonot sure for dscp14:42
ajoor may be it's because midonet's plugin does not allow creation of rules it doesn't support14:43
slaweqI made such test for dscp in fullstack tests but I don't know about tempest14:43
slaweqI will check it14:43
ajoin a multi-backend enviroment14:43
ajoall plugins would have to allow creation of any policy14:43
*** mtanino has joined #openstack-meeting-314:43
ajoand then... (when we have the rule validation) fail if you try to use a rule your backend doesn't support14:43
*** qwebirc15108 has joined #openstack-meeting-314:44
slaweqok14:44
ajoI talked about that with yamamoto the other day14:44
ajomay be it just has to wait until we finish rule validation, and that's it14:44
slaweqYou mean this change in tempest?14:45
ajoyes,14:45
ajoor we can do as yamamoto requested14:46
ajoand not try rules not reported as available14:46
*** Swami has joined #openstack-meeting-314:46
slaweqI will check how it looks in tests code14:46
slaweqand if I will find something I will describe in comments in this bug14:46
ajoack, thanks slaweq  :=14:46
ajo:)14:46
slaweq#link https://bugs.launchpad.net/neutron/+bug/150765614:47
openstackLaunchpad bug 1507656 in neutron "RPC callbacks push/pull mechanism should be remotable" [Wishlist,Opinion] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)14:47
slaweqI found also this one tagged as qos14:47
slaweqbut I don't know if it is valid for now?14:47
ajowe don't need to look at opinion bugs14:48
slaweqok14:48
ajoopinion means = we won't fix it, it's an oppinion of the reporter14:48
slaweqsorry, I didn't know14:48
slaweqstill learning14:48
ajoor something like that14:48
ajo:D14:48
ajoso we can skip it :D14:48
ajonp, it's confusing :D14:48
ajothanks for helping with this btw :D14:48
slaweq#link https://bugs.launchpad.net/neutron/+bug/163918614:49
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo)14:49
slaweqajo: do You know how it's going?14:49
ltomasbohi14:49
slaweqhello ltomasbo14:49
ajoltomasbo can explain it better :D14:50
ltomasboI just tried a simple patch to connect trunk port with br-int with veth devices14:50
*** spzala has joined #openstack-meeting-314:50
ltomasboso that QoS bw can be used14:50
*** haleyb__ has joined #openstack-meeting-314:50
ltomasboand make it configurable (so that you can choose if those ovs bridges are to be link thorugh patch or veth links14:51
*** krtaylor has joined #openstack-meeting-314:51
ltomasbohowever, that is not a good solution to merge upstream14:51
ltomasboand seems the prefered solution is to be able to apply the bw throttling at ovs patch ports14:51
*** VW has quit IRC14:51
*** VW has joined #openstack-meeting-314:51
ltomasbobut it will be nice to hear more opinions14:52
ltomasboand other possible solutions14:52
qwebirc15108good14:52
ralonsohbut it's not possible to set egress qos rules in OVS14:52
*** reedip_ has joined #openstack-meeting-314:52
ltomasboalthough I agree with armax and think it should be done at OVS first14:52
ralonsoh(ingress for OVS)14:52
ajoyes,14:53
ajoif we want something that works for dpdk14:53
ajoand does not introduce more overhead14:53
hichihara+1 > OVS first14:53
ajowe may need this kind of feature in OVS14:53
ajo(via metering, etc..)14:53
ajoI'm not sure how interested they'd be in that, metering packets adds overhead14:53
ajobut may be it's not that much14:53
ltomasboralonsoh: ingress for OVS works right now, right?14:54
*** hosanai has joined #openstack-meeting-314:54
slaweqwill qos works fine on ovs with patch-ports? I'm asking because AFAIR for example for internal ports it was not working properly14:54
ralonsohonly for interfaces, not for ports14:54
ltomasbothe problem here is that instead of having a tap device connected to the br-int, for trunk ports you have a patch port that connects to another ovs-brdige, which connects to the VM14:55
*** haleyb__ has quit IRC14:55
davidsharalonsoh: is it not the other way around?14:55
*** danpawlik has joined #openstack-meeting-314:56
ralonsohdavidsha: what do you mean? I don't understand14:56
ralonsohwe can talk about this by mail14:56
hichiharaIs it possible if use veth?14:56
ralonsohit is14:56
ltomasboyep, I tried that and it works14:56
ralonsohbut hurting a lot the performance14:56
ajoit works if the port has a linux kernel interface14:56
ajoa tap port, a veth, etc14:56
ajobut not a patch port14:56
ajocorrect14:56
hichihararalonsoh: yes14:56
ajothat's why what ltomasbo tested works, but it's not desired14:56
davidsharalonsoh: qos tables are added on the port not interface. I think I may have misunderstood though.14:57
* ajo wants https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.3.0.pdf. Section 5.7 :)14:57
ralonsohdavidsha: yes, on the port. But qos max bw in Neutron is setting the interface policing14:57
*** koji has joined #openstack-meeting-314:58
davidsharalonsoh: yes, sorry!14:58
ajoright,14:58
hichiharaExcuse me, I have one item before meeting end.14:58
*** srobert has joined #openstack-meeting-314:58
slaweqok, give it hichihara :)14:59
hichiharaI work on https://review.openstack.org/#/c/318531/14:59
hichiharaBut the implementaion about tunneling(VXLAN) is a bit complicated.14:59
hichiharaI think that it'll be independent of VLAN.14:59
*** betherly has quit IRC14:59
hichiharaSo I'll divide the patch into two patches(VLAN and Tunneling).14:59
*** rhochmuth has joined #openstack-meeting-314:59
*** prateek has joined #openstack-meeting-314:59
hichiharaMaybe I'll update VLAN patch early next week.14:59
*** yingjun has joined #openstack-meeting-314:59
ralonsoh?14:59
hichiharaThat's all :)14:59
*** Rockyg has joined #openstack-meeting-314:59
ralonsohok....14:59
*** bklei has joined #openstack-meeting-315:00
hichihararalonsoh: Please check15:00
slaweqok, I think we are out of time now15:00
slaweq#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Nov 30 15:00:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-11-30-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-11-30-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-11-30-14.00.log.html15:00
*** yamamoto has quit IRC15:00
davidshaThanks, cya!15:00
hichiharathanks15:00
ajowell, dividing is not that bad, easier to review15:00
slaweqthx15:00
ajobut it's generally a lot of work15:00
ajothanks everybody15:00
ajothanks slaweq15:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Nov 30 15:00:56 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:01
rhochmutho/15:01
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
bkleio/15:01
kojio/15:01
rhochmuthAgenda for Wednesday November 30, 2016 (15:00 UTC)15:01
rhochmuth1.Leftovers from last meeting15:01
rhochmuth1.Agent requirement out-of-sync issue15:01
rhochmuth1.https://review.openstack.org/#/c/397018/15:01
rhochmuth2.https://review.openstack.org/#/c/315792/15:01
rhochmuth2.Use oslo.db for sqla driver (yingjun)15:01
rhochmuth1.https://review.openstack.org/#/c/395897/15:01
rhochmuth3.https://storyboard.openstack.org/ - should we use that ?15:01
qwebirc15108o/15:01
rhochmuth4.InfluxDB 0.11 and beyond15:01
rhochmuth2.Removing pure mysql code ? Is it needed or is it a dead-code ?15:01
hosanaio/15:01
*** rarcea_ has joined #openstack-meeting-315:01
rhochmuthhi everyone15:01
shinya_kwbto/15:01
bkleihello15:02
rhochmuthi'm in germany at the open source monitoring conference OSMC 201615:02
rhochmuthgiving a talk tomorrow on monasca15:02
bkleinice15:02
rhochmuthbut, i'm here for 30-45 minutes15:02
rhochmuthlooks like a descent agenda15:02
rhochmuthwe should get started15:02
rhochmuth#topic Agent requirement out-of-sync issue15:03
*** openstack changes topic to "Agent requirement out-of-sync issue (Meeting topic: monasca)"15:03
rhochmuth1.https://review.openstack.org/#/c/397018/15:03
rhochmuth2.https://review.openstack.org/#/c/315792/15:03
*** mickeys has joined #openstack-meeting-315:04
rhochmuthlooks like tomasz is not here today15:04
rhochmuthand i'm guessing he added this to the agenda15:04
rhochmuthdoes anyone else know what is going on15:05
rhochmuthnormally, i wait for the openstack bot to handle this sort of stuff15:05
*** rossella_s has quit IRC15:05
rhochmuthbut tomasz updated the requirements15:05
rhochmuthand the patch is in merge conflict15:05
rhochmuthso, can't be merged15:05
rhochmuthif no one says anything, we should move on15:06
*** yamamoto has joined #openstack-meeting-315:06
*** hichihara has quit IRC15:06
rhochmuth#topic Use oslo.db for sqla driver (yingjun)15:06
*** openstack changes topic to "Use oslo.db for sqla driver (yingjun) (Meeting topic: monasca)"15:06
rhochmuthhttps://review.openstack.org/#/c/395897/15:06
*** qwebirc85906 has joined #openstack-meeting-315:06
rhochmuthpossibly tomasz added this to the agenda too15:07
*** qwebirc85906 has quit IRC15:07
rhochmuthi can't say i'm all to familiar with what the implications are15:07
*** rossella_s has joined #openstack-meeting-315:08
*** MarkBaker has quit IRC15:08
bkleime neither15:08
rhochmuth#topic storyboard15:08
*** openstack changes topic to "storyboard (Meeting topic: monasca)"15:08
rhochmuthhttps://storyboard.openstack.org/ - should we use that ?15:09
*** mickeys has quit IRC15:09
rhochmuthso, there have been some discussion recently on switching to using storyboard15:09
rhochmuthi haven't tried it out15:09
rhochmuthbut, in general, compare to using launchpad for blueprints it seems like a huge improvement15:09
rhochmuthi don't think we should use for bug tracking based on some of the comments so far15:10
*** jobrs has joined #openstack-meeting-315:10
*** prateek has quit IRC15:10
rhochmuthso, i think we'll need to get back to this topic next week too15:10
*** rbak has joined #openstack-meeting-315:10
rhochmuthas whoever posted this to agenda is not here15:10
*** spotz_zzz is now known as spotz15:11
rhochmuth#topic InfluxDB 0.11 and beyond15:11
*** openstack changes topic to "InfluxDB 0.11 and beyond (Meeting topic: monasca)"15:11
rhochmuthhttps://review.openstack.org/#/c/396457/15:11
rhochmuththis is a brilliant pice of code and should be merged immediately IMHO!15:11
rhochmuthfrom my viewpoint the code is done15:12
bkleiworks with old/new?15:12
rhochmuthi've commented on some of the questions related to unit tests, which i don't feel are necessary or even desired in this case15:12
rhochmuthyes, it works with old and new15:12
bkleisweet15:13
rhochmuththat was a lot of work to make sure that was supported15:13
rhochmuthmore work than the actual code change that is15:13
bkleiship it!15:13
rhochmuthi've also added comments around my strategy for error handling in the code15:13
*** davidsha has left #openstack-meeting-315:13
*** JamesGu_ has joined #openstack-meeting-315:14
rhochmuthsince i can't really tell waht is an error or expected, it is just json, and there isn't a well defined schema, i test and just continue on15:14
rhochmuthif it doesn't match what I'm looking for in the result set from influxdb15:14
rhochmuthi didn't want to add lot's of messages to log files15:14
rhochmuthanyway, if anyone feels differently, that would be a debate15:15
rhochmuthnot saying i got it 100% perfect15:15
rhochmuthmy biggests counter argument woudl be do we test responses from SQL?15:15
rhochmuthwe don't, other than if it was succesful15:16
rhochmuthbut, maybe i should add some log messages or just let an exception occur15:16
rhochmuthyou'll need to look at the code to no what i'm talking about15:16
rhochmuth#topic Removing pure mysql code ? Is it needed or is it a dead-code ?15:17
*** openstack changes topic to "Removing pure mysql code ? Is it needed or is it a dead-code ? (Meeting topic: monasca)"15:17
rhochmuthi think we shoudl work on removing all the pure mysql code15:17
rhochmuthfrom the python implementation at least15:17
rhochmuthi would rather not touch the java implementation at this point15:17
*** edleafe- is now known as edleafe15:17
*** armax has joined #openstack-meeting-315:18
rhochmuthwe've got a lot of testing on the java mysql code and i don't want to introduce any bugs15:18
rhochmuthsorry15:18
rhochmuthbut, the python implementation cold have the mysql specific code removed15:18
*** stevemar__ has quit IRC15:18
rhochmuthat least from an hpe stand-point15:18
rhochmuththe notification engine is not that complicated, so risk of introducing a bug is low15:19
*** stevemar__ has joined #openstack-meeting-315:19
rhochmuthhowever, the risk of a bug in the java api and threshold engine, is much higher15:19
*** spotz is now known as spotz_zzz15:19
*** slaweq has left #openstack-meeting-315:19
rhochmuth#topic open floor15:19
*** openstack changes topic to "open floor (Meeting topic: monasca)"15:19
rhochmuthdoes anyone have any other topics to discuss?15:20
bkleii have one15:20
rhochmuthtoo late15:20
rhochmuthbye15:20
bklei:)15:20
rhochmuthjust kidding15:20
bkleiare we going to meet at https://www.openstack.org/ptg/15:20
bklei?15:20
bkleii don't see monasca listed wed-thu15:20
rhochmuthi wan't planning on it15:20
*** galstrom_zzz is now known as galstrom15:20
rhochmuthi don't think we'll get enough of the community to attend15:20
rhochmuthso hard to justify IMHO15:21
bkleisince it's in the US, we at charter are likely to be able to swing it this time15:21
rhochmuthdo you have a different opinion15:21
rhochmuthyeah, i know, but it would be just you guys and me there15:21
rhochmuthwe can to that in fort collins15:21
bkleisure -- that works too15:22
rhochmuthi checked with others outside of the usa, and travel will be hard to justify15:22
bkleigotcha15:22
rhochmuth i think we shoudl to a mid-cycle though15:22
bkleiwell -- if things change, we're likely to attend15:22
rhochmuthbut a remote one again15:22
rhochmuththat is nice to know15:22
*** spotz_zzz is now known as spotz15:22
rhochmuthon a side-note15:22
rhochmuthone of the reasons i might want to attend is to drive inter-project initiatives15:23
rhochmuthone that i think woudl work well is instrumenting openstack15:23
rhochmuthi'e been looking at promethues a lot lately15:23
rhochmuthmichael hoppal has posted a plugin for the monasca agent that scrapes apps that have been instrumented with the promethieus client libraries, or scrapes promethues exporters15:24
rhochmuththere is a library for python15:24
rhochmuthso, i'm wondering if instrumenting openstack services with the "promethues" client library would be a good direction adn if openstack would be interesteed in that direction15:24
rhochmuththe library is largely independent of promethues15:25
rhochmuthit isn't like it is just a promethues thing15:25
bkleiinteresting15:25
rhochmuthand as i say with our promethues client plugin, https://review.openstack.org/#/c/401413/, everything would be applicable to monasca too15:25
jobrsto be on the safe side we also developed a plugin15:25
rhochmuthyes, does your plugin scarpe promethus plugins, or does it scrape the promethues feeration api15:26
rhochmuthi thought it was the federation api15:26
rhochmuthbut did i missunderstand15:26
rhochmuthbecause i didn't want to overlap with your work15:26
jobrsthat  is right15:26
jobrshttps://github.com/sapcc/monasca-agent/blob/master/monasca_agent/collector/checks_d/prometheus.py15:26
rhochmuthok, so we aren't over-lapping then15:27
jobrsactually we can handle both15:27
rhochmuthohhh, i missed that15:27
rhochmuthsorry15:27
rhochmuthi hope we are not stepping on your toes15:27
rhochmuththat was my last intention15:27
rhochmuthi pointed michael at your plugin15:27
jobrsno, not at all. let's just look whether we can join forces here15:27
rhochmuthabsolutely!!!15:28
*** MarkBaker has joined #openstack-meeting-315:28
jobrswe have some nice mapping functionality for example15:28
jobrslet's have a separate call on that15:28
rhochmuthsure, i'm out this week, but next week will work well15:29
rhochmuthwe'll need to get michael invovled too15:29
jobrssure, you set up a meeting? or just send me this contact details so that I can follow up15:29
jobrsthanks15:29
rhochmuthjobrs: what do you think about instrumenting openstack with the promethues python client library15:30
*** yingjun has quit IRC15:30
rhochmuthjobrs: please setup meeting15:30
rhochmuthi'm still traveling this week15:30
jobrsok15:30
*** yingjun has joined #openstack-meeting-315:30
jobrswell, I think statsd is good for push and prometheus might end-up to be the defect standard for pull metrics15:31
rhochmuthmichael dot jam dot hoppal at hpe dot com15:31
jobrsdefacto, not defect :-)15:31
rhochmuthyes, that is what i'm thinking too15:31
jobrsstatsd is easier and less risky IMHO15:31
rhochmuthbut, i think it is a good opportunity for openstack instrumentation to leverage promethus momentum15:32
jobrsno open port, no need to buffer in the application, no need to thing about protecting access15:32
rhochmuthor to build on that15:32
rhochmuthand, i don't see any issues with monasca leveraging that work15:32
rhochmuthi think gettign openstack to adopt promethus would be easier than getting them to adopt statsd or monasca-statsd15:32
rhochmuththat was my thinking15:32
rhochmuthor reasoning15:33
rhochmuthand, in the container world, with openstack be run more and more in containers, it would be nice to support both promethues and monasca in one system15:33
jobrsit would be great to have some non-intrusive instrumentation tool that keeps instrumentation separate from the code15:33
rhochmuthand leverage auto-dscovery15:33
jobrsagreed15:34
rhochmuthlike a layer/wrapper ontop of promethues or monasca-statsd15:34
rhochmuthso, you could use either15:34
jobrsthat would be perfect15:34
*** yingjun has quit IRC15:35
rhochmuthoslo.instrumentation15:35
*** gouthamr has joined #openstack-meeting-315:35
jobrsI believe statsd+datadog extensions would fit both worlds15:35
jobrsthere are several lean statsd-exporters for prometheus already15:36
jobrs(written in Go)15:36
rhochmuthinteresting15:36
rhochmuthi missed that15:36
jobrshaving something similar that is pushing directly to Monasca API would defer the decision15:36
rhochmuthwell, that would be the dvantage of a wrapper library15:37
jobrsto those assembling the containers / pods15:37
rhochmuthmonasca could be directly used15:37
rhochmuthi'm going to have to leave in a minute15:38
rhochmuthjobrs: i'll meet with you next week along with michael15:38
jobrsok15:38
rhochmuthif anyone else want to attend, please let jobrs know15:39
rhochmuththis isn't a closed meeting15:39
rhochmuthbklei: are you good?15:39
bkleiyup -- thx roland15:39
JamesGu_jobrs and Roland: I do like to attend15:40
rhochmuthok, i can end the meeting or let you guys continue on15:40
rhochmuthJamesGu_: OK15:40
rhochmuthplease let jobrs know and send email15:40
rhochmuththx15:40
JamesGu_sure thx15:40
jobrsto joachim.barheine@sap.com15:40
JamesGu_thx jobrs15:41
rhochmuthok, i've got to run15:41
rhochmuthsorry about leaving early15:41
*** darrenc has quit IRC15:41
rhochmuthi'm going to close meeting in 30 seconds unless i hear otherwise15:42
*** darrenc has joined #openstack-meeting-315:42
rhochmuth#endmeeting15:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:42
openstackMeeting ended Wed Nov 30 15:42:53 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-11-30-15.00.html15:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-11-30-15.00.txt15:42
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-11-30-15.00.log.html15:42
*** rhochmuth has quit IRC15:42
*** hosanai has quit IRC15:43
*** koji has quit IRC15:43
*** yamamoto has quit IRC15:49
*** galstrom is now known as galstrom_zzz15:49
*** psachin has quit IRC15:59
*** catherineD has joined #openstack-meeting-315:59
*** jobrs has quit IRC15:59
*** bklei_ has joined #openstack-meeting-316:00
eglute#startmeeting defcore16:00
openstackMeeting started Wed Nov 30 16:00:24 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
markvoelkero/16:00
catherineDo/16:00
hogepodgeO/16:01
egluteGood morning! hope everyone had a good Thanksgiving last week16:01
eglute#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:01
eglute#link https://etherpad.openstack.org/p/DefCoreRoble.416:01
eglute#chair markvoelker hogepodge16:01
openstackCurrent chairs: eglute hogepodge markvoelker16:01
egluteplease review agenda and add/update as needed16:02
*** gouthamr has quit IRC16:02
*** bklei has quit IRC16:02
eglute#topic time change16:02
*** openstack changes topic to "time change (Meeting topic: defcore)"16:02
luzCo/16:03
Rockygo/16:03
egluteduring the last meeting we agreed to discuss it again this week. I know for the people in west coast this is early, but markvoelker said he would not be able to make it at a later time16:03
VWo/16:03
egluteany other comments regarding time?16:04
*** gema has joined #openstack-meeting-316:04
gemao/16:04
*** andreas_s has quit IRC16:04
Rockygi'm ok with this time as I have interop challenge right before16:05
*** mickeys has joined #openstack-meeting-316:05
hogepodgeThis time is fine for me16:05
dmelladoo/16:05
*** ibmko has joined #openstack-meeting-316:05
gemathis time works for me also16:05
luzCworks for me too16:05
egluteok, then we are going to leave it as is :)16:05
*** piet_ has joined #openstack-meeting-316:05
eglute#agreed leave meeting time the same16:05
eglute#topic PTG16:06
*** openstack changes topic to "PTG (Meeting topic: defcore)"16:06
eglutehogepodge were you able to find out about space for us at PTG?16:06
*** yamamoto has joined #openstack-meeting-316:06
hogepodgeeglute: it's looking better16:07
hogepodgeeglute: I'm still negotiating on it, and can check in to see where we are.16:07
*** galstrom_zzz is now known as galstrom16:07
eglutethat would be good, thank you hogepodge16:07
egluteany other comments/updates on PTG/midcycle?16:08
markvoelkerJust a note on alternatives if the PTG falls through:16:08
*** xhku_ has quit IRC16:08
markvoelkerWe talked about having a midcycle separately if PTG can't give us space.  I know some of you will be wanting to go to both...16:08
markvoelkerI've been toldI may be able to get us space at the VMWare/Airwatch HQ in Atlanta that week if we can't get space at the PTG, so that may be one more option to keep in mind.16:09
markvoelkerBut hopefully we won't need it. =)16:09
*** xhku has joined #openstack-meeting-316:09
dmelladomarkvoelker: that'd be great in case PTG wouldn't allow it16:09
*** mickeys has quit IRC16:09
eglutenice, thank you markvoelker16:09
dmelladoto also avoid having a different travel afterwards to some mid cycle16:10
dmelladothanks ;)16:10
markvoelkerDo note that's it not really close to the PTG hotel though...it'll be a bit of a drive to the north side of town.16:10
*** iyamahat has joined #openstack-meeting-316:10
markvoelkerAnyway, I'll send out some info it comes to that and I can confirm space.16:10
*** bklei_ has quit IRC16:10
Rockygany chance it's along mass transit?16:10
*** ianychoi has joined #openstack-meeting-316:10
markvoelkerRockyg: note sure, honestly.16:10
markvoelker*not16:10
eglutefor those that joined late, here is ehterpad for today: https://etherpad.openstack.org/p/DefCoreRoble.416:11
egluteanything else regarding PTG?16:11
eglute#topic Project Oaktree16:12
*** openstack changes topic to "Project Oaktree (Meeting topic: defcore)"16:12
egluteDefCore's mascot is an oaktree ... will this project be confusing with the DefCore project?16:12
RockygI thin they have the first day for cross project?  We should not meet on the cross proj day...16:12
eglute#link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107336.html16:12
egluteRockyg, agree, not first day16:12
catherineDyea  I think we should let them know early enough about our mascot as Oaktree16:13
egluteso i think mordred already knows about it16:13
Rockyg++  we had it first ;-)16:13
catherineDRockyg: true16:14
Rockygmordred, you aware defcore mascot is an oaktree?16:14
hogepodgeI'm inclined to ask Foundation Marketing to change our mascot if it's not too late16:14
Rockygchange to what, hogepodge ?16:15
egluteI agree, either mordred changes project name or we change mascot16:15
hogepodgeThe DefCore/Interop logo to something else.16:15
hogepodgeAh, to what, I don't know.16:15
eglutewe had other suggestions when we did a quick pick last time,16:16
markvoelkerYeah, I'm personally not terribly wed to the oaktree mascot and we haven't started using it yet, so I'd be willing to change it if that's easiest for all involved.16:16
eglutebut we could also propose new ones here16:16
egluterather, in etherpad16:17
gemawhat was the second option?16:17
eglutepelase add: https://etherpad.openstack.org/p/DefCoreRoble.416:17
eglutegema I would need to find it16:17
eglutehttp://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_67553469c6bccc6a16:18
eglutehere we go16:18
gemaonion16:18
egluteeveryone ok with onion?16:19
egluteor have better suggestions?16:19
Rockygonion is ok by me16:19
hogepodgeI'm checking with staff about the possibility too and will report back16:19
*** rajinir has joined #openstack-meeting-316:19
Rockyg  any other suggestions?  We could let it sit for a week and then finalize16:19
eglutethank you hogepodge16:20
markvoelkerYeah, let's let it sit while we check with the Foundation and see if it's even possible to make a change at this point16:20
*** reed_ has joined #openstack-meeting-316:20
*** danpawlik has quit IRC16:21
eglute#action hogepodge to check with staff about the possibility of changing the logo16:21
eglute#action mordred will consider changing the name of oaktree to appletree or something16:21
eglute#topic new alias for test16:22
*** openstack changes topic to "new alias for test (Meeting topic: defcore)"16:22
egluteeveryone please review #link https://review.openstack.org/#/c/401842/16:22
eglutei think it looks straightforward to me16:23
eglute#action everyone review #link https://review.openstack.org/#/c/401842/16:23
egluteif there are no other comments, we can move to the guideline16:24
eglute#topic 2017.01 guideline16:24
*** openstack changes topic to "2017.01 guideline (Meeting topic: defcore)"16:24
egluteis shamail here today?16:24
*** revon has joined #openstack-meeting-316:24
egluteI dont have any updates on cinder from him, has anyone else had a chance to look at cinder?16:25
egluteok, i will follow up with shamail after this meeting16:26
*** yamahata has joined #openstack-meeting-316:26
eglute#action eglute to follow up with shamail regarding cinder16:26
egluteNext is swift.16:26
eglutecan everyone please review https://review.openstack.org/#/c/398428/?16:26
markvoelkereglute: I've been picking through all the new stuff proposed for Swift.  Almost done reviewing, should have it up this evening16:26
egluteI need to fix whatever is making jenkins unhappy16:27
eglutethank you markvoelker, appreciate it!16:27
egluteanyone else had a chance to take a look?16:28
egluteor have any comments?16:28
markvoelkerOne thing I was curious about: did you find external tools using objectstore-info-request and container-metadata?  E.g. things like libcloud or whatnot?16:28
eglutemarkvoelker it has been a while! i will need to get back to you on that one16:29
markvoelkerOk, no worries...I'll look around too, just wondered if you had any leads as that tends to take a little digging. =)16:29
eglutei will try to remember what i found. i will get back to you!16:30
egluteand next time i will document it too16:30
egluteanything else on swift?16:31
egluteok, next is nova16:32
egluteshamail needs to update https://review.openstack.org/#/c/385781/16:32
egluteif you have not reviewed it, please do so16:32
eglute#action eglute to follow up with shamail on https://review.openstack.org/#/c/385781/16:32
egluteanything else on this?16:33
*** ianychoi has quit IRC16:33
egluteKeystone: https://review.openstack.org/#/c/398737/216:33
eglutethanks markvoelker for submitting the patch16:33
eglutelooks good to me!16:34
egluteeveryone else please review it as well16:34
eglutemarkvoelker added one new capability as advisory16:35
egluteshould be pretty straightforward.16:35
egluteglad to see keystone capability list grow16:35
egluteif no comments on Keystone, glance is next16:35
*** reed_ has quit IRC16:36
eglute#link https://review.openstack.org/#/c/398706/16:36
eglutemarkvoelker thanks for submitting16:36
eglutewas that all for glance?16:36
markvoelkerAll I have, yes.16:36
eglutegreat, thank you!16:36
egluteeveryone, please review, should be an easy one!16:37
eglute#topic name change16:37
*** openstack changes topic to "name change (Meeting topic: defcore)"16:37
eglutewe are still working on the name change! any updates on things that were in progress?16:37
markvoelkerI have a draft blog post half-done but left off to work on reviewing swift stuff16:38
markvoelker(and since I was going to put our logo in there I guess I need to modify it a bit until the oaktree thing gets sorted =p)16:38
eglutethanks markvoelker16:38
egluteany other updates? i think shamail was working on moving wikis16:39
eglutereminder: please join #openstack-interop if you haven't yet16:39
luzCI started with Refstack but was wondering if we are changing "Defcore guideline" to "Interop working group guideline"16:40
luzC?16:40
markvoelkerluzC: I'd use "interoperability guideline".16:40
catherineDmarkvoelker: as we discuss in the RefStack meeting16:41
eglutemarkvoelker that does sound good16:41
catherineDwe believe that "Interoperability Guideline" means something much bigger scope16:41
eglutecatherineD can you explain16:42
catherineDfor example: whatever out come from Interop-Challenge or "OakTree" project could be "interoperability Guideline" so are the customized guidelines16:42
hogepodgeThis week I can finalize mailing list16:42
*** caboucha has joined #openstack-meeting-316:42
catherineDDefCore guideline is a very specific name pointing that those are the guidelines from this group .. so we need something at that level with the new name16:43
markvoelkercatherineD: I think they've been referred to in presentations  and such as interoperability guidelines for some time, but I'm ok with either. =)16:44
eglutei agree with markvoelker16:45
eglutecatherineD luzC you are talking about renaming this page, correct? https://refstack.openstack.org/#/guidelines16:46
catherineDeglute: yes16:46
catherineDthat is why it better be specific as of whoes guidelines are those ..16:47
egluteperhaps whatever teh new name is, where the heading "DefCore Guidelines" could also link to teh defcore repo? (which also needs to be renamed)16:47
*** caboucha_ has joined #openstack-meeting-316:47
eglute"OpenStack Interop Guidelines"16:47
eglutewe define the official interop guidelines for openstack16:48
*** caboucha has quit IRC16:48
eglutelinking to them might help with the confusion16:48
markvoelkerand/or using a special logo/color/some other UX hint16:49
RockygMaybe adding "official" would help?16:49
Rockygor sanctioned oe approved?16:50
eglutei like all those suggestions. what does everyone think?16:50
markvoelkerMaybe it's best to strike up an ML discussion on this?16:51
eglutemarkvoelker +116:51
luzCmarkvolker ++16:51
egluteluzC/ catherineD can you start a mailing list discussion?16:52
*** qwebirc15108 has quit IRC16:52
luzCyes NP16:52
eglutethank you luzC!16:52
eglutenaming is hard!16:52
egluteanything else on rename?16:53
eglutethanks hogepodge for working on the mailing list rename16:53
*** bpokorny has joined #openstack-meeting-316:54
eglute#topic how projects can become part of Guidelines16:54
*** openstack changes topic to "how projects can become part of Guidelines (Meeting topic: defcore)"16:54
egluteI know markvoelker has a lot of things he is working on! this one also his16:54
eglutemarkvoelker can i help with this one?16:54
markvoelkerSure.  I've sort of let this one sit since there's other stuff on the plate.16:56
*** Patifa has joined #openstack-meeting-316:56
eglutecool. do you have something started, or not yet?16:57
markvoelkerMostly bullets, but nothing in paragraph form I think.  I'll clean it up and send it your way.16:57
eglutesounds good, thank you markvoelker!16:57
eglutelast couple minutes remaining, any last comments?16:57
gemaI have a question from the interop challenge meeting. We are being evicted from the channel where we currently hold those meetings and are considering options. Would we be able to use the #openstack-interop channel for the interop challenge meetings on Wednesdays at 3pm UTC?16:57
eglutegema  i think you could, but please check that the bot there works16:58
eglutemeeting bot that is16:58
gemaeglute: ack, will do16:58
Rockygthanks, gema!16:58
gemathank you guys :D16:58
*** rhochmuth has joined #openstack-meeting-316:58
eglutei am not sure what needs to happen for a channel to have  meeting bot16:58
*** rhochmuth has quit IRC16:58
egluteit might already be tehre16:59
gemaI think it is there already, but will check16:59
Rockyginfra does magic16:59
egluteheh, nice16:59
Rockygeasiest way to check is to type startmeeting and see what happens16:59
markvoelkerNote that infra has been resistant to having meetings be in non-meeting channels in the past...16:59
*** ccamacho is now known as ccamacho|afk16:59
gemamarkvoelker: will check with them16:59
eglutewe are out of time. thanks everyone! i will be around in the interop channel if anyone wants to talk!17:00
eglute#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Nov 30 17:00:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.log.html17:00
RockygYup.  I just checked with Thierry on open meeting rooms.  We've can get 1400 but not 150017:00
catherineDbye17:00
Rockygcya17:00
*** dimtruck is now known as zz_dimtruck17:01
*** JamesGu_ has quit IRC17:03
*** mickeys has joined #openstack-meeting-317:06
*** stevejims has left #openstack-meeting-317:07
*** matrohon has quit IRC17:07
*** gema has left #openstack-meeting-317:07
*** mickeys has quit IRC17:10
*** zz_dimtruck is now known as dimtruck17:10
*** slaweq_ has joined #openstack-meeting-317:11
*** bpokorny has quit IRC17:11
*** yamamoto has quit IRC17:14
*** yamamoto has joined #openstack-meeting-317:15
*** yamamoto has quit IRC17:17
*** topol has quit IRC17:17
*** numans has quit IRC17:17
*** yamamoto has joined #openstack-meeting-317:18
*** MarkBaker has quit IRC17:18
*** MarkBaker has joined #openstack-meeting-317:19
*** mickeys has joined #openstack-meeting-317:20
*** pcaruana has quit IRC17:23
*** slaweq_ has quit IRC17:23
*** bpokorny has joined #openstack-meeting-317:24
*** slaweq_ has joined #openstack-meeting-317:24
*** spzala has quit IRC17:25
*** tongli has quit IRC17:30
*** rossella_s has quit IRC17:31
*** rossella_s has joined #openstack-meeting-317:31
*** woodster_ has joined #openstack-meeting-317:33
*** yamamoto has quit IRC17:34
*** slaweq_ has quit IRC17:36
*** catherineD has left #openstack-meeting-317:42
*** matjazp has joined #openstack-meeting-317:43
*** yamamoto has joined #openstack-meeting-317:46
*** yamamoto has quit IRC17:51
*** dimtruck is now known as zz_dimtruck17:51
*** yamahata has quit IRC17:51
*** MarkBaker has quit IRC17:52
*** matrohon has joined #openstack-meeting-317:52
*** MarkBaker has joined #openstack-meeting-317:53
*** iyamahat has quit IRC17:55
*** alexismonville has joined #openstack-meeting-317:57
*** spzala has joined #openstack-meeting-317:59
*** bobmel has quit IRC18:00
*** VW has quit IRC18:02
*** spzala has quit IRC18:03
*** numans has joined #openstack-meeting-318:04
*** ralonsoh has quit IRC18:04
*** MarkBaker has quit IRC18:06
*** alexismonville has quit IRC18:06
*** galstrom is now known as galstrom_zzz18:08
*** ibmko has quit IRC18:09
*** zz_dimtruck is now known as dimtruck18:10
*** VW has joined #openstack-meeting-318:11
*** iyamahat has joined #openstack-meeting-318:16
*** tonytan4ever has quit IRC18:19
*** tonytan4ever has joined #openstack-meeting-318:20
*** kzaitsev_mb has quit IRC18:22
*** topol has joined #openstack-meeting-318:23
*** stanzgy has joined #openstack-meeting-318:23
*** galstrom_zzz has quit IRC18:24
*** tonytan4ever has quit IRC18:27
*** galstrom_zzz has joined #openstack-meeting-318:27
*** tonytan4ever has joined #openstack-meeting-318:28
*** ianychoi has joined #openstack-meeting-318:29
*** alexismonville has joined #openstack-meeting-318:30
*** stanzgy has quit IRC18:32
*** yamahata has joined #openstack-meeting-318:35
*** paul-carlton2 has quit IRC18:35
*** kbyrne has quit IRC18:35
*** Swami has quit IRC18:36
*** Swami has joined #openstack-meeting-318:37
*** kbyrne has joined #openstack-meeting-318:38
*** spzala has joined #openstack-meeting-318:43
*** spzala has quit IRC18:47
*** spzala has joined #openstack-meeting-318:47
*** bpokorny has quit IRC18:55
*** tonytan4ever has quit IRC19:02
*** MarkBaker has joined #openstack-meeting-319:02
*** reedip_ has quit IRC19:04
*** bpokorny has joined #openstack-meeting-319:08
*** alexismonville has quit IRC19:10
*** sambetts is now known as sambetts|afk19:10
*** Swami has quit IRC19:11
*** diablo_rojo_phon has joined #openstack-meeting-319:12
*** pvaneck has joined #openstack-meeting-319:16
*** tonytan4ever has joined #openstack-meeting-319:25
*** betherly has joined #openstack-meeting-319:35
*** claudiub has quit IRC19:43
*** robcresswell has joined #openstack-meeting-319:46
*** ying_zuo has joined #openstack-meeting-319:47
*** bpokorny has quit IRC19:51
*** gugl has joined #openstack-meeting-319:51
*** bpokorny has joined #openstack-meeting-319:51
*** r1chardj0n3s has joined #openstack-meeting-319:54
*** bpokorny has quit IRC19:57
*** bpokorny has joined #openstack-meeting-319:58
*** tqtran has joined #openstack-meeting-319:59
*** tqtran has left #openstack-meeting-319:59
*** tqtran has joined #openstack-meeting-320:00
*** MeganR has joined #openstack-meeting-320:00
r1chardj0n3s#startmeeting horizon20:00
openstackMeeting started Wed Nov 30 20:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is r1chardj0n3s. 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
betherlyo/ hallo20:00
openstackThe meeting name has been set to 'horizon'20:00
r1chardj0n3so/20:00
*** VW_ has joined #openstack-meeting-320:00
robcresswello/20:00
*** clu_ has joined #openstack-meeting-320:00
r1chardj0n3sUK represent!20:00
tqtran[=_=]/20:00
betherlywooooot20:00
r1chardj0n3sokie dokie, on with the thing20:01
rhagarty_o/20:01
*** VW_ has quit IRC20:01
r1chardj0n3s#topic Priority patches for review20:01
*** openstack changes topic to "Priority patches for review (Meeting topic: horizon)"20:01
clu_o/20:01
*** jgravel has joined #openstack-meeting-320:01
r1chardj0n3s#link https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open is the list of patches we'd like to see reviewed as highest priority20:01
r1chardj0n3s#link https://etherpad.openstack.org/p/horizon-ocata-priorities has a bunch of patches under Ocata-2 that we'll start moving on to20:02
r1chardj0n3sI’ve tried to capture all of the in-play angularjs panel work, but if I missed any please note them.20:02
*** bpokorny has quit IRC20:02
*** VW_ has joined #openstack-meeting-320:02
r1chardj0n3sI think since there’s so many, I’d like to know whether anyone has any priorities in that lot. Yes, high priority priority patches20:03
*** VW_ has quit IRC20:03
*** gugl has quit IRC20:03
*** gugl has joined #openstack-meeting-320:04
david-lyleo/20:04
*** VW has quit IRC20:04
*** VW has joined #openstack-meeting-320:05
r1chardj0n3sOK, I'll just mark the ones that have active developers working on them then ;-)20:06
r1chardj0n3s#topic Badges20:06
*** openstack changes topic to "Badges (Meeting topic: horizon)"20:06
r1chardj0n3s#link https://review.openstack.org/#/c/402556/ if anyone cares enough, please fix this thing20:06
r1chardj0n3s(we do love a bit of make-work here in OpenStack)20:06
*** MarkBaker has quit IRC20:07
david-lyler1chardj0n3s: I thought there was a patch fixing that already20:07
robcresswell-.-20:07
robcresswellFixing openstack one pointless patch at a time20:07
david-lylehttps://review.openstack.org/#/c/404382/ maybe20:07
r1chardj0n3sdavid-lyle: right. my care level is super low, given other priorities20:08
r1chardj0n3sok, moving on20:09
r1chardj0n3s#topic Zaqar push-based communication via websocket (POC)20:09
*** openstack changes topic to "Zaqar push-based communication via websocket (POC) (Meeting topic: horizon)"20:09
tqtranso i brought this up last week, but wanted to wait until this week for more people to get input20:10
r1chardj0n3stqtran?20:10
r1chardj0n3s(ah, sorry)20:10
*** gouthamr has joined #openstack-meeting-320:10
tqtranthe zaqar ptl uploaded a POC patch showing how we can use websocket instead of polling20:10
tqtranhttps://review.openstack.org/#/c/246009/20:10
tqtranbut the problem is that its written using legacy js20:11
tqtranwe have plans on implementing instances panel, but i doubt that will land anytime soon20:11
tqtranso the question is: do we want the POC using legacy now, or wait until the new instances panel kick in20:11
robcresswellit'd be best to do it on Images right?20:12
robcresswellThat already misses the polling anyway20:12
david-lylewhy would we poll images?20:12
robcresswellstatus20:12
david-lyleare you expecting them to change?20:12
tqtrani believe we are polling images in the ngimages panel20:12
robcresswellWhen creating new ones? Yeah I assume so20:12
robcresswellI dont think angular tables poll do they?20:13
r1chardj0n3sthat patch needs a lot of work, also, there's a lot of hard-coding of things that should be configurable or discoverable in there20:13
tqtranthey are polling sadly, theres no push-based mechanism on the backend20:13
robcresswellI thought they did nothing right now20:13
robcresswellthe regular one does, bug I thought ng didnt20:13
tqtranpretty sure its polling, i remember reviewing a patch on it20:14
*** lpetrut has joined #openstack-meeting-320:14
tqtrananyway, maybe we can get the POC websocket thing to work on images first?20:14
david-lylewas are polling :(20:14
david-lyleat least the django was20:15
david-lyles/was/we/20:15
robcresswellanyway, yes, a websocket angular POC would make more sense20:15
* david-lyle hangs head20:15
r1chardj0n3s+1 to getting it working for images20:15
tqtranok, i'll tell them that then20:16
r1chardj0n3swebsocket polling came up at the summit and searchlight was mentioned, yeah?20:16
david-lyleI feel like we should have two dashboards20:16
r1chardj0n3sor am I misremembering things20:16
david-lyleone with only core services and plugin support20:16
david-lyleand one with support for several dependent projects that would make life better20:17
david-lylebut I digress20:17
r1chardj0n3scrazy20:17
r1chardj0n3smoving on20:17
r1chardj0n3s#topic Using execfile also for local_settings.py, not just loca_settings.d20:18
*** openstack changes topic to "Using execfile also for local_settings.py, not just loca_settings.d (Meeting topic: horizon)"20:18
r1chardj0n3s(no name against this, assuming it was radomir?)20:18
david-lyleI mean currently we're polling on the server side regardless20:18
robcresswellyeah thats rdopiera20:18
*** ibmko has joined #openstack-meeting-320:19
r1chardj0n3sI assume he's agitating for not using import to get the contents of local_settings.py; I'm not sure exactly why, but I'm generally in favour of using execfile over import unless there's a good reason to use the latter.20:19
*** matrohon has quit IRC20:19
r1chardj0n3s.. but I thought he wanted to get rid of Python-based settings completely20:20
david-lylethese are for plugins and themes, that would be even further down the road20:21
*** bobmel has joined #openstack-meeting-320:22
r1chardj0n3sOK, in the absence of Radomir, I guess we'll have to table that discussion until next meeting.20:22
r1chardj0n3s#topic Open Discussion20:23
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:23
r1chardj0n3sanyone got anything they'd like to bring up? say, the size of the ocata-2 priority list? :-)20:23
robcresswellNothing in particular :)20:24
ediardome20:25
*** srobert_ has joined #openstack-meeting-320:25
ediardohttps://review.openstack.org/#/c/388200/20:25
r1chardj0n3sI would like to point out that the run_tests.sh removal effort by robcresswell is moving along really well, and if you've not stopped using it already you should do so :-)20:25
r1chardj0n3sthe "final" tox fixup patch will merge imminently20:25
r1chardj0n3s#link https://review.openstack.org/#/c/391506/20:25
r1chardj0n3sgive it a run if you haven't, please20:25
ediardoI nevermind20:25
*** matrohon has joined #openstack-meeting-320:25
ediardoI read something there20:26
r1chardj0n3swe've also been trying to enforce upper-constraints in all the stable branches, so we'll probably release xstatic-angular-bootstrap 2.2.0.0 very soon, which breaks a bunch of stuff20:26
r1chardj0n3sediardo: yeah, the coverage fairy decided to pay a visit :-(20:27
*** galstrom_zzz is now known as galstrom20:27
ediardoyes, I'll work on it20:27
r1chardj0n3sdid you find the coverage reports?20:28
*** srobert_ has quit IRC20:28
ediardoI just read Thai's comment20:28
r1chardj0n3syup20:28
ediardoYes, I found 'em20:28
ediardoThanks20:29
*** srobert has quit IRC20:29
r1chardj0n3sok folks, I reckon we're done then, thanks for coming!20:29
r1chardj0n3s#endmeeting20:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:29
openstackMeeting ended Wed Nov 30 20:29:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-11-30-20.00.html20:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-11-30-20.00.txt20:29
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-11-30-20.00.log.html20:29
betherlyCheers all!20:29
*** tqtran has left #openstack-meeting-320:29
betherlyHave a good day/evening20:30
*** jgravel has left #openstack-meeting-320:30
*** rossella_s has quit IRC20:31
*** r1chardj0n3s has left #openstack-meeting-320:32
*** galstrom is now known as galstrom_zzz20:36
*** mickeys has quit IRC20:38
*** kzaitsev_mb has joined #openstack-meeting-320:42
*** dtp has joined #openstack-meeting-320:46
*** Swami has joined #openstack-meeting-320:48
*** spzala has quit IRC20:54
*** ying_zuo has quit IRC20:54
*** MeganR has quit IRC20:56
*** haleyb_ has joined #openstack-meeting-320:57
*** bpokorny has joined #openstack-meeting-320:58
dansmith#startmeeting nova_cells21:00
openstackMeeting started Wed Nov 30 21:00:00 2016 UTC and is due to finish in 60 minutes.  The chair is dansmith. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
dansmith*ahem*21:00
melwitto/21:00
*** mriedem has joined #openstack-meeting-321:00
mriedemo/21:00
dansmithwell...21:01
dansmithwas really hoping for alaski to show up21:01
dansmithbecause I have questions21:01
dansmithconcerns21:01
dtpo/21:01
*** haleyb_ has quit IRC21:01
dtpi made it21:01
dansmithcongrats :)21:01
dtpthank you21:02
dansmith#topic cells testing / bugs21:02
*** openstack changes topic to "cells testing / bugs (Meeting topic: nova_cells)"21:02
dansmithanything on testing/bugs this week?21:02
mriedemthe only bug we had was that pg one21:02
mriedemonly took 5 days to fix it21:02
dansmithtrue, I guess that was because of cellsv221:02
mriedemotherwise nada21:03
dansmith#topic open reviews21:03
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"21:03
dansmithso, I refreshed my set again just a bit ago:21:03
dansmithhttps://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/cells-scheduling-interaction21:03
dansmithon top of melwitt's cell database fixture21:03
dansmiththe last patch is mostly good for unit tests at this point,21:03
mriedemso https://review.openstack.org/#/c/396417/ got sorted out?21:03
dansmithexcept for one ugly gotcha around cellsv121:03
dansmithmriedem: I need a fix to oslo.messaging for that, which I have proposed21:04
dansmithmriedem: but their gate is fubar right now21:04
mriedemdo they know what's up?21:04
mriedemlike, are they fixing their stuff?21:04
dansmithmriedem: so I have a hack in there to make it work, but I don't expect us to merge it21:04
dansmithmriedem: it's zmq.. someone lobbed a patch at it claiming to fix it, but it didn't21:04
dansmithmriedem: but yeah, I've been in there poking people about it21:04
dansmithmy fix has been +W for a few days but can't make it through gate21:04
mriedemare you going to wip https://review.openstack.org/#/c/396417/ then?21:05
mriedemwe could also do the old depends-on dance21:05
dansmithif I rechecked it harder I could maybe get it in21:05
mriedembut will need to depend on a release and g-r bump21:05
dansmithyeah21:05
dansmithmriedem: this is the hack: https://review.openstack.org/#/c/396417/15/nova/rpc.py@7721:05
mriedemyeah i saw it21:05
dansmithyeah I guess I can -W it21:06
mriedemand https://review.openstack.org/#/c/403924/ is what we want21:06
dansmithyar21:06
mriedemfun http://logs.openstack.org/24/403924/1/check/gate-oslo.messaging-dsvm-functional-py27-zeromq/35e71b1/console.html#_2016-11-29_19_18_53_45826021:06
dansmithanyway, so yeah that is blocked at the moment21:07
mriedemif it's not a regression and no one is fixing it we could skip the test...21:07
mriedembut maybe that's extreme for right now21:07
*** srobert has joined #openstack-meeting-321:07
dansmith*shrug*21:07
mriedemi guess we can light a fire when we've reviewed the entire series21:07
dansmithyeah21:07
dansmiththe bottom couple of patches there can merge I think21:07
dansmithat least21:07
dansmithanyway, there is a bigger problem at the top of that set21:08
dansmithand that is around cellsv121:08
mriedemwhich one? https://review.openstack.org/#/c/396775/ ?21:08
dansmithno that one is out for the moment21:08
dansmithhttps://review.openstack.org/#/c/39641721:08
*** Marcellin__ has joined #openstack-meeting-321:08
dansmithso the deal there is something I realized yesterday while trying to squash the last couple of unit test failures21:09
dansmithin cellsv1, we do the compute/api bit, create in the api, then call down to the cell, which replays the compute/api part in the cell,21:09
*** dimtruck is now known as zz_dimtruck21:09
dansmithbefore finally casting to conductor to get things going21:09
*** rtheis has quit IRC21:10
dansmithif we finish this move of the create from api to conductor,21:10
dansmiththen we're not going to create in the api cell, and we're going to call to conductor in the api cell,21:10
dansmithwhich is then going to try to talk directly to the compute instead of calling through the cells rpc to get down there21:11
dansmithwhich is ... scary21:11
dansmithbecause (a) I don't want to add any more cells calls, and certainly not for things that need to call to conductor21:11
dansmithso I'm not really sure what to do21:11
dansmithwhich is what I was hoping to poke alaski about today21:11
dansmithdoes any of that ranting make sense?21:11
mriedemand we don't want a bunch of if CONF.cells.enabled checks all over this flow21:12
dansmithyeah21:12
dansmithand we don't want to have to keep two instance create paths either21:12
mriedemi won't profess to understand the entire create flow through the api for cells v121:12
dansmithwell, it's complicated21:12
mriedemso the parent api cell creates the instance in the parent api cell db?21:12
dansmithbut we do it twice, once in the api cell and once in the child cell21:12
mriedemoh right the instance is in both places21:13
mriedemhence the up calls to sync21:13
dansmithand that replication happens at the compute/api layer,21:13
*** srobert has quit IRC21:13
dansmithby intercepting the compute/api call, doing some of it, and then re-playing it in the child cell21:13
mriedemand when status changes in the child cell while building the instance, we send that up to the parent cell to update the instance there too right?21:13
dansmithyeah21:13
*** srobert has joined #openstack-meeting-321:13
mriedemand cellsv1 doesn't know jack about build requests...21:14
dansmithnor does it know about conductor21:14
*** MarkBaker has joined #openstack-meeting-321:14
dansmithit's purely replication at the compute/api layer21:14
*** zz_dimtruck is now known as dimtruck21:14
dansmithwe also *have* to create in the api cell before we create in the child because otherwise the api stops working,21:14
dansmithso we can't even try to patch it up by making the first sync create the instance back at the top again21:15
dansmithso yeah21:16
dansmithpretty much the suck.21:16
melwittI was thinking there's already "if cell_type == 'api'" in the compute/api and maybe we could just do the old way in there ...21:16
melwittold create I mean21:16
dansmithmelwitt: well, it means we keep two paths21:16
mriedemCellsScheduler is parent/api cell right?21:17
*** melwitt has left #openstack-meeting-321:17
mriedemwhich builds the instances in the api cell21:17
*** caboucha_ has quit IRC21:17
*** melwitt has joined #openstack-meeting-321:17
mriedemand calls the compute api code to create the instance in the api cell db21:17
melwittgah pushed the wrong key21:17
dansmithmriedem: I dunno tbh21:17
mriedemi'm pretty sure it is b/c _create_instances_here calls instance = self.compute_api.create_db_entry_for_new_instance(21:17
melwittdon't we have to keep the two paths though? I mean wherever it says things like "cell_type =='api'" has to stay because cells v1 needs it21:17
mriedemnon-cellsv1 create_db_entry_for_new_instance doesn't create the instance in the db21:18
dansmithmelwitt: well, yes, but having instance created in two different *services* is uglier than just in two places in the same service, IMHO21:18
dansmithmelwitt: because then you get into all kinds of potentials for races I think, assuming that the instance is created by a certain point, when it might not be, etc21:19
dansmithI mean, obviously the path out of this box is going to be some amount of "if cells1, else" sort of thing21:19
dansmithbut I'm just dreading it21:19
melwittyeah21:19
dansmithanyway,21:20
mriedemhmm, so have we hit the patch that sees this fail in cells v1 yet?21:20
dansmithI was hoping that maybe someone had already thought about this and what the best plan would be21:20
*** mickeys has joined #openstack-meeting-321:20
dansmithmriedem: it fails in unit tests, I'm still waiting for the run on cellsv1, but I might have other breakages to fix first21:21
dansmithI just pushed it up like 30 minutes ago21:21
mriedemand that's just https://review.openstack.org/#/c/396417 ?21:21
mriedemi figured it would manifest in https://review.openstack.org/#/c/319379/21:21
dansmithno, https://review.openstack.org/#/c/31937921:22
mriedemah ok21:22
mriedemyeah21:22
mriedemthat makes sense21:22
*** claudiub has joined #openstack-meeting-321:22
mriedemso, unit tests will fail, sure, but i think we should check out what the cells v1 job failures are and then start poking at it21:23
dansmithanyway, so I will try to fix whatever that shakes out in the next day for the normal path and then see if I can start throwing things at it to make it still work21:23
melwittyeah, I guess I would be thinking to preserve what cells v1 is doing until we remove it, which is the two path thing. because the alternatives involve trying to sync the create upward to the API or something, right?21:23
mriedemcould we....take the build request that's created in the api now and use that to hydrate and create the instance in the api/parent cell db?21:23
dansmithmelwitt: yeah, I'm just concerned about other stuff, like bits we have moved out of compute api to conductor that won't get run for cellsv1, like bdm validation or something (not really, but something like that)21:23
mriedeminstead of the cells scheduler calling the compute api to create the instance?21:24
dansmithmriedem: no, we have to create it at about the same place as we do now, or later, because of all the junk that compute/api does to the instance21:24
melwittI see21:24
mriedemdoes to the instance how?21:24
mriedemlike figuring out the name and stuff?21:25
dansmithmriedem: well, for one thing it handles the "num_instances" bit, as well as yeah names and stuff21:25
mriedemi thought that was all done before the instance was serialized and the build request was created21:25
dansmithit's spread all over the place21:25
*** hurgleburgler has joined #openstack-meeting-321:25
dansmithwell, I should say,21:25
dansmithI don't know where exactly the cell scheduler bit plugs in,21:25
dansmithso maybe it's more in the middle than I think, I dunno21:26
mriedemok, so....sounds like maybe 2 options,21:26
dansmithregardless, fixing at that layer seems like more new different code21:26
dansmithwhich I'm afraid of21:26
mriedem1. if the build_request.instance is 90% what we need in the api cell for v1, then maybe we can use that to create it in the api cell for v121:26
mriedem2. else we see if we can hack in a conditional here or there to do the dirty deeds done dirt cheap21:26
mriedemuntil we can kill cells v121:26
dansmithI think #2 is the thing to try firfst21:26
dansmithmeaning,21:27
mriedemsure21:27
melwittI like that my suggestion is the AC/DC one21:27
dansmithright now we have a place where we just no longer call instance.create()21:27
mriedem3. alaski saves our asses21:27
dansmithand so we'd just do "if cellsv1, do create like old times" but then we also have to not call the new conductor method I think21:27
melwittyeah, alaski, come and solve this for us21:27
dansmithsomething21:27
mriedemdansmith: yeah that's not too terrible21:27
mriedemif that's all it is21:27
dansmithI think it's end-of-days worst possible thing21:27
mriedem# NOTE(danms): this makes bon scott roll in his grave, but we have to do this...21:28
dtplol21:28
dansmithwhich is probably "not too terrible" times standard dansmith inflation factor21:28
melwitthaha21:28
mriedem4. dtp fixes this all for us21:28
*** diablo_rojo_phon has quit IRC21:28
dtpi wish!21:28
* dansmith reassigns to dtp21:28
mriedemdid laski mention any of this in his brain dump patch?21:28
dansmithmriedem: no21:29
dansmithmriedem: I looked21:29
dansmitha lot. :)21:29
mriedemdagnabbit21:29
mriedemha21:29
melwittI looked too21:29
melwittfirst thing I did :)21:29
dansmithalright, anyway, enough dwelling on this21:29
mriedemso,21:29
mriedemquotas?!21:29
dansmithI will keep plugging away21:29
* dansmith hands the mic to melwitt 21:29
melwittyeah, I'm working on it but nothing to show yet. haven't gotten as much done by now as I wanted to21:30
mriedemthe spec was amended :) https://review.openstack.org/#/c/399750/ that's something21:31
melwittoh, right. I did do that21:31
*** VW has quit IRC21:31
*** VW has joined #openstack-meeting-321:32
dansmithokay, well,21:32
dansmith#topic open dis-cush-ee-ohn21:32
*** openstack changes topic to "open dis-cush-ee-ohn (Meeting topic: nova_cells)"21:32
dansmithanything else?21:32
mriedemwell,21:32
mriedemon the ci front,21:32
mriedemwe should be back to nova-net being gone by eod21:33
mriedemexcept for cells v121:33
dansmithyeah, that's good21:33
mriedemand on the bright side sdague us back to look at the grenade change to require cells v2 in ocata21:33
mriedemso progress21:33
melwittyay21:33
mriedems/us/is/21:33
mriedemthere are 2 semi related things for cells v221:34
mriedemhttps://blueprints.launchpad.net/nova/+spec/prep-for-network-aware-scheduling-ocata21:34
mriedemlooks like that's moving slowly21:34
mriedemjohn has been caught up in the multiattach stuff lately21:34
dansmithboo21:34
mriedemand https://review.openstack.org/#/c/393205/ which i've asked sdague to look at again, and i need to look at again21:35
mriedemon the bright side alex has started on the json schema validation for query params https://review.openstack.org/#/q/topic:bp/consistent-query-parameters-validation21:35
dansmiththere are multiple bright sides?21:35
mriedemthere are 3 bright sides in this meeting21:36
dansmithoh my21:36
*** VW has quit IRC21:36
mriedem#action need to review https://review.openstack.org/#/c/393205/21:36
mriedem#action review https://review.openstack.org/#/c/399750/21:36
melwittone thing I realized is the remaining consoleauth stuff was covered by a spec that I missed reproposing for ocata. so that has to wait until pike21:36
mriedemdoes it block anything?21:37
mriedemif not implemented21:37
dansmithmight block the upcall thing21:37
dansmithbut also not sure who is going to work on it21:37
mriedemi was never really familiar with that series21:38
melwittyeah, upcall needed to talk to consoleauth service otherwise. so mq switch needed from a cell, I think in that case21:38
mriedemwould have to read up on it21:38
melwitthttps://review.openstack.org/#/q/topic:bp/convert-consoles-to-objects21:38
melwittI was thinking to pick it up, i.e. restore the abandoned patches21:38
mriedemi think someone would have to explain the upcall bits in more detail to me21:39
mriedemto see the relation to cells v2 here21:40
dansmithmriedem: preventing a call from a compute node up to the api db21:40
mriedemb/c the consoleauth stuff is in the api db now?21:40
mriedemno it's not21:40
melwittoh wait, my memory is recalling alaski saying we could just change deployment assumptions to run a consoleauth service per cell21:41
melwittin the meantime21:41
dansmithhmm, does that work?21:41
*** VW has joined #openstack-meeting-321:41
dansmithI thought the problem was that we route the api request by token id,21:41
dansmithwhich we couldn't resolve to a cell without more information21:41
mriedemhttps://review.openstack.org/#/c/321636/ is the cells v2 spec amendment21:41
dansmithunless maybe we change what we return for them to call or something, but that's an api change I *thought*21:41
melwittI was thinking of the message queue part. if consoleauth runs on the api host, the cell would need to be able to talk to the api message queue21:42
melwittto request auth of a token, IIUC21:42
dansmithI dunno, I don't have it in my head for sure21:42
dansmithmaybe you two can go off and figure out what needs doing and decide if someone has time for it this cycle21:42
mriedem"The consoleauth service will be retained for legacy compatibility but21:42
mriedemin a deprecated status, supported for one release. After the21:42
mriedemperiod the consoleauth service can be removed."21:42
dansmiththat's if we do paul's thing I think21:43
melwittif routing is by token id from the api then that's another problem. I'm not that familiar with consoleauth21:43
*** tonytan4ever has quit IRC21:43
melwittyeah21:43
dansmithmelwitt: I dunno, I might be making that up, but I thought there was something about that21:43
mriedemThis can be resolved by adding the instance uuid to21:43
mriedemthe query string in the URL.21:43
mriedemi think it just means adding something like &instance_uuid=foo to the url21:43
melwittdansmith: yeah, I take it as a possibility. I'll dig into it and find out what the deal is21:44
dansmithright21:44
mriedemand then we can map that to a cell21:44
dansmithmriedem: correct21:44
dansmithanyway, we've brought it up a couple weeks in a row now, so maybe we can shoot for having a plan by next week21:44
dansmith?21:44
melwittokay21:44
mriedem#action melwitt to figure out what's up with consoleauth changes wrt cells v221:45
dansmith#action melwitt to detangle the consoleauth stuff for next week21:45
mriedemooo21:45
dansmithmriedem: gdi who is running this meeting?21:45
mriedemforce of habit21:45
melwittmriedem taking over the place21:45
mriedemso on the quotas thing, if there were some steps to get started on that i could maybe take a crack21:45
mriedembut would need some hand holding21:45
mriedemanyway, i just don't do much code stuff these days on any priorities, so i'm open21:46
dansmith#info mriedem's code chops are falling into disrepair21:46
dansmithanything else?21:46
mriedemhey21:47
dansmithheh21:47
mriedemsee me triage that shelve race earlier?!21:47
melwittmriedem: okay, let me think about that. I was first going to do the object code for the quota tables we're keeping (that keep the limits)21:47
mriedemi'm done21:47
melwittand then after that work on the resource counting and replacing reserve/commit/rollback calls21:48
mriedemthe latter part is what i thought sounded somewhat simpler21:48
mriedembut maybe it's not21:48
mriedemanyway, we can take that outside the meeting21:48
dansmithI move we adjourn21:49
mriedemsecond21:49
*** gouthamr has quit IRC21:49
* dansmith wields the gavel21:49
*** julim has quit IRC21:49
dansmith#endmeeting21:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:50
openstackMeeting ended Wed Nov 30 21:49:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-11-30-21.00.html21:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-11-30-21.00.txt21:50
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-11-30-21.00.log.html21:50
*** jtomasek has quit IRC21:51
*** matrohon has quit IRC21:51
*** haleyb_ has joined #openstack-meeting-321:58
*** jrist has quit IRC22:01
*** lpetrut has quit IRC22:01
*** lblanchard has quit IRC22:01
*** clu_ has quit IRC22:01
*** jrist has joined #openstack-meeting-322:02
*** haleyb_ has quit IRC22:03
*** jrist has quit IRC22:07
*** claudiub|2 has joined #openstack-meeting-322:09
*** bpokorny has quit IRC22:11
*** dimtruck is now known as zz_dimtruck22:11
*** slaweq_ has joined #openstack-meeting-322:11
*** claudiub has quit IRC22:13
*** bpokorny has joined #openstack-meeting-322:13
*** clu_ has joined #openstack-meeting-322:18
*** lblanchard has joined #openstack-meeting-322:23
*** mriedem has quit IRC22:39
*** bobmel has quit IRC22:39
*** bobmel has joined #openstack-meeting-322:40
*** lblanchard has quit IRC22:42
*** jrist has joined #openstack-meeting-322:42
*** VW has quit IRC22:44
*** slaweq_ has quit IRC22:44
*** kzaitsev_mb has quit IRC22:46
*** slaweq_ has joined #openstack-meeting-322:46
*** haleyb_ has joined #openstack-meeting-322:59
*** alexismonville has joined #openstack-meeting-323:01
*** haleyb_ has quit IRC23:04
*** rarcea_ has quit IRC23:06
*** alexismonville has quit IRC23:10
*** bpokorny has quit IRC23:10
*** bpokorny has joined #openstack-meeting-323:11
*** alexismonville has joined #openstack-meeting-323:13
*** bpokorny has quit IRC23:15
*** alexismonville has quit IRC23:17
*** bpokorny has joined #openstack-meeting-323:18
*** spotz is now known as spotz_zzz23:18
*** topol has quit IRC23:20
*** spzala has joined #openstack-meeting-323:21
*** spzala has quit IRC23:26
*** spzala has joined #openstack-meeting-323:36
*** claudiub|2 has quit IRC23:37
*** sdague has quit IRC23:38
*** revon has quit IRC23:42
*** dtp has quit IRC23:46
*** rbak has quit IRC23:52
*** bpokorny has quit IRC23:58
*** bpokorny has joined #openstack-meeting-323:58

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